[Touch-packages] [Bug 1725404] [NEW] 10-finger typing: Ctrl+Alt does not work as "AltGr for left hand"

2017-10-20 Thread Sven R. Kunze
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:

[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-09-14 Thread Sven R. Kunze
> 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

[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-09-14 Thread Sven R. Kunze
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

[Touch-packages] [Bug 1716014] [NEW] Create Volatile Files and Directories without time limit

2017-09-08 Thread Sven R. Kunze
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

[Touch-packages] [Bug 1639555] [NEW] Same Indicator Icon for "Networking on" and "Ethernet Network on"

2016-11-06 Thread Sven R. Kunze
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

[Touch-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported

2016-08-04 Thread Sven R. Kunze
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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2016-05-11 Thread Sven R. Kunze
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:

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2016-05-11 Thread Sven R. Kunze
@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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2016-02-12 Thread Sven R. Kunze
@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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2015-12-09 Thread Sven R. Kunze
@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:

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2015-12-07 Thread Sven R. Kunze
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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2015-12-07 Thread Sven R. Kunze
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

[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown

2015-12-01 Thread Sven R. Kunze
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 >>>

[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown

2015-12-01 Thread Sven R. Kunze
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.

[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown

2015-11-30 Thread Sven R. Kunze
>>> 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

[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown

2015-11-30 Thread Sven R. Kunze
> 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

[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown

2015-11-30 Thread Sven R. Kunze
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