x11-apps/xinit-1.3.1-r1 includes a default /etc/X11/xinit/xinitrc script which, if no other configuration is specified, defaults to starting apps twm, xclock, and xterm. However, x11-apps/xinit-1.3.1-r1 does not require these packages, so this default configuration fails. This problem was reported in bug 385261, with the curious resolution that because most users won't use this default, the problem shouldn't be fixed. A default configuration shouldn't fail, regardless of how many users end up using it. This could be fixed by changing the default xinitrc script, or by having x11-apps/xinit pull in the packages it needs to make the default script work.
*** This bug has been marked as a duplicate of bug 110880 ***
This isn't a duplicate of bug 110880; it's essentially the inverse of that bug, in that one possible fix for 110880 would cause this bug.
(In reply to comment #2) > This isn't a duplicate of bug 110880; it's essentially the inverse of that > bug, in that one possible fix for 110880 would cause this bug. Yes, it is a duplicate of that bug, precisely because its resolution was the inverse of this one's aim. This bug report does not have any merit without the resolution of bug #110880 being reversed, thus making it a perfect duplicate. *** This bug has been marked as a duplicate of bug 110880 ***
(In reply to comment #3) > Yes, it is a duplicate of that bug, precisely because > its resolution was the inverse of this one's aim. This is not an accurate statement. The comments of bug 110880 -- see especially #14, the last comment written by a human -- make it clear that the gentoo package dependencies would not be changed to resolve that bug; that, were the bug to be resolved, the configuration script would have to be changed upstream. (This has not happened: the problematic lines in the current /etc/X11/xinit/xinitrc are identical to those quoted in bug 110880 comment 10, written nearly seven years ago.) I do not know when or why x11-apps/xinit's dependencies were changed, but they were not in response to 110880. Thus fixing this bug does not entail undoing 110880. > This bug report does not have any merit without > the resolution of bug #110880 being reversed, There is no merit in a package having a default configuration script which fails. An easy way to resolve this failure would be to restore the dependencies that 110880 advocated removing (but did not result in the removal of). If the advantage of the reduction in installed packages is deemed too great to roll back, then x11-apps/xinit's default configuration script should be changed so that it does not require those packages. If it's such an uncommon use case, it should probably not be the default (though bug 110880 comment 11 makes a strong case that, even if not commonly utilized, the current script is a sensible default). There are likely other possible fixes I haven't thought of. But there is zero merit in having a package's default configuration fail. This is a clear consensus in the comments of bug 110880.
Please stop doing this. Since the other bug wasn't actually fixed in one major respect, I will reopen it for you, how is that? *** This bug has been marked as a duplicate of bug 110880 ***
(In reply to comment #5) > Please stop doing this. I am reporting a legitimate bug in the current x11-apps/xinit. You have repeatedly marked this bug report as a duplicate of an inactive bug report from seven years ago, assuring that the legitimate bug I am reporting will never be addressed. I agree, one of us should please stop doing this. > Since the other bug wasn't actually fixed in one > major respect, I will reopen it for you, how is that? Thank you. I would like the bug to be addressed; it matters not to me which bug report is used to accomplish this.
We are not planning to change the xinit default from upstream. Neither twm nor xterm are strictly required for xinit to work.
