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

Bug#693265: marked as done (kde-full: keyboard stucks in some situations)

Your message dated Sun, 08 Dec 2019 18:44:25 +0100
with message-id <8550673.L1JgYx4RFG@grumly>
and subject line 
has caused the Debian Bug report #693265,
regarding kde-full: keyboard stucks in some situations
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 the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
693265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693265
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kde-full
Version: 5:77
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
There 2 easily reproducible situations:
 1. Open konsole and start okular in background, Quit okular, konsole gets
the focus back, but no keyboard input will be possible anymore. 
Solution: switch windows with ALT+TAB twice, back in konsole the keyboard
can be used again.

 2. A notice pops up like from opera mail, device manager or update manager
-> keyboard stops working 
Solution:switch windows with ALT+TAB twice, back in konsole the keyboard   
can be used again.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
type on keyboard like in this editor to write this bug report
or writing an email with kmail, or any other keyboard task

   * What was the outcome of this action?
the action press keyboard has no outcome

it happens on radeon driven system as well as on nvidia driven system
systems have no xorg.conf
the problem occurs for different users with different config files

   * What outcome did you expect instead?
I expect that the key I press has the expected effect, usaly a letter or
number does occur in editor or composer or terminal

*** End of the template - remove these lines ***


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kde-full depends on:
ii  kde-plasma-desktop  5:77
ii  kde-plasma-netbook  5:77
ii  kdeadmin            4:4.8.4-1
ii  kdeartwork          4:4.8.4-2
ii  kdeedu              4:4.8.4+5.77
ii  kdegames            4:4.8.4-3
ii  kdegraphics         4:4.8.4+5.77
ii  kdemultimedia       4:4.8.4-2
ii  kdenetwork          4:4.8.4-1
ii  kdepim              4:4.4.11.1+l10n-3
ii  kdeplasma-addons    4:4.8.4-1
ii  kdeutils            4:4.8.4+5.77

Versions of packages kde-full recommends:
ii  kde-standard      5:77
ii  kdeaccessibility  4:4.8.4+5.77
ii  kdesdk            4:4.8.4-2
ii  kdetoys           4:4.8.4-1
ii  kdewebdev         4:4.8.4-1

Versions of packages kde-full suggests:
pn  calligra  <none>
pn  kde-l10n  <none>
ii  xorg      1:7.7+1

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi Harald,

I’m marking this bug as closed since it was raised against an old and now 
unsupported version of Debian.

Feel free to open a new bug if you still experience the kind of issue you 
mentioned in this bug report.
At first glance it would look more like a window manager / driver bug.


Happy hacking,
--
Aurélien

--- End Message ---
Reply to: