** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Fix Released
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
This bug has been resolved since Jaunty.
Working fine in Karmic and now Lucid.
.b.
On 10-05-04 01:24 PM, Bryce Harrington wrote:
> [This is an automatic notification.]
>
> Hi b,
>
> This bug was reported against an earlier version of Ubuntu, can you
> test if it still occurs on Lucid?
>
> Ple
[This is an automatic notification.]
Hi b,
This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal sup
** Tags added: crash
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
** Tags added: hardy
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
Resolved by Jaunty upgrade.
I just re-enabled gdm with dpkg-reconfigure after upgrade and gdm
suddenly starts. I made no config changes.
Thanks.
.b.
Bryce Harrington wrote:
> ** Changed in: xorg-server (Ubuntu)
>Status: Confirmed => Triaged
>
--
gdm fails to start after hardy upgrade
h
"Logitech USB Receiver" is my wireless mouse.
It just means I was switched away (on the KVM) from this machine when X
started. I also tried it without switching away, the same thing happens.
I have intrepid on my powerbook now also, but it was working fine with
GDM. I think its likely a configura
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Triaged
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Hmm, well the startx log has this error:
(EE) Logitech USB Receiver: Read error: No such device
Not sure... probably next step is for this bug to go upstream.
** Changed in: xorg-server (Ubuntu)
Importance: Medium => High
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/
** Description changed:
Binary package hint: gdm
I've just upgraded my gutsy machine to hardy.
The installation went well, not errors or issues.
After the first reboot the machine does not start gdm anymore (rather
the X server starts and crashes) Eventually I get this error in
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/21808161/Xorg.0.log
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Hi Bryce,
This is what I did for the intitial report (on gutsy):
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/259156/comments/4
startx works fine, XDM works fine, GDM will not start X.
I don't see any significant differences between those results and these.
Attached.
I agree that
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, w
Well, even simpler, please do this:
1. switch to a tty (ctrl-alt-f3) and login
2. sudo /etc/init.d/gdm stop
3. pkill X
At this point, you should have no gdm or X processes running.
Doublecheck this by running 'ps aux | grep X' and 'ps aux | grep gdm'.
Next, start up X by hand:
4. startx
Po
Attached is my gdm.conf
How can I confirm (overwrite) this file to make sure its the proper
fresh installed config? I don't recall making any changes to it.
Thanks,
.b.
Bryce Harrington wrote:
> Hmm, looking at all the various logs, there still doesn't seem to be any
> error message indicating t
Hmm, looking at all the various logs, there still doesn't seem to be any
error message indicating that X is doing something wrong. So not sure
that this can be troubleshot from the X angle... I know this was
rejected as not being a gdm issue, but given that xdm is working, it
makes me wonder if t
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
I upgraded to intrepid, and the same GDM issue exists.
Still happily using xdm for now.
I've attached the logs for this version.
.b.
b wrote:
> Hi Bryce,
>
> I gave gdm another try today, still the same behaviour. This is how I
> test:
>
> sudo /etc/init.d/xdm stop
> sudo dpkg-reconfigure gdm
Hi Bryce,
I gave gdm another try today, still the same behaviour. This is how I
test:
sudo /etc/init.d/xdm stop
sudo dpkg-reconfigure gdm # Select gdm as default display manager
sudo /etc/init.d/gdm start # gdm fails to start X
Thanks,
B.
Bryce Harrington wrote:
> [This is an automat
[This is an automated message]
Hi ben-ekran,
Please attach the output of `lspci -vvnn` too.
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you ar
I've installed the recent updates.
No change in GDM failure.
I've now configured XDM for gnome, and gnome seems to be working fine.
What is the best way to reset GDM configuration settings? I tried sudo
dpkg-reconfigure gdm, but gdm will still not start X. (XDM works fine).
.b.
b wrote:
> So o
So on a hunch I tried installing ol XDM.
xdm does appear to work, it starts X fine, provides a login window, and
allows a login.
I seem only to be able to log into xfce and not gnome.
So something is different about what GDM attempts to do and what XDM
does.
Thanks,
B. Bogart
--
gdm fails to
I just updated the machine today.
Still having the same issue, GDM is unable to start X. Syslog says:
Gtk-WARNING: cannot open display: :0
WARNING: failsafe dialog failed (inhibitions: 0 0)
for each of the 6 gdm attempts.
For each one I see the cursor flash and then X dies.
happens with all xo
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: gdm => xorg-server
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
the issue doesn't really seem to be a gdm bug
** Changed in: gdm (Ubuntu)
Importance: Undecided => Medium
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The machine has locked up solid twice in the last week.
ssh connections freeze and timeout, and the console keyboard does not
respond (no VT switching or any other feedback from keyboard input).
The logs show nothing, no errors. I checked the disk with smart, and it
reports no errors.
So I went
I realized that once GDM is started that I can log into the machine via
XDMCP. Things seem to work the same as when using startx.
The missing menu and crashing applets made me wonder so I ran:
dpkg-reconfigure `dpkg -l "*gnome*" | grep ^ii | cut -d " " -f 3`
to reconfigure all packages with gnom
** Tags added: valid-xorg-conf
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
** Changed in: gdm (Ubuntu)
Status: Incomplete => New
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Any other suggestions for debugging? I believe I've supplied enough
information for this to be no longer marked as incomplete.
Correct me if I'm wrong.
B. Bogart
b wrote:
> Thanks Chris,
>
> Here are the logs from /etc/init.d/gdm start (after stop) using the
> reconfigured xorg file.
>
> I've
Thanks Chris,
Here are the logs from /etc/init.d/gdm start (after stop) using the
reconfigured xorg file.
I've run this machine for most of its life with ACPI disabled, as it
seems to cause crashes with nvidia drivers.
If the ACPI was the problem, then startx should not work either.
Maybe somet
If the NVIDIA driver is not explicitly enabled in your xorg.conf, then
Xorg will not load it. That error you see is because there is no
compatible NVIDIA driver found (because it isn't loaded). Your Xorg log
file from the attempt when you ran with the NVIDIA driver shows that the
driver loading ok
Thanks Chris,
I think I've found the problem.
Looks like GDM is trying to run X with the nvidia driver and failing:
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not
found)
This is when using the xorg failsafe configuration.
So I tried using my nvidia xorg.
For each X gu
Thank you for taking the time to report this bug and help make Ubuntu
better. However, after having a quick look through your X server log
files, I can't see anything drastically wrong with your X server. Could
you please try to start GDM with your default configuration (when it
fails), and then ad
** Attachment added: "xorg.conf.failsafe"
http://launchpadlibrarian.net/16904897/xorg.conf.failsafe
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "xorg.log.gdm.nv"
http://launchpadlibrarian.net/16904916/xorg.log.gdm.nv
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
** Attachment added: "xorg.log.startx.nv"
http://launchpadlibrarian.net/16904917/xorg.log.startx.nv
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "xorg.log.gdm.vesa"
http://launchpadlibrarian.net/16904920/xorg.log.gdm.vesa
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
** Attachment added: "xorg.log.startx.vesa"
http://launchpadlibrarian.net/16904932/xorg.log.startx.vesa
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "xorg.log.gdm.nvidia"
http://launchpadlibrarian.net/16904933/xorg.log.gdm.nvidia
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "xorg.log.startx.nvidia"
http://launchpadlibrarian.net/16904946/xorg.log.startx.nvidia
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Attachment added: "xorg.log.gdm.vesa-failsafe"
http://launchpadlibrarian.net/16904949/xorg.log.gdm.vesa-failsafe
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "xorg.log.startx.vesa-failsafe"
http://launchpadlibrarian.net/16904960/xorg.log.startx.vesa-failsafe
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/16904691/xorg.conf
--
gdm fails to start after hardy upgrade
https://bugs.launchpad.net/bugs/259156
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
45 matches
Mail list logo
