The "suspicious" errors don't give sufficient information
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg (Debian) |
New
|
Unknown
|
|||
xorg (Ubuntu) |
Won't Fix
|
Wishlist
|
Unassigned |
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/
if ((statbuf.st_uid != 0) || (statbuf.st_gid != 0)) {
(void) fprintf(stderr, "X: %s has suspicious ownership (not root:root), "
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 "
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.)
tags: | added: needs-xorglog |
tags: | added: needs-lspci-vvnn |
Changed in xorg (Ubuntu): | |
status: | New → Incomplete |
tags: | added: needs-xorglog |
tags: | added: needs-lspci-vvnn |
Changed in xorg (Ubuntu): | |
status: | New → Incomplete |
tags: | added: omit |
tags: | added: needs-xorglog |
tags: | added: needs-lspci-vvnn |
Changed in xorg (Ubuntu): | |
status: | New → Incomplete |
Changed in xorg (Ubuntu): | |
status: | New → Triaged |
Changed in xorg (Ubuntu): | |
importance: | Undecided → Low |
Changed in xorg (Debian): | |
status: | Unknown → New |
Hi Ralph,
Please attach the output of `lspci -vvnn` too.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]