Could you try if that's still an issue in jaunty or karmic?
** Changed in: gdm (Ubuntu)
Status: Triaged = Incomplete
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sebastien Bacher schrieb:
Could you try if that's still an issue in jaunty or karmic?
** Changed in: gdm (Ubuntu)
Status: Triaged = Incomplete
Have jaunty on all my machines without any issues (same hardware as
running hardy + intrepid before). For me this issue seems to be solved.
closing the bug it's a collection of issue and some seem fixed, open new
bugs if you still have one
** Changed in: gdm (Ubuntu)
Status: Incomplete = Fix Released
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a
** Tags added: 8.04 8.10 804 810 gdm kunderjan ubuntu
** Tags added: jankunder
** Tags removed: kunderjan
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
i did what jeremiah suggested but now i can only log into gnome failsafe..
if i log into gnome aftere 5 seconds i get a failure message and it returns to
log in screen.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a
failure message when i log into gnome
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Executing /usr/bin/gnome-session failed, will try to run
x-terminal-emulator
No protocol specified
(zenity:5953): Gtk-WARNING **: cannot open display: :0
No protocol specified
cannot open
i upgraded to hardy RC today and the same bug occurred.
i can only log into failsafe xterm and then i type gnome-session to enter gnome
normally..
none of the above solutions helped to solve the problem.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this
I fixed this problem by editing my .profile file. It read:
export XAUTHORITY=/home/your_user_name/.Xauthority
I changed it to:
export XAUTHORITY=/home/jeremiah/.Xauthority
And GNOME actually booted.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug
@b: to switch window manager run metacity --replace , compiz --replace ,
or the gnome gui: gnome-appearance-properties via a command line or alt+f2
seems related to bug #154596 to me. which is basically jockey improperly adding
nvidia to your xorg.conf (missing 1 all important line).
--
Can't
Well again I mess around for a couple hours and it stops happening.
In the process I did end up with my window decorations missing, so I had
to use gconf-editor to change my window manager to metacity, before it
was set to compiz, which I disabled ages ago.
Anyhow I hope it does not come back
Well I see I posted here on Jan 14th, and here I am again, as it has
come back.
Hard to tell what changed, as I keep the system up to date, and end up
being logged in somtimes for weeks at a time, so I would not notice the
problem until I log out and back in.
To refresh I do have an nvidia card,
I had this problem after doing a fresh installation of Gutsy and then
running aptititude dist-upgrade with a local copy of the Ubuntu
repository.
To resolve it, I uninstalled ubuntu-desktop (and everything that it
automatically pulls in) and then re-installed it. I got some errors
(related to
Confirming that i performed no edits or permanent workarounds and this
bug was resolved for me with a recent (1-2weeks) update to what seemed
like gnome-keyring though others were obviously instream. As i said
actions attempted except temporary workaround to start a gnome session
while broken
There seems to be different problems reported at the same bug number
here. One problem is caused by gnome-keyring. Killing gnome-keyring
makes the boot proceed. The latest updates seem to solve the problem
mostly for me, but I have experienced still at least one time where I
had to kill
Hi.
I can confirm THE BUG in Gutsy.
1. No *xgl* installed
2. Just basic glx installed
3. TODAY updated (last one was in November 2007 - test machine) system still
failed to login (didn't try newuser or failsafe login)
4. sudo chmod a+w /tmp; sudo chmod o+t /tmp (tnx David) just worked for me
There appears to be another patch from Stef Walter
this time to gkr-async and the title of the patch is
fix race condition.
I would suspect it will get to ubuntu in the next day or
so. The comment from one of the debian testers was
that it fixed the login etc. problems, however, the original
bug
Changing the tmp directory permissions also worked for me.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Oddly enough I was getting this error all morning.
Digging deeply into the problem gnome-session was bailing each time.
gnome-session would work when I log in initially after reboot, but any
subsequent logins with my user did not work (the same freeze we're
seeing above.)
Good news is now it
I havent finished testing the patch but it appears that something is in a race
condition.
I fixed a shell to sleep 2 seconds then call gnome-keyring and it the gnome
desktop appears to come up just fine.
However, in reality I believe there are several flavors of this bug.
I believe it is a
I just wanted to inform you that I've solved the problem with my system
not booting properly and the not starting gnome session. In my case it
was a problem with the previously (and manually) installed ndiswrapper
- I removed it and built it against the new kernel and everythings is
working fine
I expect your advice to solve the problem. Don't forget I am a mechanical
engineer, not a software specialist.
- Original Message -
From: jtholmes [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 11, 2008 07:07 PM
Subject: [Bug 136529] Re: Can't log in after upgrading
Sorry for the delay
Yes someone previously said that those of us using an Nvidia card seem
to have the problem.
That is correct, at least for me. I can never get gnome desktop to display
until i kill gnome-keyring proc on my Nvidia card machine, with Ubuntu
restricted Nvidia drivers.
The
@Pär Lidén:
What seems to be common for me and some other people here is that I have an
Nvidia graphics card.
no nvidia-card here... using a thinkpad x40, intel-graphics (driver:
i810/intel)
after 3 fresh gutsy-alternate-installations - corrupted after the first big
update (~150 packages)
i
Oh well, it seems my problem regarding the not-starting GNOME session is only
the tip of the iceberg. Remember you told me to remove gdm from being
automatically started at boot time jtholmes? Well, I did this yesterday and
after it didn't work out the way it should, I restored the settings
Is it this bug? (fixed)
http://bugs.debian.org/455694
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I want to add to jtholmes summary above about the problem: for me
logging in did not work even the first time on the first boot. I had to
try several times before I got a successful login. What did solve the
problem for me however, was putting the computer in uniprocessor mode,
ie. disabling
Debian bug 455 694 seems to be solved as the source for the
setuid/setgid messages are fixed. However, those messages are still
there for me, even though login and the rest of the system works
perfectly. So in my case, this will probably not solve the problem.
--
Can't log in after upgrading
Okay, as I was so stupid to post in a report that was marked as a duplicate of
this one, I'll post my problem here (thanks for the hint Pär ;-)).
I've got the same problem as all people do here - when I try to login to a
GNOME session the screen just freezes at the brown Ubuntu background. I can
** Attachment added: varlogmessages.log
http://launchpadlibrarian.net/11206369/varlogmessages.log
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/11206374/Xorg.0.log
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Thanks Bernhard for the attachments
for those of you that are interested in a possible workaround
you can try disabling gdm at boot time with this command
update-rc.d -f gdm remove
then you will recieve a normal terminal screen login
login as usual
then execute startx from the command line
Thanks for the hint. But unfortunately this doesn't work for me either. I did
like you told me and removed the gdm autostart links with update-rc.d -f gdm
remove. Then I created a .xinitrc file with exec gnome-session in it and
rebooted my machine. After logging in via terminal I then executed
** Changed in: gdm (Ubuntu)
Importance: High = Critical
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Bernhard
No need to file another bug report. This strain of bug is on several bug reports
and is being actively pursued by the developers.
What you can try is to remove the .xinitrc and just login as yourself and
execute
startx
leave .xinitrc out of the mix and let startx figure out things
Running startx by itself works perfectly and loads the full gnome
session like usual.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Looks like the bug is a collection of different issues, that's nothing
easy to read it or to get worked. Could anybody try to summarize what
the issue is exactly and how to trigger it quickly and update the
summary in a clear way?
** Changed in: gdm (Ubuntu)
Importance: Critical = High
--
Same Problem here:
X40 Thinkpad (Gutsy was running fine before - just badly upgraded to
Hardy and reinstalled Gutsy)
* installation went fine (usb-stick, alternate-iso, german language,
desktop-option, download language-packages during installation)
* first boot ok - even compiz runs
* first
What do you call boot, is that a second login or a reboot from the
computer? That looks like a session hanging. On hardy bug #175682 is a
gnome-keyring issue leading to this situation. The bug can also be due
to service not closed correctly with the session, if the issue is
triggered when login
Problem summary as I see it
I have perused about 200 bug reports this weekend and that have seen various
flavors of this problem
but as far as I can see the main issues are
Install gutsy, hardy (very few feisty) can be from CD or update-manager
boot first time after installation and things
Hi Sebastian,
What do you call boot, is that a second login or a reboot from the
computer?
i mean a complete reboot of the computer. nautilus is running all the
time...
Greets,
Falk
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification
Sebastien
From the text of the various bug reports it appears that the reporter means
a boot from full poweroff.
As for #175682 some have reported that killing gnome-keyring solves the problem.
After killing keyring, gdm goes on and does what it is suppose to do. #175682
is not so
clearly
Hi jtholmes,
I will reinstall hardy daily-live a/o 1/2/8 and do the following
why hardy? thought we were talking about a gutsy-bug?
falk
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Let me rephrase that.
We have reports on both Hardy and Gutsy havine the same problem, so i will
reinstall and perform the same tests on both Hardy and Gutsy.
I have enough computers that I can leave both of them as they
are after testing in case we need to perform further testing.
jt
--
The issue is weird, a reboot should not make any difference on the
software stack. How many people have the issue after restarting their
computer? That looks like an hardware issue there
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification
No it is not not a hardware problem. I have dual OS the other one (WIN XP)
is working fine.
- Original Message -
From: Sebastien Bacher [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2008 03:44 AM
Subject: [Bug 136529] Re: Can't log in after upgrading
The issue
Sebastien
you will love the results of this testing :)
Gutsy on Non Nvidia machine using Via-Rhine video
Installed Gutsy
Boots and runs correctly every time could not find any problems wth via-rhine
video
-
Hardy on Non Nvidia
First of all, thanks for all the help here! I just wanted to add that just
using startx without creating a .xinitrc ends with the same results: my
GNOME session won't start. After a few seconds of harddisk activity the PC just
stops loading and does nothing anymore (at least as far as I can
Hello, I've had this problem too. At first I reported it as
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/179552, but
found out that mine must be a duplicate of this bug. I found out that if
I disable Hyperthreading in the bios, it works perfectly. The GTK
setuid/setgid error
I've been experiencing the same on and off. Quite annoying. Looking at
my xorg.conf I had the 'i810' driver for my Toshiba A200, which has an
Intel 945GM chipset. I changed it to the 'intel' driver. The video board
is detected correctly:
(II) intel: Driver for Intel Integrated Graphics Chipsets:
The bug seems fixed for me so I close this bug, but please, feel free to
reopen it if you continue to have troubles.
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) = Andrea Corbellini (andrea-bs)
Status: Confirmed = Fix Released
--
Can't log in after upgrading
not fixed for me yet, reopening it...
** Changed in: gdm (Ubuntu)
Assignee: Andrea Corbellini (andrea-bs) = Clau (claudiu-covaci)
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Ok, I reopen the bug.
** Changed in: gdm (Ubuntu)
Assignee: Clau (claudiu-covaci) = (unassigned)
Status: Fix Released = Triaged
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm this bug also.
I have upgrade to Kubuntu Gutsy, and, with xserver-xgl, after logging in, I
only get the screen with the login-background (so not really blank), There is
some harddisk activity for a few seconds, but then nothing more. If I sudo
apt-get remove xserver-xgl, the
I can confirm this bug too.
I don't use any special video driver or card and it happens to me very often,
but not always.
Also, my /var/crash folder is empty.
[EMAIL PROTECTED]:~$ uname -a; lsb_release -a
Linux hivepad 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686
GNU/Linux
No LSB
\o/ fixed it for my setup. In my case there were some bash-isms in
~/.bashrc and although I tried to be careful to only source it on
interactive logins, I hadn't been careful enough. Once I fixed that I
could login normally. Why the set -x helps I can only imagine.
So, for anyone else seeing
Well this is wierd - I can now login - what I need to do is put set -x
at the start of my .profile.
One day I'll sit down and start to trim my .profile to figure out which
bit is doing it!
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification
For me 2 solutions worked:
solution 1 (simple):
from failsafe session create new user - this new user will work perfectly
solution 2:
from terminal (Ctrl-Alt-f2 for instance) _move_ all configuration to new
directory:
sth. like
mkdir invalid_conf
mv .* invalid_conf
then check (login/logout
Having installed kubuntu-desktop from the command line, I can now log in
to KDE (via GDM). Thus, this only affects GNOME.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I've commented out the three lines as suggested in #152577 but then all I get
is:
/etc/gdm/Xsession: Beginning session startup
(session still lasts 10seconds...)
Adding set -x to the Default file:
...
+ echo /usr/bin/xsetroot
+ XSETROOT=/usr/bin/xsetroot
+ [ x/usr/bin/xsetroot != x ]
+
I get the same problem. None of the suggested fixes do anything.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
the suid messages might be related to bug #152577
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm running Beta here, same problem after updates few days ago (not sure
what day as I was running big backup job and waited awhile to reboot)
Problem was write access to /tmp
I sudo chmod 777 /tmp
but I wasn't thinking and that removed the sticky bit, so I
sudo chmod +t /tmp
I guess a
Same problem here, but removing xserver-xgl solved it for me. But it's
just a workaround. I hope to be running xserver-xgl soon!
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Had the same problem upgrading from Feisty to Gutsy with working
fglrx+Xgl config. I had to revert several Xgl feisty-specific changes
so stuff actually works.
I modified the suggestion in comment 7 and executed:
sudo chmod a+w /tmp; sudo chmod o+t /tmp
After that, the gnome session actually
I removed Xgl and still see this error. Not sure what's happening
there.
(process:7684): Gtk-WARNING **: This process is currently running setuid or
setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:
I am also having this problem after having done an upgrade from Fesity
to Gutsy via apt.
None of the suggestions above (/tmp, .gnome2, remove xserver-gl) help.
I cannot log in with failsafe or normal session.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received
On an installation from the alternate CD, I found that the .gnome2
directory of my normal user account was owned by root. Doing a 'sudo
chmod -R myuser:mygroup .gnome2' (with appropriate replacements) seems
to have resolved this issue for me.
--
Can't log in after upgrading
Nuking xserver-xgl from orbit fixes the problem for me.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
In theory, touching the file .config/xserver-xgl/disable will do the
same thing.
It would be nice if whatever it was trying to run with xgl detected it
crashing and disabled it on next boot. This is a particularly bad
because you get very little useful feedback.
--
Can't log in after upgrading
I found the same as anthony. Running
sudo aptitude purge xserver-xgl
fixed the problem for me
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I have the same problem. it's not /tmp for me either, that looks fine.
On login, the gdm window goes away, then the X server appears to crash
or exit, then comes back to the login window. I tried switching to kdm,
behaves the same way.
One oddity that might be related is that it's running on the
Hm, since the upgrade to gutsy I'm seeing these setuid errors too,
although I actually *can* log in. There doesn't seem to be any setuid
binary on my system which would fit the bill. Maybe it's a misdetection
because gdm drops permissions or something like that?
--
Can't log in after upgrading
FWIW just checked on my box - /tmp is fine:
drwxrwxrwt 22 root root 12288 2007-09-17 08:16 /tmp//
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I have the same problem, my system under feisty was running beryl with
an nvidia driver and had a the four-sided cube and other effects. After
upgrading to gutsy I can only login if I choose the failsafe-gnome every
time, otherwise I get the following in ~/.xsession-errors:
(process:25692):
In my system I had the same problem. The problem was caused because an
upgrade had revoked public write permission to my /tmp directory.
I fixed it with: sudo chmod a+w /tmp; sudo chmod o+t /tmp
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug
Finally did some debugging.
I've tried removing xserver-gl (which removed
/etc/X11/Xsession.d/98xserver-xgl_start-server) - no change.
I've tried commenting out gpg-agent (no change).
My .xsession-errors:
(process:17990): Gtk-WARNING **: This process is currently running setuid or
setgid.
This
In response to rojanu, I have neither fglrx or nvidia loaded (using the
radeon driver (and module))
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Started from a fresh install of Tribe 5 on my laptop. A few days ago
(possibly the 5th) I've had to use the failsafe session. After today's
updates failsafe won't even work. Same error in my .xsession-errors as
Adam. Using failsafe-xterm until I find a work around.
--
Can't log in after
I thought it was Envy but did a fresh install on my laptop and still the
same problem but the problem started ofter doing the latest updates
after installation, so something in todays update must have caused it
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received
I think this problem was related to Envy / custom nVidia drivers.
Because after I spent a while ripping things out and putting them back
in, it works, kind of.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of
not the only one - I've got this too :-( I can login with failsafe
mode. I can't see any old *dpkg* files in /etc/X11 and I'm not sure
what the problem is.
--
Can't log in after upgrading
https://bugs.launchpad.net/bugs/136529
You received this bug notification because you are a member of
81 matches
Mail list logo
