Your message dated Thu, 05 Jul 2007 06:47:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#431655: fixed in xorg-server 2:1.3.0.0.dfsg-7
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
Your message dated Thu, 05 Jul 2007 06:47:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#420421: fixed in xorg-server 2:1.3.0.0.dfsg-7
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
Your message dated Thu, 05 Jul 2007 06:47:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424684: fixed in xorg-server 2:1.3.0.0.dfsg-7
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
Your message dated Thu, 05 Jul 2007 06:47:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#415025: fixed in xorg-server 2:1.3.0.0.dfsg-7
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
Accepted:
xdmx-tools_1.3.0.0.dfsg-7_i386.deb
to pool/main/x/xorg-server/xdmx-tools_1.3.0.0.dfsg-7_i386.deb
xdmx_1.3.0.0.dfsg-7_i386.deb
to pool/main/x/xorg-server/xdmx_1.3.0.0.dfsg-7_i386.deb
xnest_1.3.0.0.dfsg-7_i386.deb
to pool/main/x/xorg-server/xnest_1.3.0.0.dfsg-7_i386.deb
xorg-server_1
xorg-server_1.3.0.0.dfsg-7_i386.changes uploaded successfully to localhost
along with the files:
xorg-server_1.3.0.0.dfsg-7.dsc
xorg-server_1.3.0.0.dfsg-7.diff.gz
xprint-common_1.3.0.0.dfsg-7_all.deb
xserver-xorg-core_1.3.0.0.dfsg-7_i386.deb
xserver-xorg-dev_1.3.0.0.dfsg-7_i386.deb
xdmx
Tag 'xorg-server-2_1.3.0.0.dfsg-7' created by Julien Cristau <[EMAIL
PROTECTED]> at 2007-07-05 06:24 +
Tagging upload of xorg-server 2:1.3.0.0.dfsg-7 to unstable.
Changes since xorg-server-2_1.3.0.0.dfsg-6:
Brice Goglin (5):
Add 40_consolidate_portPriv_pDraw_assignments.diff to avoid a
debian/changelog |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
New commits:
commit 072a69dc01e5a4f103e757025c8d19d2f4dec35b
Author: Julien Cristau <[EMAIL PROTECTED]>
Date: Thu Jul 5 00:51:01 2007 +0200
Prepare changelog for upload.
diff --git a/debian/changelog b/debian/c
Processing commands for [EMAIL PROTECTED]:
> reassign 431743 nvidia-glx
Bug#431743: xbase-clients: [xsetroot] new background only seen after a window
goes over it
Bug reassigned from package `xbase-clients' to `nvidia-glx'.
> retitle 431743 [xsetroot] new background only seen after a window goes
reassign 431743 nvidia-glx
retitle 431743 [xsetroot] new background only seen after a window goes over it,
with nVidia on Xserver 1.3
thank you
Leandro Lisboa Penz wrote:
> Yeah, it is specific to the proprietary drivers. Even though my card does not
> work with the free drivers, it works with
On Thu, Jul 05, 2007 at 02:32:46AM +0200, Brice Goglin wrote:
> Leandro Penz wrote:
> > The two machines I have with Lenny have this problem. They have
> > different nvidia boards.
> >
> > I tried to downgrade xserver-xorg-core and it worked! The downgrade
> > was the following:
> > [DOWNGRADE] xse
Your message dated Thu, 05 Jul 2007 04:02:10 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#420403: fixed in mesa 6.5.2-6
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
There are disparities between your recently accepted upload and the
override file for the following file(s):
libgl1-mesa-dri_6.5.2-6_i386.deb: package says priority is optional, override
says extra.
Either the package or the override file is incorrect. If you think
the override is correct and t
Accepted:
libgl1-mesa-dev_6.5.2-6_all.deb
to pool/main/m/mesa/libgl1-mesa-dev_6.5.2-6_all.deb
libgl1-mesa-dri-dbg_6.5.2-6_i386.deb
to pool/main/m/mesa/libgl1-mesa-dri-dbg_6.5.2-6_i386.deb
libgl1-mesa-dri_6.5.2-6_i386.deb
to pool/main/m/mesa/libgl1-mesa-dri_6.5.2-6_i386.deb
libgl1-mesa-glx-db
mesa_6.5.2-6_i386.changes uploaded successfully to localhost
along with the files:
mesa_6.5.2-6.dsc
mesa_6.5.2-6.diff.gz
libgl1-mesa-dev_6.5.2-6_all.deb
mesa-common-dev_6.5.2-6_all.deb
mesa-swx11-source_6.5.2-6_all.deb
libgl1-mesa-swx11_6.5.2-6_i386.deb
libgl1-mesa-swx11-dbg_6.5.2-6_i
Tag 'mesa-6.5.2-6' created by Julien Cristau <[EMAIL PROTECTED]> at 2007-07-05
02:47 +
Tagging upload of mesa 6.5.2-6 to unstable.
Changes since mesa-6.5.2-5:
Julien Cristau (2):
Make libgl1-mesa-swx11 depend on libosmesa6
Prepare changelog for upload.
Samuel Thibault (1):
configs/debian-indirect-default |7 +++
configs/debian-indirect-hurd-i386 |9 +
debian/changelog |6 --
debian/control|4 ++--
debian/scripts/choose-configs |8 ++--
5 files changed, 28 insertions(+), 6 deletions(-)
Hi Brice,
On 2007-07-05 00:57:27 +0200, Brice Goglin wrote:
> Vincent Lefevre wrote:
> > I don't know. I mostly use this machine remotely. I'm installing
> > the latest versions so that when I try in 3 weeks, I can tell you.
> Any news about this?
The problem didn't occur, but I didn't use my ma
#
# 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 #431389
# * https://bugs.freedesktop.org/show_bug.cgi?id=10706
# * remote status changed: (
Leandro Penz wrote:
> The two machines I have with Lenny have this problem. They have
> different nvidia boards.
>
> I tried to downgrade xserver-xorg-core and it worked! The downgrade
> was the following:
> [DOWNGRADE] xserver-xorg 1:7.2-5 -> 1:7.1.0-16
> [DOWNGRADE] xserver-xorg-core 2:1.3.0.0.df
On 7/4/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
Leandro Penz wrote:
> After a xsetroot -solid white, the background stays the same. Only after
passing
> a window over it, it is redrawn with the correct color.
>
> Marked as serious because I think root-tail is not working because of a
common
>
#
# 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 #389576
# * https://bugs.freedesktop.org/show_bug.cgi?id=7288
# * remote status changed: (?) -> RESOLVED
#
# bts-link upstream status pull for source package libx11
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #431421
# * https://bugs.freedesktop.org/show_bug.cgi?id=11222
# * remote status changed: (?) -> RESOLVED
#
Processing commands for [EMAIL PROTECTED]:
> #
> # bts-link upstream status pull for source package libx11
> # 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]:
> reassign 428759 libx11-6
Bug#428759: gimp: Gimp crashes on certain painting tools
Bug reassigned from package `gimp' to `libx11-6'.
> forcemerge 431421 428759
Bug#431421: libx11-6: version 1.1.2 breaks gdk and especially gimp
Bug#428759: gimp: Gimp cra
Your message dated Thu, 05 Jul 2007 01:34:30 +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
Your message dated Thu, 05 Jul 2007 01:34:30 +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
Your message dated Thu, 05 Jul 2007 01:34:30 +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
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.6
> reassign 319689 xserver-xorg-video-ati
Bug#319689: xserver-xorg: locks up system using ATI 9200c
Bug reassigned from package `xserver-xorg-core' to `xserver-xorg-video-ati'.
> reassi
Your message dated Thu, 05 Jul 2007 01:34:30 +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
Your message dated Thu, 05 Jul 2007 01:34:30 +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
Your message dated Thu, 05 Jul 2007 01:34:30 +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
Your message dated Thu, 05 Jul 2007 01:28:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#353494: xserver-xorg: fails to start on Cyrix 6x86L CPU
(SIGILL)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.6
> reassign 396535 xserver-xorg-video-tdfx
Bug#396535: I Can not change the Hz. with my 3dfx card.
Bug reassigned from package `xserver-xorg-core' to `xserver-xorg-video-tdfx'.
>
End of
Your message dated Thu, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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, 05 Jul 2007 01:14:11 +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
Hello Martin:
The patch you mention is already applied upstream as of June 17th, so
included in my up-to-date local git repo. This means bug is still present in
my experience.
Thanks,
--
Raúl Sánchez Siles
->Proud Debian user<-
Linux registered user #416098
signature.asc
Vincent Lefevre wrote:
> On 2007-06-04 22:53:36 +0200, Brice Goglin wrote:
>
>> Does this problem with arrow keys sometimes producing repeated digits
>> still happen nowadays? With latest xserver-xorg-core 1.3 and drivers?
>>
>
> I don't know. I mostly use this machine remotely. I'm install
> IIRC, that you need bleeding-edge DRM modules for i915tex to work. These
> modules are not even in 2.6.22. Are you sure it worked?
yes, i am running the drm module from the git-repository from a month ago
approx.
> These 256MB of VideoRAM are probably related to the AGP aperture
> (possibly c
reassign 431746 xserver-xorg-core
found 431746 2:1.3.0.0.dfsg-6
thank you
BERTRAND Joël wrote:
> Since my last upgrade, I cannot use X anymore on all my sparc64. All use
> Creator3D framebuffer and I'm not sure that this trouble occurs with
> another framebuffer. I never see th
Ariel Garcia wrote:
> i now realized that now it is not loading i915tex_dri anymore by
> default, but
>
> (II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so
>
> instead so perhaps that is the difference. Before it was running the
> new textures version. I will try with
> Opti
Leandro Penz wrote:
> After a xsetroot -solid white, the background stays the same. Only after
> passing
> a window over it, it is redrawn with the correct color.
>
> Marked as serious because I think root-tail is not working because of a common
> problem (bug #429609).
>
> Maybe it has something
Tobias Koenig wrote:
> Well, the backtrace is the same, so I guess the faulty code causes also
> the crash mentioned in #428089.
>
Well, the backtrace in #423485 is about
SavageAdjustFrame/SavageSwitchMode, while the only backtrace I found for
#428089 is in the upstream bug and talks about
Sha
debian/changelog |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit a75ca5a12e7e265acb4fd894b91f9ee2d96332f0
Author: Brice Goglin <[EMAIL PROTECTED]>
Date: Wed Jul 4 23:21:51 2007 +0200
Add closer
diff --git a/debian/changelog b/debian/changelog
index 070fb03
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.6
> retitle 431694 Windec broken when maximized in compiz/nvidia
Bug#431694: Windec broken when maximized
Changed Bug title to `Windec broken when maximized in compiz/nvidia' from
`Winde
> i now reinstalled xserver-xorg-video-intel, but now version 2:2.0.0-5 as
> you suggested (i've just seen -6 is out...)
> Good news up to now, it seems to switch fine back and forth between X
> and console, both with ipw2200 loaded, having run glxgears, or being
> logged into kde. Suspend to ram
Your message dated Wed, 4 Jul 2007 22:34:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Mail delivery failed: returning message to sender
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
severity 431757 normal
reassign 431757 xserver-xorg-core
kthxbye
On Wed, Jul 4, 2007 at 11:17:04 -0700, dale wrote:
> I've reported this Direct rendering bug before. I've updated
> everything (I believe), yet it still occurrs. My DRI was
> very good and very fast until I updated to the new X11
Processing commands for [EMAIL PROTECTED]:
> severity 431757 normal
Bug#431757: k3dsurf: Raster type lines cover display. DRI problem?
Severity set to `normal' from `grave'
> reassign 431757 xserver-xorg-core
Bug#431757: k3dsurf: Raster type lines cover display. DRI problem?
Bug reassigned from
Hi,
i now reinstalled xserver-xorg-video-intel, but now version 2:2.0.0-5 as
you suggested (i've just seen -6 is out...)
Good news up to now, it seems to switch fine back and forth between X and
console, both with ipw2200 loaded, having run glxgears, or being logged
into kde. Suspend to ram als
Processing commands for [EMAIL PROTECTED]:
> reassign 431757 x11-common
Bug#431757: k3dsurf: Raster type lines cover display. DRI problem?
Bug reassigned from package `k3dsurf' to `x11-common'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking sys
Accepted:
x11proto-composite-dev_0.4-1_all.deb
to pool/main/x/x11proto-composite/x11proto-composite-dev_0.4-1_all.deb
x11proto-composite_0.4-1.diff.gz
to pool/main/x/x11proto-composite/x11proto-composite_0.4-1.diff.gz
x11proto-composite_0.4-1.dsc
to pool/main/x/x11proto-composite/x11proto-co
x11proto-composite_0.4-1_i386.changes uploaded successfully to localhost
along with the files:
x11proto-composite_0.4-1.dsc
x11proto-composite_0.4.orig.tar.gz
x11proto-composite_0.4-1.diff.gz
x11proto-composite-dev_0.4-1_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSC
Tag 'x11proto-composite-1_0.4-1' created by Julien Cristau <[EMAIL PROTECTED]>
at 2007-07-04 16:46 +
Tagging upload of x11proto-composite 1:0.4-1 to experimental.
Changes since compositeproto-0.3:
Aaron Plattner (1):
Have NameWindowPixmap return a Match error on unrealized windows.
Al
Package: xserver-xorg
Version: 1:7.2-5
Severity: important
Hello,
Since my last upgrade, I cannot use X anymore on all my sparc64. All use
Creator3D framebuffer and I'm not sure that this trouble occurs with
another framebuffer. I never see this bug on i386, but I
Package: xbase-clients
Version: 1:7.2.ds2-2
Severity: important
After a xsetroot -solid white, the background stays the same. Only after passing
a window over it, it is redrawn with the correct color.
Marked as serious because I think root-tail is not working because of a common
problem (bug #42
On Wed, Jul 4, 2007 at 18:05:54 +0200, Tobias Koenig wrote:
> > Hum, #407875 does not look related to this.
> The backtrace also starts in FontFileCompleteXLFD and there is a comment
> that this method could cause a memory corruption which will trigger
> crashes in other places in the code... So
On Tue, Jul 03, 2007 at 08:54:31PM +0200, Brice Goglin wrote:
> Tobias Koenig wrote:
Hi,
> Where do you see this is a duplicate? #428089 talks about console
> corruption when stopping X from within X, while #423485 talks about a
> crash while playing.
Well, the backtrace is the same, so I guess th
GL/glx/glxdri.c | 39
GL/glx/renderpix.c |1
GL/glx/renderpixswap.c |1
GL/glx/singlepix.c |1
GL/glx/singlesize.h |
On 04.07.2007 14:50 schrieb Brice Goglin:
> I don't see any similar bug report so far. Since the driver is involved
> *a lot* in Compiz for AIGLX, we need somebody to reproduce this bug with
> a free driver instead of the nVidia binary. Let me know if you can do
> that. If not, I will have to eithe
On Wed, 2007-07-04 at 14:37 +0200, Bastian Venthur wrote:
> On 04.07.2007 14:31 schrieb Michel Dänzer:
> > On Wed, 2007-07-04 at 14:23 +0200, Bastian Venthur wrote:
> >> On 04.07.2007 13:52 schrieb Brice Goglin:
> >>> I'm using compiz with a GeForce4 Ti 4800 SE and resizing windows is
> >>>
I don't see any similar bug report so far. Since the driver is involved
*a lot* in Compiz for AIGLX, we need somebody to reproduce this bug with
a free driver instead of the nVidia binary. Let me know if you can do
that. If not, I will have to either reassign to nvidia-glx or close this
bug since w
Bastian Venthur wrote:
> When resizing the window, Xorgs *CPU* utilization goes up to 100%. On my
> box you can even hear the effect. I doubt this is an nvidia driver issue
> but more likely to be a bug in the programming of the resize-window
> routine in comiz.
>
There was the same problem on
On 04.07.2007 14:31 schrieb Michel Dänzer:
> On Wed, 2007-07-04 at 14:23 +0200, Bastian Venthur wrote:
>> On 04.07.2007 13:52 schrieb Brice Goglin:
>>> I'm using compiz with a GeForce4 Ti 4800 SE and resizing windows is
>>> very
>>> slow here too. The other effects work very smooth thou
On Wed, 2007-07-04 at 14:23 +0200, Bastian Venthur wrote:
> On 04.07.2007 13:52 schrieb Brice Goglin:
> > I'm using compiz with a GeForce4 Ti 4800 SE and resizing windows is
> > very
> > slow here too. The other effects work very smooth though.
> >
> >
> > Probably related to the nvid
On 04.07.2007 13:52 schrieb Brice Goglin:
> I'm using compiz with a GeForce4 Ti 4800 SE and resizing windows is
> very
> slow here too. The other effects work very smooth though.
>
>
> Probably related to the nvidia binary driver, we can't do much about that.
When resizing the window
On 04.07.2007 13:54 schrieb Brice Goglin:
> Please send the whole output of
> /usr/share/bug/xserver-xorg/script
> so that we see your config and log.
>
> Brice
>
--
Bastian Venthur http://venthur.de
Debian Developer vent
Please send the whole output of
/usr/share/bug/xserver-xorg/script
so that we see your config and log.
Brice
I'm using compiz with a GeForce4 Ti 4800 SE and resizing windows is very
slow here too. The other effects work very smooth though.
Probably related to the nvidia binary driver, we can't do much about that.
Brice
ChangeLog | 34 ++
1 file changed, 34 insertions(+)
New commits:
commit 8b76a077e58b431d161135b3a0429ee045e17cef
Author: Julien Cristau <[EMAIL PROTECTED]>
Date: Wed Jul 4 12:53:29 2007 +0200
Update the upstream changelog.
diff --git a/ChangeLog b/ChangeL
On Wed, 2007-07-04 at 12:31 +0200, Bastian Venthur wrote:
>
> Still can reproduce this. Sometimes windows start with black content.
> Resizing them helps to get the normal content back.
That doesn't sound quite the same as the original report, which talks
about this always being the case when win
also sprach Raúl Sánchez Siles <[EMAIL PROTECTED]> [2007.07.04.0055 +0200]:
> I've read the bug report and it seems that it corresponds to the upstream
> bug https://bugs.freedesktop.org/show_bug.cgi?id=11432 which is still open.
>
> This upstream bug is reproducible in my system using July 2
Package: compiz-kde
Version: 0.5.0.dfsg-1
Severity: normal
--- Please enter the report below this line. ---
Here's a screenshot of the problem, the iceweasel window is maximized.
As you can see the windec has a black irritation. I'm using the plastic
windec, but the problem is reproducible with ma
Processing commands for [EMAIL PROTECTED]:
> package xserver-xorg-video-intel
Ignoring bugs not assigned to: xserver-xorg-video-intel
> found 430668 2:2.1.0-1
Bug#430668: xserver-xorg-video-intel: partial freeze (mouse works) with
compiz/beryl on i965
Bug marked as found in version 2:2.1.0-1 and
Package: compiz
Version: 0.5.0.dfsg-1
--- Please enter the report below this line. ---
Still can reproduce this. Sometimes windows start with black content.
Resizing them helps to get the normal content back.
Cheers,
Bastian
--- System information. ---
Architecture: i386
Kernel: Linux 2.
Package: compiz
Version: 0.5.0.dfsg-1
--- Please enter the report below this line. ---
I'm using compiz with a GeForce4 Ti 4800 SE and resizing windows is very
slow here too. The other effects work very smooth though.
Cheers,
Bastian
--- System information. ---
Architecture: i386
Kernel:
El Martes, 3 de Julio de 2007, Julien Cristau escribió:
> As far as know, the most important thing holding this up is that
> noone with the hardware and interest has stepped up to maintain a
> nouveau package. Your help would most certainly be appreciated.
I am working on this...but I am
reassign 431655 xserver-xorg-core
tags 431655 +pending
thank you
On 7/4/07, Michel Dänzer <[EMAIL PROTECTED]> wrote:
On Wed, 2007-07-04 at 02:32 -0400, Carl Fink wrote:
> When playing back video using totem (either totem-xine or
totem-gstreamer
> from debian-multimedia.org), xorg will unpredic
Processing commands for [EMAIL PROTECTED]:
> reassign 431655 xserver-xorg-core
Bug#431655: xorg restarts when playing video
Bug reassigned from package `xorg' to `xserver-xorg-core'.
> tags 431655 +pending
Bug#431655: xorg restarts when playing video
There were no tags set.
Tags added: pending
>
95 matches
Mail list logo
