| 1 |
Ühel kenal päeval, K, 19.09.2018 kell 16:35, kirjutas Helmut Jarausch: |
| 2 |
> Hi, |
| 3 |
> I wonder what I am doing wrong. |
| 4 |
> For several packages, e.g. x11-terms/kitty-0.12.1 |
| 5 |
> I get access violations like |
| 6 |
> |
| 7 |
> * ACCESS DENIED: mkdir: /root/.config/kitty |
| 8 |
> |
| 9 |
> The cause of this is clear: emerge is running as user/group |
| 10 |
> 'portage' |
| 11 |
> but |
| 12 |
> ls -ld /root/.config |
| 13 |
> gives |
| 14 |
> drwx------ 15 root portage 4096 Sep 19 14:20 /root/.config |
| 15 |
> |
| 16 |
> One could change the permission of this folder, but there are |
| 17 |
> several applications which use this folder. |
| 18 |
> |
| 19 |
> What am I missing? |
| 20 |
|
| 21 |
kitty ebuild is missing a call to gnome_environment_reset, or at least |
| 22 |
xdg_environment_reset. If that is not done (and the ebuild isn't EAPI7 |
| 23 |
and something in the build ends up using XDG standards), then you could |
| 24 |
hit issues like this. Most often when you become root in a way that |
| 25 |
keeps user settings. |
| 26 |
To avoid this, you should consider using "su -" instead of "su" to |
| 27 |
become root; or the equivalent in case of other methods (though sudo by |
| 28 |
default does this and needs an extra argument to keep the env vars). |
| 29 |
|
| 30 |
However this is also technicall a bug in the ebuild, as discussed |
| 31 |
above, and such things should be tracked on bugzilla, if a particular |
| 32 |
packages case already isn't. |
| 33 |
|
| 34 |
|
| 35 |
Mart |
Archives