Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you
continue to experience issues with current releases.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscr
** Changed in: xorg-server
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
To m
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-X,
which is subscribed
** Tags added: maverick
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in 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:
** Changed in: xdm (Ubuntu Natty)
Status: Triaged => Invalid
** Tags removed: hardy maverick
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only
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
*
> Sure, my patch just follows the license of the original code. So it's
> in MIT/X11 license.
Cool. And to be clear, I only asked because of the license issue with
the first patch on this bug report.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
Sure, my patch just follows the license of the original code. So it's
in MIT/X11 license.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use g
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-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
To ma
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-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can
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-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not
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-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not
** Changed in: slim
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in Ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
_
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-X,
which is subscribed to xdm in ubuntu.
https://bugs.launchpad.net/bugs/585
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-X,
which
** 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-X,
which is subscribed to xdm in ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not possible
** 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-X,
which is subscribed to xdm in ubuntu.
https://bugs.launchpad.net/bugs/585853
Title:
Not poss
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-X,
which is subscribe
Same problem on Radeon 9250 / Maverick.
** Tags added: maverick
** Summary changed:
- [Lucid] Not possible to use xdm, only can use gdm
+ Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
--
Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
https://bugs.launchpad.ne
Slightly better workaround:
In "/etc/init.d/slim" replace:
start-stop-daemon --start $SSD_START_ARGS ||echo -n " already running"
with:
if [ "$(pidof slim)" ]
then
echo -n " already running"
else
exec /usr/bin/slim
fi
--
[Lucid] Not possible to use xdm, only can use gdm
https://bugs.launc
** Also affects: slim
Importance: Undecided
Status: New
--
[Lucid] Not possible to use xdm, only can use gdm
https://bugs.launchpad.net/bugs/585853
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in ubuntu.
___
I can confirm this bug affects both xdm and slim. Running the slim
binary directly ("/usr/bin/slim") will work, but calling it through
star-stop-daemon ("start-stop-daemon --start --name slim --startas
/usr/bin/slim") will cause the error reported in the bug.
Messy workaround for now:
In "/etc/ini
I ran into this problem with xdm and xinit, so I tried switching to SLiM
(Simple Login Manager - http://slim.berlios.de/), but I ran into the
same problem. It works great, if I've run GDM first, but it fails
otherwise. I would like to use something other than GDM.
--
[Lucid] Not possible to use
xinit behaves in the same way as xdm.
drmSetMaster is in xf86drm.c of libdrm, and does an ioctl. How can this be
different for gdm vs xdm?
--
[Lucid] Not possible to use xdm, only can use gdm
https://bugs.launchpad.net/bugs/585853
You received this bug notification because you are a member of Ub
Now I see how I was "lucky" in 7:
If you run gdm, kill it, then xdm will work.
Somehow gdm manages to initialise drm, ie avoids:
(EE) intel(0): [drm] failed to set drm interface version.
(EE) intel(0): Failed to become DRM master.
So simply, I had a some stage run gdm => xdm thereafter, no matte
It seems that I was luckily to get a prompt - I can't get the prompt
repeatedly - diffing against the without -keeptty Xorg.0.log, the only
difference with -keeptty is that there is no "Operation not permitted" -
the drm still fails.
--
[Lucid] Not possible to use xdm, only can use gdm
https://bu
Making Xorg setuid (with hindsight obviously) didn't change anything.
The
(WW) xf86OpenConsole: setpgid failed: Operation not permitted
(WW) xf86OpenConsole: setsid failed: Operation not permitted
of the original report is definitely the cause. Looking at a copy of
xorg I happen to have, i.e., n
** Tags added: hardy
--
[Lucid] Not possible to use xdm, only can use gdm
https://bugs.launchpad.net/bugs/585853
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in ubuntu.
___
Mailing list: https://la
** Tags removed: needs-xorglog
** Tags removed: needs-lspci-vvnn
** Changed in: xdm (Ubuntu)
Status: Incomplete => Confirmed
--
[Lucid] Not possible to use xdm, only can use gdm
https://bugs.launchpad.net/bugs/585853
You received this bug notification because you are a member of Ubuntu-X
Is it right that
$ ls -l /usr/bin/Xorg
-rwxr-xr-x 1 root root 1901280 2010-04-23 18:16 /usr/bin/Xorg
? (I am used to seeing -rws--x--x, then again this must be OK for gdm to
work)
--
[Lucid] Not possible to use xdm, only can use gdm
https://bugs.launchpad.net/bugs/585853
You received this bug n
This Xorg.0.log is from a broken xdm run, so shows the "Operation not
permitted" written up in the bug report. No more info than in the
original bug report, but provided for the "needinfo" hoop. It would be
nice to actually get to working on resolving the bug...
** Attachment added: "Xorg.0.log"
lspci --vvnn output
Just provided to jump through "needinfo" hoop - no useful information here.
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/49208418/lspci-vvnn.log
--
[Lucid] Not possible to use xdm, only can use gdm
https://bugs.launchpad.net/bugs/585853
You received
** Tags added: lucid
--
[Lucid] Not possible to use xdm, only can use gdm
https://bugs.launchpad.net/bugs/585853
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in ubuntu.
___
Mailing list: https://la
So, I just jumped through the hoop to get around the "needinfo" tag - I
think you'll find that all the necessary info is in fact in the original
bug report. Extra precise requests for particular experiments to try and
particular bits of missing information will gladly be provided. This
general "sen
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: xdm
Bug discovered after upgrading an xdm-using 8.04.2 LTS x86_64-desktop
laptop to 10.04 LTS, but now repeated as follows.
Take default gdm-using 10.04 LTS x86_64-desktop laptop
aptit
Hi Patrick,
Please run the command 'apport-collect BUGNUMBER', which will attach several
files we need for debugging.
[This is an automated message. Apologies if it has reached you
inappropriately; please just reply to this message indicating so.]
** Tags added: needs-xorglog
** Tags added:
Public bug reported:
Binary package hint: xdm
Bug discovered after upgrading an xdm-using 8.04.2 LTS x86_64-desktop
laptop to 10.04 LTS, but now repeated as follows.
Take default gdm-using 10.04 LTS x86_64-desktop laptop
aptitude install xdm
and set xdm as the default window manager
restart
You
45 matches
Mail list logo
