| Summary: | sys-apps/qingy-0.4.1 works with errors under linux kernel 2.6.8 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ioannis Aslanidis (RETIRED) <deathwing00> |
| Component: | [OLD] Core system | Assignee: | Michele Noberasco (RETIRED) <s4t4n> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Ioannis Aslanidis (RETIRED)
2004-08-15 03:20:57 UTC
- Username/password text is not shown. This generally happens if you emerge freetype (which DirectFB depends upon for TTF font support) with the "bindist" USE flag. Try re-emerging freetype with USE="-bindist", and re-emerging DirectFB after that. Fonts should be visible inside qingy again. - All buttons restart qingy and do nothing else. - Cannot login, either it is a correct or an erroneous login, qingy simply restarts. This is unfortunately still a DirectFB bug. Apparently it crashes (the app) when shutting down its graphic mode. And qingy shuts down the graphic when (sigh) it logs in the user, as well as when shutting down / rebooting the machine. I wish I never used DirectFB, but it wasn't this borked at the time... Michele... what does exactly the bindist flag? Should I disable it globally or what? The bindist flag is the one that tells Portage to use a precompiled bynary version of the package you are emerging (if it is available for that package, of course), instead of compiling it directly. freetype has a binary version available, but that doesn't support well TTF fonts properly (at least with DirectFB). If you disable it globally you will end up compiling everything from source. BTW, try 'emerge ufed' and you will get a nice (console) tool to manage your USE flags, wether you want to (globally) enable/disable one, or just want to know what a specific one stands for... Yup, I verified that it is DirectFB that crashes the app when shutting down from its graphic mode. If you don't use the '-n' cmd line arg in qingy (the one that closes DirectFB mode before stopping/restarting your system), you will be able to shut down normally. Thank you very much Michele. Uhm, tonight I got seriously pissed up with this 'DirectFB crash on shutdown issue', so I thought that if I cannot prevent it, maybe I can circumvent it, so an evil evil idea came to my mind (satanic cackling with mad laughter follows): I split qingy into two executables, one with the interface and one that does the actual login. This way it does not matter anymore how the interface dies. because it communicates username, password and session to start to the other via a pipe. As a result of this I have successfully logged in with qingy using gentoo-dev-sources-2.6.8 and vanilla-sources-2.6.8. As a side result, the qingy instance that logs you in will use about 2.5M of RAM against the 40M of the old solution (this because DirectFB leaves a lot of used RAM even after shutting down its graphic mode, but that gets cleaned when the qingy-interface dies). This looks like a big improvement to me, worth a new major release of qingy. Also, it paves the way for support of other graphic toolkits in qingy (bare framebuffer, SVGAlib, maybe others): each interface will have its own executable, and the main qingy will just have to launch it depending on user preferences... Unfortunately you cannot test this code yet, it is still too dirty / hacked together for me to even put it on CVS. I'll post a follow up when it is... Come on Michele... let me taste that piece of code! :P gj btw Have a little more patience ;-) The changes I'm doing are big, and there are still a number of bugs and very rough edges to smooth down... That said, it is already working well on my machine, thus I uploaded it to qingy CVS repository... OK, released qingy version 0.5.0 which addresses the 2.6.8 kernel issues. Ebuild in Portage and already marked stable for x86. |