ArchiveOrangemail archive

Ubuntu bug tracker changes - HIGH VOLUME


ubuntu-bugs.lists.ubuntu.com
(List home) (Recent threads) (282 other Ubuntu lists)

Subscription Options

  • RSS or Atom: Read-only subscription using a browser or aggregator. This is the recommended way if you don't need to send messages to the list. You can learn more about feed syndication and clients here.
  • Conventional: All messages are delivered to your mail address, and you can reply. To subscribe, send an email to the list's subscribe address with "subscribe" in the subject line, or visit the list's homepage here.
  • This list contains about 2,645,665 messages, beginning Jun 2009
  • This list doesn't seem to be active
Report the Spam
This button sends a spam report to the moderator. Please use it sparingly. For other removal requests, read this.
Are you sure? yes no

[NEW] [Lucid] Not possible to use xdm, only can use gdm

Ad
Patrick Welche 1274882147Wed, 26 May 2010 13:55:47 +0000 (UTC)
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 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:0000: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)

** Affects: xdm (Ubuntu)
     Importance: Undecided
         Status: New
Bryce Harrington 1274962253Thu, 27 May 2010 12:10:53 +0000 (UTC)
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
Patrick Welche 1274964357Thu, 27 May 2010 12:45:57 +0000 (UTC)
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:0000: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/Depend...
Patrick Welche 1274964360Thu, 27 May 2010 12:46:00 +0000 (UTC)
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...
Bryce Harrington 1274967077Thu, 27 May 2010 13:31:17 +0000 (UTC)
** Tags added: lucid
Patrick Welche 1274968858Thu, 27 May 2010 14:00:58 +0000 (UTC)
lspci --vvnn output
Just provided to jump through "needinfo" hoop - no useful information here.

** Attachment added: "lspci-vvnn.log"
   http://launchpadlibrarian.net/49208418/lspci-...
Patrick Welche 1274968862Thu, 27 May 2010 14:01:02 +0000 (UTC)
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...
Patrick Welche 1274976666Thu, 27 May 2010 16:11:06 +0000 (UTC)
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)
Bryce Harrington 1275042050Fri, 28 May 2010 10:20:50 +0000 (UTC)
** Tags removed: needs-xorglog

** Tags removed: needs-lspci-vvnn

** Changed in: xdm (Ubuntu)
       Status: Incomplete => Confirmed
Bryce Harrington 1275053144Fri, 28 May 2010 13:25:44 +0000 (UTC)
** Tags added: hardy
Patrick Welche 1275147942Sat, 29 May 2010 15:45:42 +0000 (UTC)
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.
Patrick Welche 1275160246Sat, 29 May 2010 19:10:46 +0000 (UTC)
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.
Patrick Welche 1275238878Sun, 30 May 2010 17:01:18 +0000 (UTC)
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?)
Patrick Welche 1275308467Mon, 31 May 2010 12:21:07 +0000 (UTC)
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?
Richard Griswold 1278960675Mon, 12 Jul 2010 18:51:15 +0000 (UTC)
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.
Thorin Hopkins 1279277150Fri, 16 Jul 2010 10:45:50 +0000 (UTC)
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.
Thorin Hopkins 1279277447Fri, 16 Jul 2010 10:50:47 +0000 (UTC)
** 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.
Thorin Hopkins 1279278663Fri, 16 Jul 2010 11:11:03 +0000 (UTC)
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.
Yury V. Zaytsev 1288965078Fri, 05 Nov 2010 13:51:18 +0000 (UTC)
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.
Yury V. Zaytsev 1288965682Fri, 05 Nov 2010 14:01:22 +0000 (UTC)
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 subscribed to Ubuntu.
Richard Griswold 1288975577Fri, 05 Nov 2010 16:46:17 +0000 (UTC)
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 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.
Mark Eichin 1292198169Sun, 12 Dec 2010 23:56:09 +0000 (UTC)
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 drivers installed, X starts fine but all GL code (glxinfo,
glxgears) dies with a near-immediate coredump.)

With the "start gdm, kill gdm, start xdm" workaround, I get working
glxinfo and glxgears.

(I haven't tried turning off modeset with fglrx purged, yet.)-- 
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)
Robert Weidlich 1293189667Fri, 24 Dec 2010 11:21:07 +0000 (UTC)
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
[ 158.212] (==) intel(0): RGB weight 888
[ 158.212] (==) intel(0): Default visual is TrueColor
[ 158.212] (II) intel(0): Integrated Graphics Chipset: Intel(R) 915GM
[ 158.212] (--) intel(0): Chipset: "915GM"
[ 158.212] (==) intel(0): video overlay key set to 0x101fe
[ 158.212] (EE) intel(0): failed to get resources: Bad file descriptor
[ 158.212] (EE) intel(0): Kernel modesetting setup failed

Starting kdm, stopping kdm and then starting xdm works as already
described before.-- 
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)
Steve Langasek 1298496167Wed, 23 Feb 2011 21:22:47 +0000 (UTC)
** 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 to use xdm/wdm, only can use gdm (Lucid, Maverick)
Steve Langasek 1298496721Wed, 23 Feb 2011 21:32:01 +0000 (UTC)
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 upstart job, so there's no signal sent, which means the
plymouth and xdm processes are fighting over the console.

Marking bug #723698 as a duplicate of this one.  This is unfixed in
natty, maverick and lucid.

** Project changed: slim => lqueue

** Also affects: xdm (Ubuntu Lucid)
   Importance: Undecided
       Status: New

** Also affects: xdm (Ubuntu Maverick)
   Importance: Undecided
       Status: New

** Also affects: xdm (Ubuntu Natty)
   Importance: High
       Status: Triaged

** Changed in: xdm (Ubuntu Maverick)
       Status: New => Triaged

** Changed in: xdm (Ubuntu Lucid)
       Status: New => Triaged

** Changed in: xdm (Ubuntu Lucid)
   Importance: Undecided => High

** Changed in: xdm (Ubuntu Maverick)
   Importance: Undecided => 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 use xdm/wdm, only can use gdm (Lucid, Maverick)
Martin Pitt 1298641865Fri, 25 Feb 2011 13:51:05 +0000 (UTC)
** Bug watch added: freedesktop.org Bugzilla #17325
   http://bugs.freedesktop.org/show_bug.cgi?id=1...

** Also affects: xorg-server via
   http://bugs.freedesktop.org/show_bug.cgi?id=1...
   Importance: Unknown
       Status: Unknown-- 
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)
Bug Watch Updater 1298644277Fri, 25 Feb 2011 14:31:17 +0000 (UTC)
** 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 use xdm/wdm, only can use gdm (Lucid, Maverick)
The Compiler 1298649361Fri, 25 Feb 2011 15:56:01 +0000 (UTC)
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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/585853

Title:
  Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
The Compiler 1298649365Fri, 25 Feb 2011 15:56:05 +0000 (UTC)
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

Title:
  Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
Prashant Gupta 1302370564Sat, 09 Apr 2011 17:36:04 +0000 (UTC)
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 installed all libraries given in
packages manually but still no solution-- 
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)
jimmy the saint 1302723099Wed, 13 Apr 2011 19:31:39 +0000 (UTC)
** 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)
Peter Byrne 1303549856Sat, 23 Apr 2011 09:10:56 +0000 (UTC)
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 possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
Peter Byrne 1303549859Sat, 23 Apr 2011 09:10:59 +0000 (UTC)
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 possible to use xdm/wdm, only can use gdm (Lucid, Maverick)
Yury V. Zaytsev 1304170292Sat, 30 Apr 2011 13:31:32 +0000 (UTC)
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 gdm (Lucid, Maverick)
Yves-Alexis Perez 1309338236Wed, 29 Jun 2011 09:03:56 +0000 (UTC)
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 notifications about this bug go to:
https://bugs.launchpad.net/lqueue/+bug/585853...
Robert Muil 1320512757Sat, 05 Nov 2011 17:05:57 +0000 (UTC)
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 permissions issue. The
intel driver and drm issue seems to be there...

The workaround in comment #13 works for me. Thank you very much.

Hope this can be fixed properly. Gnome 3 may be beautiful, but it's more
or less useless on slower computers.

** Attachment added: "Xorg.0.log"
   https://bugs.launchpad.net/ubuntu/+source/xdm...-- 
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:
https://bugs.launchpad.net/lqueue/+bug/585853...
Bug Watch Updater 1327825860Sun, 29 Jan 2012 08:31:00 +0000 (UTC)
Launchpad has imported 12 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=....

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://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-08-27T12:03:28+00:00 Pavol Rusnak wrote:

Created attachment 18543
mandriva patches against xdm 1.1.8

XDM lacks consolekit support. This results in various problem when XDM
is used to login into desktop: for example, DBus messages are blocked by
PolicyKit.

I found a set of patches from KDM adapted to XDM in Mandriva SRPMS, but
I wonder why they are not upstreamed.

CCing SUSE and Mandriva Xdm maintainers.

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...

------------------------------------------------------------------------
On 2008-10-13T13:25:15+00:00 Pavol Rusnak wrote:

Paulo (pcpa): are there any specific reasons why these patches are not
upstreamed?

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...------------------------------------------------------------------------
On 2008-10-13T17:54:22+00:00 Pcpa wrote:

(In reply to comment #1)
> Paulo (pcpa): are there any specific reasons why these patches are not
> upstreamed?None that I know of. But I am afraid I don't understand consolekit
very well. I did the patch upon request, based on kde3 kdm's patches.

  But I was told it is working correctly.


Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...

------------------------------------------------------------------------
On 2008-10-13T19:46:48+00:00 Alan Coopersmith wrote:

While I don't understand what all the changes in those patches are for,
I do understand the GPLv2 header in the new consolekit files - X.Org does
not accept any GPL licensed code in our apps, so these patches will not
be acceptable until relicensed under an MIT-style license.

>From a technical standpoint:
- 0004-Support-kdm-extended-syntax-to-reserve-a-server-for.patch 
   - is this really needed for consolekit?   This seems unrelated.

-0005-Initialize-the-greeter-only-after-checking-if-the-th.patch 
   - seems reasonable, though I wonder about side-effects in people's
     setup scripts, if any assumed the xdm greeter window was displayed first

-0006-Ass-console-kit-support-to-xdm.patch
   - I might make this a bit less #ifdef heavy, but it seems okay

-consolekit-xdm/0007-Add-files-required-by-consolekit-support.patch
   - I don't know enough dbus or consolekit to comment on most of this
   - The /proc/%d/stat section would need to be #ifdef linux

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...

------------------------------------------------------------------------
On 2009-08-08T10:08:56+00:00 Sndirsch-suse wrote:

Created attachment 28437
xdm-consolekit.diff

This is a patch by Takashi Iwai we're planning to use for openSUSE 11.2.
See

  https://bugzilla.novell.com/show_bug.cgi?id=5...

for more details.

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...

------------------------------------------------------------------------
On 2010-04-03T10:14:43+00:00 Sndirsch-suse wrote:

Created attachment 34643
xdm-consolekit.diff

Now with better error message when console-kit-daemon is not
available/running

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...

------------------------------------------------------------------------
On 2010-09-11T16:45:16+00:00 Sndirsch-suse wrote:

It seems nobody apart from Mandriva/openSUSE is interested into having
this support in xdm. Hence closing as WONTFIX.

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...------------------------------------------------------------------------
On 2012-01-28T14:38:33+00:00 Samuli Suominen wrote:

(In reply to comment #6)
> It seems nobody apart from Mandriva/openSUSE is interested into having this
> support in xdm. Hence closing as WONTFIX.Untrue as both ArchLinux and Gentoo are carrying custom patch to enable
native ConsoleKit support in XDM too.

Can we reopen this bug, please?

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...

------------------------------------------------------------------------
On 2012-01-28T16:56:38+00:00 James H. Cloos Jr. wrote:

Four downstream dists seem like enough.

Reviews of each of the three as of yet unreviewed patches are welcome.

These urls are mentioned in Gentoo’s patch:

http://bugs.gentoo.org/360987
http://projects.archlinux.org/svntogit/packag...
http://lists.x.org/archives/xorg-devel/2011-F...
http://bugs.debian.org/cgi-bin/bugreport.cgi?...


Samuli:  I don’t see any license info in the patch in portage; it is definitively under an MIT-style license?

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...------------------------------------------------------------------------
On 2012-01-28T18:05:57+00:00 Alan Coopersmith wrote:

(In reply to comment #8)
> Four downstream dists seem like enough.
> 
> Reviews of each of the three as of yet unreviewed patches are welcome.Yes, as maintainer, I've been waiting for someone to review the patches
on the xorg-devel list (since I don't have time to learn enough about the
consolekit API myself to figure out if they're doing the right things) and 
not really caring if someone is playing games with the bug state here 
because they're feeling pissy.

Hopefully between those four dists you can find at least *one* person
willing to put in the time to give the patches a review.

I will impose only two absolutely required conditions on such patches:
 - Unlike the first set submitted for this bug, they must be under a
   MIT license, not changing the xdm license to GPL or anything else.
 - They must do whatever autoconf or other checks are necessary to 
   avoid breaking systems without consolekit.

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...------------------------------------------------------------------------
On 2012-01-28T20:28:08+00:00 Samuli Suominen wrote:

(In reply to comment #8)
> Four downstream dists seem like enough.
> 
> Reviews of each of the three as of yet unreviewed patches are welcome.
> 
> These urls are mentioned in Gentoo’s patch:
> 
> http://bugs.gentoo.org/360987
> http://projects.archlinux.org/svntogit/packag...
> http://lists.x.org/archives/xorg-devel/2011-F...
> http://bugs.debian.org/cgi-bin/bugreport.cgi?...
> 
> 
> Samuli:  I don’t see any license info in the patch in portage; it is
> definitively under an MIT-style license?The patch in Arch and Gentoo is modified (improved) copy of the OpenSuSE
patch. So license is presumably same as what OpenSuSE is using for their
patch.

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...------------------------------------------------------------------------
On 2012-01-28T20:31:57+00:00 Samuli Suominen wrote:

(In reply to comment #9)
>  - They must do whatever autoconf or other checks are necessary to 
>    avoid breaking systems without consolekit.This seems to be covered with the Arch/Gentoo patch based on testing.
Tested it pretty exhaustively before pushing it to our users.

Reply at: https://bugs.launchpad.net/lqueue/+bug/585853...


** Changed in: xorg-server
       Status: Won't Fix => In Progress

** Bug watch added: Novell/SUSE Bugzilla #528829
   https://bugzilla.novell.com/show_bug.cgi?id=5...

** Bug watch added: Debian Bug tracker #615020
   http://bugs.debian.org/cgi-bin/bugreport.cgi?...-- 
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:
https://bugs.launchpad.net/lqueue/+bug/585853...
Takashi Iwai 1328016057Tue, 31 Jan 2012 13:20:57 +0000 (UTC)
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
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:
https://bugs.launchpad.net/lqueue/+bug/585853...
James H. Cloos Jr. 1328016061Tue, 31 Jan 2012 13:21:01 +0000 (UTC)
> 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
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:
https://bugs.launchpad.net/lqueue/+bug/585853...
JC Hulce 1336039960Thu, 03 May 2012 10:12:40 +0000 (UTC)
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-anno...

** Changed in: xdm (Ubuntu Maverick)
       Status: Triaged => 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 manage notifications about this bug go to:
https://bugs.launchpad.net/lqueue/+bug/585853...
dino99 1368194253Fri, 10 May 2013 13:57:33 +0000 (UTC)
** 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 use gdm (Lucid, Maverick)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lqueue/+bug/585853...
bugbot 1368701449Thu, 16 May 2013 10:50:49 +0000 (UTC)
** 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:
https://bugs.launchpad.net/lqueue/+bug/585853...
Ad
Home | About | Privacy