I can confirm this really annoying bug under Ubuntu 9.10 (amd64) and
Kile 2.0.83. Is there a solution yet?
--
word wrap mix words when going to next line
https://bugs.launchpad.net/bugs/455434
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
ok, thanks for trying anyway!
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Luca A,
since I have changed the common-auth and common-password, I don't have any
login problems. lock session in gnome and login in again works fine.
--
silent login/gdm failures and sudo segfaults with smbpasswd enabled
https://bugs.launchpad.net/bugs/292791
You received this bug
Hi,
here is the common-account.
I just reproduced the seg fault when trying 'sudo -s' again. I used the
common-auth I already postet as attachment and the common-account attached to
this post.
** Attachment added: common-account
http://launchpadlibrarian.net/20187494/common-account
--
and here is the common-password
** Attachment added: common-password
http://launchpadlibrarian.net/19907065/common-password
--
login impossible, no error message
https://bugs.launchpad.net/bugs/292791
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I justed reproduced the segmentation fault, using the config files in the
attachment.
Using these attached config's, I get the seg fault when trying 'sudo -s' from a
normal (non-root) shell.
** Attachment added: common-auth
http://launchpadlibrarian.net/19907058/common-auth
--
login
No problem :)
Do you get any log messages in /var/log/auth.log that match up with this
segfault?
No, nothing in auth.log
If not, can you reproduce it when running 'sudo -s' from a root shell?
(This would let us get a backtrace from sudo using gdb)
I'm not sure if I've got you right, here is
In the attachment there are parts of the auth.log from the time in
question, I left out duplicate parts. My editing in the config to fix
the problem could be the reason for errors at the end of the log.
I also tried to reproduce the bug, by setting auth-common and auth-
password back to the old
yes, the error in auth.log was:
login[5726]: pam_unix(login:auth): authentication failure loginname=LOGIN uid=0
euid=0 tty=tty1 ruser= rhost= user=root
--
login impossible, no error message
https://bugs.launchpad.net/bugs/292791
You received this bug notification because you are a member of
I also got this error in the log:
gdm[5829] pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0
tty=0: ruser=rhost = user=my_username
I'm not very familar with this topic, therefore I don't know if this
information has anything to do with the topic, maybe it helps:
- I'm using
Public bug reported:
Ubuntu 8.10
Had no problems with Intrepid at first, but then login wasn't possible
anymore. After entering username and password in the gnome login-gui,
nothing happend and I got the username prompt again. Same problem in the
terminal. After entering username and password, I
11 matches
Mail list logo
