FS#28322 - [mc] wrong location for ini files
Attached to Project:
Community Packages
Opened by Jan Hradek (jan.hradek) - Wednesday, 08 February 2012, 10:52 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 09 February 2012, 15:20 GMT
Opened by Jan Hradek (jan.hradek) - Wednesday, 08 February 2012, 10:52 GMT
Last edited by Alexander F. Rødseth (xyproto) - Thursday, 09 February 2012, 15:20 GMT
|
Details
Description:
MidnightCommander uses the ini location of the logged-in user, instead of the user I "su"-ed into. Additional info: * package version(s): (i686) community/mc 4.8.1-1 - I also tried current mc-git from aur with the same result (propably broken upstream?) * config and/or log files etc.: /etc/mc/ configuration files are untouched, mc's logging facilities are propably non-existent :( Steps to reproduce: * login as a regular user (let's use "foo" as our regular user) * run mc and change configuration, I recommend to change something in the directory hotlist (Ctrl + \) * save your configuration * quit mc (F10) * su (to root) * now run mc in the su enviroment * (now mc reads the configuration of the regular user "foo") * NOTE: you can run 'mc -F' to actually see what data directories mc uses * go to the directory hotlist (Ctrl + \), you should see the hotlist of the logged-in user "foo", not the one you "su"d into * also if you try to save the configuration, mc clearly states where the config is written - to the user logged in "foo" * this is reproducible the other way too: login as root and su to some regular user NOTES: * this bug has somewhat ugly side effect: if you save the configuration in the su environment then the ownership and the contents of "foo"'s ini files change (obviously) * I think this is broken upstream, but I report it here first, to make sure that I didn't do something stupid "arch"wise. * mc's internal cd command (just type in "cd" and enter) changes correctly to the home of the su'd user. |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Thursday, 09 February 2012, 15:20 GMT
Reason for closing: Upstream
Additional comments about closing: Upstream says it's not a bug.
Thursday, 09 February 2012, 15:20 GMT
Reason for closing: Upstream
Additional comments about closing: Upstream says it's not a bug.
> Any other program works exactly the same. Just try.
> So NOTABUG.
This behaviour is expected. Please, close this task.