I've seen the same behaviour after an upgrade from 12.04 to 14.04. Login was
still possible but the screen did not unlock. I had this message in
/var/log/auth.log:
hostname unix_chkpwd[26503]: could not obtain user info (username)
For me this was caused by wrong file permissions on /etc/shadow.
This bug is still present (Ubuntu 14.04, 14.10 and 15.04).
Upstream bug report: https://github.com/npm/npm/issues/4530
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211104
Title:
npm package
Apparently this patch never made it into udisks2 and therefore shows up
again in Ubuntu 14.04 and later.
** Also affects: udisks2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>What is confusing however in the ps outputs attached is that in all three
>process outputs:
> - plymouthd in boot mode is still running
> - /bin/plymouth quit has not completed
I experience the same issue. This also causex 'plymouth --ping' to hang
indefinitely. If I kill plymouthd manually
Thanks for the clarification, I did not notice that MAAS does not create
A records for ... If I create them manually
mod_authz_host succeeds.
By the way here is the debug log output from Apache's error.log:
[Sat Jul 09 11:53:57.366338 2016] [authz_host:error] [pid 26131:tid
139886547891968]
Still present in 16.04 LTS. Lmod http://packages.ubuntu.com/xenial/lmod
might be a good alternative.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1056014
Title:
Improper reference to modulecmd in
** Changed in: maas-images
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647485
Title:
NVMe symlinks broken by devices with spaces in model or serial strings
To
** Also affects: maas-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647485
Title:
NVMe symlinks broken by devices with spaces in model or serial
Note that there is a Ubuntu package of 4.12.1 available now
http://packages.ubuntu.com/zesty/xfce4-settings which can be installed
at least without dependency issues on Ubuntu 16.04.
The upstream commit that fixes the issue is here
Public bug reported:
On Ubuntu 18.04
linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
According to https://www.mail-archive.com/ceph-
us...@ceph.io/msg00940.html the same happens on Disco with this kernel
version.
Processes that read data from CephFS get stuck, the system becomes
It looks like this has been fixed here:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=3b931173c97b0d73f80ea55b72bb2966a246167f
and here:
Public bug reported:
The unit file /lib/systemd/system/gssproxy.service contains the
following line
Environment=KRB5RCACHEDIR=/var/lib/gssproxy/rcache
The directory /var/lib/gssproxy/rcache however does not exist, and this
leads to authentication failures. In my case with apache2, in the
PS: this is a Ubuntu 20.04 container image. The directory
/var/lib/gssproxy/clients exists. Is this the directory that should be
referenced in the unit file instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The file /etc/xdg/autostart/xscreensaver.desktop belongs to the xfce4-session
package, see
/var/lib/dpkg/info/xfce4-session.conffiles
On a fresh Xubuntu 20.04 installation the light-locker package is not
installed, that would explain why not more people are affected by this.
--
You received
Looks like this upstream bug report
https://github.com/DisplayLink/evdi/issues/181
Seems to be triggered by disabling the laptop display. Two possible
workarounds:
a) keep laptop display enabled
b) disable compositor (in my case with Xfce, settings -> window manager
tweaks -> compositor ->
Public bug reported:
Firefox version information below. I don't think replacing the deb
version with the snap was a good idea. If your home directory is outside
of /home (quite common for central home directories on a file server
mounted via NFS or some other way for example) you cannot use
*** This bug is a duplicate of bug 1776800 ***
https://bugs.launchpad.net/bugs/1776800
I know that there are workarounds with bind-mounts and whatnot, but
workarounds are not a feasible solution for a LTS release.
--
You received this bug notification because you are a member of Ubuntu
How can this be sitting around here for 3 years unassigned with *high*
priority? And then apparently it's not even considered a blocker for
replacing Firefox in Ubuntu 22.04 with the snap. Is it really that hard
to fix or is just nobody paying attention to it?
** Also affects: firefox (Ubuntu)
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776800
Title:
Unable to start snap applications if user's home
Hi Alberto, I'm glad to hear that there is some progress. Happy to test
patches if you need feedback on something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776800
Title:
Unable to start snap
20 matches
Mail list logo
