On Thu, 15 Nov 2012 15:05:51 +1030 Simon Lees <si...@simotek.net> said:

> Hi all,
> 
> I'll make a brief comment on this  not that it means much because i don't
> have the time to implement my soln and you are the ones that would have to
> deal with it. At work where i have a old OS on a distro i don't package for
> or care about i build from source and use the forcasts and photo's module,
> i haven't looked at the code for either so i have no idea what state they
> are in but they both work for me on multiple systems so oneday i may
> consider packaging them. I am yet to see the current waring as i can't
> upgrade atm but if it was a once off with a checkbox saying don't show

it is.

> again i would be happy enough if it came up every time like some of the
> compositing errors i would not be, and i wouldn't package these modules in
> a official repository.

i'd suggest not packaging them anyway.

> My prefered solution which probably isn't yours as it is slightly more work
> for you would be to only show this popup in the segfault recovery popup if
> 3rd party modules are loaded. "Something bad has happened, Enlightenment

people don't read it - or only a few do. they just try and get rid of it
asap. :) it also hapens to tell you your e is tainted with 3rd party modules
here, but it tells u at the time the module is loaded too so you know which one
it is.

> has crashed. You are running 3rd Party modules this may be the cause". I
> would also get enlightenment to create a "diagnostics file" for debugging
> which would contain a list of loaded modules the compositor in use,

this becomes way too invovled as the crash dialog is insanely thin and minimal
not even using efl... it goes to x directly just in case its a core bug in efl
somewhere. it knows very little about e at that point and giving it all this
data is a huge amount of work and thats why we warn in advance - same way the
kernel does in its output (dmesg etc.) when tainting it with proprietary
modules.

> graphics driver potentially the screen layout and any other info that can
> be gathered at startup and make it compolsory for bug reports to be
> accompanied by this file. This would give you more useful info that a
> inexperienced user may not be able to pin down but would be more effort to
> start up.
> 
> Cheers,
> Simon
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to