[Touch-packages] [Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2055776
Title:
After updating ubuntu, the network to which the subnet address is
assigned does not become active in KVM.
Status in dnsmasq package in Ubuntu:
Confirmed
Bug description:
phenomenon:
After updating ubuntu, the network to which the subnet address is assigned
does not become active in KVM.
Cause:
This is because the following dnsmasq update operation performed by apt's
automatic update causes an error. It worked properly with dnsmasq 2.80, but
does not work properly with 2.90.
$ cat /var/log/apt/history.log
(snip)
Start-Date: 2024-02-27 06:17:31
Commandline: /usr/bin/unattended-upgrade
Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
End-Date: 2024-02-27 06:17:44
(snip)
$
Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below
is an example.
$ cat default.conf
##WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
##OVERWRITTEN AND LOST. Changes to this configuration should be made using:
##virsh net-edit default
## or other application using the libvirt API.
##
## dnsmasq conf file created by libvirt
strict-order
user=libvirt-dnsmasq
pid-file=/run/libvirt/network/default.pid
except-interface=lo
bind-dynamic
interface=virbr0
dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
dhcp-no-override
dhcp-authoritative
dhcp-lease-max=253
dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
$
When starting the network with KVM (virsh net-start), dnsmasq started from
KVM executes the make_sock function twice as shown below.
$ cat network.c
(snip)
1087 static struct listener *create_listeners(union mysockaddr *addr, int
do_
1087 tftp, int dienow)
1088 {
1089 struct listener *l = NULL;
1090 int fd = -1, tcpfd = -1, tftpfd = -1;
1091
1092 (void)do_tftp;
1093
1094 if (daemon->port != 0)
1095 {
1096 fd = make_sock(addr, SOCK_DGRAM, dienow);
1097 tcpfd = make_sock(addr, SOCK_STREAM, dienow);
1098 }
(snip)
The following code causes an issue with the update made in dnsmasq
2.90.
$ cat network.c
(snip)
895 static int make_sock(union mysockaddr *addr, int type, int dienow)
896 {
(snip)
934 if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
935 {
936 if (dienow)
937 die(s, daemon->addrbuff, EC_BADNET);
938 else
939 my_syslog(LOG_WARNING, s, daemon->addrbuff,
strerror(errno))939 ;
940 }
(snip)
function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24,
and then make_sock in network.c:1097 tries to bind to the same address.
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so
dnsmasq does not cause a startup error. As a result, virsh net-start fails.
As a temporary workaround, it will work if you try not to die.
$ diff -u network_c_back network.c
--- network_c_back 2024-02-29 15:36:05.156467935 +
+++ network.c 2024-02-29 15:36:38.733324350 +
@@ -934,7 +934,8 @@
if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
{
if (dienow)
- die(s, daemon->addrbuff, EC_BADNET);
+ my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
+ //die(s, daemon->addrbuff, EC_BADNET);
else
my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
}
$
If bind-dynamic is set, it should be modified so that it works even if
errno==98.
For reference, in the case of dnsmasq 2.80, the code is as follows, so
no error occurs.
network.c
699 static int make_sock(union mysockaddr *addr, int type, int dienow)
700 {
701 int family = addr->sa.sa_family;
702 int fd, rc, opt = 1;
(snip)
715 err:
716 errsave = errno;
717 port = prettyprint_addr(addr, daemon->addrbuff);
718 if (!option_bool(OPT_NOWILD) && !option_bool(OPT_CLEVERBIND))
719 sprintf(daemon->addrbuff, "port %d", port);
720 s = _("failed to create listening socket for %s: %s");
721
722 if (fd != -1)
723 close (fd);
724
725 errno = errsave;
726
727 if (dienow)
728 {
729 /* failure to bind addresses given by --listen-address at
this
729 point
730 is OK if we're doing bind-dynamic */
731 if (!option_bool(OPT_CLEVERBIND))
732 die(s, daemon->addrbuff, EC_BADNET);
733
[Touch-packages] [Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
Something in a recent dnsmasq update broke KVM. I hit the same and found
a workaround that gets me rolling again wtih KVM guests at least
here's a quick shell summary:
bladernr@galactica:~$ sudo virsh net-start default
error: Failed to start network default
error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) unexpected exit status 2:
dnsmasq: failed to create listening socket for 192.168.123.1: Address already
in use
bladernr@galactica:~$ sudo virsh net-list
Name State Autostart Persistent
bladernr@galactica:~$ sudo apt-cache policy dnsmasq-base
dnsmasq-base:
Installed: 2.90-0ubuntu0.23.10.1
Candidate: 2.90-0ubuntu0.23.10.1
Version table:
*** 2.90-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
100 /var/lib/dpkg/status
2.89-1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
bladernr@galactica:~$ sudo apt install dnsmasq-base=2.89-1
bladernr@galactica:~$ sudo virsh net-start default
Network default started
bladernr@galactica:~$ sudo virsh net-list
Name StateAutostart Persistent
default active yes yes
as you can see, as a workaround, reverting to the original Mantic
version allows the NAT network to start and I can once again launch KVM
guests on my machine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2055776
Title:
After updating ubuntu, the network to which the subnet address is
assigned does not become active in KVM.
Status in dnsmasq package in Ubuntu:
Confirmed
Bug description:
phenomenon:
After updating ubuntu, the network to which the subnet address is assigned
does not become active in KVM.
Cause:
This is because the following dnsmasq update operation performed by apt's
automatic update causes an error. It worked properly with dnsmasq 2.80, but
does not work properly with 2.90.
$ cat /var/log/apt/history.log
(snip)
Start-Date: 2024-02-27 06:17:31
Commandline: /usr/bin/unattended-upgrade
Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
End-Date: 2024-02-27 06:17:44
(snip)
$
Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below
is an example.
$ cat default.conf
##WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
##OVERWRITTEN AND LOST. Changes to this configuration should be made using:
##virsh net-edit default
## or other application using the libvirt API.
##
## dnsmasq conf file created by libvirt
strict-order
user=libvirt-dnsmasq
pid-file=/run/libvirt/network/default.pid
except-interface=lo
bind-dynamic
interface=virbr0
dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
dhcp-no-override
dhcp-authoritative
dhcp-lease-max=253
dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
$
When starting the network with KVM (virsh net-start), dnsmasq started from
KVM executes the make_sock function twice as shown below.
$ cat network.c
(snip)
1087 static struct listener *create_listeners(union mysockaddr *addr, int
do_
1087 tftp, int dienow)
1088 {
1089 struct listener *l = NULL;
1090 int fd = -1, tcpfd = -1, tftpfd = -1;
1091
1092 (void)do_tftp;
1093
1094 if (daemon->port != 0)
1095 {
1096 fd = make_sock(addr, SOCK_DGRAM, dienow);
1097 tcpfd = make_sock(addr, SOCK_STREAM, dienow);
1098 }
(snip)
The following code causes an issue with the update made in dnsmasq
2.90.
$ cat network.c
(snip)
895 static int make_sock(union mysockaddr *addr, int type, int dienow)
896 {
(snip)
934 if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
935 {
936 if (dienow)
937 die(s, daemon->addrbuff, EC_BADNET);
938 else
939 my_syslog(LOG_WARNING, s, daemon->addrbuff,
strerror(errno))939 ;
940 }
(snip)
function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24,
and then make_sock in network.c:1097 tries to bind to the same address.
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so
dnsmasq does not cause a startup error. As a result, virsh net-start fails.
As a temporary workaround, it will work if you try not to die.
$ diff -u network_c_back network.c
--- network_c_back
[Touch-packages] [Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
contents of /var/crash attached ** Attachment added: "crash.tgz" https://bugs.launchpad.net/subiquity/+bug/2055418/+attachment/5752934/+files/crash.tgz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: New Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
@crish it doesn't appear to like that command: $ sudo apport-cli -u 2055418 -c /var/crash/*.crash Usage: apport-cli [options] [symptom|pid|package|program path|.apport/.crash file] apport-cli: error: -u/--update-bug option cannot be used together with options for a new report -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: New Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046375] Re: gdb-dbgsym missing from jammy-updates
** Package changed: ubuntu => gdb (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2046375 Title: gdb-dbgsym missing from jammy-updates Status in gdb package in Ubuntu: New Bug description: gdb is in http://archive.ubuntu.com/ubuntu/dists/jammy- updates/main/binary-amd64/Packages.gz: Package: gdb Architecture: amd64 Version: 12.1-0ubuntu1~22.04 But gdb-dbgsym is not in http://ddebs.ubuntu.com/dists/jammy- updates/main/binary-amd64/Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2046375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2018656] [NEW] login process frozen in between username and password
Public bug reported: MY SYSTEM No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2018656 Title: login process frozen in between username and password Status in gnome-online-accounts package in Ubuntu: New Bug description: MY SYSTEM No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash
[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu
Also affected. Downgrading to 2.9 worked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
Questions/Comments: What does "remotely" mean here? The bug report speaks of using the laptop keyboard, not remote access; and a remote connection would mean just passing a data stream - the local keymap setting has no effect on the keys sent by a remote connection. localectl is not how we manage keyboard settings in Ubuntu, and console-data is a package in universe that we don't use at all. If you need to change the keymap, this should be done with `sudo dpkg-reconfigure keyboard-configuration`. localectl may or may not do the right thing, it's basically untested. Regardless, capslock or shift not working correctly should not be a question of keymap, there are no keymaps we ship by default that don't handle these keys in the normal way. Perhaps this is a kernel or issue or a bug with their ACPI tables? -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in systemd package in Ubuntu: New Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
I can confirm that the issue may be in qemu in 22.04. A "real" s390x running 22.04 does not have this issue and the same installation image does not have this issue running on Windows 11, qemu version 7.0.0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade Status in openssh package in Ubuntu: New Bug description: This s390x VM has been upgraded to Jammy, including the host (qemu- system-s390x 1:6.2+dfsg-2ubuntu6). Now any attempt to use ssh, or any incoming sshd attempt immediately results in e.g.: ryan@s390x-dev:~$ ssh g...@github.com [ 433.672800] User process fault: interruption code 0011 ilc:3 in libc.so.6[3ffa6c0+1ca000] [ 433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800 [ 433.672977] Fault in primary space mode while using user ASCE. [ 433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 P:0400 Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969656] [NEW] package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Not sure ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Apr 20 09:53:29 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash video=hyperv_fb:1366x768 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3713-0728-9815-5000-5213-4336-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1969656 Title: package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Not sure ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Apr 20 09:53:29 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash video=hyperv_fb:1366x768 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual
[Touch-packages] [Bug 1969477] Re: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection
>If direct access to Launchpad is blocked how was a bug report filed in the first place? Clicking the "Report a Bug" link on any project's page in LP. This is done from a machine outside of the airgapped or restricted access lab where the hardware sits. Also, I should point out (which I mentioned originally) that one can, and I'll also start suggesting they do this, use --save with ubuntu-bug to create a bug report that can be submitted later from a different machine. I'm just asking to have apport-collect also feature this... Perhaps the solution since, as you pointed out, apport needs to read the bug to know which package to collect files for, is to require the package as part of the commmand... e.g. apport-collect --save=/path/to/filename --package=$PACKAGE $BUG_NUMBER -- 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/1969477 Title: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection Status in apport package in Ubuntu: Incomplete Bug description: We very often tell our hardware partners to "file a bug" when they encounter issues. This requires them to run apport-collect to gather and submit logs for the bug. However, very often, the hardware that has the problem is in a lab that has tight security restrictions and direct access to launchpad is blocked. This makes it nearly impossible for them to gather any requested logs, since apport-collect requires a direct line to Launchpad. apport-collect needs to adopt the --save feature of apport-bug/ubuntu- bug to save the prescribed logs and system data in a tarball that can then be attached to a bug after the fact. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.23 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 10:25:54 2022 InstallationDate: Installed on 2016-02-11 (2258 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969477] [NEW] apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection
Public bug reported: We very often tell our hardware partners to "file a bug" when they encounter issues. This requires them to run apport-collect to gather and submit logs for the bug. However, very often, the hardware that has the problem is in a lab that has tight security restrictions and direct access to launchpad is blocked. This makes it nearly impossible for them to gather any requested logs, since apport-collect requires a direct line to Launchpad. apport-collect needs to adopt the --save feature of apport-bug/ubuntu- bug to save the prescribed logs and system data in a tarball that can then be attached to a bug after the fact. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.23 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 10:25:54 2022 InstallationDate: Installed on 2016-02-11 (2258 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1969477 Title: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection Status in apport package in Ubuntu: New Bug description: We very often tell our hardware partners to "file a bug" when they encounter issues. This requires them to run apport-collect to gather and submit logs for the bug. However, very often, the hardware that has the problem is in a lab that has tight security restrictions and direct access to launchpad is blocked. This makes it nearly impossible for them to gather any requested logs, since apport-collect requires a direct line to Launchpad. apport-collect needs to adopt the --save feature of apport-bug/ubuntu- bug to save the prescribed logs and system data in a tarball that can then be attached to a bug after the fact. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.23 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 10:25:54 2022 InstallationDate: Installed on 2016-02-11 (2258 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's seemingly much less bad if I disable suspend when plugged into power, and maybe the remaining problems come from plugging in power before resume. -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
This one seemed like it refused to wake even enough to draw a black scree, just stayed asleep. I've no idea if this is hlepful ** Attachment added: "refuses_to_wake.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5579458/+files/refuses_to_wake.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
Another purple screen lockup. It's now also more common the system runs how while closed. ** Attachment added: "purple_screen_lockup-8_april.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5578017/+files/purple_screen_lockup-8_april.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I've still not tried other kernels, in part because ubuntu keeps pushing out new OEM kernels, so I give them all a try, but the same basic problem persist, either gnome-shell gives only a black screen, or else the whole system hangs on the purple screen. I've far more diverse crashes with the latest kernels and the bolt upgrade: https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: New Status in systemd package in Ubuntu: New Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
** Changed in: systemd (Ubuntu) Importance: Undecided => High -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: New Status in systemd package in Ubuntu: New Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Can this be reproduced in EFI mode, or is it only when in Legacy Mode? ALso, what is the mount command you are using? Just basic like "mount /dev/device /mountpoint"? Or is there a different mount command you are using that is failing? -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in systemd package in Ubuntu: New Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's growing kinda worst with 5.14.0-1031-oem in that gnome-shell now more reliably fails unsleep, but I've not yet seen any real crash under 5.14.0-1031-oem. I've still not tried non OWM kernels. ** Attachment added: "black_screen_with_mouse-29_march-b.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5574448/+files/black_screen_with_mouse-29_march-b.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I'd another crash with a purple screen and no mouse movement, but this time only a 10 minute lid close caused the crash. Awful lot of gdm and gnome-shell errors this time, but not clear the source. ** Attachment added: "purple_no_mouse-23_march.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572272/+files/purple_no_mouse-23_march.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel:
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's again waking with a black screen in which only mouse and Fn+Ctrl+Alt+F?? keys work. I've attached the jountalctl -b0 output from prior to reboot, probably more relevant than grabbing the actual reboot. Mär 23 07:09:16 aletheia kernel: Restarting tasks ... done. Mär 23 07:09:16 aletheia systemd-logind[1556]: Lid opened. Mär 23 07:09:16 aletheia Tor[1683]: Tor has been idle for 26589 seconds; assuming established circuits no longer work. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: The canary thread is apparently starving. Taking action. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: Demoting known real-time threads. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: Demoted 0 threads. Mär 23 07:09:16 aletheia Tor[1683]: Heartbeat: Tor's uptime is 0:00 hours, with 0 circuits open. I've sent 0 kB and received 0 kB. Mär 23 07:09:16 aletheia systemd[1]: NetworkManager-dispatcher.service: Succeeded. Mär 23 07:09:16 aletheia kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Mär 23 07:09:16 aletheia kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mär 23 07:09:16 aletheia systemd[1]: Starting Daily apt download activities... Mär 23 07:09:16 aletheia systemd[1]: Starting Refresh fwupd metadata and update motd... Mär 23 07:09:16 aletheia systemd[1]: Starting Message of the Day... Mär 23 07:09:16 aletheia systemd[1]: Starting Ubuntu Advantage Timer for running repeated jobs... Mär 23 07:09:16 aletheia systemd[1]: motd-news.service: Succeeded. Mär 23 07:09:16 aletheia systemd[1]: Finished Message of the Day. Mär 23 07:09:16 aletheia upowerd[1864]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia upowerd[1864]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia systemd-sleep[34855]: System resumed. Mär 23 07:09:16 aletheia kernel: PM: suspend exit Mär 23 07:09:16 aletheia gsd-power[2839]: Error calling suspend action: GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress Mär 23 07:09:16 aletheia fwupd[3148]: 06:09:16:0867 FuEngine failed to record HSI attributes: failed to get historical attr: json-glib version too old Mär 23 07:09:16 aletheia systemd[1]: systemd-suspend.service: Succeeded. Mär 23 07:09:16 aletheia systemd[1]: Finished Suspend. We compare this semi-locked gnome-shell with a working unsleep from a brief lid close: Mär 23 07:42:19 aletheia kernel: Restarting tasks ... Mär 23 07:42:19 aletheia kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Mär 23 07:42:19 aletheia systemd-logind[1529]: Lid opened. Mär 23 07:42:19 aletheia kernel: done. Mär 23 07:42:19 aletheia upowerd[1838]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:42:19 aletheia kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mär 23 07:42:19 aletheia upowerd[1838]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia systemd-sleep[34855]: System resumed. Mär 23 07:42:19 aletheia kernel: PM: suspend exit Mär 23 07:42:19 aletheia systemd[1]: systemd-suspend.service: Succeeded. Mär 23 07:42:19 aletheia systemd[1]: Finished Suspend. I wind up with gnome-shell being stuck when "kernel: done" never appears, the "upowerd" line appears twice, and we get the error: Mär 23 07:09:16 aletheia gsd-power[2839]: Error calling suspend action: GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress I've maybe some early unsleep phase not finishing correctly, which then convinces gsd-power believing that sleep continues? * Irrelevant looking differences: The mei_hdcp comes before the lid opened line. Activities like tor and rt-kit-daemon have not been asleep long enough to be doing restart work. ** Attachment added: "black_screen_with_mouse.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572108/+files/black_screen_with_mouse.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
Appears nope I've purely a sleep problem, unless all this fwupd playing turnned off hibernate: ``` root@aletheia:/home/jeff/Downloads# systemctl status hibernate.target ● hibernate.target - Hibernate Loaded: loaded (/lib/systemd/system/hibernate.target; static; vendor prese> Active: inactive (dead) Docs: man:systemd.special(7) root@aletheia:/home/jeff/Downloads# systemctl status hybrid-sleep.target ● hybrid-sleep.target - Hybrid Suspend+Hibernate Loaded: loaded (/lib/systemd/system/hybrid-sleep.target; static; vendor pr> Active: inactive (dead) Docs: man:systemd.special(7) ``` -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: l
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I've found some lenovo firmware oddities too https://github.com/fwupd/firmware-lenovo/issues/210 so I'll poke around there too. ** Bug watch added: github.com/fwupd/firmware-lenovo/issues #210 https://github.com/fwupd/firmware-lenovo/issues/210 -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
It's related to during being suspended: It does not trigger on pressing suspend from the menu bar, waiting briefly, and then pressing keys to wake. It also does not trigger if I close and open the lid less than a minute later. It can now trigger if I close the lid and then reopen the lid 10 minutes later. At this point it arrives at a purple ubuntu login screen, but no responses to keyboard or mouse, and not network presence. Could this be caused by the system changing sleep/suspend mode while sleeping/suspended? Could this be related to /swapfile being only 4 gigs, while main memory is 16 gigs? It's a ThinkPad X1 Carbon Gen 11 running a kernel 5.14.0-1027-oem for a Gen 9 (nothing else exists afaik). I've no idea what OEM kernels change of course, but I can try to figure out changing the kernel. I'll likely need to change something in /etc/default/grub to get access to a grub boot menu to choose kernels. ** Attachment added: "purple_no_mouse_two.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5571706/+files/purple_no_mouse_two.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias:
[Touch-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password
I've also found folks fixed similar issues by downgrading the kernel to 5.11.0.38: https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown -- 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/1965219 Title: gnome lock screen does not permit reentering password Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [Bug 493050] Re: ubuntu-bug "Collecting problem information..." for over 30 min
Yes, this remains an issues in ubuntu 20, nearly a fresh install. I'll
try to report what happens, but it's running for over an hour so far.
It's progress bar does slowly move however.
--
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/493050
Title:
ubuntu-bug "Collecting problem information..." for over 30 min
Status in apport package in Ubuntu:
Expired
Bug description:
Binary package hint: apport
ubuntu-bug xserver-xorg-video-nouveau = "Collecting problem
information ... This might take a few minutes. ." it just
filled the 80x50 screen with 4000 dots, at about 1/2 sec per is 30
minutes.
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
carl 2529 0.2 1.8 89260 36592 pts/2Sl+ 22:11 0:08
/usr/bin/python /usr/bin/apport-cli xserver-xorg-video-nouveau
seems to be the same thing as #397140 so I am doing the strace ting:
carl@gw42:~$ pgrep apport
2529
carl@gw42:~$ ps ux|grep apport-cli | grep -v grep|awk '{print $2}'
2529
2716
carl@gw42:~$ strace -vvs1024 -o /tmp/apport-gtk.trace -p 2529
Process 2529 attached - interrupt to quit
which is lots of:
select(0, NULL, NULL, NULL, {0, 12114}) = 0 (Timeout)
gettimeofday({1260076594, 5680}, NULL) = 0
select(0, NULL, NULL, NULL, {0, 36012}) = 0 (Timeout)
gettimeofday({1260076594, 41961}, NULL) = 0
but I was able to run it for this report.
ProblemType: Bug
Architecture: amd64
Date: Sat Dec 5 23:00:07 2009
DistroRelease: Ubuntu 9.10
Package: apport 1.9.3-0ubuntu4.1
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: apport
Uname: Linux 2.6.31-16-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/493050/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
Thanks @Giovanni Pellerano for bumping this again. I can confirm that this is an issue in python3.9 (3.9.7, "3.9.7-2build1") and python3.10 (3.10.0, "3.10.0-2") on 21.10 (amd64). I imagine if nothing is done, the upcoming 22.04 LTS will have the issue in its default python(3), which I imagine will be some version of 3.10. # python3 --version Python 3.9.7 # ./checksec --file=/usr/bin/python3 RELRO STACK CANARY NXPIE RPATH RUNPATH Symbols FORTIFY Fortified Fortifiable FILE Partial RELRO Canary found NX enabledNo PIE No RPATH No RUNPATH No SymbolsYes 14 39 /usr/bin/python3 # python3.10 --version Python 3.10.0 # ./checksec --file=/usr/bin/python3.10 RELRO STACK CANARY NXPIE RPATH RUNPATH Symbols FORTIFY Fortified Fortifiable FILE Partial RELRO Canary found NX enabledNo PIE No RPATH No RUNPATH No SymbolsYes 14 39 /usr/bin/python3.10 Alternatively, via `hardening-check` from the devscripts package: # hardening-check /usr/bin/python3 /usr/bin/python3: Position Independent Executable: no, normal executable! Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: no, not found! Stack clash protection: unknown, no -fstack-clash-protection instructions found Control flow integrity: yes # hardening-check /usr/bin/python3.10 /usr/bin/python3.10: Position Independent Executable: no, normal executable! Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: no, not found! Stack clash protection: unknown, no -fstack-clash-protection instructions found Control flow integrity: yes ** Also affects: python3.9 (Ubuntu) Importance: Undecided Status: New ** Also affects: python3.10 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in Python: New Status in python2.7 package in Ubuntu: Fix Released Status in python3.10 package in Ubuntu: New Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: Confirmed Status in python3.7 package in Ubuntu: Confirmed Status in python3.8 package in Ubuntu: Confirmed Status in python3.9 package in Ubuntu: New Status in python3.7 package in Debian: New Status in python3.8 package in Debian: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki/Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1452115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array
Please verify this is no longer an issue in Focal or Hirsute based on Graham's comment #3 above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Incomplete Status in lvm2 source package in Focal: Incomplete Status in lvm2 source package in Groovy: Won't Fix Status in lvm2 source package in Hirsute: Incomplete Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941932] [NEW] Reverting to nouveau driver leaves dead nvidia links causing suspend and shutdown to fail
Public bug reported: After having problems with the nvidia driver 470, I reverted to the nouveau driver, only to find that using suspend or shutdown in the XFCE4 menu just returned to the login page. However, I found that using the 'shutdown' or 'pm-suspend' commands worked OK. Checking syslog after a failed suspend lead me to /etc/systemd/system directory: lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-hibernate.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-resume.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-suspend.service -> /dev/null Also, there were two directories containing links to the above 'masked' services. Deleting those links restored suspend and shutdown functionality. drwxr-xr-x 2 root root 4096 Aug 26 18:14 systemd-hibernate.service.requires/ drwxr-xr-x 2 root root 4096 Aug 26 18:08 systemd-suspend.service.requires/ Obviously a problem in removing all the nvidia settings. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04.2 software-properties xubuntu ** Tags added: 20.04.2 software-properties xubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1941932 Title: Reverting to nouveau driver leaves dead nvidia links causing suspend and shutdown to fail Status in software-properties package in Ubuntu: New Bug description: After having problems with the nvidia driver 470, I reverted to the nouveau driver, only to find that using suspend or shutdown in the XFCE4 menu just returned to the login page. However, I found that using the 'shutdown' or 'pm-suspend' commands worked OK. Checking syslog after a failed suspend lead me to /etc/systemd/system directory: lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-hibernate.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-resume.service -> /dev/null lrwxrwxrwx 1 root root9 Aug 25 15:04 nvidia-suspend.service -> /dev/null Also, there were two directories containing links to the above 'masked' services. Deleting those links restored suspend and shutdown functionality. drwxr-xr-x 2 root root 4096 Aug 26 18:14 systemd-hibernate.service.requires/ drwxr-xr-x 2 root root 4096 Aug 26 18:08 systemd-suspend.service.requires/ Obviously a problem in removing all the nvidia settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1941932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940779] [NEW] has_options missing so ssh-agent doesn't start
Public bug reported: The file /etc/X11/Xsession.d/20x11-common_process-args is missing the definition of the function has_option() in the 21.04 distribution. As a result, when lightdm starts X11, even though use-ssh-agent is specified in Xsession.options, the test fails and so the agent is not started. This is in the context of using the i3 window manager, which shouldn't matter except that maybe gnome does stuff on its own that makes the problem not apparent there. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3 Date: Sun Aug 22 20:14:49 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: 2021-08-21 20:57:39,784 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.11.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:060d] Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d] InstallationDate: Installed on 2015-12-17 (2075 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Dell Precision M3800 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-08-21 (0 days ago) dmi.bios.date: 08/17/2015 dmi.bios.release: 65.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/17/2015:br65.10:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.X11.Xsession.d.20x11-common_process-args: 2021-08-22T20:12:04.931804 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1940779 Title: has_options missing so ssh-agent doesn't start Status in xorg package in Ubuntu: New Bug description: The file /etc/X11/Xsession.d/20x11-common_process-args is missing the definition of the function has_option() in the 21.04 distribution. As a result, when lightdm starts X11, even though use-ssh-agent is specified in Xsession.options, the test fails and so the agent is not started. This is in the context of using the i3 window manager, which shouldn't matter except that maybe gnome does stuff on its own that makes the problem not apparent there. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3 Date: Sun Aug 22 20:14:49 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: 2021-08-21 20:57:39,784 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.11.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too
[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array
** Changed in: lvm2 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: lvm2 (Ubuntu Focal) Status: Confirmed => Incomplete ** Changed in: lvm2 (Ubuntu Hirsute) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Incomplete Status in lvm2 source package in Focal: Incomplete Status in lvm2 source package in Groovy: Won't Fix Status in lvm2 source package in Hirsute: Incomplete Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory
ai_ja_nai (albertomassidda), while it is true that the bug is still alive and kicking, there is a way to work around the issue. See bug 1652789, https://bugs.launchpad.net/ubuntu/+source/indicator- datetime/+bug/1652789/comments/4 . https://askubuntu.com/questions/876524/how-do-i-begin-to-diagnose-and- fix-indicator-datetime-service-using-100-cpu-and#1022408 describes, in a fairly detailed way, how to disable the local calendar from the online calendar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1642634 Title: indicator-datetime uses excessive memory Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: On my Aquaris 4.5, OTA-13, indicator-datetime 15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS is 315892, almost three times as much as unity8. I believe this is an OTA regression. I'm not sure if it regressed from OTA-11 or OTA-12. Just now, I got caught in an oom killer loop with constant killing of unity8-dash because of this, making my phone unusable. I had to kill indicator-datetime manually. It then restarted automatically and now uses 80456 RSS only. I see bug 1633319 exists complaining about a memory leak. It's not exactly the same version since mine is 15.10+15.04.20160820.1-0ubuntu1 and that one is 15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are the same or something? Perhaps the two are dupes, but I'll let someone more familiar make that determination. I have only a handful of alarms (perhaps five on average; rarely more) but I do have my Google calendar syncing with perhaps hundreds of events. However, there's no reason that this should cause indicator- datetime to use more RSS; it shouldn't be keeping these in memory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
After two years of waiting on this, and seeing how disappointing the progress has been both in Ubuntu and PulseAudio, I am happy to say that I believe PipeWire is the future and I would hope that Ubuntu moves forward with switching to PipeWire (while keeping PulseAudio as an alternative). I was able to follow these directions to switch to PipeWire and have found it to be acceptable with Bose NC700s and mSBC/HFP: From: https://www.reddit.com/r/pop_os/comments/ofdalv/replaced_pulseaudio_with_pipewire_on_popos_2104_i/h4c5p6u/ # Add ppa for latest build sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream && sudo apt update # Install components sudo apt install gstreamer1.0-pipewire pipewire-media-session libspa-0.2-bluetooth libspa-0.2-jack pipewire pipewire-audio-client-libraries # If you get unmet dependencies, you can run: sudo apt --fix-broken install # Reload new services systemctl --user daemon-reload # Disable PulseAudio service systemctl --user --now disable pulseaudio.service pulseaudio.socket # If you update from previous version of PopOS systemctl --user mask pulseaudio # Enable Pipewire services systemctl --user --now enable pipewire pipewire-pulse # Enable Pipewire media session systemctl --user --now enable pipewire-media-session.service # I ran into an issue with a couple dependencies and needed to do the following before everything worked: sudo apt install libspa-0.2-bluetooth libfdk-aac2 systemctl --user restart pipewire.service pipewire-pulse.service Hope this helps. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
** Package changed: lxc (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: New Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array
Mariusz, > The following patches should fix the issue (not verified yet): > https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca > https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 Were those patches verified to fix this in LVM2? And is there an upstream release version that contains them? ** Changed in: lvm2 (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Status in lvm2 source package in Groovy: Won't Fix Status in lvm2 source package in Hirsute: Confirmed Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
For those following along - it appears that the future of Linux audio servers will likely be PipeWire: https://lwn.net/SubscriberLink/847412/d7826b1353e33734/ -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array
Can this please be targeted for 21.10? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Status in lvm2 source package in Groovy: Confirmed Status in lvm2 source package in Hirsute: Confirmed Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array
** Also affects: lvm2 (Ubuntu Hirsute) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Status in lvm2 source package in Groovy: Confirmed Status in lvm2 source package in Hirsute: Confirmed Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
>Jean- (jean-helou) wrote 6 hours ago: #87 >the next step to get a full fix and improved sound quality for voip calls over >BT headset is >coming in >https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 This is good news! Proper support for mSBC is critical for me to consider this bug resolved. It was the original intention of opening the bug in the first place :) -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1170353] Re: Host names intermittently resolve to 0.0.0.0
It's happened to me a few times on 20.04.1: $ host support.coinjar.com support.coinjar.com has address 0.0.0.0 support.coinjar.com has IPv6 address :: support.coinjar.com is an alias for coinjar.zendesk.com. coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com. $ sudo resolvectl flush-caches $ host support.coinjar.com support.coinjar.com has address 0.0.0.0 support.coinjar.com has IPv6 address :: support.coinjar.com is an alias for coinjar.zendesk.com. coinjar.zendesk.com mail is handled by 10 mail-pod-25.int.zendesk.com. $ dig support.coinjar.com ; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12759 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;support.coinjar.com. IN A ;; ANSWER SECTION: support.coinjar.com.34 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jan 06 20:23:28 AEDT 2021 ;; MSG SIZE rcvd: 64 Then 2 minutes later the problem resolves itself: $ dig support.coinjar.com ; <<>> DiG 9.16.1-Ubuntu <<>> support.coinjar.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64605 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;support.coinjar.com. IN A ;; ANSWER SECTION: support.coinjar.com.151 IN CNAME coinjar.zendesk.com. coinjar.zendesk.com.900 IN A 104.16.51.111 coinjar.zendesk.com.900 IN A 104.16.53.111 ;; Query time: 68 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Jan 06 20:25:31 AEDT 2021 ;; MSG SIZE rcvd: 110 Nothing in /var/log/syslog or systemd-resolved's systemd log. -- 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/1170353 Title: Host names intermittently resolve to 0.0.0.0 Status in network-manager package in Ubuntu: Invalid Bug description: About 5% of DNS queries resolve to 0.0.0.0. A couple of times an hour during normal browsing, Firefox resolves a domain to 0.0.0.0. Opening the same site in Chrome has a 50% chance of it working, then it normally works after a few reloads. Thunderbird has also occasionally resolved googlemail.com to 0.0.0.0. Domains include google.com, wikipedia.org, harvestapp.com and many more. I couldn't reproduce this with dig/nslookup for a while, but after 5 minutes of (re)trying random domains) did: $ dig mail.google.com ; <<>> DiG 9.8.1-P1 <<>> mail.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22905 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com. 60 IN A 0.0.0.0 ;; Query time: 0 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Thu Apr 18 13:57:04 2013 ;; MSG SIZE rcvd: 49 Note the "0 msec", so I'm pretty sure this is dnsmasq's local cache. Using Xubuntu 12.10, NetworkManager 0.9.6.0, Dnsmasq 2.63rc6. NetworkManager has DNS servers set to "8.8.8.8, 8.8.4.4" (also tried setting it to my router's DNS server, with no effect). /etc/resolve.conf just has "nameserver 127.0.1.1" dnsmasq is currently running: /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind- interfaces --pid-file=/var/run/sendsigs.omit.d/network- manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run /nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable- dbus=org.freedesktop.NetworkManager.dnsmasq --conf- dir=/etc/NetworkManager/dnsmasq.d ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Apr 18 14:27:33 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-11 (97 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) IpRoute: default via 10.0.0.1 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.10 metric 1 169.254.0.0/16 dev eth0 scope
[Touch-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
It appears that one of the recent updates fixed this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902580 Title: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: Confirmed Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
systemctl --user status pulseaudio.service ** Attachment added: "systemctl --user status pulseaudio.service" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+attachment/5438826/+files/systemctl_--user_status_pulseaudio.service.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902580 Title: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: Confirmed Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887372] Re: Cannot create lvm upon IMSM raid array
** Changed in: lvm2 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887372 Title: Cannot create lvm upon IMSM raid array Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Status in lvm2 source package in Groovy: Confirmed Bug description: The issue has been observed on 2.3.7 (Ubuntu 20.04). Reported to lvm team: https://bugzilla.redhat.com/show_bug.cgi?id=1855251 Steps to Reproduce: 1. Create IMSM raid array: #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G 2. Create lvm volume on raid: # pvcreate -ff -y /dev/md/vol # vgcreate group0 /dev/md/vol # lvcreate -Z y -y -l +100%FREE group0 -n lvm0 Actual results: Vg creation fails. Expected results: LVM should be able to determine the best drive and ignore duplicates. Additional info: IMSM metadata is written at the end of the drive. The first drive sector belongs to the raid volume and other metadata saved there (like lvm) can be recognized directly on raid members. The following patches should fix the issue (not verified yet): https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
** Description changed: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. + + + Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902580 Title: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: Confirmed Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Note: File samples are after reinstalling. (working state) Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902580] Re: Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
** Summary changed: - Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. + Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. ** Description changed: - My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I + My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902580 Title: Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: New Bug description: My Xubuntu 20.10 installation has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902580] [NEW] Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
Public bug reported: My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. - How I re-install pulseaudio (obvious but just in case) Xubuntu 20.10 has - No Sound (Dummy Output) unless I reinstall pulseaudio after every - reboot. + How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. - Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Nov 2 13:42:36 2020 InstallationDate: Installed on 2020-11-02 (0 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902580 Title: Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. Status in pulseaudio package in Ubuntu: New Bug description: My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot. pulseaudio does survive a suspend. Just a hard reset or power cycle causes it to fail. How I re-install pulseaudio: sudo apt-get install --reinstall pulseaudio I have tried just killing the pulseaudio service, and letting it restart on it's own. It restarts, but no audio. Reinstalling seems to do the trick though. Thank You, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: s
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
@Giovanni Pellerano (evilaliv3): So while lack of any of these (currently mainstream) hardening features is concerning with regards to exploitation (especially the lack of ASLR in a generally non-highly interactive exploitation context), my guess is that the upstream Python build toolchain is just outmoded and buggy and package maintainers are left holding the bag. Hanlon's razor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in Python: New Status in python2.7 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: Confirmed Status in python3.7 package in Ubuntu: Confirmed Status in python3.8 package in Ubuntu: Confirmed Status in python3.7 package in Debian: Unknown Status in python3.8 package in Debian: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki /Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1452115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
Sorry, turns out the /etc/systemd/system service file needs to be a symlink to trigger the bug. This will do it: su - cat < /crashsystemd@.service [Unit] Description=Template for instance %i [Service] ExecStart=/bin/true EOF cd /etc/systemd/system ln -s /crashsystemd@.service crashsystemd.service systemctl daemon-reload systemctl start crashsystemd After the 'systemctl start crashsystemd' my terminal says: Failed to start crashsystemd.service: Connection reset by peer See system logs and 'systemctl status crashsystemd.service' for details. and in the systemd logs I see: Jul 17 23:20:33 jturner-desktop systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Things are pretty broken now. 'systemctl' and 'reboot' commands won't work. Don't forget to delete the /etc/systemd/system/crashsystemd.service symlink before rebooting. -- 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd package in Ubuntu: New Bug description: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
Replicated on my local Ubuntu 20.04 system with systemd 245.4-4ubuntu3.1. It's a PEBCAK error where a user writes a .service file containing %i's, but instead of naming the file foo@bar.service, just names it foo.service. To replicate: cd /etc/systemd/system curl -s -o testemail2jira.service 'https://hg.sr.ht/~redradishtech/testemail2jira/raw/testemail2jira%40.service?rev=tip' systemctl daemon-reload systemctl start testemail2jira On one of the last two steps everything freezes, errors start appearing: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and /var/crash/_usr_lib_systemd_systemd.0.crash is created. -- 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd package in Ubuntu: New Bug description: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887744] Re: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
Attached is /var/crash/_usr_lib_systemd_systemd.0.crash ** Attachment added: "/var/crash/_usr_lib_systemd_systemd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+attachment/5393190/+files/_usr_lib_systemd_systemd.0.crash -- 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd package in Ubuntu: New Bug description: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1887744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887744] [NEW] systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798
Public bug reported: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service -> /opt/atlassian/jira/current/emailprocessing/testemail2jira/testemail2jira@.service File contents: [Unit] Description=Check that email to %i JIRA works [Service] #Type=oneshot # Note: I keep the config file, testemail2jira.json5 and rsa.* files in emailprocessing/, one directory below testemail2jira/, so that they can be version-controlled independently. # If you want testemail2jira.json5 and rsa.* within testemail2jira/, then add testemail2jira/ to WorkingDirectory and remove it from the ExecStart command WorkingDirectory=/opt/atlassian/%i/current/emailprocessing ExecStart=/opt/atlassian/%i/current/emailprocessing/testemail2jira/venv/bin/python testemail2jira/testemail2jira.py User=root [Install] WantedBy=multi-user.target Perhaps the problem is that my service file is a template (testemail2jira@.service), but I symlinked it as a regular 'testemail2jira.service'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 16 14:13:06 2020 InstallationDate: Installed on 2020-05-27 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 'Error:'] failed with exit code 1: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1887744 Title: systemd dumps core on starting service: Assertion 'u->instance' failed at src/core/load-fragment.c:4798 Status in systemd package in Ubuntu: New Bug description: On an Ubuntu 20.04 server, when I started a newly installed systemd service 'systemctl start testemail2jira.service', systemd trips on an assertion (from journalctl): Jul 16 13:49:12 pangolin-jiraconf systemd[1]: Assertion 'u->instance' failed at src/core/load-fragment.c:4798, function unit_load_fragment(). Aborting. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Caught , dumped core as pid 2906637. Jul 16 13:49:13 pangolin-jiraconf systemd[1]: Freezing execution. apport generates a core dump which I trust is attached. The server still works, but my terminal keeps showing: Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) and pauses for 25s after each command. In case it's relevant, the i was trying to start had just been symlinked into /etc/systemd/system/: root@pangolin-jiraconf # ls -la /etc/systemd/system/testemail2jira.service lrwxrwxrwx 1 root root 82 Jul 16 13:48 /etc/systemd/system/testemail2jira.service ->
[Touch-packages] [Bug 1881226] [NEW] package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18 Uname: Linux 5.3.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.core.rules Date: Thu May 28 21:49:38 2020 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-02-09 (474 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Shuttle Inc. DS81D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-55-generic root=UUID=ea9922c0-ef41-4846-8661-d5e00af2a309 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-29 (0 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.14 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FS81 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.14:bd09/17/2018:svnShuttleInc.:pnDS81D:pvrV1.0:rvnShuttleInc.:rnFS81:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: R dmi.product.name: DS81D dmi.product.sku: 1.0 dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1881226 Title: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18 Uname: Linux 5.3.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.core.rules Date: Thu May 28 21:49:38 2020 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-02-09 (474 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Shuttle Inc. DS81D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-55-generic root=UUID=ea9922c0-ef41-4846-8661-d5e00af2a309 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-29 (0 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.14 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FS81 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.14:bd09/17/2018:svnShuttleInc.:pnDS81D:pvrV1.0:rvnShuttleInc.:rnFS81:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: R dmi.product.name: DS81D dmi.product.sku: 1.0 dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1881226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879080] [NEW] error message when installing pyodbc in a venv
Public bug reported:
I have a fresh install of Ubuntu 20.04. I have the following packages
installed:
python3-venv
python3-pip
python3-wheel
unixodbc-dev
If I run these commands:
python3 -m venv ./test_env
. ./test_env/bin/activate
pip3 install pyodbc
This is the output I get. The package does seem to install successfully,
in spite of the fact that this is an error, not a warning.
Collecting pyodbc
Downloading pyodbc-4.0.30.tar.gz (266 kB)
|| 266 kB 3.5 MB/s
Building wheels for collected packages: pyodbc
Building wheel for pyodbc (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /tmp/test_env/bin/python3 -u -c 'import sys, setuptools, tokenize;
sys.argv[0] = '"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';
__file__='"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))'
bdist_wheel -d /tmp/pip-wheel-snlh9z0l
cwd: /tmp/pip-install-5uh1fr89/pyodbc/
Complete output (6 lines):
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'bdist_wheel'
ERROR: Failed building wheel for pyodbc
Running setup.py clean for pyodbc
Failed to build pyodbc
Installing collected packages: pyodbc
Running setup.py install for pyodbc ... done
Successfully installed pyodbc-4.0.30
Note that I do not get this error if I install pyodbc outside the venv.
Also, if I install it outside the venv FIRST, then pip will cache the
wheel package and use it when installing in the venv, and I don't get
the above error in that case.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 10:14:28 2020
InstallationDate: Installed on 2020-05-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1879080
Title:
error message when installing pyodbc in a venv
Status in python3-defaults package in Ubuntu:
New
Bug description:
I have a fresh install of Ubuntu 20.04. I have the following packages
installed:
python3-venv
python3-pip
python3-wheel
unixodbc-dev
If I run these commands:
python3 -m venv ./test_env
. ./test_env/bin/activate
pip3 install pyodbc
This is the output I get. The package does seem to install
successfully, in spite of the fact that this is an error, not a
warning.
Collecting pyodbc
Downloading pyodbc-4.0.30.tar.gz (266 kB)
|| 266 kB 3.5 MB/s
Building wheels for collected packages: pyodbc
Building wheel for pyodbc (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /tmp/test_env/bin/python3 -u -c 'import sys, setuptools,
tokenize; sys.argv[0] = '"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';
__file__='"'"'/tmp/pip-install-5uh1fr89/pyodbc/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))'
bdist_wheel -d /tmp/pip-wheel-snlh9z0l
cwd: /tmp/pip-install-5uh1fr89/pyodbc/
Complete output (6 lines):
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: invalid command 'bdist_wheel'
ERROR: Failed building wheel for pyodbc
Running setup.py clean for pyodbc
Failed to build pyodbc
Installing collected packages: pyodbc
Running setup.py install for pyodbc ... done
Successfully installed pyodbc-4.0.30
Note that I do not get this error if I install pyodbc outside the
venv. Also, if I install it outside the venv FIRST, then pip will
cache the wheel package and use it when installing in the venv, and I
don't get the above error in that case.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Toshiba Satellite Radius 12 C-720 same problem ubuntu 20.04 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Great to see traction on this, thank you for all your efforts Daniel! And to everyone else, this is a far more complex problem than you can imagine However it can and will be solved :) -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867799] Re: Focal: sudo: setrlimit(RLIMIT_CORE): Operation not permitted
Just spun up a Focal LXD container and this is still an issue in containers: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ sudo vim /etc/apt/sources.list sudo: setrlimit(RLIMIT_CORE): Operation not permitted ** Also affects: sudo (Ubuntu) Importance: Undecided Status: New ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1867799 Title: Focal: sudo: setrlimit(RLIMIT_CORE): Operation not permitted Status in juju: Invalid Status in sudo package in Ubuntu: Confirmed Bug description: When bootstrapping to focal and using debug output, we get the following outputted to the stderr. sudo: setrlimit(RLIMIT_CORE): Operation not permitted I'm unsure what it's attempting to do at that point, but others have also run into this with a suggested workaround. https://gitlab.alpinelinux.org/alpine/aports/issues/11122 https://bugzilla.redhat.com/show_bug.cgi?id=1773148 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1867799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
So I found a comment at https://unix.stackexchange.com/a/533900/253840 > My problem was that I had two services using same RuntimeDirectory (isc-dhcp-server and isc-dhcp-server6), but I configured only one to work. So when the second one died, its runtime directory got removed, making it a problem for the first service. Since I have only the IPv4 addresses configured as well, I decided to look into this. When I tested this out by changing the RuntimeDirectory to "dhcp- server6" and the exec line's PID file parameter to "-pf /run/dhcp- server6/dhcpd6.pid", everything worked as it should on a reboot. The PID file was created for /run/dhcp-server/dhcpd.pid successfully. -- 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/1448657 Title: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Just upgraded from 14-10 to 15-04, and now see the following in syslog: Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 audit(1430045408.725:8): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove rride" Apr 26 10:50:08 server sh[8619]: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied. Description:Ubuntu 15.04 Release:15.04 isc-dhcp-server: Installed: 4.3.1-5ubuntu2 --- 8x - # cat /etc/default/isc-dhcp-server # Defaults for isc-dhcp-server initscript # sourced by /etc/init.d/isc-dhcp-server # installed at /etc/default/isc-dhcp-server by the maintainer scripts # # This is a POSIX shell fragment # # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf). #DHCPD_CONF=/etc/dhcp/dhcpd.conf # Path to dhcpd's PID file (default: /var/run/dhcpd.pid). #DHCPD_PID=/var/run/dhcpd.pid # Additional options to start dhcpd with. # Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead #OPTIONS="" # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="" --- 8x - # ls -la /var/run lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run # ls -la /run/dhcp-server/ total 0 drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 . drwxr-xr-x 34 root root 1060 Apr 26 11:33 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
I'm encountering the same thing on a fresh installation of Ubuntu 20.04. Here is what happens right after a reboot: jeff@bridges:~$ ll /run/ | grep dhcp jeff@bridges:~$ sudo systemctl status isc-dhcp-server [sudo] password for jeff: ● isc-dhcp-server.service - ISC DHCP IPv4 server Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-04-28 23:59:43 MST; 11s ago Docs: man:dhcpd(8) Main PID: 1374 (dhcpd) Tasks: 4 (limit: 19047) Memory: 6.9M CGroup: /system.slice/isc-dhcp-server.service └─1374 dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf Apr 28 23:59:44 bridges dhcpd[1374]: Apr 28 23:59:44 bridges dhcpd[1374]: Listening on LPF/enp2s0/2c:60:0c:c6:a4:be/192.168.1.0/24 Apr 28 23:59:44 bridges sh[1374]: Listening on LPF/enp2s0/2c:60:0c:c6:a4:be/192.168.1.0/24 Apr 28 23:59:44 bridges sh[1374]: Sending on LPF/enp2s0/2c:60:0c:c6:a4:be/192.168.1.0/24 Apr 28 23:59:44 bridges sh[1374]: Sending on Socket/fallback/fallback-net Apr 28 23:59:44 bridges sh[1374]: Can't create PID file /run/dhcp-server/dhcpd.pid: No such file or directory. Apr 28 23:59:44 bridges dhcpd[1374]: Sending on LPF/enp2s0/2c:60:0c:c6:a4:be/192.168.1.0/24 Apr 28 23:59:44 bridges dhcpd[1374]: Sending on Socket/fallback/fallback-net Apr 28 23:59:44 bridges dhcpd[1374]: Can't create PID file /run/dhcp-server/dhcpd.pid: No such file or directory. Apr 28 23:59:44 bridges dhcpd[1374]: Server starting service. jeff@bridges:~$ sudo systemctl restart isc-dhcp-server jeff@bridges:~$ ll /run/ | grep dhcp drwxr-xr-x 2 rootroot 60 Apr 29 00:00 dhcp-server/ jeff@bridges:~$ ll /run/dhcp-server/ total 4 drwxr-xr-x 2 root root 60 Apr 29 00:00 ./ drwxr-xr-x 39 root root 1140 Apr 29 00:00 ../ -rw-r--r-- 1 root root5 Apr 29 00:00 dhcpd.pid I can hardcode the PID file names like Nicorac above mentions, but I'd rather things just work out of the box without needing to apply random workarounds like that. -- 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/1448657 Title: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Just upgraded from 14-10 to 15-04, and now see the following in syslog: Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 audit(1430045408.725:8): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove rride" Apr 26 10:50:08 server sh[8619]: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied. Description:Ubuntu 15.04 Release:15.04 isc-dhcp-server: Installed: 4.3.1-5ubuntu2 --- 8x - # cat /etc/default/isc-dhcp-server # Defaults for isc-dhcp-server initscript # sourced by /etc/init.d/isc-dhcp-server # installed at /etc/default/isc-dhcp-server by the maintainer scripts # # This is a POSIX shell fragment # # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf). #DHCPD_CONF=/etc/dhcp/dhcpd.conf # Path to dhcpd's PID file (default: /var/run/dhcpd.pid). #DHCPD_PID=/var/run/dhcpd.pid # Additional options to start dhcpd with. # Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead #OPTIONS="" # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="" --- 8x - # ls -la /var/run lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run # ls -la /run/dhcp-server/ total 0 drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 . drwxr-xr-x 34 root root 1060 Apr 26 11:33 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874964] [NEW] Secondary display in portrait mode renders incorrectly
Public bug reported: Using the Ubuntu 20.04 settings app to setup multiple monitors creates broken xrandr settings. Using the app to set a 3840x2160 primary monitor in Landscape and 1920x1080 in Right Portrait, the primary monitor ends up with a "virtual resolution" of 4680x2160 which creates a horizontal panning effect at the monitor boundary and pushes the secondary monitor's content far off to the side. Running xrandr shows the following (truncated for readability - screenshot attached) Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 connected 1080x1920+3840+0 left (normal left inverted right x axis y axis) 527mm x 296mm panning 1920x1920+3840+0 tracking 5760x2160+0+0 border 0/0/0/0 1920x1080 60.00 + 60.00* 59.9450.0023.98 ... DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 697mm x 392mm panning 4680x2160+0+0 tracking 5760x2160+0+0 border 0/0/0/0 The correct result for DP-4 would be 3840x2160. I will set this manually but wanted to report the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:42:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 22:53:21 2020 DistUpgraded: 2020-04-24 21:48:22,001 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696] InstallationDate: Installed on 2019-07-30 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Micro-Star International Co., Ltd. MS-7B09 ProcEnviron: LC_COLLATE=C PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) dmi.bios.date: 11/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.C0:bd11/14/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B09 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal possible-manual-nvidia-install resolution ubuntu ** Attachment added: "Screenshot from 2020-04-24 23-02-48.png" https://bugs.launchpad.net/bugs/1874964/+attachment/5360022/+files/Screenshot%20from%202020-04-24%2023-02-48.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,
[Touch-packages] [Bug 1868456] [NEW] "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container
Public bug reported: I fired up a LXD container using ubuntu-daily:f on my machine and every time I issue a comment inside the container using sudo, I get this error: sudo: setrlimit(RLIMIT_CORE): Operation not permitted I did some digging online and found this was reported against Fedora last fall which lead me to this bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 which seems to tie this to a change in sudo between 1.8.28 and 1.8.29. Focal has 1.8.31: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo sudo: Installed: 1.8.31-1ubuntu1 Candidate: 1.8.31-1ubuntu1 Version table: *** 1.8.31-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status This is not an issue on Bionic: bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1.2 Candidate: 1.8.21p2-3ubuntu1.2 Version table: *** 1.8.21p2-3ubuntu1.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.8.21p2-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages >From the redhat bug, the described workaround does clear these messages up: # set disable_coredump false Once I've done that, the error messages go away. ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Description changed: I fired up a LXD container using ubuntu-daily:f on my machine and every time I issue a comment inside the container using sudo, I get this error: sudo: setrlimit(RLIMIT_CORE): Operation not permitted - I did some digging online and found this was reported against Fedora last fall: + I did some digging online and found this was reported against Fedora last fall which lead me to this bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 which seems to tie this to a change in sudo between 1.8.28 and 1.8.29. Focal has 1.8.31: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo sudo: - Installed: 1.8.31-1ubuntu1 - Candidate: 1.8.31-1ubuntu1 - Version table: - *** 1.8.31-1ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.8.31-1ubuntu1 + Candidate: 1.8.31-1ubuntu1 + Version table: + *** 1.8.31-1ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status This is not an issue on Bionic: bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy sudo sudo: - Installed: 1.8.21p2-3ubuntu1.2 - Candidate: 1.8.21p2-3ubuntu1.2 - Version table: - *** 1.8.21p2-3ubuntu1.2 500 - 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 1.8.21p2-3ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installed: 1.8.21p2-3ubuntu1.2 + Candidate: 1.8.21p2-3ubuntu1.2 + Version table: + *** 1.8.21p2-3ubuntu1.2 500 + 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 1.8.21p2-3ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages From the redhat bug, the described workaround does clear these messages up: # set disable_coredump false Once I've done that, the error messages go away. ** Package changed: lxd (Ubuntu) => sudo (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1868456 Title: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container Status in sudo package in Ubuntu: New Bug description: I fired up a LXD container using ubuntu-daily:f on my machine and every time I issue a comment inside the container using sudo, I get this error: sudo: setrlimit(RLIMIT_CORE): Operation not permitted I did some digging online and found this was reported against Fedora last fall which lead me to this bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 which seems to tie this to a change in sudo between 1.8.28 and 1.8.29. Focal has 1.8.31: bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo sudo: Installed: 1.8.31-1ubuntu1 Candidate: 1.8.31-1ubuntu1 Version table: *** 1.8.31-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100
[Touch-packages] [Bug 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported
** Tags removed: hwcert-server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1089389 Title: juju bootstrap fail behind a proxy when a gpg key must be imported Status in software-properties package in Ubuntu: Triaged Bug description: This is related to a Maas environment hosted behind a proxy. I'm trying to use juju 0.6.0.1+bzr603-0juju1~precise1 ubuntu@maas:~$ cat .juju/environments.yaml environments: mymaas: type: maas maas-server: 'http://192.168.124.2:80/MAAS' maas-oauth: 'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt' admin-secret: 'nothing' default-series: precise juju-origin: ppa When juju boostrap, things do not behave as expected on the zookeeper node. Excerpt from the cloud-init-output.log: W: GPG error: http://ppa.launchpad.net precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 376A290EC8068B11 On the zookeeper node, if i try to apt-add-repository , the needed gpg key is not injected, but the scrpit does not return any error code: ubuntu@zookeeper:/var/log$ sudo mv /etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/ ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/ ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 recv failed ubuntu@zookeeper:/var/log$ echo $? 0 Trying to inject key while setting the http_proxy environment variable works better: ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ apt-add-repository ppa:juju/pkgs --yes gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK ubuntu@zookeeper:/var/log$ echo $? 0 On the zookeeper node, python-software-properties is version 0.82.7.3 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Wed Dec 12 14:40:21 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime
I had the same problem. Sunk over a day into trying to figure it out. I'm taking no chances: I removed evolution. I might reinstall it sometime when I am no under such a crunch. What I find really frustrating is that I would expect the OOM (Out of Memory) killer to recognize that the process had consumed 14 GBytes of virtual memory and kill it, but it didn't. I would argue that if a user space process that can bring a system to its knees, then there is something else wrong with the system. I don't know enough about kernel internals to put my finger on it, and I am in a bit of time crunch right now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
YEAH!!! Finally Fixed!!! I just tested the bluez proposed update and my headphones connected in A2DP mode the first time (without having to go through all the tricks of connecting/disconnecting bluetooth, etc, etc). I did try powering off and on my headphones several times and it continues to work as expected. I'm a "good-to-go" for this fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860622] Re: Dependency error installing pulseaudio-esound-compat
Do you know when 1:11.1-1ubuntu7.5 will be re-released? My update Ubuntu installation has the last version installed on Nov 22, 2019. Also, my apt package manager doesn't seem to know about "withdrawals" so the rest of my pulseaudio files remain from 1:11.1-1ubuntu7.5 BTW, I was able to install pulseaudio-esound-compate 11.1-1ubuntu7.5 manually from the site you linked above so your diagnosis seems right. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: Fix Committed Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860622] [NEW] Dependency error installing pulseaudio-esound-compat
Public bug reported: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1860622 Title: Dependency error installing pulseaudio-esound-compat Status in pulseaudio package in Ubuntu: New Bug description: Running: apt-get install pulseaudio-esound-compat I get the following error: The following packages have unmet dependencies: pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: pulseaudio (= 1:11.1-1ubuntu7.4) Seems like pulseaudio-esound-compat has not been updated for the latest package versions of libpulse0 and pulseaudio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837580] Re: memlock is not set
This is currently an issue in 19.10's systemd (version 242). By default,
unless services are configured to set LimitMEMLOCK, they will have 64k
as their memlock limit (though oddly, systemd bumped its own memlock
limit higher than previous versions have used). The only processes not
affected are those that increase their own memlock rlimits at runtime,
such as `systemd --user`.
```
# for pid in $(ps --ppid 1 | awk 'NR!=1 {print $1}'); do echo -n "${pid}: ";
cat "/proc/${pid}/limits" | grep locked ; done
400: Max locked memory 6553665536bytes
480: Max locked memory 6553665536bytes
514: Max locked memory 6553665536bytes
559: Max locked memory 6553665536bytes
561: Max locked memory 6553665536bytes
596: Max locked memory 6553665536bytes
657: Max locked memory 6553665536bytes
658: Max locked memory 6553665536bytes
659: Max locked memory 6553665536bytes
661: Max locked memory 6553665536bytes
662: Max locked memory 6553665536bytes
665: Max locked memory 6553665536bytes
681: Max locked memory 6553665536bytes
685: Max locked memory 6553665536bytes
688: Max locked memory 6553665536bytes
704: Max locked memory 6553665536bytes
710: Max locked memory 6553665536bytes
711: Max locked memory 6553665536bytes
732: Max locked memory 6553665536bytes
939: Max locked memory 6553665536bytes
6673: Max locked memory 67108864 67108864 bytes
7310: Max locked memory 6553665536bytes
# ps aux | grep 6673
root 6673 0.0 0.8 18132 8348 ?Ss 00:07 0:00
/lib/systemd/systemd --user
root 10442 0.0 0.0 8020 864 pts/2S+ 03:32 0:00 grep
--color=auto 6673
```
This includes sshd, but the forked (still `sshd`) children of sshd
appear to have their memlock limit increased. This results in direct
shell operations under sshd having realistic limits. However, processes
"kicked off" by an ssh shell session, but not actually originally
parented under them, will have the austere 64k memlock limit. This is
the case with docker (the ubuntu docker.io package) containers, as
containerd's systemd configuration
(/lib/systemd/system/containerd.service) does not set LimitMEMLOCK. And
it should not have to.
Per this thread
(https://twitter.com/ChaosDatumz/status/1198075570921394177), this is
causing problems for eBPF related functionality running under docker due
to the fact that the memlock limit is used to track eBPF maps and is
tracked on the user, which is an issue because root in a non-user
namespaced container is technically root on the outside, so on top of
this paltry memlock limit, existing host processes running as root are
counting towards the container's memlock limit. This likely has
cascading effects for anything eBPF-related that isn't being started by
a user's shell, but the user-based memlock accounting behavior will
likely cause other issues for anything running in a container that
performs such checks given that on a typical system, root host processes
may well already have more than 64k in locked kernel memory allocated. I
don't think the solution for this is just to special case containerd (or
docker.io) with a configuration, but to fix this at its heart, systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837580
Title:
memlock is not set
Status in systemd package in Ubuntu:
Confirmed
Status in systemd package in Debian:
New
Bug description:
I discovered this in relation to jack, which installs
/etc/security/limits.d/audio.conf, containing:
@audio - rtprio 95
@audio - memlockunlimited
For a user in the audio group:
$ulimit -l -r
max locked memory (kbytes, -l) 65536
real-time priority (-r) 95
So jack (run as user via qjackctl) reports:
ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate
memory)
but does not report that it cannot set real-time priority, which it
does if run by a user not in the audio group.
I also tried putting the line in /etc/security/limits.conf, and trying
a number rather than "unlimited", but it didn't
[Touch-packages] [Bug 1846543] [NEW] --massive-debug option produces very little debug messaging
Public bug reported: According to --help: -m, --massive-debug Print a lot of debug information to the command line Now, perhaps my understanding of the words "massive" and "debug" are flawed, but the output I get while trying to debug failure to add a PPA is neither massive, nor really debug level information: ubuntu@hogplum:~$ sudo add-apt-repository -m ppa:checkbox-dev/testing Cannot add PPA: 'ppa:~checkbox-dev/ubuntu/testing'. ERROR: '~checkbox-dev' user or team does not exist. The PPA most certainly exists: https://code.launchpad.net/~checkbox-dev/+archive/ubuntu/testing This message is the utterly useless messaging one gets when add-apt- repository cannot talk to something upstream, be it ppa.launchpad.net or keyserver.ubuntu.com, perhaps. Either way, "user or team does not exist" is factually wrong, and utterly unhelpful, and the level of messaging is in no way debug level messaging, nor is it massive. add-apt-repository should actually provide MASSIVE debug level logging when -m/--massive-debug is passed to it, explaining each and every action it takes from beginning to end. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-common 0.96.24.32.11 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 3 13:57:15 2019 InstallationDate: Installed on 2016-02-11 (1329 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1846543 Title: --massive-debug option produces very little debug messaging Status in software-properties package in Ubuntu: New Bug description: According to --help: -m, --massive-debug Print a lot of debug information to the command line Now, perhaps my understanding of the words "massive" and "debug" are flawed, but the output I get while trying to debug failure to add a PPA is neither massive, nor really debug level information: ubuntu@hogplum:~$ sudo add-apt-repository -m ppa:checkbox-dev/testing Cannot add PPA: 'ppa:~checkbox-dev/ubuntu/testing'. ERROR: '~checkbox-dev' user or team does not exist. The PPA most certainly exists: https://code.launchpad.net/~checkbox-dev/+archive/ubuntu/testing This message is the utterly useless messaging one gets when add-apt- repository cannot talk to something upstream, be it ppa.launchpad.net or keyserver.ubuntu.com, perhaps. Either way, "user or team does not exist" is factually wrong, and utterly unhelpful, and the level of messaging is in no way debug level messaging, nor is it massive. add-apt-repository should actually provide MASSIVE debug level logging when -m/--massive-debug is passed to it, explaining each and every action it takes from beginning to end. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-common 0.96.24.32.11 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 3 13:57:15 2019 InstallationDate: Installed on 2016-02-11 (1329 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1846543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 90085] Re: When /tmp is mounted noexec, preconfigure fails
On Ubuntu 18.04 with noexec on /tmp running 'apt-get install -y selinux' and then doing a required reboot will give you a non-booting host. As an aside, the same security guidance (CIS Benchmarks for one) about noexec on /tmp should be applied to /var/tmp, so changing APT::ExtractTemplates::TempDir to "/var/tmp"; isn't really an option here in the long run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/90085 Title: When /tmp is mounted noexec, preconfigure fails Status in debconf package in Ubuntu: Triaged Status in debconf package in Debian: Confirmed Bug description: Binary package hint: mysql-server /tmp mounted noexec, this ensues: Preconfiguring packages ... Can't exec "/tmp/mysql-server-5.0.config.89611": Permission denied at /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of /tmp/mysql-server-5.0.config.89611 configure failed at /usr/share/perl5/Debconf/ConfModule.pm line 57 mysql-server-5.0 failed to preconfigure, with exit status 2 ace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/90085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832292] Re: reboot reboots system when -h is passed
Also, yes, I get that this is a nit-pick and that there's a history there, this is more a wishlist thing because it's a usability issue. ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist -- 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/1832292 Title: reboot reboots system when -h is passed Status in systemd package in Ubuntu: New Bug description: -h is a fairly common shortcut for --help. reboot, however, reboots the machine when one issues the command: reboot -h Now looking at the man page, there is an entry for --halt and --help, but NOTHING for -h at all. reboot should return the same as --help when -h is passed, or at the very least it should error out and not reboot the system, instead perhaps dumping a message like "-h unknown argument". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jun 11 00:50:22 2019 InstallationDate: Installed on 2016-02-11 (1215 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832292] [NEW] reboot reboots system when -h is passed
Public bug reported: -h is a fairly common shortcut for --help. reboot, however, reboots the machine when one issues the command: reboot -h Now looking at the man page, there is an entry for --halt and --help, but NOTHING for -h at all. reboot should return the same as --help when -h is passed, or at the very least it should error out and not reboot the system, instead perhaps dumping a message like "-h unknown argument". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jun 11 00:50:22 2019 InstallationDate: Installed on 2016-02-11 (1215 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1832292 Title: reboot reboots system when -h is passed Status in systemd package in Ubuntu: New Bug description: -h is a fairly common shortcut for --help. reboot, however, reboots the machine when one issues the command: reboot -h Now looking at the man page, there is an entry for --halt and --help, but NOTHING for -h at all. reboot should return the same as --help when -h is passed, or at the very least it should error out and not reboot the system, instead perhaps dumping a message like "-h unknown argument". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jun 11 00:50:22 2019 InstallationDate: Installed on 2016-02-11 (1215 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824565] [NEW] I'm just trying to make my compouter more stable.
Public bug reported: My computer keeps changing. Sometimes my add ons on firefox are gone, and I have many programs I do not want on MY computer! I have very little control over my own property. Why can't I remove the programs I do not want, like the games and all the log files and analyzers and remote desktop crap I never downloaded.??? Microshaft does the same thing that is why I switched to linux. Are there any lenox programs that are private? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 12 10:21:46 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GF108M [GeForce GT 540M] [104d:9089] InstallationDate: Installed on 2019-03-15 (28 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Sony Corporation VPCF22SFX ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=0e73d203-aa1a-40f8-ab34-0abfb2d5d2e8 ro plymouth:debug vesafb.invalid=1 drm.debug=0xe nopat SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1190V3 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1190V3:bd09/05/2011:svnSonyCorporation:pnVPCF22SFX:pvrC609T4GV:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCF22SFX dmi.product.version: C609T4GV dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Apr 12 07:42:00 2019 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1824565 Title: I'm just trying to make my compouter more stable. Status in xorg package in Ubuntu: New Bug description: My computer keeps changing. Sometimes my add ons on firefox are gone, and I have many programs I do not want on MY computer! I have very little control over my own property. Why can't I remove the programs I do not want, like the games and all the log files and analyzers and remote desktop crap I never downloaded.??? Microshaft does the same thing that is why I switched to linux. Are there any lenox programs that are private? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7
Any update on this issue? ** Also affects: apport Importance: Undecided Status: New -- 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/1774843 Title: apport python exception handler messes up python3.7 Status in Apport: New Status in apport package in Ubuntu: Triaged Status in python-apt package in Ubuntu: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1774843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442775] Re: apt-get --ignore-missing doesn't ignore missing packages
Yes this affects me as well. Still true as of apt 1.6.6 (Ubuntu 18.04) -- 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/1442775 Title: apt-get --ignore-missing doesn't ignore missing packages Status in apt package in Ubuntu: Confirmed Bug description: The man page for apt-get states: -m, --ignore-missing, --fix-missing Ignore missing packages; if packages cannot be retrieved or fail the integrity check after retrieval (corrupted package files), hold back those packages and handle the result. Use of this option together with -f may produce an error in some situations. If a package is selected for installation (particularly if it is mentioned on the command line) and it could not be downloaded then it will be silently held back. Configuration Item: APT::Get::Fix-Missing. However, when removing or purging packages, it does /not/ actually ignore missing packages: build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo apt-get purge -y --ignore-missing zimbra-openssl-lib Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package zimbra-openssl-lib build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $? 100 This causes some pain when using apt-get in a Makefile and wanting to ensure custom packages have been removed. dpkg handles this correctly: build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo dpkg --purge zimbra-openssl-lib dpkg: warning: ignoring request to remove zimbra-openssl-lib which isn't installed build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $? 0 however you then lose dependency tracking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1442775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
I can confirm that the solution Florian posted (modifying /lib/udev/rules.d/97-hid2hci.rules) works for me as well. Dell Latitude E6500, Kubuntu 18.04 with hwe kernel (4.18.0-13-generic), udev/systemd version 237-3ubuntu10.9, bluez version 5.48-0ubuntu3.1 -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually
I have a Sony MDR-XB950N1 and I'm seeing the same thing -- 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/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: [SRU] [xenial] [bionic] autofs needs to be restarted to pick up some shares
The issue seems to have returned with an update in 16.04 in mid- november. I will continue to peruse the above solutions and see if there's anything I have not tried yet but so far no joy. OpenLDAP + autofs still requires a restart of autofs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: [SRU] [xenial] [bionic] autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Fix Released Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Status in autofs source package in Xenial: Incomplete Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774419] Re: easy_install command is missing
This affects me as well; there are a number of build tools and test environments I maintain and/or use which assume the availability of easy_install if python-setuptools is installed. Outside of this issue, the only helpful documentation I could find was on Stack Exchange: https://askubuntu.com/a/1052682/88829 The Bionic package even states (ref: https://launchpad.net/ubuntu/bionic/+source/python-setuptools): > The setuptools project also includes the widely used easy_install application for downloading and installing Python packages. ...which would seem to indicate easy_install should be available after installing the package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1774419 Title: easy_install command is missing Status in python-setuptools package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 Package: python-setuptools Version: 39.0.1-2 This package installs the easy_install module, but the command is missing: deploy@controller0:~$ which easy_install deploy@controller0:~$ echo $? 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1774419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
That fix is great, but not for those going through a new install of
18.04. I had to let the entire installation process finish before I
could do anything about those messages at all, and their are dozens of
them that go by. Given this is a new problem in this theme in 18.04 (at
least as far as I know) and was definitely not present in 16.04, the
issue should be addressed to avoid errors during installation of (or
upgrade to) 18.04. Your fix can't be made until one of those is done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
Confirmed
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
This same issue show up *many* times during the upgrade from 16.04 to
18.04.
Many times.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
Confirmed
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
Sorry, I'm not familiar with Ubuntu packaging. I see: ``` "cryptsetup" versions published in Ubuntu Cosmic (2:2.0.2-1ubuntu2): main/admin Bionic (2:2.0.2-1ubuntu1): main/admin ``` Out of curiosity, what needs to happen for this change to make it to Bionic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Won't Fix Status in cryptsetup package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Obviously I didn't just jump in and release a fix. I accidentally updated the status and can't set it back. Sorry folks. I didn't mean to get anyone excited about the fix being out. -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
I vote for changing it from "Low" to "Insanely broken and wrong". Even the workaround to set DNS in resolved.conf is still wrong. There is a reason that every dhcp server on earth is configured to provide a DNS server for a reason. Jeff Carr CEO WIT.COM Inc. Formerly co-founder Digital Ocean -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773007] [NEW] sntp return code is not EXIT_FAILURE when hostname query is not successful
Public bug reported: # sntp abc sntp 4.2.8p10@1.3728-o (1) kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory abc lookup error Temporary failure in name resolution echo $? 0 from the manpage for sntp: EXIT STATUS One of the following exit values will be returned: 0 (EXIT_SUCCESS) Successful program execution. 1 (EXIT_FAILURE) The operation failed or the command syntax was not valid. 66 (EX_NOINPUT) A specified configuration file could not be loaded. 70 (EX_SOFTWARE) libopts had an internal operational error. Please report it to auto‐ gen-us...@lists.sourceforge.net. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sntp 1:4.2.8p10+dfsg-5ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 19:53:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2018-05-23T19:24:22.724839 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- 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/1773007 Title: sntp return code is not EXIT_FAILURE when hostname query is not successful Status in ntp package in Ubuntu: New Bug description: # sntp abc sntp 4.2.8p10@1.3728-o (1) kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory abc lookup error Temporary failure in name resolution echo $? 0 from the manpage for sntp: EXIT STATUS One of the following exit values will be returned: 0 (EXIT_SUCCESS) Successful program execution. 1 (EXIT_FAILURE) The operation failed or the command syntax was not valid. 66 (EX_NOINPUT) A specified configuration file could not be loaded. 70 (EX_SOFTWARE) libopts had an internal operational error. Please report it to auto‐ gen-us...@lists.sourceforge.net. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sntp 1:4.2.8p10+dfsg-5ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 19:53:29 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2018-05-23T19:24:22.724839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1773007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772041] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 25
Public bug reported: Upugrading from Xubuntu 17.10 to 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri May 18 09:09:13 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 25 InstallationDate: Installed on 2016-03-04 (804 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 25 UpgradeStatus: Upgraded to bionic on 2018-05-18 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1772041 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 25 Status in ca-certificates package in Ubuntu: New Bug description: Upugrading from Xubuntu 17.10 to 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri May 18 09:09:13 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 25 InstallationDate: Installed on 2016-03-04 (804 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 25 UpgradeStatus: Upgraded to bionic on 2018-05-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1772041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762023] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1760128 *** https://bugs.launchpad.net/bugs/1760128 Public bug reported: Ubuntu Mate 16.04.4 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Apr 7 11:51:09 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-07-08 (638 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1762023 Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in avahi package in Ubuntu: New Bug description: Ubuntu Mate 16.04.4 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Apr 7 11:51:09 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-07-08 (638 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new 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/avahi/+bug/1762023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728093] Re: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices
I had a similar problem with my Dell Latitude 5289 using Ubuntu 17.10. After trying different things, I got it to work by using hdajackretask. I got a clue from norteo on this thread: https://askubuntu.com/questions/926590/headphone-not-working-on- ubuntu-17-04-dell-xps-15 To get it to work for my specific setup, I ran hdajackretask, checked the box to "show unconnected pins," selected "override" for pin 0x21, and set it to "Headphone." I did not override or adjust any of the other pins. I realize you're using a different version of Ubuntu, but I hope this might help you or someone else using a Dell Latitude 5289. -- 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/1728093 Title: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a fresh installation of Ubuntu 16.04 on a Dell Latitude 5289 Ultrabook that has a single 3.5mm jack for both input and output. This installation is in a dual-boot situation with Windows 10. This device has UEFI secure boot enabled. The combo jack works perfectly in Windows 10, however, when I plug in a headset or headphone of any kind, it does not register that anything has been plugged in. The laptop is connected to a Dell dock via USB-C, so there is also USB Audio (Output only) available on the dock, but that also does not work. It worked for one session yesterday on my dock at work, however it does not work at my dock that I have at home. The internal speakers and the microphone built into the lid work fine. The Combo jack also does not work disconnected from the dock. I have installed gnome and gnome-shell, but it does not work in either gnome or unity (I continue to use lightdm so that I can switch back and forth). Neither Unity nor Gnome bring up any kind of "What Did You Plug In" dialog. alsamixer does not have a headphone option as expected pavucontrol does not allow me to select "Headphones" under the Built- in Audio Analog Stereo Port I have attempted to tweak settings in hdajackretask to no success I have attempted to add: options snd_hda_intel model=dell-headset-multi(dell-headset-dock, generic, auto, headset-mic, etc) to no success I have also tried updating my kernel to 4.13.10, to no success. I also tried 17.10 to no success. Outputs: -- uname -sr Linux 4.10.0-37-generic -- aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [USB Audio], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [USB Audio], device 1: USB Audio [USB Audio #1] Subdevices: 1/1 Subdevice #0: subdevice #0 cat /proc/asound/car*/co* | grep Codec Codec: Realtek ALC3253 Codec: Intel Kabylake HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1728093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752430] [NEW] tracker-miner-apps fails when /usr/local/share/applications is a link
Public bug reported: /usr/local/share/applications is a symbolic link on one of my systems because I am using xstow to manage packages in /usr/local. There are valid .desktop files within this linked directory, however. tracker-miner-apps cannot parse this file/link/directory, so it keeps trying forever with high CPU usage, and spewing error messages to syslog. Feb 28 12:55:25 gallium gnome-session[30827]: (tracker-miner-apps:30995): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/local/share/applications': 'Couldn't load desktop file:'/usr/local/share/applications'' Feb 28 12:55:25 gallium gnome-session[30827]: message repeated 40 times: [ (tracker-miner-apps:30995): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/local/share/applications': 'Couldn't load desktop file:'/usr/local/share/applications''] I worked around the problem by making /usr/local/share/applications and directory containing symbolic links to .desktop files within the stowed packages. This is what it looks like now: jeffrey@gallium:/usr/local/share/applications$ ls -l total 20 -rw-r--r-- 1 root root 13 Feb 25 20:27 mimeinfo.cache lrwxrwxrwx 1 root root 61 Feb 28 13:14 thinlinc-setup.desktop -> ../../stow/thinlinc/share/applications/thinlinc-setup.desktop lrwxrwxrwx 1 root root 65 Feb 28 13:14 thinlinc-webaccess.desktop -> ../../stow/thinlinc/share/applications/thinlinc-webaccess.desktop lrwxrwxrwx 1 root root 62 Feb 28 13:14 thinlinc-webadm.desktop -> ../../stow/thinlinc/share/applications/thinlinc-webadm.desktop lrwxrwxrwx 1 root root 75 Feb 28 13:12 vncviewer.desktop -> ../../stow/tigervnc-Linux-x86_64-1.6.0/share/applications/vncviewer.desktop After this change tracker-miner-apps seems to be happy. More generally, it's bad and wrong that an indexer can peg the CPU when it has a bug. It should limit rescan attempts to a certain number and then put them on a queue to check infrequently. Would it be just as aggressive if I created a bad .desktop file? An indexer should be as tolerant as possible of bad files, IMO. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker-miner-fs 1.6.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Feb 28 13:26:36 2018 InstallationDate: Installed on 2015-11-19 (832 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) JournalErrors: -- No entries -- ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: tracker UpgradeStatus: Upgraded to xenial on 2016-09-17 (528 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1752430 Title: tracker-miner-apps fails when /usr/local/share/applications is a link Status in tracker package in Ubuntu: New Bug description: /usr/local/share/applications is a symbolic link on one of my systems because I am using xstow to manage packages in /usr/local. There are valid .desktop files within this linked directory, however. tracker-miner-apps cannot parse this file/link/directory, so it keeps trying forever with high CPU usage, and spewing error messages to syslog. Feb 28 12:55:25 gallium gnome-session[30827]: (tracker-miner-apps:30995): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/local/share/applications': 'Couldn't load desktop file:'/usr/local/share/applications'' Feb 28 12:55:25 gallium gnome-session[30827]: message repeated 40 times: [ (tracker-miner-apps:30995): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/local/share/applications': 'Couldn't load desktop file:'/usr/local/share/applications''] I worked around the problem by making /usr/local/share/applications and directory containing symbolic links to .desktop files within the stowed packages. This is what it looks like now: jeffrey@gallium:/usr/local/share/applications$ ls -l total 20 -rw-r--r-- 1 root root 13 Feb 25 20:27 mimeinfo.cache lrwxrwxrwx 1 root root 61 Feb 28 13:14 thinlinc-setup.desktop -> ../../stow/thinlinc/share/applications/thinlinc-setup.desktop lrwxrwxrwx 1 root root 65 Feb 28 13:14 thinlinc-webaccess.desktop -> ../../stow/thinlinc/share/applications/thinlinc-webaccess.desktop lrwxrwxrwx 1 root root 62 Feb 28 13:14 thinlinc-webadm.desktop -> ../../stow/thinlinc/share/applications/thinlinc-webadm.desktop lrwxrwxrwx 1 root root 75 Feb 28 13:12 vncviewer.desktop -> ../../stow/tigervnc-Linux-x86_64-1.6.0/share/applications/vncviewer.desktop After this change tracker-miner-apps seems to be happy. More generally, it's bad and wrong that an indexer can peg the CPU when
[Touch-packages] [Bug 1749774] [NEW] include fwupd packages in Server Seed
Public bug reported: fwupd is the closest we have to a standard mechanism currently for doing in-band firmware updates in a vendor agnostic way. As long as the vendors provide firmware blobs in an appropriately formatted package, fwupd (or fwupdate) can install those firmware blobs from within Ubuntu. Because of this, we should include the related packages in the server seed. The main components all live in Main currently. As far as I can tell (verified on a Bionic install), nothing in the current server seed pulls in fwupd, fwupdate, or fwupdate-signed as a dependency. ubuntu@xwing:~$ apt-cache policy fwup* fwupdate: Installed: (none) Candidate: 10-2 Version table: 10-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages fwupd: Installed: (none) Candidate: 1.0.4-3build1 Version table: 1.0.4-3build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages fwupdate-signed: Installed: (none) Candidate: 1.17+10-2 Version table: 1.17+10-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: hwcert-server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1749774 Title: include fwupd packages in Server Seed Status in ubuntu-meta package in Ubuntu: New Bug description: fwupd is the closest we have to a standard mechanism currently for doing in-band firmware updates in a vendor agnostic way. As long as the vendors provide firmware blobs in an appropriately formatted package, fwupd (or fwupdate) can install those firmware blobs from within Ubuntu. Because of this, we should include the related packages in the server seed. The main components all live in Main currently. As far as I can tell (verified on a Bionic install), nothing in the current server seed pulls in fwupd, fwupdate, or fwupdate-signed as a dependency. ubuntu@xwing:~$ apt-cache policy fwup* fwupdate: Installed: (none) Candidate: 10-2 Version table: 10-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages fwupd: Installed: (none) Candidate: 1.0.4-3build1 Version table: 1.0.4-3build1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages fwupdate-signed: Installed: (none) Candidate: 1.17+10-2 Version table: 1.17+10-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1749774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746582] [NEW] package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: I *think* this was from trying to install python-guestfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Wed Jan 31 09:56:36 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-28 (217 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1746582 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: I *think* this was from trying to install python-guestfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Wed Jan 31 09:56:36 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-28 (217 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1746582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook
Logged at https://github.com/sickill/stderred/issues/63 ** Bug watch added: github.com/sickill/stderred/issues #63 https://github.com/sickill/stderred/issues/63 -- 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/1729836 Title: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After running 'update-initramfs -u -k $(uname -r)', Linux will not boot. With 'quiet splash' set in grub, it appears to freeze after the 'Loading ramdisk...' message, and if booted in recovery mode, I see the following kernel panic: Freeing unused kernel memory: 948k Freeing unused kernel memory: 104K x86/mm: Chcked W+X mappings: passed, no W+X pages found. Failed to execute /init (error -2) Kernel panic - not syncing: No working init found. Try passing init= optin to kernel. See Linux Documentation/admin-guide/init.rst for guidance. CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011 Call Trace: dump_stack+0x63/0x8b ? rest_init+0xb0/0xc0 panic+0xe4/0x23d ? putname+0x4b/0x50 ? rest_init+0xc0/0xc0 kernel_init+0xeb/0xfc ret_from_fork0x25/0x30 Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 0x8000-0xbfff) ---[ end Kernel panic - no syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. (full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2). Examining the initrd files, here is a good one, as installed by the Ubuntu 17.10 installer: # file /boot/initrd.img-4.13.0-16-generic /boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC) # ls -la /boot/initrd.img-4.13.0-16-generic -rw-r--r-- 1 root root 50764087 Nov 3 21:02 /boot/initrd.img-4.13.0-16-generic and here is the file after 'update-initramfs -u -k 4.13.0-16-generic': # file /boot/initrd.img-4.13.0-16-generic /boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu Nov 2 10:51:42 2017, from Unix root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic -rw-r--r-- 1 root root 50895514 Nov 3 21:01 /boot/initrd.img-4.13.0-16-generic Good and bad initrds can be downloaded from https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing After downloading initrd.img-4.13.0-16-generic-broken, the panic can be replicated in qemu with: kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd /boot/initrd.img-4.13.0-16-generic-broken (tip obtained from https://lists.debian.org/debian- kernel/2016/02/msg00323.html) I've experienced this problem with Ubuntu 17.04 and 17.10 on two separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially, until one day I update the kernel or something, and a .deb postinst script calls update-initramfs and trashes that kernel's initrd file. If I run 'update-initramfs -u -k all', all my old initrd files are toast. The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is strange. I'm not getting many google hits on it. None of my other Ubuntu/Debian servers use that format in their initrds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Nov 3 21:33:12 2017 InstallationDate: Installed on 2017-08-05 (90 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to artful on 2017-10-24 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1729836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook
I think I figured out the cause. Basically PEBCAK.. There's a program called stderred (https://github.com/sickill/stderred) which colorizes stderr to differentiate it from stdout, via a LD_PRELOAD hook. I have had this set for years in my ~/.bashrc: root@jturner-home:~# echo $LD_PRELOAD /home/jturner/src/github/stderred/build/libstderred.so When I examine the initrd file as follows, I see half the binaries in bin/ contain ANSI escape codes, and the libstderred.so library has been pulled in: root@jturner-home:/boot# update-initramfs -u -k 4.13.0-25-generic update-initramfs: Generating /boot/initrd.img-4.13.0-25-generic root@jturner-home:/boot# mkdir bad root@jturner-home:/boot# ( cd bad; zcat ../initrd.img-4.13.0-25-generic | cpio -idmv; ) root@jturner-home:/boot# ls bad/home/jturner/src/github/stderred/build/libstderred.so bad/home/jturner/src/github/stderred/build/libstderred.so root@jturner-home:/boot# ls -1 bad/bin ?[0m ?[0m?[1m?[31m[[?[0m?[1m?[31m ?[0m?[1m?[31macpid?[0m?[1m?[31m ?[0m?[1m?[31mash?[0m?[1m?[31m ?[0m?[1m?[31mawk?[0m?[1m?[31m ?[0m?[1m?[31mbasename?[0m?[1m?[31m ?[0m?[1m?[31mblockdev?[0m?[1m?[31m ?[0m?[1m?[31mcat?[0m?[1m?[31m ... ?[1m?[31m[?[0m?[1m?[31m busybox cat chroot cpio dash date dd ... The output of update-initramfs goes red halfway. Perhaps update-initramfs could sanitize its environment, or explicitly unset LD_PRELOAD. Hard to be idiot-proof when there's such sophisticated idiots :) -- 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/1729836 Title: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After running 'update-initramfs -u -k $(uname -r)', Linux will not boot. With 'quiet splash' set in grub, it appears to freeze after the 'Loading ramdisk...' message, and if booted in recovery mode, I see the following kernel panic: Freeing unused kernel memory: 948k Freeing unused kernel memory: 104K x86/mm: Chcked W+X mappings: passed, no W+X pages found. Failed to execute /init (error -2) Kernel panic - not syncing: No working init found. Try passing init= optin to kernel. See Linux Documentation/admin-guide/init.rst for guidance. CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011 Call Trace: dump_stack+0x63/0x8b ? rest_init+0xb0/0xc0 panic+0xe4/0x23d ? putname+0x4b/0x50 ? rest_init+0xc0/0xc0 kernel_init+0xeb/0xfc ret_from_fork0x25/0x30 Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 0x8000-0xbfff) ---[ end Kernel panic - no syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. (full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2). Examining the initrd files, here is a good one, as installed by the Ubuntu 17.10 installer: # file /boot/initrd.img-4.13.0-16-generic /boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC) # ls -la /boot/initrd.img-4.13.0-16-generic -rw-r--r-- 1 root root 50764087 Nov 3 21:02 /boot/initrd.img-4.13.0-16-generic and here is the file after 'update-initramfs -u -k 4.13.0-16-generic': # file /boot/initrd.img-4.13.0-16-generic /boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu Nov 2 10:51:42 2017, from Unix root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic -rw-r--r-- 1 root root 50895514 Nov 3 21:01 /boot/initrd.img-4.13.0-16-generic Good and bad initrds can be downloaded from https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing After downloading initrd.img-4.13.0-16-generic-broken, the panic can be replicated in qemu with: kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd /boot/initrd.img-4.13.0-16-generic-broken (tip obtained from https://lists.debian.org/debian- kernel/2016/02/msg00323.html) I've experienced this problem with Ubuntu 17.04 and 17.10 on two separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially, until one day I update the kernel or something, and a .deb postinst script calls update-initramfs and trashes that kernel's initrd file. If I run 'update-initramfs -u -k all', all my old initrd files are toast. The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is strange. I'm not getting many google hits on it. None of my other Ubuntu/Debian servers use that format in their initrds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64
[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files
Sure, I've attached update-initramfs -v output, and confirmed that the generated initrd is unusable, both with kvm and a real computer. ** Attachment added: "Output of 'update-initramfs -v' that generates an unusable initrd." https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1729836/+attachment/5039270/+files/update-initramfs-output.txt ** Summary changed: - update-initramfs generating unbootable initrd files + update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook -- 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/1729836 Title: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook Status in initramfs-tools package in Ubuntu: Incomplete Bug description: After running 'update-initramfs -u -k $(uname -r)', Linux will not boot. With 'quiet splash' set in grub, it appears to freeze after the 'Loading ramdisk...' message, and if booted in recovery mode, I see the following kernel panic: Freeing unused kernel memory: 948k Freeing unused kernel memory: 104K x86/mm: Chcked W+X mappings: passed, no W+X pages found. Failed to execute /init (error -2) Kernel panic - not syncing: No working init found. Try passing init= optin to kernel. See Linux Documentation/admin-guide/init.rst for guidance. CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011 Call Trace: dump_stack+0x63/0x8b ? rest_init+0xb0/0xc0 panic+0xe4/0x23d ? putname+0x4b/0x50 ? rest_init+0xc0/0xc0 kernel_init+0xeb/0xfc ret_from_fork0x25/0x30 Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 0x8000-0xbfff) ---[ end Kernel panic - no syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. (full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2). Examining the initrd files, here is a good one, as installed by the Ubuntu 17.10 installer: # file /boot/initrd.img-4.13.0-16-generic /boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC) # ls -la /boot/initrd.img-4.13.0-16-generic -rw-r--r-- 1 root root 50764087 Nov 3 21:02 /boot/initrd.img-4.13.0-16-generic and here is the file after 'update-initramfs -u -k 4.13.0-16-generic': # file /boot/initrd.img-4.13.0-16-generic /boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu Nov 2 10:51:42 2017, from Unix root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic -rw-r--r-- 1 root root 50895514 Nov 3 21:01 /boot/initrd.img-4.13.0-16-generic Good and bad initrds can be downloaded from https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing After downloading initrd.img-4.13.0-16-generic-broken, the panic can be replicated in qemu with: kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd /boot/initrd.img-4.13.0-16-generic-broken (tip obtained from https://lists.debian.org/debian- kernel/2016/02/msg00323.html) I've experienced this problem with Ubuntu 17.04 and 17.10 on two separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially, until one day I update the kernel or something, and a .deb postinst script calls update-initramfs and trashes that kernel's initrd file. If I run 'update-initramfs -u -k all', all my old initrd files are toast. The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is strange. I'm not getting many google hits on it. None of my other Ubuntu/Debian servers use that format in their initrds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Nov 3 21:33:12 2017 InstallationDate: Installed on 2017-08-05 (90 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to artful on 2017-10-24 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1729836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743873] [NEW] rsync version for xenial
Public bug reported: Any chance that rsync could be updated to 3.1.2 for xenial? The --backup-dir option in 3.1.1 doesn't work properly - it creates empty directories even when no files need to be put in them. Thanks, -Jeff ** Affects: rsync (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1743873 Title: rsync version for xenial Status in rsync package in Ubuntu: New Bug description: Any chance that rsync could be updated to 3.1.2 for xenial? The --backup-dir option in 3.1.1 doesn't work properly - it creates empty directories even when no files need to be put in them. Thanks, -Jeff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1743873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434986] Re: Not working network connection after boot
All, Is anyone working on this considering this issue is marked critical? -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729836] [NEW] update-initramfs generating unbootable initrd files
Public bug reported: After running 'update-initramfs -u -k $(uname -r)', Linux will not boot. With 'quiet splash' set in grub, it appears to freeze after the 'Loading ramdisk...' message, and if booted in recovery mode, I see the following kernel panic: Freeing unused kernel memory: 948k Freeing unused kernel memory: 104K x86/mm: Chcked W+X mappings: passed, no W+X pages found. Failed to execute /init (error -2) Kernel panic - not syncing: No working init found. Try passing init= optin to kernel. See Linux Documentation/admin-guide/init.rst for guidance. CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011 Call Trace: dump_stack+0x63/0x8b ? rest_init+0xb0/0xc0 panic+0xe4/0x23d ? putname+0x4b/0x50 ? rest_init+0xc0/0xc0 kernel_init+0xeb/0xfc ret_from_fork0x25/0x30 Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 0x8000-0xbfff) ---[ end Kernel panic - no syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. (full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2). Examining the initrd files, here is a good one, as installed by the Ubuntu 17.10 installer: # file /boot/initrd.img-4.13.0-16-generic /boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC) # ls -la /boot/initrd.img-4.13.0-16-generic -rw-r--r-- 1 root root 50764087 Nov 3 21:02 /boot/initrd.img-4.13.0-16-generic and here is the file after 'update-initramfs -u -k 4.13.0-16-generic': # file /boot/initrd.img-4.13.0-16-generic /boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu Nov 2 10:51:42 2017, from Unix root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic -rw-r--r-- 1 root root 50895514 Nov 3 21:01 /boot/initrd.img-4.13.0-16-generic Good and bad initrds can be downloaded from https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing After downloading initrd.img-4.13.0-16-generic-broken, the panic can be replicated in qemu with: kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd /boot/initrd.img-4.13.0-16-generic-broken (tip obtained from https://lists.debian.org/debian- kernel/2016/02/msg00323.html) I've experienced this problem with Ubuntu 17.04 and 17.10 on two separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially, until one day I update the kernel or something, and a .deb postinst script calls update-initramfs and trashes that kernel's initrd file. If I run 'update-initramfs -u -k all', all my old initrd files are toast. The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is strange. I'm not getting many google hits on it. None of my other Ubuntu/Debian servers use that format in their initrds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Nov 3 21:33:12 2017 InstallationDate: Installed on 2017-08-05 (90 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to artful on 2017-10-24 (10 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1729836 Title: update-initramfs generating unbootable initrd files Status in initramfs-tools package in Ubuntu: New Bug description: After running 'update-initramfs -u -k $(uname -r)', Linux will not boot. With 'quiet splash' set in grub, it appears to freeze after the 'Loading ramdisk...' message, and if booted in recovery mode, I see the following kernel panic: Freeing unused kernel memory: 948k Freeing unused kernel memory: 104K x86/mm: Chcked W+X mappings: passed, no W+X pages found. Failed to execute /init (error -2) Kernel panic - not syncing: No working init found. Try passing init= optin to kernel. See Linux Documentation/admin-guide/init.rst for guidance. CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011 Call Trace: dump_stack+0x63/0x8b ? rest_init+0xb0/0xc0 panic+0xe4/0x23d ? putname+0x4b/0x50 ? rest_init+0xc0/0xc0 kernel_init+0xeb/0xfc ret_from_fork0x25/0x30 Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 0x8000-0xbfff) ---[ end Kernel panic - no syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. (full screenshot at
[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address
Confirmed to resolve issue seen here. I won't be concerned if you prefer alternate sh-script formatting over mine. ** Patch added: "Patch to detect no link-local address" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1718568/+attachment/4954114/+files/dhclient-script.diff ** Description changed: Summary: If a interface does not yet have a link-local address (as it may have just been brought up), dhclient -6 will fail. The built-in "wait for link-local address" loop does not function properly, causing DHCP failure. Discussion: === In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on Ubuntu 17.04, I was finding that on boot I was getting failures with the logged message "no link-local IPv6 address for " I found that it took several seconds for the link-local address to be assigned when the interface came up (in this case, the ISP/modem-facing interface), and worked around it with a script that looks at /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20' and loops for a fixed number of times for that to be successful. On looking at /sbin/dhclient-script it appears that it *tries* to do the same thing in # set the link up and wait for ipv6 link local dad to finish ipv6_link_up_and_dad() this code sets out=$(ip -6 -o address show dev "$dev" scope link) then checks it with a case statement inside of a loop for case " $out " in *\ dadfailed\ *) error "$dev: ipv6 dad failed." return 1;; *\ tentative\ *) :;; *) return 0;; esac If there is no link-local address, $out will be empty. The default case is taken, and the loop exits immediately: $ echo "'$out'" ; case " $out " in > *\ dadfailed\ *) > echo "dadfailed" > ;; > *\ tentative\ *) > echo "tentative" > ;; > *) > echo "default" > esac '' default As a result, there is no "wait for link-local address" and when there is no link-local address, dhclient fails later on. Possible Fix: = Adding "the missing case" for "no address" case that continues the loop is one possible solution. - case " $out " in - *\ dadfailed\ *) - error "$dev: ipv6 dad failed." - return 1;; - *\ tentative\ *) :;; - " ") - : - ;; - *) return 0;; - esac + .case " $out " in + .*\ dadfailed\ *) + .error "$dev: ipv6 dad failed." + .return 1;; + .*\ tentative\ *) :;; + + " ") + + : + + ;; + .*) return 0;; + .esac At least in my situation, this prevents the failure of dhclient due to the link-local address not being "ready" yet. -- 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/1718568 Title: dhclient-script fails to wait for link-local address Status in isc-dhcp package in Ubuntu: New Status in isc-dhcp package in Debian: Unknown Bug description: Summary: If a interface does not yet have a link-local address (as it may have just been brought up), dhclient -6 will fail. The built-in "wait for link-local address" loop does not function properly, causing DHCP failure. Discussion: === In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on Ubuntu 17.04, I was finding that on boot I was getting failures with the logged message "no link-local IPv6 address for " I found that it took several seconds for the link-local address to be assigned when the interface came up (in this case, the ISP/modem- facing interface), and worked around it with a script that looks at /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20' and loops for a fixed number of times for that to be successful. On looking at /sbin/dhclient-script it appears that it *tries* to do the same thing in # set the link up and wait for ipv6 link local dad to finish ipv6_link_up_and_dad() this code sets out=$(ip -6 -o address show dev "$dev" scope link) then checks it with a case statement inside of a loop for case " $out " in *\ dadfailed\ *) error "$dev: ipv6 dad failed." return 1;; *\ tentative\ *) :;; *) return 0;; esac If there is no link-local address, $out will be empty. The default case is taken, and the loop exits immediately: $ echo "'$out'" ; case " $out " in > *\ dadfailed\ *) > echo "dadfailed" > ;; > *\ tentative\ *) > echo "tentative" > ;; > *)
[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)
This does *not* appear to resolve a closely related problem where the link-local address has not yet been assigned. See LP: 1718568 In brief, the loop case " $out " in *\ dadfailed\ *) error "$dev: ipv6 dad failed." return 1;; *\ tentative\ *) :;; *) return 0;; esac exits with 'return 0' with the lack of a link-local address as " " ($out empty) matches the default pattern as would a valid, link-local address. One possible solution is to add "the missing case" that matches $out being empty that performs the "wait and try again" action. -- 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/1633479 Title: dhclient does not wait for ipv6 dad (duplicate address detection) Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Precise: Fix Released Status in isc-dhcp source package in Trusty: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Status in isc-dhcp source package in Yakkety: Fix Released Bug description: dhclient -6 does not wait for an interface go through duplicate address detection. As a result the following will almost always fail: $ dev=eth0 $ ip link set down dev $dev $ dhclient -6 -1 -v eth0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. $ echo $? 1 Related bugs: * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign requested address * bug 1633562: 'dhclient -6 -S' does not bring interface up ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: isc-dhcp-client 4.3.3-5ubuntu15 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 09:18:52 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (449 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) SourcePackage: isc-dhcp 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/1633479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address
Confirmed that the same apparent flaw in dhclient-script appears to exist in 4.3.3-5ubuntu12.7 under Ubuntu 16.04.3 LTS This appears related to / caused by LP: #1633479 based on http://launchpadlibrarian.net/291516262/isc-dhcp_4.3.3-5ubuntu15_4.3.3-5ubuntu15.1.diff.gz ** Description changed: Summary: If a interface does not yet have a link-local address (as it may have just been brought up), dhclient -6 will fail. The built-in "wait for link-local address" loop does not function properly, causing DHCP failure. Discussion: === In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on Ubuntu 17.04, I was finding that on boot I was getting failures with the logged message "no link-local IPv6 address for " I found that it took several seconds for the link-local address to be assigned when the interface came up (in this case, the ISP/modem-facing interface), and worked around it with a script that looks at /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20' and loops for a fixed number of times for that to be successful. On looking at /sbin/dhclient-script it appears that it *tries* to do the same thing in # set the link up and wait for ipv6 link local dad to finish ipv6_link_up_and_dad() this code sets out=$(ip -6 -o address show dev "$dev" scope link) then checks it with a case statement inside of a loop for case " $out " in *\ dadfailed\ *) error "$dev: ipv6 dad failed." return 1;; *\ tentative\ *) :;; *) return 0;; esac If there is no link-local address, $out will be empty. The default case is taken, and the loop exits immediately: $ echo "'$out'" ; case " $out " in > *\ dadfailed\ *) > echo "dadfailed" > ;; > *\ tentative\ *) > echo "tentative" > ;; > *) > echo "default" > esac '' default As a result, there is no "wait for link-local address" and when there is no link-local address, dhclient fails later on. Possible Fix: = Adding "the missing case" for "no address" case that continues the loop is one possible solution. case " $out " in *\ dadfailed\ *) error "$dev: ipv6 dad failed." return 1;; *\ tentative\ *) :;; - " ") - : - ;; + " ") + : + ;; *) return 0;; esac At least in my situation, this prevents the failure of dhclient due to the link-local address not being "ready" yet. -- 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/1718568 Title: dhclient-script fails to wait for link-local address Status in isc-dhcp package in Ubuntu: New Status in isc-dhcp package in Debian: Unknown Bug description: Summary: If a interface does not yet have a link-local address (as it may have just been brought up), dhclient -6 will fail. The built-in "wait for link-local address" loop does not function properly, causing DHCP failure. Discussion: === In trying to configure isc-dhcp-client 4.3.5-3ubuntu1 for IPv6 on Ubuntu 17.04, I was finding that on boot I was getting failures with the logged message "no link-local IPv6 address for " I found that it took several seconds for the link-local address to be assigned when the interface came up (in this case, the ISP/modem- facing interface), and worked around it with a script that looks at /sbin/ifconfig $IFACE | /bin/fgrep -q 'scopeid 0x20' and loops for a fixed number of times for that to be successful. On looking at /sbin/dhclient-script it appears that it *tries* to do the same thing in # set the link up and wait for ipv6 link local dad to finish ipv6_link_up_and_dad() this code sets out=$(ip -6 -o address show dev "$dev" scope link) then checks it with a case statement inside of a loop for case " $out " in *\ dadfailed\ *) error "$dev: ipv6 dad failed." return 1;; *\ tentative\ *) :;; *) return 0;; esac If there is no link-local address, $out will be empty. The default case is taken, and the loop exits immediately: $ echo "'$out'" ; case " $out " in > *\ dadfailed\ *) > echo "dadfailed" > ;; > *\ tentative\ *) > echo "tentative" > ;; > *) > echo "default" > esac '' default As a result, there is no "wait for link-local address" and when there is no link-local address, dhclient fails later on. Possible Fix: = Adding "the missing case" for "no address" case that continues
