*** This bug is a duplicate of bug 553200 ***
https://bugs.launchpad.net/bugs/553200
On 04/15/2010 01:09 AM, Martin Pitt wrote:
*** This bug is a duplicate of bug 553200 ***
https://bugs.launchpad.net/bugs/553200
Ah, that would explain also why I'm not able to reproduce the issue
On 04/13/2010 10:48 PM, Chris Thompson wrote:
By disabling I mean using the System-Administration-Hardware
Drivers and then specifying Remove as the action against Nvidia
proprietary driver.
Confirmed that doing the same works for me as well. Removed the driver
via the same method, changed
Now I'll try testing by reinstalling nvidia-96 and then with just
nouveau.
Reinstalling nvidia-96 reverts gdm back to the original symptoms. I'll
have a look at trying:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/553200/comments/33
--
pam_unix(gdm:auth): conversation failed
NoOp [2010-04-08 17:25 -]:
So what's actually left for you on this bug?
To get the gdm menu working :-)
gdm menu → is that System → Administration → Login Window
configuration program? (i. e. gdmsetup). Or the login screen itself,
which you see when you start the computer and disabled
Hello Chris,
Chris Thompson [2010-04-12 11:01 -]:
Attempt to login in user crt: gdm login screen asks for password,
but mouse is frozen and no keyboard input accepted. After about 7
seconds gdm login screen redisplayed.
This sounds like an entirely different problem. Can you please do
On 04/12/2010 01:54 AM, Martin Pitt wrote:
NoOp [2010-04-08 17:25 -]:
So what's actually left for you on this bug?
To get the gdm menu working :-)
gdm menu → is that System → Administration → Login Window
configuration program? (i. e. gdmsetup). Or the login screen itself,
which
NoOp [2010-04-06 16:31 -]:
Modified custom.conf to:
[daemon]
AutomaticLogin=laptop
If you don't actually have a laptop user, this doesn't look healthy.
How did it get there, was that damaged this way with System -
Administration - Login Window? Or did you add it by hand?
rebooted and
NoOp [2010-04-07 14:50 -]:
For some unknown reason, the screen resolution has been modified during
the upgrade process to an unsupported value.
I changed the screen resolution according the monitor's specs and the
login loop problem disappeared.
Ah, that would explain it, too. You can
On 04/08/2010 02:53 AM, Martin Pitt wrote:
NoOp [2010-04-06 16:31 -]:
Modified custom.conf to:
[daemon]
AutomaticLogin=laptop
If you don't actually have a laptop user, this doesn't look healthy.
How did it get there, was that damaged this way with System -
Administration - Login
On 04/08/2010 02:55 AM, Martin Pitt wrote:
NoOp [2010-04-07 14:50 -]:
For some unknown reason, the screen resolution has been modified during
the upgrade process to an unsupported value.
I changed the screen resolution according the monitor's specs and the
login loop problem disappeared.
NoOp [2010-04-08 15:21 -]:
User is 'gg' home for that user is 'gg'. 'gg-main' is the machine
sometime back I'd changed the 'full name' to 'gg-main' just so that I'd
remember the machne name. Doesn't matter. If I change the full name to
'gg' so that 'gg' shows up on the gdm menu, the
On 04/08/2010 08:47 AM, Martin Pitt wrote:
...
- 'sudo nano /etc/gdm/custom.conf',
- change from 'laptop' to 'gg',
- 'sudo stop gdm' and then 'sudo start gdm'
- back into user 'gg' desktop.
This looks like it worked?
Yes.
So what's actually left for you on this bug?
To get
When I had the problem that is how I got myself logged in, yes. I had to
unlock the keyring manually, but that was it.
Right now it is working as it should (see earlier post; one of many
updates solved it).
cheers
Tom
--
pam_unix(gdm:auth): conversation failed
NoOp,
thanks, the PAM related files/outputs look alright. Can you please check
if your /etc/gdm/custom.conf still tries to log in the laptop user
automatically? Also, can you try changing DefaultSession=gnome to
DefaultSession=gnome.desktop? (Log into a text terminal with
Ctrl+Alt+F1 and
NoOp [2010-04-03 0:23 -]:
gdm-simple-greeter[2584]: WARNING: Unable to lookup user name laptop: Success
Is your user name actually called laptop?
If so, can you please give me the output of these commands:
getent passwd laptop
ls -l /etc/passwd /etc/shadow
grep passwd
..
gdm-simple-greeter[2584]: WARNING: Unable to lookup user name laptop: Success
Is your user name actually called laptop?
If so, can you please give me the output of these commands:
getent passwd laptop
ls -l /etc/passwd /etc/shadow
grep passwd /etc/nsswitch.conf
No. There may
On 04/01/2010 03:01 PM, Johannes Rohr wrote:
I have seen the same. What solved it for me was purging gdm and
reinstalling it, this indicates that there is indeed something wrong
with the conffiles ( dpkg --purge --force-depends gdm gdm-guest-session
)
That worked - once. Note: I'd even mv'ed
17 matches
Mail list logo
