|
Bugzilla – Full Text Bug Listing |
| Summary: | /run/lock no longer belongs to the "lock" group; it is now in "root" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | David Walker <David> |
| Component: | Basesystem | Assignee: | E-mail List <screening-team-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | chcao, filatovalex91 |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | aarch64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
David Walker
2023-09-10 07:04:51 UTC
(In reply to David Walker from comment #0) > What this change deliberate? Yes, this was necessary to fix a huge amount of problems and race conditions. > If not, could it be reversed? Not without introducing a huge amount of problems affecting everybody with every installation. > If it can't be reversed, suggestions for a workaround would be appreciated. Same as for any other package, create your own sub-directory with the permissions you need? Thanks, Thorsten. I'll find another way. Based on the comments above, I mark this bug report as WONTFIX, if I get wrong, please feel free to reopen it, thanks. Another inconvenience introduced: minicom can't create lock file in /run/lock without root permissions. |