On Fri, 3 Sep 2021 21:04:35 +0900 Florian Schaefer <list...@netego.de> said:

quick - if you unload the ibox module ... does the problem stop? that crash is
inside ibox code - memory it's accessing is bad/wrong - why i don't know. not
more information. like 363 in ibox is:

   if ((ic->ibox->inst->ci->show_preview) &&
(edje_object_part_exists(ic->o_holder, "e.swallow.preview")))

so what is ic? whats is ic->ibox, ic->ibox->inst, ic->ibox->inst->ci ?

if you attach gdb when e crashes and dump these values - i'd know more. maybe.
I actually stopped using ibox a while ago since ibar does both effectively
these days. perhaps it is an ibox bug and i havent seen it as i dont use it. so
try the above, if it goes away - attach gdb

i can say that i dont see the problem here with ibox enabled and on amd + e
(git).

> Dear everyone,
> 
> so I got a new desktop PC at work and the first thing I did, of course, 
> was to install Debian sid and enlightenment-git. ;-)
> 
> The machine has a Nvidia T600 card and this is where troubles probably 
> begin. As I kind of need the graphics performance for CAD I went with 
> the drivers from Nvidia (the stock open source drivers were terribly slow).
> 
> Now what happens is that enlightenment crashes often. Like kind of 
> constantly. I got the impression it happens mostly when several windows 
> are going through their appearance fade-in transition at the same time. 
> Then the "red screen of death" appears and I need to press F1 to 
> continue. With some applications this happens always (Eagle anyone?) 
> with others only sometimes. After the forced restart many windows (e.g. 
> terminology always, firefox sometimes) need to be minimized and 
> uncovered again for their content to display again. Some dialog windows 
> won't even show their content from the beginning and instead just some 
> different portion of the screen. Needless to say that for a machine at 
> work this is not an optimal situation.
> 
> The most pressing issue are of course the crashes. I recompiled 
> everything with debugging symbols and optimization disabled (or at least 
> I thought so, some things seem still to be optimized away) to get some 
> meaningful dumps. One of which I uploaded to pastebin 
> (https://pastebin.com/YWSarC10) hoping that it makes sense to someone.
> 
> I am sure that it is not E that is "at fault" but Nvidia, but for now I 
> need to find a way around this so that I can work without having to 
> reset everything every five minutes. Any ideas?
> 
> Oh, I also tried to disable OpenGL in the compositor settings and 
> choosing the software option. And it still crashes!
> 
> For starters I was hoping that I can just switch off all the window 
> transition-fading eye-candy but I did not understand whether this is 
> possible. Is it?
> 
> Finally, being a desktop system (my first in like 10 years or so) it 
> does not run an acpi daemon. I don't really see any reason to do so. 
> Therefore E also complains on every startup that no acpi daemon can be 
> found. I did not find any compile time or runtime options to disable 
> acpi. Is there a way to silence this error/warning?
> 
> Cheers,
> Florian
> 
> 
> _______________________________________________
> enlightenment-users mailing list
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> 


-- 
------------- 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

Reply via email to