0.9.1 was released 2006-08-24. The summurized open issue has been fixed 2006-09-20. But 0.9.2 isn't released ATM (2006-10-09). http://svn.sourceforge.net/viewvc/qingy/trunk/qingy/ChangeLog?revision=396&view=markup I think that b0rked release needs to back port or p.mask.
I have a workaround for this problem in the meanwhile. If you don't use the "-n" switch for qingy, it doesn't hang. But you don't get the shutdown messages.. 0.9.2 is desperately wanted :)
The reason why qingy 0.9.2 isn't out yet is that the shutdown issue isn't totally fixed, yet. I'm working on it ;-)
Renato: Thank your info. I knew another workaround is, "re-login console then do shutdown or reboot". :) Michele: Good to hear, so thank your effort. I guess someone ready to be victim^H^H^H^H^H^Htester! :P
Just added qingy 0.9.2 ebuild to Portage. It should solve the hang on DirectFB shutdown issue...
Michele: I've tried to emerge 0.9.2. But there is no qingy-gentoo-theme.tar.bz2. So, that emerging got failure at fetch phase. Could you mind to check whether it's mirror sync problem or not?
Is *is* a mirror sync issue, due to the fact that I forgot to upload it to the master server ;-) Fixed, but now it will take a few hours for the file to spread... BTW, make sure you don't enable openssl as crypto library (not enabled by default for Gentoo anyway), otherwise it won't compile :-/
(In reply to comment #6) > Is *is* a mirror sync issue, due to the fact that I forgot to upload it to the > master server ;-) Fixed, but now it will take a few hours for the file to > spread... OK, now thre're no fetching issue. And I confirmed 0.9.2 has no shutdown issue, at leaset for me. Thank again for your effort. :) > BTW, make sure you don't enable openssl as crypto library (not enabled by > default for Gentoo anyway), otherwise it won't compile :-/ Yeah, I confirmed it got failure when compiling w/ USE=crypto_openssl. So, there's no choice to enable libgcrypt instead of OpenSSL. And then just courious, the upstream would drop OpenSSL? Or just it has a breakage ATM?
> OK, now thre're no fetching issue. Good > And I confirmed 0.9.2 has no shutdown issue, at leaset for me. > Thank again for your effort. :) Finally! :-) > So, there's no choice to enable libgcrypt instead of OpenSSL. I assume you meant to say 'there's no choice but to enable libgcrypt instead of OpenSSL' here. Partially correct: you can either use libgcrypt or no encryption at all... > And then just courious, the upstream would drop OpenSSL? > Or just it has a breakage ATM? Uh? If you are asking whether qingy will drop openssl support, the answer is: probably not. After fixing the compilation issue (which is trivial), qingy still fails when linked to openssl non-statically, and the issue is subtle, I haven't nailed it down, yet...
