** Changed in: xorg-server
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
To manag
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: xdm (Ubuntu Lucid)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Tags added: maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
To manage notifications about this bug go to:
htt
** Changed in: xdm (Ubuntu Natty)
Status: Triaged => Invalid
** Tags removed: hardy maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can
This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached
end-of-life and is no longer supported, so I am closing the bugtask for
Maverick. Please upgrade to a newer version of Ubuntu.
More information here:
https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html
*
Launchpad has imported 12 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=17325.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
I seem to be seeing this bug also. Trying Slim doesn't get past black
screen after the Ubuntu loading logo.
I don't even get access to the virtual terminals, but I have SSH access
from another computer and the xorg logs seem very similar to the
original poster's, although it seems not to be a perm
Seems that xdm bug is unrelated, it's about consolekit support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
To manage
xdm upstream closed it as wontfix, because they claim nobody is
interested into it. How come???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use
What is the status of this bug - why has it not been assigned to anyone
and why does it seem that no one is doing any work on it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not poss
What is the status of this bug - why has it not been assigned to anyone
and why does it seem that no one is doing any work on it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not poss
** Changed in: slim
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
--
ubuntu-bugs maili
i installed slim through apt-get and also through package files(software
center) and when i type this ,"slim -p
/usr/share/slim/themes/default"login screen screenshot comes up but when
i restart my computer ,it gets struck at boot no login screen appears
.please tell what is wrong i m doing install
Is xdk really the right place to fix it, seeing it also seems to be
broken in SLiM, wdm, and probably every other login manager except kdm
and gdm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Is xdk really the right place to fix it, seeing it also seems to be
broken in SLiM, wdm, and probably every other login manager except kdm
and gdm?
** Also affects: slim
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Changed in: xorg-server
Status: Unknown => Won't Fix
** Changed in: xorg-server
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to
** Bug watch added: freedesktop.org Bugzilla #17325
http://bugs.freedesktop.org/show_bug.cgi?id=17325
** Also affects: xorg-server via
http://bugs.freedesktop.org/show_bug.cgi?id=17325
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a mem
This appears to be caused by the xdm package not integrating with
upstart. The plymouth process which holds the console open is waiting
for a signal that the xdm job is starting up, so that it can let go of
the console; but the xdm package, which is not well cared for in Ubuntu,
doesn't have an up
** Changed in: xdm (Ubuntu)
Importance: Undecided => High
** Changed in: xdm (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible
I can confirm this issue also with maverick on a Intel 915GM. Just starting xdm
after a reboot crashes X with:
[ 158.212] (EE) intel(0): [drm] failed to set drm interface version.
[ 158.212] (EE) intel(0): Failed to become DRM master.
[ 158.212] (**) intel(0): Depth 24, (--) framebuffer bpp 32
[ 1
FTR I'm seeing this on maverick, with radeon.modeset=1 (and options
radeon modeset=1) on a Thinkpad T60p, lspci says "ATI Technologies Inc
M56GL [Mobility FireGL V5200]", with the fglrx drivers --purged (because
they dropped support for this chipset a while back - with the useless
proprietary drive
The workaround in /etc/init.d/slim does work for me in Maverick, but I
am running on an Intel i915 (8086:2A42). I also added "i915.modeset=1"
to my boot options due to bug #566379. Comment 32 for that bug mentions
adding "nomodeset" to boot options so X would work with ATI and Radeon.
--
Not po
The workaround doesn't for for me on Maverick.
** Changed in: slim
Status: New => Confirmed
--
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
https://bugs.launchpad.net/bugs/585853
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
23 matches
Mail list logo
