Processing commands for [EMAIL PROTECTED]:
> reassign 390901 xserver-xorg-video-ati 1:6.6.3-2
Bug#390901: Drawing artefacts after suspend to ram
Bug#390551: compiz: Flickery after resume
Bug reassigned from package `compiz' to `xserver-xorg-video-ati'.
> reassign 390551 xserver-xorg-video-ati 1:6
reassign 390901 xserver-xorg-video-ati 1:6.6.3-2
reassign 390551 xserver-xorg-video-ati 1:6.6.3-2
kthxbye
On Thu, 2007-06-07 at 02:43 +0200, Michael Biebl wrote:
>
> Brice Goglin wrote:
> > Hi,
> >
> > Do you still reproduce these rendering problems in compiz after
> > suspend/resume? Even with
On Wed, 2007-06-06 at 20:01 +0100, Jason Cormie wrote:
> Brice Goglin wrote:
> > Jason Cormie wrote:
> >> Package: libdrm2
> >> Version: 2.3.0-4
> >> Followup-For: Bug #324560
> >>
> >>
> >> Could this be the reason that with an amd64 kernel I get this:
> >>
> >> [drm:radeon_do_init_cp] *ERROR* Can
Brice Goglin a écrit :
Hi,
Did any of you guys reproduce this problem regarding missing window
borders in compiz recently? With latest compiz 0.5 and xserver-xorg-core
1.3 currently in unstable?
Thanks,
Brice
Hello,
since Etch became stable and compiz takes place in it, I no longer use
unst
Michel Dänzer wrote:
> So the X server is 32 bit? If so, there's probably indeed some kind of
> 32/64 bit breakage somewhere, though unlikely related to the warnings in
> the bug report you referenced. It looks like although the X driver
> thinks setting the new memory map parameter succeeded, the
On Thu, 2007-06-07 at 08:58 +0100, Jason Cormie wrote:
> Michel Dänzer wrote:
> > So the X server is 32 bit? If so, there's probably indeed some kind of
> > 32/64 bit breakage somewhere, though unlikely related to the warnings in
> > the bug report you referenced. It looks like although the X drive
Your message dated Thu, 07 Jun 2007 11:35:28 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in experimental
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
Michel Dänzer wrote:
> reassign 390901 xserver-xorg-video-ati 1:6.6.3-2
> reassign 390551 xserver-xorg-video-ati 1:6.6.3-2
> kthxbye
>
> On Thu, 2007-06-07 at 02:43 +0200, Michael Biebl wrote:
>> Brice Goglin wrote:
>>> Hi,
>>>
>>> Do you still reproduce these rendering problems in compiz after
>>
Package: xorg-server
Version: 2:1.3.0.0.dfsg-6
Severity: important
Hi,
I am trying to get a machine with an Intel 965G chipset to work with
Debian. The xorg and mesa packages in etch do not work well enough.
With xorg 7.2 and mesa 6.5.3 (from experimental) the situtation is
much better. Theref
Your message dated Thu, 07 Jun 2007 15:27:13 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390551: compiz: Flickery after resume
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 n
.gitignore |1
COPYING | 70 -
ChangeLog | 49 --
Makefile.am | 14 +
configure.ac| 17 ++
man/.gitignore |7
man/Makefile.am | 86 +++
man/XTest.xml | 414
src/Makefile.
.gitignore| 22
COPYING | 70 +
ChangeLog | 49 -
INSTALL | 236 ++
Makefile.am | 14
Makefile.in | 41 +
aclocal
Tag 'libxtst-1_1.0.2-1' created by Julien Cristau <[EMAIL PROTECTED]> at
2007-06-07 16:07 +
Tagging upload of libxtst 1:1.0.2-1 to unstable.
Changes since libxtst-1_1.0.1-5:
Adam Jackson (3):
more trailing whitespace
Do PKG_CHECK_MODULES on a unique token instead of on "DEP", so
libxtst_1.0.2-1_i386.changes uploaded successfully to localhost
along with the files:
libxtst_1.0.2-1.dsc
libxtst_1.0.2.orig.tar.gz
libxtst_1.0.2-1.diff.gz
libxtst6_1.0.2-1_i386.deb
libxtst6-dbg_1.0.2-1_i386.deb
libxtst-dev_1.0.2-1_i386.deb
Greetings,
Your Debian queue daemon
Le mercredi 06 juin 2007 à 23:01 +0200, Brice Goglin a écrit :
> Hi Benoit,
>
> Do you still reproduce your problems with compiz 0.5.0 currently in
> unstable? With xserver-xorg-core 1.3 and latest ATI drivers (6.6.192 is
> currenlty in experimental)?
Only compiz 0.2.2-1 is available on ppc righ
Accepted:
libxtst-dev_1.0.2-1_i386.deb
to pool/main/libx/libxtst/libxtst-dev_1.0.2-1_i386.deb
libxtst6-dbg_1.0.2-1_i386.deb
to pool/main/libx/libxtst/libxtst6-dbg_1.0.2-1_i386.deb
libxtst6_1.0.2-1_i386.deb
to pool/main/libx/libxtst/libxtst6_1.0.2-1_i386.deb
libxtst_1.0.2-1.diff.gz
to pool/
There are disparities between your recently accepted upload and the
override file for the following file(s):
libxtst-dev_1.0.2-1_i386.deb: package says section is x11, override says
libdevel.
libxtst6-dbg_1.0.2-1_i386.deb: package says section is x11, override says
libdevel.
libxtst6_1.0.2-1_i38
debian/changelog |6 ++
debian/control |3 +++
2 files changed, 9 insertions(+)
New commits:
commit 674143ae770819caa23b536d113eb92879cece60
Author: Julien Cristau <[EMAIL PROTECTED]>
Date: Thu Jun 7 18:39:06 2007 +0200
Sync package sections with the override.
diff --git a/d
Benoît Dejean wrote:
> Only compiz 0.2.2-1 is available on ppc right now.
> I have xserver-xorg-core 2:1.3.0.0.dfsg-5.
> What is the package name for the ati drivers ?
>
It's "xserver-xorg-video-ati".
Latest 1:6.6.192-1 did not build on ppc yet, but the previous one
(1:6.6.191-1) is available i
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.2
> unmerge 390901
Bug#390901: Drawing artefacts after suspend to ram
Bug#390551: compiz: Flickery after resume
Disconnected #390901 from all other report(s).
>
End of message, stopping
Your message dated Thu, 07 Jun 2007 19:21:46 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427921: xorg-server: FTBFS with mesa 6.5.3-1
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
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.2
> tags 390551 + patch
Bug#390551: compiz: Flickery after resume
There were no tags set.
Tags added: patch
>
End of message, stopping processing here.
Please contact me if you need ass
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.2
> notfixed 390551 1:6.6.191-1
Bug#390551: compiz: Flickery after resume
Bug marked as not fixed in version 1:6.6.191-1.
>
End of message, stopping processing here.
Please contact me i
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.2
> reopen 390551
Bug#390551: compiz: Flickery after resume
Bug reopened, originator not changed.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Your message dated Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:49:52 +0200
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 Thu, 07 Jun 2007 20:51:43 +0200
with message-id <[EMAIL PROTECTED]>
and subject line 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 responsibility to reopen t
On Mon, May 28, 2007 at 09:41:40AM +0200, Brice Goglin wrote:
> About 2 years ago, you reported (or replied to) a bug in the Debian BTS
> regarding a lock up of the server when running Xorg 6.9 on an Radeon
> 9200 board. Did any of you guys reproduce this exact same problem
> recently? With Xorg/Et
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package xorg-server
> # 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 repo
#
# bts-link upstream status pull for source package xorg-server
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #415025
# * https://bugs.freedesktop.org/show_bug.cgi?id=10313
# * remote status changed: NEW -> RESOLVE
#
# bts-link upstream status pull for source package xserver-xorg-video-intel
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #427721
# * https://bugs.freedesktop.org/show_bug.cgi?id=10664
# * remote status changed: (
Package: xdm
Version: 1:1.1.4-3
Severity: wishlist
Regarding 328317, 359987: actually please put the xdm logs in their
own subdirectory. Imagine if every package kept 52 logs in the root
/var/log directory, it would quickly become unusable.
That's what subdirectories are for. Also imagine if each
Tag 'twm-1_1.0.3-1' created by Julien Cristau <[EMAIL PROTECTED]> at 2007-06-07
22:47 +
Tagging upload of twm 1:1.0.3-1 to unstable.
Changes since twm-1.0.3:
Branden Robinson (4):
Set svn:keywords property to "Id" (keyword already present).
Note probable out-of-dateness of maplin
.cvsignore | 17
ChangeLog| 11
autogen.sh | 13
compile | 147 --
config.guess | 667
config.sub | 222 +++--
con
Rebased ref, commits from common ancestor:
commit 849257f0765fd101e71ae7eb53d4d5a33e9ae31f
Author: Julien Cristau <[EMAIL PROTECTED]>
Date: Fri Jun 8 01:06:33 2007 +0200
Make twm look for system.twmrc in /etc/X11/twm, where it has a chance to
find it
diff --git a/aclocal.m4 b/aclocal.m4
in
aclocal.m4 | 22 ++-
config.guess | 32 +
config.h.in|9
config.sub | 28 +++--
configure
twm_1.0.3-1_i386.changes uploaded successfully to localhost
along with the files:
twm_1.0.3-1.dsc
twm_1.0.3.orig.tar.gz
twm_1.0.3-1.diff.gz
twm_1.0.3-1_i386.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tr
twm_1.0.3-1.diff.gz
to pool/main/t/twm/twm_1.0.3-1.diff.gz
twm_1.0.3-1.dsc
to pool/main/t/twm/twm_1.0.3-1.dsc
(new) twm_1.0.3-1_i386.deb optional x11
WARNING: Already present in main distribution.
Tab window manager
twm is a window manager for the X Window System. It provides title bars,
sha
debian/changelog |8
debian/rules |2 +-
debian/twm.postinst.in | 10 --
debian/twm.postrm.in | 10 --
debian/twm.preinst.in | 30 --
debian/twm.prerm.in|2 --
6 files changed, 9 insertions(+), 53 deletio
Brice Goglin wrote:
> Wakko Warner wrote:
> > At one point, I installed XFree86 that was still laying in pool. It didn't
> > have a problem. I think older copies of Xorg worked (<7.x) but I'm not
> > quite sure.
> >
> > IIRC, if I just use the onboard nic, it did work.
> >
>
> Somebody just r
Accepted:
twm_1.0.3-1.diff.gz
to pool/main/t/twm/twm_1.0.3-1.diff.gz
twm_1.0.3-1.dsc
to pool/main/t/twm/twm_1.0.3-1.dsc
twm_1.0.3-1_i386.deb
to pool/main/t/twm/twm_1.0.3-1_i386.deb
twm_1.0.3.orig.tar.gz
to pool/main/t/twm/twm_1.0.3.orig.tar.gz
Override entries for your package:
twm_1.0.3
Your message dated Fri, 08 Jun 2007 02:23:29 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#384073: fixed in twm 1:1.0.3-1
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
Your message dated Fri, 08 Jun 2007 02:23:29 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396940: fixed in twm 1:1.0.3-1
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
51 matches
Mail list logo
