** 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.
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
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.
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
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
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
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
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
** 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
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:
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:
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
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:
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
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
** 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
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
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
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
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
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
Is part of the issue here that some (most) initramfs-tools created
images have an uncompressed early CPU microcode firmware prefixed ?
That is stored as ASCII CPIO which is why Con see's that reported by
'file' since that tool checks the magic signatures at start of a file.
binwalk reveals more d
I've worked with upstream AMD and we've fixed the problem in in xf86
-video-amdgpu. As soon as that is available in the upstream repository
I'll prepare a cherry-pick update to 20.04.
I suspect we also need to consider an SRU patch to 18.04 ?
--
You received this bug notification because you are
** Also affects: linux via
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bug
Urgh, should have written "With the help and suggestions of 'brainwash'
and 'bluesabre' on #xubuntu-devel..."
** Summary changed:
- Regression: block staircase display with side-by-side monitors
+ Regression: block staircase display with side-by-side monitors of different
pixel widths
** Descri
With the help and suggestions of Bluesabre on #xubuntu-devel we've
tracked it down to a recent change in xfwm4 where it switched from using
glx to xpresent:
https://git.xfce.org/xfce/xfwm4/commit/?id=23900123ad8418149897a094d1096d6ecb984d3c
which seems to be a bug in the driver as mentioned orgin
** Also affects: xfwm4 (Ubuntu)
Importance: Undecided
Status: New
--
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 staircase displa
Reproducing this:
$ xrandr -d :0.0 --output HDMI-A-0 --left-of eDP
$ xrandr -d :0.0 --output HDMI-A-0 --right-of eDP
No problem with:
$ xrandr -d :0.0 --output HDMI-A-0 --above eDP
$ xrandr -d :0.0 --output HDMI-A-0 --below eDP
The affected and unaffected laptops each have identical kernel log
Timo: yes, sorry, I think I got a bit confused about packages due to
lack of sleep. I've reported this against xserver-xorg-video-amdgpu for
now although looking at the apt history it wasn't updated.
I'm not too familiar with the Xorg internals so any pointers on
potential culprits would be welcom
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357351/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357359/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357358/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357352/+files/Lsusb.txt
--
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/
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357362/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357364/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.launchp
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357363/+files/Xrandr.txt
--
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.ne
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357360/+files/UdevDb.txt
--
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.ne
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357361/+files/XorgLog.txt
--
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
Tim
--
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 staircase display with side-by-side monitors
Status in libxcb package in Ubuntu:
New
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357356/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357357/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357355/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357353/+files/Lsusb-t.txt
--
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
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357354/+files/Lsusb-v.txt
--
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
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357348/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
ht
apport information
** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided
Status: New
** Tags added: apport-collected focal ubuntu
** Description changed:
Two identical Lenovo E495 laptops with 20.04 installed. The problem
occurred initially on the laptop that i
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357347/+files/DpkgLog.txt
--
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
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357350/+files/Lspci.txt
--
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/
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357349/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1873895/+attachment/5357346/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs
These are the packages I've tested via a downgrade:
$ apt list --upgradeable
Listing... Done
libxcomposite1/focal 1:0.4.5-1 amd64 [upgradable from: 1:0.4.5-0ubuntu1]
libxcomposite1/focal 1:0.4.5-1 i386 [upgradable from: 1:0.4.5-0ubuntu1]
libxdamage1/focal 1:1.1.5-2 amd64 [upgradable from: 1:1.1.5-
I'm attaching the complete list of packages upgraded on the second
laptop that triggered this bug.
The total list is over 300 packages. I've prefixed the unlikely package
with #. That leaves 77 possibles all related to X server or display
drivers.
** Attachment added: "List of upgraded packages w
The packages upgraded on the second laptop that are libx related are:
$ grep 'Upgrade: hunspell' /var/log/apt/history.log | grep -o 'libx[^ ]*'
libxml2-utils:amd64
libxml2:amd64
libxatracker2:amd64
libxcomposite1:amd64
libxcomposite1:i386
libxml2-dev:amd64
libxfixes3:amd64
libxfixes3:i386
libxdam
Public bug reported:
Two identical Lenovo E495 laptops with 20.04 installed. The problem
occurred initially on the laptop that is having package upgrades applied
regularly.
With dual monitors and the external monitor placed left or right the
display has a blocked staircase effect shown in the att
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
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
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
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
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
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
: 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
** 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
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
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
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}/
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
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
** 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
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);
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
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
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
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
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
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
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
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
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
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
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
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
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:
** 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
**
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
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
*** This bug is a duplicate of bug 1817308 ***
https://bugs.launchpad.net/bugs/1817308
I installed the fix. Both computers and both printers back to normal.
Life is good. Thanks!
On Sat, Feb 23, 2019 at 10:55 AM Launchpad Bug Tracker <
1817...@bugs.launchpad.net> wrote:
> Status changed to
Public bug reported:
This has happened to both of my computers running xubuntu. My first
computer, I updated yesterday. The second computer did not exhibit the
problem this morning. Once I updated the software with Software
Updater, it acquired the same issue.
ProblemType: Bug
DistroRelease: U
Julian - I hadn't realised there are two gpgv's!
Having found apt's own /usr/lib/methods/gpgv
I have been able to create a shell wrapper that can feed it the expected
request headers and parse the response headers to ensure a GPGVOutput:
GOODSIG ...
It's a proof of concept right now; if this app
)
E: Unable to lock directory /var/lib/apt/lists/
Investigating further I discovered a 3 day old cron job is hung:
$ date
Tue 6 Nov 08:50:20 GMT 2018
$ ps -efly | grep apt
S tj 31068 8492 0 80 0 1016 5384 pipe_w 08:48 pts/400:00:00
grep --color=auto apt
S root 31280 1
I've created a shell wrapper than might be useful for this called
"gpgpv-multisig" which is a multi-call executable. Given /usr/bin/gpgv-
multisig
ln -s gpgv-multisig /usr/bin/gpgv-aptkeys
and called as 'gpgv-aptkeys' it will assume the keyring to be used is
/etc/apt/trusted.gpg (set by APT_KEYRI
*** This bug is a duplicate of bug 1781418 ***
https://bugs.launchpad.net/bugs/1781418
This appears to be due to CVE patches in kwallet-pam not policykit-1.
Marking this as a duplicate of
Bug #1781418 "User not being initialized correctly on login"
It affects lightdm due to its /etc/pam.d/li
I'm still seeing the issue and have followed up in bug #1797557
--
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/1769657
Title:
update toolchain packages for bionic
Status
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
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
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
** 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
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
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
1 - 100 of 300 matches
Mail list logo
