[Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
@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 Title: cannot view wifi networks after re-enabling wifi To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634310] Re: crypt:dev=/dev/vdb parameter does not work with randomly generated passphrase
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 logging in /dev/.initramfs/${MYTAG}.log.
Then I did the same thing on a fresh Ubuntu 16.04 instance and couldn't
use the same overlayroot=crypt:dev=/dev/vdb to get the expected result.
Then I just tried overlayroot=/dev/vdb, without encryption, after
creating a filesystem on the extra volume and that worked, but I still
don't get any logging.
--
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/vdb parameter does not work with randomly generated
passphrase
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1634310/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634310] Re: crypt:dev=/dev/vdb parameter does not work with randomly generated passphrase
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/1634310 Title: crypt:dev=/dev/vdb parameter does not work with randomly generated passphrase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1634310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634310] Re: crypt:dev=/dev/vdb parameter does not work with randomly generated passphrase
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/vdb parameter does not work with randomly generated
passphrase
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1634310/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634310] [NEW] crypt:dev=/dev/vdb parameter does not work with randomly generated passphrase
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 I try overlayroot=crypt:dev=/dev/vdb,mkfs=1 or just overlayroot=crypt:dev=/dev/vdb I get no overlay after reboot. I have also tried the "debug=1" parameter and I'm not getting any debug output either. Where are the logs and/or where should I be able to see the debug output? As Dustin has so eloquently documented, it defeats the privacy of your encryption if you have to specify the passphrase in clear text in your unencrypted read-only directory. So the only way I will be using this is if I can use the simple "overlayroot=crypt:dev=/dev/vdb" one-liner and have the passphrase generated automatically on boot. ** Affects: cloud-initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: dm-crypt overlayroot -- 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/vdb parameter does not work with randomly generated passphrase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1634310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615973] Re: Remote filesystems hang shutdown because network-manager stops too early
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 work consistently. Unreal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615973 Title: Remote filesystems hang shutdown because network-manager stops too early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early
@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.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615973] [NEW] Remote filesystems hang shutdown because network-manager stops too early
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/system/. The problem is with something like the following in /etc/fstab: 172.100.1.2:/mnt/share /mnt/nfsnfs noauto,_netdev,noatime,nofail,x-systemd.automount,x-systemd.device- timeout=10,timeo=14,x-systemd.idle-timeout=1min,rsize=8192,wsize=8192 0 0 This is in the latest systemd package on Xubuntu 16.04. The system hangs on shutdown indefinitely and I get the following output from journalctl in a debug shell on shutdown: Aug 23 01:23:41 ubuntu-user systemd[1]: Stopped LSB: Start NTP daemon. Aug 23 01:23:41 ubuntu-user systemd[1]: Stopped LSB: Record successful boot for GRUB. Aug 23 01:23:41 ubuntu-user systemd[1]: Stopped LSB: disk temperature monitoring daemon. Aug 23 01:23:41 ubuntu-user systemd[1]: Stopped LSB: Set the CPU Frequency Scaling governor to "ondemand". Aug 23 01:23:41 ubuntu-user systemd[1]: Removed slice User Slice of ubuntu-user. Aug 23 01:23:41 ubuntu-user avahi-daemon[2584]: Got SIGTERM, quitting. Aug 23 01:23:41 ubuntu-user systemd[1]: Stopping Login Service... Aug 23 01:23:41 ubuntu-user avahi-daemon[2584]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fdcb:6a3d:3361:0:883:3f94:65f7:8f2d. Aug 23 01:23:41 ubuntu-user NetworkManager[2678]: [1471904621.5584] device (wlp1s0): state change: activated -> deactivating (reason 'connection-removed') [100 110 38] Aug 23 01:23:41 ubuntu-user avahi-daemon[2584]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 172.100.1.231. Aug 23 01:23:41 ubuntu-user systemd[1]: Stopping Avahi mDNS/DNS-SD Stack... Aug 23 01:23:41 ubuntu-user avahi-daemon[2584]: avahi-daemon 0.6.32-rc exiting. Aug 23 01:23:41 ubuntu-user NetworkManager[2678]: [1471904621.5585] manager: NetworkManager state is now DISCONNECTING Aug 23 01:23:41 ubuntu-user systemd[1]: Stopping CUPS Scheduler... Aug 23 01:23:41 ubuntu-user systemd[1]: Stopped /etc/rc.local Compatibility. Aug 23 01:23:41 ubuntu-user systemd[1]: Removed slice system-getty.slice. Aug 23 01:23:41 ubuntu-user systemd[1]: Stopped Avahi mDNS/DNS-SD Stack. Aug 23 01:23:41 ubuntu-user NetworkManager[2678]: [1471904621.5683] device (wlp1s0): state change: deactivating -> disconnected (reason 'connection-removed') [110 30 38] Aug 23 01:23:41 ubuntu-user systemd[1]: Stopped CUPS Scheduler. Aug 23 01:23:41 ubuntu-user NetworkManager[2678]: [1471904621.5768] dhcp4 (wlp1s0): canceled DHCP transaction, DHCP client pid 3108 Aug 23 01:23:41 ubuntu-user NetworkManager[2678]: [1471904621.5768] dhcp4 (wlp1s0): state changed bound -> done Aug 23 01:23:41 ubuntu-user NetworkManager[2678]: [1471904621.5777] dhcp6 (wlp1s0): canceled DHCP transaction, DHCP client pid 3320 Aug 23 01:23:41 ubuntu-user NetworkManager[2678]: [1471904621.5778] dhcp6 (wlp1s0): state changed bound -> done Aug 23 01:23:41 ubuntu-user wpa_supplicant[2785]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=00:25:9c:13:f7:6d reason=3 locally_generated=1 Aug 23 01:23:41 ubuntu-user NetworkManager[2678]: [1471904621.5886] dns-mgr: Writing DNS information to /sbin/resolvconf Aug 23 01:23:41 ubuntu-user wpa_supplicant[2785]: p2p-dev-wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Aug 23 01:23:42 ubuntu-user thermald[2590]: terminating on user request .. Aug 23 01:23:42 ubuntu-user kernel: wlp1s0: deauthenticating from 00:25:9c:13:f7:6d by local choice (Reason: 3=DEAUTH_LEAVING) Aug 23 01:23:42 ubuntu-user systemd[1]: Stopped LXDE Display Manager. Aug 23 01:23:42 ubuntu-user systemd[1]: Starting Show Plymouth Power Off Screen... Aug 23 01:23:42 ubuntu-user systemd[1]: Stopping Permit User Sessions... Aug 23 01:23:42 ubuntu-user systemd[1]: Stopped Copies the configs for the ChromeOS touchpad driver. Aug 23 01:23:42 ubuntu-user systemd[1]: Stopped Permit User Sessions. Aug 23 01:23:42 ubuntu-user systemd[1]: Stopped target Remote File Systems. Aug 23 01:23:42 ubuntu-user systemd[1]: Unmounting /mnt/nfs... Aug 23 01:23:42 ubuntu-user systemd[1]: Stopped Login Service. Aug 23 01:23:42 ubuntu-user systemd[1]: Stopped target User and Group Name Lookups. Aug 23 01:23:43 ubuntu-user systemd[1]: Received SIGRTMIN+20 from PID 3903 (plymouthd). Aug 23 01:23:43 ubuntu-user systemd[1]: Started Show Plymouth Power Off Screen. Aug 23 01:23:43 ubuntu-user systemd[1]: Stopped Thermal Daemon Service. Aug 23 01:23:44 ubuntu-user systemd[1]: Received SIGRTMIN+20 from PID 3903 (plymouthd). Aug 23 01:23:46 ubuntu-user kernel: nfs: server 172.100.1.3 not responding, still trying Aug 23 01:23:51 ubuntu-user NetworkManager[2678]: [1471904631.6437] dns-mgr: Removing DNS information from /sbin/resolvconf Aug 23 01:23:51 ubuntu-user NetworkManager[2678]: [1471904631.6766] manager: NetworkManager state is now DISCONNECTE
[Bug 1559735] Re: light-locker-settings does not start
@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 correct which you downloaded. The resulting output in your terminal should say "patching file light-locker-settings.py" and Light Locker Settings should work. If you couldn't patch it just try to edit the py file manually in the /usr/share/... directory by removing the lines with a - in front and adding lines with a + in front from the diff file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559735 Title: light-locker-settings does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1559735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless
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 uninstalling the fglrx which I downloaded from the repository and then installing the new ones from AMD I am able to switch to any Virtual Terminals via CTRL + ALT + F1, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470862 Title: When using fglrx module, the virtual consoles are blank and useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1470862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless
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 the lightdm greeter. Reinstalling/reconfiguring lightdm and other steps didn't fix the problem. The /var/log/lightdm logs showed errors "Segmentation fault" in the x-0.log and "Process terminated with signal 6" in the lightdm.log. My system: $ uname -a Linux trustycrucial 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ lspci -nn | grep VGA 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] 02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470862 Title: When using fglrx module, the virtual consoles are blank and useless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1470862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
