|
Post by snugbug on Mar 11, 2022 0:55:01 GMT
Today, I've found something what might be a little bug. Not sure about this, though. If I create a personal app launcher in the settings console, that launcher does in fact appear in ~/.local/share/applications/ and it is working fine, but it isn't listed in the composing window, where I've just created the launcher. Not sure if it is meant to be like that or if it may be a bug.
Don't know if this is important, but that launcher is a screenlayout.sh, because I have a two monitor system and I've made the right monitor, not the left one, to be the main one.
Could it be that it is because that launcher is related to a .sh-file?
|
|
|
Post by snugbug on Mar 16, 2022 9:33:46 GMT
The entry in the composing window of the personal app launcher only appears after rebooting Bodhi. Is it a bug or is it meant to be like that?
|
|
|
Post by thewaiter on Mar 16, 2022 12:36:34 GMT
Yes, it could be a bug. I have seen such a behaviour before. Restarting Moksha with CTRL ALT END always did the trick. Surely we need to solve it...
Stefan
|
|
|
Post by thewaiter on Mar 16, 2022 18:28:14 GMT
I have just tried created a personal launcher for testing purpose. I can see it in "Personal Application Launcher" dialog list as well as in ~/.local/share/applications/. Now it is not easy to reproduce the problem.
Stefan
EDIT: in case you need to start something after boot, it is comfortable to put the commnad line into ~/.e/e/applications/startup/startupcommands file.
|
|