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-u
> 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
Bugs, w
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 not
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 /e
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 a
Still not working on Ubuntu 16.04. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/388553
Title:
Wi-Fi Protected Setup (WPS) not supported
To manage notifications about this bug go to:
https://bug
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
Shutdown failure: Assertion '
@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
Bugs, wh
@Martin Is there some update on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
Shutdown failure: Assertion 'sd_id128_randomize(&id) >= 0' failed at
../src/core/dbus.c:657, func
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
Shutdown failure: Assertion 'sd_id128_randomize(&i
Tested. However, it does not fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
Shutdown failure: Assertion 'sd_id128_randomize(&id) >= 0' failed at
../src/core/dbus.c:657
Nice. Is there something else I can do here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
Shutdown failure: Assertion 'sd_id128_randomize(&id) >= 0' failed at
../src/core/dbus.c:65
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Ti
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/syst
Also note: confirmed for lxd==0.23
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519499
Title:
[systemd] SIGPWR doesn't always lead to shutdown
To manage notifications about this bug go to:
https:
>>> 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
> 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 Ubunt
Confirmations for:
1) lxd-images import ubuntu wily --alias ubuntu; lxc launch ubuntu test; sleep
10s; lxc stop test
Confirmed: It does not shutdown.
2) Executing "shutdown" manually inside the container (through lxc exec) does
shutdown the container
Confirmed: It does not shutdown.
3) Manuall
The requestes versions:
>>> lxc --version
0.22
>>> apt search liblxc1
Sorting... Done
Full Text Search... Done
liblxc1/trusty,now 1.1.5-0ubuntu3~ubuntu14.04.1~ppa1 amd64 [installed,automatic]
Linux Containers userspace tools (library)
>>> apt search lxcfs
Sorting... Done
Full Text Search... Do
Public bug reported:
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.
** Affects: lxd (Ubuntu)
Importance: Undecided
Status
20 matches
Mail list logo