[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#292441: marked as done (Non-root startx cannot move log file)



Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <45E33155.30402@ens-lyon.org>
and subject line ping timeout, closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: xserver-common
Version: 4.3.0.dfsg.1-10
Severity: Important

Attempting to use startx from non-root account suffers fatal server error
'Cannot move old logfile "/var/log/XFree86.0.log.old"', even after
running dpkg-reconfigure xserver-common, and selecting 'Console Users Only'.

After ripping down my filesystem to reorganize my partitions, and installing from floppies and .deb files brought home from the library on ZIP disks (lack of Internet pipe at the time) a 100MB worth at a time, last September, I had this problem and worked around it by modifying a start-up script (I'm struggling to remember which one), and, ultimately, setting /usr/bin/X11/XFree86 (I think) setuid.

One ramification of this work-around was that ~/.xsession was being ignored, unlike when using previous version, but I succeeded in using .xinitrc for the same functionality.

This worked until upgrading this evening from -8 to -10.  Now I'm back to the same place, thinking one ought not have to setuid by hand when debconf ought to take care of it (and not remembering quickly what that script I modified is - old age, I guess) .


--- End Message ---
--- Begin Message ---
Closing this bug since I didn't get any reply from the submitter (or
repliers) after my ping a month ago. If anybody ever reproduces this
problem, feel free to reopen.

Brice


--- End Message ---

Reply to: