On Tue, Aug 11, 2009 at 11:53:44PM +0200, Aurelien Jarno wrote:
Package: xserver-xorg-input-kbd
Version: 1:1.3.2-3
Severity: wishlist
Please find attached an fdi file to drop in
/usr/share/hal/fdi/policy/10osvendor,
which contains the rules to support GNU/kFreeBSD.
Actually it makes
Hi,
I get redrawing issues with 244-1 too, downgrading to 243-1 fixes the
issue for me.
Cheers
--
Alexander Clouter
.sigmonster says: L'hasard ne favorise que l'esprit prepare.
-- L. Pasteur
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with
Processing commands for cont...@bugs.debian.org:
reassign 534945 xkb-data
Bug #534945 [xserver-xorg-input-kbd] xserver-xorg-input-kbd: XkbOptions have no
effect in some applications
Bug reassigned from package 'xserver-xorg-input-kbd' to 'xkb-data'.
Bug No longer marked as found in versions
On Wed, May 27, 2009 at 17:58:08 +0200, Vincent Lefevre wrote:
And the backtrace of previous execution (without valgrind):
vin:~ gdb =midori core
GNU gdb 6.8-debian
[...]
Core was generated by `midori'.
Program terminated with signal 11, Segmentation fault.
[New process 10943]
#0
This appears to be the same issue that I am having. I regularly change xterm
sizes via key mappings in fvwm. I'm loosing xterms to segv right and left.
I request that this gets bumped up to important or higher. At the rate it's
going for me I'm going to be switching terminal emulators this
Package: xserver-xorg-input-evdev
Version: 1:2.0.8-1
Severity: normal
I recently was forced to switch to the evdev driver from the kbd driver
(the kbd driver generates spurious repeat events under load due to
the lack of event timestamps, evdev fixes that as the kernel delivers
timestamps).
Package: x11-xserver-utils
Version: 7.4+2
Severity: wishlist
The xrdb(1) man page says:
SEE ALSO
X(7), appres(1), listres(1), Xlib Resource Manager documentation,
Xt resource documentation
(ditto for other x11-xserver-utils utilities), but the X(7) man page is
not provided and it is a
Processing commands for cont...@bugs.debian.org:
forwarded 531771 https://bugs.freedesktop.org/show_bug.cgi?id=23266
Bug #531771 [xkb-data] xkb-data: level 3 switch not working anymore
Bug #532717 [xkb-data] gtk+2.0: AltGr stop fully to function since reecent
update
Bug #534945 [xkb-data]
FYI: The status of the xtrans source package
in Debian's testing distribution has changed.
Previous version: 1.2.3-3
Current version: 1.2.4-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
Ditto. Here's a backtrace:
(gdb) run
Starting program: /usr/bin/xterm
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x00430510 in ?? ()
(gdb) bt
#0 0x00430510 in ?? ()
#1 0x00430e64 in ?? ()
#2 0x7feb33f313aa in
Package: xserver-xorg-video-ati
Version: 1:6.12.2-3
Severity: important
*** Please type your report below this line ***
Hello,
I've been hesitating a lot before posting this bug and still am not 100%
sure if it's worth doing it, but whatever...
Brief description:
I use the radeon driver
Package: xterm
Version: 244-1
Severity: normal
Under some conditions, a word selection selects whitespace characters
too. This problem seems to be new.
To reproduce the problem, I've attached a file. As said in this file:
1. Open this file in a 80x60 xterm terminal.
2. Do a Page Down.
3.
On 2009-08-12 19:14:23 +0200, Vincent Lefevre wrote:
Under some conditions, a word selection selects whitespace characters
too. This problem seems to be new.
Indeed, I've reverted to xterm 243-1, and I cannot reproduce the bug
with this older version.
--
Vincent Lefèvre vinc...@vinc17.org -
On Wed, Aug 12, 2009 at 1:06 PM, Stefanopietran...@gmail.com wrote:
Package: xserver-xorg-video-ati
Version: 1:6.12.2-3
Severity: important
*** Please type your report below this line ***
Hello,
I've been hesitating a lot before posting this bug and still am not 100%
sure if it's worth
Package: Xdmx
Version: 2:1.6.3-1
Severity: normal
If I start Xdmx, it just segfaults. I tried 2 Sid systems: my Desktop with
an amd64 system, and my laptop with i386.
$ Xdmx -display :0 :1
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for
Processing commands for cont...@bugs.debian.org:
severity 541254 grave
Bug #541254 [xdmx] Xdmx just segfaults
Severity set to 'grave' from 'normal'
tags 541254 upstream
Bug #541254 [xdmx] Xdmx just segfaults
Added tag(s) upstream.
End of message, stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
reassign 541259 xserver-xorg-input-synaptics
Bug #541259 [xserver-xorg] xserver-xorg: crash in XisbRead on wakeup
Bug reassigned from package 'xserver-xorg' to 'xserver-xorg-input-synaptics'.
Bug No longer marked as found in versions xorg/1:7.4+3.
...just bad timing (I'm now looking to see the problem). A short-term fix
should be to configure/build xterm using --disable-fifo-lines
--
Thomas E. Dickey dic...@invisible-island.net
http://invisible-island.net
ftp://invisible-island.net
signature.asc
Description: Digital signature
debian/changelog |8
debian/rules |1 +
2 files changed, 9 insertions(+)
New commits:
commit 0aa37f76fb31c8c5c06569dd7c12dc65514edc3c
Author: Julien Cristau jcris...@debian.org
Date: Wed Aug 12 22:25:21 2009 +0200
Prepare changelog for upload
diff --git
Tag 'xterm-244-2' created by Julien Cristau jcris...@debian.org at 2009-08-12
20:43 +
Tagging upload of xterm 244-2 to unstable.
Changes since xterm-244-1:
Julien Cristau (2):
Configure with --disable-fifo-lines
Prepare changelog for upload
---
debian/changelog |8
xterm_244-2_i386.changes uploaded successfully to localhost
along with the files:
xterm_244-2.dsc
xterm_244-2.diff.gz
xterm_244-2_i386.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
I can reproduce the positioning error. Resizing the fifo-lines required
splitting the logic into parts - seems that I missed a special case in
one of those parts, where the window size first grows, then shrinks before
adding text (something like that...).
--
Thomas E. Dickey
This one is hard to reproduce (here). valgrind is not showing me any
problems as I resize the screen in various ways.
There are several special cases in the resizing logic, depending on
resource-settings, as well as the amount of text that has been scrolled
off onto the saved-lines buffer.
More
Hi,
AGPMode 8 is not supported by my video card
AGPMode 4 was the default mode, thus it does not work
I tried AGPMode 2 but with no results,
at the time I'm writing this email I'm using AGPMode 1 but still I have
the display not behaving correctly (as the attached image in my first
email) and
On 2009-08-12 17:15:25 -0400, Thomas Dickey wrote:
This one is hard to reproduce (here). valgrind is not showing me any
problems as I resize the screen in various ways.
There are several special cases in the resizing logic, depending on
resource-settings, as well as the amount of text that
On Wed, 12 Aug 2009, Vincent Lefevre wrote:
On 2009-08-12 17:15:25 -0400, Thomas Dickey wrote:
This one is hard to reproduce (here). valgrind is not showing me any
problems as I resize the screen in various ways.
There are several special cases in the resizing logic, depending on
On Wed, Aug 12, 2009 at 17:35:40 -0400, Stefano wrote:
I also tried to compile the xf86-video-ati-6.12.2 driver but when
running autogen.sh I have the following error:
./configure: line 11076: syntax error near unexpected token `XINERAMA,'
./configure: line 11076:
Accepted:
xterm_244-2.diff.gz
to pool/main/x/xterm/xterm_244-2.diff.gz
xterm_244-2.dsc
to pool/main/x/xterm/xterm_244-2.dsc
xterm_244-2_i386.deb
to pool/main/x/xterm/xterm_244-2_i386.deb
Override entries for your package:
xterm_244-2.dsc - source x11
xterm_244-2_i386.deb - optional x11
Your message dated Wed, 12 Aug 2009 22:10:48 +
with message-id e1mbm1w-0002ac...@ries.debian.org
and subject line Bug#541109: fixed in xterm 244-2
has caused the Debian Bug report #541109,
regarding with ratpoison, changing font makes terminal window unuseable
to be marked as done.
This means
Your message dated Wed, 12 Aug 2009 22:10:48 +
with message-id e1mbm1w-0002ai...@ries.debian.org
and subject line Bug#541236: fixed in xterm 244-2
has caused the Debian Bug report #541236,
regarding xterm: word selection selects whitespace characters too
to be marked as done.
This means that
Your message dated Wed, 12 Aug 2009 22:10:48 +
with message-id e1mbm1w-0002ae...@ries.debian.org
and subject line Bug#541132: fixed in xterm 244-2
has caused the Debian Bug report #541132,
regarding xterm: crashes when embedded by yeahconsole
to be marked as done.
This means that you claim
Your message dated Wed, 12 Aug 2009 22:10:48 +
with message-id e1mbm1w-0002ag...@ries.debian.org
and subject line Bug#541160: fixed in xterm 244-2
has caused the Debian Bug report #541160,
regarding xterm: heap corruption when changing window size
to be marked as done.
This means that you
2009/7/31 Michel Dänzer daen...@debian.org:
On Fri, 2009-07-31 at 10:29 +0200, Michal Suchanek wrote:
2009/7/31 Michel Dänzer daen...@debian.org:
On Fri, 2009-07-31 at 00:13 +0200, Michal Suchanek wrote:
The next thing to try might be to install the drm modules that came
with the mesa
Hi Julien,
On Wed, Aug 12, 2009 at 10:39:28PM +, Debian Bug Tracking System wrote:
* Configure with --disable-fifo-lines to work around a crash in the new
saved-lines handling code (closes: #541236, #541160, #541132, #541109).
Thanks to Thomas Dickey for the workaround.
On 2009-08-12 17:40:10 -0400, Thomas Dickey wrote:
On Wed, 12 Aug 2009, Vincent Lefevre wrote:
I can reproduce the crash every time with the example given in
bug 541236 (see step 4). In case this depends on the window manager,
I use fvwm.
still no But the stack traces look useful...
I
On Thu, 13 Aug 2009, Vincent Lefevre wrote:
On 2009-08-12 17:40:10 -0400, Thomas Dickey wrote:
On Wed, 12 Aug 2009, Vincent Lefevre wrote:
I can reproduce the crash every time with the example given in
bug 541236 (see step 4). In case this depends on the window manager,
I use fvwm.
still
Hi Thomas,
This one is hard to reproduce (here). valgrind is not showing me any
problems as I resize the screen in various ways.
There are several special cases in the resizing logic, depending on
resource-settings, as well as the amount of text that has been scrolled
off onto the
On Thu, Aug 13, 2009 at 02:17:55 +0200, Jan Christoph Nordholz wrote:
I'll do a few valgrind runs myself and report back.
I got a crash (glibc abort in free()) once, can't seem to reproduce now.
valgrind reports these issues though:
==864== Invalid write of size 1
==864==at 0x402766C:
On Thu, 13 Aug 2009, Jan Christoph Nordholz wrote:
Hi Thomas,
This one is hard to reproduce (here). valgrind is not showing me any
problems as I resize the screen in various ways.
There are several special cases in the resizing logic, depending on
resource-settings, as well as the amount of
On Thu, Aug 13, 2009 at 02:17:55AM +0200, Jan Christoph Nordholz wrote:
Hi Thomas,
This one is hard to reproduce (here). valgrind is not showing me any
problems as I resize the screen in various ways.
There are several special cases in the resizing logic, depending on
On 2009-08-13 02:17:55 +0200, Jan Christoph Nordholz wrote:
I'll do a few valgrind runs myself and report back.
I've just done a test with valgrind. Here's the output:
==22673== Memcheck, a memory error detector.
==22673== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al.
Hi Thomas,
Here's a fix for the positioning problem that I've been seeing (attached).
thank you very much, the malloc corruption is gone now, too.
Regards,
Jan
signature.asc
Description: Digital signature
On Thu, 13 Aug 2009, Jan Christoph Nordholz wrote:
Hi Thomas,
Here's a fix for the positioning problem that I've been seeing (attached).
thank you very much, the malloc corruption is gone now, too.
thanks (I can see how the addressing-error might happen, but am puzzled
that I could not
On Thu, 13 Aug 2009, Julien Cristau wrote:
On Thu, Aug 13, 2009 at 02:17:55 +0200, Jan Christoph Nordholz wrote:
I'll do a few valgrind runs myself and report back.
I got a crash (glibc abort in free()) once, can't seem to reproduce now.
valgrind reports these issues though:
I'm puzzled
This bug sounds like a duplicate of these two upstream:
http://bugs.freedesktop.org/show_bug.cgi?id=20348
http://bugs.freedesktop.org/show_bug.cgi?id=13176
At least for me, enabling XAA and XaaNoSolidFillRect seems to get
decent performance without locking up.
-Dave
--
To UNSUBSCRIBE, email
45 matches
Mail list logo
