[Touch-packages] [Bug 1982692] [NEW] screen flickering
Public bug reported: sometimes screen is continuously flickering ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 17:10:15 2022 DistUpgraded: 2022-04-25 11:41:26,744 INFO cache.commit() DistroCodename: jammy 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 / Radeon 520 Mobile] [1028:06b2] InstallationDate: Installed on 2021-02-24 (515 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=e2bb84ca-dd6e-40ec-8b37-00f696fb958e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-04-25 (90 days ago) dmi.bios.date: 09/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 04D1V1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd09/07/2020:br1.9:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct10:cvr:sku06B2: dmi.product.family: Inspiron dmi.product.name: Inspiron 5559 dmi.product.sku: 06B2 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1982692 Title: screen flickering Status in xorg package in Ubuntu: New Bug description: sometimes screen is continuously flickering ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 17:10:15 2022 DistUpgraded: 2022-04-25 11:41:26,744 INFO cache.commit() DistroCodename: jammy 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 / Radeon 520 Mobile] [1028:06b2] InstallationDate: Installed on 2021-02-24 (515 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=e2bb84ca-dd6e-40ec-8b37-00f696fb958e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-04-25 (90 days ago) dmi.bios.date: 09/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 04D1V1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Verified in both focal and impish that the bug is fixed with the keyutils package in the proposed repo. Also ran some sanity tests to make sure that other functionalities are not affected. You can mark this as verified. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Fix Committed Status in keyutils source package in Impish: Fix Committed Status in keyutils source package in Jammy: Fix Released Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Thanks Robie/Utkarsh. I will test out the package in the proposed repositories and update here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Fix Committed Status in keyutils source package in Impish: Fix Committed Status in keyutils source package in Jammy: Fix Released Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975554] [NEW] Apply default TTL to records obtained from getaddrinfo(): Focal and beyond
Public bug reported: The issue was fixed for bionic in: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453 However, was missed for Focal, Impish and Jammy. Since I'm not getting responses for that bug, I'm opening this one. ** Affects: keyutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1975554 Title: Apply default TTL to records obtained from getaddrinfo(): Focal and beyond Status in keyutils package in Ubuntu: New Bug description: The issue was fixed for bionic in: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453 However, was missed for Focal, Impish and Jammy. Since I'm not getting responses for that bug, I'm opening this one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1975554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Hi Utkarsh, Is the backport taken for all the above versions as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Hi Robie, Any progress on the keyutils backports for 22.04 and 22.10? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Thanks Robie. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Utkarsh/Robie, When can we expect similar backports to Ubuntu 20.04 and newer? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Committed Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
We have validated this fix. The fix works as expected. We've also run several xfstests using various SMB mount scenarios to see that nothing regressed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Committed Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Just a quick update. We've hit some issues during the tests, and we're trying to debug and understand if it's an actual bug, or a setup issue. I will keep this page updated on the results. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Committed Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Thanks for the update, Robie. I'll let you know how our testing goes with this soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Committed Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946625] [NEW] package libgrilo-0.3-0:amd64 0.3.12-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
Public bug reported: this problem occur while updating software using, update-manager command. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgrilo-0.3-0:amd64 0.3.12-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 11 13:38:06 2021 DuplicateSignature: package:libgrilo-0.3-0:amd64:0.3.12-1ubuntu0.1 Setting up libxatracker2:amd64 (21.0.3-0ubuntu0.3~20.04.2) ... dpkg: error processing package libgrilo-0.3-0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-10-10 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: grilo Title: package libgrilo-0.3-0:amd64 0.3.12-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grilo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo in Ubuntu. https://bugs.launchpad.net/bugs/1946625 Title: package libgrilo-0.3-0:amd64 0.3.12-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in grilo package in Ubuntu: New Bug description: this problem occur while updating software using, update-manager command. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgrilo-0.3-0:amd64 0.3.12-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 11 13:38:06 2021 DuplicateSignature: package:libgrilo-0.3-0:amd64:0.3.12-1ubuntu0.1 Setting up libxatracker2:amd64 (21.0.3-0ubuntu0.3~20.04.2) ... dpkg: error processing package libgrilo-0.3-0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-10-10 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: grilo Title: package libgrilo-0.3-0:amd64 0.3.12-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo/+bug/1946625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1938814] [NEW] package gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a
Public bug reported: Unable to install it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: libevview3-3:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 3 20:40:35 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-08-03 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: gst-plugins-base1.0 Title: package gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1938814 Title: package gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: Unable to install it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: libevview3-3:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 3 20:40:35 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-08-03 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: gst-plugins-base1.0 Title: package gstreamer1.0-plugins-base:amd64 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1938814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855445] [NEW] Touchpad is not working
Public bug reported: Day before yesterday, I updated Ubuntu in my laptop, then the next morning when I try to use touch-pad it wasn't working, I switched to windows to see whether touch-pad was working or not, it was working fine. Here's the details $ xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=17 [slave pointer (2)] ⎜ ↳ Synaptics TM3252-001 id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ Logitech USB Receiver id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=12 [slave keyboard (3)] ↳ Intel HID events id=14 [slave keyboard (3)] ↳ Dell WMI hotkeys id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=18 [slave keyboard (3)] $ dmesg | grep i2c [0.766631] i2c /dev entries driver [2.419114] psmouse serio1: synaptics: Your touchpad (PNP: SYN0609 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. [ 34.129216] i2c_hid i2c-DELL0792:00: i2c-DELL0792:00 supply vdd not found, using dummy regulator [ 34.837858] input: Synaptics TM3252-001 as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-0/i2c-DELL0792:00/0018:06CB:7F09.0003/input/input13 [ 34.837945] hid-rmi 0018:06CB:7F09.0003: input,hidraw2: I2C HID v1.00 Mouse [DELL0792:00 06CB:7F09] on i2c-DELL0792:00 $ locate i2c-designware /lib/modules/4.15.0-70-generic/kernel/drivers/i2c/busses/i2c-designware-pci.ko /lib/modules/4.15.0-72-generic/kernel/drivers/i2c/busses/i2c-designware-pci.ko /usr/src/linux-headers-4.15.0-70/include/linux/platform_data/i2c-designware.h /usr/src/linux-headers-4.15.0-72/include/linux/platform_data/i2c-designware.h $ uname -a Linux ubuntu-vostro-14-3468 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -crid Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1855445 Title: Touchpad is not working Status in unattended-upgrades package in Ubuntu: New Bug description: Day before yesterday, I updated Ubuntu in my laptop, then the next morning when I try to use touch-pad it wasn't working, I switched to windows to see whether touch-pad was working or not, it was working fine. Here's the details $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)] ⎜ ↳ Synaptics TM3252-001id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Logitech USB Receiver id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=12 [slave keyboard (3)] ↳ Intel HID eventsid=14 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Logitech USB Receiver id=18 [slave keyboard (3)] $
[Touch-packages] [Bug 1847216] [NEW] motd-news only works with one URL even though docs say mutiple URLs can be configured
Public bug reported: The motd-news script etc/update-motd/50-motd-news the following section ``` # Loop over any configured URLs for u in $URLS; do # Ensure https:// protocol, for security reasons case $u in https://*) true ;; https://motd.ubuntu.com) u="$u/$codename/$arch" ;; *) continue ;; esac # If we're forced, set the wait to much higher (1 minute) [ "$FORCED" = "1" ] && WAIT=60 # Fetch and print the news motd if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" -o- "$u" >"$NEWS" 2>"$ERR"; then echo # At most, 10 lines of text, remove control characters, print at most 80 characters per line safe_print "$NEWS" # Try to update the cache safe_print "$NEWS" 2>/dev/null >$CACHE || true else : > "$CACHE" fi done ``` As you can see the $CACHE gets overwritten if multiple URLs are configured in /etc/default/motd-news /etc/default/motd-news has ``` # Configure the source of dynamic MOTD news # White space separated list of 0 to many news services # For security reasons, these must be https # and have a valid certificate # Canonical runs a service at motd.ubuntu.com, and you # can easily run one too URLS="https://motd.ubuntu.com; ``` ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: motd ** Description changed: - The motd-news script etc/update-motd/50-motd-news + The motd-news script etc/update-motd/50-motd-news the following section ``` # Loop over any configured URLs for u in $URLS; do - # Ensure https:// protocol, for security reasons - case $u in - https://*) - true - ;; - https://motd.ubuntu.com) - u="$u/$codename/$arch" - ;; - *) - continue - ;; - esac - # If we're forced, set the wait to much higher (1 minute) - [ "$FORCED" = "1" ] && WAIT=60 - # Fetch and print the news motd - if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" -o- "$u" >"$NEWS" 2>"$ERR"; then - echo - # At most, 10 lines of text, remove control characters, print at most 80 characters per line - safe_print "$NEWS" - # Try to update the cache - safe_print "$NEWS" 2>/dev/null >$CACHE || true - else - : > "$CACHE" - fi + # Ensure https:// protocol, for security reasons + case $u in + https://*) + true + ;; + https://motd.ubuntu.com) + u="$u/$codename/$arch" + ;; + *) + continue + ;; + esac + # If we're forced, set the wait to much higher (1 minute) + [ "$FORCED" = "1" ] && WAIT=60 + # Fetch and print the news motd + if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" -o- "$u" >"$NEWS" 2>"$ERR"; then + echo + # At most, 10 lines of text, remove control characters, print at most 80 characters per line + safe_print "$NEWS" + # Try to update the cache + safe_print "$NEWS" 2>/dev/null >$CACHE || true + else + : > "$CACHE" + fi done ``` As you can see the $CACHE gets overwritten if multiple URLs are configured in /etc/default/motd-news /etc/default/motd-news has ``` # Configure the source of dynamic MOTD news # White space separated list of 0 to many news services # For security reasons, these must be https # and have a valid certificate # Canonical runs a service at motd.ubuntu.com, and you # can easily run one too - URLS="https://tprasadtp.github.io/motd/spacex/upcoming https://tprasadtp.github.io/motd/nasa/apod; + URLS="https://motd.ubuntu.com; ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1847216 Title: motd-news only works with one URL even though docs say mutiple URLs can be configured Status in base-files package in Ubuntu: New Bug description: The motd-news script etc/update-motd/50-motd-news the following section ``` # Loop over any configured URLs for u in $URLS; do # Ensure https:// protocol, for security reasons case $u in https://*) true ;;
[Touch-packages] [Bug 1779925] [NEW] Compiz not running
Public bug reported: To whoever reading this, I assume that you are reading the below message after seeing the auto generated bug report. I'm just explaining below the scenario of how and when I got the error and how it got fixed. Till date I'm not sure what caused this error in first place. The details of the error: I used to get this error every time I started the system. Report error also used to fail. Ironically now report error is working when there is no longer an error. Coupled with this error one day my desktop user interface itself was not working as compiz was not running. I tried different solutions from many forums, community pages online. But none has worked. I had opened guest session out of curiosity to check if it works and it worked perfectly. Then I observed a differnce and made the below change in config file ~/.config/compiz-1/compizconfig/config ## FROM profile = unity-lowgfx ## TO profile = unity Then after re-start it started working. No errors since then. P.S. Ignore if the above doesn't make any sense or it is not related the bug report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jul 4 00:17:09 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.60, 4.4.0-122-generic, x86_64: installed ndiswrapper, 1.60, 4.4.0-128-generic, x86_64: installed ndiswrapper, 1.60, 4.4.0-130-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2014-09-25 (1377 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3521 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=9717b719-a04b-4f40-ac66-56a9b1165260 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 06RYX8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron3521:pvrA08:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Jul 3 21:29:09 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 939 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1779925 Title: Compiz not running Status in xorg package in Ubuntu: New Bug description: To whoever reading this, I assume that you are reading the below message after seeing the auto generated bug report. I'm just explaining below the scenario of how and when I got the error and how it got fixed. Till date I'm not sure what caused this error in first place. The details of the error: I used to get this error every time I started the system. Report error also used to fail. Ironically now report error is working when there is no longer an error. Coupled with this error one day my desktop user interface itself was not working as compiz was not running. I tried different solutions from many
[Touch-packages] [Bug 1760178] [NEW] package isc-dhcp-client 4.3.3-5ubuntu12.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
Public bug reported: Error invoking sudo command ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu12.9 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 22 08:59:13 2018 DhclientLeases: ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-02-09 (48 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=1fd42b9f-fe42-47e2-a9b7-f6a3a0a84af5 ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.3.3-5ubuntu12.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: isc-dhcp (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 isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1760178 Title: package isc-dhcp-client 4.3.3-5ubuntu12.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in isc-dhcp package in Ubuntu: New Bug description: Error invoking sudo command ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu12.9 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 22 08:59:13 2018 DhclientLeases: ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-02-09 (48 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=1fd42b9f-fe42-47e2-a9b7-f6a3a0a84af5 ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.3.3-5ubuntu12.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1760178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
I can confirm this bug exists. OS version: Ubuntu 18.04 beta rc Hardware: Intel core i5 7400 (Kaby lake processor) with Intel HD graphics 630 supporting VP9 10-bit and 8-bit video decoding. In version 1.8.x of the driver the VP9 decoding is broken, the corresponding upstream patch got into 2.0.0. But since VP9 profiles are missing in 2.0.0 driver in Ubuntu, hardware acceleration is absent, so high cpu and power usage. The buggy driver 1.8.x is used in the vlc snap too and snap developers doubt the driver version in snap will be upgraded. * VP9 decoding broken in 17.10 * VP9 decoding broken in snap packages * VP9 decoding broken in 18.04 beta rc Either driver version has to be updated to 2.1.0 or at-least cherry pick a one line patch to current Ubuntu core snap, a link for which I will mention below. Upstream driver patch: https://github.com/intel/intel-vaapi- driver/commit/9d66570032fb02b1e79a883af7697b035d700a8e Upstream bug report: https://github.com/intel/intel-vaapi- driver/issues/297 In any way kindly support VP9 hardware decoding via supported Intel hardwares in 18.04 or in 17.10(by backporting/cherry picking) or atleast via updated snap core/apps. ** Bug watch added: github.com/intel/intel-vaapi-driver/issues #297 https://github.com/intel/intel-vaapi-driver/issues/297 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: New Status in libva package in Ubuntu: New Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:
[Touch-packages] [Bug 1731532] [NEW] package liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 failed to install/upgrade: package liblightdm-gobject-1-0:amd64 is not ready for configuration cannot config
Public bug reported: Please fix the issue as soon as possible. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Nov 10 18:32:18 2017 DuplicateSignature: package:liblightdm-gobject-1-0:amd64:1.18.3-0ubuntu1.1 Processing triggers for ureadahead (0.100.0-19) ... dpkg: error processing package liblightdm-gobject-1-0:amd64 (--configure): package liblightdm-gobject-1-0:amd64 is not ready for configuration ErrorMessage: package liblightdm-gobject-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: lightdm Title: package liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 failed to install/upgrade: package liblightdm-gobject-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1731532 Title: package liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 failed to install/upgrade: package liblightdm-gobject-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in lightdm package in Ubuntu: New Bug description: Please fix the issue as soon as possible. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Nov 10 18:32:18 2017 DuplicateSignature: package:liblightdm-gobject-1-0:amd64:1.18.3-0ubuntu1.1 Processing triggers for ureadahead (0.100.0-19) ... dpkg: error processing package liblightdm-gobject-1-0:amd64 (--configure): package liblightdm-gobject-1-0:amd64 is not ready for configuration ErrorMessage: package liblightdm-gobject-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: lightdm Title: package liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 failed to install/upgrade: package liblightdm-gobject-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1731532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692247] Re: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed')
Following commands helped me get this fixed sudo apt-get install --reinstall iproute2 sudo apt-get update sudo apt-get upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692247 Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') Status in iproute2 package in Ubuntu: Incomplete Bug description: I dont know anything. I just try to instal some programs on my comp, and when i try to start virtualbox it cant. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: iproute2: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat May 20 16:22:19 2017 DpkgTerminalLog: dpkg: error processing package iproute2 (--configure): package iproute2 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-02-20 (88 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692055] [NEW] Printer not printing even though it is installed but printing in my windows system
Public bug reported: Printer not printing even though it is installed but printer is printing in my windows system ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 3.13.0-36.63+hwe3-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 19 21:27:17 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-06-09 (710 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A2A3MD8h MachineType: Dell Inc. Latitude 3450 PpdFiles: Canon-LBP2900: Canon LBP-3360 - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=f8fb5d2a-2608-412d-bd82-e59860e815c2 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PW7C8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd04/15/2015:svnDellInc.:pnLatitude3450:pvr01:rvnDellInc.:rn0PW7C8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1692055 Title: Printer not printing even though it is installed but printing in my windows system Status in cups package in Ubuntu: New Bug description: Printer not printing even though it is installed but printer is printing in my windows system ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 3.13.0-36.63+hwe3-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 19 21:27:17 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-06-09 (710 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A2A3MD8h MachineType: Dell Inc. Latitude 3450 PpdFiles: Canon-LBP2900: Canon LBP-3360 - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=f8fb5d2a-2608-412d-bd82-e59860e815c2 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PW7C8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd04/15/2015:svnDellInc.:pnLatitude3450:pvr01:rvnDellInc.:rn0PW7C8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1692055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676736] [NEW] package console-setup 1.108ubuntu15.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat
Public bug reported: I am unable to update my software ProblemType: Package DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: keyboard-configuration: Install keyboard-configuration: Configure console-setup-linux: Configure console-setup: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Mar 28 11:07:48 2017 DpkgHistoryLog: Start-Date: 2017-03-28 11:07:33 Commandline: apt-get install -f Requested-By: prasad (1000) Upgrade: keyboard-configuration:amd64 (1.108ubuntu15.2, 1.108ubuntu15.3) DuplicateSignature: package:console-setup:1.108ubuntu15.3 Installing new version of config file /etc/console-setup/compose.ISO-8859-9.inc ... dpkg: error processing package console-setup (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-05-30 (301 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: console-setup Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (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 console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1676736 Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in console-setup package in Ubuntu: New Bug description: I am unable to update my software ProblemType: Package DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: keyboard-configuration: Install keyboard-configuration: Configure console-setup-linux: Configure console-setup: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Mar 28 11:07:48 2017 DpkgHistoryLog: Start-Date: 2017-03-28 11:07:33 Commandline: apt-get install -f Requested-By: prasad (1000) Upgrade: keyboard-configuration:amd64 (1.108ubuntu15.2, 1.108ubuntu15.3) DuplicateSignature: package:console-setup:1.108ubuntu15.3 Installing new version of config file /etc/console-setup/compose.ISO-8859-9.inc ... dpkg: error processing package console-setup (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-05-30 (301 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: console-setup Title: package console-setup 1.108ubuntu15.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1676736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241101]
*** Bug 457512 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in gtk+2.0 package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460038] Re: libarchive extracts zip as corrupt files but no warning or error
I can confirm the bug. Check this bug report for details https://bugs.kde.org/show_bug.cgi?id=339536 ** Bug watch added: KDE Bug Tracking System #339536 https://bugs.kde.org/show_bug.cgi?id=339536 ** Changed in: libarchive (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1460038 Title: libarchive extracts zip as corrupt files but no warning or error Status in libarchive package in Ubuntu: Confirmed Bug description: The attached zip file is produced by AirDroid and can be extracted successfully by unzip 6.00, ASUS File Manager for Android, and Windows 8.1. However libarchive13 version 3.1.2-7ubuntu2.1, in Linux Mint KDE 17.1 amd64, while extracts the files without any warning or error, results in corrupt files. These are all JPG files which cannot be viewed when extracted by Ark. Tested using both: * Ark 2.19 (4:4.14.2-0ubuntu1~ubuntu14.04~ppa1) * bsdcpio 3.1.2-7ubuntu2.1 Reproducible: Always Steps to Reproduce: 1. Extract Actual Results: Corrupt JPGs Expected Results: Proper JPGs For complete thread/diagnostics history please see https://bugs.kde.org/show_bug.cgi?id=348357 Upstream bug: https://github.com/libarchive/libarchive/issues/554 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1460038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 295832] Re: Alsa does not honor pcm.!default because of /usr/share/alsa/pulse.conf
This bug exists in Ubuntu 14.04.
I created ~/.asoundrc and attempted to override pcm.!default which was
not honoured by ALSA due to /usr/share/alsa/alsa.conf.d/pulse.conf
running after /usr/share/alsa/alsa.conf. This caused pulse to override
my defaults.
An easy fix so far seems to be including ~/.asoundrc in
/usr/share/alsa/alsa.conf.d/pulse.conf.
--
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/295832
Title:
Alsa does not honor pcm.!default because of /usr/share/alsa/pulse.conf
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Intrepid:
Fix Released
Bug description:
SRU information follows:
Impact statement: Users of Ubuntu 8.10 find that their
/etc/asound.conf and ~/.asoundrc are ignored due to missing entries in
/usr/share/alsa/pulse.conf. This symptom affects all users with the
pulseaudio package installed *and* the daemon (regardless of system-
wide or per-user session instance) running.
Bug resolution: The missing lines [referencing /etc/asound.conf and
~/.asoundrc] are added to /usr/share/alsa/pulse.conf. The change to
the errors line mimics libasound2's /usr/share/alsa/alsa.conf [to not
throw an error upon a missing ~/.asoundrc]. With these changes, users
of default Ubuntu 8.10 will have their /etc/asound.conf and
~/.asoundrc, if extant, honoured with higher priority than the
configuration shipped by pulseaudio, thereby restoring expected alsa-
lib runtime conf behaviour (for native ALSA applications) prior to
intrepid. If either /etc/asound.conf or ~/.asoundrc is missing, the
current intrepid behaviour of pulseaudio overriding {pcm,ctl}.default
is retained. This change is shown via Loggerhead here:
http://bazaar.launchpad.net/~crimsun/pulseaudio/ubuntu/revision/38?remember=36compare_revid=36.
SRU patch:
http://launchpadlibrarian.net/2123/pulseaudio_0.9.10-2ubuntu9.3.debdiff
Instructions to reproduce the symptom: Create an ~/.asoundrc with the
following contents only:
# --- begin ---
pcm.!default {
type plug
slave hw:5,0
}
ctl.!default {
type hw
card 5
}
# --- end ---
After a fresh GNOME session login, open Applications Accessories Terminal,
and use `speaker-test -Ddefault -c2' to verify that:
1) the speaker-test output continues to play (until interrupt, ctrl+c)
through the PulseAudio-configured default device;
2) no errors are generated by alsa-lib.
These two symptoms verify that ~/.asoundrc is ignored.
Regression potential: Users who have a misconfigured /etc/asound.conf
or ~/.asoundrc will notice that native ALSA apps refuse to start and
throw alsa-lib error(s), which can be resolved by removing the
offending conffile.
Original description follows:
Binary package hint: pulseaudio
Even if I define a pcm.!default section in ~/.asoundrc, /usr/share
/pulse-alsa.conf overrides this definition, so the default alsa output
is always pulseaudio.
If I comment the pcm.!default and ctl.!default in /usr/share/alsa
/pulse-alsa.conf everything behaves as normal.
Using Intrepid amd64.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/295832/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423679] [NEW] no resume after suspend
Public bug reported: I had been using ubuntu 12.10, system resume after suspend worked fine. Now I have upgraded to 14.04 LTS and the system does not resume after a suspend. Also I would like to know if there's any way in which I can create a hotspot in ubuntu using a WIFI connection. The inbuilt hotspot works like android, i.e. the wifi connection stops as soon as the hotspot is created, I wish to use the wifi connection to create a hotspot for my phone (just like connectify me software on windows). Help me. Avinash Prasad ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 20 01:30:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1950] InstallationDate: Installed on 2015-02-16 (3 days ago) InstallationMedia: It MachineType: Hewlett-Packard HP ProBook 445 G1 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic root=/dev/mapper/it--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1:pvrA2018CD200:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 19 20:05:45 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1423679 Title: no resume after suspend Status in xorg package in Ubuntu: New Bug description: I had been using ubuntu 12.10, system resume after suspend worked fine. Now I have upgraded to 14.04 LTS and the system does not resume after a suspend. Also I would like to know if there's any way in which I can create a hotspot in ubuntu using a WIFI connection. The inbuilt hotspot works like android, i.e. the wifi connection stops as soon as the hotspot is created, I wish to use the wifi connection to create a hotspot for my phone (just like connectify me software on windows). Help me. Avinash Prasad ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 20 01:30:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8450G] [1002:9995] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard
[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
** Also affects: xorg-server Importance: Undecided Status: New ** No longer affects: xorg-server -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in xorg package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible chops (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway. Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369270] [NEW] unable to reset key storage
Public bug reported: I am unable to access certificate/ key storage. Please suggest remedy. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Sep 14 20:20:45 2014 DistUpgraded: 2014-08-15 01:14:08,508 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-34-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-36-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05ea] InstallationDate: Installed on 2014-05-25 (112 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=4ffa5340-61a4-4ab9-8e6f-994622ca85ba ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-08-14 (30 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 01TCR4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn01TCR4:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Sep 14 19:47:04 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 939 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1369270 Title: unable to reset key storage Status in “xorg” package in Ubuntu: New Bug description: I am unable to access certificate/ key storage. Please suggest remedy. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Sep 14 20:20:45 2014 DistUpgraded: 2014-08-15 01:14:08,508 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-34-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-36-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05ea] InstallationDate: Installed on 2014-05-25 (112 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=4ffa5340-61a4-4ab9-8e6f-994622ca85ba ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-08-14 (30 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 01TCR4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias:
