[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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.net/bugs/585853 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/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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.launchpad.net/bugs/585853 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/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
** 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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/init.d/slim" replace:
start-stop-daemon --start $SSD_START_ARGS ||echo -n " already running"
with:
exec $DAEMON
A similar workaround will work for xdm too.
--
[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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [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 use xdm, only can use gdm https://bugs.launchpad.net/bugs/585853 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/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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 what I tried, would work. Any clues anyone? (This is an intel (xdriinfo says i965) which I think means that the X driver needs kernel support. What stumps me, is that gdm works, therefore the kernel support must be there, and the driver OK - but what is the difference between the way gdm calls Xorg and the way xdm calls it?) -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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://bugs.launchpad.net/bugs/585853 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/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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., not necessarily the one used in ubuntu, I see that in xorg-server/dist/hw/xfree86/os-support/linux/lnx_init.c, the calls to setpgid() and setsid() are enclosed in an if(!KeepTty) block. Adding -keeptty to /etc/X11/xdm/Xservers gets me an xdm login prompt and avoids the hang. This isn't the answer, as -keeptty isn't meant for usual operation, and again makes me wonder how gdm is treated differently - as the call is made by the same server in each case. -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
** 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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 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/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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" http://launchpadlibrarian.net/49208519/Xorg.0.log -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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 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/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
** 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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 us loads of logs which may or may not contain the needle in the haystack" (as these are now collected on the working gdm) seems silly... -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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
aptitude install xdm
and set xdm as the default window manager
restart
You will now see the ubuntu white/red dots animation, and that's as far as
things go.
ctrl-alt f1 gets you a log in prompt
ps ax | grep dm
shows nothing - so this isn't the same as the "both gdm and xdm run" bug.
In fact
ps ax | grep -i x
returns nothing.
Extras: x.org x server v 1.7.6, intel graphics controller. According to
kern.log
fb0: inteldrmfb frame buffer device
... drm Initialized i915
vga16fb: not registering due to another framebuffer present
so things should be set for X to start, namely drm Initialized looks
hopeful
Yet running xdm -debug 2 from vt1 shows
...
/usr/bin/X :0 vt7 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/...
(all OK)
...
(EE) intel(0): [drm] failed to set drm interface version.
Failed to become DRM master.
failed to get resources: Bad file descriptor
Kernel modesetting setup failed
(EE) Screen(s) found, but none have a useable configuration.
Also surprising as:
drmOpenDevice: node name is /dev/dri/card0
open result is 9 (OK)
(Chipset GM45)
So, how come X thinks drm isn't setup, yet the kernel thinks it is?
Work around: put gdm back as default with dpkg-reconfigure {gdm|xdm}
Now comparing Xorg.0.log in broken xdm and working gdm cases, xdm has:
xf86OpenConsole: setpgid failed: Operation not permitted
xf86OpenConsole: setsid failed: Operation not permitted
and later drmOpenByBusid returns nothing as opposed to pci::00:02.0
So, why the permission denied? apparmor not treating xdm as well as it
treats gdm?
(no ubuntu-bug -p xdm included, as I am writing this on a working single-boot
NetBSD/i386 laptop)
+ ---
+ Architecture: amd64
+ DistroRelease: Ubuntu 10.04
+ Package: xdm 1:1.1.8-6ubuntu2
+ PackageArchitecture: amd64
+ ProcEnviron:
+ LANGUAGE=en_GB:en
+ LANG=en_GB.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
+ Tags: lucid
+ Uname: Linux 2.6.32-22-generic x86_64
+ UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49203672/Dependencies.txt
--
[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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 585853] Re: [Lucid] Not possible to use xdm, only can use gdm
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: needs-lspci-vvnn ** Changed in: xdm (Ubuntu) Status: New => Incomplete -- [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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
