[Support] Djoss - MakeMKV


Recommended Posts

On 4/10/2021 at 5:17 PM, BigWorm said:

Getting a Fatal error when scanning BD+ title.  It's not on every disc, but so far I have 2 that it keeps doing that.  Anyone have any tips?

Does the issue occur while running java ?  What are the messages displayed in MakeMKV ?

Link to comment
On 4/13/2021 at 1:27 PM, Djoss said:

Where is the destination of your rip ?  Is it on your cache drive ?

It was to my media share. At the time I had no cache drive. Since then I have switched to ripping with my laptop instead of the server so I can reencode as well as it really taxes my server. 

Link to comment
  • 1 month later...

I'm also getting a "fatal error occurred, program will not exit" while manually scanning a disk. This isn't happening for every disk, and so far, it's just this one, Monster Hunter (2020). 

 

Debug log started at Mon May 24 01:31:49 2021 , written by MakeMKV v1.16.3 linux(x64-release)
001005:0000 MakeMKV v1.16.3 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///config/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.58.0/OpenSSL/1.1.1 (x86_64-pc-linux-gnu) , proxy server not set.
001003:0020 DEBUG: Code 0 at x4I7N2~a46M>:KH-Kp0hI^:29393631
SDF  v07e: HL-DT-ST_BD-RE__WH14NS40_1.01_211304042325_K9BD4Q62426
SDF  v07e: HL-DT-ST_BD-RE__WH14NS40_1.01_211304042325_K9BD4Q62426
001011:0000 Using LibreDrive mode (v06.2 id=94DE7D3D0ADE)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at Hk&nzPc`mXELw9{):121264625
001003:0020 DEBUG: Code 0 at Hk&nzPc`mXELw9{):29396966
Found java version=1.8.0.275 path=/usr/bin/java
003344:0000 Using Java runtime from /usr/bin/java

 

Any suggestions on how to proceed? I'm getting a segfault in the server log when running java, at least I think this part of the log is the relevant section

 

May 23 21:24:48 Tower kernel: vethf7c4303: renamed from eth0
May 23 21:24:48 Tower kernel: docker0: port 10(veth8a2b051) entered disabled state
May 23 21:24:48 Tower kernel: docker0: port 10(veth8a2b051) entered disabled state
May 23 21:24:48 Tower kernel: device veth8a2b051 left promiscuous mode
May 23 21:24:48 Tower kernel: docker0: port 10(veth8a2b051) entered disabled state
May 23 21:24:57 Tower kernel: docker0: port 10(veth7671832) entered blocking state
May 23 21:24:57 Tower kernel: docker0: port 10(veth7671832) entered disabled state
May 23 21:24:57 Tower kernel: device veth7671832 entered promiscuous mode
May 23 21:24:59 Tower kernel: eth0: renamed from veth7e0d1e6
May 23 21:24:59 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7671832: link becomes ready
May 23 21:24:59 Tower kernel: docker0: port 10(veth7671832) entered blocking state
May 23 21:24:59 Tower kernel: docker0: port 10(veth7671832) entered forwarding state
May 23 21:25:24 Tower kernel: makemkvcon[37041]: segfault at 8 ip 00000000007ac79b sp 00001489921b1f20 error 4 in makemkvcon[48d000+391000]
May 23 21:25:24 Tower kernel: Code: ef 05 41 c6 86 60 01 00 00 00 31 f6 89 7c 24 54 44 89 44 24 64 45 84 c0 0f 84 e7 02 00 00 40 84 f6 b8 00 00 00 00 49 0f 44 c7 <8b> 70 08 48 8b bc 24 90 00 00 00 e8 c5 c2 e9 ff 41 8a b6 60 01 00

 

Link to comment
11 hours ago, rbroberts said:

I'm also getting a "fatal error occurred, program will not exit" while manually scanning a disk. This isn't happening for every disk, and so far, it's just this one, Monster Hunter (2020). 

 


Debug log started at Mon May 24 01:31:49 2021 , written by MakeMKV v1.16.3 linux(x64-release)
001005:0000 MakeMKV v1.16.3 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///config/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.58.0/OpenSSL/1.1.1 (x86_64-pc-linux-gnu) , proxy server not set.
001003:0020 DEBUG: Code 0 at x4I7N2~a46M>:KH-Kp0hI^:29393631
SDF  v07e: HL-DT-ST_BD-RE__WH14NS40_1.01_211304042325_K9BD4Q62426
SDF  v07e: HL-DT-ST_BD-RE__WH14NS40_1.01_211304042325_K9BD4Q62426
001011:0000 Using LibreDrive mode (v06.2 id=94DE7D3D0ADE)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at Hk&nzPc`mXELw9{):121264625
001003:0020 DEBUG: Code 0 at Hk&nzPc`mXELw9{):29396966
Found java version=1.8.0.275 path=/usr/bin/java
003344:0000 Using Java runtime from /usr/bin/java

 

Any suggestions on how to proceed? I'm getting a segfault in the server log when running java, at least I think this part of the log is the relevant section

 


May 23 21:24:48 Tower kernel: vethf7c4303: renamed from eth0
May 23 21:24:48 Tower kernel: docker0: port 10(veth8a2b051) entered disabled state
May 23 21:24:48 Tower kernel: docker0: port 10(veth8a2b051) entered disabled state
May 23 21:24:48 Tower kernel: device veth8a2b051 left promiscuous mode
May 23 21:24:48 Tower kernel: docker0: port 10(veth8a2b051) entered disabled state
May 23 21:24:57 Tower kernel: docker0: port 10(veth7671832) entered blocking state
May 23 21:24:57 Tower kernel: docker0: port 10(veth7671832) entered disabled state
May 23 21:24:57 Tower kernel: device veth7671832 entered promiscuous mode
May 23 21:24:59 Tower kernel: eth0: renamed from veth7e0d1e6
May 23 21:24:59 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7671832: link becomes ready
May 23 21:24:59 Tower kernel: docker0: port 10(veth7671832) entered blocking state
May 23 21:24:59 Tower kernel: docker0: port 10(veth7671832) entered forwarding state
May 23 21:25:24 Tower kernel: makemkvcon[37041]: segfault at 8 ip 00000000007ac79b sp 00001489921b1f20 error 4 in makemkvcon[48d000+391000]
May 23 21:25:24 Tower kernel: Code: ef 05 41 c6 86 60 01 00 00 00 31 f6 89 7c 24 54 44 89 44 24 64 45 84 c0 0f 84 e7 02 00 00 40 84 f6 b8 00 00 00 00 49 0f 44 c7 <8b> 70 08 48 8b bc 24 90 00 00 00 e8 c5 c2 e9 ff 41 8a b6 60 01 00

 

 

Can you try with image version 1.18.1 to see if you have the same issue ?

Link to comment

First off great work on this docker. For the most part I've had great success with blu-ray and 4K. I am now having issues with ripping DVDs. I will initially get quick speeds but then it quickly slows down where the rip time will go up to 2 hours a disk. The optical drive setup works fine with blu-ray and will finish in about 30min. Rips are going to an external unassigned devices drive and I have attempted privileged mode with same results. Same result with any DVD I attempt to rip. I also have both devices passed through in docker advanced. Any idea what could be going on?

Link to comment
On 5/27/2021 at 9:59 AM, KrypticKahos said:

First off great work on this docker. For the most part I've had great success with blu-ray and 4K. I am now having issues with ripping DVDs. I will initially get quick speeds but then it quickly slows down where the rip time will go up to 2 hours a disk. The optical drive setup works fine with blu-ray and will finish in about 30min. Rips are going to an external unassigned devices drive and I have attempted privileged mode with same results. Same result with any DVD I attempt to rip. I also have both devices passed through in docker advanced. Any idea what could be going on?

So you get the same speed no matter the DVD disc ?  Do you have a CC (Closed Caption) track selected ?

Link to comment
31 minutes ago, Djoss said:

So you get the same speed no matter the DVD disc ?  Do you have a CC (Closed Caption) track selected ?

Correct. I have tried with somewhere between 5-10 DVDs and I am not using a CC track. makeMKV will report a disk read speed of between 2.5-3x but it will still take the 2+ hours to complete. Connecting the optical drive to a windows OS or Mac OS computer will give the expected speed with about 15min to complete in makeMKV.

Link to comment

Just wanted to say that I'm experiencing a similar issue to KrypticKahos.

 

I recently ripped the same file (3.2 GB) from the same DVD disc using the same optical drive on two different computers with extremely different results:

 

Windows 10 PC
 - MakeMKV v1.16.3
 - Optical drive connected to a SATA III port on motherboard
 - Output file saved to SSD connected to SATA III port on motherboard
 - Read rate: unsure of average rate, but kept increasing during the course of the rip to a max of 14.3x by the end of the rip
 - Elapsed time: 4:13

 

Unraid server:
 - MakeMKV v1.16.3 (Djoss MakeMKV docker)
 - Optical drive connected to a SATA I port on PCI add-on card
 - Output file saved to SSD (cache-only) connected to SATA III port on motherboard
 - Read rate: Reached a max rate of 2.5x, but averaged ~1.8x throughout most of the rip
 - Elapsed time: 38:39 (~9 times longer to rip than on the Windows 10 PC)
 * All other dockers were stopped for this test and no other data transfers were occurring on that server

 

I initially suspected that the optical drive being connected to the SATA I port was the issue.  However, SATA I has a "theoretical" max transfer rate of ~150 MB/s.  The rip on the Unraid machine was averaging ~ 2.4MB/s, which should have had a lot more headroom.

 

Any idea if the SATA I connection is the cause for the significant delta?  Or if there's an obvious (not to me) alternative explanation for that extreme difference?

 

Thanks!
Paul

Edited by Datrox
Changed 6Gb to III
Link to comment
  • 1 month later...

Starting off--new to unRAID and to Dockers in general.  Not having an issue with any other docker -- strange situation with the MakeMKV one.  Firstly, I have a Buffalo USB drive, I've exposed both linux devices to the container.  It can read *some* disks, but when it has a problem and just reads forever--either loading the disk or during ripping--the container hangs and can't be shutdown...it's worse than that as even killing the associated processes still don't allow the array to be shutdown successfully and I have to go unclean hard down.  I've pulled the drive over to the same release of MakeMKV on Windows10--it does not become unresponsive under those conditions.  So in other words I was trying to eliminate a specific disk or drive issue.  

 

In the container log it always hangs on 'syncing disks'--even if I haven't gotten past the actual identification of the disk, when trying to stop the container it hangs there.  

 

I'm not running the container in priveleged mode.  I am exposing both drive devices through extra parameters.  This is happening with the latest release and with the last most recent container release.  Bottom line is that everything's golden if the disk reads perfectly, but when it doesn't, then I have to hard down the server because I can't get the container to shut down.  

 

My instinct tells me there is something here with permissions and possibly the fact this is USB hardware.  What's not clear is why the container is stuck on synching disks and won't allow the array to shutdown or the container to stop gracefully.

 

Thoughts?

 

 

Link to comment
15 hours ago, NDDan said:

Starting off--new to unRAID and to Dockers in general.  Not having an issue with any other docker -- strange situation with the MakeMKV one.  Firstly, I have a Buffalo USB drive, I've exposed both linux devices to the container.  It can read *some* disks, but when it has a problem and just reads forever--either loading the disk or during ripping--the container hangs and can't be shutdown...it's worse than that as even killing the associated processes still don't allow the array to be shutdown successfully and I have to go unclean hard down.  I've pulled the drive over to the same release of MakeMKV on Windows10--it does not become unresponsive under those conditions.  So in other words I was trying to eliminate a specific disk or drive issue.  

 

In the container log it always hangs on 'syncing disks'--even if I haven't gotten past the actual identification of the disk, when trying to stop the container it hangs there.  

 

I'm not running the container in priveleged mode.  I am exposing both drive devices through extra parameters.  This is happening with the latest release and with the last most recent container release.  Bottom line is that everything's golden if the disk reads perfectly, but when it doesn't, then I have to hard down the server because I can't get the container to shut down.  

 

My instinct tells me there is something here with permissions and possibly the fact this is USB hardware.  What's not clear is why the container is stuck on synching disks and won't allow the array to shutdown or the container to stop gracefully.

 

Thoughts?

 

I think this is not related to the container itself, but to the Linux version of HandBrake (you would probably be able to reproduce the same behaviour in a Linux VM).

 

Try to look at the MakeMKV forum.  For example, I found the following post, which seem to describe your problem.  But I'm not sure if the solution applies to unRAID though.

 

https://forum.makemkv.com/forum/viewtopic.php?f=3&t=25357&p=109149&hilit=hang#p109149

 

 

Link to comment
On 7/26/2021 at 6:51 AM, Djoss said:

 

I think this is not related to the container itself, but to the Linux version of HandBrake (you would probably be able to reproduce the same behaviour in a Linux VM).

 

Try to look at the MakeMKV forum.  For example, I found the following post, which seem to describe your problem.  But I'm not sure if the solution applies to unRAID though.

 

https://forum.makemkv.com/forum/viewtopic.php?f=3&t=25357&p=109149&hilit=hang#p109149

 

 

Thank you for the suggestion.  It does sound exceedingly similar.  I'm not savvy enough with unRAID to translate this to a potential solution for unRAID however.  I've posted it on the unRAID:Docker Engine forum, but have not gotten any traction yet.  If someone picks it up I've reference any solution here for others.  

Edited by NDDan
Link to comment

When I went to log into MakeMKV to rip a DVD today I got this error....

 

562137733_ScreenShot2021-08-01at4_26_22PM.thumb.png.b6bc9325eec138853b44c2ea96865e1d.png

 

954212951_ScreenShot2021-08-01at4_26_32PM.thumb.png.d7b3485be2f1d0a48db20befdb2d56d7.png

 

I then went and purchased a code and entered it to register... it accepted the code and asked me to restart the program. I close the tab... and then restarted the docker container. After the restart I get the same error. Not sure what is happening... but no matter when I do I am in this same loop.

 

I have attacked the log file in case that helps in some way.

 

Thanks for any help on this!

 

Edited by ALMattSr
Log File delete
Link to comment
1 minute ago, ALMattSr said:

When I went to log into MakeMKV to rip a DVD today I got this error....

 

562137733_ScreenShot2021-08-01at4_26_22PM.thumb.png.b6bc9325eec138853b44c2ea96865e1d.png

 

954212951_ScreenShot2021-08-01at4_26_32PM.thumb.png.d7b3485be2f1d0a48db20befdb2d56d7.png

 

I then went and purchased a code and entered it to register... it accepted the code and asked me to restart the program. I close the tab... and then restarted the docker container. After the restart I get the same error. Not sure what is happening... but no matter when I do I am in this same loop.

 

I have attacked the log file in case that helps in some way.

 

Thanks for any help on this!

MakeMKV Log.pdf 87.97 kB · 1 download

In the settings of the docker there's a field called "License key".  Put your key there, (or BETA for beta).  There always seems to be a lag at the first of the month, though, in getting the app to recognize the beta key or get the new version.

  • Like 1
Link to comment
  • 1 month later...
On 1/2/2021 at 11:50 AM, Djoss said:

Could you try to rip the disc manually and provide the output ?

 

First, login to the container:

docker exec -ti MakeMKV sh

Then, to rip disc 0, execute:

env HOME=/config /opt/makemkv/bin/makemkvcon -r --progress=-same mkv disc:0 all /output/manual_rip_test

If you don't know the disc ID, you can run:

/opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999

 

I have had several movies recently that wouldn't rip via GUI but do via the command line above.  Specifically Princess Bride DVD and Black Hawk Down BluRay.  Any idea why that is?

Screenshot 2021-09-15 163135.png

Link to comment
On 9/12/2017 at 12:24 AM, MowMdown said:

@cybrnook Tick the "Advanced View" in the upper right corner, and you'll see an "Extra Parameters" section just below the "Description" section

 

once your device is plugged into the machine, find its device id/path. 

 

cd into /dev/disk/by-id

 

then run 

ls -l

 then figure out which is the USB/Device you need - see below on the far right.

root@Tower:/dev/disk/by-id# ls -l
total 0                                                                                              
lrwxrwxrwx 1 root root  9 Sep  7 16:46 ata-ASUS_DRW-24B1ST_c_C1D0CL043771 -> ../../sr0
lrwxrwxrwx 1 root root  9 Sep  7 16:46 ata-WDC_WD6400AAVS-00G9B0_WD-WCAUF0537940 -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep  7 16:46 ata-WDC_WD6400AAVS-00G9B0_WD-WCAUF0537940-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Sep  7 16:46 usb-PNY_USB_2.0_FD_4530100578919190-0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Sep  7 16:46 usb-PNY_USB_2.0_FD_4530100578919190-0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  9 Sep  7 16:46 wwn-0x10770454365260107777x -> ../../sdb
lrwxrwxrwx 1 root root 10 Sep  7 16:46 wwn-0x10770454365260107777x-part1 -> ../../sdb1

 

so lets say I wanted to add a device like my CD-DVD drive (obviously not a storage device)

 

I would add in the extra parameters section

 

--device /dev/sr0

 

Hit Save

for some reason this does not work. i know it used to on my old unraid build. I have rebuilt everything and reused the disc drive. but following this though does not make any difference. i have to stub the disc drive or something like that?

Link to comment
9 minutes ago, Goldmaster said:
for some reason this does not work. i know it used to on my old unraid build. I have rebuilt everything and reused the disc drive. but following this though does not make any difference. i have to stub the disc drive or something like that?


After the docker is started look in the docker log, it tells you exactly what parameters to pass.

 

here is mine:

[cont-init.d] 95-check-optical-drive.sh: executing...
[cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives...
[cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg7], group 19.
[cont-init.d] 95-check-optical-drive.sh: exited 0.

 so therefore i add:

-device /dev/sr0 --device /dev/sg7

to the extra parameters section

Edited by spl147
Link to comment
10 minutes ago, spl147 said:


After the docker is started look in the docker log, it tells you exactly what parameters to pass

 

well this is the log

 


ErrorWarningSystemArrayLogin

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-app-niceness.sh: executing...
[cont-init.d] 00-app-niceness.sh: exited 0.
[cont-init.d] 00-app-script.sh: executing...
[cont-init.d] 00-app-script.sh: exited 0.
[cont-init.d] 00-app-user-map.sh: executing...
[cont-init.d] 00-app-user-map.sh: exited 0.
[cont-init.d] 00-clean-logmonitor-states.sh: executing...
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.
[cont-init.d] 00-clean-tmp-dir.sh: executing...
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.
[cont-init.d] 00-set-app-deps.sh: executing...
[cont-init.d] 00-set-app-deps.sh: exited 0.
[cont-init.d] 00-set-home.sh: executing...
[cont-init.d] 00-set-home.sh: exited 0.
[cont-init.d] 00-take-config-ownership.sh: executing...
[cont-init.d] 00-take-config-ownership.sh: exited 0.
[cont-init.d] 00-xdg-runtime-dir.sh: executing...
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.
[cont-init.d] 10-certs.sh: executing...
[cont-init.d] 10-certs.sh: exited 0.
[cont-init.d] 10-cjk-font.sh: executing...
[cont-init.d] 10-cjk-font.sh: exited 0.
[cont-init.d] 10-nginx.sh: executing...
[cont-init.d] 10-nginx.sh: exited 0.
[cont-init.d] 10-vnc-password.sh: executing...
[cont-init.d] 10-vnc-password.sh: exited 0.
[cont-init.d] 10-web-index.sh: executing...
[cont-init.d] 10-web-index.sh: exited 0.
[cont-init.d] 90-makemkv.sh: executing...
[cont-init.d] 90-makemkv.sh: generating machine-id...
app_ccextractor = "/usr/bin/ccextractor"
Checking for new beta key...
Registration key already up-to-date.
[cont-init.d] 90-makemkv.sh: exited 0.
[cont-init.d] 95-check-optical-drive.sh: executing...
[cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives...
[cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg1], but it is not usable because:
[cont-init.d] 95-check-optical-drive.sh: --> the host device /dev/sg1 is not exposed to the container.
[cont-init.d] 95-check-optical-drive.sh: no usable optical drive found.
[cont-init.d] 95-check-optical-drive.sh: exited 0.
[cont-init.d] 96-install-autodiscripper-srv.sh: executing...
[cont-init.d] 96-install-autodiscripper-srv.sh: automatic disc ripper disabled.
[cont-init.d] 96-install-autodiscripper-srv.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] starting s6-fdholderd...
[services.d] starting certsmonitor...
[services.d] starting nginx...
[services.d] starting xvfb...
[nginx] starting...
[certsmonitor] disabling service: secure connection not enabled.
[xvfb] starting...
[services.d] starting logmonitor...
[services.d] starting statusmonitor...
[logmonitor] no file to monitor: disabling service...
[services.d] starting openbox...
[statusmonitor] no file to monitor: disabling service...
[openbox] starting...
[services.d] starting x11vnc...
[services.d] starting app...
[x11vnc] starting...
[app] starting MakeMKV...
[services.d] done.
19/09/2021 21:59:16 passing arg to libvncserver: -rfbport
19/09/2021 21:59:16 passing arg to libvncserver: 5900
19/09/2021 21:59:16 passing arg to libvncserver: -rfbportv6
19/09/2021 21:59:16 passing arg to libvncserver: -1
19/09/2021 21:59:16 passing arg to libvncserver: -httpportv6
19/09/2021 21:59:16 passing arg to libvncserver: -1
19/09/2021 21:59:16 passing arg to libvncserver: -desktop
19/09/2021 21:59:16 passing arg to libvncserver: MakeMKV
19/09/2021 21:59:16 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 922
19/09/2021 21:59:16 Using X display :0
19/09/2021 21:59:16 rootwin: 0x43 reswin: 0x400001 dpy: 0x78bfeb00
19/09/2021 21:59:16
19/09/2021 21:59:16 ------------------ USEFUL INFORMATION ------------------
19/09/2021 21:59:16 X DAMAGE available on display, using it for polling hints.
19/09/2021 21:59:16 To disable this behavior use: '-noxdamage'
19/09/2021 21:59:16
19/09/2021 21:59:16 Most compositing window managers like 'compiz' or 'beryl'
19/09/2021 21:59:16 cause X DAMAGE to fail, and so you may not see any screen
19/09/2021 21:59:16 updates via VNC. Either disable 'compiz' (recommended) or
19/09/2021 21:59:16 supply the x11vnc '-noxdamage' command line option.
19/09/2021 21:59:16 X COMPOSITE available on display, using it for window polling.
19/09/2021 21:59:16 To disable this behavior use: '-noxcomposite'
19/09/2021 21:59:16
19/09/2021 21:59:16 Wireframing: -wireframe mode is in effect for window moves.
19/09/2021 21:59:16 If this yields undesired behavior (poor response, painting
19/09/2021 21:59:16 errors, etc) it may be disabled:
19/09/2021 21:59:16 - use '-nowf' to disable wireframing completely.
19/09/2021 21:59:16 - use '-nowcr' to disable the Copy Rectangle after the
19/09/2021 21:59:16 moved window is released in the new position.
19/09/2021 21:59:16 Also see the -help entry for tuning parameters.
19/09/2021 21:59:16 You can press 3 Alt_L's (Left "Alt" key) in a row to
19/09/2021 21:59:16 repaint the screen, also see the -fixscreen option for
19/09/2021 21:59:16 periodic repaints.
19/09/2021 21:59:16 GrabServer control via XTEST.
19/09/2021 21:59:16
19/09/2021 21:59:16 Scroll Detection: -scrollcopyrect mode is in effect to
19/09/2021 21:59:16 use RECORD extension to try to detect scrolling windows
19/09/2021 21:59:16 (induced by either user keystroke or mouse input).
19/09/2021 21:59:16 If this yields undesired behavior (poor response, painting
19/09/2021 21:59:16 errors, etc) it may be disabled via: '-noscr'
19/09/2021 21:59:16 Also see the -help entry for tuning parameters.
19/09/2021 21:59:16 You can press 3 Alt_L's (Left "Alt" key) in a row to
19/09/2021 21:59:16 repaint the screen, also see the -fixscreen option for
19/09/2021 21:59:16 periodic repaints.
19/09/2021 21:59:16
19/09/2021 21:59:16 XKEYBOARD: number of keysyms per keycode 7 is greater
19/09/2021 21:59:16 than 4 and 51 keysyms are mapped above 4.
19/09/2021 21:59:16 Automatically switching to -xkb mode.
19/09/2021 21:59:16 If this makes the key mapping worse you can
19/09/2021 21:59:16 disable it with the "-noxkb" option.
19/09/2021 21:59:16 Also, remember "-remap DEAD" for accenting characters.
19/09/2021 21:59:16
19/09/2021 21:59:16 X FBPM extension not supported.
Xlib: extension "DPMS" missing on display ":0".
19/09/2021 21:59:16 X display is not capable of DPMS.
19/09/2021 21:59:16 --------------------------------------------------------
19/09/2021 21:59:16
19/09/2021 21:59:16 Default visual ID: 0x21
19/09/2021 21:59:16 Read initial data from X display into framebuffer.
19/09/2021 21:59:16 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120
19/09/2021 21:59:16
19/09/2021 21:59:16 X display :0 is 32bpp depth=24 true color
19/09/2021 21:59:16
19/09/2021 21:59:16 Listening for VNC connections on TCP port 5900
19/09/2021 21:59:16
19/09/2021 21:59:16 Xinerama is present and active (e.g. multi-head).
19/09/2021 21:59:16 Xinerama: number of sub-screens: 1
19/09/2021 21:59:16 Xinerama: no blackouts needed (only one sub-screen)
19/09/2021 21:59:16
19/09/2021 21:59:16 fb read rate: 2319 MB/sec
19/09/2021 21:59:16 fast read: reset -wait ms to: 10
19/09/2021 21:59:16 fast read: reset -defer ms to: 10
19/09/2021 21:59:16 The X server says there are 10 mouse buttons.
19/09/2021 21:59:16 screen setup finished.
19/09/2021 21:59:16

The VNC desktop is: fee0a2b37793:0

0

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:

x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching

 

 

ok i think its something where it says `[cont-init.d] 95-check-optical-drive.sh: --> the host device /dev/sg1 is not exposed to the container.` not sure how to fix that.

Link to comment
5 minutes ago, Goldmaster said:

ok i think its something where it says `[cont-init.d] 95-check-optical-drive.sh: --> the host device /dev/sg1 is not exposed to the container.` not sure how to fix that.

edit the container, click in the right corner where it says basic view, so it will say advanced, scroll down to where it says extra parameters and put --device /dev/sr0 --device /dev/sg1, then click apply

Edited by spl147
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.