Forum › Forums › Orphaned Posts › antiX-17 “Heather Heyer, Helen Keller” › Problem opening Geany in root from rox-filer *Solved
- This topic has 6 replies, 2 voices, and was last updated Feb 28-7:46 am by sleekmason.
-
AuthorPosts
-
February 27, 2018 at 5:06 pm #7015Member
sleekmason
Geany will not open from a root instance of rox-filer. It matter how it is called. If I use:
[exec] (Rox-filer-ROOT) {/usr/bin/gksu -u root -w /usr/bin/rox-filer}
rox-filer is called with su instead of sudo, but neither allows Geany to be opened. Su to root –> rox-filer from a terminal does the same.No idea if this is a permissions problem, a Geany problem, or a rox-filer problem. any input appreciated.
- This topic was modified 5 years, 2 months ago by sleekmason.
February 27, 2018 at 6:19 pm #7019Anonymous
::First, simplify the exec string and retry:
[exec] (Rox-filer-ROOT) {gksu rox-filer}The implicit behavior of gksu (sans -u) is to authorize as root. IOW, specifying – u root isn’t necessary.
Maybe you intend this to be a “special handling” case? (just rox-filer, just this instance of the in-menu launcher)
If so, I’m at a loss to understand why you expect “su mode” (-w option in your launchstring) will be more suitable.If you want to switch all your “as Root” launchers to “gksu su mode”, check out the manpage for “gksu-properties command”.
Again, I’m at a loss to understand why that change would be appealing.Browse the /root directory, and notice the relative absence of .config files, compared to what you’d find present in your normal user’s home directory.
Regardless of the rox-filer launchstring, you’ll probably want to copy into place ( under /root ) a set of rox config files,
in order to to have a set of pre-populated mimetype / filetype OpenWith handlers.Also, toward troubleshooting, change the execstring from geany to leafpad (or other); rule-out whether the problem is specific to geany.
February 27, 2018 at 7:47 pm #7025Member
sleekmason
::The code was to see if there was something someone would see. Thank you for showing me a better way. Thats why I’m here.
–
–rox-filer from a terminal does the same.
I should also specify that Thunar did not have the same issue if that makes any difference. I really like rox-filer and have become accustomed to it’s ease of use. I’d rather solve this if I can rather than be berated for not having the knowledge you think I should. Callous.
February 27, 2018 at 11:22 pm #7047Anonymous
::Are my posts are being read via GoogleTranslator and getting mangled in translation?
.
Happy Birthday!
.
https://www.youtube.com/watch?v=SiXCZ-Ew0b0
short (1min 3sec) video clip
February 28, 2018 at 3:20 am #7050Member
sleekmason
::If so, I’m at a loss to understand why you expect
and, your double down:
–Again, I’m at a loss to understand why that change would be appealing
These are opinions, not translations, and I’ve been around awhile, even your reply is condescending. I understand intention just fine.
- This reply was modified 5 years, 2 months ago by sleekmason.
February 28, 2018 at 7:38 am #7063Member
sleekmason
::I think Iv’e found the problem.
If I use:
[exec] (Rox-filer-ROOT) {gksu rox-filer}
–
and then close the rox-filer window, . .When I click on it again, i’m not asked for a password, (timeout?) but it opens rox-filer anyway and if I then goto /etc/apt/sources.list.d/debian.list, and try tpo open with Geany I get nothing.If this is indeed a timeout problem with gksu? I would like to change it for single instance. I don’t mind tying my password over again.
February 28, 2018 at 7:46 am #7064Member
sleekmason
::*SOLVED!
Found It!
sudo visudo
–
–
then add to defaults:timestamp_timeout=X
–
where x = time (0) -
AuthorPosts
- You must be logged in to reply to this topic.