On Wed, 17 Apr 2019 10:25:19 +0200 leoutat...@gmx.fr said: > On 4/16/19 7:35 PM, Carsten Haitzler wrote: > > On Tue, 16 Apr 2019 11:25:01 +0200 leoutat...@gmx.fr said: > > > >> On 4/16/19 10:44 AM, Carsten Haitzler (The Rasterman) wrote: > >>> On Fri, 12 Apr 2019 13:58:14 +0200 leoutat...@gmx.fr said: > >>> > >>>> Hi > >>>> I use wayland on two computers. Mouse pointer works normally on first > >>>> computer (laptop) with i915 and/or bumblee/nvidia driver. > >>>> On the secund computer with nvidia quadro pro 600/Nouveau, i can't move > >>>> mouse pointer in wayland session. It works with X. > >>>> [I tried proprietary nvidia driver on this computer, it's worth: i can't > >>>> launch wayland]. > >>>> Archlinux system > >>>> efl-git 1.22.99.61804 > >>>> enlightenment-git 0.22.99.23542 > >>> > >>> is it that you can't move the mouse or all rendering has stopped? like the > >>> clock doesnt even update anymore etc? > >>> > >> Clock doesnt update, i can't move mouse pointer, all desktop seems freezed. > >> Alt+F2, F2, F3 etc, doesnt work. Ctrl+alt+back works to kill e. > >> I checked cpu percent, it's normal. > >> efl-git 1.22.99.61758 > >> enlightenmentgit-0.22.99.22539 > > > > ok. it's stopped rendering... though interestingly vt switch is broken. but > > as ctrl+alt+backspace works - enlightenment is alive processing events > > so... let's just deal with one problem: rendering stopped. why? i did see > > something like this where animation ticks stop. we ask for them from the > > drm driver (ask for frame swap event callbacks). i did add a workaround > > where we requested such an event and it never came. i added a timeout then > > a re-request. this seemed to have fixed it. there was another report that > > some time after beta1 of efl this broke. i was trying to reproduce this and > > the bug that i could reproduce went away. i don't know why. i couldn't > > reproduce it anymore. > > > > if i could know what commit caused this, then i might have an idea of what > > it really could be, but i was unable to reproduce and thus find the commit. > > if you have some luck doing this by maybe picking an older efl revision > > (like v1.22-beta1 tag) and then bisect.. that'd be really helpful. i tired > > this and it just stopped happening... :( > > > efl-1.22b.0beta2.61568 works with nouveau. > efl-git-1.22.99.61758 doesnt work
i have no nvidia cards/systems. i can't test. i can not reproduce on current git master (and haven't been able to for a week or 3). could you git bisect to find a commit? i can't look at 100's commits in detail and know what causes it... :( bisecting is a log(n) number of steps - so maybe for that revision range 7-9 or so steps (rebuilds - ensure you rm all the libe*.so* files between each build in the target lib directory) -- ------------- 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
