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)
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
** 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.
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
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
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
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 matter
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.,
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
** 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
** 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:
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
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 send
** 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:
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
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
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
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
18 matches
Mail list logo
