05-19-2019, 02:35 PM
(This post was last modified: 05-19-2019, 03:38 PM by BigScaryTiger.)
I hadn't realised that running update in 5.0 would take me to 5.1 (I thought it would just jump to 5.2).
So I can confirm that UPnP is working in 5.1 [proven]
(a) Onto a 5.1 to 5.2 upgrade, and.... yep no UPnP working.
(b) Reverted back to 4.19.34 kernel in 5.2 using Tim's script above... and UPnP is back and running <yay>
Unfortunately, the GUI issue has returned in 5.2 when I have Google Chrome maximised to my screen resolution of 1366 x 768. However, as indicated by Kent if I put Moode into a Chrome window on its own (using Chrome's Create Shortcut function) then it has no issue.
So something has happened to the CSS I suspect between 5.1 and 5.2
Anyway... I am happy again as I now have UPnP working and to be honest I listen to moode that way 90% of the time. Thanks Tim
So I can confirm that UPnP is working in 5.1 [proven]
(a) Onto a 5.1 to 5.2 upgrade, and.... yep no UPnP working.
(b) Reverted back to 4.19.34 kernel in 5.2 using Tim's script above... and UPnP is back and running <yay>
Unfortunately, the GUI issue has returned in 5.2 when I have Google Chrome maximised to my screen resolution of 1366 x 768. However, as indicated by Kent if I put Moode into a Chrome window on its own (using Chrome's Create Shortcut function) then it has no issue.
So something has happened to the CSS I suspect between 5.1 and 5.2
Anyway... I am happy again as I now have UPnP working and to be honest I listen to moode that way 90% of the time. Thanks Tim
