Bug 339035 – x11-base/xorg-server-1.9.0-r1 - missing "${FILESDIR}"/xdm.initd-2 xdm

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description avx 2010-09-28 14:28:54 UTC]

Merging xorg-server-1.9.0-r1 currently fails because of a missing file and/or typo.

Reproducible: Always

Steps to Reproduce:
1. emerge --sync
2. emerge -u xorg-server
3.

Actual Results:  
!!! newinitd: /usr/portage/gentoo/x11-base/xorg-server/files/xdm.initd-2 does not exist

Expected Results:  
clean merge

[Comment 1 Robert Cabrera 2010-09-28 14:54:44 UTC]

Same problem here on my ~x86 laptop.

Emerge dies with the following message:

Making install in xi2
 /usr/bin/install -c -m 644 xorg-server.m4 '/var/tmp/portage/x11-base/xorg-server-1.9.0-r1/image//usr/share/aclocal'
 /usr/bin/install -c -m 644 xorg-server.pc '/var/tmp/portage/x11-base/xorg-server-1.9.0-r1/image//usr/lib/pkgconfig'
 * Moving GL files for dynamic switching ...                                                                                        [
!!! newinitd: /usr/portage/x11-base/xorg-server/files/xdm.initd-2 does not exist
 * ERROR: x11-base/xorg-server-1.9.0-r1 failed:
 *   initd file install failed
 * 
 * Call stack:
 *     ebuild.sh, line  56:  Called src_install
 *   environment, line 3819:  Called die
 * The specific snippet of code:
 *       newinitd "${FILESDIR}"/xdm.initd-2 xdm || die "initd file install failed";
 * 
 * If you need support, post the output of 'emerge --info =x11-base/xorg-server-1.9.0-r1',
 * the complete build log and the output of 'emerge -pqv =x11-base/xorg-server-1.9.0-r1'.
 * The complete build log is located at '/var/tmp/portage/x11-base/xorg-server-1.9.0-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-base/xorg-server-1.9.0-r1/temp/environment'.
 * S: '/var/tmp/portage/x11-base/xorg-server-1.9.0-r1/work/xorg-server-1.9.0'
 * QA Notice: file does not exist:
 * 
 *      newinitd: /usr/portage/x11-base/xorg-server/files/xdm.initd-2 does not exist

If I recall, there was a similar though not exact problem with the previous release of xorg-server-1.9.0 (The lines where the build failed are slightly different, but both relate to a non-existent xdm.initd-2). 

That bug was # 336997 which was fixed shortly after it was originally released.

I hope this helps.

[Comment 2 Samuli Suominen (RETIRED) 2010-09-28 15:35:22 UTC]

*** Bug 339038 has been marked as a duplicate of this bug. ***

[Comment 3 thunderrd 2010-09-28 15:53:27 UTC]

*** Bug 339041 has been marked as a duplicate of this bug. ***

[Comment 4 Michał Górny 2010-09-28 17:33:52 UTC]

Fixed in rev1.2:

Tue Sep 28 15:05:56 2010 UTC (2 hours, 27 minutes ago) by scarabeus 
Branch: MAIN 
CVS Tags: HEAD 
Changes since 1.1: +2 -2 lines
Fix typo

(Portage version: 2.2_rc87/cvs/Linux x86_64)

[Comment 5 Frank Hellmuth 2010-09-28 17:37:54 UTC]

I don't know if this is the same bug, but at least it seems related:

x11-base/xorg-server-1.9.0-r1 builds and installs here (~amd64) but xdm fails to start because of a missing init-script "xdm-setup", needed by the line

        need localmount xdm-setup

in /etc/init.d/xdm. There is no file xdm-setup in /etc/init.d, just xdm.

Something seems to be serious broken in xorg-server-1.9.0-r1, this leaves the user without a working Xsession manager after a reboot or X restart ... :(

[Comment 6 Lars Wendler (Polynomial-C) (RETIRED) 2010-09-28 18:37:00 UTC]

(In reply to comment #5)
> I don't know if this is the same bug, but at least it seems related:
> 
> x11-base/xorg-server-1.9.0-r1 builds and installs here (~amd64) but xdm fails
> to start because of a missing init-script "xdm-setup", needed by the line
> 
>         need localmount xdm-setup
> 
> in /etc/init.d/xdm. There is no file xdm-setup in /etc/init.d, just xdm.
> 
> Something seems to be serious broken in xorg-server-1.9.0-r1, this leaves the


> user without a working Xsession manager after a reboot or X restart ... :(
> 

Frank, your problem is unrelated to this bug. Please have a look at bug #338257

[Comment 7 Lars Wendler (Polynomial-C) (RETIRED) 2010-09-28 21:55:32 UTC]

Forget my previous comment. bug #339058 is what you should look for...