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
** 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
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
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.
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.
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
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.
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
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
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
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
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
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
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
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,
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
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.
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
**
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
** 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.
___
** 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:
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
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
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
24 matches
Mail list logo
