More > JRiver Media Center 25 for Linux
JRiver MC25 Docker Image with WebUI as VNC
max096:
--- Quote from: bob on August 02, 2019, 09:42:50 am ---MC child windows shouldn't popup behind the main MC window. We never specify underneath stacking and we don't alter the stacking order. You can get a window to go behind by clicking on the main window while the popup is showing IF there is a window manager since that's out of the control of MC. We've done some preliminary work to restack in that case but it's not as simple as it seems since many windows in MC are a collection of windows.
When there is a window manager ALT-Tab generally cycles through the windows. When we had a QNAP version, their window manager forced every open window to fullscreen so that it was impossible to restack the windows by accident.
--- End quote ---
shortie ended up with a container where the about window popped up behind. Witch should not happen (although Im not saying its necessarily your fault). Even in that version it worked for me. He replaced the home folder and it worked again.
Since it only ever runs one application. The way I did make this work is to write a service script that reads out all the xorg changes. Whenever the window changes it makes the last windows in existence active and thus it will be focused and on top. That didnt really quite fully work back when shortie had this happen though.
If you see any potential problem with that you can tell me. But I believe since there is only one application you really should never get into a situation where the last window you opened isnt the one you want/need to interact with. Clicking JRiver should result in jriver being active for a split second then the other one being set active by the script and it comes back.
There is an option to start windows in fullscreen in openbox too. Works for everything, but the main window (you can still make them smaller though). Maybe its also able to make them stay fullscreen. But I didnt really like the looks of it.
The current script works very well now, though. Or at least nobody has told me to have any problems with it since that one time. It still would be nice to have a plan B should it fail. Right now plan B is to make a library backup, tear down everything. And then restore the library backup. If you could do "docker exec my-jriver-container resetgui" that would be ideal I think. Now I´m not sure if it fixes it. But chances are good that it would. ^^
bob:
--- Quote from: max096 on August 02, 2019, 10:32:02 am ---shortie ended up with a container where the about window popped up behind. Witch should not happen (although Im not saying its necessarily your fault). Even in that version it worked for me. He replaced the home folder and it worked again.
Since it only ever runs one application. The way I did make this work is to write a service script that reads out all the xorg changes. Whenever the window changes it makes the last windows in existence active and thus it will be focused and on top. That didnt really quite fully work back when shortie had this happen though.
If you see any potential problem with that you can tell me. But I believe since there is only one application you really should never get into a situation where the last window you opened isnt the one you want/need to interact with. Clicking JRiver should result in jriver being active for a split second then the other one being set active by the script and it comes back.
There is an option to start windows in fullscreen in openbox too. Works for everything, but the main window (you can still make them smaller though). Maybe its also able to make them stay fullscreen. But I didnt really like the looks of it.
The current script works very well now, though. Or at least nobody has told me to have any problems with it since that one time. It still would be nice to have a plan B should it fail. Right now plan B is to make a library backup, tear down everything. And then restore the library backup. If you could do "docker exec my-jriver-container resetgui" that would be ideal I think. Now I´m not sure if it fixes it. But chances are good that it would. ^^
--- End quote ---
Glad to hear you have it working well.
The issues I had with restacking the windows concerned a fight with other apps IIRC so I think that won't apply to you. The other thing to watch for is the windows within the window thing. Suggestion tool tips and the like. You can see with xprop that all of MC's windows have class and class names that make sense if that helps.
balky:
--- Quote from: max096 on August 02, 2019, 09:05:24 am ---What does docker inspect have to say about the network configuration of the container you made with v2 and v3?
Either way if v2 works fine. It is perfectly fine to run that since the version in the compose file refers to the version of the configuration file standard. It has no affect on what docker, or docker-compose version you are using. There are newer docker-compose.yml versions, but those are more targeted towards docker-swarm.
Have you tried host networking? That does work? Bridge networking is not really working on my centos ovirt NAS either, because of the firewall rules and networks ovirt setup. But host networking works and bridge networking works in VMs ovirt can host. So it may be the same thing for your openmediavault.
.
.
.
--- End quote ---
Thanks a lot for the comments...
I decided to go for a "near bare-bone" setup... i.e. I removed OpenMediaVault, reinstalled Debian minimal with only SSH server, then installed ZFS, samba, docker and docker-compose
That was it... I created docker-compose.yml for host, pulled the jrivermc25 image and that was all...
I am sincerely overjoyed... no more X11, no more desktop... all was done within 45 minutes and I have a running DLNA server...
Many thanks to all those who keep JRiver alive and on the bleeding edge...
max096:
--- Quote from: balky on August 02, 2019, 02:32:03 pm ---Thanks a lot for the comments...
I decided to go for a "near bare-bone" setup... i.e. I removed OpenMediaVault, reinstalled Debian minimal with only SSH server, then installed ZFS, samba, docker and docker-compose
That was it... I created docker-compose.yml for host, pulled the jrivermc25 image and that was all...
I am sincerely overjoyed... no more X11, no more desktop... all was done within 45 minutes and I have a running DLNA server...
Many thanks to all those who keep JRiver alive and on the bleeding edge...
--- End quote ---
A bit drastic actions..., but great that it works now! :)
max096:
I also built a jrivermc24 image now. Not sure if anybody asked for that... ?
I didn't ask for it either. But I was trying to make the entire build process a bit more modular (not quite there yet. 24 worked right off the bat without a single change required to the image. None of this changed the resulting container other than what JRiver version was installed and what docker repo it was pushed to.
23 didn't work, not gonna try to get that to work. Would not have tried for 24 either tbh. But since it just worked with no effort, there it is.
https://hub.docker.com/r/shiomax/jrivermc24
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version