[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#598837: kwrite: Kwrite regularly goes into "backwards typing" mode



Package: kwrite
Version: 4:4.4.5-1
Severity: important

*** Please type your report below this line ***

Hi, if I use kwrite to actively edit fairly large text files (with
long, wrapping lines, in dynamic wrap mode), then after about 5-10
minutes kwrite goes into "backwards typing" mode.

By "backward typing" mode, I mean when I press keys, that the cursor
in kwrite doesn't move, but the typed letters appear to the right of
the cursor, with the effect that what you type comes out backwards.

I can move the cursor around by clicking with the mouse, but when I
resume typing, I still have the same problem (at the new cursor
location).

This is pretty annoying - the only way I've found to correct this is
to restart kwrite.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kwrite depends on:
ii  kdebase-runtime               4:4.4.5-1  runtime components from the offici
ii  libc6                         2.11.2-6   Embedded GNU C Library: Shared lib
ii  libkdecore5                   4:4.4.5-1  the KDE Platform Core Library
ii  libkdeui5                     4:4.4.5-1  the KDE Platform User Interface Li
ii  libkio5                       4:4.4.5-1  the Network-enabled File Managemen
ii  libkparts4                    4:4.4.5-1  the Framework for the KDE Platform
ii  libktexteditor4               4:4.4.5-1  the KTextEditor interfaces for the
ii  libqtcore4                    4:4.6.3-2  Qt 4 core module
ii  libqtgui4                     4:4.6.3-2  Qt 4 GUI module
ii  libstdc++6                    4.4.4-17   The GNU Standard C++ Library v3

kwrite recommends no packages.

kwrite suggests no packages.

-- no debconf information



Reply to: