This issue is now fixed upstream.
https://github.com/util-linux/util-linux/commit/304b4dc4936b115ca33af5325c3b04d0997c1353
https://github.com/util-linux/util-linux/commit/c9671a3cf7738bb81e1cbef2f56485a36c6e7623
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I got a reply on the util-linux issue tracker
https://github.com/util-linux/util-
linux/issues/1704#issuecomment-1144962011
So it seems te a systemd issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
The previous comment was a red herring.
It turns out it doesn't matter if uuidd is self compiled or not. The
system uuidd also works perfectly if it is started in the terminal
simply by
sudo uuidd
However systemd starts uuidd with
/usr/sbin/uuidd --socket-activation
which probably makes a diff
I forgot to mention that a self compiled uuidd does not suffer from this
bug(?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976630
Title:
uuidd appears to be broken on Ubuntu 20.04 LTS
To manag
Public bug reported:
uuidgen -t returns a correct result when uuidd is _not_ running. See the
following transcript
vdbergh@pl:~/$ sudo systemctl stop uuidd.service uuidd.socket
vdbergh@pl:~/$ uuidgen -t
ef485202-e275-11ec-b7ab-448500dea459 < (correct: last part is the MAC
addr
I have the same behaviour as andy1. Lid close behaves correctly (no
password) but after resuming from suspend via the menu in the right
corner of the screen a password is needed.
This is Ubuntu 9.10 on 64bit core duo.
--
No GUI method to disable screen lock on lid close event
https://bugs.la
I have some useful info to contribute I think.
I just got myself a 340Gb IDE drive. The bios claims it is only on a 139Gb
drive but the Karmic installer recognized the full
drive and the installer seemed to work fine. However when trying to boot into
my freshly installed sytem I got the error d
Sorry for the spam but I would like to add that this is definitely a
problem. I just got a new laptop with a 1600x1000 resolution and
resizing windows has become very frustrating.
--
Resizing windows by grabbing window borders is difficult
https://bugs.launchpad.net/bugs/160311
You received this
Yes this problem still exists in karmic. After plugging in a camera an
incomprehensible mess of error dialogs is spawned
by the foto app du jour that pops up (either f-spot of gthumb) and photo's
cannot be imported.
After reading the above bug reports I realize this is because gvfs has mounted
