** Changed in: isc-dhcp (Ubuntu)
Assignee: TJ (tj) => (unassigned)
** Changed in: network-manager (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
Public bug reported:
I've been working with a user for the last 2 days on a failure to even
start the kernel when installing 20.04 or 21.04 (possibly other
releases) with a UEFI boot.
System is Dell XPS 9550 amd64 with Ubuntu Budgie.
The symptom is that after GRUB successfully loads the kernel i
I suspect these may be related:
https://github.com/electron/electron/pull/30893 "fix: crash when
launching app with systemd v249"
https://github.com/microsoft/vscode/issues/132609 "Electron 14+
required? Potential systemd 249 / nVidia issue"
Electron patch backported from Chromium:
https://gith
Update: Lennart's AF_SOCKET solution was added to systemd v248 in:
commit e2c2f868b28f1445e061bf7eb475b0c49efe3ac2
Author: Lennart Poettering
Date: Wed Nov 4 17:24:53 2020 +0100
cryptsetup: port cryptsetup's main key file logic over to
read_full_file_full()
Previously, we'd load
This really should not be marked Invalid since it represents a very real
regression on recommended and documented functionality that many
installs using LUKS rely upon. Workarounds of varying security quality
abound as a result instead of a single, well designed and integrated
solution.
Indeed, in
I'm currently working on getting my optimisation patches into the
mainline kernel and to Debian's initramfs-tools. After that I'll
investigate dracut.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
y it has minimal potential for causing regressions.
[1] https://github.com/linux-surface/linux-surface/issues/625
[2] https://launchpad.net/~tj/+archive/ubuntu/bugfixes
[3] https://salsa.debian.org/apt-
team/apt/-/commit/06ec0067057e0578f3bc515f6a97d6a9d70824f6
** Affects: apt (Ubuntu)
Impor
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1905800
Title:
Apparmor denies pid file creation for dhcli
Had my techie test the SRU for 20.04 on the affected E495 and can
confirm this works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Regression: block stairc
Another follow-up. Had the same problem with 20.04 amd64. My solution
detailed above would not work when using the GUI where the Blueman
bluetooth applet was in the notification area.
Eventually I found it worked from a real tty console (switched from GUI
to tty2 with Ctrl+Alt+F2) and running the
Public bug reported:
iputils-ping includes ping6 which can send Node Information requests,
e.g:
ping6 -N name ipv6:addr::ess
but there is no system daemon to listen and respond.
iputils package contains ninfod which performs that function but it
isn't built or packaged.
For IPv6 networks Node
I'm also wondering if these are laptops or desktops, and if laptops, are
they mainly on battery whilst not sleeping/charging? I ask since apt-
daily-upgrade.service has:
ConditionACPower=true
and so may be reporting:
Condition check resulted in Daily apt upgrade and clean activities being
skippe
I haven't been able to test this since the systems I have here don't
have any kernel images lying around, but wondering if this patch could
help narrow down the cause?
Apply to a (copy) of /usr/bin/unattended-upgrade - possibly put in
/usr/local/bin/ so it is called before the package-installed ve
Erich, looks like that code wasn't reached or if it was the object
(list) "auto_removable" was empty.
Maybe the problem is outside this code. Does apt think those packages
are still installed?
apt list --installed 'linux-image*'
Also, what is the actual content of /boot/ ("ls -latr /boot/") ? I
Public bug reported:
Possible vulnerability with an active proof of concept that may well
become a CVE.
ssh-agent Shielded Private Key Extraction
https://security.humanativaspa.it/openssh-ssh-agent-shielded-private-
key-extraction-x86_64-linux/
** Affects: openssh (Ubuntu)
Importance: Unde
Public bug reported:
Despite the fix in 2012 (bug #991360) the default configuration shipped
with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the
DHCPv6 hostname option by default. All it needs is:
# send host-name with DHCPv6 not just DHCPv4
send fqdn.fqdn = gethostname();
Wit
** Description changed:
Despite the fix in 2012 (bug #991360) the default configuration shipped
- with isb-dhcp-client /etc/dhclient.conf in 2021 still does not set the
- DHCPv6 hostname option by default. All it needs is:
+ with isb-dhcp-client /etc/dhcp/dhclient.conf in 2021 still does not set
Public bug reported:
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server answers and then
resolved sends an ICMP Destination Unreachable (Port Unreachabl
** Description changed:
+ Afffects Ubuntu 18.04 through 21.04 (fixes are in systemd v248)
+
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server an
** Description changed:
Afffects Ubuntu 18.04 through 21.04 (fixes are in systemd v248)
With systemd v245 (and v247) and systemd-resolved we're seeing frequent
problems due to resolved rapidly closing the socket on which it sends
out a query before the server has answered. The server an
The local systemd-resolved fails to resolve the name so client
applications return failures. Most notably it shows up in web browsers
but also for apt package updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
I've cherry-picked the upstream patches and built the package in my bug-
fixes PPA:
https://launchpad.net/~tj/+archive/ubuntu/bugfixes
Verified it solves the issue even in the face of a 1000ms delay being
imposed by the router using:
## example traffic control to slow down UDP port 53 tr
providing the same
file with different content.
tj ~ apt-file list live-tools | grep man
live-tools: /usr/share/man/ca/man7/live-tools.7.gz
live-tools: /usr/share/man/ca/man8/live-update-initramfs.8.gz
live-tools: /usr/share/man/de/man1/live-system.1.gz
live-tools: /usr/share/man/de/man1/live-toram
Turns out this *is* systemd-logind and xfce4-power-manager fighting over
the lid close event.
It can be solved with:
echo "HandleLidSwitch=ignore" | sudo tee -a /etc/systemd/logind.conf
echo "HandleLidSwitchExternalPower=ignore" | sudo tee -a
/etc/systemd/logind.conf
If you're doing this change
** Bug watch added: Xfce Bugzilla #15151
https://bugzilla.xfce.org/show_bug.cgi?id=15151
** Also affects: systemd via
https://bugzilla.xfce.org/show_bug.cgi?id=15151
Importance: Unknown
Status: Unknown
** Changed in: xfce4-power-manager (Ubuntu)
Status: New => Confirmed
**
To check on current systemd-logind properties including these:
$ loginctl -a show-session
--
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/1759950
Title:
Lid-close suspend:
More search seems to point to a 2015 commit that integrated light-locker
into xfce4-power-manager. This patch in particular appears to attempt to
work with logind Lid handling too:
commit 10076da7caa49320b3e907d319a9f27ee6702969
Author: Sean Davis
Date: Sat Feb 7 11:49:31 2015 +0300
Light
I've done some more tests with another clean install of 19.04; The only
user setting I changed was on x-p-m for Laptop Lid Closed, On Battery =
suspend.
1st suspend=resume cycle is fine; user session re-appears after
unlocking with password
*BUT*
2nd suspend-resume cycle turns the LCD panel off
Update: Disabling x-p-m Security > Lock screen when system is going to
sleep causes the LCD to be blank resume for the 1st cycle.
This definitely feels like some weird interaction with x-p-m, light-
locker, and logind.
--
You received this bug notification because you are a member of Ubuntu
Touc
And it gets weirder... with supend-lock disabled AND leaving x-p-m
dialog box on screen whilst suspending the LCD always gets enabled on
resume!
I tried leaving other application windows open but those don't have the
same effect.
--
You received this bug notification because you are a member of
On brainwash's suggestion (IRC #xubuntu-devel) I disabled UPower's Lid
handling with /etc/UPower/UPower.conf:
IgnoreLid=true
After six suspend-resume cycles this does seem to have prevented the issue.
*However* I then noticed that in the x-p-m dialog, General tab, the
options to control the Lid
I purged both xfce4-screensaver and light-locker packages, restarted
lightdm and tested with x-p-m set to suspend on lid-close for battery
(and AC as I've had the battery exhaust several times due to the length
of these tests!)
In this case there is no password challenge dialog on resume.
It fail
maxpus=1 still suffers the same issue.
I then disabled and stopped the upower daemon but the issue remains with
the only common factors being systemd-logind and lightdm.
I tried console-only tests with lightdm stopped and CANNOT reproduce the
issue.
I installed sddm and changed the default displ
Yet more results changing the target once again!
I was able to reproduce the issue whilst using sddm which tends to
suggest lightdm may not be the cause.
I also managed to prove (not sure why this did not occur to me before
now!) that the DPMS state is being set 'off' when switching to the GUI
tt
Finally found some evidence and it is surprising.
I added /usr/local/bin/xfce4-power-manager:
#!/bin/sh
exec /usr/bin/xfce4-power-manager --debug
and logged in as normal. Confirmed x-p-m is writing debug messages.
Closed the lid, it suspended, opened lid and tap key to resume as per
usual.
The
This seems to be the crux of the issue. In a VT console I did:
DISPLAY=:0 XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon
and the did the usual lid-close->resume cycle and found:
xfce4-settings(displays): UPower lid event received (open -> closed).
xfce4-settings(displays): Toggling intern
I've captured a log where it doesn't fail. The difference is a single
error message. In failing sessions there is an additional "Failed to
configure CRTC..." which is not seen here:
xfce4-settings(displays): UPower lid event received (closed -> open).
xfce4-settings(displays): Toggling internal ou
The reason the CRTC isn't configured:
(xfsettingsd:1694): xfsettingsd-WARNING **: 15:02:36.290: Failed to
configure CRTC 79 XRRSetCrtcConfig()=3.
This due to my patch:
--- xfce4-settings-4.13.4.orig/xfsettingsd/displays.c
+++ xfce4-settings-4.13.4/xfsettingsd/displays.c
@@ -1265,7 +1265,7 @@ xfc
Added:
Description: Loop delay on CRTc config failure
--- xfce4-settings-4.13.4.orig/xfsettingsd/displays.c
+++ xfce4-settings-4.13.4/xfsettingsd/displays.c
@@ -1256,10 +1256,17 @@ xfce_displays_helper_apply_crtc (XfceRRC
ret = xfce_displays_helper_disable_crtc (helper, crtc->id);
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubunt
After many hours diving down rabbit holes it turns out this is due to a
major change in the behaviour of update-initramfs introduced by Debian
in July 2018 which made its way into the Ubuntu archive end of april
2019.
01:02 Right! initramfs-tools had a MAJOR import from Debian with
"initramfs-too
We have a second bug that causes the call by update-
initramfs::get_sorted_versions() to report nothing when calling
(/usr/bin/) "linux-versions list".
This because the target root file-system is copied from the
filesystem.squashfs on the ISO which does NOT contain a
/boot/vmlinuz-$(uname -r).
ca
I should have made clear, this 'second bug' is the only bug.
initrmafs-tools is in the clear - it wasn't finding a kernel image
because there wasn't one when update-initramfs was executed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
Or is it? Actually I not, because the test in update-
initramfs::get_sorted_versions() expects an existing
initrd.img-$version:
get_sorted_versions()
{
version_list="$(
linux-version list |
while read -r version; do
test -e "${BOOTDIR}/
I modified libxrandr to return the actual error code returned from
XRRSetCrtcConfig():
--- libxrandr-1.5.1.orig/src/XrrCrtc.c
+++ libxrandr-1.5.1/src/XrrCrtc.c
@@ -155,9 +155,10 @@ XRRSetCrtcConfig (Display *dpy,
req->mode = mode;
req->rotation = rotation;
Data32 (dpy, outputs, nout
Tested with the 19.10 daily (2019-06-22) amd64 build and the problem
affects the live environment too.
Set x-p-m Lid Close action on battery to suspend and the 2nd lid close
cycle results in DPMS=off when the GUI TTY is active.
As in comment #15 I monitored the LVDS DPMS state whilst switching
be
** Also affects: policykit-1 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/polkit/polkit/issues #39
https://gitlab.freedesktop.org/polkit/polkit/issues/39
** Also affects: policykit-1 via
https://gitlab.freedesktop.org/polkit/polkit/issues/3
: In Progress => Invalid
** Changed in: lxqt-policykit (Ubuntu)
Status: Confirmed => Invalid
** Changed in: policykit-1 (Ubuntu)
Status: New => Confirmed
** Changed in: lubuntu-meta (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because y
Using gparted (which requires root access to the block storage devices)
"test" user fails whilst original "lubuntu" user is successful:
# In "lubuntu" user's GUI terminal emulator:
lubuntu@lubuntu:~$ gparted
localuser:root being added to access control list
==
libparted : 3.2
Possibly related to Bug #1821415 "pkexec fails in a non-graphical
environment"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1828663
Title:
policykit failures due to
Lubuntu is suffering what seems to be a related failure although I
tracked that down to what I thought was a different upstream bug report.
In Lubuntu's case the lxqt-policykit-agent suffers a SIGSEGV as a side-
affect (I think) of polkit failing to authorise.
It was originally discovered when, us
d. After nearly a minute I pressed the
power button and the PC instantly resumed.
dmesg reported "Suspended for 43 seconds" which is correct and
network-manager correctly returned to connected state.
---
tj@T300CHI:~$ nmcli gen
STATE CONNECTIVITY WIFI-HW WIFI WWA
f systemd-sleep)
the system immediately suspended. After nearly a minute I pressed the
power button and the PC instantly resumed.
dmesg reported "Suspended for 43 seconds" which is correct and
network-manager correctly returned to connected state.
---
tj@T300CHI:~$ nmcli g
Today in IRC we were asked if the ficed package is in the 19.04 ISOs. It
isn't so they will fail to boot on AMD Ryzen 3000 CPUs.
Is there a plan to re-build the 19.04 ISOs? If not there ought to at
least be a prominent addition to the 19.04 release notes.
--
You received this bug notification be
auth_admin_keep
yes
# member of sudo and adm
$ groups
tj adm dialout cdrom sudo dip plugdev lpadmin sambashare sbuild lxd libvirtd
two_factor_auth
$ sudo find /etc/polkit-1/ -type f -exec sh -c 'echo === {} ===; cat {}' \; |
egr
Public bug reported:
On 16.04 (XFCE session and others) and possibly later the power-manager
is unable to suspend the system when the user is inactive. A PK user-
agent dialog is presented for the user to authenticate first - and as
this action occurs specifically when the user is idle and away th
/usr/share/polkit-1/actions/org.freedesktop.login1.policy
auth_admin_keep
auth_admin_keep
yes
# member of sudo and adm
$ groups
tj adm dialout cdrom sudo dip plugdev lpadmin samb
Public bug reported:
Hit this again today on 16.04 on a new system. Thought I'd reported this
but obviously not.
lxc-checkconfig erroneously reports:
Kernel configuration not found at /proc/config.gz; searching...
Kernel configuration found at /boot/config-4.13.0-37-lowlatency
--- Namespaces ---
Thanks @Craig - helped someone in #ubuntu on 17.10, and I experimented
on 18.04 and found it is still a problem there too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1584
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1706760
Title:
lightdm/login session fails to resume after dis
Network issue is either kernel or Network Manager.
After the issue occurs we need to see the current 'dmesg' log (which
will show if devices resumed successfully) and /var/log/syslog (where
Network Manager is very verbose).
We also need to know which devices the system has:
lspci -nnk
lsusb
--
The Dbus bluze system config doesn't run, it has "Exec=/bin/false" --
/usr/share/dbus-1/system-services/org.bluez.service It's left to systemd
to activate it via /lib/systemd/system/bluetooth.service
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys
This is a command-line that is useful for manually exercising the
org.bluez DBus activiation. It might reproduce the timeout or otherwise
give useful clues. Command should be all on one line (ignore Launchpad
line wrapping):
dbus-send --system --print-reply --dest=org.bluez /
org.freedesktop.DBus.
I'd concur and suggest that as so many people use openvpn for 'Private
Internet Access' that would be a far more appropriate out-of-the-box VPN
add-on to ship.
That obviously has implications because it would require adding openvpn
to the seed.
PPTP is, I think, a hold over from the dial-up ISP d
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1752417
Title:
Out of the box, Ubuntu
Public bug reported:
apt-cache policy console-setup
console-setup:
Installed: 1.178ubuntu1
Candidate: 1.178ubuntu1
Version table:
*** 1.178ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386
Public bug reported:
apt-cache policy apt
apt:
Installed: 1.6~beta1
Candidate: 1.6~beta1
Version table:
*** 1.6~beta1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
Whilst trying to use virt-manager it reported requiring add
Public bug reported:
On 16.04 and 18.04 hosts on my LAN I've been suffering intermittent loss
of mDNS resolution after devices have been suspended and resumed.
Today I decided to investigate and noticed that on resume the hostname
being advertised is changed.
E.g.
hephaestion.local == Cold Boot
This is still affecting 18.04, I've added a link to an upstream bug
report.
** Bug watch added: github.com/lathiat/avahi/issues #176
https://github.com/lathiat/avahi/issues/176
** Also affects: avahi via
https://github.com/lathiat/avahi/issues/176
Importance: Unknown
Status: Unkno
** Changed in: avahi (Ubuntu)
Status: Confirmed => Triaged
** Changed in: avahi (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bu
ready-connected
keyboard (built-in, USB, etc.)
9. Once the "Paired: yes" message is reported TRUST the BT Keyboard
tj ~ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF XPS1530 [default]
[NEW] Device 00:0A:95:44:37:11 Apple Wireless Keyboard
[NEW] Device 2C:8A:72:15:A8:55 HTC One M8
[NEW]
Having this in 18.04 LTS would be extremely useful for use by hosting
operations to streamline required packages (avoiding the need for clvmd
+ dlm, and in some scenarios corosync).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
In IRC support we've been getting reports about this issue for 17.10;
Can we get the SRU pushed out?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1661869
Title:
maas insta
** Changed in: e2fsprogs (Ubuntu)
Status: Invalid => Triaged
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpa
I'm re-assigning the status and importance based on user reports in IRC
and elsewhere.
See also the related "Ubuntu 16.10 installer sets metadata_csum option
on ext4 partition which is incompatible with other LTS Ubuntu versions"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997
*
An issue for 18.04 too, reported in IRC.
There is a related bug "Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not
support ext4 metadata checksumming"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874
--
You received this bug notification because you are a member of Ubuntu
Touch seed
I'll try to get core dev's attention this week; it'd require a Feature
Freeze Exception (FFE) now to get v1.44.0 into 18.04 but as an LTS it
would be better to have it from the start - and decide on the default
installer/mkfs flags now rather than have users suffer later.
>From that we could possi
** Summary changed:
- Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is
incompatible with other LTS Ubuntu versions
+ Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is
incompatible with older (LTS) e2fsprogs
--
You received this bug notification becau
Public bug reported:
This report is tracking a possible regression caused by the recent
CVE-2018-1116 patches to policykit-1.
On 18.04, since package upgrades on July 23rd, and after the first
reboot since then on Aug 1st, I hit an issue with the primary (sudo,
adm, etc...) user getting Permissio
** Description changed:
This report is tracking a possible regression caused by the recent
CVE-2018-1116 patches to policykit-1.
On 18.04, since package upgrades on July 23rd, and after the first
reboot since then on Aug 1st, I hit an issue with the primary (sudo,
adm, etc...) user ge
journalctl shows the problem with the auid and session values being
0x (-1) when calling a sudo command:
Aug 02 01:18:20 hephaestion.lan.iam.tj audit[5094]: USER_AUTH pid=5094
uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:authentication
acct="tj" exe="/usr/bin/s
I've discovered another quirk:
If my first log-in after booting is at the TTY console (not GUI) the
groups show up correctly there *and* in a terminal in the Xorg GUI
session afterwards.
But if I first log-in to the GUI then log-in to the TTY console both
show only the user group.
--
You receiv
The quirk is more nuanced than I reported above.
This reports groups correctly:
1. GUI login
2. Switch to TTY, login
3. "groups"
4. Switch to GUI
5. Launch Terminal
6. "groups"
This only reports the username:
1. GUI Login
2. Launch Terminal
3. "groups"
4. Switch to TTY, login
5. "groups"
Tests
Looking at the diff between Ubuntu and upstream I noticed Ubuntu 0.105
code isn't adapted for "systemd --user" as described in
https://bugs.freedesktop.org/show_bug.cgi?id=76358
and in the source for the function:
polkit_backend_session_monitor_is_session_active()
** Bug watch added: freedesktop
Looking at the diff between upstream 0.105 and Ubuntu's I happened to
notice the CKDB_PATH (ConsoleKit database path)
/var/run/ConsoleKit/database which seems to be consulted on some
occasions.
On the affected PC which was d-r-u-ed from 16.04 ConsoleKit 0.4.6-5 is
still installed and that database
It seems that /var/run/ConsoleKit directory and its database is only
created by console tty log-ins but not the GUI. There was no directory
after GUI Terminal shell started; only after switching to TTY1.
So it would seem this isn't the cause since PCs without ConsoleKit work
fine.
--
You receive
I've awk-ed a list of the packages Upgraded or Installed on July 28th on
the affected PC (previous upgrade was on July 8th). I've put a ? in
front of those that could be suspect. That list is short:
grep '^?' Hacking/bug-groups-packages-updated.log
? gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubu
Tom tried those things in a VM last night and could reproduce it. On a
suggestion by Robbie Basak but the downgrade didn't solve it, which made
me suggest something in the configuration is being permanently changed.
I'm not going to downgrade the package because I am debugging it and
don't want to
** Summary changed:
- Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
+ Regression due to CVE-2018-1116 (processes not inheriting user's groups )
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p
I think this Debian-reported bug is closely related. The description
certainly sounds very like what I've experienced so far. I'm not linking
it to this bug report until any relationship is clearer.
"policykit-1: please treat background processes (user bus) as part of
active GUI session"
https://
I am beginning to suspect this is an systemd-logind issue. I've been
thinking it's logind but just checked the upgrade packages to/from
versions and cross-checked against the changelogs.
? systemd:amd64 (237-3ubuntu10, 237-3ubuntu10.3),
And we have a major change to logind included in that:
syst
Marc: regular stand-alone install, local authentication via
passwd/shadow/group.
Here's what I see with the 'broken' sequence GUI terminal:
tj ~ id
uid=1000(tj) gid=1000(tj) groups=1000(tj)
tj ~ groups
tj
tj ~ groups $USER
tj : tj root adm disk lp dialout cdrom fl
Marc:
Are you using gdm to log into the graphical session?
lightdm - this is Xubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1784964
Title:
Regression due to
Just noticed the PID tree trace didn't match on the Group: from
proc/$PID/status. Here's the corrected output.
$ pid=$BASHPID; while [[ $pid -ne 0 ]]; do ids=$(grep
'^\(.*id:\|Group\)' /proc/$pid/status); echo -e "cmdline: $(cat
/proc/$pid/cmdline) \n $ids" 2>/dev/null; pid=$(echo $ids | awk '{pri
And this is the same output using the 'correct' scenario by logging into
the TTY console first.
cmdline: -bash
Tgid: 3516
Ngid: 0
Pid:3516
PPid: 3488
TracerPid: 0
Uid:1000100010001000
Gid:1000100010001000
Groups: 0 4 6 7 20 24 25 27 29 44 46 100 108
Just noticed in $HOME/.xsession-errors the following:
(polkit-gnome-authentication-agent-1:4029): polkit-gnome-1-WARNING **:
15:04:54.498: Failed to register client:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files
** Summary changed:
- Regression due to CVE-2018-1116 (processes not inheriting user's groups )
+ Regression due to CVE-2018-1116 (processes not inheriting user's
supplementary groups )
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
This issue effects a manual (debootstrap) installation of 18.04.1.
Ethernet devices are unmanaged by NetworkManager until a netplan
configuration is added.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubu
I suspect the recent Bionic changes have broken the install. At least
I'm seeing the following:
$ sudo apt-get upgrade
Reading package lists... 0%
Reading package lists... 100%
Reading package lists... Done
Building dependency tree... 0%
Building dependency tree... 0%
Building dependency tr
An strace shows:
$ sudo strace -o /tmp/dpkg.log -f dpkg -i /var/cache/apt/archives/libc6
-dev-armhf-cross_2.27-3ubuntu1cross1.1_all.deb
$ grep -E '(Mcrt1|error processing)' /tmp/strace-dpkg.log
22528 lstat("/usr/arm-linux-gnueabihf/lib/Mcrt1.o", 0x7ffef13bf320) = -1 ENOENT
(No such file or dir
1 - 100 of 300 matches
Mail list logo
