Quoting Ottone Maurizio Grasso ([EMAIL PROTECTED]):
> Some assorted questions:
> How can I use XDirectFB in rootless mode ? What's a possible user
> scenario? I read something about Darwin and understood that context ...
> but under Linux ? Do you mean that it is possible to have two working X
> servers at the same moment: one rootless and one with a root window ?
> BTW: I managed to use XDirectFB as my main X server and played with the
> opacity factor, but didn't find any rootless option: where is it?
Currently XDirectFB runs only in rootless mode and therefore doesn't
have an option for rootless mode. Rootless also means that the X server
doesn't use DirectFB in fullscreen mode but creates DirectFB windows.
After starting XDirectFB you will see the normal DirectFB background.
You can set a background image in your '/etc/directfbrc' or '~/.directfbrc':
bg-image = file
XDirectFB is meant to be a backward compatibility once the multi application
core is stable enough. Currently the only advantage of XDirectFB is the
window opacity stuff.
> Another thing that is puzzling me is: how can I recover the use of my
> terminal when a DirectFB app exits leaving behind a locked screen? In
> the case of XDirectFB (using Gnome as Desktop Manager), whenever I
> logout the server remains active. I can kill it with a remote shell and
> restart any other X application afterwards but the local terminal stays
> unusable unless restarted in X again. The problem is a more general one
> what manual operation should I do to get a text fb terminal back?
This is indeed a general and ugly problem. The best way to quit XDirectFB
is to press "Ctrl+Alt+Backspace". In the general case that a terminal is
locked you can use "Alt+SysRQ+K" to kill all apps running on this terminal.
After that the keyboard is in unraw mode so you can switch consoles again.
To only unraw the keyboard you can press "Alt+SysRQ+R".
See linux/Documentation/sysrq.txt for more information on SysRQ keys.
Once you are logged in over network and killed a DirectFB app you can run
"chvt 1" to switch to tty1.
> Third thing(kind of minor): as of 0.9.9 'm not able to use the avi
> provider anymore: it dies with a segmentation fault: I'm nearly sure
> that none of 0.9.8 libraries has been left behind. I'll try to debug the
> app and see what happens, but I'm quite a beginner at this and I don't
> know if I'll solve this, any hint anyone? Something curious that still
> nags me is the fact that whenever I launch a DirectFB 0.9.9 app and
> after its termination start a classic X server (4.1.x) this results
> unusable because it receives all sorts of sprious events. So I have to
> kill it and reboot the machine before being able to use X again. This
> did not happen with 0.9.8. has someone experienced the same behaviour ?
> could it be related tho the avi problem and maybe a symptom that I DID
> leave a 0.9.8 library behind? (even if I tend to exclude this ...)
I also recognized segfaults caused by the avifile provider,
but can't remember if I got it working again. I think the problem is
related to the changes that were made to support static linking of
DirectFB apps with the main library and drivers/providers.
You may have a look at 'src/interface_implementation.h'.
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
convergence integrated media GmbH
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-users" as subject.
