[Touch-packages] [Bug 1930112] [NEW] Error When Shutting Down via GUI- Xubuntu 21.04
Public bug reported: I get an error when I try to shutdown via the GUI, screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 28 19:59:00 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Desktop) [1028:085a] InstallationDate: Installed on 2021-05-27 (1 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. OptiPlex 7060 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c7908293-5a44-4112-b804-867efc7801ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0NC2VH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd05/05/2021:br1.12:svnDellInc.:pnOptiPlex7060:pvr:rvnDellInc.:rn0NC2VH:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7060 dmi.product.sku: 085A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 ** Attachment added: "Screenshot_2021-05-28_20-04-08.png" https://bugs.launchpad.net/bugs/1930112/+attachment/5500947/+files/Screenshot_2021-05-28_20-04-08.png -- 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/1930112 Title: Error When Shutting Down via GUI- Xubuntu 21.04 Status in xorg package in Ubuntu: New Bug description: I get an error when I try to shutdown via the GUI, screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 28 19:59:00 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Desktop) [1028:085a] InstallationDate: Installed on 2021-05-27 (1 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. OptiPlex 7060 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c7908293-5a44-4112-b804-867efc7801ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0NC2VH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd05/05/2021:br1.12:svnDellInc.:pnOptiPlex7060:pvr:rvnDellInc.:rn0NC2VH:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7060 dmi.product.sku: 085A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage
[Touch-packages] [Bug 1930103] Re: isc-dhcp-server overwrites /etc/default/isc-dhcp-server during update
Hello Milan, I just tested an upgrade: Unpacking isc-dhcp-server (4.4.1-2.1ubuntu5.20.04.2) over (4.4.1-2.1ubuntu5) ... and my /etc/default/isc-dhcp-server modifications had been left in place. The maintainer scripts will create a new one if the file cannot be read: https://sources.debian.org/src/isc-dhcp/4.4.1-2.2/debian/isc-dhcp-server.postinst/#L33 (Debian sources, but Ubuntu's are very similar.) Is it possible your old /etc/default/isc-dhcp-server could not be read? Thanks -- 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/1930103 Title: isc-dhcp-server overwrites /etc/default/isc-dhcp-server during update Status in isc-dhcp package in Ubuntu: New Bug description: Today unattended upgrade of ISC DHCPD overwrite config file /etc/default/isc-dhcp-server and set wrong interface where daemon have to listen (eno2 instead of br0 as was set before update). I see no backup file of original config file so I had to investigate where the problem was. Update have to never overwrite config file and throw away previous version. /var/log/apt/history.log: Start-Date: 2021-05-28 06:17:41 Commandline: /usr/bin/unattended-upgrade Upgrade: isc-dhcp-server:amd64 (4.4.1-2.1ubuntu5, 4.4.1-2.1ubuntu5.20.04.2) End-Date: 2021-05-28 06:17:47 root@linux:~# ls -l /etc/default/isc-dhcp-server -rw-r--r-- 1 root root 629 May 28 06:17 /etc/default/isc-dhcp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1930103/+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 1785383] Re: missing EDNS0 record confuses systemd-resolved
marking incomplete for hirsute based on Brian's comment above.
** Changed in: systemd (Ubuntu Hirsute)
Status: In Progress => Incomplete
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in dnsmasq source package in Bionic:
Triaged
Status in systemd source package in Bionic:
In Progress
Status in dnsmasq source package in Focal:
Fix Released
Status in systemd source package in Focal:
In Progress
Status in dnsmasq source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
In Progress
Status in dnsmasq source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
Incomplete
Status in dnsmasq source package in Impish:
Fix Released
Status in systemd source package in Impish:
Triaged
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which there are no records, there can sometimes be a five
second hang in resolution.
[Fix]
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
[Test Case]
Simple-ish test case for bionic:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 --server=/test/ &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
More detailed test case for focal and later:
install dnsmasq on a bionic system and start it, listening to an
interface that is externally reachable, e.g. for a normal libvirt vm
with interface name 'ens3':
IFACE=ens3
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,1.2.3.4 --server=/test/
note that the '1.2.3.4' address doesn't matter, any addr is ok.
then setup a test system that can reach the dnsmasq system, and
configure networkd to use the dnsmasq server, e.g. using config like:
[Match]
Name=ens3
[Network]
DHCP=yes
DNS=DNSMASQ_IP_ADDRESS
Domains=test
[DHCPv4]
UseDNS=no
UseDomains=no
replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
dnsmasq is running, and replace 'ens3' with whatever the test system
interface name is. Then restart systemd-networkd, and test:
systemd-resolve --reset-server-features
systemd-resolve --flush-caches
host test.test
The lookup using 'host' should complete immediately;.
[Discussion]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1785383/+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 1664844] Re: No distinction between link-up and link-down interfaces
** Description changed: [Impact] Since very long, we had a feature request in netplan to determine the activation mode of a given network interface. We got requests to enable marking some interfaces as 'manual', meaning that networkd (or any other backend) would not control its state in any way, requiring the administrator to bring the interface up or down manually. The other request was to mark a interface as 'off', that is: forcing the network interface to always be down until the configuration option isn't changed. This was mainly requested for the networkd backend and requires the new feature of specifying ActivationPolicy= for interfaces, alongside the required netplan changes. This feature is present in systemd 248 - for netplan supported stable series we have decided to cherry-pick and backport this feature on top of current systemd. The networkd feature basically adds the following 5 ActivationPolicy modes: always-down, down, manual, up, always-up. For netplan purposes we only use 'always-down' and 'manual'. The netplan feature, hopefully landing as part of 0.103, is called 'activation-mode' and supports two values: 'manual' and 'off'. [Test Case] For the systemd part: * Bring up a VM test environment with either a dummy interface or an interface that can be safely manipulated. * Upgrade systemd to the -proposed version * For the target interface, create/modify the networkd configuration to include the ActivationPolicy= setting in [Link], for instance: [Match] Name=dummy0 [Network] Address=192.168.10.30/24 Gateway=192.168.10.1 [Link] ActivationPolicy=manual * Try all 5 combinations of ActivationPolicy values: always-down, down, manual, up, always-up - doing `sudo networkctl reload` everytime and checking if the interface behaves as expected. [Where problems could occur] The patchset modifies quite a lot of code in the networkd link handling code paths, so regressions could appear in how networkd manages links - maybe by suddenly certain interfaces not getting brought up as they were - before. + before. By code inspection, the implementation defaults to + ACTIVATION_POLICY_UP as the default, equivalent to the current behavior, + so this risk is small. --- [Original Description] [Old Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Old Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Old Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Status in netplan.io source package in Focal: New Status in systemd source package in Focal: New Status in netplan.io source
[Touch-packages] [Bug 1930103] [NEW] isc-dhcp-server overwrites /etc/default/isc-dhcp-server during update
Public bug reported: Today unattended upgrade of ISC DHCPD overwrite config file /etc/default /isc-dhcp-server and set wrong interface where daemon have to listen (eno2 instead of br0 as was set before update). I see no backup file of original config file so I had to investigate where the problem was. Update have to never overwrite config file and throw away previous version. /var/log/apt/history.log: Start-Date: 2021-05-28 06:17:41 Commandline: /usr/bin/unattended-upgrade Upgrade: isc-dhcp-server:amd64 (4.4.1-2.1ubuntu5, 4.4.1-2.1ubuntu5.20.04.2) End-Date: 2021-05-28 06:17:47 root@linux:~# ls -l /etc/default/isc-dhcp-server -rw-r--r-- 1 root root 629 May 28 06:17 /etc/default/isc-dhcp-server ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Description changed: Today unattended upgrade of ISC DHCPD overwrite config file /etc/default /isc-dhcp-server and set wrong interface where daemon have to listen (eno2 instead of br0 as was set before update). I see no backup file of original config file so I had to investigate where the problem was. Update have to never overwrite config file and throw away previous version. /var/log/apt/history.log: Start-Date: 2021-05-28 06:17:41 Commandline: /usr/bin/unattended-upgrade Upgrade: isc-dhcp-server:amd64 (4.4.1-2.1ubuntu5, 4.4.1-2.1ubuntu5.20.04.2) End-Date: 2021-05-28 06:17:47 + + root@linux:~# ls -l /etc/default/isc-dhcp-server + -rw-r--r-- 1 root root 629 May 28 06:17 /etc/default/isc-dhcp-server -- 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/1930103 Title: isc-dhcp-server overwrites /etc/default/isc-dhcp-server during update Status in isc-dhcp package in Ubuntu: New Bug description: Today unattended upgrade of ISC DHCPD overwrite config file /etc/default/isc-dhcp-server and set wrong interface where daemon have to listen (eno2 instead of br0 as was set before update). I see no backup file of original config file so I had to investigate where the problem was. Update have to never overwrite config file and throw away previous version. /var/log/apt/history.log: Start-Date: 2021-05-28 06:17:41 Commandline: /usr/bin/unattended-upgrade Upgrade: isc-dhcp-server:amd64 (4.4.1-2.1ubuntu5, 4.4.1-2.1ubuntu5.20.04.2) End-Date: 2021-05-28 06:17:47 root@linux:~# ls -l /etc/default/isc-dhcp-server -rw-r--r-- 1 root root 629 May 28 06:17 /etc/default/isc-dhcp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1930103/+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 1929758] Re: OpenSSH vulnerabilities
Great, thanks Ian. ** Package changed: ubuntu => openssh (Ubuntu) ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid ** Information type changed from Private Security to Public Security -- 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/1929758 Title: OpenSSH vulnerabilities Status in openssh package in Ubuntu: Invalid Bug description: Hi, I was using NMAP to scan my Ubuntu server and it listed some vulnerabilities in OpenSSH. It also came up with exploits against these vulnerabilities. On my home network, I have several computers that I use for various purposes; a Ubuntu 20.04 LTS computer and Kali Linux computer being the subject for this email. I wanted to test if I had any security issues on my Ubuntu computer so I was doing some scans on it from my Kali computer. I did a scan with NMAP and it produced some vulnerabilities in OpenSSH and what exploits to use. Here is some info on my computers and the NMAP command that I used: ~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal ─$ lsb_release -a No LSB modules are available. Distributor ID: Kali Description: Kali GNU/Linux Rolling Release: 2021.1 Codename: kali-rolling ~$ ssh -V OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 ~$ apt-cache policy ssh ssh: Installed: (none) Candidate: 1:8.2p1-4ubuntu0.2 Version table: 1:8.2p1-4ubuntu0.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:8.2p1-4 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages ─$ sudo nmap -sV --script vuln 192.168.0.10 Starting Nmap 7.91 ( https://nmap.org ) at 2021-05-26 17:26 PDT Pre-scan script results: | broadcast-avahi-dos: | Discovered hosts: | 224.0.0.251 | After NULL UDP avahi packet DoS (CVE-2011-1002). |_ Hosts are all up (not vulnerable). Nmap scan report for 192.168.0.10 Host is up (0.00017s latency). Not shown: 995 filtered ports PORTSTATE SERVICE VERSION 20/tcp closed ftp-data 21/tcp closed ftp 22/tcp open ssh OpenSSH 8.2p1 Ubuntu 4ubuntu0.2 (Ubuntu Linux; protocol 2.0) | vulners: | cpe:/a:openbsd:openssh:8.2p1: | EDB-ID:2101810.0 https://vulners.com/exploitdb/EDB-ID:21018 *EXPLOIT* | CVE-2001-0554 10.0https://vulners.com/cve/CVE-2001-0554 | CVE-2020-15778 6.8 https://vulners.com/cve/CVE-2020-15778 | CVE-2020-12062 5.0 https://vulners.com/cve/CVE-2020-12062 | CVE-2021-28041 4.6 https://vulners.com/cve/CVE-2021-28041 | MSF:ILITIES/OPENBSD-OPENSSH-CVE-2020-14145/ 4.3 https://vulners.com/metasploit/MSF:ILITIES/OPENBSD-OPENSSH-CVE-2020-14145/ *EXPLOIT* | MSF:ILITIES/HUAWEI-EULEROS-2_0_SP9-CVE-2020-14145/ 4.3 https://vulners.com/metasploit/MSF:ILITIES/HUAWEI-EULEROS-2_0_SP9-CVE-2020-14145/ *EXPLOIT* | MSF:ILITIES/HUAWEI-EULEROS-2_0_SP8-CVE-2020-14145/ 4.3 https://vulners.com/metasploit/MSF:ILITIES/HUAWEI-EULEROS-2_0_SP8-CVE-2020-14145/ *EXPLOIT* | MSF:ILITIES/HUAWEI-EULEROS-2_0_SP5-CVE-2020-14145/ 4.3 https://vulners.com/metasploit/MSF:ILITIES/HUAWEI-EULEROS-2_0_SP5-CVE-2020-14145/ *EXPLOIT* | MSF:ILITIES/F5-BIG-IP-CVE-2020-14145/ 4.3 https://vulners.com/metasploit/MSF:ILITIES/F5-BIG-IP-CVE-2020-14145/ *EXPLOIT* | CVE-2020-14145 4.3 https://vulners.com/cve/CVE-2020-14145 |_MSF:AUXILIARY/SCANNER/SSH/FORTINET_BACKDOOR/0.0 https://vulners.com/metasploit/MSF:AUXILIARY/SCANNER/SSH/FORTINET_BACKDOOR/ *EXPLOIT* 80/tcp open http Apache httpd |_http-csrf: Couldn't find any CSRF vulnerabilities. |_http-dombased-xss: Couldn't find any DOM based XSS. |_http-server-header: Apache |_http-stored-xss: Couldn't find any stored XSS vulnerabilities. 443/tcp open ssl/http Apache httpd |_http-csrf: Couldn't find any CSRF vulnerabilities. |_http-dombased-xss: Couldn't find any DOM based XSS. |_http-server-header: Apache |_http-stored-xss: Couldn't find any stored XSS vulnerabilities. |_sslv2-drown: MAC Address: 00:15:C5:F6:5D:94 (Dell) Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 80.86 seconds Thanks, Ian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1929758/+subscriptions --
[Touch-packages] [Bug 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
+ case EROFS:
+ ignore_failure = true;
+ xwarn(_("setting key \"%s\"%s"), outname,
(ignore_failure?_(", ignoring"):""));
+ break;
default:
xwarn(_("setting key \"%s\"%s"), outname,
(ignore_failure?_(", ignoring"):""));
break;
Instead of reproducing the xwarn() call, I believe this should be:
+ case EROFS:
+ ignore_failure = true;
default:
xwarn(_("setting key \"%s\"%s"), outname,
(ignore_failure?_(", ignoring"):""));
break;
I would prefer to see this reconciled before proceeding with the SRU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1903351
Title:
ignore_eacces and ignore_erofs patches don't work properly
Status in procps package in Ubuntu:
Fix Released
Status in procps source package in Focal:
In Progress
Status in procps source package in Groovy:
In Progress
Status in procps source package in Hirsute:
In Progress
Bug description:
The patches used to ignore errors in containers no longer work as of
3.3.16 due to upstream commit https://gitlab.com/procps-
ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932
The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not
WriteSetting
Both patches ignore the change that rc is no longer propagated up and instead
everything is trapped by:
if (!ignore_failure && errno != ENOENT)
rc = -1;
Versions affected: focal+
root@bfee89058713:/tmp# cat /etc/os-release
NAME="Ubuntu"
VERSION="20.10 (Groovy Gorilla)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.10"
VERSION_ID="20.10"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=groovy
UBUNTU_CODENAME=groovy
root@bfee89058713:/# dpkg -l procps
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-=--=
ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities
root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf
root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $?
sysctl: setting key "kernel.shmmax": Read-only file system
255
root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf
root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $?
sysctl: setting key "kernel.shmmax": Read-only file system
0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1928316] Re: package linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1928316 Title: package linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Unknown ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 13 11:26:52 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1928316/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
I've gone ahead and uploaded the patches for F, G and H. ** Also affects: procps (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: procps (Ubuntu Focal) Status: New => In Progress ** Changed in: procps (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: procps (Ubuntu Groovy) Status: New => In Progress ** Changed in: procps (Ubuntu Groovy) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: procps (Ubuntu Hirsute) Status: New => In Progress ** Changed in: procps (Ubuntu Hirsute) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: In Progress Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1785383] Re: missing EDNS0 record confuses systemd-resolved
The SRU of systemd for Hirsute (and all its accompanying bugs) looks
good to me, but I'd like to see this fix merged for Impish at least per
SRU policy.
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in dnsmasq source package in Bionic:
Triaged
Status in systemd source package in Bionic:
In Progress
Status in dnsmasq source package in Focal:
Fix Released
Status in systemd source package in Focal:
In Progress
Status in dnsmasq source package in Groovy:
Fix Released
Status in systemd source package in Groovy:
In Progress
Status in dnsmasq source package in Hirsute:
Fix Released
Status in systemd source package in Hirsute:
In Progress
Status in dnsmasq source package in Impish:
Fix Released
Status in systemd source package in Impish:
Triaged
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which there are no records, there can sometimes be a five
second hang in resolution.
[Fix]
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
[Test Case]
Simple-ish test case for bionic:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 --server=/test/ &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
More detailed test case for focal and later:
install dnsmasq on a bionic system and start it, listening to an
interface that is externally reachable, e.g. for a normal libvirt vm
with interface name 'ens3':
IFACE=ens3
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,1.2.3.4 --server=/test/
note that the '1.2.3.4' address doesn't matter, any addr is ok.
then setup a test system that can reach the dnsmasq system, and
configure networkd to use the dnsmasq server, e.g. using config like:
[Match]
Name=ens3
[Network]
DHCP=yes
DNS=DNSMASQ_IP_ADDRESS
Domains=test
[DHCPv4]
UseDNS=no
UseDomains=no
replace 'DNSMASQ_IP_ADDRESS' with the addr of the bionic system where
dnsmasq is running, and replace 'ens3' with whatever the test system
interface name is. Then restart systemd-networkd, and test:
systemd-resolve --reset-server-features
systemd-resolve --flush-caches
host test.test
The lookup using 'host' should complete immediately;.
[Discussion]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1785383/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Well. My installation of Ubuntu 20.04 is one week old + all the updates and it is still happening occasionally. I just did what I did a year ago and I can reproduce the bug again and again. See attachment for a screenshot I did a few minutes ago. ** Attachment added: "Screenshot from 2021-05-28 17-57-22.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5500920/+files/Screenshot%20from%202021-05-28%2017-57-22.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1930082] [NEW] systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F
Public bug reported: This is a scripted bug report about ADT failures while running systemd tests for linux-raspi/5.11.0-1009.10 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on Hirsute/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/s/systemd/20210528_100011_6f6f0@/log.gz Testing failed on Groovy/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/s/systemd/20210528_084522_9b779@/log.gz Testing failed on Focal/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/s/systemd/20210528_092727_7c33b@/log.gz ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - systemd/247.3-3ubuntu3 ADT test failure with linux-raspi/5.11.0-1009.10 + systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F ** Description changed: This is a scripted bug report about ADT failures while running systemd tests for linux-raspi/5.11.0-1009.10 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. - Testing failed on: - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/s/systemd/20210528_100011_6f6f0@/log.gz + Testing failed on Hirsute/raspi: + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/s/systemd/20210528_100011_6f6f0@/log.gz + + Testing failed on Groovy/raspi: + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/s/systemd/20210528_084522_9b779@/log.gz + + Testing failed on Focal/raspi: + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/s/systemd/20210528_092727_7c33b@/log.gz -- 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/1930082 Title: systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F Status in linux-raspi package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-raspi/5.11.0-1009.10 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on Hirsute/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/s/systemd/20210528_100011_6f6f0@/log.gz Testing failed on Groovy/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/s/systemd/20210528_084522_9b779@/log.gz Testing failed on Focal/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/s/systemd/20210528_092727_7c33b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1930082/+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 1920130] Re: System icons missing in kubuntu 21.04
As it turns out, this also needs a change in qtbase-opensource-src. Change in -gles is not enough: https://lists.debian.org/debian-devel/2021/05/msg00076.html https://lists.debian.org/debian-devel/2021/05/msg00150.html ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in qtbase-opensource-src package in Ubuntu: New Status in qtbase-opensource-src-gles package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Hirsute: New Status in qtbase-opensource-src-gles source package in Hirsute: New Status in qtbase-opensource-src-gles package in Debian: Fix Released Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/paul/.kde/share/config/kdeglobals QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25: QML ScrollBar: Bindi ng loop detected for property
[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping
Hi @Dan, No, the patch won't break anything in groovy. Thanks for help. -- 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/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1829665] Re: Network Manager and upower not starting, libhogweed error
Thank you for your bug report, is that still an issue in newer versions? ** Changed in: nettle (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1829665 Title: Network Manager and upower not starting, libhogweed error Status in nettle package in Ubuntu: Incomplete Bug description: After updating Lubuntu 18.10 to 19.04, NetworkManager and upower no longer start. After a bit of digging it shows the source to be libhogweed4 v3.4.1-1. The error is: relocation error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: symbol nettle_rsa_sec_decrypt version HOGWEED_4 not defined in file libhogweed.so.4 with link time reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1829665/+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 1925775] Re: SRU the current 3.36.1 stable update
Using 3.36.1-0ubuntu1 the account are working as expected ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1925775 Title: SRU the current 3.36.1 stable update Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some API documentation fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try adding online account in a GNOME session, ensure the service is correctly enabled in application, for example that a google accounts are picked up in gnome-calendar and evolution. * Regression potential The changes are in API documentation so nothing specific to check, if there is an issue it would be from a toolchain regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+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 1900008] Re: Sessions of screen does not keep running in background
Hi Gustavo, Thanks. Let us know when you've found sometime to do that. No rush, absolutely. Meanwhile I am working this bug as "Incomplete". Please set it back to "New" once you've reported your findings. Thanks! ** Changed in: screen (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/198 Title: Sessions of screen does not keep running in background Status in screen package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: In a new fresh installed 20.04, when I use screen command and close the terminal (not closing screen sesion), then I can't recover it with screen -x, since does not exist. I can only recover screen sesion if the original terminal running screen is not being closed. For some reason, this is closing screen session of that user: Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded. Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario. This does not happen in an upgraded system from 18.04 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+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 1925795] Re: SRU the current 0.20.4 stable update
The 0.20.4-0ubuntu1 update works as expected, accessing the keyring is working. Trying to open a protected pdf in evince the password is correctly stored and re-used after trying to open the document again. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1925795 Title: SRU the current 0.20.4 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1926843] Re: online accounts integration with fb isn't working
Confirmed that using 3.38.1-1ubuntu1.1 facebook isn't listed, other provides are still available and keep working ** Tags removed: verification-needed verification-needed-focal verification-needed-hirsute ** Tags added: verification-done verification-done-focal verification-done-hirsute -- 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/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Committed Status in gnome-online-accounts source package in Hirsute: Fix Committed Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1152187] Re: [MIR] systemd
Hello, > For the record, ack from the Ubuntu Security Team on promoting the > systemd-container binary from universe to main in bionic. Thank you, Steve! I'll work on doing the next steps. -- 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/1152187 Title: [MIR] systemd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Incomplete Bug description: * The package is in universe and built on all archs: https://launchpad.net/ubuntu/+source/systemd/44-10ubuntu1 * Rationale: - in a first step we want systemd-services promoted to replace ubuntu- system-services - We will also want to move from consolekit to logind soon (https://blueprints.launchpad.net/ubuntu/+spec/foundations-1303 -consolekit-logind-migration) - udev has been merged in the systemd source upstream so we will want to build it from there at some point as well we don't plan to use the systemd init system at this point * Security: there has been some security issues in the past http://secunia.com/advisories/search/?search=systemd http://secunia.com/advisories/48220/ http://secunia.com/advisories/48208/ http://secunia.com/advisories/48331/ Those are mostly logind issue and have been fixed upstream. Our current package is outdated but we do plan to update it before starting using logind. There should be no issue with the services * Quality: - there is no RC bug in debian: http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=systemd - there is no bug open in launchpad: https://launchpad.net/ubuntu/+source/systemd/+bugs - upstream is active and responsive to issues The desktop bugs team is subscribed to the package in launchpad, foundations/desktop will maintain the package and look to the bug reports regularly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1152187/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
The focal SRU has been reuploaded merging the fixes -- 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/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
Oh, I see now that you comment on the other bug, already I will merge the changes ** Changed in: pulseaudio (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: pulseaudio (Ubuntu) Status: In Progress => Fix Released -- 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/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1197712] Re: 0.9.8.0-0ubuntu13 is causing conf prompt
Closing since it's an old issue with no report in 8 years also not likely Mathieu is still working on it at this point ** Changed in: network-manager (Ubuntu) Status: Triaged => Invalid -- 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/1197712 Title: 0.9.8.0-0ubuntu13 is causing conf prompt Status in network-manager package in Ubuntu: Invalid Bug description: Got a conf promt. not sure why =) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197712/+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 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
Thanks for the work, there is already a SRU in the queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=pulseaudio Do you want to include your changes and do another upload since it hasn't been accepted yet or should we wait for the other SRU to clear out first? -- 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/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Merge proposal linked: https://code.launchpad.net/~os369510/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/403448 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
** Tags removed: verification-needed
--
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/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
Fix Released
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
Fix Committed
Status in apt source package in Hirsute:
Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
Fix Released
Bug description:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release
upgrader being unable to handle interrupts after it did the initial
update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(1)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see
"Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of
bionic although the upgrade has quit. With the version of ubuntu-
release-upgrader in -proposed you will not see the "Ctrl+C" message.
For your sources.list file to be restored you'll need the version of
apt from bionic-proposed installed before starting the upgrade.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
ubuntu-release-upgrader: The change is wrapping a bunch of code in a
try: except: block so if the indentation was off the pyflakes /
pycodestyle tests would fail but autopkgtest will catch that.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a
number of times earlier; just to *check* if the upgrade was on offer; but this
is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected
through an adequate pipe? Are you sitting with full batteries; better
a power supply?" would be convenient; since I am using my PC for
urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898026/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
@Timo, I guess you could get passed if adding "--oomable" ** Also affects: plainbox-provider-checkbox Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in Provider for Plainbox - Checkbox: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918855] Re: Xorg xserver got signal 6 to abort
I was able to reproduce it on my RKL, but the reason was bad RAM. After swapping it to another otherwise identical set, it works fine. The reproducer here was running 'stress-ng --stack 0' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918855] Re: Xorg xserver got signal 6 to abort
``` Mar 3 18:07:02 kernel: [ 4935.420223] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:07:16 kernel: [ 4949.440656] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:08:11 kernel: [ 5004.462545] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:09:14 kernel: [ 5066.643244] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 18:09:34 kernel: [ 5087.214632] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:26 kernel: [10538.987863] gnome-terminal- invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:28 kernel: [10541.043501] gnome-terminal- invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:45 kernel: [10558.082088] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:40:49 kernel: [10562.058290] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:14 kernel: [10586.699020] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:35 kernel: [10608.175575] gnome-shell invoked oom-killer: gfp_mask=0x0(), order=0, oom_score_adj=0 Mar 3 19:41:55 kernel: [10627.942562] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:41:55 kernel: [10628.294303] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:42:12 kernel: [10645.292252] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:42:43 kernel: [10675.670335] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:06 gnome-shell[1691]: GNOME Shell crashed with signal 6 Mar 3 19:43:15 kernel: [10708.155220] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:31 kernel: [10724.420148] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:32 kernel: [10725.336522] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:36 kernel: [10729.101114] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:43:44 kernel: [10737.358855] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:44:09 kernel: [10761.733283] gnome-shell invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:44:31 kernel: [10783.687545] pool-gnome-shel invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 Mar 3 19:45:23 /usr/lib/gdm3/gdm-x-session[1425]: (EE) Caught signal 6 (Aborted). Server aborting ``` Does not make sense to me, I don't think it's DM/WM issue but tool issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
[Touch-packages] [Bug 1929915] Re: "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt-sudo'")
If tried to access from 'Settings', `kdesu` is used instead of `lxqt- sudo` and application starts properly. Snap attached. ** Attachment added: "Screenshot at 2021-05-28 08-51-12.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1929915/+attachment/5500840/+files/Screenshot%20at%202021-05-28%2008-51-12.png -- 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/1929915 Title: "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt- sudo'") Status in software-properties package in Ubuntu: New Bug description: Release: Kubuntu Groovy (also affects focal, hirsute) SW, version: software-properties-qt, 0.99.3.1 (for groovy but also affects version on focal) How to reproduce: 1) Launch Discover. 2) Search for (or scroll to) 'software sources', select the 'Software Sources' from the search result. 3) Click on 'Launch'. Expected: The application launches, possibly asking for admin password. Actual: Does not launch (on groovy). On focal, launches with error (Snapshot attached). However, if we try to access software sources from 'Settings', it launches properly. When launched from terminal, it was seen that discover was trying to use `lxqt-sudo` and failing since it was not installed. Error message as below. `kf.kio.gui: "Could not find the program 'lxqt-sudo'"` Whereas when we access 'Software Sources' from 'Settings', it is using `kdesu`. Message as below. `org.kde.kdesu: Daemon not safe (not sgid), not using it.`. Inspite of 'Daemon not safe...' error, the software sources launches and able to make changes. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-qt 0.99.3.1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 28 11:41:34 2021 InstallationDate: Installed on 2021-05-28 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) 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/1929915/+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 1929915] [NEW] "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt-sudo'")
Public bug reported: Release: Kubuntu Groovy (also affects focal, hirsute) SW, version: software-properties-qt, 0.99.3.1 (for groovy but also affects version on focal) How to reproduce: 1) Launch Discover. 2) Search for (or scroll to) 'software sources', select the 'Software Sources' from the search result. 3) Click on 'Launch'. Expected: The application launches, possibly asking for admin password. Actual: Does not launch (on groovy). On focal, launches with error (Snapshot attached). However, if we try to access software sources from 'Settings', it launches properly. When launched from terminal, it was seen that discover was trying to use `lxqt-sudo` and failing since it was not installed. Error message as below. `kf.kio.gui: "Could not find the program 'lxqt-sudo'"` Whereas when we access 'Software Sources' from 'Settings', it is using `kdesu`. Message as below. `org.kde.kdesu: Daemon not safe (not sgid), not using it.`. Inspite of 'Daemon not safe...' error, the software sources launches and able to make changes. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-qt 0.99.3.1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 28 11:41:34 2021 InstallationDate: Installed on 2021-05-28 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) 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 focal groovy hirsute impish ** Tags added: focal hirsute impish ** Summary changed: - "Software Sources" fails to launch from Discover when trying lauch from applicatins list (kf.kio.gui: "Could not find the program 'lxqt-sudo'") + "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt-sudo'") -- 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/1929915 Title: "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt- sudo'") Status in software-properties package in Ubuntu: New Bug description: Release: Kubuntu Groovy (also affects focal, hirsute) SW, version: software-properties-qt, 0.99.3.1 (for groovy but also affects version on focal) How to reproduce: 1) Launch Discover. 2) Search for (or scroll to) 'software sources', select the 'Software Sources' from the search result. 3) Click on 'Launch'. Expected: The application launches, possibly asking for admin password. Actual: Does not launch (on groovy). On focal, launches with error (Snapshot attached). However, if we try to access software sources from 'Settings', it launches properly. When launched from terminal, it was seen that discover was trying to use `lxqt-sudo` and failing since it was not installed. Error message as below. `kf.kio.gui: "Could not find the program 'lxqt-sudo'"` Whereas when we access 'Software Sources' from 'Settings', it is using `kdesu`. Message as below. `org.kde.kdesu: Daemon not safe (not sgid), not using it.`. Inspite of 'Daemon not safe...' error, the software sources launches and able to make changes. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-qt 0.99.3.1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 28 11:41:34 2021 InstallationDate: Installed on 2021-05-28 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) 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/1929915/+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 1929915] Re: "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt-sudo'")
On Groovy, Hirsute, no error message window pops-up; the 'Launch' button is not-responsive. On Focal an error message is shown. Snap attached. ** Attachment added: "Screenshot at 2021-05-28 08-50-36.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1929915/+attachment/5500839/+files/Screenshot%20at%202021-05-28%2008-50-36.png -- 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/1929915 Title: "Software Sources" fails to launch from Discover when tried to launch from applications list (kf.kio.gui: "Could not find the program 'lxqt- sudo'") Status in software-properties package in Ubuntu: New Bug description: Release: Kubuntu Groovy (also affects focal, hirsute) SW, version: software-properties-qt, 0.99.3.1 (for groovy but also affects version on focal) How to reproduce: 1) Launch Discover. 2) Search for (or scroll to) 'software sources', select the 'Software Sources' from the search result. 3) Click on 'Launch'. Expected: The application launches, possibly asking for admin password. Actual: Does not launch (on groovy). On focal, launches with error (Snapshot attached). However, if we try to access software sources from 'Settings', it launches properly. When launched from terminal, it was seen that discover was trying to use `lxqt-sudo` and failing since it was not installed. Error message as below. `kf.kio.gui: "Could not find the program 'lxqt-sudo'"` Whereas when we access 'Software Sources' from 'Settings', it is using `kdesu`. Message as below. `org.kde.kdesu: Daemon not safe (not sgid), not using it.`. Inspite of 'Daemon not safe...' error, the software sources launches and able to make changes. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-qt 0.99.3.1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 28 11:41:34 2021 InstallationDate: Installed on 2021-05-28 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) 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/1929915/+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
