[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 22.04.2024 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. In dringenden Fällen wenden Sie sich bitte an Markus Delorenzo: +43-5232-2208-39 md(@)ruetz.at Mit freundlichen Grüßen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 22.04.2024 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. In dringenden Fällen wenden Sie sich bitte an Markus Delorenzo: +43-5232-2208-39 md(@)ruetz.at Mit freundlichen Grüßen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Problem solved (At last!!). Since I am not a Linux/Debian/Ubuntu matter, I can't give detailed reasoning the cause-consequence relationship. But this is what I did after hundreds of tries. 1. Update SOF firmware binaries. Read this: https://askubuntu.com/questions/1421513/22-04-lts-no-sound-intel-sound-card-snd-hda-intel-not-working 2. Edit '/etc/modprobe.d/alsa-base.conf' to add 'options snd-intel-dspcfg dsp_driver=1' Read this: https://thesofproject.github.io/latest/getting_started/intel_debug/introduction.html Reboot and voilà! I would be happy if I see that this solution works for others. Please comment below if you try this. -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 02.01.2024 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. In dringenden Fällen wenden Sie sich bitte an Markus Delorenzo: +43-5232-2208-39 md(@)ruetz.at Mit freundlichen Grüßen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 12.12.2023 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. In dringenden Fällen wenden Sie sich bitte an Markus Delorenzo: +43-5232-2208-39 md(@)ruetz.at Mit freundlichen Grüßen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 12.12.2023 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. In dringenden Fällen wenden Sie sich bitte an Markus Delorenzo: +43-5232-2208-39 md(@)ruetz.at Mit freundlichen Grüßen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 20.11.2023 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. In dringenden Fällen wenden Sie sich bitte an Markus Delorenzo: +43-5232-2208-39 md(@)ruetz.at Mit freundlichen Grüßen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 20.11.2023 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. In dringenden Fällen wenden Sie sich bitte an Markus Delorenzo: +43-5232-2208-39 md(@)ruetz.at Mit freundlichen Grüßen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 30.10.2023 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. Mit freundlichen Grüssen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036358] Abwesenheitsnachricht
Guten Tag! Ich bin am 30.10.2023 wieder im Büro. Ihre Nachricht wird NICHT automatisch weitergeleitet. Mit freundlichen Grüssen Hans-Peter Schmidt -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036427] Re: Upgrade to version 249.11-0ubuntu3.10 breaks 12d1:15c1 Huawei ME906s LTE M.2 Module
this bug affects us too -- 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/2036427 Title: Upgrade to version 249.11-0ubuntu3.10 breaks 12d1:15c1 Huawei ME906s LTE M.2 Module Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu 22.04.3 LTS Release: 22.04 After the latest upgrade our Huawei LTE modem is not working anymore. We can see the modem wie lsusb, but no interfaces gets activated and systemd-networkd-wait-online gets a timeout. The following packages have been upgraded: Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), thermald:amd64 (2.4.9-1ubuntu0.3, 2.4.9-1ubuntu0.4) When we switch back to an older version the modem is working again! Downgrade: systemd-timesyncd:amd64 (249.11-0ubuntu3.10, 249.11-0ubuntu3.7), libpam-systemd:amd64 (249.11-0ubuntu3.10, 249.11-0ubuntu3.7), libsystemd0:amd64 (249.11-0ubuntu3.10, 249.11-0ubuntu3.7), libnss-systemd:amd64 (249.11-0ubuntu3.10, 249.11-0ubuntu3.7), systemd:amd64 (249.11-0ubuntu3.10, 249.11-0ubuntu3.7), systemd-sysv:amd64 (249.11-0ubuntu3.10, 249.11-0ubuntu3.7) So the latest update breaks anything with that modem. The output of lsusb stays the same with both versions: Bus 001 Device 003: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module With old packages "ip link" looks like that: 9: wwan0: mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 2e:c4:ac:0a:11:f2 brd ff:ff:ff:ff:ff:ff With new packages "ip link" does not show any wwan0 or similar interface. Other network interfaces are avaiable. The network interfaces are configured with /etc/network/interfaces: allow-hotplug wwan0 iface wwan0 inet dhcp apn a1.net metric 100 We use modemmanager to connect: /usr/bin/mmcli --modem 0 --simple-connect="apn=a1.net" "mmcli -L" can't find any modems on a upgraded system. With the previous version we see the Huawei modem: /org/freedesktop/ModemManager1/Modem/0 [Huawei Technologies Co., Ltd.] HUAWEI Mobile V7R11 We have a lot of systems with Huawei LTE modems and that's a serious problem for us! Do you need more information to debug that problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Thanks all for your contributions. In my case, the only available kernels in grub are 5.19.0-35-generic and 5.19.0-38-generic. Booting with both options have the same result: HDMI Audio is missing. I've restarted the computer for weeks without any change. Is there a safe way to install a previous version without crashing the whole system. Shall I expect a fix in the future? Is there anyone accountable for delivering this fix? Apologies if my last two questions are naive. -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007913] [NEW] HDMI Output sound has disappeared after Ubuntu update
Public bug reported: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 ** 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: New Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1882071] [NEW] service ntp restart fails with error: unable to bind to wildcard address
Public bug reported: Description:Ubuntu 16.04.6 LTS Release:16.04 Package: ntp Version: 1:4.2.8p4+dfsg-3ubuntu5.10 Restarting the ntp daemon ntpd after a change in the configuration file /etc/ntp.conf via the shell command % sudo service ntp restart fails in a small fraction of cases (about 2-3%), logging the error: unable to bind to wildcard address :: - another process may be running - EXITING and leaving the system without a running ntpd process. Expected behaviour: ntpd process running with new configuration Actual behaviour: no ntpd process running Additional information: Syslog shows systemd launching the "start" action before the old daemon has exited. Consequently, the new ntpd process races the old one for the UDP socket to listen on. Example log excerpt: May 25 06:31:12 capetown systemd[1]: Stopping LSB: Start NTP daemon... May 25 06:31:12 capetown ntp[28437]: * Stopping NTP server ntpd May 25 06:31:12 capetown ntp[28437]:...done. May 25 06:31:12 capetown systemd[1]: Stopped LSB: Start NTP daemon. May 25 06:31:12 capetown systemd[1]: Starting LSB: Start NTP daemon... May 25 06:31:12 capetown ntp[28449]: * Starting NTP server ntpd May 25 06:31:12 capetown ntpd[28457]: ntpd 4.2.8p4@1.3265-o Tue Jan 7 15:08:23 UTC 2020 (1): Starting May 25 06:31:12 capetown ntpd[28457]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 113:119 May 25 06:31:12 capetown ntp[28449]:...done. May 25 06:31:12 capetown systemd[1]: Started LSB: Start NTP daemon. May 25 06:31:12 capetown ntpd[28460]: proto: precision = 0.105 usec (-23) May 25 06:31:12 capetown ntpd[2749]: 41.76.128.222 local addr 192.168.0.42 -> May 25 06:31:12 capetown ntpd[28460]: MS-SNTP signd operations currently block ntpd degrading service to all clients. May 25 06:31:12 capetown ntpd[28460]: restrict 0.0.0.0: KOD does nothing without LIMITED. May 25 06:31:12 capetown ntpd[28460]: restrict ::: KOD does nothing without LIMITED. May 25 06:31:12 capetown ntpd[28460]: unable to bind to wildcard address :: - another process may be running - EXITING Running the "service ntp restart" command a second time successfully starts the ntpd daemon again. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1882071 Title: service ntp restart fails with error: unable to bind to wildcard address Status in ntp package in Ubuntu: New Bug description: Description:Ubuntu 16.04.6 LTS Release:16.04 Package: ntp Version: 1:4.2.8p4+dfsg-3ubuntu5.10 Restarting the ntp daemon ntpd after a change in the configuration file /etc/ntp.conf via the shell command % sudo service ntp restart fails in a small fraction of cases (about 2-3%), logging the error: unable to bind to wildcard address :: - another process may be running - EXITING and leaving the system without a running ntpd process. Expected behaviour: ntpd process running with new configuration Actual behaviour: no ntpd process running Additional information: Syslog shows systemd launching the "start" action before the old daemon has exited. Consequently, the new ntpd process races the old one for the UDP socket to listen on. Example log excerpt: May 25 06:31:12 capetown systemd[1]: Stopping LSB: Start NTP daemon... May 25 06:31:12 capetown ntp[28437]: * Stopping NTP server ntpd May 25 06:31:12 capetown ntp[28437]:...done. May 25 06:31:12 capetown systemd[1]: Stopped LSB: Start NTP daemon. May 25 06:31:12 capetown systemd[1]: Starting LSB: Start NTP daemon... May 25 06:31:12 capetown ntp[28449]: * Starting NTP server ntpd May 25 06:31:12 capetown ntpd[28457]: ntpd 4.2.8p4@1.3265-o Tue Jan 7 15:08:23 UTC 2020 (1): Starting May 25 06:31:12 capetown ntpd[28457]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 113:119 May 25 06:31:12 capetown ntp[28449]:...done. May 25 06:31:12 capetown systemd[1]: Started LSB: Start NTP daemon. May 25 06:31:12 capetown ntpd[28460]: proto: precision = 0.105 usec (-23) May 25 06:31:12 capetown ntpd[2749]: 41.76.128.222 local addr 192.168.0.42 -> May 25 06:31:12 capetown ntpd[28460]: MS-SNTP signd operations currently block ntpd degrading service to all clients. May 25 06:31:12 capetown ntpd[28460]: restrict 0.0.0.0: KOD does nothing without LIMITED. May 25 06:31:12 capetown ntpd[28460]: restrict ::: KOD does nothing without LIMITED. May 25 06:31:12 capetown ntpd[28460]: unable to bind to wildcard address :: - another process may be running - EXITING Running the "service ntp restart" command a second time successfully starts the ntpd daemon again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1882071/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
I had the same problem with 237-3ubuntu10.28 AND 237-3ubuntu10.26.
237-3ubuntu10.25 was the solution.
--
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/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
New
Status in systemd package in Ubuntu:
New
Bug description:
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840221] [NEW] libcurl built without libssh2/sftp/scp support <= 18.04
Public bug reported: Recently I found that in distributions <=18.04 libcurl is built without libssh2 and therefore does not support the sftp/scp protocols. I am not sure if this is a bug, but maybe this should be added per default as its the case on 19.10 for example. ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: curl libcurl libssh2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1840221 Title: libcurl built without libssh2/sftp/scp support <= 18.04 Status in curl package in Ubuntu: New Bug description: Recently I found that in distributions <=18.04 libcurl is built without libssh2 and therefore does not support the sftp/scp protocols. I am not sure if this is a bug, but maybe this should be added per default as its the case on 19.10 for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1840221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1331856] Re: apparmor-utils don't work when defining a variable on
Still exists in Ubuntu Bionic Beaver (18.04).
apparmor-utils 2.12-4ubuntu5.1 amd64
# aa-logprof
ERROR: Values added to a non-existing variable @{HOMEDIRS}: /srv/ in
tunables/home.d/ubuntu
--
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/1331856
Title:
apparmor-utils don't work when defining a variable on
Status in AppArmor:
Triaged
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
When a variable is set in tunables/home.d/ the apparmor-utils programs
don't work and return this error messages:
root@ws24:~# aa-logprof
Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in
apparmor.loadincludes()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 4643, in
loadincludes
load_include(fi)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 4520, in
load_include
incdata = parse_profile_data(data, incfile, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2839, in
parse_profile_data
store_list_var(profile_data[profile]['lvar'], list_var, value,
var_operation)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3279, in
store_list_var
raise AppArmorException(_('Values added to a non-existing variable: %s')
% list_var)
apparmor.common.AppArmorException: 'Values added to a non-existing variable:
@{HOMEDIRS}'
root@ws24:~#
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1331856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Easy workaround which does not require another apt-setup.udeb: d-i preseed/late_commandstring \ in-target wget -q -O /etc/apt/trusted.gpg.d/bla.asc http://bla.de/bla.asc ; \ in-target sed -i '/keyword to uncomment specific line in file/s/^# *//' /etc/apt/sources.list ; \ in-target apt-get update ; \ in-target apt-get -y install packages to install ; -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
I guess every sysadmin installing an agent-based configuration management system via di will experience this problem, too. Funny how there was no progress on this in half a year. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380976] Re: Limiting queue disk space does not work, upgrade needed
I confirmed this bug as it still affects 7.4.4-1ubuntu2.7 from trusty- updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1380976 Title: Limiting queue disk space does not work, upgrade needed Status in rsyslog package in Ubuntu: Confirmed Bug description: # lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 # apt-cache policy rsyslog rsyslog: Installed: 7.4.4-1ubuntu2.3 Candidate: 7.4.4-1ubuntu2.3 Version table: [...] When rsyslog is run with a config to save/cache log to disk, e.g when the host that it is forwarding log to is not responding, it fails to respect the maxdiskspace parameter. This is a known bug and 7.4.7 of v7-stable has been released to fix this, see http://www.rsyslog.com/changelog-for-7-4-7-v7-stable/ Config for testing: global( workDirectory="/tmp" ) module(load="imudp") module(load="omrelp") input(type="imudp" port="514" ) action(type="omrelp" target="localhost" port="2514" action.resumeRetryCount="-1" queue.saveonshutdown="on" queue.type="LinkedList" queue.filename="omrelp" queue.maxfilesize="100M" queue.maxdiskspace="1M" queue.checkpointinterval="100" queue.highwatermark="10" ) Then just log more than 1MB of messages to UDP to see that it doesn't stop at 1MB but just continues forever. Please upgrade the package to 7.4.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1380976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673717] Re: rsyslog GnuTLS error -50
Test case Step 1: Create a rsyslog-config using gtls: /etc/rsyslog.d/10-tlstest.conf Step 2: To generate the needed ca-, key-, cert-files, follow the guide at http://www.rsyslog.com/doc/v8-stable/tutorials/tls.html#certificates Step 3: Setup a client, which relays logs to the server that was just set up Step 4: Check the rsyslog-log for the errors mentioned in the initial post. ** Attachment added: "10-tlstest.conf" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+attachment/4973253/+files/10-tlstest.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1673717 Title: rsyslog GnuTLS error -50 Status in rsyslog package in Ubuntu: Confirmed Status in rsyslog package in Debian: New Bug description: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708693] [NEW] package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installiere
Public bug reported: gir1.2-webkit2-4.0:amd64 (2.16.6-0ubuntu0.16.04.1) wird eingerichtet ... imagemagick-6.q16 (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ... imagemagick (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ... libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ... linux-libc-dev:amd64 (4.4.0-89.112) wird eingerichtet ... unattended-upgrades (0.90ubuntu0.7) wird eingerichtet ... Trigger für libc-bin (2.23-0ubuntu9) werden verarbeitet ... Trigger für shim-signed (1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) werden verarbeitet ... No DKMS packages installed: not changing Secure Boot validation state. Fehler traten auf beim Bearbeiten von: isc-dhcp-client E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu12.7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 4 18:49:02 2017 DhclientLeases: ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2017-05-31 (64 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed root=UUID=507a1f26-305d-4a62-b708-6ad478301961 ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1708693 Title: package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in isc-dhcp package in Ubuntu: New Bug description: gir1.2-webkit2-4.0:amd64 (2.16.6-0ubuntu0.16.04.1) wird eingerichtet ... imagemagick-6.q16 (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ... imagemagick (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ... libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ... linux-libc-dev:amd64 (4.4.0-89.112) wird eingerichtet ... unattended-upgrades (0.90ubuntu0.7) wird eingerichtet ... Trigger für libc-bin (2.23-0ubuntu9) werden verarbeitet ... Trigger für shim-signed (1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) werden verarbeitet ... No DKMS packages installed: not changing Secure Boot validation state. Fehler traten auf beim Bearbeiten von: isc-dhcp-client E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu12.7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 4 18:49:02 2017 DhclientLeases: ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2017-05-31 (64 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed root=UUID=507a1f26-305d-4a62-b708-6ad478301961 ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1708693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 919200] Re: Doesn't know system default layout/variant
*** This bug is a duplicate of bug 1051288 *** https://bugs.launchpad.net/bugs/1051288 ** This bug has been marked a duplicate of bug 1051288 LightDM assumes there's only ONE system default layout -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/919200 Title: Doesn't know system default layout/variant Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: lightdm_get_layout does not return the correct system default keyboard layout/variant. For that, pitti says we need to access xkl_config->layouts[0]/xkl_config->variants[0]. Currently, we just grab the first layout returned from xkl_config_registry_foreach_layout, which only returns the available layouts, not the configured layouts. So "us" will always be first there. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/919200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Well, thanks a lot! I do not get it working, but i dont know, what i am doing wrong. I followed your description, but still no sound. Audiocard seems to be installed: cat /proc/asound/cards 0 [Audio ]: HdmiLpeAudio - Intel HDMI/DP LPE Audio Intel HDMI/DP LPE Audio 1 [chtcx2072x ]: chtcx2072x - chtcx2072x chtcx2072x But i do not getting any sound, neither from the speakers, or from headphones. Alsamixer did not help, i cannot change the volume from the headphone. I am using lubuntu 16.04 2. Any idea, what i can do? -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666256] Re: Mouse Pointer flicking and blocked after locked screen with two displays
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1666256 Title: Mouse Pointer flicking and blocked after locked screen with two displays Status in light-locker package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-intel-hwe-16.04 package in Ubuntu: New Bug description: After upgrading to the HWE (Xubuntu 16.04.2) I am experiencing sometimes the following bug: When the screen is locked, I wake the displays up. The mouse pointer is flicking and cannot be moved. The keyboard is not responsive as well regarding the light locker. I can change to another terminal (via CTRL+ALT+F1) and quit the session. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: light-locker 1.7.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 20 16:51:54 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-10 (893 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: light-locker UpgradeStatus: Upgraded to xenial on 2016-10-10 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1666256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Sorry, I mean in comment #20! -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I can confirm that using the workaround in #6 makes the VPN operable again. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Here is my output for @piti: Positive Trust Anchors: . IN DS19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa corp home internal intranet lan local private test Using system hostname 'Thinkpad-T440s'. New scope on link *, protocol dns, family * Found new link 3/wlan0 Found new link 2/eth0 Found new link 1/lo New scope on link eth0, protocol llmnr, family AF_INET6 Excercising transaction 8616 for on scope llmnr on eth0/AF_INET6. Delaying llmnr transaction for 4242us. New scope on link eth0, protocol llmnr, family AF_INET Excercising transaction 28149 for on scope llmnr on eth0/AF_INET. Delaying llmnr transaction for 51982us. Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 error=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.128 object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName cookie=2 reply_cookie=0 error=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.128 object=n/a interface=n/a member=n/a cookie=4 reply_cookie=2 error=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=3 reply_cookie=0 error=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.128 object=n/a interface=n/a member=n/a cookie=5 reply_cookie=3 error=n/a Switching to system DNS server 127.0.1.1. Got message type=signal sender=org.freedesktop.DBus destination=:1.128 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 error=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.128 object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=3 reply_cookie=0 error=n/a Timeout reached on transaction 8616. Retrying transaction 8616. Excercising transaction 8616 for on scope llmnr on eth0/AF_INET6. Sending query packet with id 8616 on interface 2/AF_INET6. Timeout reached on transaction 28149. Retrying transaction 28149. Excercising transaction 28149 for on scope llmnr on eth0/AF_INET. Sending query packet with id 28149 on interface 2/AF_INET. Got LLMNR query packet for id 8616 Sending response packet with id 8616 on interface 2/AF_INET6. Got LLMNR query packet for id 28149 Sending response packet with id 28149 on interface 2/AF_INET. Got LLMNR reply packet for id 8616 Processing incoming packet on transaction 8616. Got LLMNR reply packet for id 28149 Processing incoming packet on transaction 28149. Timeout reached on transaction 8616. Retrying transaction 8616. Excercising transaction 8616 for on scope llmnr on eth0/AF_INET6. Sending query packet with id 8616 on interface 2/AF_INET6. Timeout reached on transaction 28149. Retrying transaction 28149. Excercising transaction 28149 for on scope llmnr on eth0/AF_INET. Sending query packet with id 28149 on interface 2/AF_INET. Got LLMNR query packet for id 8616 Sending response packet with id 8616 on interface 2/AF_INET6. Got LLMNR query packet for id 28149 Sending response packet with id 28149 on interface 2/AF_INET. Got LLMNR reply packet for id 8616 Processing incoming packet on transaction 8616. Got LLMNR reply packet for id 28149 Processing incoming packet on transaction 28149. Timeout reached on transaction 8616. Retrying transaction 8616. Excercising transaction 8616 for on scope llmnr on eth0/AF_INET6. Sending query packet with id 8616 on interface 2/AF_INET6. Timeout reached on transaction 28149. Retrying transaction 28149. Excercising transaction 28149 for on scope llmnr on eth0/AF_INET. Sending query packet with id 28149 on interface 2/AF_INET. Got LLMNR query packet for id 8616 Sending response packet with id 8616 on interface 2/AF_INET6. Got LLMNR query packet for id 28149 Sending response packet with id 28149 on interface 2/AF_INET. Got LLMNR reply packet for id 8616 Processing incoming packet on transaction 8616. Got LLMNR reply packet for id 28149 Processing incoming packet on transaction 28149. Timeout reached on transaction 8616. Retrying transaction 8616. Transaction 8616 for on scope llmnr on eth0/AF_INET6 now complete with from none (unsigned). Record Thinkpad-T440s. IN fe80::95eb:8e44:c908:cafc successfully probed. Freeing transaction 8616. Timeout reached on
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Same problem with VPNC and 16.04.2. Worked before on fresh upgrade to 16.04.0. At the moment I am not able to work remote. Please fix this! ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi
This is so interesting, and such an old thread that keeps on going. I have the exact *opposite* of this problem. On Windows 10, this: >>"For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time."<< is *exactly* what happens. The file buffers/downloads, the sound begins playback, and the Bluetooth signal interferes with its own download. Turning off the Bluetooth speakers instantly returns Wlan activity. And more, amazingly, it works perfectly fine on Linux (Mint, Kali tested so far). I have to conclude at this point that this is a software problem. Obviously I'm not looking for Win10 assistance here, but I thought it was too interesting a thread not to post in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650961] Re: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106
Same problem. Still on 16.04. Recently installed system76 drivers, didn't notice this error. I can give you the packages last updated, 1/16/2017. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1650961 Title: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 Status in apport package in Ubuntu: New Bug description: caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux caravena@caravena-530U3C-530U4C:~$ [12375:12409:1218/134054:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 Se creó una nueva ventana en la sesión existente del navegador. [7185:7220:1218/142107:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/142111:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7318:1218/142115:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/142117:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -105 [7185:7220:1218/143613:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/144540:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/145430:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106 [7185:7318:1218/162533:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates [7185:7220:1218/162540:ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -21 [7185:7318:1218/162540:ERROR:get_updates_processor.cc(242)] PostClientToServerMessage() failed during GetUpdates caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux caravena@caravena-530U3C-530U4C:~$ [18327:18362:1218/165822:ERROR:nss_util.cc(809)] After loading Root Certs, loaded==false: NSS error code: -8018 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 18 17:32:53 2016 InstallationDate: Installed on 2015-07-26 (511 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to zesty on 2016-10-29 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1650961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644666] Re: Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
Linux Mint 18 on NVIDIA C61 with Linux 4.4.0-21 is affected as well. I did not experience the login loop but Cinnamon started in fall back mode. Removing nvidia-304.132-0ubuntu0.16.04.2 and installing nvidia-304.131-0ubuntu3 worked for me. -- 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/1644666 Title: Xorg crash 1: nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.1 (Automatic Upgrade from 14.04) My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): Nvidia C61 [GeForce 7025 / nForce 630a] --- In the Past: => System and Apps worked well with Auto-Login enabled. To eliminate Hardware-Errors: > Memtest > Boot with Windows-XP => No Problems Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart) -- 1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop 2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen --- I don't know in which Category to sort the Bugs So this one is for the (Nr.1) Login-Loop (from tty-Terminal) (I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with Stripes-Screen) First Problem startet on 2016-Nov-05: => Login-Loop --- I later found out, that one Day before, the following Auto-Updates had been installed: --- libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2) nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2) nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2) libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2) --- After Shutdown, the next Computer-Start was stuck in a => Login-Loop: After entering the correct Password, the Screen turns black for a Second, then the Login-Form shows up again. --- I tried a few things, that did not help, like: > CTRL+F2 => Terminal > sudo .. > apt autoclean > apt clean > apt autoremove > apt update > apt upgrade > apt dist-upgrade > shutdown -r now > mv .Xauthority .Xauthority.alt > shutdown -r now > service lightdm restart > shutdown -r now > apt purge lightdm > apt install lightdm > shutdown -r now > .. Boot into different Linux-Kernel, .. (upstart), > .. Boot into Recovery-Mode > .. > Repair > .. > .. I also tried to install other nvidia-drivers, which, sadly, i did not document. => Did NOT work --- Only Thing that helped was: --- > sudo apt purge nvidia-* > sudo shutdown -r now => (nouveau-Driver was automatically installed) => Auto-Login to Desktop But then there was a second Problem: When > starting Thunderbird, mostly at once, sometimes after > opening some E-Mail-Windows, another Error occurred: => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => Total (Freeze-)Crash -- Later, even with DISabled Hardware-Acceleration, starting both, Firefox and Thunderbird led to the System-Crash. (Sometimes, the System with nouveau booted and auto-logined into a Black Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could be rebooted normally.) --- > CTRL+ALT+F2 => did NOT work > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work > ping to IP => unreachable --- After cold Reboot, i tried again to switch back from nouveau- to nvidia-Drivers > Additional Drivers > Nvidia-304.132 => Login-Loop --- > sudo apt purge nvidia-* > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau => Auto-Login > Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen --- > .. removed and tried to install the old driver (I probably did wrong): > sudo apt purge nvidia-* > sudo add-apt-repository ppa:graphics-drivers/ppa > sudo apt update > sudo apt install nvidia-current=304.131-0ubuntu3 => Login-Loop --- > sudo apt purge nvidia-* > Additional Drivers > nouveau > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 4.4.0-47-generic" (NO Option=SYSTEMD?) => Auto-Login > Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen What seemed to help was: > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 4.4.0-47-generic (upstart)" (UPSTART!) => Auto-Login > Firefox / Thunderbird => seem to work stable! => After half an Hour of testing: > open Firefox (Hardware-Acceleration disabled) => System-(Freeze)-Crash with Stripes-Screen - Because this is far more stable: Changed Standard-Boot in Grub-2 to UpStart instead of SystemD --- > Terminal > sudo apt install upstart-sysv su sudo shutdown -r now --- For Roll-Back:
[Touch-packages] [Bug 1576949] [NEW] package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück
Public bug reported: I tried to start an upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.31-4ubuntu4 Uname: Linux 3.4.108 armv7l ApportVersion: 2.20.1-0ubuntu2 Architecture: armhf Date: Fri Apr 29 23:02:34 2016 ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1576949 Title: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück Status in avahi package in Ubuntu: New Bug description: I tried to start an upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.31-4ubuntu4 Uname: Linux 3.4.108 armv7l ApportVersion: 2.20.1-0ubuntu2 Architecture: armhf Date: Fri Apr 29 23:02:34 2016 ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.31-4ubuntu4 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1576949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576762] [NEW] package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: just updating ubuntu mate, then this erroe occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 Uname: Linux 3.4.108 armv7l ApportVersion: 2.19.1-0ubuntu5 Architecture: armhf Date: Fri Apr 29 17:14:59 2016 DuplicateSignature: package:initramfs-tools:0.122ubuntu8:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2016-02-21T22:22:01 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1576762 Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: just updating ubuntu mate, then this erroe occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 Uname: Linux 3.4.108 armv7l ApportVersion: 2.19.1-0ubuntu5 Architecture: armhf Date: Fri Apr 29 17:14:59 2016 DuplicateSignature: package:initramfs-tools:0.122ubuntu8:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2016-02-21T22:22:01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1576762/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1524182] [NEW] package rsyslog-mysql 5.8.6-1ubuntu8.9 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: When I installed MySQL I use ')' in the password. The symbol does on work when the password is on the command line to start MySQL(I do this since I am the only one who uses this computer). I forgot that I did not need to put the password on a command line ans started to uninstall MySQL. That is when I got this message. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: rsyslog-mysql 5.8.6-1ubuntu8.9 ProcVersionSignature: Ubuntu 3.13.0-71.114~precise1-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic i686 ApportVersion: 2.0.1-0ubuntu17.13 Architecture: i386 Date: Tue Dec 8 23:00:05 2015 DuplicateSignature: package:rsyslog-mysql:5.8.6-1ubuntu8.9:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) MarkForUpload: True SourcePackage: rsyslog Title: package rsyslog-mysql 5.8.6-1ubuntu8.9 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check precise -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1524182 Title: package rsyslog-mysql 5.8.6-1ubuntu8.9 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in rsyslog package in Ubuntu: New Bug description: When I installed MySQL I use ')' in the password. The symbol does on work when the password is on the command line to start MySQL(I do this since I am the only one who uses this computer). I forgot that I did not need to put the password on a command line ans started to uninstall MySQL. That is when I got this message. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: rsyslog-mysql 5.8.6-1ubuntu8.9 ProcVersionSignature: Ubuntu 3.13.0-71.114~precise1-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic i686 ApportVersion: 2.0.1-0ubuntu17.13 Architecture: i386 Date: Tue Dec 8 23:00:05 2015 DuplicateSignature: package:rsyslog-mysql:5.8.6-1ubuntu8.9:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) MarkForUpload: True SourcePackage: rsyslog Title: package rsyslog-mysql 5.8.6-1ubuntu8.9 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1524182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381042] Re: No networking after suspend and resume
The bug is still present in Wily on my installation. In addition, the network connections widget continues to draw the "refresh" animation, producing a cpu load of 100% on one core. If I don't reboot in this situation, Plasma crashes eventually. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1381042 Title: No networking after suspend and resume Status in network-manager package in Ubuntu: Confirmed Bug description: I started having problems with suspend and resume after upgrading to kernel 3.13.0-37. Resume takes a long time, suspend sometimes takes me to the log in screen and I have no networking after resuming (I need to restart Network Manager). I am running Ubuntu 14.04 (64 bit) on a DELL XPS 13 (full HD, Intel GPU) notebook. Everything works fine with kernel 3.13.0-36. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Tue Oct 14 09:19:50 2014 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-04-27 (170 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.25.1 dev wlan0 proto static 192.168.25.0/24 dev wlan0 proto kernel scope link src 192.168.25.2 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CC:07:AB:0D:ED:A4 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/3 9C:65:B0:BF:D2:55 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/2 30:19:66:26:90:06 bluetooth disconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1381042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508826] Re: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all when headset plugged in
Same thinkpad here. I figured out in the meantime that the headphones must not be plugged in on boot; otherwise they won't work until the next complete power down. If I boot without headphones, however, it works fine. If you have Alsa 1.0.29 already, you could try the patches from here https://bugzilla.kernel.org/show_bug.cgi?id=99721 (comment 8/9). -- 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/1508826 Title: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all when headset plugged in Status in alsa-driver package in Ubuntu: Incomplete Bug description: Sounds works fine through the internal speakers, but once I plug a headset or headphones (I tried two things, in case one was broken) in to the audio out, I get nothing. Looking in alsamixer, plugging the headset in mutes the 'Speaker' output and unmutes the 'Headphone' output, and restores the Master volume to its previous headset-in value. Unplugging the headset does the opposite (mutes 'Headphone'; unmutes 'Speaker'), as I would expect. This was working on vivid, so a definite regression, I think. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 5155 F pulseaudio /dev/snd/controlC0: daniel 5155 F pulseaudio Date: Thu Oct 22 09:37:39 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-04 (412 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to wily on 2015-10-21 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET70WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1508826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508826] Re: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all when headset plugged in
Same problem here after update to Wily. Fixed by following this guide: http://unix.stackexchange.com/questions/218108/no-output-from- headphones-jack-occasionally-although-system-displays-output and adding "options snd-hda-intel model=tpt440-dock" to /etc/modprobe.d /alsa-base.conf. Version info: Kernel 4.2.0-16-generic #19-Ubuntu SMP and alsa-base 1.0.25+dfsg-0ubuntu5. This is not related to a docking station, and I have a TP440p. Reported this to the original kernel bug. -- 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/1508826 Title: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all when headset plugged in Status in alsa-driver package in Ubuntu: Incomplete Bug description: Sounds works fine through the internal speakers, but once I plug a headset or headphones (I tried two things, in case one was broken) in to the audio out, I get nothing. Looking in alsamixer, plugging the headset in mutes the 'Speaker' output and unmutes the 'Headphone' output, and restores the Master volume to its previous headset-in value. Unplugging the headset does the opposite (mutes 'Headphone'; unmutes 'Speaker'), as I would expect. This was working on vivid, so a definite regression, I think. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 5155 F pulseaudio /dev/snd/controlC0: daniel 5155 F pulseaudio Date: Thu Oct 22 09:37:39 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-04 (412 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [20ANCTO1WW, Realtek ALC3232, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to wily on 2015-10-21 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET70WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1508826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1499701] [NEW] package bluez 5.34-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Error is reported spontaneously. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.34-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Fri Sep 25 11:13:43 2015 DuplicateSignature: package:bluez:5.34-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-30 (329 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard Compaq 615 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=5c188f95-bbdb-49b7-bb3a-be84c71897a9 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.9.10ubuntu7 SourcePackage: bluez Title: package bluez 5.34-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68GVV Ver. F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 308C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 27.07 dmi.chassis.asset.tag: CNU93824ND dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68GVVVer.F.06:bd08/03/2009:svnHewlett-Packard:pnCompaq615:pvrF.06:rvnHewlett-Packard:rn308C:rvrKBCVersion27.07:cvnHewlett-Packard:ct10:cvr: dmi.product.name: Compaq 615 dmi.product.version: F.06 dmi.sys.vendor: Hewlett-Packard hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1499701 Title: package bluez 5.34-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: Error is reported spontaneously. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.34-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Fri Sep 25 11:13:43 2015 DuplicateSignature: package:bluez:5.34-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-30 (329 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard Compaq 615 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=5c188f95-bbdb-49b7-bb3a-be84c71897a9 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.9.10ubuntu7 SourcePackage: bluez Title: package bluez 5.34-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68GVV Ver. F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 308C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 27.07 dmi.chassis.asset.tag: CNU93824ND dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68GVVVer.F.06:bd08/03/2009:svnHewlett-Packard:pnCompaq615:pvrF.06:rvnHewlett-Packard:rn308C:rvrKBCVersion27.07:cvnHewlett-Packard:ct10:cvr: dmi.product.name: Compaq 615 dmi.product.version: F.06 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1499701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473674] Re: apt fails a test from the testsuite on ppc64el when built with gcc-5 and -O3
Spent some time trying to reproduce this upstream. From the information given, I am unable to do so. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1473674 Title: apt fails a test from the testsuite on ppc64el when built with gcc-5 and -O3 Status in gcc: Unknown Status in apt package in Ubuntu: Confirmed Status in gcc-5 package in Ubuntu: New Status in apt source package in Wily: Confirmed Status in gcc-5 source package in Wily: New Bug description: to reproduce: - wily chroot - PPA https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016/ (this holds gcc-5 as the default, branch 20150711). - dpkg-buildpackage -B note that explicitly using the gcc-5/g++-5 from wily doesn't show the test failure. the only difference in the configuration is that the one in wily is built using the old libstdc++ ABI and the one in the PPA with the dual ABI defaulting to new/c++11. building with -O2 instead of -O3 works around the issue. [ RUN ] CDROMTest.FindPackages /scratch/doko/tmp/apt-1.0.9.10ubuntu1/test/libapt/cdromfindpackages_test.cc:95: Failure Value of: InfoDir Actual: Expected: path + /.disk/ Which is: /tmp/apt-tests-findpackage.gpopMw/.disk/ [ FAILED ] CDROMTest.FindPackages (4 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1473674/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473674] Re: apt fails a test from the testsuite on ppc64el when built with gcc-5 and -O3
As a guess, is FindPackages being inlined? If so, and if the parameter passed in as InfoDir isn't subsequently used, the compiler would be within its rights to remove the assignment to InfoDir. May want to check callers of FindPackages for this possibility. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1473674 Title: apt fails a test from the testsuite on ppc64el when built with gcc-5 and -O3 Status in gcc: Unknown Status in apt package in Ubuntu: Confirmed Status in gcc-5 package in Ubuntu: New Status in apt source package in Wily: Confirmed Status in gcc-5 source package in Wily: New Bug description: to reproduce: - wily chroot - PPA https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016/ (this holds gcc-5 as the default, branch 20150711). - dpkg-buildpackage -B note that explicitly using the gcc-5/g++-5 from wily doesn't show the test failure. the only difference in the configuration is that the one in wily is built using the old libstdc++ ABI and the one in the PPA with the dual ABI defaulting to new/c++11. building with -O2 instead of -O3 works around the issue. [ RUN ] CDROMTest.FindPackages /scratch/doko/tmp/apt-1.0.9.10ubuntu1/test/libapt/cdromfindpackages_test.cc:95: Failure Value of: InfoDir Actual: Expected: path + /.disk/ Which is: /tmp/apt-tests-findpackage.gpopMw/.disk/ [ FAILED ] CDROMTest.FindPackages (4 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1473674/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
