Posts by PigCop

    It's very odd, didn't have this on OMV4.

    And I don't have any issues for sure on any other site misbehaving like this between mobile or desktop css.

    Tried on a virtualized Win10 on the same machine, no problems there too.

    In your image in #4 click on the double arrow next to the X I believe that is a 'docking' option

    Like I said in #1, already clicked there. The popup does return kinda to normal but is only temporary.

    As soon as I close it and reopen a new dialog I get the same maximization.

    so OMV is not to blame :)

    If a full de-install/re-install of browser doesn't cure the issue, the next step would be to re-install the PC from scratch or accept the annoyance and live with it

    Well not really a solution is it? Especially when nothing apart from this is wrong with my system.

    And it's not about blaming anything, it's about reporting something that isn't working properly for no apparent reason.

    I suspect that there's some issue in how OMV5 detects if the device is mobile or not because I just noticed that this is the default behaviour on a mobile device (just tried on my tablet).


    Check the DPI scaling, right click on the desktop and select display settings, check scaling and layout this should be set to 100%

    No issues there, I always set it to 100%.

    Just installed OMV5.

    Is it me or now by default every popup dialog window is always maximized?

    I flushed my cache, reset UI to defaults, tried private mode, different browser, clicked the small double arrow and repositioned the dialog to no avail: every time a new dialog opens it's maximized and covers the whole page.

    What's going on?

    Hello everyone, the other day I installed a 4TB WD Red on a ODROID HC2.
    Is there any way to access the information on the dialog window attached to this post after I exited the web-gui?
    As far as I can tell after dozens of hours is still formatting the disk but I don't have a clue about what progress the system has made.

    Looking in the syslog I get these CDB write operations, so I guess is still at work, but I cannot interpret what block is writing.
    sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x8a 8a 00 00 00 00 00 b9 40 29 00 00 00 04 00 00 00


    • dialog.png

      (75.4 kB, downloaded 166 times, last: )