After upgrading DirectFB to version 1.1.0 and revdep-rebuilding everything, qingy-0.9.6-r1 gets broken. The problem is that the qingy login screen gets compressed to half the screen width and the colors get messed up. The mouse pointer also doesn't work. Apart from that, I can login correctly.
Created attachment 139293 [details] A picture of the login screen Sorry for the poor quality, but I guess it's descriptive enough ;)
I was able to reproduce your issue... I'm currently investigating.
Unfortunately this issue is not qingy related, but depends on the version of DirectFB and framebuffer driver of choice. It worked for me with ati fb, had the issue with vesa, but there is nothing that can be done in qingy to fix it...
For your interest... I had an issue like yours once when framebuffer was set up at 16 bits color, but DirectFB tried to use it as 32 bits... fixed DirectFB config and all went ok.
Am I right, that the mouse pointer problem is only caused by the DirectFB version? I cannot believe, that this problem is caused by the framebuffer driver (uvesafb) or the color depth. Or do I understand something wrong?
(In reply to comment #5) > Am I right, that the mouse pointer problem is only caused by the DirectFB > version? I cannot believe, that this problem is caused by the framebuffer driver > (uvesafb) or the color depth. > Or do I understand something wrong? Ah, yes... I was writing about graphics issues here! About mouse pointer not working, this is probable a DirectFB (mis)configuration issue, too. What kind(d) of mouse device(s) do you have attached to your system? These days it usually all boils down to PS/2 or USB devices. To support both, make sure to emerge DirectFB like this: INPUT_DEVICES="keyboard linuxinput ps2mouse" emerge DirectFB For further info, have a look at http://qingy.sourceforge.net/faq.php There is a Gentoo section there...
I read the site and know the INPUT_DEVICES hint, but when I used emerge I do not see the input_devices_... stuff at the USE flags. So I thought this was outdated. I had have a look at the ebuild know and saw that it uses INPUT_DEVICES, but in a (I believe) unusual way. /usr/portage/dev-libs/DirectFB/DirectFB-1.1.1.ebuild: IUSE_VIDEO_CARDS="ati128 cle266 cyber5k i810 i830 mach64 matrox neomagic none nsc nvidia radeon savage sis315 tdfx unichrome" IUSE_INPUT_DEVICES="dbox2remote elo-input gunze h3600_ts joystick keyboard dreamboxremote linuxinput lirc mutouch none permount ps2mouse serialmouse sonypijogdial wm97xx" IUSE="debug fbcon fusion gif jpeg mmx png sdl sse sysfs truetype v4l v4l2 X zlib" /usr/portage/x11-base/xorg-server/xorg-server-1.4.0.90-r3.ebuild: IUSE_INPUT_DEVICES="..." IUSE_VIDEO_CARDS="..." IUSE="${IUSE_VIDEO_CARDS} ${IUSE_INPUT_DEVICES} ${IUSE_SERVERS} 3dfx ..." So in the second one I will the it as 'USE flags'. But that should be another 'bug/improvement'. I will try a rebuild...
