[Touch-packages] [Bug 2081645] Re: (during boot) failed: Cannot assign requested address
I've solved this by statically entering the first IPv6 address in my netplan config. Previously it came up via DHCPv6, whereas the second IPv6 address was static. I don't know why the above script didn't achieve the required delay, given that it explicitly waits for the IPv6 address which nginx fails to bind to, but I'll close this as everything is working well now. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Invalid Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
I've added my script back in to the wait-online override, which looks like this. After a few reboots, nginx once again failed to bind to this address. My hacky solution is to add a 5 second sleep to the end of this script. #!/bin/bash ip=$(ip -6 address) until [[ $ip == *"2603:af50:1630:aec9:f19a:227e:2f54:5c73"* ]] do ip=$(ip -6 address) sleep 1 done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
Another thing I tried was an additional script to loop "ip address" and look for the IPv6 address I need before wait-online finishes, and even that failed to sufficiently delay the boot process enough to allow nginx to bind to the address. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
** Attachment added: "wait-online.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+attachment/5826892/+files/wait-online.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
** Attachment added: "networkd.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+attachment/5826893/+files/networkd.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
> it does not override the existing one (maybe you already know that) Yep, I did know that. My drop-in creates a second wait-online invocation, but since they are both waiting I saw no need to remove the initial invocation. > I am wondering if networkd is reporting the link as configured after *one* of the addresses is configured In the log I posted previously, you can see systemd-networkd reports the required address as up *before* nginx fails to bind to the very same address. Two logs to follow, I put the nginx failure at the end of networkd.txt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
Any update? I'm still seeing failures to bind to an IPv6 address that systemd-networkd has previously reported as being up. I can insert an arbitrary 5 second pause as a workaround, but this should not be necessary. ubuntu@hawk:~$ journalctl -g 2603:af50:1630:aec9:f19a:227e:2f54:5c73 -b Oct 10 13:34:05 hawk systemd-networkd[311]: ens5: DHCPv6 address 2603:af50:1630:aec9:f19a:227e:2f54:5c73/128 (valid for 7min 29s, preferred for 2min 19s) Oct 10 13:34:05 hawk named[566]: listening on IPv6 interface ens5, 2603:af50:1630:aec9:f19a:227e:2f54:5c73#53 Oct 10 13:34:06 hawk nginx[585]: nginx: [emerg] bind() to [2603:af50:1630:aec9:f19a:227e:2f54:5c73]:443 failed (99: Cannot assign requested address) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
Logs attached. I created the file: /etc/systemd/system/systemd-networkd-wait-online.service.d/override.conf in order to delay boot until IPv6 is available. ** Attachment added: "networkctl.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+attachment/5821598/+files/networkctl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
** Attachment added: "cat-sd-wait-online.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+attachment/5821600/+files/cat-sd-wait-online.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
** Attachment added: "wait-online.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+attachment/5821599/+files/wait-online.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
Also, there is no problem launching services manually after boot, and the issue doesn't happen on every boot, so whatever is happening is very time-dependant. I can manually add a few seconds of delay to the boot process, but that feels hacky. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
I'm using two IPv6 addresses, bind9 is binding to one, which as you say is fine. But when nginx and dovecot try to bind to the other IPv6 address during boot, they (sometimes) fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
This sounds very similar: https://github.com/systemd/systemd/issues/650 Nevertheless that bug was resolved, so it may be a regression or something else entirely. ** Bug watch added: github.com/systemd/systemd/issues #650 https://github.com/systemd/systemd/issues/650 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: New Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] Re: (during boot) failed: Cannot assign requested address
I can launch the services manually after boot, so the IP addresses are fine. It's a question of why during boot systemd-networkd is reporting the IPv6 addresses as available before they actually are. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: New Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2081645] [NEW] (during boot) failed: Cannot assign requested address
Public bug reported: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journal-1.txt" https://bugs.launchpad.net/bugs/2081645/+attachment/5820732/+files/journal-1.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: New Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+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 2056153] [NEW] Removing the systemd-resolved package breaks DNSSEC validation
Public bug reported: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2056153 Title: Removing the systemd-resolved package breaks DNSSEC validation Status in systemd package in Ubuntu: New Bug description: Removing the systemd-resolved package breaks glibc DNSSEC validation, because it removes an existing line from the new /etc/resolv.conf file. This line should be retained so that packages like Exim can continue to use the AD bit after systemd-resolved is removed. ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search vcn.oraclevcn.com ubuntu@instance:~$ sudo apt remove systemd-resolved ubuntu@instance:~$ grep -v '^#' /etc/resolv.conf nameserver 169.254.169.254 search vcn.oraclevcn.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056153/+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 1823171] Re: systemd-resolve hides DS records in explicit queries
DNSSEC isn't required to query a DS record. The reason your query succeeded after you enabled DNSSEC is because systemd-resolved caches it internally as a result of the DNSSEC lookup. Once the DS query is cached, the bug will not manifest. Another way to cache it is: ubuntu@server:~$ dig ripe.net ds @127.0.0.53 +short ubuntu@server:~$ dig ripe.net ds @127.0.0.54 +short 10186 13 2 BC15C85E16FE7C651EAAFCEE3B1F1C956217A5B70A536BFEF38C24A9 AB7B9A3F ubuntu@server:~$ dig ripe.net ds @127.0.0.53 +short 10186 13 2 BC15C85E16FE7C651EAAFCEE3B1F1C956217A5B70A536BFEF38C24A9 AB7B9A3F -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823171 Title: systemd-resolve hides DS records in explicit queries Status in systemd package in Ubuntu: Invalid Bug description: When querying for DS resource records on a DNSSEC signed domain using dig, the DS records are not shown when the system is using systemd- resolve. Run: dig +short DS ripe.net Expected: something like 40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6 Actual result: no output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.15 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 4 14:14:06 2019 MachineType: MSI MS-7A70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=/dev/mapper/system-slash ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.80 dmi.board.asset.tag: Default string dmi.board.name: B250M PRO-VDH (MS-7A70) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A70 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+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 1823171] Re: systemd-resolve hides DS records in explicit queries
Still a problem in 23.10 (mantic). Using resolved's passthrough address 127.0.0.54 results in success. After it's cached, the default 127.0.0.53 address is happy to return it. ubuntu@server:~$ dig arin.net ds @127.0.0.53 +short ubuntu@server:~$ dig arin.net ds @127.0.0.54 +short 50716 8 2 EB708BF25CC3F568B017DA1BFFBD6B31FE4B94B4D89D1C27C1603133 5CE50526 ubuntu@server:~$ dig arin.net ds @127.0.0.53 +short 50716 8 2 EB708BF25CC3F568B017DA1BFFBD6B31FE4B94B4D89D1C27C1603133 5CE50526 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823171 Title: systemd-resolve hides DS records in explicit queries Status in systemd package in Ubuntu: Confirmed Bug description: When querying for DS resource records on a DNSSEC signed domain using dig, the DS records are not shown when the system is using systemd- resolve. Run: dig +short DS ripe.net Expected: something like 40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6 Actual result: no output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.15 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 4 14:14:06 2019 MachineType: MSI MS-7A70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=/dev/mapper/system-slash ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.80 dmi.board.asset.tag: Default string dmi.board.name: B250M PRO-VDH (MS-7A70) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A70 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+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 1782709] Re: Updating systemd kills network on bionic
Despite my comment above, I still have this problem when using netplan. Here is my /etc/netplan/config.yaml (external IP quatrains have been changed), the setup is that enp8s1 provides internet access (with metric 49) and enp7s0 provides local lan access *and* (with metric 51) fallback internet access: network: version: 2 renderer: networkd ethernets: enp8s1: dhcp4: false wakeonlan: true addresses: [111.94.100.80/24] nameservers: addresses: [111.94.100.1] # makes this the default route - deprecated #gateway4: 111.94.100.1 link-local: [] routes: - to: default via: 111.94.100.1 metric: 49 on-link: true enp7s0: dhcp4: false wakeonlan: true addresses: [192.168.20.88/24] nameservers: addresses: [192.168.20.1] link-local: [] routes: - to: default via: 192.168.20.1 metric: 51 on-link: true # to avoid conflict with enp8s1 default route, but makes no difference #table: 76 - to: 192.168.20.0/24 via: 192.168.20.1 metric: 48 When working properly: # ip route show to default default via 111.94.100.1 dev enp8s1 proto static metric 49 onlink default via 192.168.20.1 dev enp7s0 proto static metric 51 onlink But after systemd reconfiguration we have two default routes with a metric of 0! We have to delete one of them to restore the correct setup (as above) and get internet access via enp8s1 again. My workaround is continuous monitoring of syslog for a line indicating that the network has been (re)configured by systemd and then running some bash code like this (extract): if [[ -n $(ip route show to default metric 0 via 192.168.20.1) ]]; then NUM_DEFAULT_ROUTES=$(ip route show to default|wc -l) if [[ $NUM_DEFAULT_ROUTES -gt 2 ]]; then ip route delete to default metric 0 via 192.168.20.1 fi fi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-gen
[Touch-packages] [Bug 2049977] [NEW] journalctl --follow --grep lists lines in wrong order
Public bug reported: Version: systemd 253 (253.5-1ubuntu6.1) (23.10 mantic) When executing: journalctl --follow --grep="session closed" the lines are printed from newest to oldest. This essentially makes --follow useless since it is tail-ing in the wrong direction. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2049977 Title: journalctl --follow --grep lists lines in wrong order Status in systemd package in Ubuntu: New Bug description: Version: systemd 253 (253.5-1ubuntu6.1) (23.10 mantic) When executing: journalctl --follow --grep="session closed" the lines are printed from newest to oldest. This essentially makes --follow useless since it is tail-ing in the wrong direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049977/+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 2027930] Re: Open hotspot, open WIFI, exit the network Settings page and enter again, WIFI switch will be closed automatically.
** Package changed: perl (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2027930 Title: Open hotspot, open WIFI, exit the network Settings page and enter again, WIFI switch will be closed automatically. Status in Ubuntu: New Bug description: 1.Environment Module manufacturer: Fibocom Model of module: L860 R+ FW Packkage=18601.5001.00.01.16.54 Enumeration Port：MBIM+2AT OS：22.04.2 LTS Kernel: 6.1.27-060127 Test SIM Card: Unicom PLMN: 46001 Module IMEI: 359869740059493 Sympthon: Open hotspot, open WIFI, exit the network Settings page and enter again, WIFI switch will be closed automatically. FR=100% How to recovery: NA 2. Test Steps 1). Use Unicom card to dial successfully. 2). On the WIFI Settings page, open the hotspot and turn on the WIFI switch. 3). Exit the Settings and go to the Settings page again. 3. Expected Result The WIFI switch is on 4. Actual Result The WIFI switch is off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2027930/+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 2025382] Re: 22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)
Oracle seem to have started sending invalid bytes at the end of dhcpv6 packets. Systemd has just issued a patch to work around this. Can this patch be backported into Ubuntu 22.04? https://github.com/systemd/systemd/commit/1d2b93ff89f28b18c222321c8c7bc48be2185375 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2025382 Title: 22.04 DHCPv6 IPv6 broken (at least on Oracle OCI) Status in systemd package in Ubuntu: New Bug description: Ubuntu 22.04.2 LTS kernel 5.15.0-1038-oracle systemd 249.11-0ubuntu3.9 After an update a couple weeks ago, Ubuntu 22.04 can no longer get IPv6 via DHCPv6 systemd-networkd, at least on Oracle OCI, but there are also other similar reports, e.g. https://ubuntuforums.org/showthread.php?t=2487465&p=14146758 Oracle seems to be aware of the issue but they claim it's a Ubuntu 22.04 bug: https://community.oracle.com/customerconnect/discussion/687610/oci- ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp The workaround to assign a static IPv6 is not great when managing multiple cloud instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2025382/+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 2015355] Re: Please backport patches for false atari partition detection to Ubuntu 20.04
Thanks for completing the backport, rolling out the proposed .deb now and will comment again once I've confirmed the fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2015355 Title: Please backport patches for false atari partition detection to Ubuntu 20.04 Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Focal: Fix Committed Bug description: [Impact] The partition detection logic in libblkid1 can falsely report the presence of an atari partition. One place where this has a practical impact is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441). [Test Plan] * Create a new qcow2 disk image: $ qemu-img create -f qcow2 test.img 20G * Boot a focal ISO with QEMU/KVM as if installing to test.img: $ qemu-system-x86_64 -enable-kvm -m 4096 -name test -drive file=test.img,format=qcow2 -net nic,model=virtio -net user,hostfwd=tcp::1022-:22 -vga virtio -cdrom ubuntu-20.04.6-desktop- amd64.iso * Using the live environment, format the empty disk. These particular commands were given as a reproducer on the upstream bug report (https://github.com/util-linux/util-linux/issues/1116). $ parted -s /dev/sda -- mklabel msdos $ parted -s /dev/sda -- mkpart primary 0% 10% mkpart primary 10% 30% * Run wipefs on /dev/sda to list partitions. On an affected machine, an atari partition will be listed. On a fixed machine, the incorrect atari listing will be gone. $ wipefs /dev/sda DEVICE OFFSET TYPE UUID LABEL sda0x1fe dos sda0x1d2 atari [Where problems could occur] These patches specifically address the atari prober logic in libblkid. Therefore, if we saw regressions it would be related to detecting atari partitions with libblkid. This would potentially impact tools such as wipefs and blkid, or any other tool that uses libblkid1 for this purpose. [Original Description] There are three patches in util-linux upstream that were released in util-linux 2.37 and prevent false detection of the atari partition table with blkid and wipefs. We see this mostly on LUKS devices initialised via luksFormat reporting there is an atari partition table on the device when it is empty. This causes issues in various places, but one key example for us is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441) RedHat backported these fixes to RHEL 8 under https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be helpful if Ubuntu also backported them to Ubuntu 20.04 which is still running util-linux 2.34 The request is to backport patches based on the https://github.com/util-linux/util-linux/issues/1159 upstream report. Upstream commits to cherry-pick the changes to libblkid/src/partitions/atari.c from: 2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2 282ceadc3a72fc07dd0388b8880fd751490bb87f c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1 # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.6 LTS Release:20.04 Codename: focal # blkid -V blkid from util-linux 2.34 (libblkid 2.34.0, 14-Jun-2019) # blkid -p -s TYPE -s PTTYPE -o export /dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted PTTYPE=atari # lsblk ... sdccrypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-3600a09803830474a735d4c63744c4a56crypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2015355/+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 1796946] Re: cups does not allow adding, deleting or changing printers
This seems related to https://github.com/apple/cups/issues/6076, but this bug would be more appropriately corrected in the Ubuntu installation, because it is a configuration issue. ** Bug watch added: github.com/apple/cups/issues #6076 https://github.com/apple/cups/issues/6076 -- 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/1796946 Title: cups does not allow adding, deleting or changing printers Status in cups package in Ubuntu: New Bug description: Cups tells changing a printer the user would have to authenticate with username and password, but never asks for username and password in tune cups denys access to printer configurations and no changes are possible using the web interface. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18 Uname: Linux 4.15.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 9 20:12:12 2018 InstallationDate: Installed on 2011-10-19 (2546 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for Kyocera_FS-1300D: socket://kymi.fritz.box:9100 device for PDF: cups-pdf:/ device for Roger-Router-Fax: roger-cups:/ MachineType: Acer TravelMate P643-M Papersize: a4 PpdFiles: Kyocera_FS-1128MFP: Kyocera FS-1118MFP - CUPS+Gutenprint v5.2.8-pre1 Roger-Router-Fax: roger fax printer, 1.0 PDF: Generic CUPS-PDF Printer Kyocera_FS-1300D: Kyocera FS-1300D (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-37-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.version: V2.15 dmi.sys.vendor: Acer mtime.conffile..etc.cups.cupsd.conf: 2018-10-09T20:06:41.547549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1796946/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
I bare good news, On 22.10 current build for desktop, this issue no longer is valid as it will be resolved! No more garbled mess. I have been looking about but perhaps the fixes there can be applied to jammy. Been testing 22.10 :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
I think this is to do with the hardware (probably 3D) acceleration under OpenGL since the effect is reproducable by installing virt-manager, setting the type to SPICE instead of VNC and then enabling OpenGL hadware accelerated rendering (3d acceleration as it might be called.) Thus, I believe that this is not limited to just webkit. You may also need to make sure that your MESA_GL_VERSION_OVERRIDE environment variable is set to 3.2 of you are experiancing issues related to "failed to create a GL context" as totem and other apps will experiance this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** No longer affects: linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1978853] [NEW] Volume keys on USB keyboard do not work
Public bug reported: I use a USB keyboard plugged into a laptop running Ubuntu. The USB keyboard has volume adjustment integrated into the function row: mute is Fn + F1, decrease volume is Fn + F2, and increase volume is Fn + F3. On Ubuntu 20.04.4, I could use these keys to do volume adjustment. But, when I upgraded to Ubuntu 22.04, these keys no longer work. I also have volume keys on my laptop integrated into the function row, but the Fn key does not need to be held: mute is just the "F1" key, decrease volume is just the "F2" key, and increase volume is just the "F3" key. These keys adjust volume as expected. I tried plugging in my USB keyboard into a Macbook Pro, and I can use the keyboard to do volume adjustment as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 5481 F pulseaudio /dev/snd/pcmC0D0p: ubuntu 5481 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 17:23:53 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20HDCTO1WW, Realtek ALC298, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2017 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrN1QET68W(1.43):bd11/10/2017:br1.43:efr1.29:svnLENOVO:pn20HDCTO1WW:pvrThinkPadT470:rvnLENOVO:rn20HDCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HD_BU_Think_FM_ThinkPadT470: dmi.product.family: ThinkPad T470 dmi.product.name: 20HDCTO1WW dmi.product.sku: LENOVO_MT_20HD_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1978853 Title: Volume keys on USB keyboard do not work Status in alsa-driver package in Ubuntu: New Bug description: I use a USB keyboard plugged into a laptop running Ubuntu. The USB keyboard has volume adjustment integrated into the function row: mute is Fn + F1, decrease volume is Fn + F2, and increase volume is Fn + F3. On Ubuntu 20.04.4, I could use these keys to do volume adjustment. But, when I upgraded to Ubuntu 22.04, these keys no longer work. I also have volume keys on my laptop integrated into the function row, but the Fn key does not need to be held: mute is just the "F1" key, decrease volume is just the "F2" key, and increase volume is just the "F3" key. These keys adjust volume as expected. I tried plugging in my USB keyboard into a Macbook Pro, and I can use the keyboard to do volume adjustment as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 5481 F pulseaudio /dev/snd/pcmC0D0p: ubuntu 5481 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 17:23:53 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20HDCTO1WW, Realtek ALC298, Spe
[Touch-packages] [Bug 1977689] Re: Wrong error msg: "state file /var/lib/logrotate/status is world-readable" although it is not
+1 I see the same after upgrading to Ubuntu 22.04. Two problems I think: - it is not really an error since the file is *not* world-readable - if the file was world-readable the message should I think say 'cannot', not 'can' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1977689 Title: Wrong error msg: "state file /var/lib/logrotate/status is world- readable" although it is not Status in logrotate package in Ubuntu: New Bug description: Ubuntu 22.04 logrotate 3.19.0-1ubuntu1.1 Every hour, I receive this wrong message: Subject: Cron >cd / && run-parts --report /etc/cron.hourly /etc/cron.hourly/logrotate: error: state file /var/lib/logrotate/status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... despite: # ls -al /var/lib/logrotate total 40 drwxr-x--- 2 root root 4096 Jun 5 17:17 . drwxr-xr-x 66 root root 4096 Jun 3 20:02 .. -rw-r- 1 root root 31974 Jun 5 17:17 status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1977689/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
Ok, thanks for the fast reply. Hope you have a good day :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in linux-raspi package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+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 1782709] Re: Updating systemd kills network on bionic
I changed my networking setup to use netplan and the problem disappeared. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+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 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
my problem is I think likely better covered by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6) ... Failed to try-restart systemd-networkd.service: Transaction is destructive. See system logs and 'systemctl status systemd-networkd.service' for detail
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
TTFN: To add to (and correct) my earlier comments: after the updating shown there, the machine had to be rebooted manually. Checking /var/log/apt/term.log it appears that the upgrade did complete successfully: Log started: 2021-01-07 13:28:19 (Reading database ... 151099 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libnss-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libpam-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../systemd_237-3ubuntu10.43_i386.deb ... Unpacking systemd (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.43_i386.deb ... Unpacking libsystemd0:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Setting up libsystemd0:i386 (237-3ubuntu10.43) ... Setting up systemd (237-3ubuntu10.43) ... Setting up libnss-systemd:i386 (237-3ubuntu10.43) ... Setting up libpam-systemd:i386 (237-3ubuntu10.43) ... Processing triggers for libc-bin (2.27-3ubuntu1.4) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for dbus (1.12.2-1ubuntu1.2) ... Processing triggers for ureadahead (0.100.0-21) ... Log ended: 2021-01-07 13:29:10 ... this even though the (ssh) interface died at the point where systemd was being set up. The system now runs systemd 237-3ubuntu10.43. But based on past experience I think the same thing will happen the next time there is a version upgrade of systemd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
I have this problem with Ubuntu 18.04 system set up with 'encrypted LVM' (standard Ubuntu recipe as per the alternate installer). Whenever there is systemd upgrade it hangs (whole machine crashes - other logins not possible) and has to be manually rebooted (which is not ideal as the machine is 1500 miles away). Note the installed version of systemd seems to be 237-3ubuntu10.42, obviously I am unable to update it. I have another machine also Ubuntu 18.04 system set up with 'encrypted LVM' which has systemd 237-3ubuntu10.43 and does not have this problem. Latest instance of this problem: # apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 3,414 kB of archives. After this operation, 7,168 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libnss-systemd i386 237-3ubuntu10.43 [111 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libpam-systemd i386 237-3ubuntu10.43 [114 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 systemd i386 237-3ubuntu10.43 [2,964 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libsystemd0 i386 237-3ubuntu10.43 [225 kB] Fetched 3,414 kB in 1s (3,309 kB/s) (Reading database ... 151099 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libnss-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libpam-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../systemd_237-3ubuntu10.43_i386.deb ... Unpacking systemd (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.43_i386.deb ... Unpacking libsystemd0:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Setting up libsystemd0:i386 (237-3ubuntu10.43) ... Setting up systemd (237-3ubuntu10.43) ... [system dies] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upg
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Affected by this also. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1875950] Re: rsyslog log files failing to rotate
VM reinstalled, logs are rotating now. ** Changed in: logrotate (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1875950 Title: rsyslog log files failing to rotate Status in logrotate package in Ubuntu: Invalid Bug description: In focal, /etc/logrotate.conf contains: su root adm logrotate does not rotate files in /var/log: error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Parent directory permissions: drwxrwxr-x 9 root syslog 4096 Apr 29 17:17 log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1875950/+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 1875950] Re: rsyslog log files failing to rotate
My mistake, error does not appear with: sudo logrotate -d /etc/logrotate.conf For some reason my logs are not being rotated though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1875950 Title: rsyslog log files failing to rotate Status in logrotate package in Ubuntu: New Bug description: In focal, /etc/logrotate.conf contains: su root adm logrotate does not rotate files in /var/log: error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Parent directory permissions: drwxrwxr-x 9 root syslog 4096 Apr 29 17:17 log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1875950/+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 1875950] [NEW] rsyslog log files failing to rotate
Public bug reported: In focal, /etc/logrotate.conf contains: su root adm logrotate does not rotate files in /var/log: error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Parent directory permissions: drwxrwxr-x 9 root syslog 4096 Apr 29 17:17 log ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1875950 Title: rsyslog log files failing to rotate Status in logrotate package in Ubuntu: New Bug description: In focal, /etc/logrotate.conf contains: su root adm logrotate does not rotate files in /var/log: error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Parent directory permissions: drwxrwxr-x 9 root syslog 4096 Apr 29 17:17 log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1875950/+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 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
*** This bug is a duplicate of bug 1768610 *** https://bugs.launchpad.net/bugs/1768610 I have witnessed a _related_ issue but it does not appear to be precisely the same problem. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853585 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration Status in nux package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) It is caused by the file /etc/X11/Xsession.d/50_check_unity_support which can be deleted and then this problem goes away. Apparently the problem is that nux-tools is not purged, leaving the above file (also see #1768610). > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+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 1853466] [NEW] I have installed the xserver-xorg-video-intel package but cannot detect monitor
Public bug reported: The monitor U2414H is not detected by Ubuntu, the graphics card displayed in settings is llvmpipe (LLVM 8.0, 256 bits). I believe it should be "Intel Iris Plus Graphics", which is what shows up in Windows Device Manager (my device is set up to dual boot). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 15:03:21 2019 DistUpgraded: SystemError: E:Setting in Stop via TCSAFLUSH for stdin failed! - tcsetattr (5: Input/output error), W:Operation was interrupted before it could finish DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8042, 4.15.0-70-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08b0] InstallationDate: Installed on 2019-11-15 (6 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=4540fdd6-b986-43c5-99ec-e2baa34ca219 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-11-19 (2 days ago) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 21 15:01:07 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1853466 Title: I have installed the xserver-xorg-video-intel package but cannot detect monitor Status in xorg package in Ubuntu: New Bug description: The monitor U2414H is not detected by Ubuntu, the graphics card displayed in settings is llvmpipe (LLVM 8.0, 256 bits). I believe it should be "Intel Iris Plus Graphics", which is what shows up in Windows Device Manager (my device is set up to dual boot). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 15:03:21 2019 DistUpgraded: SystemError: E:Setting in Stop via TCSAFLUSH for stdin failed! - tcsetattr (5: Input/output error), W:Operation was interrupted before it could finish DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8042, 4.15.0-70-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08b0] InstallationDate: Installed on 2019-11-15 (6 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcKer
[Touch-packages] [Bug 1849298] Re: unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config
Not sure I can close the bug. Nevertheless it's confusing to have this
configuration in two places. Maybe deserves a review.
--
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/1849298
Title:
unattended-upgrade is checking o=UbuntuESM,a=eoan-security when
disabled in config
Status in unattended-upgrades package in Ubuntu:
New
Bug description:
My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
// "${distro_id}ESM:${distro_codename}";
// "${distro_id}ESM:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
"${distro_id}:${distro_codename}-proposed";
"${distro_id}:${distro_codename}-backports";
};
Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is
allowed for updates despite not being enabled in config:
2019-10-22 08:10:46,075 INFO Initial blacklist :
2019-10-22 08:10:46,077 INFO Initial whitelist:
2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan,
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed,
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1849298/+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 1849298] Re: unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config
I just realised it's enabled by /etc/apt/apt.conf.d/51ubuntu-advantage-
esm. Closing bug.
--
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/1849298
Title:
unattended-upgrade is checking o=UbuntuESM,a=eoan-security when
disabled in config
Status in unattended-upgrades package in Ubuntu:
New
Bug description:
My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
// "${distro_id}ESM:${distro_codename}";
// "${distro_id}ESM:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
"${distro_id}:${distro_codename}-proposed";
"${distro_id}:${distro_codename}-backports";
};
Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is
allowed for updates despite not being enabled in config:
2019-10-22 08:10:46,075 INFO Initial blacklist :
2019-10-22 08:10:46,077 INFO Initial whitelist:
2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan,
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed,
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1849298/+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 1849298] [NEW] unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config
Public bug reported:
My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
// "${distro_id}ESM:${distro_codename}";
// "${distro_id}ESM:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
"${distro_id}:${distro_codename}-proposed";
"${distro_id}:${distro_codename}-backports";
};
Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is allowed
for updates despite not being enabled in config:
2019-10-22 08:10:46,075 INFO Initial blacklist :
2019-10-22 08:10:46,077 INFO Initial whitelist:
2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan,
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed,
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security
** 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/1849298
Title:
unattended-upgrade is checking o=UbuntuESM,a=eoan-security when
disabled in config
Status in unattended-upgrades package in Ubuntu:
New
Bug description:
My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
// "${distro_id}ESM:${distro_codename}";
// "${distro_id}ESM:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
"${distro_id}:${distro_codename}-proposed";
"${distro_id}:${distro_codename}-backports";
};
Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is
allowed for updates despite not being enabled in config:
2019-10-22 08:10:46,075 INFO Initial blacklist :
2019-10-22 08:10:46,077 INFO Initial whitelist:
2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan,
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed,
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1849298/+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 1802090] Re: update overwrites sshd_config
attached: /var/log/apt/term.log ** Attachment added: "term.log.gz" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+attachment/5210010/+files/term.log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1802090 Title: update overwrites sshd_config Status in openssh package in Ubuntu: Incomplete Bug description: The latest update for Bionic (18.04.1) either overwrote or modified my /etc/ssh/sshd_config with the result that I could no longer access my machine using ssh. A specific Port [x] line was removed and replaced by: #Port 22 This was the only change. It happened as part of an automated process this morning - presumably a security update. Was this behaviour intended?! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1802090] Re: update overwrites sshd_config
The update to 18.04 was a long time ago, the problem occurred this morning... On Wed, 7 Nov 2018 at 13:01, Marc Deslauriers < marc.deslauri...@canonical.com> wrote: > It looks like you upgraded from Ubuntu 16.04 to Ubuntu 18.04. > >From the log file: > > Unpacking openssh-server (1:7.6p1-4) over (1:7.2p2-4ubuntu2.4) ... > > Then the upgrade asked you what to do with the modified conffile, again, > from the log: > > Configuring openssh-server > sshd_config: A new version (/tmp/filerMG8sJ) of configuration file > /etc/ssh/sshd_config is available, but the > version installed currently has been locally modified. > What do you want to do about modified configuration file sshd_config? > install the package maintainer's > version > keep the local version currently installed > show the differences between the versions > show a side-by-side difference between the versions > start a new shell to examine the situation > > # nano /tmp/filerMG8sJ > > Replacing config file /etc/ssh/sshd_config with new version > > At which point you edited the file and instructed the upgrade process to > use the new package version. > > I'm not quite sure what you expect this bug to resolve, the package > seems to be acting as it should. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1802090 > > Title: > update overwrites sshd_config > > Status in openssh package in Ubuntu: > Incomplete > > Bug description: > The latest update for Bionic (18.04.1) either overwrote or modified my > /etc/ssh/sshd_config with the result that I could no longer access my > machine using ssh. > > A specific > Port [x] > line was removed and replaced by: > #Port 22 > > This was the only change. It happened as part of an automated process > this morning - presumably a security update. > > Was this behaviour intended?! > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1802090 Title: update overwrites sshd_config Status in openssh package in Ubuntu: Incomplete Bug description: The latest update for Bionic (18.04.1) either overwrote or modified my /etc/ssh/sshd_config with the result that I could no longer access my machine using ssh. A specific Port [x] line was removed and replaced by: #Port 22 This was the only change. It happened as part of an automated process this morning - presumably a security update. Was this behaviour intended?! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+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 1802090] Re: update overwrites sshd_config
It was an automatic update, file attached ** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+attachment/5209992/+files/apt-term.log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1802090 Title: update overwrites sshd_config Status in openssh package in Ubuntu: Incomplete Bug description: The latest update for Bionic (18.04.1) either overwrote or modified my /etc/ssh/sshd_config with the result that I could no longer access my machine using ssh. A specific Port [x] line was removed and replaced by: #Port 22 This was the only change. It happened as part of an automated process this morning - presumably a security update. Was this behaviour intended?! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+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 1802090] [NEW] update overwrites sshd_config
Public bug reported: The latest update for Bionic (18.04.1) either overwrote or modified my /etc/ssh/sshd_config with the result that I could no longer access my machine using ssh. A specific Port [x] line was removed and replaced by: #Port 22 This was the only change. It happened as part of an automated process this morning - presumably a security update. Was this behaviour intended?! ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1802090 Title: update overwrites sshd_config Status in openssh package in Ubuntu: New Bug description: The latest update for Bionic (18.04.1) either overwrote or modified my /etc/ssh/sshd_config with the result that I could no longer access my machine using ssh. A specific Port [x] line was removed and replaced by: #Port 22 This was the only change. It happened as part of an automated process this morning - presumably a security update. Was this behaviour intended?! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1802090/+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 1786195] Re: broken audio/muffled, no system audio
The bug was not gone when using kernel 4.4 there was also an additional kernel between 4.4 and 4.15 that was available. I tried that as well. same result.no fix. Since then I backed up my system and did a completely fresh install of 18.04LTS and the issue is still not fixed. -- 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/1786195 Title: broken audio/muffled, no system audio Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS pulseaudio: Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages expected sound to return to normal/crisp throughout system and media applications. sound became muffled/distorted throughout all media applications, while other system sounds failed altogether. volume up/down failed. Chime on reboot also distorted. system and application sounds appear normal when used via bluetooth. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: novgorod 1787 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 9 01:40:50 2018 InstallationDate: Installed on 2018-08-01 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00CC.B00.1802021826 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.family: MacBook dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786195/+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 1786195] Re: broken audio/muffled, no system audio
The bug was not gone when using kernel 4.4 there was also an additional kernel between 4.4 and 4.15 that was available. I tried that as well. same result.no fix. Since then I backed up my system and did a completely fresh install of 18.04LTS and the issue is still not fixed. -- 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/1786195 Title: broken audio/muffled, no system audio Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS pulseaudio: Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages expected sound to return to normal/crisp throughout system and media applications. sound became muffled/distorted throughout all media applications, while other system sounds failed altogether. volume up/down failed. Chime on reboot also distorted. system and application sounds appear normal when used via bluetooth. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: novgorod 1787 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 9 01:40:50 2018 InstallationDate: Installed on 2018-08-01 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00CC.B00.1802021826 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.family: MacBook dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786195/+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 1786195] Re: broken audio/muffled, no system audio
"16.04 used kernel 4.4 and you are presently using kernel 4.15" Have been running 18.04 for a week. Until earlier today issue was not present, each day until now however, had been just fine. Is "4.15" the same kernel used at install of "18.04"? -- 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/1786195 Title: broken audio/muffled, no system audio Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS pulseaudio: Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages expected sound to return to normal/crisp throughout system and media applications. sound became muffled/distorted throughout all media applications, while other system sounds failed altogether. volume up/down failed. Chime on reboot also distorted. system and application sounds appear normal when used via bluetooth. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: novgorod 1787 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 9 01:40:50 2018 InstallationDate: Installed on 2018-08-01 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00CC.B00.1802021826 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.family: MacBook dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786195/+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 1786195] Re: broken audio/muffled, no system audio
uname -a Linux novgorod-LinuxBook 4.4.146-0404146-generic #201808061143 SMP Mon Aug 6 15:51:56 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1786195 Title: broken audio/muffled, no system audio Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS pulseaudio: Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages expected sound to return to normal/crisp throughout system and media applications. sound became muffled/distorted throughout all media applications, while other system sounds failed altogether. volume up/down failed. Chime on reboot also distorted. system and application sounds appear normal when used via bluetooth. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: novgorod 1787 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 9 01:40:50 2018 InstallationDate: Installed on 2018-08-01 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00CC.B00.1802021826 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.family: MacBook dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786195/+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 1786195] Re: broken audio/muffled, no system audio
Over-Amplification is set to "OFF" Test Speakers returned no sound from either left or right speaker. Previous version of Ubuntu "16.04 LTS" -- 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/1786195 Title: broken audio/muffled, no system audio Status in pulseaudio package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS pulseaudio: Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages expected sound to return to normal/crisp throughout system and media applications. sound became muffled/distorted throughout all media applications, while other system sounds failed altogether. volume up/down failed. Chime on reboot also distorted. system and application sounds appear normal when used via bluetooth. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: novgorod 1787 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 9 01:40:50 2018 InstallationDate: Installed on 2018-08-01 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00CC.B00.1802021826 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.family: MacBook dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1786195/+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 1786195] [NEW] broken audio/muffled, no system audio
Public bug reported: Ubuntu 18.04.1 LTS pulseaudio: Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages expected sound to return to normal/crisp throughout system and media applications. sound became muffled/distorted throughout all media applications, while other system sounds failed altogether. volume up/down failed. Chime on reboot also distorted. system and application sounds appear normal when used via bluetooth. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: novgorod 1787 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 9 01:40:50 2018 InstallationDate: Installed on 2018-08-01 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00CC.B00.1802021826 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.family: MacBook dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic -- 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/1786195 Title: broken audio/muffled, no system audio Status in pulseaudio package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS pulseaudio: Installed: 1:11.1-1ubuntu7.1 Candidate: 1:11.1-1ubuntu7.1 Version table: *** 1:11.1-1ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages expected sound to return to normal/crisp throughout system and media applications. sound became muffled/distorted throughout all media applications, while other system sounds failed altogether. volume up/down failed. Chime on reboot also distorted. system and application sounds appear normal when used via bluetooth. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: novgorod 1787 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 9 01:40:50 2018 InstallationDate: Installed on 2018-08-01 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/18 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB61.88Z.00CC.B00.1802021826 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C8AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C8AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMB61.88Z.00CC.B00.1802021826:bd02/02/18:svnAppleInc.:pnMacBook6,1:pvr1.0:rvnAppleInc.:rnMac-F22C8AC8:rvr:cvnAppleInc.:ct10:cvrMac-F22C8AC8: dmi.product.family: MacBook dmi.product.name: MacBook6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1786195/+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 1774717] Re: Saying goodbye to search.cpan.org
Here is a relevant thread on debian-perl: https://lists.debian.org /debian-perl/2018/05/msg00046.html In short: yes, but there is no urgency. I don't think a bug on perl in ubuntu is needed to track this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1774717 Title: Saying goodbye to search.cpan.org Status in perl package in Ubuntu: New Bug description: search.cpan.org is being retired and will transparently redirect to the new https://metacpan.org/ replacement site. Are there any plans to update the URLs like FreeBSD did? https://svnweb.freebsd.org/ports?view=revision&revision=470993 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1774717/+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 1683179] Re: Variables set inside files executed with do not visible to script
Hello, I'm one of the perl maintainers in Debian. In Debian we're still finalising the release notes for this issue for our next release; I suspect noone thought about communicating this change for Ubuntu :( A couple of observations that might be helpful to you and others: 1) you can revert this change (if you need to) by commenting out the relevant line in /etc/perl/sitecustomize.pl 2) I recommend that you in any case check for 'do' returning false, so that you at least don't get a silent failure. 3) This change is being made in the upcoming 5.26.0 release but for release timing reasons we have made it early. ** Summary changed: - Variables set inside files executed with do not visible to script + silent failure in 'do' due to '.' being removed from @INC ** Summary changed: - silent failure in 'do' due to '.' being removed from @INC + 'do' no longer loading files from '.' due to '.' being removed from @INC -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1683179 Title: 'do' no longer loading files from '.' due to '.' being removed from @INC Status in perl package in Ubuntu: New Bug description: I just downloaded and compiled stock Perl 5.24.1 without any Ubuntu packages. Then I put this in a file called foo.pl: --cut do 'froodle.conf'; print $froodle, "\n"; --cut and this in froodle.conf: --cut $froodle = 'freedle'; --cut Then I ran "perl foo.pl" with the stock Perl I had just compiled, and saw this: --cut $ perl foo.pl freedle $ --cut However, when I run "perl foo.pl" with the version of Perl included in Zesty, I see this: --cut $ perl foo.pl $ --cut This is a serious, significant difference in behavior between stock Perl and Ubuntu's Perl, and a regression from Yakkety. Using "do EXPR" to get variable settings from configuration files is even documented in the Perl documentation (https://perldoc.perl.org/functions/do.html). You can't just break this. :-/ ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: perl 5.24.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Apr 16 16:11:29 2017 InstallationDate: Installed on 2016-01-16 (456 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: perl UpgradeStatus: Upgraded to zesty on 2017-04-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1683179/+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 1085766] Re: /var/log/upstart/ureadahead.log contains garbage
I have this too with Xenial. Looking at yesterday's syslog: $ sudo grep -c "Ignored relative path" /var/log/syslog.1 19728 and here are the first few lines: $ sudo grep -m30 ureadahead /var/log/syslog.1 Oct 6 08:00:20 dl1 systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup. Oct 6 08:01:02 dl1 systemd[1]: Started Stop ureadahead data collection 45s after completed startup. Oct 6 08:01:47 dl1 systemd[1]: Starting Stop ureadahead data collection... Oct 6 08:01:47 dl1 systemd[1]: Started Stop ureadahead data collection. Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:events/fs/open_exec/enable: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:buffer_size_kb: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:tracing_on: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:binfmt_misc: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:size: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:start: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:dm/uuid: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: message repeated 11 times: [ ureadahead:dm/uuid: Ignored relative path] Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:.: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:1/stat: Ignored relative path Oct 6 08:01:47 dl1 ureadahead[222]: ureadahead:1/cmdline: Ignored relative path -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1085766 Title: /var/log/upstart/ureadahead.log contains garbage Status in linux package in Ubuntu: Fix Released Status in ureadahead package in Ubuntu: Fix Released Bug description: After an upgrade to Raring (as of today) from Quantal I'm seeing tons of these in /var/log/upstart/ureadahead.log: Counted 8 CPUs ureadahead: ��&a��w: Ignored relative path ureadahead: : Ignored relative path ureadahead: �=%���n�T9: Ignored relative path ureadahead: �=%v9T9: Ignored relative path ureadahead: �=%���U�Ek�: Ignored relative path ureadahead: �=%���`�a: Ignored relative path (the boot was wonderfully fast - not sure if that's because ureadahead was working well or if it's because it didn't do anything). Dave ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ureadahead 0.100.0-12build1 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.3-0ubuntu2 Architecture: amd64 Date: Mon Dec 3 02:06:14 2012 InstallationDate: Installed on 2012-07-17 (138 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120717) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: Upgraded to raring on 2012-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085766/+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 1614215] Re: "md5sums differ" message seems to indicate an install problem
Agree with OP on both points, but also note that when I check the two supposedly different files afterwards they are in fact identical except for timestamp: $ sudo diff /var/lib/dpkg/info/apparmor.md5sums /var/lib/apparmor/profiles/.apparmor.md5sums; echo $? 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1614215 Title: "md5sums differ" message seems to indicate an install problem Status in apparmor package in Ubuntu: New Bug description: Upon applying the latest Ubuntu routine-update, I observed these messages: Setting up apparmor (2.10.95-0ubuntu2.2) ... Installing new version of config file /etc/apparmor.d/abstractions/dbus-session-strict ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2 Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Files /var/lib/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ "The reason why I am filing a bug report" is the LAST line. I presume that if md5sums do not agree, something was probably done improperly in preparing this particular software-update blast. However, in-passing, I would also point out line #3, about "start and stop actions no longer supported." That seems to me to be something (of much less importance, obviously) that might have been overlooked. (I've seen =that= message for some time now.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 17 14:22:55 2016 InstallationDate: Installed on 2016-03-02 (168 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: apparmor Syslog: Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is enabled Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is enabled Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is enabled Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614215/+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 1237042] Re: ureadahead source needs "tracing_enabled" changed to "tracing_on" for 12.04.3
I also have this problem with Ubuntu 15.10, same output as Nicolas: $ sudo systemctl status ureadahead ● ureadahead.service - Read required files in advance Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2016-01-30 07:07:07 GMT; 15min ago Process: 233 ExecStart=/sbin/ureadahead (code=exited, status=5) Main PID: 233 (code=exited, status=5) Jan 30 07:07:07 dicer2 ureadahead[233]: ureadahead: Error while tracing: No such file or directory Jan 30 07:07:07 dicer2 ureadahead[233]: Counted 2 CPUs Jan 30 07:08:19 dicer2 systemd[1]: Stopped Read required files in advance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1237042 Title: ureadahead source needs "tracing_enabled" changed to "tracing_on" for 12.04.3 Status in ureadahead package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu 12.04.3 (64-bit), ureadahead was always exiting with status code 5. When manually run as: sudo /sbin/ureadahead --force-trace --debug The output is: Counted 4 CPUs trace: Missing uselib tracing: No such file or directory ureadahead: Error while tracing: No such file or directory The uselib tracing notice is not important. The "error while tracing" notice lead me to compare ureadahead sources between 12.04.3 and 13.04. Note that ureadahead in 13.04 works. I noticed this difference on lines 195 and 232: if (set_value (dfd, "tracing_enabled", vs: if (set_value (dfd, "tracing_on", This change is mentioned in the changelog as: ureadahead (0.100.0-13) raring; urgency=low * src/trace.c: tracing_enabled is deprecated and gone, switch to tracing_on (LP: #1085766). -- Andy Whitcroft Fri, 11 Jan 2013 12:05:17 + I suspect that this issue occurs in 12.04.3 because it is now using the newer raring kernel 3.8.0-31. Previous flavors of 12.04 such as 12.04.2 do not seem to exhibit this ureadahead issue, probably because the kernel is older 3.5.xx. As a proof-of-concept test, I hex edited the 12.04.3 /sbin/ureadahead to change "tracing_enabled" to "tracing_on". Upon reboot, now ureadahead works, generates the /var/lib/ureadahead/pack file, and it does not report status code 5. Another workaround is to use the ureadahead binary from 13.04, but the updated /lib/x86_64-linux-gnu/libext2fs.so.2.4 is also required from 13.04. $ lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 $ apt-cache policy ureadahead ureadahead: Installed: 0.100.0-12 Candidate: 0.100.0-12 Version table: *** 0.100.0-12 0 500 http://mirror.peer1.net/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1237042/+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 613273] Re: run-init: nuking initramfs contents: directory not empty
I have been having this problem (intermittently) with Ubuntu Server 15.04 and now with 15.10 on my Intel NUC5CPYH for the last 3 months (since I bought it in fact). It only seems to happen when rebooting (never from a cold boot), and it doesn't always happen. I've attached an image of the console output. As my machine is normally headless it is particularly frustrating! I use LVM but not for the root/system partition, only for /home. My system/root is at /dev/sda1 and formatted with ext4. I am using latest kernels downloaded from Ubuntu's http://kernel.ubuntu.com/~kernel-ppa/mainline/ (currently 4.2.5) - but as discussed here it doesn't seem to be a kernel issue. ** Attachment added: "Image of the console output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/613273/+attachment/4509728/+files/IMG_20151017_072019871.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/613273 Title: run-init: nuking initramfs contents: directory not empty Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in udev package in Ubuntu: Fix Released Status in initramfs-tools source package in Lucid: Invalid Status in linux source package in Lucid: Invalid Status in udev source package in Lucid: Fix Released Status in initramfs-tools source package in Maverick: Invalid Status in linux source package in Maverick: Invalid Status in udev source package in Maverick: Invalid Status in initramfs-tools source package in Natty: Invalid Status in linux source package in Natty: Invalid Status in udev source package in Natty: Invalid Bug description: In testing alpha-3 build 20100813.2, I found the following kernel oops: [0.473264] Kernel panic - not syncing: Attempted to kill init!^M [0.473277] Pid: 1, comm: run-init Not tainted 2.6.35-14-virtual #19-Ubuntu^M [0.473284] Call Trace:^M [0.473294] [] panic+0x90/0x111^M [0.473303] [] ? __raw_callee_save_xen_irq_enable+0x11/0x26^M [0.473312] [] forget_original_parent+0x33d/0x350^M [0.473318] [] ? put_files_struct+0xc4/0xf0^M [0.473325] [] exit_notify+0x1b/0x190^M [0.473330] [] do_exit+0x1c5/0x3f0^M [0.473336] [] ? __raw_callee_save_xen_irq_disable+0x11/0x1e^M [0.473343] [] sys_exit+0x17/0x20^M [0.473349] [] system_call_fastpath+0x16/0x1b^M This happened only once in my testing so far today (dozens of boots). I'm attaching the console log of failed instance. The instance that reported this bug is same ami/region different instance. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-14-virtual 2.6.35-14.19 Regression: Yes Reproducible: No ProcVersionSignature: User Name 2.6.35-14.19-virtual 2.6.35 Uname: Linux 2.6.35-14-virtual x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory CurrentDmesg: [ 12.900041] eth0: no IPv6 routers present Date: Wed Aug 4 01:19:11 2010 Ec2AMI: ami-09c3bc5b Ec2AMIManifest: ubuntu-images-testing-ap-southeast-1/ubuntu-maverick-daily-amd64-server-20100803.2.manifest.xml Ec2AvailabilityZone: ap-southeast-1b Ec2InstanceType: m1.large Ec2Kernel: aki-11d5aa43 Ec2Ramdisk: unavailable Frequency: Once a week. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcCmdLine: root=LABEL=uec-rootfs ro ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcModules: acpiphp 18752 0 - Live 0xa000 SourcePackage: linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/613273/+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 1130611] Re: Upstart never closes /var/log/upstart/mysql.log
oops, looks like I spoke too soon. The report from dmesg mentioned in my previous comment has gone away on reboot. I believe the cause may have been a fault in my /etc/rc.local file, which may not have been completing. This is fixed now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1130611 Title: Upstart never closes /var/log/upstart/mysql.log Status in upstart package in Ubuntu: New Bug description: I ran "init u" after noticing a lingering FD to a log file that lsof showed as "(deleted)". However because the file handle is never closed, and the log files get logrotate'd it keeps happening, like so: init 1 root 11w REG 252,0 3532 394558 /var/log/upstart/mysql.log.1 (deleted) It's possible this might be fixed by a version update, as I noticed there were closed bugs relating to "leaked" file descriptors? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1130611/+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 1130611] Re: Upstart never closes /var/log/upstart/mysql.log
I confirm this problem in ubuntu 14.04: $ sudo lsof|grep deleted|grep -Ev "/(dev|tmp|run)" init 1 root 10w REG 252,4 778 131190 /var/log/upstart/mysql.log.1 (deleted) An effect (and how I noticed it) is that when I take LVM snapshot of the underlying volume I get warning messages in dmesg: $ dmesg -T ... [Fri Mar 6 06:02:19 2015] bio: create slab at 1 [Fri Mar 6 06:02:19 2015] EXT4-fs (dm-6): 1 orphan inode deleted [Fri Mar 6 06:02:19 2015] EXT4-fs (dm-6): recovery complete ... So the orphan inode in the snapshot (i.e. dm-6) gets deleted but it remains in the underlying volume. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1130611 Title: Upstart never closes /var/log/upstart/mysql.log Status in upstart package in Ubuntu: New Bug description: I ran "init u" after noticing a lingering FD to a log file that lsof showed as "(deleted)". However because the file handle is never closed, and the log files get logrotate'd it keeps happening, like so: init 1 root 11w REG 252,0 3532 394558 /var/log/upstart/mysql.log.1 (deleted) It's possible this might be fixed by a version update, as I noticed there were closed bugs relating to "leaked" file descriptors? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1130611/+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 1388647] Re: DRI_PRIME=1 has no effect in Ubuntu 14.10
Hi Christopher, No backport required by me thanks. Alain Rouet's work-around solves this problem. Thanks, Dominic. -- 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/1388647 Title: DRI_PRIME=1 has no effect in Ubuntu 14.10 Status in xorg package in Ubuntu: Incomplete Bug description: On an Optimus laptop with both GPUs enabled, having run this command so that the Nvidia GPU can be used to offload 3D work from the Intel GPU: ``` xrandr --setprovideroffloadsink nouveau Intel ``` Then running this command: ``` DRI_PRIME=1 glxinfo | grep "OpenGL vendor string" ``` provides the incorrect output: ``` OpenGL vendor string: Intel Open Source Technology Center ``` when it should actually show that the Nouveau driver is in use for the program. This worked previously in Ubuntu 14.04. Apart from only having a 3.16 kernel (instead of 3.17) Ubuntu 14.10 actually supports recent enough versions of the requisite packages necesarry to get DRI 3 offloading support, so perhaps this is part of the problem. Or, more likely, I notice a Nouveau failure after startup, and then again after running xrandr commands, for example: ``` [ 170.912483] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 217.550205] thinkpad_acpi: EC reports that Thermal Table has changed [ 223.857442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.858395] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.860200] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] [ 224.654622] thinkpad_acpi: EC reports that Thermal Table has changed [ 825.172094] thinkpad_acpi: EC reports that Thermal Table has changed [ 831.132156] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.133030] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.134832] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] ``` Perhaps this is just a regression in either the Nouveau or Intel drivers for my hardware. I'm using a Lenovo T430. I can confirm that I'm able to start the laptop without errors when I only enable the Intel GPU or NVidia GPU separately, and only see this error when both GPUs are enabled simultaneously. Extra Info: 1: Description: Ubuntu 14.10 Release: 14.10 2: N/A 3: The text 'nouveau' should have appeared in the output of the command. 4: The text 'Intel' appeared in the output of the command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388647/+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 1388647] Re: DRI_PRIME=1 has no effect in Ubuntu 14.10
Hi Christopher, I can confirm that this issue has been fixed in the current daily build of Ubuntu 15.04. Thanks, Dominic. -- 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/1388647 Title: DRI_PRIME=1 has no effect in Ubuntu 14.10 Status in xorg package in Ubuntu: Incomplete Bug description: On an Optimus laptop with both GPUs enabled, having run this command so that the Nvidia GPU can be used to offload 3D work from the Intel GPU: ``` xrandr --setprovideroffloadsink nouveau Intel ``` Then running this command: ``` DRI_PRIME=1 glxinfo | grep "OpenGL vendor string" ``` provides the incorrect output: ``` OpenGL vendor string: Intel Open Source Technology Center ``` when it should actually show that the Nouveau driver is in use for the program. This worked previously in Ubuntu 14.04. Apart from only having a 3.16 kernel (instead of 3.17) Ubuntu 14.10 actually supports recent enough versions of the requisite packages necesarry to get DRI 3 offloading support, so perhaps this is part of the problem. Or, more likely, I notice a Nouveau failure after startup, and then again after running xrandr commands, for example: ``` [ 170.912483] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 217.550205] thinkpad_acpi: EC reports that Thermal Table has changed [ 223.857442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.858395] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.860200] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] [ 224.654622] thinkpad_acpi: EC reports that Thermal Table has changed [ 825.172094] thinkpad_acpi: EC reports that Thermal Table has changed [ 831.132156] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.133030] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.134832] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] ``` Perhaps this is just a regression in either the Nouveau or Intel drivers for my hardware. I'm using a Lenovo T430. I can confirm that I'm able to start the laptop without errors when I only enable the Intel GPU or NVidia GPU separately, and only see this error when both GPUs are enabled simultaneously. Extra Info: 1: Description: Ubuntu 14.10 Release: 14.10 2: N/A 3: The text 'nouveau' should have appeared in the output of the command. 4: The text 'Intel' appeared in the output of the command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388647/+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 1388647] Re: DRI_PRIME=1 has no effect in Ubuntu 14.10
That's a clever trick, being able to downgrade dependencies like that. Any pointers on how one goes about doing it, since even if I add 'trusty' sources to `/etc/apt/sources.list' then I still only see a single version available to install if I run `apt-show-versions xserver- xorg`? Anyway, great work narrowing it down so quickly! -- 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/1388647 Title: DRI_PRIME=1 has no effect in Ubuntu 14.10 Status in “xorg” package in Ubuntu: Confirmed Bug description: On an Optimus laptop with both GPUs enabled, having run this command so that the Nvidia GPU can be used to offload 3D work from the Intel GPU: ``` xrandr --setprovideroffloadsink nouveau Intel ``` Then running this command: ``` DRI_PRIME=1 glxinfo | grep "OpenGL vendor string" ``` provides the incorrect output: ``` OpenGL vendor string: Intel Open Source Technology Center ``` when it should actually show that the Nouveau driver is in use for the program. This worked previously in Ubuntu 14.04. Apart from only having a 3.16 kernel (instead of 3.17) Ubuntu 14.10 actually supports recent enough versions of the requisite packages necesarry to get DRI 3 offloading support, so perhaps this is part of the problem. Or, more likely, I notice a Nouveau failure after startup, and then again after running xrandr commands, for example: ``` [ 170.912483] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 217.550205] thinkpad_acpi: EC reports that Thermal Table has changed [ 223.857442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.858395] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 223.860200] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] [ 224.654622] thinkpad_acpi: EC reports that Thermal Table has changed [ 825.172094] thinkpad_acpi: EC reports that Thermal Table has changed [ 831.132156] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.133030] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 831.134832] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x002140 [ !ENGINE ] ``` Perhaps this is just a regression in either the Nouveau or Intel drivers for my hardware. I'm using a Lenovo T430. I can confirm that I'm able to start the laptop without errors when I only enable the Intel GPU or NVidia GPU separately, and only see this error when both GPUs are enabled simultaneously. Extra Info: 1: Description: Ubuntu 14.10 Release: 14.10 2: N/A 3: The text 'nouveau' should have appeared in the output of the command. 4: The text 'Intel' appeared in the output of the command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1388647/+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
