Public bug reported:
When linux-boot-prober is invoked with /dev/mapper/VOLUMEGROUP-VOLUME2
from a linux root partition on /dev/mapper/VOLUMEGROUP-VOLUME1 the last
field returned has "root=/dev/mapper/VOLUMEGROUP-VOLUME1 ro recovery
nomodeset" while the first field (the requested root partition) i
Set the user to be a SystemUser in /var/lib/AccountsService/users works.
I would be more interested in a whitelist feature, so newly created unworthy
users don't have to be blacklisted.
Why is there not a simple requirement like: only members of the lightdm
group are allowed to use lightdm??
--
*** This bug is a duplicate of bug 1479251 ***
https://bugs.launchpad.net/bugs/1479251
Indeed, I had Skype installed and when I got the upgrade to work, I had
to reinstall Skype.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
*** This bug is a duplicate of bug 1479251 ***
https://bugs.launchpad.net/bugs/1479251
After following Louwtjie's solution above, I got it to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14
Again, the fix is easy: always change the layout back to default when
locking the screen, or before presenting the login applet. The initial
login also has the default layout, the changed layout is not relevant
for logging back in. As a additional service to the user, you could
switch the layout ba
PROPOSED FIX
The current popup shows:
Information: Username, Current keyboard layout (also a button)
Buttons: Switch user, Unlock
When you click on Switch user, you end up at the correct behaviour: the
keyboard is switched back to the default layout, the same layout that
the user used to lo
After more than a year, may I suggest the right way of handling this?
The lockscreen password dialogue should default to the keyboard that the
current user uses for normal login, ie, the standard layout. Because that is
what that user normally would get for login, and it will work as always, as
** Tags added: rpc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336905
Title:
Client can't connect to transmission-daemon
To manage notifications about this bug go to:
https://bugs.launchpad.net/
Public bug reported:
Installed transmission-daemon 2.82-1.1ubuntu3 on a server (Ubuntu 14.04
LTS) on the local network. When trying to connect through any
webbrowser, it says:
"""
409: Conflict
Your request had an invalid session-id header.
To fix this, follow these steps:
When reading a r
@50 That is very strange, because Ctrl-Shift is no longer possible as a
key sequence since 13.10 onwards...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244548
Title:
Keyboard shortcut for changin
I think this came up especially because the old language-agnostic ways of
changing layouts is no longer available. I used to use Shift+CapsLock, which
would be recognized in any layout. Unfortunately that is no longer possible.
Now I use Ctrl-` (which is something different in the main other lay
Standard new install of 14.04, bug on lockscreen is still there.
Clicking on the language button works, but the keyboard shortcut
doesn't.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244548
Title:
Additional note: on the console I get messages like:
[ 601.586905] INFO: task lvcreateL1999 blocked for more than 120 seconds.
[ 601.593195] Tainted: G W 3.12.0-7-generic #15-Ubuntu
[ 601.593195] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
OK, on a non-luks encrypted bog-standard lvm2 install of the latest trusty tahr.
Note: the original bug was already solved. The case where the output of the
lv-snapshot creation is directed to a file on the volume being snapshotted is a
mixed bag with the latest trusty tahr. The first time it wen
Sorry, the iso won't install. It's stuck at 98% CPU for over an hour at
'cryptsetup', which manually only takes a second... I don't even know if
the installer uses the proper setup, and I don't see a way to do it with
"Something else".
--
You received this bug notification because you are a membe
I don't think the status should be invalid. A workaround is provided,
and there is an interaction with udev that causes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096520
Title:
lvm2 hangs wh
16 matches
Mail list logo
