** Package changed: gdm (Ubuntu Lucid) => nvidia-graphics-drivers-96
(Ubuntu Lucid)
** Changed in: nvidia-graphics-drivers-96 (Ubuntu Lucid)
Status: Incomplete => Confirmed
** Summary changed:
- pam_unix(gdm:auth): conversation failed
+ login fails with nvidia driver 96
--
login fails w
NoOp unsubscribed, so the point is mostly moot, but the original report
is not the same symptom, it describes a black screen and an X server
restart *after* logging in. Bug #553200 is a hang or crash as soon as
the password prompt is displayed. In addition, Saša's report confirming
the original s
*** This bug is a duplicate of bug 553200 ***
https://bugs.launchpad.net/bugs/553200
FYI: I was simply thanking Martin for all the time & effort spent
working on this bug. So I've no idea what you are going on about.
If you read the *original* description of this bug report the *symptoms*
are
*** This bug is a duplicate of bug 553200 ***
https://bugs.launchpad.net/bugs/553200
NoOp, I already mentioned in the other bug that I don't think electhor's
original problem is related. Electhor was using a GeForce 8600 GT,
which is not supported by the 96.43.* legacy driver, so can't have b
*** 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
*** 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 with
any of the previous descriptions (changing gdmsetup, etc.). So I'm going
to mark this as a duplicate of bug 553200.
If there is anyone
> 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
https://b
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, c
It appears that https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/553200";>bugs.launchpad.net/ubuntu/+source/gdm/+bug/553200
describes the problem that has been described in this thread.
I will be watching that thread from now on.
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchp
By "disabling" I mean using the "System->Administration->Hardware
Drivers" and then specifying "Remove" as the action against Nvidia
proprietary driver.
Xorg.0.log.old is a better place to look as it seems that when X crashes
and restarts the crash log is remained .old, and the new instance of X
w
I don't think there's anything "confirmed" about this bug. There are
about six different issues being discussed in this bug, and we still
don't actually have an explanation for the problem you're having on your
system.
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchpad.net/bugs/51
Note to Martin: can this bug be marked as 'Confirmed' rather than
'Incomplete'? Others have confirmed the same & the bug affects 12 people
so far.
@Chris: by "disabling the Nvidia video driver fixes this problem", just
how/what did you do to disable the driver?
--
pam_unix(gdm:auth): conversatio
I'm not seeing that in my Xorg.0.log - the log file is attached.
apt-cache policy nvidia-96
nvidia-96:
Installed: 96.43.14-0ubuntu13
Candidate: 96.43.14-0ubuntu13
Version table:
*** 96.43.14-0ubuntu13 0
500 http://archive.ubuntu.com/ubuntu/ lucid/restricted Packages
100 /va
I have determined that (on my system) disabling the Nvidia video driver fixes
this problem.
When using the Nvidia video driver the following is found in the Xorg.0.log
file:
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e937b]
1: /usr/bin/X (0x8048000+0x61c7d) [0x80a9c7d]
2: (vdso) (__ker
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 itsel
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
For me the system as standard with one user "crt" (or at least via standard
updates) has a frozen gdm login screen as described by others.
Modify /etc/gdm/custom.conf to add the following:
[daemon]
AutomaticLogin=crt
AlwaysLoginCurrentSession=false
AutomaticLoginEnable=true
TimedLoginEnable=false
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 disab
Hi,
It looks like I have the same issue. But, I have it under control with a quite
little workaround.
The problem suddenly appears when I installed privative NVidia drivers and
after executed nvidia-xconfig.
Until that I have lucid working without any issue (apparently), except,
obviusly, the re
I would like to confirm that I have the same problem (as "NoOp") on a test
system (inability to login using gdm login screen).
It is ok when using AutomaticLogin.
I have a single user on the system.
It failed after an update somewhere between 26 March to 6 April (I was away for
a week, came back
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
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 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 di
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 ->
> Administrat
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
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?
> reboot
@Sebastien: not sure exactly what you are asking. If you mean 'no
autologin' and at the gdm menu, Ctrl-Alt-F1-6, login at the console &
then '$ startx', no it does not work.
$ startx
Fatal server error:
Server is already active for display 0
If this server is already running, remove /tmp/.X0-lo
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
https://bugs.launchpad.net/bugs/5
those getting the issue does starting your user session using startx
works correctly?
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchpad.net/bugs/516520
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Ah, got it. I'll leave the machine in it's exisiting state for further testing.
It's not a primary machine (right now) so it's not a problem for me to continue
troubleshooting if it can help. BTW: no issues with my nvidia-96 drivers
w/regard to compiz et al. But a user on the users list mentione
I did something as close as you can get to a complete reinstall: I
purged everything except for the bare minimum (those packages on which
ubuntu-minimal depends on), next I cleaned up the /etc dir and removed
all config files which had no owner and did not belong to an installed
package, including,
Martin: I know you folks are busy trying to get 10.04 out the door. So,
unless you'd like me to troubleshoot further I plan to just do an
inplace reinstall from today's daily. I'll reload all of my additional
packages via Synaptic markings. Thanks for all the effort, but this one
is just taking too
Martin: as a test I created the user 'laptop' & modified the custom.conf
accordingly. Autologin to that username works (standard login does not),
but if I try to switch to another user from 'laptop' (ggserv for
example) I get the same results; gdm loops & sends me back to the
switcher password to g
> 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+
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 do
Guyz, I fixed this problem also by apt-getting install ubuntu-desktop!
thanks
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchpad.net/bugs/516520
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
..
>> 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.
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 /etc/nsswitc
regarding my previous message: I now disabled samba and winbind
authentication in pam-auth-upate, this got me rid of the console login
problem, but did not affect gdm
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchpad.net/bugs/516520
You received this bug notification because you a
one observation: As long as samba is running I cannot even log on at the
console. Only passwordless login via ssh works.
When I stop samba, console login works, but gdm login still fails.
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchpad.net/bugs/516520
You received this bug noti
Not sure if this is of help or not. info from 0.greeter.log after
attempting to switch user:
(gnome-power-manager:2583): GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.24.0/gobject/gsignal.c:2273: signal `proxy-status' is
invalid for instance `0x8313f58'
gdm-simple-greeter[2584]: Gtk-WARNING:
And the other one. I realised that you may not learn much from them
since I did not have the issue on logging in.
Tom
** Attachment added: "common-account"
http://launchpadlibrarian.net/42917603/common-account
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchpad.net/bugs/516520
Hi guys,
Had to do without you for 48 hours and was getting withdrawal symptoms. Then
somehow my system got past the boot issues, that is the upside of errors that
come and go: this time it went. I got to load like 174 updates, including a
kernel, Xcore , ATI and Radeon and quite some Gnome ele
> - Can you log into a text console with your user? (Ctrl+Alt+F1; press
> Ctrl+Alt+F7 or Ctrl+Alt+F8 to go back)
OK, I can now get to tty consoles again (had to edit out VGA= in
menu.lst - the machine is still using grub1) from the desktop + gdm. I
still have to use autologin to get to the deskto
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'
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
)
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchpad.net/bugs/516520
You rece
Console status changed after the upgrade to UD 1.194:
Ctrl+Alt+F1-6 results in a blank screen & turns off the display as
before. However, ctrl+Alt+F7 does now get me back to the original
desktop. Switch user takes me to the gdm screen; that loops as before,
but now on the loop it promts me for the
Architecture: i386
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: nvidia
Package: gdm 2.30.0-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Tags: lucid lucid
Uname: Linux 2.6.32-18-generic i686
Also, do you have the "ubuntu-desktop" package installed?
--
pam_unix(gdm:auth): conversation failed
https://bugs.launchpad.net/bugs/516520
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
49 matches
Mail list logo
