dan
Member
Posts: 4
Likes: 1
|
Post by dan on Dec 4, 2021 20:33:19 GMT
I wish to not have to use sudo for every command and write a password for everything. It is also trivial to move stuff moving files, wallpaper or changing the configuration of any program manually. I know the security risks involved but I still insist on being root always. Currently I cannot access Moshka as root because whenever I do so nothing except the wallpaper appears and the screen flickers. PLEASE GUIDE ME ON HOW I SOLVE THIS ISSUE!! BTW IM USING SLIM without autologin
|
|
|
Post by ylee on Dec 4, 2021 22:45:48 GMT
Hello Dan, In case you do not know who I am I am the lead developer for Bodhi and one of the two developers that work on Moksha. I personally do not support logging in as root, on forums discord or elsewhere. But I can give you some clues as to what is going on if you try to run Moksha as root. Simply put Moksha fails to initialize and gets caught in an infinite loop. I also see a number of other issues going on. ecore, efreet and eina (all components of the Enlightenment Foundation Library) are having problems initializing but in the end appear to do so ... without further investigation, I can not be really sure tho. dbus or at least the library moksha uses for the dbus interface is failing completely. And Moksha's mixer module which handles pulseaudio is completely failing to initialize. The mixer module is caught in an infinite loop most likely due to pulse audio not working as root user. But even if one disables this module by editing root users config files for moksha, Moksha is still caught in an infinite loop. You are not going to succeed logging as root user and running moksha without configuring dbus and pulseaudio to work running as root and or modifying the moksha source code. Moksha has never been tested running as root nor do I really see a need for it to. This falls in the category this is probably a bug but one I am going to put no time into fixing. My recommendation is do not do it. Our other developer may feel differently, I do not know (he is probably asleep now anyway). If a change in moksha's code can fix this I would accept a patch or pull request to fix it. I wish to not have to use sudo for every command and write a password for everything ... I configure sudo to accept common and safe commands without the need for a password. sudo apt install ... for example on my machine does not prompt for a password. EDIT: I managed to get moksha running as root. Not posting how to do so as this is dangerous and not something one should do. If one knows enough about linux to do it then I can not stop you but I certainly do not have to help you figure out how to do it.
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Dec 5, 2021 0:03:58 GMT
I wish to not have to use sudo for every command and write a password for everything. Dont use sudo for every command. That is worse than logging in as root. Only use sudo when it is absolutely necessary, i.e. when doing things that you cannot do yourself and need to be admin. Otherwise you'll end up causing yourself problems, apps not working right etc, not just security issues.
But you can disable password requirement for sudo. Or increase the timeout before it's asked for again.
|
|
batden
Member
Posts: 55
Likes: 74
|
Post by batden on Dec 5, 2021 6:38:28 GMT
|
|
dan
Member
Posts: 4
Likes: 1
|
Post by dan on Dec 5, 2021 8:46:56 GMT
Thanks for the help Is it possible for every elevated command to run using sudo without me having to type it
|
|
enigma9o7
Crew Member
Posts: 1,427
Likes: 1,336
|
Post by enigma9o7 on Dec 5, 2021 14:36:59 GMT
You dont want to do that. It's not just security risks (which I agree arent much of a big deal on home computer with nothing special on it), it will cause you permission issues. You will end up breaking applications. For example config and other files could get written as root, and normal user cannot modify them later. Just dont do it. Dont use sudo unless you have to. The only time you ever have to use it is if you are editing things outside your home folder. Other than installing new software for all users, there is not many reasons to do that; you can use local copies (in .local) of lotsa things that take priority. The reason sudo exists is so you are well aware when you're not doing something as yourself, and think twice before doing it.
But I imagine that's possible with some .bashrc trickery. Just don't do it tho.
|
|