Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to get an application (Quake2) to run without a window manager.
Curiously, the way it's built now, I can run it like:
startx ./quake2
and the video and sound works, but I get no mouse or keyboard events.
On the same system, I've also compiled from source QuakeSpasm and DarkPlaces SDL, which, when loaded the same way, work perfectly.
These were all built on the same system, with the same drivers, same libraries, same compiler, one right after another. The results are consistent from day to day.
this leads me to think there must be some hook in the code itself that's having an effect on how X is handing control over to the application at launch time.
I'm at the point of reading through the source code of both QuakeSpasm and DarkPlaces (several other applications work perfectly too, these are just the most relevant examples) just to see what they do and see if I can graft that behavior onto Quake 2....but I would hope there's a "right way" to do it, for which there might just be documentation.
That is an interesting read, for sure. Ear marking that for future use, but I think I know most of what's already in it.
Quote:
Originally Posted by dugan
Maybe give Yamagi Quake2, vkQuake2, or another source port a try?
I'm actually working primarily with Yamagi Quake 2 and have spoken with Yamagi about exactly this. He and the other dev were as confused as I am, so my hope was to fork YQ2 and try to sift out whatever weirdness is causing this issue.
I've not heard of vkQuake2, I'll have to give that a shot.
All of this has me wondering if there's not anything special that should be done in the code to make a program work without a window manager. Many applications seem to do it by accident!
With only the utmost respect for Yamagi's work, I wonder if something is being done /wrong/ as opposed to not at all, like I had thought.
Maybe there's not "a way" to write or build applications that work without a window manager...I'm slowly getting the impression that's simply how they should work by default provided they're linked against Xorg and OpenGL where necessary.
I'd be curious to hear from an Xorg dev....or maybe there's an Xorg forum I should visit?
Thanks again for the suggestions and responses thus far!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.