Raster, first I'd like to apologize and say I'm sorry as it seems you took at least part of this critique personally. I didn't realize you are practically the only one working on this so I think I incorrectly assumed this thing was a "corporate decision" of sorts and reading back I realize I worded this much more strongly than I should have. Didn't even check who was replying to me or who the OP was... Also realized I'm chasing the master branch so I'm very much getting a snapshot of work in progress, and maybe even one that is bad at representing what it will eventually look/function like. I think trying to get work done in this frigging heat and also having to unexpectedly deal with this on my workstations didn't help. ;)

Maybe it'll grow on me, and some of my gripes are probably just bugs or unfinished parts that haven't been worked out yet. Still feels a bit alienating though.

I just updated EFL and Enlightenment for the first time in a long time and I'm sorry but this change hit me in the face like a sledgehammer. It's a manifestation of everything wrong with modern design and this flat trend.

I now have this issue as well on several machines, or it just never blanks.
Usually it works once after locking the screen then no blanking until I restart E completely.

Now I got the (or at least a) Phpstorm crash. I think it was about to pop up a contextual menu for autocompletion etc when it crashed. Recovering works fine and it's been a long while since I ended up in one of those crash loops.

Looks like the same issue I encountered on https://aur.archlinux.org/packages/enlightenment-git, good to know it's not specific to my system. :)

Thanks! A rebuild of EFL+E made it much more stable when resizing.

I am not entirely sure this is related, but I just ended up in a crashloop when opening a couple of windows and couldn't get out without logging out with F12.

Recreated the issue again with the configuration mentioned above, got no parameters in the log again. After a reboot I also had massive performance issues (<10 fps with just E running) and even a dimming or slight flickering of the screen (possibly due to G-Sync being enabled, but I've never seen it act like this until this week).

I just tried changing the DEBUG_ version of the flags and modified OPTIONS to have "!strip" and "debug". Doing this over SSH from work to save some time when I get home and I managed to capture when it printed out the configuration.

CPPFLAGS......: -D_FORTIFY_SOURCE=2
CFLAGS........: -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -g3 -O0 -fvar-tracking-assignments -fvisibility=hidden -fpie
CXXFLAGS......: -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -g3 -O0 -fvar-tracking-assignments -fvisibility=hidden -fPIC -DPIC
LDFLAGS.......: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fPIC -DPIC -pie -rdynamic
EFLJS_CXXFLAGS:

Seems those flags do get appended to the regular flags now. Setting flags multiple times should only use the last variant, right?

Built all AUR packages with makepkg, usually via pacaur but have done it straight up too for EFL & Enlightenment just to be sure the generated packages were no different. Did indeed also install the -debug packages and make sure they are shown as the correct version after each update.
Yes, will try modifying /etc/makepkg.conf directly and rebuild. Thanks for the help!

I'm using the efl-git and enlightenment-git AUR packacages, which specify options=(debug), which should be pulling in these flags from my makepkg.conf

DEBUG_CFLAGS="-g -fvar-tracking-assignments"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"

I'm using the default OPTIONS line in makepkg.conf which does include strip so I have to install the debug package separately:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !optipng !upx !debug)

Sorry guys but I'm still having issues related to this. Updated my machine and re-built all the packages from here straight out of git a few moments ago.

I can confirm reverting 3ee5a0 fixes the issue for me too.

.21.99.2679

I can confirm this issue began some time since 23 July 10pm as that was the last time I updated my home machine. Only updated EFL, Enlightenment and Terminology at home this morning and now I have the same problem there.

I think so. I have not noticed it until after the update today at work. Will see if I can reproduce at home later today.

In T5470#87663, @simotek wrote:

In T5470#87631, @ApB wrote:

On wayland you cant unlock E after it locks. Fun stuff ?

Well that sounds like a different bug that probably deserves its own ticket.

I tried two of the Valgrind methods outlined on https://www.enlightenment.org/debugging/enlightenment_debugging#Valgrind but didn't get either to work exactly as listed.
Xephyr got some error which I think was related to OpenGL (sorry, didn't note exactly what it was as I'm running on the proprietary nVidia drivers and simply assumed it came down to that).

I updated from the repos today so that would be included, yes. But it's possible it mitigated the issue as I've found it slightly more difficult to reproduce since I originally discovered the crash (/probably months ago) but hadn't yet connected it to the bell or anything to do with sound as I didn't have the volume up at the time.

Been a slow morning so I decided to mess with this thing a bit. :)

Sure, I'll take a look at getting one when I'm back home.
Currently at work where I have pretty much the same setup except for any debug stuff.

Turns out I'm an idiot.

@ProhtMeyhet No offense taken. I hope I didn't sound too whiny about this. Yes, it's basically just about not expecting my CPUs to run on full throttle on idle.
I'm not thinking about this a bug report, just a request for information about what I could try to do about it. I completely understand the point @ProhtMeyhet is making and I usually think unused hardware is basically wasted hardware If you say it's a non-issue, I'll just accept it. The rigs I've got have good coolers so their idle temps are just about 30-40C anyway and that shouldn't hurt at all even when running 24/7.

Thank you so much @jpeg!
This fixed the black windows and got rid of the performance issues I had because I couldn't use pixmaps.

http://selenium-release.storage.googleapis.com/2.53/selenium-server-standalone-2.53.0.jar

I think always using at least an initial HEAD request would be convenient anyway. Accidentally hovered the URL to a .jar file (~20MB) and it made the entire desktop (not the cursor) hang until I restarted Enlightenment.
Happens every time I hover it. :/

@zmike I think that'd work. Maybe add a Tutorial/Hints button in the Terminology Controls section with that information?

If there was a quick way to toggle Teamwork quickly, that'd be fine. I think my main problem with this was that I at first didn't understand what was happening and why the links were already expired when I clicked on them. There was no indication that Teamwork failed to render a preview, or that it even tried to do so. (Not one that I could notice anyway.)
Maybe if a tooltip appeared with the text "Teamwork opening preview..." (and then one with "No preview available" which fades out after a few seconds if I still hover it) I would have immediately understood why the link was unusable after that.

If you mean a one-time-login URL, here's one I just generated for a Drupal site: http://example.com/user/reset/1/1463227991/eEHUNYEbRl5ZlEHEVGMfM2ocVX1-IR8nDXjIbUiye7A/login.

Just want to add that I now get the completely black windows (with visible decorations) on my home computer after removing the nVidia 470 GPU and putting in an nVidia 970 instead, as long as OpenGL rendering with pixmaps is enabled I can't use any applications. I'm using the, now stable, 364.19 driver both at home and work since the libpthread crash is fixed.

@zmike I no longer have this issue. Not sure when it stopped being a problem as I upgraded both the nvidia drivers and Enlightenment several times last month and windows currently maximize correctly.

@splurben Did you try the workaround I used?
If you've enabled hardware compositing and now can't access the settings then before starting X, log out and add E_COMP_ENGINE=sw to /etc/environment. Then log into E, go to Settings->Composite->Advanced->Rendering and disable "Texture from pixmap". ('Ive got swapping method set to Auto, don't know if it matters). Then log out, remove the environment variable and log back in with HW rendering enabled and see if it works.

I have this issue with all windows, including Chromium (with system title bar and borders), Terminology and everything else I can think of when maximizing them.

I was able to make HW rendering usable (still a few black dialogs, but they re-render when poked around in or resized) by disabling "Texture from pixmaps" in Composite Settings. (While I was still running in SW mode - forced by the environment variable - or that dialog would also be black.

Updated my home machine today. Black windows with the HW renderer there too now.
Launching Everything just gives a black window I can't get to render correctly at all, but Chromium works after a resize. Window decorations appear to be normal, at least in Terminology, but I can't get Terminology to render its contents by resizing it.

Even with SW rendering the automatic "new updates available" dialog in Steam is black and there's no way to close it or make the contents appear. The dialog works fine if manually launched from the "check for Steam client updates" menu item.

Was looking through the logs and noticed the nVidia warning: "NVRM: Your system is not currently configured to drive a VGA console..." when I realized that the work computer, which has the black/transparent windows issues, is booting directly to the kernel using EFI.

Thank you for looking into this!
I don't have a good grasp on the various drivers and software layers involved in the rendering process, but if there's a combination of things you want me to try on either machine I'd be happy to do what I can.
The screen setup tool makes much more sense to me now. Maybe add a short help text in the application itself about the priority concept? I didn't immediately recognize it from anywhere else so I guess others may also be confused.

The transparent dithering went away after restarting Chromium but comes back as soon as I toggle using native decorations.

As a side note... How do I ensure my bottom shelf is always on the left monitor? It keeps jumping around depending on which renderer (or perhaps some other setting) I pick...

Ok, I though it tried to be clever and tell image/video/other URLs apart by the file extension (if any) before requesting it (and possibly checking the response headers?). Haven't looked at the source of either Terminology or the Teamwork stuff...

Well, that works, but what if I still want the other previews, image URLs etc?

I was thinking Settings first, since Gadgets are usually "Nice to have" vs Settings being "Need to have".
But if we have an easy to find document explaining the settings that are there so far - the linked document is a great start - I can live with it being initially quirky.