I'd really like to purge my systems of this failsafe-x nonsense. Is
there documentation some where that explain how to disable the
ironically named program? When I was bit by this bug, I didn't have
access to another computer to search for a solution. I didn't have a
console to read the logs.
I had success with Philip's gdm patch! kdm[1064]: X server died during
startup and kdm[1064]: Failed to start X server. Starting failsafe X
server. are not to be found in the syslog.
PLEASE refactor this upstart sprawl. This was a very painful bug for
me. As an Intel IGP owner, I wasn't even
Please disregard the packages in my PPA and use the official proposed
packages. Martin Pitt beat me by a minute.
--
Since failsafe-x was enabled in karmic it starts if gdm is disabled and kdm is
used. (low graphics mode error)
https://bugs.launchpad.net/bugs/491483
You received this bug
So the fix that I'm using, post #30, works because KDM starts faster
because it doesn't have to test drivers?
--
after recent update which included xorg, xserver etc causes low-graphics mode
error at start
https://bugs.launchpad.net/bugs/491483
You received this bug notification because you are
@Philip and Michael
I undid my changes and tried your fix, but I'm still getting the low-
graphics mode error.
syslog shows:
Dec 6 16:00:51 kevthinkpadr61 kdm[1055]: X server died during startup
Dec 6 16:00:51 kevthinkpadr61 kdm[1055]: Failed to start X server. Starting
failsafe X server.
--
I use the free version of NoMachine NX (www.nomachine.com) to connect from my
home PC (current Intrepid, the one
that had this bug a few weeks ago) to a PC at my university (current hardy).
Inside the NX window, the keyboard exhibits
the same behaviour as described here.
I'm having the exact
should have read the all the comments!
fixed by running 'setxkbmap -model evdev -layout us' on the machine
running hardy.
--
Up arrow key mapped to Print [screen]
https://bugs.launchpad.net/bugs/255008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The hard drive in brother's external IDE was once JFS, but is now
formatted NTFS. I had the exact same problem. HAL kept thinking it was
JFS.
This is how I fixed my problem. In
/etc/hal/fdi/policy/preferences.fdi, I added this
device
match key=volume.uuid
