If this bug is going to be marked wontfix, I think a justification is
in order. Enabling "eightBitInput" (which Henning has correctly noted
is a misnomer) by default clashes with non-7bit characters, making it
unreasonable for any application using a terminal to attempt to treat
octets with the 8th
Your message dated Tue, 20 Nov 2007 02:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#451950: fixed in xorg-server 2:1.4.1~git20071119-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
Your message dated Tue, 20 Nov 2007 02:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#451950: fixed in xorg-server 2:1.4.1~git20071119-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
Your message dated Tue, 20 Nov 2007 02:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#451950: fixed in xorg-server 2:1.4.1~git20071119-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
Your message dated Tue, 20 Nov 2007 02:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#451891: fixed in xorg-server 2:1.4.1~git20071119-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
Your message dated Tue, 20 Nov 2007 02:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#451891: fixed in xorg-server 2:1.4.1~git20071119-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
Your message dated Tue, 20 Nov 2007 02:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#451950: fixed in xorg-server 2:1.4.1~git20071119-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
Your message dated Tue, 20 Nov 2007 02:47:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#451950: fixed in xorg-server 2:1.4.1~git20071119-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
Tag 'xorg-server-2_1.4.1_git20071119-1' created by David Nusinow <[EMAIL
PROTECTED]> at 2007-11-20 02:31 +
Tagging upload of xorg-server-2_1.4.1_git20071119-1 to unstable.
Changes since xorg-server-2_1.4.1_git20071117-1:
Brice Goglin (1):
Do not call laptop-detect, let the only user ca
debian/changelog | 10 +++--
debian/patches/14_default_screen_section.diff | 49 +-
debian/rules |2 -
3 files changed, 40 insertions(+), 21 deletions(-)
New commits:
commit 789139ee3ce57258a294e2f1cf33d
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.10
> reassign 452040 xserver-xorg-core
Bug#452040: xserver-xorg: xserver don't find device specified for screen
Bug reassigned from package `xserver-xorg' to `xserver-xorg-core'.
> reass
Package: xserver-xorg
Version: 1:7.3+6
Severity: important
Hi,
As you may see in the attached log file, when X
starts, it claims the DefaultScreen section did
not specify a device or monitor. As a result, it
picks, instead of my "BenQ Monitor", some default
configuration that only supports 640x4
Cameron McCormack:
> Sorry for the delay in replying, and not following up originally. I did
> attempt to install it (after your initial reply), but found it brought
> in other things which broke. After that I reverted to 6.6.3.
>
> I will try again today with the 6.7 package and report back.
1
Package: xserver-xorg
Version: 1:7.3+6
Severity: important
The device specified in the Screen section is not recognized : xserver
always takes the device of the first Device section in xorg.conf
the related section of xorg.conf :
Section "Device"
Identifier "NVidia"
Driver
Hi Brice.
Brice Goglin:
> > If 6.6.193 does not work for you, you should either revert to the old
> > 6.6.3 or upgrade to new 6.7.194 in experimental. The 6.6.x branch is
> > dead anyway, so this exact problem won't be fixed.
> >
> > The 6.7.x branch contains RandR 1.2 which provides dynamic conf
Brice,
> Could you test with xserver-xorg-core 2:1.4.1~git20071117-1 which
> just got uploaded to unstable? It contains multiple input-related fixes.
No, it still fails -- same behavior.
Thanks.. Bill
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
Alan W. Irwin wrote:
> This is a production system so my top priority is to get X working again,
> Thus, the next thing I am going to try is removing xorg from unstable and
> reinstalling the testing version. I only moved to the unstable xorg version
> in desperation when I could not get modelines
also sprach Brice Goglin <[EMAIL PROTECTED]> [2007.11.19.2042 +0100]:
> As soon as you have one board with a RandR 1.2 driver, you can't
> use any other board, even if its driver is different and does not
> support RandR 1.2. It just crashes the server.
> I am merging with the exiting relevant bugs
Anthony Campbell wrote:
> I'm not sure this is an xserver-xorg issue. It seems to have something
> to do with icewm. When I bring up a menu with Ctrl-Esc it locks up. If I
> bring it up with the mouse by clicking on the link at the bottom of the
> screen it doesn't happen. However, it has started d
On Mon, 2007-11-19 at 20:33 +0100, Brice Goglin wrote:
> Does it help if you add
> Option "AccelMethod" "XAA"
> in the above section? EXA is enabled by default in 2.2.0.
> But there is at least one known problem with fonts and EXA.
I can confirm that fixes the problem for me (82Q963/Q965).
Package: xserver-xorg-video-intel
Version: 2:2.2.0-1
Followup-For: Bug #451917
Brice said:
> Anyway, could you try changing your modeline into something else?
For instance [EMAIL PROTECTED] or [EMAIL PROTECTED] instead?
(use gtf to get the corresponding modeline).
Hi Brice:
I was also concerne
reassign 451972 xserver-xorg-core
forcemerge 443274 451972
thank you
On Mon, Nov 19, 2007 at 04:16:55PM +0100, martin f krafft wrote:
> Package: xserver-xorg-video-ati
> Version: 1:6.6.193-3
> Severity: serious
>
> sid's xserver-xorg-video-ati (and also in experimental) no longer
> supports Mer
Processing commands for [EMAIL PROTECTED]:
> reassign 451972 xserver-xorg-core
Bug#451972: no longer supports xinerama across multiple graphics cards
Bug reassigned from package `xserver-xorg-video-ati' to `xserver-xorg-core'.
> forcemerge 443274 451972
Bug#443274: Xserver 1.4 + RandR 1.2 driver
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.10
> reassign 451977 xserver-xorg-core
Bug#451977: xorg: After lastest upgrade HorizSync and VertRefresh no longer
works
Bug reassigned from package `xorg' to `xserver-xorg-core'.
> rea
On Mon, Nov 19, 2007 at 08:45:57AM +0100, Philip Frei wrote:
> Package: xserver-xorg-video-intel
> Version: 2:2.2.0-1
> Severity: grave
> Justification: renders package unusable
>
>
> Since I installaed the new driver my xservder doesn't show any fonts.
> Not in input boxes, not in menus.
> I can
found 444049 1:6.7.196-1
retitle 444049 ati: locks up radeon 9000/9250 in AGP mode
thank you
Michal Suchanek wrote:
> Yes, it works in PCI mode. 6.7.196 is still broken.
>
> Unless somebody specifically tries to fix this or there are changes
> that are likely to fix this I guess there is not mu
Processing commands for [EMAIL PROTECTED]:
> found 444049 1:6.7.196-1
Bug#444049: xserver-xorg-video-ati: 6.6.193 and on locks up radeon 9000/9250
Bug marked as found in version 1:6.7.196-1.
> retitle 444049 ati: locks up radeon 9000/9250 in AGP mode
Bug#444049: xserver-xorg-video-ati: 6.6.193 an
I'm not sure this is an xserver-xorg issue. It seems to have something
to do with icewm. When I bring up a menu with Ctrl-Esc it locks up. If I
bring it up with the mouse by clicking on the link at the bottom of the
screen it doesn't happen. However, it has started doing this since the
recent upgra
Hi,
Downgrading xserver-xorg-core 2:1.4.1~git20071117-1 -> 2:1.4-3 fixed
this problem for me.
/Fredrik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The problem is not Xorg 1:7.3+6 but som of the other packages related to it.
Downgradeing those package solves the problem. See the Aptitdude log below.
O.B.S. I upgrade to Xorg 1:7.3+6 after that I tested to solve the problem by
downgrade to Xorg 1:7.2-5.
Aptitude log.
[NEDGRADERING] xserver-xorg
Package: xserver-xorg
Version: 1:7.3+6
Severity: grave
Justification: renders package unusable
*** Please type your report below this line *
Just after upgrade, if I start X it comes up. But as soon as I open an
xterm the whole things locks up and I have to reboot.
-- Package-specific info:
/var/
Processing commands for [EMAIL PROTECTED]:
> reassign 451983 xserver-xorg-core
Bug#451983: Device and Monitor identifiers in Screen section of xorg.conf
ignored
Bug reassigned from package `xorg' to `xserver-xorg-core'.
> merge 451983 451876
Bug#451876: xserver-xorg-core: screen mode selection e
Package: xorg
Version: 1:7.3+6
Severity: normal
After upgrading xorg 1:7.3+3 -> 1:7.3+6 the Device and Montior
identifiers in the Screen section are ignored and replaced with default
values. This works ok for my first screen, since the default is to use
the first device section in the file, but my
debian/changelog| 1128
debian/control |6
debian/local/dexconf|1
debian/xserver-xorg.postinst.in | 19
debian/xserver-xorg.prerm.in| 19
5 files changed, 1146 insertions(+), 27 deletions(-)
Package: xorg
Version: 1:7.3+6
Severity: important
When reading EDID from a connected monitors fails xorg no more uses the
manually provide HorizSync and VertRefresh which means that xorg will fall back
to the hardcoded 800x600 and not permit any higher resolution even if the
graphics card supp
Same thing here - GM965/GL960.
--
dann frazier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: xserver-xorg-video-ati
Version: 1:6.6.193-3
Severity: serious
sid's xserver-xorg-video-ati (and also in experimental) no longer
supports MergedFB. Thus, it is no longer possible to address the two
ports without RandR.
Since RandR is incompatible with Xinerama, and RandR 1.2 does not
yet
On 18/11/2007, Brice Goglin <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 25, 2007 at 08:41:36PM +0200, Brice Goglin wrote:
> > notfound 444049 1:6.6.3-2
> > found 444049 1:6.6.193-3
> > found 444049 1:6.7.194-1
> > forwarded 444049 https://bugs.freedesktop.org/show_bug.cgi?id=12544
> > thank you
> >
>
On 11/11/2007, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Hi Michal,
>
> Any news about this bug? Anything better with 1:6.7.195-2 currently
> in experimental?
>
It's been fixed (the resolution) in some 6.7.192 or so.
The lockup is present in 6.7.196 but the mode handling there is
apparently differ
You may need to apply this patch:
http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commitdiff_plain;h=28ef7f59416677be380561709197b04df0479bef;hp=ea2d4dc468dcebe6d38e676469ec51ed1d43490b
On Mon, 19 November 2007, you wrote:
> That's very surprising since DisplaySize didn't work earlier and is
> supposed to be fixed now. Can you try with the nv driver instead of
> nvidia? It could explain this strange behavior.
(**) NV(0): Display dimensions: (350, 260) mm
(**) NV(0): DPI set to (1
Robert Grimm wrote:
> Package: xserver-xorg-core
> Version: 2:1.4.1~git20071117-1
> Severity: minor
>
> After the last upgrade of xserver-xorg-core I noticed that DisplaySize
> is ignored and I ended up with a 75x75 DPI, and thus unusable Display.
>
> As a workaround I inserted
> Option
Package: xserver-xorg-core
Version: 2:1.4.1~git20071117-1
Severity: important
hi,
restarting X earlier left me with a nasty surprise. after checking the
log, it was telling me no modes of that name (1024x768) even though the
version previous it was working fine. seems it "forgot" that others
mode
Package: xserver-xorg-core
Version: 2:1.4.1~git20071117-1
Severity: minor
After the last upgrade of xserver-xorg-core I noticed that DisplaySize
is ignored and I ended up with a 75x75 DPI, and thus unusable Display.
As a workaround I inserted
Option "DPI" "109 x 109"
in the
You don't even have to give up alcohol or smoking for our [EMAIL PROTECTED]
Little Super thing to Work!
Alexsandra Marasigan
http://hourstretch.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Impotenz cure pillz right to your door
Tonia trizis
http://www.radiohundred.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The easiest way to avoid shame with a nice baby
Macave Gokulam
http://www.radiohundred.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Tumble all night long
brie Bellemare
http://www.objectsave.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Version 2:2.2.0-1 havbe the same problem with mu-cade and additionally
crash in the same maneer when I run any wine emulated opengl games
using pixel shader (wine 0.9.47~winehq0~debian~4.0-1 from winehq.org)
Bye
--
-
|Marco
Works for me now. Thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Alan W. Irwin wrote:
> Package: xserver-xorg-video-intel
> Version: 2:2.2.0-1
> Severity: normal
>
>
> X -probeonly
>
> completely locks up the keyboard with the monitor immediately put into its
> low-power state (as close to turned off as possible without quite being
> turned off) so the only r
Your message dated Mon, 19 Nov 2007 10:54:07 +0100
with message-id <[EMAIL PROTECTED]>
and subject line xserver-xorg-input-kbd: order matters when pressing Ctrl + Alt
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
Your message dated Mon, 19 Nov 2007 10:54:07 +0100
with message-id <[EMAIL PROTECTED]>
and subject line xserver-xorg-input-kbd: order matters when pressing Ctrl + Alt
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
Your message dated Mon, 19 Nov 2007 10:54:07 +0100
with message-id <[EMAIL PROTECTED]>
and subject line xserver-xorg-input-kbd: order matters when pressing Ctrl + Alt
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
Package: xserver-xorg-video-intel
Version: 2:2.2.0-1
Severity: normal
X -probeonly
completely locks up the keyboard with the monitor immediately put into its
low-power state (as close to turned off as possible without quite being
turned off) so the only recourse is to log in remotely and shutdow
On Nov 18, 2007 6:29 PM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Could you guys test with xserver-xorg-core 2:1.4.1~git20071117-1 which
> just got uploaded to unstable? It contains multiple input-related fixes.
Fixed mine (443471) but reverted back to xserver-xorg-core 2:1.4-3 as
with 2:1.4.1~gi
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> forcemerge 451904 451891
Bug#451904: xorg-server - FTBFS: /bin/sh: line 1: ../configure: Permission
denied
Bug#451891: ftbfs: configure has no x-bit
Forcibly Merged 451891 451904.
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.11
> tags 451904 pending
Bug#451904: xorg-server - FTBFS: /bin/sh: line 1: ../configure: Permission
denied
There were no tags set.
Bug#451891: ftbfs: configure has no x-bit
Tags added: p
Package: xorg-server
Version: 2:1.4.1~git20071117-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of xorg-server_2:1.4.1~git20071117-1 on lxdebian.bfinv.de by
> sbuild/s390 98
[...]
> mkdir -p obj-s390-linux-gnu/GL
> cd obj-s390-linux-gnu && \
>
59 matches
Mail list logo