...
> $ apt-cache policy ubuntu-desktop
> ubuntu-desktop:
> Installed: 1.193
> Candidate: 1.194
> Version table:
> 1.194 0
> 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
> *** 1.193 0
> 100 /var/lib/dpkg/status
...
Sorry, it finished the updates when I rebo
On 04/01/2010 08:16 AM, Martin Pitt wrote:
> So, this bug is a bit confusing, let's try to untangle it. The original
> reporter, electhor, already closed it, so let's devote this report to
> NoOp's problem, who seems to have submitted most information.
>
> So if you use autologin, you get to the d
So, this bug is a bit confusing, let's try to untangle it. The original
reporter, electhor, already closed it, so let's devote this report to
NoOp's problem, who seems to have submitted most information.
So if you use autologin, you get to the desktop just fine. If you are
using the user switcher
I never had login issues, maybe should we fork the bugs (login issue /
desktop broken)?
2010/4/1 NoOp :
> Yep, setting to 'show the screen for choosing who will log in' breaks
> it. Can't unlock System|Administration|Login Screen. If I log back in
> via the recovery/Ctrl-Alt-F1 mode I see that /e
cat /etc/gdm/custom.conf on the test machine that was upgraded from -16
to -18 shows:
$ cat custom.conf
[daemon]
TimedLoginEnable=false
AutomaticLoginEnable=false
TimedLogin=
AutomaticLogin=
TimedLoginDelay=30
DefaultSession=gnome
--
lucid lynx - login screen stuck in a loop - SYSTEM BROKEN
htt
Yep, setting to 'show the screen for choosing who will log in' breaks
it. Can't unlock System|Administration|Login Screen. If I log back in
via the recovery/Ctrl-Alt-F1 mode I see that /etc/gdm/custom.conf has
been modified to:
[daemon]
AutomaticLogin=
AlwaysLoginCurrentSession=false
AutomaticLog
OK. Not sure how I managed to do this, but the problem (9.10 > 10.04) machine
is now working again. I modified the /etc/apt/custom.conf file to:
===
# GDM Configuration Customization file.
#
# This file is the appropriate place for specifying your customizations to the
# GDM configuration. If yo
upgraded the test machine. GDM login shows options for Language,
Keyboard, Sessions and accepts the password & desktop shows up fine. I
wonder if perhaps the 9.10 > 10.04 machine has issues with old policykit
permissions, etc, settings? Unfortunately that machine has multiple
accounts setup on it,
I've got another test machine that hasn't been updated since
2.6.32-16-generic (32bit). I'll fire that one up, update it & see if I
can reproduce on that one as well.
--
lucid lynx - login screen stuck in a loop - SYSTEM BROKEN
https://bugs.launchpad.net/bugs/516520
You received this bug notifica
Bonjour,
Updated my Lucid Beta @ 05:00 am UTC, over 100 updates, rebooted. Since
GDM loops, and I cannot go into recovery mode. When tryin gto go into
recovery mode, I get fsck from util-linux-ng 2.1.7.2 4 times.
So I'm totally stuck
AO
--
lucid lynx - login screen stuck in a loop - SYSTEM B
** Also affects: gdm (Ubuntu Lucid)
Importance: Undecided
Status: Confirmed
** Changed in: gdm (Ubuntu Lucid)
Milestone: None => ubuntu-10.04-beta-2
** Changed in: gdm (Ubuntu Lucid)
Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)
--
lucid lynx - log
Mar 31 10:18:23 x gdm-session-worker[1259]: pam_unix(gdm:auth): conversation
failed
Mar 31 10:18:23 x gdm-session-worker[1259]: pam_unix(gdm:auth): auth could not
identify password for [x]
Mar 31 10:18:23 x gdm-session-worker[1259]: pam_winbind(gdm:auth): getting
password (0x0388)
Mar 31 10:
Another added note: on the machine still having issues, I cannot unlock
the Login Screen Settings (System|Administration|Login Screen); click
'Unlock' and it remains greyed out. On the machine that is working
again, I can unlock the Login Screen Settings.
--
lucid lynx - login screen stuck in a l
Same issue; however I found that at the end of the recovery mode
messages, I hit enter, msgs to to last, and then from there I can do
Ctrl-Alt-F1 and get into a console. From that I can login, stop gdm
(need to use 'sudo /etc/init.d/gdm stop'), and then 'startx' and I'm in.
auth.log is showing:
Ma
Cristian,
No, I did not try KDE and right now I can't. I'll have to wait for this to get
fixed and then reinstall from a daily cd containing the right kernel and ati
drivers.
Single user mode (as in 'recovery mode > root') for repair and adding a second
user, but did not startx.
The other way o
Cristian,
Thanx for your support.
I know very well it is beta, but until last week even alpha was a lot better
than beta now. Better even than Karmic.
AFAIK a LTS release is branched off Debian stable, so should be pretty good to
start with.
It's a number of bugs biting me simultaneously that ha
@Tom, did you tried installing kdm (the KDE desktop manager)? That
always worked for me, anyway it seems that you are having trouble also
with authentication. Have you tried login in with single user mode?
That automatically logs you in as root if I am correct, so you can at
least avoid the first s
Good to hear it makes sense to you.
I have not modified or even peeked into these files, no.
If I ever get into my Lucid installation again I will get those files and
post them here. Promised.
Tom
--
lucid lynx - login screen stuck in a loop - SYSTEM BROKEN
https://bugs.launchpad.net/bugs/51652
Maybe I got it!
I had to reinstall (yet again!) the ubuntu-desktop package:
Note that I had to **install** it and it wasn't saying "already install, he
just installed it has if it did not have it (and I believe it wasn't having
it)... see attachment to look at what had been installed
ii ubuntu
@Tom: Lucid is now unstable, I think these things are quite normal when
you do beta test... at least I think you should be aware that is more
risky to use (and headache-prone), so you can always use previous stable
version instead of use other OSes ;).
Anyway, got the same behaviour after KERNEL u
> Mar 29 18:24:26 tom-laptop gdm-session-worker[1237]:
> pam_succeed_if(gdm:auth): requirement "user ingroup nopasswdlogin" not met by
> user "thomas"
> Mar 29 18:30:58 tom-laptop login[1213]: pam_unix(login:session): session
> opened for user thomas by LOGIN(uid=0)
This shows that somewhere be
Booted into recovery mode then root (had to remove plymouth -which was
reinstalled by some partial upgrade- to get recovery mode working).
Added another user. Rebooted. Both user names appear in the login
screen, but clicking either one makes the screen fade out and in again.
Background stays on al
With updates the system is fully fuctional.
ii gdm 2.29.92-0ubuntu9
ii kdm 4:4.4.1-0ubuntu7
I should reconfigure to set GDM as default (now I boot with KDM). News will
follow.
--
lucid lynx - login screen stuck in a loop - SYSTEM BR
Was experiencing the same login boot issue you guys describe after the current
Lucid update (was working on earlier Alpha)
Tried the usual update NVidia drivers etc, No luck :-(
I couldn't login, but was able to see this by using tty1 and install Lynx (ugh!)
After seeing CristianCantoro's posts,
Please check /var/log/auth.log for errors.
--
lucid lynx - login screen stuck in a loop - SYSTEM BROKEN
https://bugs.launchpad.net/bugs/516520
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
d
=== system now useless ===
Loaded a lot of updates today: a new kernel, gdm, gnome-session-manager and
others.
- Booting without 'nomodeset' does not work because KMS is broken, no change
here (bug 509273)
- Have to boot into recovery mode and then resume normal boot because gdm is
broken (bug
26 matches
Mail list logo
