I'm not sure if any of this is something I should maybe report on
trac.enlightenment.org? or if it's strictly a snowlinux only thing???
Anyway I installed the SnowLinux 3.1 E17 respin iso on my laptop...
It was running pretty good. I guess the most annoying thing was an occasional
SEGV'd pop-up asking me to press F1... {Which always seemed to work.}
The only time it was really aggravating was after using apt-get to install
or remove something that altered the application menu. Then the SEGV'd
pop-up would happen the next few times I opened the menu. But after that
it was all good again. And remained so even after rebooting etc...
But yesterday, after I did {in a root shell}:
apt-get update
apt-get upgrade
E17 started giving me several SEGV'd pop-ups every time I run startx...
If I do a ctrl+alt+F1 to look at tty1, I see several of these:
- - - - - - - - -< s n i p >- - - - - - - - - -
CRI<>lib/eo/eo.c:430 *** Eina Magic Check Failed !!!
Input handle pointer is NULL !
*** NAUGHTY PROGRAMMER!!!
*** SPANK SPANK SPANK!!!
*** Now go fix your code. Tut tut tut!
- - - - - - - - -< s n i p >- - - - - - - - - -
and occasionally a couple of these:
- - - - - - - - -< s n i p >- - - - - - - - - -
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x1c0000e
- - - - - - - - -< s n i p >- - - - - - - - - -
When I logout of my {startx} E17 session, I get this:
- - - - - - - - -< s n i p >- - - - - - - - - -
E17: Begin Shutdown Procedure!
xinit: connection to X server lost
waiting for X server to shut down kdeinit4: Fatal IO error: client killed
klauncher: Exiting on signal 15
knotify4: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
kded4: Fatal IO error: client killed
Server terminated successfully (0). Closing log file.
- - - - - - - - -< s n i p >- - - - - - - - - -
At the moment my simplistic ~/.xinitrc consists of:
- - - - - - - - -< s n i p >- - - - - - - - - -
yakuake &
synclient TouchpadOff=2
xrandr -s 3
/opt/e17/bin/enlightenment_start
- - - - - - - - -< s n i p >- - - - - - - - - -
I note that the reason I use xrandr is because for some reason the display
resolution module was unable to properly restore my chosen resolution on login
until I did so. (I still needed to select it in E17 module for it to start
cleanly. Which behavior was described in detail in this Snowlinux forum thread:
http://tinylink.in/Z4J
{Be aware, if you have javascript enabled, there is an advertising pop-up...}
And last but not least the Xorg.0.log (from a session where I simply ran
startx, and waited till E17 finished initializing {hitting F1 for several
SEGV,d pop-ups along the way...} Then after it stopped "SEGV,d"ing, logged
out) can be found here:
http://pastebin.com/riGutEKv
--
JtWdyP
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
