[Touch-packages] [Bug 1725404] [NEW] 10-finger typing: Ctrl+Alt does not work as "AltGr for left hand"
Public bug reported: Touch typing (or 10-finger typing) requires to utilize both hands to maximize writing speed. Unfortunately, Ubuntu currently doesn't support a left-hand alternative to AltGr. Related questions: StackOverflow: https://askubuntu.com/questions/919257/ctrl-alt-not-working-on-ubuntu-but-does-on-windows Launchpad: https://answers.launchpad.net/ubuntu/+question/657015 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725404 Title: 10-finger typing: Ctrl+Alt does not work as "AltGr for left hand" Status in xorg package in Ubuntu: New Bug description: Touch typing (or 10-finger typing) requires to utilize both hands to maximize writing speed. Unfortunately, Ubuntu currently doesn't support a left-hand alternative to AltGr. Related questions: StackOverflow: https://askubuntu.com/questions/919257/ctrl-alt-not-working-on-ubuntu-but-does-on-windows Launchpad: https://answers.launchpad.net/ubuntu/+question/657015 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1725404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04
> PS: short domains also don't work. Only FQDNs. Fixed by changing: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns to hosts: files mdns4_minimal [NOTFOUND=return] dns -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684854 Title: The default behaviour for search domains changed from 16.10 to 17.04 Status in network-manager package in Ubuntu: Confirmed Bug description: Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default behaviour for search domains changed. By default systemd-resolved does not use the domain supplied by DHCP as a search domain. So network-manager should at least have an option to tell systemd- networkd to change it's behaviour. In systemd-networkd the corresponding option is named "UseDomains". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1684854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04
I added search domains in '/etc/resolvconf/resolv.conf.d/base'. Now, I have at least named access to servers outside of our internal network. Is there some checkbox in settings to enable searchdomains coming from dhcp? PS: short domains also don't work. Only FQDNs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684854 Title: The default behaviour for search domains changed from 16.10 to 17.04 Status in network-manager package in Ubuntu: Confirmed Bug description: Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default behaviour for search domains changed. By default systemd-resolved does not use the domain supplied by DHCP as a search domain. So network-manager should at least have an option to tell systemd- networkd to change it's behaviour. In systemd-networkd the corresponding option is named "UseDomains". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1684854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716014] [NEW] Create Volatile Files and Directories without time limit
Public bug reported: I installed Ubuntu 17.04 on Lenovo X270. Works fine so far. But the boot process **sometimes** hangs. Please note the attachment. I don't know if that contributes to the issue, but on the X270, the Trackpoint is very slow. The proposed solution around the Web is: ~# vim /etc/tmpfiles.d/trackpoint.conf #and add the following lines w /sys/devices/platform/i8042/serio1/serio2/speed - - - - 255 w /sys/devices/platform/i8042/serio1/serio2/sensitivity - - - - 200 then ~# systemd-tmpfiles --prefix=/sys --create ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Boot-up Error" https://bugs.launchpad.net/bugs/1716014/+attachment/4946607/+files/IMG_20170908_180312.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1716014 Title: Create Volatile Files and Directories without time limit Status in systemd package in Ubuntu: New Bug description: I installed Ubuntu 17.04 on Lenovo X270. Works fine so far. But the boot process **sometimes** hangs. Please note the attachment. I don't know if that contributes to the issue, but on the X270, the Trackpoint is very slow. The proposed solution around the Web is: ~# vim /etc/tmpfiles.d/trackpoint.conf #and add the following lines w /sys/devices/platform/i8042/serio1/serio2/speed - - - - 255 w /sys/devices/platform/i8042/serio1/serio2/sensitivity - - - - 200 then ~# systemd-tmpfiles --prefix=/sys --create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639555] [NEW] Same Indicator Icon for "Networking on" and "Ethernet Network on"
Public bug reported: Coming from 14.04, I was used to see a difference between "no connection at all" and "wired connection". As of Ubuntu 16.04, the indicator icons are the same for "wired connection" and "networking on but no connection at all". Working in Web Development, this not-difference already proved to be confusing, when I had no Ethernet connection but the icons suggests that I am online. Do you think you could either be changed back OR provide two different indicator icons for "wired on" and "networking on but offline"? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: Coming from 14.04, I was used to see a difference between "no connection at all" and "wired connection". As of Ubuntu 16.04, the indicator icons are the same for "wired connection" and "networking on but no connection at all". Working in Web Development, this not-difference already proved to be confusing, when I - had no Ethernet connection but the icons suggests, I am online. + had no Ethernet connection but the icons suggests that I am online. Do you think, that could either be changed back OR you can provide two different icons for "Wired on" and "Networking on but offline"? ** Description changed: Coming from 14.04, I was used to see a difference between "no connection at all" and "wired connection". As of Ubuntu 16.04, the indicator icons are the same for "wired connection" and "networking on but no connection at all". Working in Web Development, this not-difference already proved to be confusing, when I had no Ethernet connection but the icons suggests that I am online. - Do you think, that could either be changed back OR you can provide two - different icons for "Wired on" and "Networking on but offline"? + Do you think you could either be changed back OR provide two different + indicator icons for "wired on" and "networking on but offline"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1639555 Title: Same Indicator Icon for "Networking on" and "Ethernet Network on" Status in network-manager package in Ubuntu: New Bug description: Coming from 14.04, I was used to see a difference between "no connection at all" and "wired connection". As of Ubuntu 16.04, the indicator icons are the same for "wired connection" and "networking on but no connection at all". Working in Web Development, this not-difference already proved to be confusing, when I had no Ethernet connection but the icons suggests that I am online. Do you think you could either be changed back OR provide two different indicator icons for "wired on" and "networking on but offline"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1639555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported
Still not working on Ubuntu 16.04. :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/388553 Title: Wi-Fi Protected Setup (WPS) not supported Status in Ayatana Design: New Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: As the title the Wi-Fi Protected Setup (WPS) is not supported by NetworkManager (but is supported by wpa_supplicant). The WPS WI-Fi standard is implementated in various newer access points and allow user to configure the access point in just a few of steps and do all configuring process very simple. Specifications: http://www.wi-fi.org/wifi-protected-setup/ To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.
Indeed it does. Glad to see the bug persists even on 16.04 and its not just a mal-configuration on my side. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting. Status in systemd package in Ubuntu: Confirmed Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.
@Hans To confirm that it's the same issue, you might replay the instructions Martin gave at #12: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/comments/12 It should reveal the triggered assertion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting. Status in systemd package in Ubuntu: Confirmed Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.
@Martin Is there some update on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting. Status in systemd package in Ubuntu: New Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.
@Martin I'd be glad to assist if you require more information to make it reproducible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting. Status in systemd package in Ubuntu: New Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.
Nice. Is there something else I can do here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting. Status in lxd package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.
Tested. However, it does not fix the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting. Status in lxd package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown
Thanks for looking at this, Martin. Minor correction: I work with Ubuntu 14.04. Containers are Wily. > I suppose your journal output in comment #6 was from *after* you did "lxc > stop"? Correct, it was *after* "lxc stop" (resp. all the other variants) >>> lxc exec test -- ls -l >>> /lib/systemd/system/sigpwr.target.wants/sigpwr-container-shutdown.service >>> /lib/systemd/system/sigpwr-container-shutdown.service -rw-r--r-- 1 root root 153 Oct 15 11:34 /lib/systemd/system/sigpwr-container-shutdown.service lrwxrwxrwx 1 root root 36 Oct 15 12:02 /lib/systemd/system/sigpwr.target.wants/sigpwr-container-shutdown.service -> ../sigpwr-container-shutdown.service >>> lxc exec test -- systemd-detect-virt lxc >>> lxc stop test ^C>>>lxc exec test -- systemctl status -l sigpwr-container-shutdown.service ^C The last call basically hangs (also without the -l option). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: [systemd] SIGPWR doesn't always lead to shutdown Status in lxd package in Ubuntu: Triaged Status in systemd package in Ubuntu: Incomplete Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown
Done. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+attachment/4528051/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: [systemd] SIGPWR doesn't always lead to shutdown Status in lxd package in Ubuntu: Triaged Status in systemd package in Ubuntu: Incomplete Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown
>>> uname -a Linux mexico 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux >>> lxc exec test -- uname -a Linux test 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux journalctl only shows messages related to container startup: >>> lxc exec test -- journalctl -- Logs begin at Mon 2015-11-30 21:03:37 UTC, end at Mon 2015-11-30 21:03:53 UTC. -- Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) is currently using 8.0M. Maximum allowed usage is set to 799.2M. Leaving at least 1.1G free (of currently available 7.7G of space). Enforced usage limit is thus 799.2M. Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) is currently using 8.0M. Maximum allowed usage is set to 799.2M. Leaving at least 1.1G free (of currently available 7.7G of space). Enforced usage limit is thus 799.2M. Nov 30 21:03:37 test systemd-journal[223]: Journal started Nov 30 21:03:37 test systemd-remount-fs[108]: /bin/mount for / exited with exit status 1. Nov 30 21:03:37 test systemd-remount-fs[108]: mount: can't find LABEL=cloudimg-rootfs Nov 30 21:03:37 test mount[133]: mount: permission denied Nov 30 21:03:37 test loadkeys[145]: Couldn't get a file descriptor referring to the console Nov 30 21:03:37 test apparmor[157]: lxc Nov 30 21:03:37 test apparmor[157]: * Not starting AppArmor in container Nov 30 21:03:37 test apparmor[157]: ...done. Nov 30 21:03:37 test systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: Failed to start Set console keymap. Nov 30 21:03:37 test systemd[1]: console-setup.service: Unit entered failed state. Nov 30 21:03:37 test systemd-journal[223]: Forwarding to syslog missed 1 messages. Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed with result 'exit-code'. Nov 30 21:03:37 test systemd[1]: Started LSB: AppArmor initialization. Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Nov 30 21:03:37 test systemd[1]: Started Load/Save Random Seed. Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control group: Invalid argument Nov 30 21:03:37 test systemd[1]: Started Clean up any mess left by 0dns-up. Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on /lxc/test/system.slice/resolvconf.service: Permission denied Nov 30 21:03:37 test systemd[1]: Starting Nameserver information manager... Nov 30 21:03:37 test sh[185]: Segmentation fault (core dumped) Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on /lxc/test/system.slice/systemd-journal-flush.service: Permission denied Nov 30 21:03:37 test systemd[1]: Starting Flush Journal to Persistent Storage... Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on /lxc/test/system.slice/systemd-random-seed.service: Permission denied Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) is currently using 8.0M. Maximum allowed usage is set to 799.2M. Leaving at least 1.1G free (of currently available 7.7G of space). Enforced usage limit is thus 799.2M. Nov 30 21:03:37 test systemd[1]: Started Flush Journal to Persistent Storage. Nov 30 21:03:37 test systemd[1]: Started Nameserver information manager. Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on /lxc/test/system.slice/systemd-journal-flush.service: Permission denied -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title:
[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown
> We've seen some weird behavior with systemd on some specific kernel releases in the past. Not sure if that info helps: I have been installing several different kernels in the mean time; all of them share the same behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: [systemd] SIGPWR doesn't always lead to shutdown Status in lxd package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown
Also note: confirmed for lxd==0.23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1519499 Title: [systemd] SIGPWR doesn't always lead to shutdown Status in lxd package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: This is a follow-up on this issue here: https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container gently and as it seems the issue lies within ubuntu/systemd which does not handle SIGPWR correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1519499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
