Ralph Corderoy, as the xorg stack syncs with upstream, there is no
compelling reason to deviate from them on this. If this is repeatable on
xorg trunk, please feel free to file a bug upstream via
https://bugs.freedesktop.org/ .
** Changed in: xorg (Ubuntu)
Importance: Low => Wishlist
** Changed in: xorg (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/622179
Title:
The "suspicious" errors don't give sufficient information
Status in “xorg” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: xorg
Package xorg, version 1:7.5+5ubuntu1 on 10.04 is leaving error messages
in log files, e.g.
X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a
directory, aborting.
They're from debian/local/xserver-wrapper.c.
if ((statbuf.st_uid != 0) || (statbuf.st_gid != 0)) {
(void) fprintf(stderr, "X: %s has suspicious ownership (not root:root),
"
"aborting.\n", X_SOCKET_DIR);
exit(1);
}
if (statbuf.st_mode != (S_IFDIR | X_SOCKET_DIR_MODE)) {
(void) fprintf(stderr, "X: %s has suspicious mode (not %o) or is not a "
"directory, aborting.\n", X_SOCKET_DIR,
X_SOCKET_DIR_MODE);
exit(1);
}
In both cases it would help a lot, given the number of times these
errors appear on Google, if the message included what the unexpected
value(s) were, e.g.
X: /tmp/.X11-unix has suspicious mode, 01755 is not 01777, aborting.
X: /tmp/.X11-unix has suspicious ownership, 1000:0 is not 0:0, aborting.
(If the `%o' were `%#o' too then the error would make clear the numbers are
octal.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/622179/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
