[Touch-packages] [Bug 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it
[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: plymouth (Ubuntu) Status: Incomplete => Expired -- 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/1871641 Title: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it Status in plymouth package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: Boot process freezes at the splash screen and nothing happens after that. The computer can be suspended and it is able to return from suspend. Boot is possible by pressing escape early in the process to bypass plymouth. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Wed Apr 8 14:30:13 2020 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-04-08 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 7469A23 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6DET72WW (3.22 ) dmi.board.name: 7469A23 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X200s dmi.product.name: 7469A23 dmi.product.version: ThinkPad X200s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871641/+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 1906986] Re: defective ir-keytable udev rule → custom keytable does not get loaded
[Expired for v4l-utils (Ubuntu) because there has been no activity for
60 days.]
** Changed in: v4l-utils (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to v4l-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1906986
Title:
defective ir-keytable udev rule → custom keytable does not get loaded
Status in v4l-utils package in Ubuntu:
Expired
Bug description:
ir-keytable v1.18.0-2build1 ships /lib/udev/rules.d/60-ir-
keytable.rules containing the following rule:
ACTION=="add", SUBSYSTEM=="rc", RUN+="/usr/bin/ir-keytable -a
/etc/rc_maps.cfg -s $name"
After upgrading to Focal, this does not get triggered at boot, nor if
I (re)insert my receiver when the system is running. Therefore, the
custom keytable does not get loaded.
This is the udev events that occur when I insert the receiver:
$ sudo udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1195.829011] add /devices/pci:00/:00:14.0/usb1/1-3 (usb)
KERNEL[1195.834989] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
KERNEL[1195.874055] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
KERNEL[1195.875019] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
KERNEL[1195.875183] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
KERNEL[1196.134164] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
KERNEL[1196.134448] bind
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
KERNEL[1196.134704] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)
UDEV [1196.158923] add /devices/pci:00/:00:14.0/usb1/1-3 (usb)
UDEV [1196.174559] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
UDEV [1196.194750] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/lirc0 (lirc)
UDEV [1196.196268] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11 (input)
UDEV [1196.197180] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/wakeup/wakeup21 (wakeup)
UDEV [1196.224577] add
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/rc/rc0/input11/event3 (input)
UDEV [1196.231346] bind
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0 (usb)
UDEV [1196.244978] bind /devices/pci:00/:00:14.0/usb1/1-3 (usb)
Note how there's no «(rc)» displayed on any of the lines, which means
that the «SUBSYSTEM=="rc"» condition from the udev rule filters all of
the above events.
I found a rule that works at https://www.mail-archive.com/linux-
me...@vger.kernel.org/msg117165.html:
ACTION=="add", SUBSYSTEM=="input", SUBSYSTEMS=="rc", KERNEL=="event*",
ENV{.rc_sysdev}="$id", RUN+="/usr/bin/ir-keytable -a /etc/rc_maps.cfg
-s $env{.rc_sysdev}"
Creating a custom /etc/udev/rules.d/60-ir-keytable.rules file
containing this rule solves the problem; now my custom keymap is
loaded at boot, as it did before (when I was running Bionic).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ir-keytable 1.18.0-2build1 [modified: usr/bin/ir-keytable]
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 6 18:05:06 2020
SourcePackage: v4l-utils
UpgradeStatus: Upgraded to focal on 2020-12-06 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1906986/+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 1907893] Re: package openssh-server 1:8.3p1-1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- 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/1907893 Title: package openssh-server 1:8.3p1-1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Expired Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.10 Package: openssh-server 1:8.3p1-1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 11 23:16:05 2020 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-12 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh Title: package openssh-server 1:8.3p1-1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1907893/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted
I just read about the correct way to report a bug or fix to the gnulib developers. I have emailed them as below: Date: Sat, 13 Feb 2021 at 12:40 Subject: Suggested fix to mountlist.c: Define fuse.portal, devtmpfs and squashfs mounts as dummy To: bug-gnu...@gnu.org Cc: juli...@ubuntu.com Hi gnulib developers, At present many gnulib users encounter this error: Running 'df' as user (not root) causes results in output that includes this error message: "df: /run/user/1000/doc: Operation not permitted" I would like to pass on to you a suggested fix: @@ -164,7 +164,10 @@ #define ME_DUMMY_0(Fs_name, Fs_type)\ (strcmp (Fs_type, "autofs") == 0 \ + || strcmp (Fs_type, "devtmpfs") == 0 \ + || strcmp (Fs_type, "fuse.portal") == 0 \ || strcmp (Fs_type, "proc") == 0 \ + || strcmp (Fs_type, "squashfs") == 0 \ || strcmp (Fs_type, "subfs") == 0\ /* for Linux 2.6/3.x */ \ || strcmp (Fs_type, "debugfs") == 0 \ Julian Klode, from Ubuntu, deserves credit for this suggested fix. He published a patch that has been included in the Ubuntu Hirsute 21.04 package: coreutils 8.32-4ubuntu2. See https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/19056232. https://launchpadlibrarian.net/510003931/coreutils_8.32-4ubuntu1_8.32-4ubuntu2.diff.gz I have cc'ed Julian in this email. The patch addresses a problem that particularly affects gnulib users with fuse.portal mounts, such as users who have installed Flatpak. This is a significant problem for users who depend on df not returning an error exit code in their scripts. Julian's bug report said: "/run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work)." This problem has also been reported on Fedora 32 here: flatpak/xdg-desktop-portal#512 Kind regards, Daniel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted
I formatted it as follows: @@ -164,7 +164,10 @@ #define ME_DUMMY_0(Fs_name, Fs_type) \ (strcmp (Fs_type, "autofs") == 0 \ + || strcmp (Fs_type, "devtmpfs") == 0 \ + || strcmp (Fs_type, "fuse.portal") == 0 \ || strcmp (Fs_type, "proc") == 0 \ + || strcmp (Fs_type, "squashfs") == 0 \ || strcmp (Fs_type, "subfs") == 0 \ /* for Linux 2.6/3.x */ \ || strcmp (Fs_type, "debugfs") == 0 \ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1915568] Re: lessfile is broken when using ~/.lessfilter
The attachment "fix-lessfile-with-lessfilter.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1915568 Title: lessfile is broken when using ~/.lessfilter Status in less package in Ubuntu: New Bug description: If ~/.lessfilter exists and is used by lesspipe/lessfile, then lessfile will make the filename of the temporary file visible in less. The attached patch fixes this. (The filename is echoed to less after the subshell exits; trying to do it inside the subshell means it ends up looking to less like part of the file being viewed.) To test this, you can place the following file at ~/.lessfilter: #!/bin/sh echo foo exit 0 Then opening any file in less (assuming you have lessfile set up) should show "foo". The bug is that, currently, it also shows a filename from somewhere in /tmp. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: less 487-0.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: Unity7 Date: Fri Feb 12 21:25:34 2021 Dependencies: debianutils 4.8.4 gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.4 libgcc1 1:8.4.0-1ubuntu1~18.04 libtinfo5 6.1-1ubuntu1.18.04 InstallationDate: Installed on 2018-08-13 (914 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: less UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1915568/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted
Hi Julian and Kamil, I tried to notify the gnulib upstream developers of this fix by creating a pull request in the github mirror (https://github.com/coreutils/gnulib/pull/11). I don't know how to create a pull request in the original git repository (git://git.sv.gnu.org/gnulib.git). I'm still learning. I hope that the developers are able to see my pull request, even though it is in the github mirror, not the original repository. All the best, Daniel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1915191] Re: ping utility displays wrong IPv4 address upon receiving ICMP Redirect
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: iputils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1915191
Title:
ping utility displays wrong IPv4 address upon receiving ICMP Redirect
Status in iputils package in Ubuntu:
Confirmed
Bug description:
* Observed behaviour *
We ping a host, say 137.226.39.170. While doing so, the router redirects us
to 137.226.42.42. (We verify, with Wireshark and taking a close look at RFC
792, that our redirect packet is formatted correctly on-wire.) We see the
following output of the ping utility:
64 bytes from 137.226.39.170: icmp_seq=46 ttl=251 time=0.619 ms
64 bytes from 137.226.39.170: icmp_seq=47 ttl=251 time=0.676 ms
64 bytes from 137.226.39.170: icmp_seq=48 ttl=251 time=1.92 ms
From 134.130.3.3 icmp_seq=47 Redirect Host(New nexthop: 42.42.226.137)
64 bytes from 137.226.39.170: icmp_seq=49 ttl=251 time=4.79 ms
The gateway address, as RFC 792 calls it, is displayed the wrong way
around. Feels like an Endianness bug right from the start.
* Expected behaviour *
ping utility should display the gateway address correctly. ("New nexthop:
137.226.42.42")
* Inspection of source code; bug theory of operation *
iputils_20190709.orig.tar.xz --> iputils-20190709/ping.c
Bug happens in the function pr_icmph(). This gets called from one of
three different places (lines 899, 1075, and 1101 of ping.c), and only
in one case, the fourth parameter is set to NULL (when called from
line 899).
The third parameter ("info") of pr_icmph() is generally meant to be
understood in host byte order. This can be seen in several places
(lines 1185, 1284).
Well, but in one place, this fact is ignored and the content of this
third parameter, being in host byte order, gets copied into a
structure that, by definition, is supposed to contain that piece of
information in network byte order, which constitutes the bug.
lines 1250 etc:
{
struct sockaddr_in sin = {
.sin_family = AF_INET,
.sin_addr = {
icp ? icp->un.gateway : info
}
};
printf(_("(New nexthop: %s)\n"), pr_addr(, sizeof sin));
}
In the first alternative of the ternary operator, icp->un.gateway is
in network byte order, and the value s_addr within struct in_addr that
it gets copied to is also in network byte order, so everything's
beautiful. But in the second alternative of the ternary operator, i.e.
if icp (parameter number four of pr_icmph) happens to be NULL, as
happens when pr_icmph() gets called from line 899, unfortunately the
value of "info" (in host byte order) gets copied into s_addr, and bad
things happen.
* Bugfix patch *
--- ping.c2019-07-09 22:55:49.0 +0200
+++ ping_fixed.c 2021-02-09 20:08:18.724747594 +0100
@@ -1251,7 +1251,7 @@
struct sockaddr_in sin = {
.sin_family = AF_INET,
.sin_addr = {
- icp ? icp->un.gateway : info
+ icp ? icp->un.gateway : htonl(info)
}
};
Simply converts the contents of info (which is in h_ost byte order) to
n_etwork byte order, and everything's fine.
Tried it, and this reliably fixes the bug.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iputils-ping 3:20190709-3
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Feb 9 19:33:57 2021
InstallationDate: Installed on 2015-12-09 (1889 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64
(20150805)
SourcePackage: iputils
UpgradeStatus: Upgraded to focal on 2020-12-28 (43 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1915191/+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 1915579] [NEW] version 2.03.11-2ubuntu1 breaks initramfs
Public bug reported: I upgraded lvm2 from 2.03.07-1ubuntu4 to 2.03.11-2ubuntu1 and my initramfs broke. I had to manually rollback to the old version to be able to boot. The error was something like: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/vgubuntu-root does not exist. Dropping to a shell! And there was no neither my lvm lvs, nor lvm binary on initramfs. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lvm2 2.03.07-1ubuntu4 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 13 02:42:08 2021 InstallationDate: Installed on 2019-11-01 (469 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1915579 Title: version 2.03.11-2ubuntu1 breaks initramfs Status in lvm2 package in Ubuntu: New Bug description: I upgraded lvm2 from 2.03.07-1ubuntu4 to 2.03.11-2ubuntu1 and my initramfs broke. I had to manually rollback to the old version to be able to boot. The error was something like: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/vgubuntu-root does not exist. Dropping to a shell! And there was no neither my lvm lvs, nor lvm binary on initramfs. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lvm2 2.03.07-1ubuntu4 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 13 02:42:08 2021 InstallationDate: Installed on 2019-11-01 (469 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915579/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
I have a new HP Envy TE-01 with Windows. Tried to load Ubuntu Studio 20.04 to dual boot. Installation crashed. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package
[Touch-packages] [Bug 1915568] [NEW] lessfile is broken when using ~/.lessfilter
Public bug reported: If ~/.lessfilter exists and is used by lesspipe/lessfile, then lessfile will make the filename of the temporary file visible in less. The attached patch fixes this. (The filename is echoed to less after the subshell exits; trying to do it inside the subshell means it ends up looking to less like part of the file being viewed.) To test this, you can place the following file at ~/.lessfilter: #!/bin/sh echo foo exit 0 Then opening any file in less (assuming you have lessfile set up) should show "foo". The bug is that, currently, it also shows a filename from somewhere in /tmp. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: less 487-0.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: Unity7 Date: Fri Feb 12 21:25:34 2021 Dependencies: debianutils 4.8.4 gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.4 libgcc1 1:8.4.0-1ubuntu1~18.04 libtinfo5 6.1-1ubuntu1.18.04 InstallationDate: Installed on 2018-08-13 (914 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: less UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: less (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Patch added: "fix-lessfile-with-lessfilter.patch" https://bugs.launchpad.net/bugs/1915568/+attachment/5463304/+files/fix-lessfile-with-lessfilter.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1915568 Title: lessfile is broken when using ~/.lessfilter Status in less package in Ubuntu: New Bug description: If ~/.lessfilter exists and is used by lesspipe/lessfile, then lessfile will make the filename of the temporary file visible in less. The attached patch fixes this. (The filename is echoed to less after the subshell exits; trying to do it inside the subshell means it ends up looking to less like part of the file being viewed.) To test this, you can place the following file at ~/.lessfilter: #!/bin/sh echo foo exit 0 Then opening any file in less (assuming you have lessfile set up) should show "foo". The bug is that, currently, it also shows a filename from somewhere in /tmp. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: less 487-0.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: Unity7 Date: Fri Feb 12 21:25:34 2021 Dependencies: debianutils 4.8.4 gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.4 libgcc1 1:8.4.0-1ubuntu1~18.04 libtinfo5 6.1-1ubuntu1.18.04 InstallationDate: Installed on 2018-08-13 (914 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: less UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1915568/+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 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
** Merge proposal linked: https://code.launchpad.net/~jawn-smith/bluez/+git/bluez/+merge/398022 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Status in bluez source package in Groovy: New Status in bluez source package in Hirsute: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+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 1915565] [NEW] screen fades for about 10 seconds glslideshowthen returns to normal
Public bug reported: The fading happens online at . But it also happens offline in games. Using Ubuntu 20.04 Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 12 13:14:56 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:820c] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:820c] InstallationDate: Installed on 2017-04-14 (1400 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0eef:c04d D-WAV Scientific Co., Ltd eGalaxTouch EXC3000-0367-44.01.00 Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0408:5090 Quanta Computer, Inc. HP Wide version HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=07e929a4-0ebf-4ecc-bedd-3f5fbf79e6d8 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 820C dmi.board.vendor: HP dmi.board.version: 82.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd09/21/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn820C:rvr82.29:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Notebook dmi.product.sku: X0S49UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Oct 17 14:45:19 2020 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915565 Title: screen fades for about 10 seconds glslideshowthen returns to normal Status in xorg package in Ubuntu: New Bug description: The fading happens online at . But it also happens offline in games. Using Ubuntu 20.04 Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 12 13:14:56 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.4.0-64-generic, x86_64: installed bbswitch, 0.8, 5.4.0-65-generic, x86_64: installed nvidia, 390.141, 5.4.0-64-generic, x86_64: installed nvidia, 390.141, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
** Changed in: sudo (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: In Progress Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE for sudoedit in src/parse_args.c. - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag checks in plugin in plugins/sudoers/policy.c. - debian/patches/CVE-2021-3156-3.patch: fix potential buffer overflow when unescaping backslashes in plugins/sudoers/sudoers.c. - debian/patches/CVE-2021-3156-4.patch: fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL in plugins/sudoers/timestamp.c. - debian/patches/CVE-2021-3156-5.patch: don't assume that argv is
[Touch-packages] [Bug 1915347] Re: Sync pyxdg 0.27-2 (main) from Debian unstable (main)
** Changed in: pyxdg (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pyxdg in Ubuntu. https://bugs.launchpad.net/bugs/1915347 Title: Sync pyxdg 0.27-2 (main) from Debian unstable (main) Status in pyxdg package in Ubuntu: In Progress Bug description: Please sync pyxdg 0.27-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Fix compatibility issue with python 3.8.4 (Closes: #964609, #968399) pyxdg delta was meant to fix an incompatibility with Python 3.8.4 This was causing a FTBFS at the time. The initial solution was cherry picked from an upstream github PR and has since been released. Debian BTS bug is referenced in both ubuntu and debian ChangeLog Changelog entries since current hirsute version 0.26-3ubuntu1: pyxdg (0.27-2) unstable; urgency=medium * Add the missing build dependency on setuptools. -- Andrej Shadura Wed, 13 Jan 2021 12:13:36 +0100 pyxdg (0.27-1) unstable; urgency=medium [ Andrej Shadura ] * New upstream release (Closes: #949738, #964609). * Refresh patches and drop a patch applied upstream. * Provide the actual module name. * Add a compatibility layer for the alternative xdg package. [ Debian Janitor ] * Use secure URI in Homepage field. [ Håvard Flaget Aasen ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. -- Andrej Shadura Tue, 12 Jan 2021 15:17:29 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyxdg/+bug/1915347/+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 1915553] [NEW] add-apt-repository won't remove ppa if ppa has been deleted
Public bug reported: If a ppa is added to the system, and then the ppa is deleted, add-apt- repository fails to remove it, e.g.: $ sudo add-apt-repository -r ppa:ubuntu-support-team/add-apt-repository ERROR: ppa 'ubuntu-support-team/add-apt-repository' not found (use --login if private) the script should remove the source.list entry, which can be calculated even if the ppa doesn't exist anymore. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- 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/1915553 Title: add-apt-repository won't remove ppa if ppa has been deleted Status in software-properties package in Ubuntu: New Bug description: If a ppa is added to the system, and then the ppa is deleted, add-apt- repository fails to remove it, e.g.: $ sudo add-apt-repository -r ppa:ubuntu-support-team/add-apt-repository ERROR: ppa 'ubuntu-support-team/add-apt-repository' not found (use --login if private) the script should remove the source.list entry, which can be calculated even if the ppa doesn't exist anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1915553/+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 1915548] [NEW] package libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co
Public bug reported: yes ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 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: Fri Feb 12 03:11:48 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: db5.3 Title: package libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: db5.3 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package focal i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1915548 Title: package libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in db5.3 package in Ubuntu: New Bug description: yes ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 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: Fri Feb 12 03:11:48 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: db5.3 Title: package libdb5.3:i386 5.3.28+dfsg1-0.6ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1915548/+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 1915547] [NEW] sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Public bug reported:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644 2020-02-17
18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
[Test Case]
We have performed a manual test with a modified version of the xenial package:
https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
Using that package, we were able to verify that the config change prompt
no longer happens from trusty to xenial.
[Regression Potential]
Since we are modifying are features on unattended-upgrades, just adding a new
file to package, we don't believe there is any regression potential
[Discussion]
== End SRU Template ==
== Changelog ==
* data: add md5sum history file on the data folder
- This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file
** Affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
** Affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1915547
Title:
sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to
1.1ubuntu1.18.04.7~16.04.7 ) Xenial
Status in unattended-upgrades package in Ubuntu:
New
Status in unattended-upgrades source package in Xenial:
New
Bug description:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08
19:21:39
+++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644
2020-02-17 18:03:38
@@ -1,11 +1,13 @@
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
+ "${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
The reason we are presented with this diff is that the xenial package
does not contain a md5sum history file that informs ucf about all the
supported configs for 50unattended-upgrades. To fix that upgrade
problem, we are prosing the following changes on the xenial package of
unattended-upgrades:
- Add 50unattended-upgrades.md5sum file into the xenial package
- Add md5sum of the current xenial 50unattende-upgrades file into the
md5sum history file
- Modify ucf command in postinst to be aware of the md5sum history file
See the changelog entry below for a full list of changes and bugs.
[Test
[Touch-packages] [Bug 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
Sorry, this bug is not fixed. After getting better wifi driver, it gains a different kernel name. And hence NetworkManager "disconnects" and doesn't reconnect. When this happens, you need to setup Wifi connection again. I do not know how to fix this, and/or anticipate the new wifi card name. -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1867465/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
Ok, here you go. I reproduced the (or a) failure in Canonistack. This was the first run FWIW, so it wasn't too hard to get it to fail: autopkgtest [14:05:12]: test systemd-fsckd: [--- test_fsck_failure (__main__.FsckdTest) Ensure that a failing fsck doesn't prevent fsckd to stop ... bash: line 1: 1250 Killed /tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd 2> >(tee -a /tmp/autopkgtest.5SlVJo/systemd-fsckd-stderr >&2) > >(tee -a /tmp/autopkgtest.5SlVJo/systemd-fsckd-stdout) autopkgtest [14:05:16]: test process requested reboot with marker test_fsck_failure autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... test_fsck_failure (__main__.FsckdTest) Ensure that a failing fsck doesn't prevent fsckd to stop ... FAIL == FAIL: test_fsck_failure (__main__.FsckdTest) Ensure that a failing fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 190, in test_fsck_failure self.check_plymouth_start() File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 158, in check_plymouth_start self.assertUnitStarted(unit) File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 228, in assertUnitStarted self.assertTrue(has_unit_started(unit)) AssertionError: False is not true -- Ran 1 test in 11.289s FAILED (failures=1) autopkgtest [14:06:11]: test systemd-fsckd: ---] autopkgtest [14:06:12]: test systemd-fsckd: - - - - - - - - - - results - - - - - - - - - - systemd-fsckdFAIL non-zero exit status 1 autopkgtest [14:06:13]: summary timedatedPASS hostnamedPASS localed-locale PASS localed-x11-keymap PASS logind PASS unit-config PASS storage PASS networkd-test.py PASS build-login PASS boot-and-servicesPASS udev PASS root-unittests PASS tests-in-lxd PASS upstream PASS boot-smoke PASS systemd-fsckdFAIL non-zero exit status 1 Full logs attached. The commandline is at the top of the log - is that enough for you to be able to have a go, Balint? I suggest adding --shell-fail of course so you can break in once it happens. ** Attachment added: "systemd-canonistack-cpu4-ram8-disk50.tar.xz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915126/+attachment/5463223/+files/systemd-canonistack-cpu4-ram8-disk50.tar.xz -- 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/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/)
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
This new diff from debian drops the whitespace changes and adds the dropped CVE patches to the changelog ** Patch added: "Diff from Debian take two" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915307/+attachment/5463220/+files/debian-ubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: In Progress Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE for sudoedit in src/parse_args.c. - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag checks in plugin in plugins/sudoers/policy.c. - debian/patches/CVE-2021-3156-3.patch: fix potential buffer overflow when unescaping backslashes in plugins/sudoers/sudoers.c. - debian/patches/CVE-2021-3156-4.patch: fix the
[Touch-packages] [Bug 1915250] Re: buildd file owner/group for shared libraries
** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1915250 Title: buildd file owner/group for shared libraries Status in binutils package in Ubuntu: Confirmed Status in debhelper package in Ubuntu: Confirmed Status in fakeroot package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Confirmed Status in debhelper package in Debian: Unknown Bug description: the current state of -proposed creates deb packages with buildd file owner/group for shared libraries. reported at least for kwayland-integration. $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so -rw-r--r-- doko/doko 18984 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so -rw-r--r-- doko/doko 85392 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so -rw-r--r-- doko/doko 35536 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so - in a release pocket, rebuild binutils from proposed. correctly restores the file ownership - in a release pocket, update glibc from proposed. then rebuild binutils from proposed. shows the wrong ownership To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
** Also affects: wpa (Debian) Importance: Undecided Status: New ** Changed in: wpa (Debian) Importance: Undecided => Wishlist ** Changed in: wpa (Debian) Status: New => Fix Released ** Changed in: wpa (Debian) Assignee: (unassigned) => Andrej Shadura (andrew.sh) -- 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/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Fix Committed Status in wpa package in Debian: Fix Released Bug description: [Impact] Users booting from OEM setup may find that their wireless device is "not ready" as per NetworkManager, because wpasupplicant is not running. This is because the steps taken to start in OEM prepare, before moving to the real system runs systemctl isolate, and wpasupplicant gets caught in the crossfire. [Test case] * Steps to reproduce: 1. Install in OEM mode 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. [Regression potential] The following are examples of possible regression scenarios from this stable update: - Failure to get the wireless device ready at session start - Driver loading issues for the wireless devices - Failure to complete OEM preparation steps, due to the oem user remaining connected while it's being removed by the last steps of the OEM preparation process. [Background information] * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1915526] [NEW] GDebi disappears with no messages on Mate 20.10
Public bug reported: Ubuntu Mate 20.10 - Release 20.10 (Groovy Gorilla) 64-bit - Kernel Linux 5.8.0-43-generic x86_64 - MATE 1.24.1 - gdebi 0.9.5.7+nmu3 Tried installing 3 downloaded .deb packages: - onlyoffice-desktopeditors_amd64.deb - opera-stable_74.0.3911.107_amd64.deb - Simplenote-linux-2.6.0-amd64.deb In all instances, after gdebi displays a window saying that additional packages will be installed and then asks for a password, it just disappears with no messages and the packages are not installed. Installing the packages using "sudo dpkg -i" in the terminal successfully installed these packages. gdebi in Ubuntu Mate 20.10 seems broken. ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1915526 Title: GDebi disappears with no messages on Mate 20.10 Status in gdebi package in Ubuntu: New Bug description: Ubuntu Mate 20.10 - Release 20.10 (Groovy Gorilla) 64-bit - Kernel Linux 5.8.0-43-generic x86_64 - MATE 1.24.1 - gdebi 0.9.5.7+nmu3 Tried installing 3 downloaded .deb packages: - onlyoffice-desktopeditors_amd64.deb - opera-stable_74.0.3911.107_amd64.deb - Simplenote-linux-2.6.0-amd64.deb In all instances, after gdebi displays a window saying that additional packages will be installed and then asks for a password, it just disappears with no messages and the packages are not installed. Installing the packages using "sudo dpkg -i" in the terminal successfully installed these packages. gdebi in Ubuntu Mate 20.10 seems broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1915526/+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 1915443] Re: 有 46 个软件包没有被完全安装或卸载。 需要下载 0 B/116 kB 的归档。 解压缩后会消耗 285 kB 的额外空间。 您希望继续执行吗？ [Y/n] y (正在读取数据库 ... 系统当前共安装有 282921 个文件和目录。) 准备解压 .../libpng12-0_1.2.54-1ubuntu1_amd64.deb
*** This bug is a duplicate of bug 1915442 *** https://bugs.launchpad.net/bugs/1915442 ** This bug has been marked a duplicate of bug 1915442 有 46 个软件包没有被完全安装或卸载。 需要下载 0 B/116 kB 的归档。 解压缩后会消耗 285 kB 的额外空间。 您希望继续执行吗？ [Y/n] y (正在读取数据库 ... 系统当前共安装有 282921 个文件和目录。) 准备解压 .../libpng12-0_1.2.54-1ubuntu1_amd64.deb ... 正在解压 libpng12-0:amd64 (1.2.54-1ubuntu1) ... dpkg: 处理归档 /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--u npack)时出错： 无法安装 /lib/x86_64-linux-gnu/libpng12.so.0 的新版本: 没有那个文件或目录 错误信息显示本地系统有一些问题，因此没有写入 apport 报告 在处理时有错误发生： /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpng in Ubuntu. https://bugs.launchpad.net/bugs/1915443 Title: 有 46 个软件包没有被完全安装或卸载。 需要下载 0 B/116 kB 的归档。 解压缩后会消耗 285 kB 的额外空间。 您希望继续执行吗？ [Y/n] y (正在读取数据库 ... 系统当前共安装有 282921 个文件和目录。) 准备解压 .../libpng12-0_1.2.54-1ubuntu1_amd64.deb ... 正在解压 libpng12-0:amd64 (1.2.54-1ubuntu1) ... dpkg: 处理归档 /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--u npack)时出错： 无法安装 /lib/x86_64-linux-gnu/libpng12.so.0 的新版本: 没有那个文件或目录 错误信息显示本地系统有一些问题，因此没有写入 apport 报告 在处理时有错误发生： /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb E: Sub- process /usr/bin/dpkg returned an error code (1) Status in libpng package in Ubuntu: New Bug description: 有 46 个软件包没有被完全安装或卸载。 需要下载 0 B/116 kB 的归档。 解压缩后会消耗 285 kB 的额外空间。 您希望继续执行吗？ [Y/n] y (正在读取数据库 ... 系统当前共安装有 282921 个文件和目录。) 准备解压 .../libpng12-0_1.2.54-1ubuntu1_amd64.deb ... 正在解压 libpng12-0:amd64 (1.2.54-1ubuntu1) ... dpkg: 处理归档 /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--u npack)时出错： 无法安装 /lib/x86_64-linux-gnu/libpng12.so.0 的新版本: 没有那个文件或目录 错误信息显示本地系统有一些问题，因此没有写入 apport 报告 在处理时有错误发生： /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1915443/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
I had this same bug. This was fixed? -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1867465/+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 1867465] Re: Installer disconnects wifi (after choosing download while installing, 3rd party)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- 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/1867465 Title: Installer disconnects wifi (after choosing download while installing, 3rd party) Status in systemd: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Bug description: ISO testing 20.04 daily 20200314. On the Live desktop I connect to wifi. When I click the install icon, and choose to install 3rd party (leaving download while installing checked), the wifi disconnects. I rebooted and tried again to make sure it wasn't something random. (It happened exactly the same.). This is an older Dell E5420 laptop with Broadcom BCM4313 wireless card. (Today's Lubuntu had a wifi-related problem too. I couldn't connect to wifi upon reboot after install. I had to reboot a 2nd time for it to work. I reported that to their Discourse forum, not reported as a bug yet.). I apologize that I don't know the package or pid to report this for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.441 CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 14 20:29:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:049b] LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: Dell Inc. Latitude E5420 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/ubuntustudio.seed initrd=/casper/initrd quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0H5TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/26/2013:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1867465/+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 387957] Re: Improve Save As Dialog Box (focus issues)
This truly feels like a significant downgrade when coming from any other OS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/387957 Title: Improve Save As Dialog Box (focus issues) Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: The save dialog box has the irritating habit of not focusing on the file name area once I have browsed to the location where I would like to save my document. This is done better in Windows. There are two main scenarios when saving a document where this behaviour annoys: Scanario 1 - Browsing to save location by double-clicking: 1. File -> Save As (to bring up the "Save" dialog box). 2. Double click on the folder in which you would like to save the document. 3. Notice that the focus is now in the folder list area, not on the file name area. 4. I now have to click in the file name area to be able to name my document. In Windows, the focus is returned immediately to the file name box once a folder is double clicked, so the name can be typed and the document saved in one step. Scenario 2 - Browsing save location using the keyboard (find as you type): 1. File -> Save As (to bring up the "Save" dialog box). 2. Click on the folder area so that folder names can be typed to find them. Hit enter to enter desired folder. 3. Within the folder, step 2 can be repeated for subfolders indefinitely. 4. Once the desired location has been reached, the user must use the mouse click in the file name area to name the file before saving. In Windows, when using find as you type, although focus is retained by the folder area when entering a lower folder level (so that you can browse to another level using the keyboard if desired), jumping to the file name box is simply a matter of pressing tab ONCE. In Ubuntu, I have to reverse tab (shift-tab) around 10 times to get back to the file name box at the top of the screen, or use the mouse - most annoying. Solutions (copy the Windows behaviour): 1. If a folder is double clicked with the mouse, the focus should jump back to the file name box. 2. If a folder is entered into by pressing enter (on the keyboard), focus should remain in the folder area, but the file name box should only be a single tab away. I understand that solution 2 is problematic in that tabbing would ordinarily jump to the next element (usually the "file type" dropdown), not back to the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+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 1915508] [NEW] reduced many features of desktop
Public bug reported: removed all of my shortcuts, when i right click fewer options appear and i cannot plug external mouse or keyboard and also i cannot multiselect items. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 15:47:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:3184] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:398a] InstallationDate: Installed on 2021-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:116a Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81D1 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=a1766085-d55f-4da8-a290-9b0a643db278 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7XCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IGM dmi.modalias: dmi:bvnLENOVO:bvr7XCN24WW:bd07/16/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM: dmi.product.family: ideapad 330-15IGM dmi.product.name: 81D1 dmi.product.sku: LENOVO_MT_81D1_BU_idea_FM_ideapad 330-15IGM dmi.product.version: Lenovo ideapad 330-15IGM dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915508 Title: reduced many features of desktop Status in xorg package in Ubuntu: New Bug description: removed all of my shortcuts, when i right click fewer options appear and i cannot plug external mouse or keyboard and also i cannot multiselect items. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 15:47:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:3184] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:398a] InstallationDate: Installed on 2021-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:116a Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81D1 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=a1766085-d55f-4da8-a290-9b0a643db278 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7XCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IGM dmi.modalias:
[Touch-packages] [Bug 1779767] Re: Default cron PATH does not include /snap/bin
** Also affects: cron (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: cron (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in cron package in Ubuntu: Confirmed Status in cron source package in Bionic: New Status in cron source package in Focal: New Status in cron source package in Groovy: New Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779767/+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 1915502] [NEW] "systemd --user" fails to start for non-local users
Public bug reported:
systemd-logind fails to start the systemd --user process for non-local
users on Ubuntu 20.04. This is a reproducible problem; all our systems
are displaying the same symptoms.
The systems are using Kerberos (Active Directory) for authentication,
and NIS for account meta-data and authorisation (groups)
A base installation is performed using the server 20.04 ISO image. No
additional packages are selected. Post-install, I run:
apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd
I set up the NIS client (supply the default domain name, check ypbind is
running and ypcat passwd is working)
I then set up /etc/krb5.conf for kerberos authentication to a domain
controller, confirm that kinit works and a kerberos ticket is issued.
I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the
end of each.
/etc/nsswitch.conf is modified to support compat mode, as well as
systemd:
passwd: compat systemd
group: compat systemd
shadow: compat
I can log in remotely via ssh using my NIS account and Kerberos
credentials. MY NIS meta-data looks like:
amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh
(where UID and GID are replaced with values unique to the organisation)
On login, the following occurs:
hostname:~> systemctl --user
Failed to connect to bus: No such file or directory
I put pam-systemd and systemd-logind into debug mode to get more
information:
Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from
[redact] port 58849 ssh2: RSA SHA256:[redact]
Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened
for user amcvey by (uid=0)
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd
initializing
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind
to create session: uid=198083 pid=1210 service=sshd type=tty class=user
desktop= seat= vtnr=0 tty= display= remote=yes remote_user=
remote_host=10.105.121.110
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return
sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a
cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a
runtime_max_sec=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to
create session: No such process
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return
sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a
cookie=14 reply_cookie=41 signature=u error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state
idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: Sending message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client
→ awaiting-reply
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: New incoming message:
{"error":"io.systemd.UserDatabase.NoRecordFound","parameters":{}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state
awaiting-reply → processing-reply
Feb 12 09:51:32 myhostname systemd-logind[903]: Got lookup error:
io.systemd.UserDatabase.NoRecordFound
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state
processing-reply → idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=error
sender=n/a destination=:1.13 path=n/a interface=n/a member=n/a cookie=42
reply_cookie=2 signature=s
[Touch-packages] [Bug 1846180] Re: 1910 software-properties larger screen size
fix released with 20.04.2 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- 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/1846180 Title: 1910 software-properties larger screen size Status in software-properties package in Ubuntu: Fix Released Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Screen size 1366x768, Russian language. Update settings go beyond the edge of the screen. The window cannot be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1846180/+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 1893563] Re: netplan: can't login to ap mode with psk
Right, my apologies, I was too quick to be angry: I only checked the patch proposed here but not the actual one committed — and apparently I haven’t read the discussion to the end. Having checked the actual package, I see it is in fact a patch from the upstream Git. Still, it’d be great if you could at least notify me, and it would be much better if we could first push such changes into Debian first. -- 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/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1893563] Re: netplan: can't login to ap mode with psk
I’ve just verified and in fact not only this hasn’t been submitted upstream, but the upstream has shipped an alternative implementation of this by Beniamino Galvani (@bengal). I’d really appreciate if Ubuntu didn’t add non-trivial patches without discussion with the upstream and me as the Debian maintainer for this package. -- 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/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1915491] Re: Wifi Adpter Not found
Thanks for the bug report. I can see from your Lspci.txt that there definitely is an Intel wifi card installed. So this looks like some kind of GUI (or intermediate daemon) bug. ** Summary changed: - Wifi Adpter Not found + Wifi adapter installed but can't be found in Settings ** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915491 Title: Wifi adapter installed but can't be found in Settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: # Summary: > ## Wifi Adpter Not found ## Steps to Reproduce: - I don't know ## Expected Results: Wifi should always be available ## Problem Description: Sometimes when startup my pc there is no wifi icon on the top right corner menu. When checking the wifi settings on the settings window it shows that the wifi adapter not found. But after restarting the pc, everything back to normal again. This is happening too frequently now. * * * Screenshot: https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 11:13:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E7470 [1028:06dc] InstallationDate: Installed on 2021-01-06 (36 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E7470 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 047I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+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 1893563] Re: netplan: can't login to ap mode with psk
@seb128, @mhodson, @shemgp, has this patch been submitted to the upstream? -- 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/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Committed Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1915491] Re: Wifi Adpter Not found
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915491 Title: Wifi adapter installed but can't be found in Settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: # Summary: > ## Wifi Adpter Not found ## Steps to Reproduce: - I don't know ## Expected Results: Wifi should always be available ## Problem Description: Sometimes when startup my pc there is no wifi icon on the top right corner menu. When checking the wifi settings on the settings window it shows that the wifi adapter not found. But after restarting the pc, everything back to normal again. This is happening too frequently now. * * * Screenshot: https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 11:13:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E7470 [1028:06dc] InstallationDate: Installed on 2021-01-06 (36 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E7470 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 047I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+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 1915491] [NEW] Wifi Adpter Not found
You have been subscribed to a public bug: # Summary: > ## Wifi Adpter Not found ## Steps to Reproduce: - I don't know ## Expected Results: Wifi should always be available ## Problem Description: Sometimes when startup my pc there is no wifi icon on the top right corner menu. When checking the wifi settings on the settings window it shows that the wifi adapter not found. But after restarting the pc, everything back to normal again. This is happening too frequently now. * * * Screenshot: https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 11:13:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E7470 [1028:06dc] InstallationDate: Installed on 2021-01-06 (36 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E7470 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 047I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- Wifi Adpter Not found https://bugs.launchpad.net/bugs/1915491 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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
