Public bug reported:
In some circumstances (see
https://code.google.com/p/chromium/issues/detail?id=410649 for details)
ibus ends up giving keystrokes to Chromium and other programs with out-
of-order timestamps, resulting in mangled input. This can happen even
under light load.
https://github.co
Gunnar, the point here is that the code is checking the wrong thing.
Nobody sat down and designed the current behavior. I believe that, in
fact policykit *is* the way Ubuntu handles these things.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
Public bug reported:
Inexplicably, one set of udev rules in /lib/udev/rules.d/69-cd-
sensors.rules didn't get converted from gcm to colord:
# i1Display3
ATTRS{id
I can confirm that the fix works for us as well. Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/956848
Title:
pam_mkhomedir.so fails to create homedir in precise
Status in Li
The documentation for pam_open_session says, "It should be noted that
the effective uid, geteuid(2). of the application should be of
sufficient privilege to perform such tasks as creating or mounting the
user's home directory for example."
AFAICT, this is contrary to Steve Langasek's assertion tha
We rely on pam_mkhomedir. We're using it with the standard options.
It used to work fine on lightdm, but as of recently, it doesn't.
It works fine with ssh.
This is crucial for us.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightd
Fix works for us.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/880104
Title:
Using pam_group results in: pam_group(lightdm:setcred): unable to set
the group membership for user: o
We've seen this as well on Precise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/877904
Title:
Top panel visible in locked screen
Status in “gnome-screensaver” package in
We no longer see the error message, but pam_group is still not setting
the groups we need it to set.
** Changed in: lightdm
Status: Incomplete => Confirmed
** Changed in: lightdm (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 844039 ***
https://bugs.launchpad.net/bugs/844039
John, I'm confused by why you think this is a dup of bug #844039. That
bug requests that the Other option be disabled. This bug complains the
opposite: that it *is* disabled, even when it should not be.
--
Y
Has any progress happened on this bug? It turns out it's even more
important to us than we initially realized; we rely on it to add users
to the "fuse" and "cdrom" groups; being absent those groups cases real
inconvenience.
--
You received this bug notification because you are a member of Desktop
I have confirmed that adding "greeter-hide-users=true" in the
SeatDefaults stanza of lightdm.conf fixes the problem.
We would still like to have the behavior I saw before, where if a user
was known to the accounts manager, they would be listed, but there was
always an "other" box also. However, th
We're case 2. Listing all the users is impossible anyhow. Where would you
get the list? But we're OK I believe with listing those who have logged in
before on the particular machine. That's not essential however.
Right now the "other" selector is totally missing. It should be impossible
for that t
By the way, this bug is quite new. With our configuration, in December,
it worked just fine, as far as I can tell.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/921315
Title:
lightdm
No. We are fine with users who have already logged in having their
username visible; that's helpful.
It's not a lightdm issue, but I'm really quite flabbergasted how even
one user shows up in the accounts manager before anyone has logged in,
on our configuration. In any case, we like the idea that
Public bug reported:
In our configuration, nearly all users are granted access to the system
via pam. The User Accounts dialog in Settings shows only a single user
which was created at install time...and I'm not sure where from, because
we preseed "d-i passwd/make-user boolean false" to try and in
We have this problem too. Our users typically do not have a home
directory until the first time they log in, by the way, with the use of
pam_mkhomedir.so to create it, however this behavior is independent of
whether the home directory exists or not.
We do not see the session chooser widget until y
As far as I can tell, this isn't fixed. I just had the following:
Unpacking evince-common (from .../evince-common_3.2.1-1ubuntu4_all.deb) ...
dpkg: error processing
/var/cache/apt/archives/evince-common_3.2.1-1ubuntu4_all.deb (--unpack):
trying to overwrite '/etc/apparmor.d/abstractions/evince',
Public bug reported:
evince-common version 3.2.1-1ubuntu1 (in precise) contains the file
/etc/apparmor.d/abstractions/evince, which is also found in the evince
package 2.30.3-0ubuntu1.2 (in lucid). It should declare a conflict, at
the very least.
** Affects: evince (Ubuntu)
Importance: Undec
Public bug reported:
libnm-glib-vpn1 in precise contains the file /usr/lib/libnm-glib-
vpn.so.1 which was also found in lucid's libnm-glib2 package. At the
least it needs to declare an appropriate conflict.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
Public bug reported:
I need to disable guest logins for lightdm, and did so by adding the
line "allow-guest=false" to /etc/lightdm/lightdm.conf.
However, this also has the side-effect of disabling the user-switcher in
the indicator area of Unity after I log in, which is bad. I want the
user-switc
Let me stress that this is not a "fairly minor problem", but is a
critical security vulnerability in some contexts.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/620693
Tit
This affects lucid; can the patch be pulled in to an SRU?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/377367
Title:
gnome-terminal doesn't handle colons in URLs
Status in G
23 matches
Mail list logo