On Mon, 8 Jun 2020 20:49:19 -0700 Marc MERLIN <marc_...@merlins.org> said:
> On Mon, Jun 08, 2020 at 12:40:26AM +0100, Carsten Haitzler wrote:
> > > > hmmm no. i don't see any suspicious there... i can't say what is going
> > > > on. perhaps a bug already long fixed? i don't know.
> > >
> > > Isn't "move resize 0 0 -65536x-65536" something bad?
> >
> > not. this is just the first time it runs with some initial values chosen
> > that will ensure a later "did this actually change - did coords change" will
> > actually tigger for the first change of coords... :)
>
> Ok, I had this happen again.
> I'm starting to wonder if my video cable (4K, so it's a lot of BW) picks
> up a bit of noise and the screen disappears for a short while.
it shouldn';t as you clone so one of them still plugged in, unless somehow both
get disconnected at once and then E is in panic mode as in "haaaaaalp no
screens!!!" - in which case e just assumes current root window size == screen
and marches on, but it's going to be a little tested code path.
> But still, that shouldn't cause E to do what it does.
>
> Here are logs;
> [793669.554] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
> [793669.554] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
> [793669.554] (--) NVIDIA(GPU-0):
> [793670.239] (--) NVIDIA(GPU-0): DFP-0: disconnected
> [793670.239] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
> [793670.239] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
> [793670.239] (--) NVIDIA(GPU-0):
> [793670.239] (--) NVIDIA(GPU-0): DFP-1: disconnected
> [793670.239] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
> [793670.239] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
> [793670.239] (--) NVIDIA(GPU-0):
> [793670.239] (--) NVIDIA(GPU-0): DFP-2: disconnected
> [793670.239] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
> [793670.239] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
> [793670.239] (--) NVIDIA(GPU-0):
> [793670.239] (--) NVIDIA(GPU-0): DFP-3: disconnected
> [793670.239] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
> [793670.239] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
> [793670.239] (--) NVIDIA(GPU-0):
> [793670.239] (--) NVIDIA(GPU-0): Panasonic (DFP-4): connected
> [793670.239] (--) NVIDIA(GPU-0): Panasonic (DFP-4): Internal DisplayPort
> [793670.239] (--) NVIDIA(GPU-0): Panasonic (DFP-4): 960.0 MHz maximum pixel
> clock [793670.239] (--) NVIDIA(GPU-0):
> [793670.239] (--) NVIDIA(GPU-0): DFP-5: disconnected
> [793670.239] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
> [793670.239] (--) NVIDIA(GPU-0): DFP-5: 960.0 MHz maximum pixel clock
> [793670.240] (--) NVIDIA(GPU-0):
> [793670.240] (--) NVIDIA(GPU-0): DFP-6: disconnected
> [793670.240] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
> [793670.240] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
> [793670.240] (--) NVIDIA(GPU-0):
> [793670.240] (--) NVIDIA(GPU-0): DFP-0: disconnected
> [793670.240] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
> [793670.240] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
> [793670.240] (--) NVIDIA(GPU-0):
> [793670.240] (--) NVIDIA(GPU-0): DFP-1: disconnected
> [793670.240] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
> [793670.240] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
> [793670.240] (--) NVIDIA(GPU-0):
> [793670.240] (--) NVIDIA(GPU-0): DFP-2: disconnected
> [793670.240] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
> [793670.240] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
> [793670.240] (--) NVIDIA(GPU-0):
> [793670.240] (--) NVIDIA(GPU-0): DFP-3: disconnected
> [793670.240] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
> [793670.240] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
> [793670.240] (--) NVIDIA(GPU-0):
> [793670.240] (--) NVIDIA(GPU-0): Panasonic (DFP-4): connected
> [793670.240] (--) NVIDIA(GPU-0): Panasonic (DFP-4): Internal DisplayPort
> [793670.240] (--) NVIDIA(GPU-0): Panasonic (DFP-4): 960.0 MHz maximum pixel
> clock (...)
> [793764.977] (--) NVIDIA(GPU-0): Acer B326HK (DFP-3): connected
> [793764.977] (--) NVIDIA(GPU-0): Acer B326HK (DFP-3): Internal DisplayPort
> [793764.977] (--) NVIDIA(GPU-0): Acer B326HK (DFP-3): 960.0 MHz maximum pixel
> clock [793764.977] (--) NVIDIA(GPU-0):
> [793764.977] (--) NVIDIA(GPU-0): Panasonic (DFP-4): connected
> [793764.977] (--) NVIDIA(GPU-0): Panasonic (DFP-4): Internal DisplayPort
> [793764.977] (--) NVIDIA(GPU-0): Panasonic (DFP-4): 960.0 MHz maximum pixel
> clock [793764.977] (--) NVIDIA(GPU-0):
> [793764.977] (--) NVIDIA(GPU-0): DFP-5: disconnected
> [793764.977] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
> [793764.977] (--) NVIDIA(GPU-0): DFP-5: 960.0 MHz maximum pixel clock
> [793764.977] (--) NVIDIA(GPU-0):
> [793764.977] (--) NVIDIA(GPU-0): DFP-6: disconnected
> [793764.977] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
> [793764.977] (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
> [793764.977] (--) NVIDIA(GPU-0):
> [794923.602] (--) NVIDIA(GPU-0): DFP-3: disconnected
>
> Ok, so this shows a screen connection/disconnection (there are a few, it
> probably flaps a fair bit).
DFP-3 seems to be flaky.
> Maybe there is a bug if screens are added/removed too quickly in E?
> ERR<20124>: ../src/lib/eina/eina_tiler.c:1252 eina_tiler_rect_del() *** Eina
> Magic Check Failed !!! Input handle pointer is NULL.
>
>
> RRR: ... 1 0
> RRR: reconfigure screens due to event...
> RRR: ................. info get!
> RRR: .... out DP-0
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: .... out DP-1
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: .... out DP-2
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: .... out DP-3
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 1
> RRR: ...... modes 0x55947b248d90
> RRR: 'DP-3' 0 0 3840x2160
> RRR: .... out DP-4
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 1
> RRR: ...... modes 0x55947a215720
> RRR: 'DP-4' 0 0 3840x2160
> RRR: .... out DP-5
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: .... out DP-6
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: check fingerprint...
> RRR: ... fingerprint says 0
> RRR: screens lists 7 -> 7
> RRR: --------
> RRR: --------
> RRR: --------
> RRR: screens 2 -> 2
> RRR: --------
> RRR: skip change because of single laptop lid
> RRR: skip change because of single laptop lid
> RRR: skip change because of single laptop lid
> RRR: skip change because of single laptop lid
> RRR: skip change because of single laptop lid
> RRR: skip change because of single laptop lid
> RRR: skip change because of single laptop lid
> RRR: --------
> RRR: changed = 0
> --------------------------------------------------
> RRR: out id=DP-0/: connected=0
> RRR: out id=DP-1/: connected=0
> RRR: out id=DP-2/: connected=0
> RRR: out
> id=DP-3/00ffffffffffff00047210043f8c4073221b0104b54728783e88e1a8554da0250e5054bfef80714f8140818081c09500b300d1c001014dd000a0f0703e8030203500c48f2100001a000000fd001d4c1f873c000a202020202020000000fc0042333236484b0a202020202020000000ff0054314e4141303033383532320a01f3020320f15390050403020716011f121314201511065d5e5f2309070783010000023a801871382d40582c4500c48f2100001f011d8018711c1620582c2500c48f2100009f011d007251d01e206e285500c48f2100001f04740030f2705a80b0588a00c48f2100001b565e00a0a0a0295030203500c48f2100001b000000000051:
> connected=1 RRR: check lid for DP-3... RRR: out
> id=DP-4/00ffffffffffff0034a9a29600000000ff190104a526157802b651a85242ac2709505400000001010101010101010101010101010101c3d100baf0703f80a20888007ed71000001ec3d100baf0703f80a20888007ed71000001e000000fd003a3e818a38010a202020202020000000fe005656583137503035314a30300a00dc:
> connected=1 RRR: check lid for DP-4... RRR: out id=DP-5/: connected=0
> RRR: out id=DP-6/: connected=0
> --------------------------------------------------
> RRR: lids=0 closed=0 ext=2
> RRR: change = 0
> RRR: ................. info get!
> RRR: .... out DP-0
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: .... out DP-1
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: .... out DP-2
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: .... out DP-3
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 1
> RRR: ...... modes 0x55947a0ab7f0
> RRR: 'DP-3' 0 0 3840x2160
> RRR: .... out DP-4
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 1
> RRR: ...... modes 0x559479d83210
> RRR: 'DP-4' 0 0 3840x2160
> RRR: .... out DP-5
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR: .... out DP-6
> RRR: ...... lid_closed = 0 (0 && 0)
> RRR: ...... connected 0
> RRR: ...... modes (nil)
> RRR:-------------------------------- 2
> RRR: 'DP-3': 0 0 3840x2160
> RRR: 'DP-4': 0 0 3840x2160
> RRR: result max: 3840x2160
> xinerama screen 0 0 3840x2160
> xinerama setup............... 1 (nil)
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ match screens 0x55947a1dff80[0] = 0 0 3840x2160 -- 0
> @ matches existing zone 0x55947979b040
> move resize 0 0 -65536x-65536 -> 0 0 3840x2160
> @@@ FOUND ZONE 0 0 [0x55947979b040]
> @@@ SCREENS: 0 0 | 0 0 3840x2160
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ match screens 0x55947a1dff80[0] = 0 0 3840x2160 -- 0
> @ matches existing zone 0x55947979b040
> move resize 0 0 3840x2160 -> 0 0 3840x2160
> ERR<20124>:edje ../src/lib/edje/edje_util.c:3845
> _efl_canvas_layout_efl_layout_calc_calc_size_min()
> file /usr/share/elementary/themes/default.edj, group e/modules/battery/main
> has a non-fixed part 'top'. Adding 'fixed: 1 1;' to source EDC may help.
> Continuing discarding faulty part. RRR: New unconfigured screen on DP-0 RRR:
> New unconfigured screen on DP-1 RRR: New unconfigured screen on DP-2 RRR: New
> unconfigured screen on DP-3 RRR: New unconfigured screen on DP-4 RRR: New
> unconfigured screen on DP-5 RRR: New unconfigured screen on DP-6
>
> By then, all my windows are banished in a corner again.
>
> Does that help?
well the fact you are on 0.23 doesn't help as i fixed at least one issue to do
with randr and e missing screen changes entirely and 0.24 is out. so i'm not
likely going to try debug an older release of e unless you're willing to
actually hack on the code and add appropriate debug, find the issue and
identify it's the same one in the current release and maybe send a patch... :)
i can easily turn off one of my monitors and over displayport this means it
looks disconnected and then reconfigures screens. i've just tested both
side-by-side and clone here and turned my right screen on and off like ever
second or so now 5-10 times. if i keep turning it on and off fast enough
nothing happens (screen is not faded in or out - that's the sign e's randr is
about to reconfigure). if i let it sit for a second or so then e responds and
does its thing.
e does have a delay timer to at 1 second for things to settle on changes in
screens to precisely avoid the "a bunch of screens plug/unplug at about the
same time" (plugging into a dock or unplugging for example, or a dodgey
connector that disconnects and then reconnects quickly), so it already has code
to deal with this situation. as long as it sees changes happening within 1
second of each-other it'll keep deferring doing anything about it until that
stops. if a screen unplugs and plugs for like 0.5 sec it should ignore it then.
like any change events from x's randr events call
e_randr2_screen_refresh_queue() and that does:
// delay handling of screen shances as they can come in in a series over
// time and thus we can batch up responding to them by waiting 1.0 sec
if (_screen_delay_timer)
ecore_timer_loop_reset(_screen_delay_timer);
else
_screen_delay_timer = ecore_timer_loop_add(1.0, _cb_screen_change_delay,
NULL);
(nice typo in comments :))
so whatever is happening your logs aren't clear to me at this point. as usual
"update" is the first order of the day. i just spent a few weeks working with
some other people only to discover they were on a 1year old tree of another
software stack in android and after 2 weeks of chasing a "bug" they thought
might be in the kernel driver (i was picking through it to figure out if it was
and threw in some debugging to find out and ruled it out) it turned out that
simply the bug was already fixed a while ago in "master" in a userspace
component and we wasted multiple peoples full time jobs for a few weeks and a
whole bunch of managers stressing out over "not up to date" tendencies. it
happens far too often, so i encourage you to update first. perhaps just
one-time set up the ability to git clone and build efl and e so i can throw
patches at you and say "try this" where it may add logging or debug or have a
try at a fix. without that i'm left staring back in time and going "well it
works perfectly here - i can't reproduce trying to mimic your setup". :)
> Thanks,
> Marc
> --
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
>
> Home page: http://marc.merlins.org/
>
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
Carsten Haitzler - ras...@rasterman.com
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
