Bug#357713: Fixed... is it really?

[Vasilis Vasaitis <v.vasaitis@sms.ed.ac.uk>]

reopen 357713
severity 361516 important
merge 357713 361516 362122
tags 362122 - experimental
thanks

  Hello,

  I just wanted to point out here, that just because the problem *went
away* for the submitter does not necessarily mean that the bug was
*fixed*.

  Here's my take on this: the reported behaviour was probably caused
by bug #362122 (which I reported yesterday). That is, when the
submitter first upgraded to the new modular packages, xbase-clients
unpacked things meant for /usr/lib/X11 over the existing symlink to
/usr/X11R6/lib/X11. Amongst those was the symlink xinit, pointing to
/etc/X11/xinit. Therefore startx could not find
/usr/lib/X11/xinit/xinitrc anymore, so it passed an empty client
argument to xinit, which then fell back to executing "xterm -geometry
+1+1 -n login -display :0", which was what the submitter was seeing on
his screen.

  Fast forward to yesterday. The submitter upgraded to the packages in
unstable, which included a version bump of xbase-clients, so it got
upgraded. This time, /usr/lib/X11 already existed as a directory
(because of xutils, for example), so everything got unpacked in the
correct position, and things started working again. So for example, if
I am correct, there should be two xinit links in both /usr/lib/X11 and
/usr/X11R6/lib/X11.

  So, did the problem go away? Sure did. Did it got fixed? Probably
not. I'm actually reopening the bug and merging it with the other bug
reports that I've identified as relevant; please yell at me if that's
inappropriate.

Thanks,
Vasilis

-- 
Vasilis Vasaitis
"A man is well or woe as he thinks himself so."