@chesterman86 Download the light-locker-settings_python-psutil-newer-
than-2.0.0.diff file from post #3. Then run;
sudo patch
/usr/share/light-locker-settings/light-locker-settings/light-locker-settings.py
//light-locker-settings_python-psutil-newer-than-2.0.0.diff
Make sure you use the correc
Public bug reported:
This is related to the bug "remote file systems hang on shutdown, D-BUS
stops too early" here
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1438612. This bug's
status is a "won't fix" because I believe it has to do with the network-
manager.service file in /lib/systemd/s
@stormhike do you run Upstart or systemd? I'm just wondering if this
works on systemd since you're modifying init scripts and I thought
systemd doesn't look at these.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
We're talking about a core Linux service here, NFS, and I've seen bug
reports of the same exact issue going back years and it's still not
fixed in 16.04. It's passed between tons of different maintainers; the
systemd people, the dbus people, the NM people, no one has committed to
getting this to wo
The open source AMD drivers are not a solution; I was obliged to switch
to proprietary drivers because X/lightdm kept crashing on startup
leaving me only with VTs to trouble shoot. Now with the proprietary
drivers I can't see the VTs.
The open source drivers every once in a while stopped loading t
I can confirm that this bug is fixed if you install the latest 15.302
drivers from http://support.amd.com/en-us/download/linux and also
carefully follow the Installer Notes here http://www2.ati.com/relnotes
/amd-catalyst-graphics-driver-installer-notes-for-linux-operating-
systems.pdf.
After unins
Public bug reported:
For the life of me I cannot get the parameter crypt:dev=/dev/vdb to work
in /etc/overlayroot.conf.
I have tried the line
overlayroot=crypt:dev=/dev/vdb,pass=somepass,mkfs=0
Which works when I create the LUKS device ahead of time, and set the
passphrase 'somepass'. But when
Also, I am not getting any logging output in
"/dev/.initramfs/${MYTAG}.log". The .initramfs directory is never
created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634310
Title:
crypt:dev=/dev/vd
This is on a fresh Ubuntu 16.04 cloud instance at an OpenStack host,
launched from the typical Ubuntu cloud image with overlayroot already
included.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/163431
I can confirm that the crypt parameter without pass= set isn't working
in Ubuntu 16.04. At least in the cloud images that I've tested.
I tried it on a freshly launched Ubuntu 14.04 instance and had no
problems setting overlayroot=crypt:dev=/dev/vdb and getting everything
as expected including logg
@peter-sevemark Yep, same exact problems with WICD means it's the
wireless driver/kernel. Probably why no one is looking at this bug
seriously.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Ti
11 matches
Mail list logo
