*** This bug is a duplicate of bug 278722 ***
https://bugs.launchpad.net/bugs/278722
the comments suggest kde doesn't handle the alternative setting
correctly
** Changed in: kdelibs (Ubuntu)
Sourcepackagename: gnome-desktop = kdelibs
--
After intrepid upgrade, gnome session won't start
*** This bug is a duplicate of bug 278722 ***
https://bugs.launchpad.net/bugs/278722
** This bug has been marked a duplicate of bug 278722
Fail Safe login broken due to missing xterm
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
** Changed in: xorg-server
Status: Confirmed = Invalid
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Based on pretty much every confirmers' comment, the issue is resolved by
fiddling with gnome bits, with no change to X required, so this pretty
clearly is a gnome bug not an X bug. Upstream seems to concur.
Reassigning.
** Changed in: gnome-desktop (Ubuntu)
Sourcepackagename:
Thanks Mark
I too had a similar problem and did as you said I removed the following
.gnome .gnome2 .gconf .gconfd and logged in just fine to one of the
users that were affected. But in my case not all logins were affected,
for some reason the logins that had admin access worked fine but the
Ah, yes, I remember seeing something just before the login screen came
up that referred to 'kdm being nonexistent' or some such. I thought it
was strange but didn't make the connection between it and this bug. I
can state, I think with a certain amount of surety, that the problem
you've
I had this problem exactly as described in the original report, after an
upgrade from 8.04 to 8.10.
I eventually tracked it down to a dangling link from /etc/alternatives/x
-session-manager. It was pointing to a nonexistent KDE4 startkde
script, which presumably used to exist in 8.04. I had
** Tags added: 965gm intel intrepid regression xorg
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've since done a fresh install for other reasons. Problem solved with
xclient script. Something must have gone wrong during the upgrade.
Regards
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this
Hi. I've just upgraded from Hardy to Intrepid with the official
release. I have this same issue. I am running the AMD64 build on a
laptop with intel x3100 graphics and 965 chipset. Not sure if it's
relevant, but my one of my gdm logs had this at the end:
(==) Log file: /var/log/Xorg.0.log,
This happened to me as well, and setting the session to GNOME fixed it;
however, when trying to run the guest session, it seems to be running
the Xclient script still, since it just hangs on a black screen like it
did when I uses to login to my normal user account. Any idea how to fix
this, or at
I tried this (choosing Gnome as session) and confirmed it works for me
too. Didn't try this before as I assumed that's what it was using
before, but obviously not...
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
I followed Casper guide, and choosing Gnome as session, now starts ok.
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hello,
Thanks for your help but it did not work for me.
As I found no other solution, I reinstalled this morning from a fresh
and clean Iso of the Intrepid Release Candidate, all updates after got
well and for the moment it is OK.
Best regards.
--
After intrepid upgrade, gnome session won't
Hello,
I'm exactly in the same case, as described here :
http://ubuntuforums.org/showthread.php?t=957672
I was still on Intrepid beta, all worked fine, but after the last update
of yesterday, going on RC, at reboot all was normal until login, but
after just a blank screen, with only the mouse
In console mode, it is also written desktop tty1
I tired a sudo apt-get upgrade :
Some errors occurred during execution (I translate from french)
/var/cache/apt/archives/gnome-session_2.24.1-0ubuntu1_i386.deb
/var/cache/apt/archives/gnome-applets_2.24.1-0ubuntu1_i386.deb
Simply choosing a Gnome session at the GDM login screen (instead of the default
that was 'Run Xclient script' according to the message that pops up when
entering password) solved the problem for me. No need to remove the .gnome* etc
directories. Running Intrepid RC or newer, but not newer than
... and lspci -vvnn
** Attachment added: lspci-vvnn.txt
http://launchpadlibrarian.net/1408/lspci-vvnn.txt
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because you are a
For what it's worth: first I thought I had the compiz hanging problem
described at https://bugs.launchpad.net/ubuntu/+bug/259385 but removing
compiz didn't work for me. Compiz works fine after the workaround I
described above.
--
After intrepid upgrade, gnome session won't start unless logging
I resolved this bug on my installation by removing all of the gnome and
compiz config files in my home directory and re-selecting gnome as the
session type in the gdm login screen. Does this work for anyone else?
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
Christopher,
What config files exactly did you remove? I haven't been able to resolve
this issue for my installation.
Seth
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because
I want to confirm that resetting GNOME desktop also allowed me to log
in normally.
I removed the following files:
.gnome .gnome2 .gconf .gconfd .metacity
restarted gdm, selected new Gnome session and I was good to go.
Mark
--
After intrepid upgrade, gnome session won't start unless logging
Per Bryce's suggestion:
- lspci -vvnn output attached
- Booted into intrepid live CD (beta) - worked fine - gave me a clean
gnome session
- get-edid | parse-edid:
[EMAIL PROTECTED]:~# get-edid | parse-edid
get-edid: get-edid version 1.4.1
Performing real mode VBE call
Just noticed that trying to switch to Guest Session from my regular
user account hangs with the same symptoms - i.e. hangs with a light
brown background. Pressing ctr+alt+backspace brought me back to the
password prompt to re-login to my own user account's session.
Should I file this as a
I'm having the same problem after upgrading from Hardy. I have all the
essential Gnome 2.24 packages installed, and the system up-to-date.
Using the Failsafe session works fine. Maybe the problem is something
from Hardy that's not installed on Intrepid?
If there's anything I could do to help,
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) = (unassigned)
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because you are a
I have the same problem as Tom Haddon explained. Do you know any
workaround just to be able use my system?
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because you are a member
I just reinstalled Intrepid beta from CD and everything works fine. This
time I don't install system updates, because last time doing that caused
this problem. So, I think, problem is with those updates. There are more
than 200 of them, so I can't tell exactly which one of them caused this
I think the problem is with removing gnome-control-center and some other
gnome-* packages.
I've just checked for system updates again and noticed changes: no one of
gnome-* packages is going to be removed. Maybe this time it wouldn't brake, but
I don't want to try it, because I'm tired of
I've tried to update system, because I noticed changes in what package
were going to be updated and removed. And, good news, I don't have the
problem described in this report anymore. :)
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
I had this problem today after I did an update of my intrepid amd64
install (hadn't updated in several days). I looked in synaptics and
found that the latest of several gnome packages were not installed,
including gnome-settings-daemon, gnome-control-center, nautilus, gnome-
common, and
i have intrepid running with latest updates - till yesterday i could log
in perfectly, today gdm loads, i log in and then i get nothing but an
application that is scheduled for autostart and a gnome-power-manager
error.
i tried the read-edid thing and seems broken, i'm trying to hardcode
video
Attached Xorg.0.log. Will try the other options mentioned, thx.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/18312748/Xorg.0.log
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this
Ok, I tried the suggested methods as follows:
* Try using the recovery mode option in grub, then Resume normal boot
- Same thing - just stopped loading the gnome session with a light brown
background. Mouse still responsive, but this is the same state as I'm
experiencing normally unless I use
** Attachment added: Contents of /var/log/gdm
http://launchpadlibrarian.net/18351033/gdm.tar.gz
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because you are a member of
** Attachment added: Xorg.0.log while running failsafe gnome session
http://launchpadlibrarian.net/18351154/Xorg.0.log
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because
Here's the error from running with vesa.
(EE) VESA(0): No valid modes
(EE) Screen(s) found, but none have a usable configuration.
Sounds like EDID isn't working for this case; may need to hardcode the
modes for it to work. Odd.
--
After intrepid upgrade, gnome session won't start unless
** Changed in: xserver-xorg-video-intel (Ubuntu)
Sourcepackagename: None = xserver-xorg-video-intel
Importance: Undecided = High
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
Status: New = Triaged
--
After intrepid upgrade, gnome session won't start unless logging
Hi Tom,
I've forwarded this bug upstream to
https://bugs.freedesktop.org/show_bug.cgi?id=17985. Could you please
subscribe to this bug, in case upstream wishes further information or
needs you to test something? Thanks ahead of time.
Also, three other things:
1. Please attach the output of
** Changed in: xorg-server
Status: Unknown = Confirmed
--
After intrepid upgrade, gnome session won't start unless logging into failsafe
gnome
https://bugs.launchpad.net/bugs/279450
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I upgraded too from Hardy to Intrepid, but something with GDM went
wrong.
Now I only see my screen flickering :(
To enter to a somewhat usable desktop, I have to kill X, stop GDM and do
sudo xinit, then close it with ctrl+alt+backspace then do a startx
from a TTY to get to my Gnome Desktop :S
Vladimir, yours sounds like a different problem, and I'd suggest it
needs a different bug report. I can get the gdm login screen fine, it's
just after I've entered my username and password that it fails to
complete the gnome session initialization.
--
After intrepid upgrade, gnome session won't
Bump, and it also happens to me after upgrading from 8.04 to 8.10 via the
update-manager.
I'm running on x86_64 arch, with dual core, 2 GB ram and nVidia GeForce M8400
GS. The hardware being slow is definitely not the problem here. My hard drive
isn't even working when it hangs, either.
The symptoms described are fairly generic so it's hard to say what's
going on. Some things to do:
* Attach your Xorg.0.log. If it is an X bug (which it sort of sounds like),
this is required.
* Try using the recovery mode option in grub, then Resume normal boot
* Try using the recovery mode
44 matches
Mail list logo
