MakeMKV just won't work.

[Shibblet]

Hey there everyone...

I have been trying to get MakeMKV to work since 1.17.8 was released. All I get is this:

Screenshot_20241223_230733.png (96.03 KiB) Viewed 4125 times

With a disc in the drive, it does nothing but spin, and spin, and spin... Eventually I can hear the drive stop spinning, but MakeMKV does nothing different.

I am using Manjaro Linux, and I have tried the AUR version, the Flatpak Version, the AppImage Version, and the Snap Version. they all do the same thing.

I have cleared out the /home/svirf/.MakeMKV folder every time I change the version.

I have followed the information in viewtopic.php?f=3&t=16939&start=45 to even get the drive to register.

I am truly at my wits-end here. I cannot get this to function at all. Can someone PLEASE help?

[DukeFleed]

Hi.

I had the same problem on EndeavourOS, and I solved it thanks to the previous version I have on Ubuntu in dual boot. I don't know if it can be the same for you too. Read here: viewtopic.php?f=3&t=35703

[Shibblet]

Hi.

I had the same problem on EndeavourOS, and I solved it thanks to the previous version I have on Ubuntu in dual boot. I don't know if it can be the same for you too. Read here: viewtopic.php?f=3&t=35703

I have tried downgrading. But when I do, the registration key is out of date... hence, no workie.
And the current version won't allow me to input the registration key, because it seems to freeze at launch.

I have tried different OS's and futzing with things, until I finally decided that I would even change out my Blu-Ray drive, only to find out it still doesn't work. I just replaced an LG Blu-Ray drive with this new Pioneer. I also just removed Windows 11 (all the reasons) and installed Manjaro for the express purposes of encoding my Blu-Ray collection.

Again... without MakeMKV, I am dead in the water. I have been dead in the water since 1.17.8 released. So, we're going on three months now, and everything I have read doesn't seem to have any solution...

I assume that this is not a huge problem, or that there is some kind of fix... but i can't seem to figure it out.

[DukeFleed]

You could try to do it this way (untested, is just an idea), but only if you have purchased a license. Make a virtual machine with Virtualbox, install Ubuntu 24.04, then install an old version of MakeMKV from sources, download it here: https://makemkv.com/download/old/

Start MakeMKV of the VM and enter your key, wait for it to download the private_data.tar file, then after that copy it to your host Home, if I understand correctly it's Manjaro. Now try launching MakeMKV 1.17.8 and see if it works.

[storageisfun]

If you are using a Linux VM then I would suggest just making a new VM

[Pingoo]

Hi there,
did anyone find a solution for that? I have the same issue under Fedora 41. To install it I followed this guide:
https://linuxconfig.org/how-to-install- ... dora-linux

I also tried the snap install. That works fine but I'd like to avoid snap. So I would be quite thankful if somebody finds a problem to the eternal loading screen

[Michael A.]

Hi,
just another idea. Do you get something in the terminal if you run

Code: Select all

makemkvcon info dev:/dev/sr0

?

[dercakeman]

Hi, I think I have the exact same Problem, on dual-booted Windows it works perfectly but when booting arch makemkv behaves in the following way:
Disk in Drive:
MakeMKV stuck scanning for drives
No disk in Drive:
MakeMKV finds the drive, but when inserting the disk it's stuck loading just like your screen.

Additionally, I found out I don't have the SDF from the debug log:

Code: Select all

Debug log started at Sat Feb  8 22:23:02 2025 , written by MakeMKV v1.17.9 linux(x64-release)
001005:0000 MakeMKV v1.17.9 linux(x64-release) started
001004:0000 Debug logging enabled, log will be saved as file:///home/nicolas/MakeMKV_log.txt
Using 262272KB for read cache.
Network access is ENABLED, CURL version 8.12.0/OpenSSL/3.4.0/1.64.0 (x86_64-pc-linux-gnu) , proxy server not set.
001003:0020 DEBUG: Code 0 at %!`0:r|CkMG!# EZc^amvu:29393631
No  SDF v098: HL-DT-ST_BDDVDRW_CH10LS28_1.00_20110607123456_K8MCBUF0613
SDF id v098: HL-DT-ST_BDDVDRW_CH10LS28_1.00_20110607123456_K8MCBUF0613
001003:0020 DEBUG: Code 0 at %!`0:r|CkMG!# EZc^amvu:29393631
No  SDF v098: HL-DT-ST_BDDVDRW_CH10LS28_1.00_20110607123456_K8MCBUF0613
SDF auto v098: HL-DT-ST_BDDVDRW_CH10LS28_1.00_20110607123456_K8MCBUF0613

Also when using the cmd Michael A. suggested it just hangs after this line:

Code: Select all

MakeMKV v1.17.9 linux(x64-release) started
Debug logging enabled, log will be saved as file:///home/nicolas/MakeMKV_log.txt
DEBUG: Code 0 at %!`0:r|CkMG!# EZc^amvu:29393631

[ukos444]

I think, I have a similar problem since 1.17.8. I have the same symptoms of a hanging process. When doing makemkv info processes. It mostly happens when two parallel makemkvcon info processes are running but hanging may also happen with only a single instance.
To add on that, The process cannot be killed (SIGTERM, SIGINT, SIGKILL), finally creating zombie processes which fail to get reaped. Only system reboot (sometimes even hard reset / REISUB) gets the process to cancel.

Kernel: 6.8.0-52
System: Ubuntu 22.04.5
Drives: PIONEER BD-RW BDR-UD04
FW: 1.14
MakeMkv says it is using LibreDrive mode (v01.0 id=489CDFD6D392)

syslog:

Code: Select all

Feb 09 19:20:27 ubuntu kernel: INFO: task makemkvcon:11828 blocked for more than 614 seconds.
Feb 09 19:20:27 ubuntu kernel:       Not tainted 6.8.0-52-generic #53~22.04.1-Ubuntu
Feb 09 19:20:27 ubuntu kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 09 19:20:27 ubuntu kernel: task:makemkvcon      state:D stack:0     pid:11828 tgid:11825 ppid:11737  flags:0x00000002
Feb 09 19:20:27 ubuntu kernel: Call Trace:
Feb 09 19:20:27 ubuntu kernel:  <TASK>
Feb 09 19:20:27 ubuntu kernel:  __schedule+0x27c/0x6a0
Feb 09 19:20:27 ubuntu kernel:  schedule+0x33/0x110
Feb 09 19:20:27 ubuntu kernel:  io_schedule+0x46/0x80
Feb 09 19:20:27 ubuntu kernel:  blk_mq_get_tag+0x117/0x2f0
Feb 09 19:20:27 ubuntu kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Feb 09 19:20:27 ubuntu kernel:  __blk_mq_alloc_requests+0xc4/0x290
Feb 09 19:20:27 ubuntu kernel:  blk_mq_alloc_request+0x243/0x290
Feb 09 19:20:27 ubuntu kernel:  scsi_alloc_request+0xf/0x40
Feb 09 19:20:27 ubuntu kernel:  sg_start_req+0x97/0x4f0
Feb 09 19:20:27 ubuntu kernel:  sg_common_write.constprop.0+0x76/0x240
Feb 09 19:20:27 ubuntu kernel:  sg_new_write.isra.0+0x1ae/0x300
Feb 09 19:20:27 ubuntu kernel:  sg_ioctl_common+0x78c/0xb00
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? __schedule+0x284/0x6a0
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  sg_ioctl+0x3b/0x80
Feb 09 19:20:27 ubuntu kernel:  __x64_sys_ioctl+0xa3/0xf0
Feb 09 19:20:27 ubuntu kernel:  x64_sys_call+0xa71/0x2480
Feb 09 19:20:27 ubuntu kernel:  do_syscall_64+0x81/0x170
Feb 09 19:20:27 ubuntu kernel:  ? __pfx_futex_wake_mark+0x10/0x10
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? futex_wait+0x74/0x120
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? rseq_get_rseq_cs+0x22/0x280
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? rseq_ip_fixup+0x90/0x1f0
Feb 09 19:20:27 ubuntu kernel:  ? __x64_sys_futex+0x95/0x200
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? restore_fpregs_from_fpstate+0x3d/0xd0
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? switch_fpu_return+0x55/0xf0
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? syscall_exit_to_user_mode+0x83/0x260
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? do_syscall_64+0x8d/0x170
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? do_futex+0x128/0x230
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? __x64_sys_futex+0x95/0x200
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? syscall_exit_to_user_mode+0x83/0x260
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? do_syscall_64+0x8d/0x170
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? restore_fpregs_from_fpstate+0x3d/0xd0
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? switch_fpu_return+0x55/0xf0
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? syscall_exit_to_user_mode+0x83/0x260
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? do_syscall_64+0x8d/0x170
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? do_syscall_64+0x8d/0x170
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? syscall_exit_to_user_mode+0x83/0x260
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? do_syscall_64+0x8d/0x170
Feb 09 19:20:27 ubuntu kernel:  ? srso_return_thunk+0x5/0x5f
Feb 09 19:20:27 ubuntu kernel:  ? do_syscall_64+0x8d/0x170
Feb 09 19:20:27 ubuntu kernel:  ? do_syscall_64+0x8d/0x170
Feb 09 19:20:27 ubuntu kernel:  ? exc_page_fault+0x94/0x1b0
Feb 09 19:20:27 ubuntu kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Feb 09 19:20:27 ubuntu kernel: RIP: 0033:0x70132c6e094f
Feb 09 19:20:27 ubuntu kernel: RSP: 002b:000070130dbff5c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Feb 09 19:20:27 ubuntu kernel: RAX: ffffffffffffffda RBX: 000070130dbff700 RCX: 000070132c6e094f
Feb 09 19:20:27 ubuntu kernel: RDX: 000070130dbff620 RSI: 0000000000002285 RDI: 000000000000000d
Feb 09 19:20:27 ubuntu kernel: RBP: 0000000000000800 R08: 000070130ddb0000 R09: 0000000000000800
Feb 09 19:20:27 ubuntu kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000070130ddb0000
Feb 09 19:20:27 ubuntu kernel: R13: 000070130dbff700 R14: 000070130880f788 R15: 0000701308004a60
Feb 09 19:20:27 ubuntu kernel:  </TASK>
Feb 09 19:20:27 ubuntu kernel: Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
Feb 09 19:50:52 ubuntu kernel: pcieport 0000:00:01.1: AER: Correctable error message received from 0000:01:00.0
Feb 09 19:50:52 ubuntu kernel: xhci_hcd 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
Feb 09 19:50:52 ubuntu kernel: xhci_hcd 0000:01:00.0:   device [1022:43ba] error status/mask=00001000/00002000
Feb 09 19:50:52 ubuntu kernel: xhci_hcd 0000:01:00.0:    [12] Timeout 

[eang91]

Hello,

I was affected by the same problem: any makemkv v1.17.9 process would just hang forever (I'm on archlinux with makemkv compiled from source).

The fix for me was to downgrade to v1.17.6: I had initially tried with 1.17.7, but that version would just segfault on start for whatever reason.

I noticed this problem only when I upgraded my drive to a ASUS BW-16D1HT. My old drive (some dvd-only Atapi model) was working just fine with makemkv v1.17.9.

FWIW makemkv v1.17.9 works fine on Windows with this asus drive.

So it looks like the bug can only be triggered on Linux and only with "recent" drives.

EDIT: forgot to mention: I also have a Verbatim 43888 USB drive and that was NOT affected by the hang issue, using the same v1.17.9 linux build.

[LuminousEssence]

Hello,

I am on arch linux and I have the same issue. I wasn't able to resolve it even after an hour of investigation. In the end, I plugged the external drive into my mac mini and used the MacOS software, here it works without issue.

As I plan to buy the software, I would ask for this issue to please be fixed. I would feel bad spending money on something that doesn't work on my main PC. Thanks.