The new version 18.04.3 in bionic-proposed works fine on my other
laptop, too, so I'd call this fixed.
** Changed in: xubuntu-default-settings (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have tested the most recent 18.04.3 version on my work laptop and the
problem appears to have been solved. Haven't tested it on my personal
laptop yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1751414 ***
https://bugs.launchpad.net/bugs/1751414
On Xubuntu, can you try downgrading the package xubuntu-default-settings
from version 18.04.2 to version 18.04.1? Maybe it's related to what I'm
seeing in bug #1752798
(you can find the older package here:
Here's the lightdm.log of the system run with the package version that
prevents booting to Desktop.
Note that it shows that it permanently retries starting lightdm until
the user has had enough and reboots or powers off the system (hence the
section at the end that looks different).
**
For comparision, here's my lightdm.log with the previous package version
where it boots to Desktop successfully.
** Attachment added: "lightdm.log of succeeding run (xubuntu-default-settings
18.04.1)"
Note that on my personal laptop, there's a difference in the Xorg.0.log
regarding the detection of the NVidia gfx board, the failing run using
xubuntu-default-settings package version 18.04.2 and the succeeding run
using version 18.04.1:
$ diff -u <( sed -e 's/^\[[^]]*\] //'
Public bug reported:
Upon upgrading the package from version 18.04.1 to 18.04.2 and
subsequent reboot, the system is rendered unable to start lightdm and
gets stuck in an endless loop retrying.
This happened on 2 laptops, one company machine and one personal
machine.
I'm running bionic beaver
Public bug reported:
Apparently, gitlint needs the Python "sh" package:
$ gitlint --help
Traceback (most recent call last):
File "/usr/bin/gitlint", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3144,
in
I think there is a better solution (involving disabling recordfail in
the affected cases, which is LVM for me).
I believe that the correct thing to use to check for LVM or RAID is
grub-probe's abstraction target. This returns a list of possible
abstractions below the filesystem level (or an empty
@wiley.coyote: I wrote the patch to err on the conservative side, so I
deliberately avoided matching for *$check_abstraction*, so if grub-
probe spat out (contrived example) a list of braid ponytail, it would
not accidentally match on *raid*.
So it seems that for you, grub-probe
@schneibva: Can you please try my patch on your /etc/grub.d/00_header
file and manually add the word raid to the for-in list?
I.e. replace this line:
for check_abstraction in lvm ; do
with that:
for check_abstraction in lvm raid ; do
And afterwards run update-grub, of course. (If you
11 matches
Mail list logo
