Can you switch from the graphical console (ctrl-alt-f5) to a text
console (ctrl-alt-f1), and back? That may help with input device
related problems.
On 2014 Nov 23 (Sun) at 11:08:23 -0500 (-0500), Maximilian Pichler wrote:
:Hi,
:
:After resuming from suspend (either by closing and reopening the
On 24/11/14(Mon) 09:04, Peter Hessler wrote:
Can you switch from the graphical console (ctrl-alt-f5) to a text
console (ctrl-alt-f1), and back? That may help with input device
related problems.
That won't work in this case. His pointer isn't behind the mux and
needs to be calibrated.
Thanks for the explanations!
On Mon, Nov 24, 2014 at 4:19 AM, Martin Pieuchot mpieuc...@nolizard.org wrote:
On 24/11/14(Mon) 09:04, Peter Hessler wrote:
Can you switch from the graphical console (ctrl-alt-f5) to a text
console (ctrl-alt-f1), and back? That may help with input device
related
On 24/11/14(Mon) 08:11, Maximilian Pichler wrote:
Thanks for the explanations!
On Mon, Nov 24, 2014 at 4:19 AM, Martin Pieuchot mpieuc...@nolizard.org
wrote:
On 24/11/14(Mon) 09:04, Peter Hessler wrote:
Can you switch from the graphical console (ctrl-alt-f5) to a text
console
On Mon, Nov 24, 2014 at 8:21 AM, Martin Pieuchot mpieuc...@nolizard.org wrote:
On 24/11/14(Mon) 08:11, Maximilian Pichler wrote:
It's even slightly worse: after resuming, the keyboard still works in
X, but switching to a text console (either via ctrl-alt-f1 or by
quitting X) results in the
* On Mon Nov 24, 2014 at 08:56:59AM -0500 1558 , Maximilian Pichler
(maxim.pich...@gmail.com) wrote:
On Mon, Nov 24, 2014 at 8:21 AM, Martin Pieuchot mpieuc...@nolizard.org
wrote:
On 24/11/14(Mon) 08:11, Maximilian Pichler wrote:
It's even slightly worse: after resuming, the keyboard still
Thanks for explaining!
On Sun, Nov 23, 2014 at 12:44 AM, Martin Pieuchot wrote:
The best you can do for the moment is restart X after resuming,
it should recalibrate your touchpad properly.
Quitting X after resuming results in the keyboard becoming unusable in
the text console, i.e. garbled
That works! In fact, 'xinput enable /dev/wsmouse1' seems to suffice to
fix the trackpad after resume.
In the text console the keyboard remains broken, though.
Thanks
On Mon, Nov 24, 2014 at 9:09 AM, Jaime Tarrant j...@cookiesystems.com wrote:
* On Mon Nov 24, 2014 at 08:56:59AM -0500 1558 ,
* On Mon Nov 24, 2014 at 07:32:51PM -0500 1636 , Maximilian Pichler
(maxim.pich...@gmail.com) wrote:
Subject: Re: Trackpad after suspend/resume on MacBookAir4,1
That works! In fact, 'xinput enable /dev/wsmouse1' seems to suffice to
fix the trackpad after resume.
In the text console
Hello Maximilian,
On 23/11/14(Sun) 11:08, Maximilian Pichler wrote:
Hi,
After resuming from suspend (either by closing and reopening the lid
or via zzz) the trackpad behaves erratically -- the pointer jumps
around wildly when using it. The issue is reproducible.
This is a known issue with
10 matches
Mail list logo
