Hi Brice,
never had that Problem since than. It might have been silently
disappeared on the next upgrade. So you might close it right now.
Thanks,
Erwin
smime.p7s
Description: S/MIME cryptographic signature
On Sun, Feb 25, 2007 at 09:53:32PM +0100, Brice Goglin wrote:
>
> There's probably another problem apart from X freezing when the time is
> changed. Maybe the system clock is not stored correctly in the hardware
> clock before shutdown. I remember having problems like this on a core
> duo processo
On Mon, Feb 26, 2007 at 11:44:36AM +0100, Robert Millan [ackstorm] wrote:
> On Fri, Feb 23, 2007 at 10:25:56PM +0100, Robert Millan wrote:
> >
> > Oh, not really. Screw nVidia. Beryl is only for faithful followers of the
> > one true Intel card brand. :-)
> >
> > So which lines are we going to
On Fri, Feb 23, 2007 at 10:25:56PM +0100, Robert Millan wrote:
>
> Oh, not really. Screw nVidia. Beryl is only for faithful followers of the
> one true Intel card brand. :-)
>
> So which lines are we going to add, if any? I can test which lines can
> Intel do without, but not till monday.
My
On Mon, 2007-02-26 at 11:44 +0100, Robert Millan [ackstorm] wrote:
> My intel card can do without either XAANoOffscreenPixmaps or
> AddARGBGLXVisuals.
> No difference can be found on first sight (and I tested most basic stuff:
> cube,
> skydome, etc).
>
> nVidia doesn't need AddARGBGLXVisuals, b
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package xorg
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status report for
On Mon, Feb 26, 2007 at 12:39:45PM +0100, Xavier Bestel wrote:
> On Mon, 2007-02-26 at 11:44 +0100, Robert Millan [ackstorm] wrote:
> > My intel card can do without either XAANoOffscreenPixmaps or
> > AddARGBGLXVisuals.
> > No difference can be found on first sight (and I tested most basic stuff:
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package compiz
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remote status report fo
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package xserver-xorg-input-evdev
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
> # remot
Package: xkb-data
Version: 0.9-4
Uzbek keyboard layout is not standard compliant. The attached patch fixes it.
I was accepted by the upstream maintainer. Please see the following upstream
bug report:
http://bugs.freedesktop.org/show_bug.cgi?id=10091
The attached patch is from the following URL
Your message dated Mon, 26 Feb 2007 18:39:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#165146: xlibs-dev: $(SOSYMLINK) not expanding in
gnuLib.rules
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Mon, 26 Feb 2007 18:53:52 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, or no hardware anymore, 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
Your message dated Mon, 26 Feb 2007 18:53:52 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout, or no hardware anymore, 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
Your message dated Mon, 26 Feb 2007 18:51:31 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 18:51:31 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 18:55:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line address invalid or 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 no
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 18:51:31 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:19:26 +0100
with message-id <[EMAIL PROTECTED]>
and subject line ping timeout or invalid address, 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 no
Your message dated Mon, 26 Feb 2007 19:20:32 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 19:17:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Processing commands for [EMAIL PROTECTED]:
> reassign 183029 xserver-xorg-core
Bug#183029: xfree86: put X server, XIM, and font server Unix domain sockets in
/var/run/X11 instead of /tmp
Bug reassigned from package `xfree86' to `xserver-xorg-core'.
> reassign 227005 xserver-xorg-core
Bug#227005:
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> tags 197156 wontfix
Bug#197156: xfree86: dexconf and xfs should use x-ttcidfont-conf font paths by
default
There were no tags set.
Tags added: wontfix
>
End of message, stopping pro
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:13:25 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:24:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:24:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:24:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 20:24:49 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Processing commands for [EMAIL PROTECTED]:
> reassign 243288 x11-common
Bug#243288: xfree86-common: [rgb.txt] add color definition for DebianRed
Bug reassigned from package `xfree86-common' to `x11-common'.
> reassign 251449 xorg
Bug#251449: xfree86-common: please add instructions on configuring
Your message dated Mon, 26 Feb 2007 20:50:06 +0100
with message-id <[EMAIL PROTECTED]>
and subject line #198397: Startup performance problem due to /tmp/.ICE_unix
permissions
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Mon, 26 Feb 2007 20:53:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#376826: xlibmesa-glu: marking packages to keep blow up
outside program
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Mon, 26 Feb 2007 20:50:06 +0100
with message-id <[EMAIL PROTECTED]>
and subject line #198397: Startup performance problem due to /tmp/.ICE_unix
permissions
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
I
reopen 203942
tags 203942 wontfix
thank you
Francois Gouget wrote:
> Brice Goglin wrote:
>
>> Closing this bug since I didn't get any reply from the submitter after
>> my ping a month ago. If anybody ever reproduces this problem, feel
>> free to reopen.
>>
>
> What the heck is this the
Brice Goglin wrote:
> Closing this bug since I didn't get any reply from the submitter after
> my ping a month ago. If anybody ever reproduces this problem, feel
> free to reopen.
What the heck is this then?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203942;msg=24
--
Francois Gouget <[EM
Processing commands for [EMAIL PROTECTED]:
> reopen 203942
Bug#203942: xfree86-common: [Xsession] want more flexible ssh-agent invocation
Bug reopened, originator not changed.
> tags 203942 wontfix
Bug#203942: xfree86-common: [Xsession] want more flexible ssh-agent invocation
There were no tags s
reopen 230422
thanks
[Brice Goglin]
> About 3 years ago, you reported a bug to the Debian BTS regarding
> the missing /etc/X11/Xreset{,.d}. Does this problem still matter
> today? If not, I will close this bug in the next weeks.
Yes, it does. We would for example like to kill processes, remove
Processing commands for [EMAIL PROTECTED]:
> reopen 230422
Bug#230422: xfree86-common: Should include /etc/X11/Xreset{.d}
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, D
reassign 230422 x11-common
thank you
> Yes, it does. We would for example like to kill processes, remove
> temp files or similar, and it would be a lot easier if some Xreset.d/
> like mechanism is available.
>
> For example, we would like to supply a script in the debian-edu-config
> package to c
Processing commands for [EMAIL PROTECTED]:
> reassign 230422 x11-common
Bug#230422: xfree86-common: Should include /etc/X11/Xreset{.d}
Bug reassigned from package `xfree86-common' to `x11-common'.
> thank you
Stopping processing here.
Please contact me if you need assistance.
Debian bug trackin
Your message dated Mon, 26 Feb 2007 22:36:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362778: missing /usr/lib/libXft.la
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 message dated Mon, 26 Feb 2007 22:36:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362778: missing /usr/lib/libXft.la
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 message dated Mon, 26 Feb 2007 23:09:58 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
Your message dated Mon, 26 Feb 2007 23:09:58 +0100
with message-id <[EMAIL PROTECTED]>
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 responsibili
reassign #252585 x11-common
reopen #252585
found #252585 7.1.0-12
thanks
On Mon, Feb 26, 2007 at 08:24:49PM +0100, Brice Goglin wrote:
> Closing this bug since I didn't get any reply from the submitter after
> my ping a month ago. If anybody ever reproduces this problem, feel free
> to reopen.
I
Processing commands for [EMAIL PROTECTED]:
> reassign #252585 x11-common
Bug#252585: xfree86-common: Xsession.options parsing fragile
Bug reassigned from package `xfree86-common' to `x11-common'.
> reopen #252585
Bug#252585: xfree86-common: Xsession.options parsing fragile
Bug reopened, originat
On Sun, Feb 25, 2007 at 02:46:58PM +0100, Mattia Dongili wrote:
> ...
> > mkdir: cannot create directory `xserver-xorg-input-synaptics.git':
> > Permission denied
> >
> > it seems a chmod g+w is missing on the driver/ dir :)
>
> Ping?
Crap! I'm so sorry, this slipped my mind. I just created the
Package: compiz
Version: 0.2.2-1
Severity: normal
Compiz is mostly unusable because :
1) its slow. It takes several seconds to switch from one desktop to another.
2) desktop brightness/colors are strange, they look lighter.
3) some window parts are not displayed, which means that there are white
r
Package: xterm
Version: 224-1
Severity: normal
Hi,
the manual page of xterm says: Note that xterm has one bold font which
you may set explicitly. It attempts to match a bold font for the other
font selections (font1 through font6). If the normal and bold fonts are
distinct, this resource [boldMod
Benoît Dejean wrote:
> Package: compiz
> Version: 0.2.2-1
> Severity: normal
>
> Compiz is mostly unusable because :
> 1) its slow. It takes several seconds to switch from one desktop to another.
> 2) desktop brightness/colors are strange, they look lighter.
> 3) some window parts are not displayed
Package: xkb-data
Version: 0.9-4
Followup-For: Bug #409982
The patch I've sent before was accepted by the maintainer of xkeyboard-config at
freedesktop.org into the upstream. So, please apply it in Debian.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testi
On Sun, Feb 25, 2007 at 02:46:58PM +0100, Mattia Dongili wrote:
> ...
> > mkdir: cannot create directory `xserver-xorg-input-synaptics.git':
> > Permission denied
> >
> > it seems a chmod g+w is missing on the driver/ dir :)
>
> Ping?
Julien just noticed that the directory didn't give the group
On Fri, Feb 23, 2007 at 12:18:06PM +0100, Robert Millan [ackstorm] wrote:
> Package: xserver-xorg
> Severity: wishlist
> Tags: patch
>
> I know it's too late for Beryl to make it into etch, but can we at least ship
> an xorg.conf that is frendly to Beryl ? With this patch, only installing
> the b
68 matches
Mail list logo
