OK, ryecoaaron this topic seems more or less ontopic. To go on from the asual mantion of Extras which seem to trigger you.
Since i can not reply to you in place and it would be offtopic anyway, let me clear it here.
> The webui should not stop working after omv-extras is installed.
I agree, but it does, not every time but enough to make it common.
When the whole of UI of OMV stops working - this is hardly to perceive differently than "system is falling apart".
Now there can be "not my problem" game between OMV core, OMV extras core and specific plugins.
How ever from user perspective it looks like that.
1. User installs OMV - and it works
2. User installs OMV-Extra and some Extra-provided plugins, and then his OMV box is bricked.
You may be triggered by using "bricked" word, but then we have to remember
> Running a GUI on OMV is absolutely not supported because OMV and GUI's work against each other. OMV is the master of the system by design.
And there is no other UI than WebUI. (for example Mikrotik routers have dsktop applications as alternative first citizen UI).
So, if WebUI is not available, then system is bricked, from user perspective.
What users sees is that he enters OMV UI, checks some checkmarks - and OMV UI is not available any more.
> Even if it isn't installed and a plugin needs, it doesn't break the web interface. It only breaks the folder browser.
The missing file names imly this, yes. Howeve reality is different, WebUI stops to work.
I can speculate that WebUI tryes to force me to some "panel open in previous session" and that panel happens to have browser. Or anything.
However, on occasion, mere installing Extras (core and some plugins) makes fresh one day old OMV box bricked.
Voker sais i have some sad luck to step into bugs, and that is somewhat true. However not me alone. One of top lines in google leads to Login Error and Reappearing Deleted Log Files
The same story. Install something frm extras - get the whole WebUI bricked. Reboots do not fix it.
It is not like page renders but some "directory listing" iframe does not appear. It that user can not login into OMV at all.
I may say, there should be something fragile in OMV itself then, if lack of one file can break the whole UI, not some localized part of it.
> It is needed by a handful of plugins that should install it just like any other dependency when you install the plugin. If that isn't happening, something is wrong with apt on the system.
I do not think there is "something wrong with apt", would it be so, to borrow your words "APT would have thousands of people with issues otherwise".
> omvextras-common is not needed by most plugins or omv-extras itself. It is needed by a handful of plugins that should install it just like any other dependency when you install the plugin.
Now that is probably correct. But there is nothing in OMV Extrast the project that ensures it. Users keep stambleupon it again and again and OMV Extras the project says "have no idea what is deleting the files".
You are triggered by "falling apart" but put on users shoes. You enter standard system UI, you click several "omv extras" packages, you click apply - and the sysatem is bricked and OMV Extras say "we have no idea". It doesn't sound like "fallign apart", not at all?
> If something is removing that package
I dop not believe it. it was a fresh one day old OMV installation.
However would something really be deleting it than APT would delete also al lthe dependent packages, won't it?
So it is most probably a long-standing problems with dependencies amonf OMV Extras packages, plugins including.
> It would be interesting to have more details.
Sure. But sadly there is no. I was battling with a totally unknown to me system, and other issues. So i can not remember much of specifics. I have a photo showing apt-geet window in process, but i am not sure iot was related to this or something else.
I have no repro and little details i remember with certainty.
> If you can't close the window, you can alway refresh the page
Eventually i did. Maybe that was when the whole WebUI stopped working, or maybe not, i am not sure.
User can also open their browser's DevTools and enable the close button or remove the frame/div altogether.
But see, it is last resort. User has to be sure it is time to close the window.
It would be disrupting to destory that frame while apt-get session is stil lrunning and the output is not finalized, won't it?
But user has no way to know the underlying process is already finished and hardkilling the window is safe now