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 me
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 solv
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
Desktop Bugs, which is subscri
** 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
Desktop Bugs, which is subscribed to gdm in ubun
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 displ
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 mem
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 bug
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).
-
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 aga
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 d
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 (kill
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 gnome-keyri
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
--
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
Desktop Bugs, which is a bug contact for gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bu
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
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 ra
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 wo
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: C
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 gnome
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 no
@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
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
http
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 Hypert
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
Desktop Bugs, which is a bug contact for gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@l
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 with
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 s
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 m
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'
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 beca
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
--
Can't
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
Desktop Bugs,
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 de
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 bec
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 upd
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 aga
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 are
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
--
Ca
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
Desktop Bugs, which is a bug contact for gdm in ubuntu.
--
desktop-
** 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
Desktop Bugs, which is a bug contact for gdm in ubuntu.
--
desktop-bugs mailing list
desktop-b
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 an
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 execut
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
** 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
Desktop Bugs, which is a bug contact for gdm in ubuntu.
--
desktop
** 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
Desktop Bugs, which is a bug contact for gdm in ubun
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
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 message
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: i
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
Desktop Bugs,
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
Desktop Bugs, which
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
https://bugs.laun
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 mo
53 matches
Mail list logo
