Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #175689
| Path | csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod |
|---|---|
| From | Kent West <westk@acu.edu> |
| Newsgroups | linux.debian.user |
| Subject | Re: Plasma: keyboard crash |
| Date | Tue, 13 Dec 2016 22:40:02 +0100 |
| Message-ID | <sO2XM-6i5-13@gated-at.bofh.it> (permalink) |
| References | <sNFHQ-v6-23@gated-at.bofh.it> <sNZnb-44P-3@gated-at.bofh.it> <sO15E-58V-37@gated-at.bofh.it> <sO1p0-5fY-33@gated-at.bofh.it> |
| X-Original-To | debian users <debian-user@lists.debian.org> |
| X-Mailbox-Line | From debian-user-request@lists.debian.org Tue Dec 13 21:30:43 2016 |
| Old-Return-Path | <westk@acu.edu> |
| X-Amavis-Spam-Status | No, score=-5.7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no autolearn_force=no |
| X-Policyd-Weight | NOT_IN_SBL_XBL_SPAMHAUS=-1.5 BL_NJABL=SKIP(-1.5) CL_IP_EQ_HELO_IP=-2 (check from: .acu. - helo: .mail-qt0-x230.google. - helo-domain: .google.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -5 |
| Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=acu-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to; bh=e/WtubrHmb47QIGUoYx+JcLhMdvYFRVLJRkvvb/MOmw=; b=i4QmnTZK7AwGMEuPzDInycbfkUVokx1x7hpqtKsNURB6ViTZH71fldnrTPuhb8q8r8 kLy+qkqork4su7856y160976Cn3LoBUHW1Xkd21T7pXaJhIRRJTIPS27+CxPBE11/aOm mawD+LR8QIlSkyZUeR+dIEH/MjErH2kgw8UdqLksRIoY1LmxCCIoyj8pQM+g2skBtFeD he6+X32PmgkHb+VfsLjjSUcZzfYGiLSxFYe2EW/sxa+pOMfl37bSmPTeH5yRUPJHr4V7 bDKQnB7doYWBIXghse2Hy/JUeP6mcjKh6t2RTs/oXE+HEY2Pte4f11btTewBgGJeMYMZ mEsA== |
| X-Google-Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=e/WtubrHmb47QIGUoYx+JcLhMdvYFRVLJRkvvb/MOmw=; b=eLqRyEQOJ5SJSiDZY3zP/aBj0onWcbjDUiFA+/ThhYS0Joh4vL20US+QO+V8BESWMT eg7q1KGu2gjUAJaMOyWnEekKf9fXEo6MVcQC0UkOeR3tuhcbZAxps1y9b3A0PRsrAixJ LUIBcPFkq9KXCuf5/APQJkyGIMKDdOxUX3xyHSvRnKOMPfG0qpPjPtiS/XwUvn/L23uA 9+ZyaMpmUhkLNN9KdK6aAAN0/rOa5t2jKf6bQT/oZ2YHCSdZBtDLG7no8ZlEhJRfep2d yEoV8gAvBX2xNnSxkVe++0sjiX/oYH7XD4Iiubo9H1DMiztyoUZFUq15pdUww0isqk6J Js6g== |
| X-Gm-Message-State | AKaTC01y/kg2cP2Ahr4jMOVdYCiNPJRMDvduoRMFA4hCLqAEW12IxF2OWPW8EFBesDIQoCdBCxPluAkQ/YgC0vsQ |
| X-Received | by 10.237.33.173 with SMTP id l42mr84255048qtc.271.1481664625004; Tue, 13 Dec 2016 13:30:25 -0800 (PST) |
| MIME-Version | 1.0 |
| Reply-To | kent.west@acu.edu |
| Content-Type | multipart/alternative; boundary=001a113e46fea6755a054390ed33 |
| X-Mailing-List | <debian-user@lists.debian.org> archive/latest/715262 |
| List-ID | <debian-user.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-user/> |
| List-Archive | https://lists.debian.org/msgid-search/CAByJ6DGFfoYVGuWMOt9hH=0sYVs=8gszu1Jn8AvzRq_zoFOouA@mail.gmail.com |
| Approved | robomod@news.nic.it |
| Lines | 61 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Tue, 13 Dec 2016 15:29:44 -0600 |
| X-Original-Message-ID | <CAByJ6DGFfoYVGuWMOt9hH=0sYVs=8gszu1Jn8AvzRq_zoFOouA@mail.gmail.com> |
| X-Original-References | <10736675.pWBBTQaZZP@protheus2> <3342006.6pjPDBQQra@protheus2> <1798500.gDBl2nBEdW@mark> <2236367.E12SyYjcZv@protheus2> |
| Xref | csiph.com linux.debian.user:175689 |
Show key headers only | View raw
[Multipart message — attachments visible in raw view] - view raw
On Tue, Dec 13, 2016 at 1:54 PM, Hans <hans.ullrich@loop.de> wrote: > > But that is another story. However, is there a way, to restart the > keyboard, > without leaving plasma? When the keyboard crashes, I can still open a > console, > start an onscreen keyboard (ie. kvkbd) and could use the mouse for input. > A similar problem is at https://bbs.archlinux.org/viewtopic.php?id=203724, and a recommendation was to restart the relevant module: > rmmod atkbd ; modprobe atkbd reset=1 I'm not sure what module is driving your keyboard, but "lsmod" should list the loaded modules, and you can probably guess/tinker to find the module, like maybe "uinput" or "hid" or "hid_generic" or "usb_hid" or "usbcore" or .... However, I'd recommend you do the command in a single line, like above, rather than separate lines, in case you kill your mouse in the process and lose the ability to mouse-type. -- Kent
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Plasma: keyboard crash Hans <hans.ullrich@loop.de> - 2016-12-12 21:50 +0100
Re: Plasma: keyboard crash kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2016-12-13 06:00 +0100
Re: Plasma: keyboard crash Hans <hans.ullrich@loop.de> - 2016-12-13 18:50 +0100
Re: Plasma: keyboard crash Mark Neidorff <mark@neidorff.com> - 2016-12-13 20:40 +0100
Re: Plasma: keyboard crash Hans <hans.ullrich@loop.de> - 2016-12-13 21:00 +0100
Re: Plasma: keyboard crash Kent West <westk@acu.edu> - 2016-12-13 22:40 +0100
Re: Plasma: keyboard crash Mark Neidorff <mark@neidorff.com> - 2016-12-13 18:50 +0100
csiph-web