On Wed, 4 May 2016 16:45:24 -0400 Conrad Knight said:
> Just ran into a problem i've never seen before... E0.21-b has been
> working fine for me so far, but today was the first time since
> switching that i had to take my laptop somewhere, so i closed the lid
> to suspend it. When i later opened the lid, the laptop woke up, but
> the display was blank, or so i thought at first.
>
> Near the top left corner was the cursor, apparently pointing at a
> small (10 x 10 pixels, maybe?), blue-ish square. Moving my finger over
> the touchpad did not move the cursor. Experimenting a little, i
> realised that if i continually slid across the touchpad in the same
> direction, the mouse cursor would very gradually move in that
> direction.
>
> When i got to an edge of the tiny square, the cursor would appear to
> stutter, and bounce back a pixel -- edge flip! The tiny square was my
> desktop, so the colour made sense, the cursor movement was scaled to
> the same miniature size... it made sense. But why? And, by the way,
> the cursor itself was full sized, much larger than the tiny box
> itself.
>
> No clues in any log files i could find. E responded to
> enlightenment_remote (-restart didn't fix it, -exit exited cleanly and
> reset the screen). X itself seems to have the correct resolution (the
> cursor was the right size). I haven't had any driver issues, and
> haven't changed them any time recently. Does anyone have an idea what
> might be going on? As i mentioned, this is the 0.21-beta release, so
> if it's a Known Problem, is there maybe a command line work-around to
> use for now?
never seen that. sounds like randr has reconfigured the screen to 10x10 or
whatever. e does have logs. look for RRR: in stdout/err logs from e. but at
least on my laptop (intel gfx) it stays happy. different drivers do different
things - on some you get screen unplug events from the randr subsystem inside x
when you close the lid. on others you don't. if no screens are left (everything
unplugged) e just uses root window size as screen until at least 1 screen is
back... but randr is a hell hole of pain due to inconsistent behaviour, some
drivers not producing any events on plug/unplug, randr itself often refusing to
update the client-side cache without jumping through polling hoops that force
the server to paus for like 0.1 sec as it re-probes all outputs (causing
horrible framerate stutters)... then even more fun that any x app/client can
mess with randr. there isnt a single controller.
--
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com
--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
