[Ubuntu-x-swat] [Bug 788596] Re: xclock's reverseVideo draws black on black
Hi Chris, that's not what I'm seeing. Please describe what it is you are seeing working normally, and confirm you've no .Xresources, etc., implicitly in play. I see xclock(1) now describes hourColor, etc., and says that reverseVideo, AKA -rv, affects their defaults. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-apps in Ubuntu. https://bugs.launchpad.net/bugs/788596 Title: xclock's reverseVideo draws black on black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/788596/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
** Bug watch added: Debian Bug tracker #750469 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750469 ** Also affects: xorg (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750469 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/622179 Title: The suspicious errors don't give sufficient information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/622179/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
Hi Christopher, another six weeks have passed and this bug still hasn't had its correct status and importance settings restored. As you changed them, wrongly, it would seem a matter of taking pride in your work that you restore them to Bryce's settings. Or at least reply to my requests with your argument as to why not. No, this is not an April Fool's. :-) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/622179 Title: The suspicious errors don't give sufficient information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/622179/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
Hi Christopher, it's been about six weeks and Julien Cristau hasn't responded. Please restore Bryce's settings of status and importance as this isn't a freedesktop issue AFAICS. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/622179 Title: The suspicious errors don't give sufficient information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/622179/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
Hi Christopher, as I stated They're from debian/local/xserver-wrapper.c so is freedesktop.org relevant? If not, please restore importance and status. Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/622179 Title: The suspicious errors don't give sufficient information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/622179/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 788596] [NEW] xclock's reverseVideo draws black on black
Public bug reported: Binary package hint: x11-apps Package x11-apps 7.5+5. When xclock is given -rv it has a black background instead of a white one but much of the clock isn't drawn; presumably those missing bits are still being drawn in black. Easy to confirm; compare `xclock' and `xclock -rv'. Adding -norender changes the behaviour; white hands are now visible with -rv but the clock face is still missing. With -digital no text is displayed. It has been like this for several releases but decades ago it used to work just fine. I suspect the render additions are what's caused the bugs. ** Affects: x11-apps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-apps in Ubuntu. https://bugs.launchpad.net/bugs/788596 Title: xclock's reverseVideo draws black on black ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 788596] Re: xclock's reverseVideo draws black on black
Setting to Confirmed. Bad form to confirm one's own bugs I know but John's seeing the same. ** Changed in: x11-apps (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-apps in Ubuntu. https://bugs.launchpad.net/bugs/788596 Title: xclock's reverseVideo draws black on black ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 394430] Re: xclock -twentyfour option ignored
Looks like Josh should have set status back from Incomplete. I'm seeing the same issue here so setting to Confirmed. ** Changed in: x11-apps (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-apps in Ubuntu. https://bugs.launchpad.net/bugs/394430 Title: xclock -twentyfour option ignored ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623294] Re: /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
Unlike the root user, I don't think there's anything special about the group ID of group `root'. IOW, the kernel places no special significance on GID 0. So the chown can't change from root:root to root:0 because group root isn't necessarily GID 0. That leaves ensuring a group called root exists. I think the issue of why some installations have a group called root and others don't is worthy of a separate, non- xorg, bug. -- /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid https://bugs.launchpad.net/bugs/623294 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623294] Re: /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
Paul, I've looked at 8.04 and 10.04 systems and /etc/group already had root:x:0: as the first line. So your system seems odd in that it didn't have this line. Could it have been removed accidentally at some point? -- /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid https://bugs.launchpad.net/bugs/623294 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623294] Re: /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
Given the number of Google hits for the family of errors like X: /tmp/.X11-unix has suspicious mode I think the Low priority set by Bryce is too low. Something is causing them and users doing recursive `sudo chowns' on /tmp without regard for the consequences could well be it. It's agreed `chmod 1777' is wrong so let's get a fixed version out there to remove the known causes and see if any others are left. -- /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid https://bugs.launchpad.net/bugs/623294 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623294] Re: /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
Who can stop the brain-damaged bot!? Tune in next week... ** Tags removed: needs-lspci-vvnn needs-xorglog ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid https://bugs.launchpad.net/bugs/623294 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623294] Re: /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
alt.bot.die.die.die. ** Changed in: xorg (Ubuntu) Status: Incomplete = New ** Tags removed: needs-lspci-vvnn needs-xorglog -- /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid https://bugs.launchpad.net/bugs/623294 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
Bryce said add the tag 'omit' and that will make it stop making automated changes to your bug so I did. But the evil, rampaging, bot continues to wage war. ** Tags removed: needs-lspci-vvnn needs-xorglog ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- The suspicious errors don't give sufficient information https://bugs.launchpad.net/bugs/622179 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
Strby, I sympathise, our LUG has a user that sees this error only every few boots rather than consistently, but this is not the correct bug to try and get your problem fixed. This is only about improving the error message when it occurs, not investigating causes of the error occurring. However, you're correct, the problem lies with the 1777. I'll raise another bug for that and report that number here for you and others that follow. -- The suspicious errors don't give sufficient information https://bugs.launchpad.net/bugs/622179 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623294] [NEW] /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
Public bug reported:
Binary package hint: xorg
/etc/init.d/x11-common in package x11-common, version 1:7.5+5ubuntu1
from 10.04 includes
$ awk 'BEGIN {RS = ; ORS = \n\n} /chmod/' /etc/init.d/x11-common
set_up_socket_dir () {
if [ $VERBOSE != no ]; then
log_begin_msg Setting up X server socket directory $SOCKET_DIR...
fi
if [ -e $SOCKET_DIR ] [ ! -d $SOCKET_DIR ]; then
mv $SOCKET_DIR $SOCKET_DIR.$$
fi
mkdir -p $SOCKET_DIR
chown root:root $SOCKET_DIR
chmod 1777 $SOCKET_DIR
do_restorecon $SOCKET_DIR
[ $VERBOSE != no ] log_end_msg 0 || return 0
}
set_up_ice_dir () {
if [ $VERBOSE != no ]; then
log_begin_msg Setting up ICE socket directory $ICE_DIR...
fi
if [ -e $ICE_DIR ] [ ! -d $ICE_DIR ]; then
mv $ICE_DIR $ICE_DIR.$$
fi
mkdir -p $ICE_DIR
chown root:root $ICE_DIR
chmod 1777 $ICE_DIR
do_restorecon $ICE_DIR
[ $VERBOSE != no ] log_end_msg 0 || return 0
}
$
Both functions allow for the directory, /tmp/.X11-unix or
/tmp/.ICE-unix, to already exist. They then attempt to ensure it has
the correct owner, group, and permissions. But the
chmod 1777 ...
fails to do this. chmod(1) says
chmod preserves a directory's set-user-ID and set-group-ID bits
unless you explicitly specify otherwise. You can set or clear the
bits with symbolic modes like u+s and g-s, and you can set (but not
clear) the bits with a numeric mode.
This is allowed by chmod(1posix).
For an octal integer mode operand, the file mode bits shall be set
absolutely. [Sounds good so far.]
For each bit set in the octal number, the corresponding file
permission bit [meaning rwx] shown in the following table shall be
set; all other file permission bits shall be cleared. For regular
files, for each bit set in the octal number corresponding to the
set-user-ID-on-execution or the set-group-ID-on-execution, bits
shown in the following table shall be set; if these bits are not set
in the octal number, they are cleared. [Good.] For other file
types [e.g. directories], it is implementation-defined whether or
not requests to set or clear the set-user-ID-on-execution or
set-group-ID-on-execution bits are honored.
IOW, the numeric mode 1777 will *never* clear the setuid and setgid
bits. A symbolic mode must be used to do this.
$ mkdir foo
$ l -d foo
drwxr-xr-x 2 ralph ralph 4096 2010-08-24 11:07 foo
$ chmod 1777 foo
$ l -d foo
drwxrwxrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
Correct. x11-common's chmod works in this case.
$ chmod u+s foo
$ l -d foo
drwsrwxrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
$ chmod 1777 foo
$ l -d foo
drwsrwxrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
Wrong. It fails to clear setuid.
$ chmod u-s,g+s foo
$ l -d foo
drwxrwsrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
$ chmod 1777 foo
$ l -d foo
drwxrwsrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
Wrong. Nor does it clear setgid.
$ chmod a-s=rwxt foo
$ l -d foo
drwxrwxrwt 2 ralph ralph 4096 2010-08-24 11:07 foo
$
The symbolic `a-s=rwxt' should be used for both of x11-common's chmods
in order to have the desired effect.
Because of the incorrect 1777, users are seeing errors from xorg's
xserver-wrapper.c,
X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a
directory, aborting.
see bug #622179. Perhaps this is being caused by the parent directory,
/tmp, being setgid and this is inherited by the mkdir(1), see mkdir(2),
and not cleared by the chmod.
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
/etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
https://bugs.launchpad.net/bugs/623294
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
Strby, bug #623294 covers your issue of setgid not be cleared by 1777. -- The suspicious errors don't give sufficient information https://bugs.launchpad.net/bugs/622179 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
Bryce. This is rapidly losing its charm. What do I have to do to stop your bot from making this change over and over. Can it not see it has already done it and been rebutted? Is there some do-not-dare-make-that- change,-bot tag I need add? ** Tags removed: needs-lspci-vvnn needs-xorglog ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- The suspicious errors don't give sufficient information https://bugs.launchpad.net/bugs/622179 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623294] Re: /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
Bryce's bot is incorrect in moving it from New to Incomplete and adding those tags. The data is not required. ** Tags removed: needs-lspci-vvnn needs-xorglog ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid https://bugs.launchpad.net/bugs/623294 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 623294] Re: /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid
** Tags added: omit -- /etc/init.d/x11-common's chmod 1777 fails to clear setuid and setgid https://bugs.launchpad.net/bugs/623294 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
** Tags added: omit -- The suspicious errors don't give sufficient information https://bugs.launchpad.net/bugs/622179 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
Bryce, can you stop your automatic thing adding tags and making this bug Incomplete? Or explain why they're needed. Thanks. ** Tags removed: needs-lspci-vvnn needs-xorglog ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- The suspicious errors don't give sufficient information https://bugs.launchpad.net/bugs/622179 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] [NEW] The suspicious errors don't give sufficient information
Public bug reported:
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.)
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
The suspicious errors don't give sufficient information
https://bugs.launchpad.net/bugs/622179
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 622179] Re: The suspicious errors don't give sufficient information
No log files or PCI listing required as I'm pointing out a clear, easily confirmable, problem with the source code. ** Tags removed: needs-lspci-vvnn needs-xorglog ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- The suspicious errors don't give sufficient information https://bugs.launchpad.net/bugs/622179 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
