antiX / MX LinuxThis forum is for the discussion of antiX and MX Linux.
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've just installed the latest AntiX on a Samsung laptop. It runs icewm as its desktop and the desktop menu is using geany as its default editor. When I click on it, a window flashes up and immediately disappears. There's nothing wrong with geany as such: you can run it from a terminal. Other menu options such as "Default browser" work normally.
The menu runs a bash script called desktop-defaults-run. I studied this and found that the operative command is: gksu -u `whoami` geany. When I typed this in a terminal, it crashed in the same way. Yet "gksu -u hazel geany" ran normally.
It gets odder. "gksu -u `whoami` geany &" works. And once I had run the command in this form, "gksu -u `whoami` geany" also worked. But when I ran it from the menu, it crashed again and no longer worked from a terminal either. In other words, the crashing behaviour can be switched on and off.
I can only assume that there is some kind of weird interaction between whoami, geany and bash's job control system.
I've just installed the latest AntiX on a Samsung laptop. It runs icewm as its desktop and the desktop menu is using geany as its default editor. When I click on it, a window flashes up and immediately disappears. There's nothing wrong with geany as such: you can run it from a terminal. Other menu options such as "Default browser" work normally.
The menu runs a bash script called desktop-defaults-run. I studied this and found that the operative command is: gksu -u `whoami` geany. When I typed this in a terminal, it crashed in the same way. Yet "gksu -u hazel geany" ran normally.
It gets odder. "gksu -u `whoami` geany &" works. And once I had run the command in this form, "gksu -u `whoami` geany" also worked. But when I ran it from the menu, it crashed again and no longer worked from a terminal either. In other words, the crashing behaviour can be switched on and off.
I can only assume that there is some kind of weird interaction between whoami, geany and bash's job control system.
wrt: "flashing", Any clipboard helpers installed?
Have you tried a new user profile and tested as the new user?
I didn't think of running the entire script from the terminal. I did that just now (desktop-defaults-run -te) and it worked. It output the word "Geany" and then launched the application successfully. And then I triggered it from the menu and that worked too! Curiouser and curiouser.
So I logged out, logged in again and then tried from the menu. Still works. So now I have an unreproducible bug.
Keruskerfuerst, I don't know what you mean by "start geany". I've never heard of a "start" command. I certainly don't have one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.