On 6/18/07, Drew Parsons <[EMAIL PROTECTED]> wrote:
Thanks for that, I'm looking at dejavu now using xfontsel as well as xfd
and gfontview.
Moreover I can't see any difference between iso8859-1 and iso10646-1.
In both cases the ascents and descents vary between letters.
I've attached two scree
severity 429574 important
thank you
> On an etch box, after a recent upgrade of newly-migrated
> xserver-xorg-core, launching X causes the machine to freeze, with even
> sysrq not responding. Switching the video driver from ati to vesa
> allows to run X again, but downgrading the xserver as show
severity 429569 important
reassign 429569 xserver-xorg-core
thank you
Le Gluon du Net wrote:
> Severity: critical
> Justification: breaks the whole system
Actually, this kind of problem is important or normal.
> desktop, xorg consumes 50% or more of the cpu!!! I could move the
> mouse and the
Brice Goglin a écrit :
severity 429569 important
reassign 429569 xserver-xorg-core
thank you
Le Gluon du Net wrote:
Severity: critical
Justification: breaks the whole system
Actually, this kind of problem is important or normal.
In fact i don't know, when it happens I've genera
Processing commands for [EMAIL PROTECTED]:
> severity 429574 important
Bug#429574: hard lockup after xserver-xorg upgrade
Severity set to `important' from `critical'
> thank you
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adminis
Processing commands for [EMAIL PROTECTED]:
> severity 429569 important
Bug#429569: xorg: Xorg consumes a lot of cpu at screensaver exit
Severity set to `important' from `critical'
> reassign 429569 xserver-xorg-core
Bug#429569: xorg: Xorg consumes a lot of cpu at screensaver exit
Bug reassigned f
FYI: The status of the libxtst source package
in Debian's testing distribution has changed.
Previous version: 1:1.0.1-5
Current version: 1:1.0.2-1
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more information.
Package: x11proto-scrnsaver-dev
Version: 1.1.0.0-1
Severity: wishlist
Attempting to clean up my system with
for i in `deborphan --guess-dev`
do apt-cache show $i; apt-get --purge remove $i
done
I encounter the scary looking package Descriptions for packages like
this one, x11proto-scrnsaver-dev,
ubject: xorg: Xorg consumes a lot of cpu at screensaver exit
Package: xorg
Version: 1:7.2-5
Severity: critical
Justification: breaks the whole system
*** Please type your report below this line ***
Hello,
After a long period with a screensaver, when I would like to return to my
desktop, xorg con
Your message dated Mon, 18 Jun 2007 19:15:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#363285: xserver-xorg: Error activating XKB configuration
after update
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Mon, 18 Jun 2007 19:07:27 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396234: XOrg graphic problems (Matrox Mystique MGA 1064SG)
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
Wim De Smet wrote:
> Haven't gotten around to debugging it yet. I'll try to get you a
> backtrace by the end of the week.
>
Thanks.
>> Which compiz* and libdecoration* packages are you running?
>> xserver-xorg-core 1.3?
>>
>
> I upgraded to the latest versions in the archive of compiz and
Your message dated Mon, 18 Jun 2007 19:09:37 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#355365: xserver-xorg: Wrong keyboard model for japanese
keyboard
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
On 6/17/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
Hi,
Did you reproduce this problem regarding the screen going blank while
reconfigure xorg from a console recently? With latest Xorg packages? Do
you get the screen back later, for instance by switching back/to VT
again? Or do you need to reboo
debian/changelog|7 +++
debian/xserver-xorg.postinst.in | 78
2 files changed, 6 insertions(+), 79 deletions(-)
New commits:
commit 4b21f9970b745df62a4e1fc56d3cf00b4ed1e414
Author: David Nusinow <[EMAIL PROTECTED]>
Date: Mon Jun 18
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421523: fixed in xterm 226-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 r
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#420974: fixed in xterm 226-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 r
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422521: fixed in xterm 226-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 r
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426863: fixed in xterm 226-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 r
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#426364: fixed in xterm 226-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 r
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#418324: fixed in xterm 226-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 r
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349142: fixed in xterm 226-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 r
On Mon, Jun 18, 2007 at 01:58:02PM +0100, Joachim Breitner wrote:
> Package: xserver-xorg-video-ati
> Version: 1:6.6.3-2
> Severity: normal
>
> Hi,
>
> I can not disable DRI. Attached is the xorg config and the log file.
> Also filed here:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=20
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#12261: fixed in xterm 226-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 re
Hi,
Am Montag, den 18.06.2007, 14:25 +0100 schrieb Julien Cristau:
> On Mon, Jun 18, 2007 at 13:58:02 +0100, Joachim Breitner wrote:
>
> > I can not disable DRI. Attached is the xorg config and the log file.
> > Also filed here:
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207614
> >
Your message dated Mon, 18 Jun 2007 13:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349142: fixed in xterm 226-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 r
On Mon, Jun 18, 2007 at 13:58:02 +0100, Joachim Breitner wrote:
> I can not disable DRI. Attached is the xorg config and the log file.
> Also filed here:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207614
>
Hi Joachim,
can you try adding 'Disable "dri"' in the Module section of xorg.c
Accepted:
xterm_226-1.diff.gz
to pool/main/x/xterm/xterm_226-1.diff.gz
xterm_226-1.dsc
to pool/main/x/xterm/xterm_226-1.dsc
xterm_226-1_i386.deb
to pool/main/x/xterm/xterm_226-1_i386.deb
xterm_226.orig.tar.gz
to pool/main/x/xterm/xterm_226.orig.tar.gz
Override entries for your package:
x
xterm_226-1_i386.changes uploaded successfully to localhost
along with the files:
xterm_226-1.dsc
xterm_226.orig.tar.gz
xterm_226-1.diff.gz
xterm_226-1_i386.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tr
Tag 'xterm-226-1' created by Julien Cristau <[EMAIL PROTECTED]> at 2007-06-18
13:37 +
Tagging upload of xterm 226-1 to unstable.
Changes since xterm-225-1:
Branden Robinson (1):
Remove debian/NEWS.
Julien Cristau (6):
Configure with --with-tty-group=tty.
Import xterm 226.
256colres.h |2
256colres.pl |9
88colres.h|2
88colres.pl | 10
INSTALL | 31
MANIFEST | 13
Makefile.in
256colres.h |2
256colres.pl|9
88colres.h |2
88colres.pl | 10
INSTALL | 31
MANIFEST| 13
Makefile.in | 31
README |4
Te
Your message dated Mon, 18 Jun 2007 13:50:34 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#391895: xserver-xorg: incorrect display after X starts up
(not always reproducible)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has b
Your message dated Mon, 18 Jun 2007 14:18:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#429345: /usr/bin/bitmap: [bitmap] can't edit bitmap
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 th
Nope, all seems fine now under unstable.
Cheers,
Eamonn
On Sun, 2007-06-17 at 15:58 +0200, Brice Goglin wrote:
> Hi,
>
> About a year ago, you reported a bug to the Debian BTS regarding your
> XKB config not being enabled anymore after upgrade. Did you reproduce
> this problem recently? With Xor
discover --data-path=xfree86/server/device/driver display
returns the correct driver on both PCs (i810 and savage, respectively).
Unfortunately I don't have access to any sarge-machines I could upgrade
at the moment.
Daniel
Brice Goglin wrote:
> Hi Daniel,
>
> Could you install discover and se
On Sun, Jun 17, 2007 at 08:20:44PM +0200, Brice Goglin <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> About a year ago, you reported a bug to the Debian BTS regarding a wrong
> keyboard being chosen for japanese keyboard. Did you reproduce this
> problem recently? With Xorg/Etch? With latest Xorg packages
#
# 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 #419614
# * https://bugs.freedesktop.org/show_bug.cgi?id=9275
# * remote status changed: (?) -> RESOLVED
#
# bts-link upstream status pull for source package xserver-xorg-input-penmount
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #422678
# * https://bugs.freedesktop.org/show_bug.cgi?id=10262
# * remote status changed
Am Sun, 17 Jun 2007 01:46:34 +0200
schrieb Brice Goglin <[EMAIL PROTECTED]>:
> About a year ago, you reported a bug to the Debian BTS regarding the
> nv driver leading to garbage on screen after moving objects. Did you
> reproduce this problem recently? With Xorg/Etch? With latest
> xserver-xorg-c
Hi,
> About 8 months ago, you reported a bug to the Debian BTS regarding some
> rendering problems with Xorg on a Matrox Mystique 1064GS board. Did you
> reproduce this problem recently? With Xorg/Etch? With latest
> xserver-xorg-core 1.3 and mga driver 1.4.6.1 currently in unstable? If
> not, I wi
Your message dated Mon, 18 Jun 2007 08:36:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400695: Add support for the ATI Technologies Inc M56P
[Radeon Mobility X1600]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been de
Your message dated Mon, 18 Jun 2007 08:39:29 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#381447: xserver-xorg-video-ati: Fails to detect Radeon
V5200 on thinkpad T60p
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been de
On Mon, 2007-06-18 at 09:03 +0400, Sergei Golovan wrote:
> On 6/18/07, Drew Parsons <[EMAIL PROTECTED]> wrote:
> > I haven't got this arial font installed. Which package is it in?
>
> Any TTF font metrics are incorrect if the font in iso10646-1 encoding.
>
> xfd -fn '-dejavu-dejavu sans-medium-r-
44 matches
Mail list logo
