On Sat, 2007-02-10 at 23:15 +0100, Julien Cristau wrote:
>
> * 110_fedora_no_move_damage.patch
Some variation of this will probably go in upstream at some point, see
https://bugs.freedesktop.org/show_bug.cgi?id=5275 . However, note that
e.g. compiz still relies on window moves generating damage (
On Sat, 2007-02-10 at 12:04 -0500, David Nusinow wrote:
>
> Why your compiz package still conflicts with libmetacity > 2.15.21? Is
> that a problem of 0.2.x compiz versions?
> I've removed the tag and recompiled compiz, and I've noticed no
> segfaults.
libmetacity changed ABI around that tim
Package: xkb-data
Version: 0.9-4
Severity: normal
Previously, I was using XOrg backports (6.9.0.dfsg.1-6~bpo.4) on a sarge
system, and I had written my own variant of a US keyboard layout
appropriate for typing lots of german text. In this version, it was
possible to add new files in /etc/X11/xkb
On Mon, Feb 12, 2007 at 09:10:01 +, Michel Dänzer wrote:
> libmetacity changed ABI around that time without bumping the soname. It
> breaks if you build against an older version and run against a newer
> version or vice versa. So when building against a newer version, the
> conflict needs to b
Hi Ionel,
About 5 years ago, you reported a bug to the Debian BTS regarding ro_RO
having to migrate from ISO 8859-2 to 8859-16. Does this still matter
today? Maybe UTF-8 is better solution? If so, I will close your bug in
the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
On Mon, 2007-02-12 at 08:08 +0100, Brice Goglin wrote:
> Hi Guys,
>
> About 8 months ago, you reported (a replied to a bug) in the Debian BTS
> regarding ssh -X problems between sarge and sid machines. I just want to
> know whether it still occurs with latest packages nowadays, especially
> Sarge<
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> forwarded 407573 https://bugs.freedesktop.org/show_bug.cgi?id=9953
Bug#407573: libX11-data: Please provide locale alias hu_HU.utf8
Noted your statement that Bug has been forwarded to
Hi Clint,
About 2 years ago, you reported a bug to the Debian BTS requesting new
Compose combos to be added. "!?" and "?!" for interrobang look ok to me.
But there are also things like:
: "ÿ" ydiaeresis # LATIN SMALL LETTER Y
WITH DIAERESIS
+ : "ÿ" ydiaeresis # LATIN SMALL LETTER Y
Package: xbase-clients
Version: 1:7.2.ds1-1
Severity: serious
Tags: experimental
Heya,
xbase-clients failed to build:
Automatic build of xbase-clients_1:7.2.ds1-1 on xenophanes by sbuild/amd64
98-farm
Build started at 20070212-
On 12-02-2007, at 09h 27'54", Brice Goglin wrote about "Bug#119524: xlibs-data:
[nls] migrate ro_RO from ISO 8859-2 to ISO 8859-16 when glibc and the rest of X
support that encoding"
> Hi Ionel,
>
> About 5 years ago, you reported a bug to the Debian BTS regarding ro_RO
> having to migrate from
If you want to clone our git repo and do the split yourself, and put the
split repo up somewhere that we can look at it, you're welcome to do so.
If it's good, we'll pull your version and use it.
I tried to clone the repo, but is the url on the Wiki wrong?
git clone http://alioth.debian.org/
Processing commands for [EMAIL PROTECTED]:
> tags 295356 wontfix
Bug#295356: libx11-data: want modifiable XKeysymDB
There were no tags set.
Tags added: wontfix
> thank you
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
Hi Denis,
About a year ago, after some discussion regarding whether Compose files
under /usr should be conffiles and/or moved to /etc, you ended up
retitling this bug and saying that you would work on providing a
/etc/X11/Compose fie to preserve local changes. Is there anything new
about this?
Th
tags 295356 wontfix
thank you
I don't see why somebody could seriously need to modify this file, and I
don't think this request will ever be accepted, so I am tagging as wontfix.
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO
[I keep cc:ing you because I don't know if you're subscribed to
debian-x. Let me know if you are, so I'll stop doing that :)]
On Mon, Feb 12, 2007 at 11:27:36 +, Timo Aaltonen wrote:
> I tried to clone the repo, but is the url on the Wiki wrong?
>
> git clone http://alioth.debian.org/git/pkg
_1:7.2.ds1-1 on xenophanes by sbuild/amd64
98-farm
Build started at 20070212-
**
[...]
xclock
[...]
checking pkg-config is at least version 0.9.0... yes
checking for XCURSORGEN... configure: error: Package requirement
Your message dated Mon, 12 Feb 2007 11:10:25 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#119524: xlibs-data: [nls] migrate ro_RO from ISO 8859-2 to
ISO 8859-16 when glibc and the rest of X support that encoding
has caused the attached Bug report to be marked as done.
This means
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> forwarded 396871 https://bugs.freedesktop.org/show_bug.cgi?id=8762
Bug#396871: libx11-data: Please recover the fontset order in XLC_LOCALE for
zh_TW.UTF-8 locale
Noted your statement
Hi,
About 14 months ago, you reported a bug to the Debian BTS regarding a
crash of Xemacs on a nVidia board, possibly caused by a bug in libX11.
Did you reproduce this problem recently? If not, I will close this bug
in the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Hi,
About 5 years ago, you reported (or replied to) a bug in the Debian BTS
regarding on_demand_loading in XLC_LOCALE files breaking XFontsOfFontSet().
Did any of you guys reproduce this problem recently? If not, I will
close this bug in the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email
Hi Joe,
About 19 month ago, you reported a bug to the Debian BTS regarding the
maximum number of X clients being reached, possibly caused by a leak.
Did you reproduce this problem recently? If not, I will close this bug
in the next weeks.
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Processing commands for [EMAIL PROTECTED]:
> retitle 244900 Xlib: Maximum number of clients reached, possible
Bug#244900: (no subject)
Changed Bug title.
> resource de-allocation issues
Unknown command or malformed arguments to command.
> severity 244900 important
Bug#244900: Xlib: Maximum numbe
Hi,
About 3 years ago, you reported a bug to the Debian BTS regarding
XcmsLRGB_RGBi_ParseString() parsing float without being locale aware,
causing your xterm to not read your color declaration correctly. Looking
at the code, I guess you still have the problem, right? If so, we should
forward the
Hi,
About 4 years ago, you reported a bug to the Debian BTS regarding xlib
trying to open :0.0 instead of:10.0 when xscreensaver is used. Did you
reproduce this problem recently? If not, I will close this bug in the
next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Hi,
About 3 years ago, you reported a bug to the Debian BTS regarding
_XPollfdCacheDel() calling select() forever when called by fglrx. Did
you reproduce this problem recently? If not, I will close this bug in
the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Your message dated Mon, 12 Feb 2007 12:32:21 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed since 2:1.0.3-5
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
On Mon, 12 Feb 2007, Julien Cristau wrote:
[I keep cc:ing you because I don't know if you're subscribed to
debian-x. Let me know if you are, so I'll stop doing that :)]
I subscribed today, so you can stop now ;)
On Mon, Feb 12, 2007 at 11:27:36 +, Timo Aaltonen wrote:
I tried to clone
Your message dated Mon, 12 Feb 2007 13:26:40 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400443: libx11-6: multiple wrong calls to LockDisplay and
UnlockDisplay
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt wi
On Mon, Feb 12, 2007 at 08:08:15AM +0100, Brice Goglin wrote:
> Hi Guys,
>
> About 8 months ago, you reported (a replied to a bug) in the Debian BTS
> regarding ssh -X problems between sarge and sid machines. I just want to
> know whether it still occurs with latest packages nowadays, especially
>
I'm confirming this bug.
Yesterday (02/11/07) I apt-get update/upgraded my system (already
running etch).
Same issue as the Rich. Can start an X session via console or kdm as
root, but not as user.
chmod 777 /tmp
chmod +t /tmp
fixes the problem; however, it doesn't really seem like a good id
On Mon, 2007-02-12 at 11:41 +0100, Brice Goglin wrote:
> About 14 months ago, you reported a bug to the Debian BTS regarding a
> crash of Xemacs on a nVidia board, possibly caused by a bug in libX11.
> Did you reproduce this problem recently?
No, I haven't seen this in a while. I think it's OK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ionel Mugurel Ciobica wrote:
> On 12-02-2007, at 09h 27'54", Brice Goglin wrote about "Bug#119524:
> xlibs-data: [nls] migrate ro_RO from ISO 8859-2 to ISO 8859-16 when glibc and
> the rest of X support that encoding"
>> Hi Ionel,
>>
>> About 5 years
Package: xserver-xorg-core
Version: 2:1.1.1-15
Severity: normal
File: /usr/bin/X
My X server just died on me, and wrote the following in /var/log/Xorg.0.log.old:
"
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354]
1: [0xb7fd9420]
2: /usr/bin/X(Dispatch+0x81) [0x8086b91]
3: /usr/bin/X(main
Tag 'xtrans-1.0.3-1' created by Julien Cristau <[EMAIL PROTECTED]> at
2007-02-12 18:40 +0100
Tagging upload of xtrans 1.0.3-1 to experimental.
Changes since xtrans-1.0.3:
David Nusinow:
Vendor drop of proto and lib for 7.0
Update libs to 7.0 release with packaging
Set libs to b
debian/changelog |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
New commits:
commit cdb16ca9e7b71627d4e628a4b8ff66bfd1c7909b
Author: Julien Cristau <[EMAIL PROTECTED]>
Date: Mon Feb 12 19:15:12 2007 +0100
Prepare changelog for upload to experimental.
diff --git a/debian/cha
On Mon, Feb 12, 2007 at 18:57:08 +0100, Johan Walles wrote:
> Package: xserver-xorg-core
> Version: 2:1.1.1-15
> Severity: normal
> File: /usr/bin/X
>
>
> My X server just died on me, and wrote the following in
> /var/log/Xorg.0.log.old:
> "
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x84) [0x
xtrans_1.0.3-1_i386.changes uploaded successfully to localhost
along with the files:
xtrans_1.0.3-1.dsc
xtrans_1.0.3.orig.tar.gz
xtrans_1.0.3-1.diff.gz
xtrans-dev_1.0.3-1_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
> On Mon, 2006-12-11 at 11:25 +0100, Giuseppe Bilotta wrote:
> >
> > Backtrace:
> > 0: /usr/bin/X11/X(xf86SigHandler+0x84) [0x80c4354]
> > 1: [0xb7fbc420]
> > 2: /lib/tls/i686/cmov/libc.so.6(__strtoul_internal+0x3f) [0xb7dd482f]
> > 3: /usr/bin/X11/X [0x80e6624]
> > 4: /usr/bin/X11/X(xf86HandlePME
Accepted:
xtrans-dev_1.0.3-1_all.deb
to pool/main/x/xtrans/xtrans-dev_1.0.3-1_all.deb
xtrans_1.0.3-1.diff.gz
to pool/main/x/xtrans/xtrans_1.0.3-1.diff.gz
xtrans_1.0.3-1.dsc
to pool/main/x/xtrans/xtrans_1.0.3-1.dsc
xtrans_1.0.3.orig.tar.gz
to pool/main/x/xtrans/xtrans_1.0.3.orig.tar.gz
Ov
Since I've only seen this once, me trying 2:1.1.1-17 wouldn't answer
your question about whether this has been fixed recently :-(.
//Johan
2007/2/12, Julien Cristau <[EMAIL PROTECTED]>:
On Mon, Feb 12, 2007 at 18:57:08 +0100, Johan Walles wrote:
> Package: xserver-xorg-core
> Version: 2:1.1.1
merge 410386 410696
thank you
Shlomi Israel wrote:
> I get a back trace in the xorg logs:
>
> Backtrace:
> 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354]
> 1: [0xb7f83420]
> 2: /usr/bin/X(Dispatch+0x81) [0x8086b91]
> 3: /usr/bin/X(main+0x489) [0x806e699]
> 4: /lib/tls/libc.so.6(__libc_start_mai
Xavier Bestel wrote:
> On Mon, 2007-02-12 at 08:08 +0100, Brice Goglin wrote:
>
>> Hi Guys,
>>
>> About 8 months ago, you reported (a replied to a bug) in the Debian BTS
>> regarding ssh -X problems between sarge and sid machines. I just want to
>> know whether it still occurs with latest packag
Hi BernhardHi,
About 2 years ago, you reported a bug to the Debian BTS regarding
XOpenDisplay failing because the XDM auth key matched an existing
client. I tried to reproduce with your testcase, but I couldn't. The
relevant source code did not change a lot, but did changed a little bit.
Did you r
Your message dated Mon, 12 Feb 2007 20:24:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#298720: libx11-6: XCreateFontSet crashes with "*" as font
name
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Processing commands for [EMAIL PROTECTED]:
> reassign 410386 xserver-xorg-core
Bug#410386: Xorg segfaults randomly
Bug reassigned from package `xorg' to `xserver-xorg-core'.
> merge 410386 410696
Bug#410386: Xorg segfaults randomly
Bug#410696: /usr/bin/X: Uncommon X crash with backtrace
Merged 41
Your message dated Mon, 12 Feb 2007 21:23:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#319077: libx11-6: pure python in ipython shell with -pylab
option SEGV in libX11, XrmQGetResource
has caused the attached Bug report to be marked as done.
This means that you claim that the
Hi,
About a year ago, you reported a bug to the Debian BTS regarding UTF-8
being incorrectly displayed in ion window title.
Did you reproduce this problem recently? If not, I will close this bug
in the next weeks.
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
debian/changelog|7 ---
debian/control |2 +-
debian/rules|4 +++-
debian/serverabiver |2 +-
4 files changed, 9 insertions(+), 6 deletions(-)
New commits:
commit 885e8a1af534956793edb68d5138b53eddac767d
Author: Julien Cristau <[EMAIL PROTECTED]>
Date: Mon F
Package: xserver-xorg
Version: 1:7.1.0-11
Severity: normal
I've a desktop with Etch on it (LG's L204WT LCD monitor and BFG's NVIDIA
GeForce
7800GS card). Displayed fonts are all ugly. Some of the fonts that are
displayed
have light white shadow right beside it. This ugly effect is visible on b
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> forwarded 403618 https://bugs.freedesktop.org/show_bug.cgi?id=1182
Bug#403618: libx11-6: libx11 has bug in XFilterEvent
Noted your statement that Bug has been forwarded to
https://bu
so is this bug going to get fixed? thanks.
_
Your Space. Your Friends. Your Stories. Share your world with Windows Live
Spaces. http://discoverspaces.live.com/?loc=en-CA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
On Mon, 12 Feb 2007, Brice Goglin wrote:
Did you reproduce this problem recently? If not, I will close this bug
in the next weeks.
Yes, it happens with Skype, whose "trademark" symbol is displayed
as `"b'. However, some other programs (e.g. Opera, when displaying Japanese
titles) seem to wor
Package: xserver-xorg
Version: 1:7.1.0-11
Severity: normal
The old XFree86-4.conf looked like this (and worked correctly):
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules"
On Mon, Feb 12, 2007 at 10:37:33AM +0100, Brice Goglin wrote:
> Hi Denis,
>
> About a year ago, after some discussion regarding whether Compose files
> under /usr should be conffiles and/or moved to /etc, you ended up
> retitling this bug and saying that you would work on providing a
> /etc/X11/Co
i think i may have a similar issue on a box that has been tracking etch for a
while with a british keyboard and developed the "can't switch out of x with the
"CTRL-ALT-Fx" keys sometime while tracking etch (i don't recall exactly when).
i mention this because it means the issue of keyboard layou
Your message dated Mon, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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, 12 Feb 2007 23:40:01 +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
1 - 100 of 173 matches
Mail list logo
