INTERACT FORUM
Linux => JRiver Media Center 33 for Linux => Topic started by: cochinada on March 17, 2025, 03:32:50 pm
-
Help please!!!
I had to install Debian 12 on my new HTPC and decided to upgrade to the latest MC for Linux but...
I've followed these instructions https://yabb.jriver.com/interact/index.php/topic,139542.0.html (https://yabb.jriver.com/interact/index.php/topic,139542.0.html) and executed this command:
joaquim@HTPC:~$ curl -O https://git.bryanroessler.com/bryan/installJRMC/raw/master/installJRMC &&
chmod +x ./installJRMC &&
./installJRMC [--option [ARGUMENT]]
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 59185 0 59185 0 0 140k 0 --:--:-- --:--:-- --:--:-- 140k
Starting installJRMC 1.4.8
To enable debugging output, use --debug or -d
Installing JRiver Media Center from remote repository
Installing JRiver Media Center RPM key
Adding MC repository file: /etc/apt/sources.list.d/jriver.list
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://dist.jriver.com/latest/mediacenter bookworm InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
mediacenter33 is already the newest version (33.0.71).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
JRiver Media Center installed successfully from remote repository
Warning: Install firewall-cmd or ufw to open firewall ports
joaquim@HTPC:~$
Now I'm trying to register it but I got an error message:
"There was a problem communicating with the license server"
-
Hello Support,
I would like an answer of how can I use my Registration code as I'm getting that error still!
-
This is likely due to the server move:
https://yabb.jriver.com/interact/index.php/topic,140860.msg976918.html#msg976918
-
This is likely due to the server move:
https://yabb.jriver.com/interact/index.php/topic,140860.msg976918.html#msg976918
I see! Murphy's law is very strong with me so I have even a more serious issue. Not sure if it is because I'm not able to register yet but here goes what happened:
I've restored the Library using my latest backup. Then it told me it had to restart to apply the changes and so it restarted...
After coming back (in Theater View as before) my PC is completely frozen!!! The keyboard is irresponsive and so is the mouse. Num lock or caps lock keys don't even function. It is like I didn't have a keyboard.
All I see is the initial Theater view screen and nothing else.
I cannot also ping it from another PC. ::)
-
Wireless mouse/keyb ? Try plugging a wired one.
-
No. They are both wired.
-
So, how do I get out of this predicament?
Did I do something wrong?
This was a backup from my previous version MC30 also for Linux.
The only difference between this new PC and the previous one, aside from the different HW of course, is that I was using Debian 11 and now I have Debian 12.
Previous HW:
Pentium Gold G5500T
ASRock B360M PRO4
GSkill DDR4 2400 8GB C15 Aegis K2 (F4-2400C15D-8GIS)
SSD SAMSUNG 970 EVO NVME (MZ-V7E250BW) 250GB
Current HW:
AMD Ryzen 5 8600G
ASRock B850M-X
Crucial Pro DDR5-6000 16GB
SSD SAMSUNG 970 EVO NVME (MZ-V7E250BW) 250GB
Note: I have three more SDD sata disks just for storage.
-
If your brand new PC is freezing, maybe it's a hardware fault - new stuff can also be broken.
More likely, your Debian install has some driver issue that needs fixing or reinstalling. Does the keyboard work during boot? Can you enter the PC BIOS or type commands at the linux boot prompt? If that works then you'll need to enter linux in safe mode and look at logs to find out what's wrong. Or just reinstall from scratch, if you have backups.
-
If your brand new PC is freezing, maybe it's a hardware fault - new stuff can also be broken.
More likely, your Debian install has some driver issue that needs fixing or reinstalling. Does the keyboard work during boot? Can you enter the PC BIOS or type commands at the linux boot prompt? If that works then you'll need to enter linux in safe mode and look at logs to find out what's wrong. Or just reinstall from scratch, if you have backups.
I don't have any HW fault. Perhaps I was not clear enough but this freezing only happened after I've restored my Library. Before everything was working fine but of course my MC Library was totally empty.
The event(s) that triggered this were either the restoring of the Library (and subsequent restart) or entering Theater View as a consequence of the restore.
-
For newer hardware like that, I would actually recommend using Ubuntu or even Fedora over Debian, which has older dependencies like Mesa and other drivers.
-
For newer hardware like that, I would actually recommend using Ubuntu or even Fedora over Debian, which has older dependencies like Mesa and other drivers.
Any particular Ubuntu that suits the best?
Is Ubuntu 24.04.2 LTS ok?
-
Any of the Ubuntu 24.10 flavors would suffice. It comes down to what your desktop environment of choice is (GNOME, KDE Plasma, Xfce, etc.). Of course make sure you're using the X11 session as running MC with Wayland and XWayland may present other issues, especially if you're wanting to use KDE Plasma, theater view potentially, etc.
-
Any of the Ubuntu 24.10 flavors would suffice. It comes down to what your desktop environment of choice is (GNOME, KDE Plasma, Xfce, etc.). Of course make sure you're using the X11 session as running MC with Wayland and XWayland may present other issues, especially if you're wanting to use KDE Plasma, theater view potentially, etc.
"The latest version of the Ubuntu operating system for desktop PCs and laptops, Ubuntu 24.10 comes with nine months of security and maintenance updates, until July 2025."
Only 9 months? Isn't this a bummer?
Sorry to ask but what is that "Of course make sure you're using the X11 session as running MC with Wayland"?
-
The problem may not be Debian. Try starting in Standard View (ctrl-1) outside Theater View.
I do think that Zybex is right about a possible hardware issue. Can you get to the bios?
-
The problem may not be Debian. Try starting in Standard View (ctrl-1) outside Theater View.
I do think that Zybex is right about a possible hardware issue. Can you get to the bios?
OK. Yes, I'm in the BIOS right now. What do you want me to do please?
P.S. right now I cannot switch to Standard View because MC starts automatically after booting and in Theater View and my PC freezes immediately.
-
zybex suggested what to do in the BIOS.
You may be seeing the X11 problem Awesome Donkey described. Your desktop may matter.
-
"Can you enter the PC BIOS or type commands at the linux boot prompt? If that works then you'll need to enter linux in safe mode and look at logs to find out what's wrong. Or just reinstall from scratch, if you have backups."
I can enter the BIOS.
I cannot type any commands at the linux boot prompt (it takes 1s or so for the boot to end).
I tried starting in Safe/Rescue mode by pressing <shift> or <ESC> key before booting but it didn't work.
-
If the keyboard works in BIOS then it's likely a Debian issue - possibly related to the video driver hanging when Theater View starts. You need to get to the grub/lilo boot prompt (google for info) to start linux at a lower runlevel and disable MC from starting, or theater view from opening. You'll still need to find the underlying cause of the hang or install a different distro/driver set.
Also, try CTRL+ALT+F1 or CTRL+ALT+F2 after boot.
-
If the keyboard works in BIOS then it's likely a Debian issue - possibly related to the video driver hanging when Theater View starts. You need to get to the grub/lilo boot prompt (google for info) to start linux at a lower runlevel and disable MC from starting, or theater view from opening. You'll still need to find the underlying cause of the hang or install a different distro/driver set.
Also, try CTRL+ALT+F1 or CTRL+ALT+F2 after boot.
I'm trying... I'm trying but this thing boots so fast that I can't even see what's showing on the screen and I cannot stop the process. :(
I agree this might be a video driver thing because like I said this only started after I switched to Theater View.
CTRL+ALT+F1 or CTRL+ALT+F2 after boot didn't do anything.
I have a USB Live pen. Perhaps I can use it to login but then what should I do to prevent MC from starting in Theater View?
-
I have some good news. Following the instructions of zybex, I pressed CTRL+ALT+F1 as soon as the GNOME screen started and the system acknowledged by displaying my user (I have autologin setup).
Then I was able to enter with my pwd and although MC still started in Theater View, this time the PC didn't freeze!
So, I took the opportunity and configured MC to start in Standard View.
I have this error:
amdgpu 0000:0f:00.0: firmware: failed to load amdgpu/gc_11_0_1_mes_2.bin (-2)
So, this is what I did:
sudo nano /etc/apt/sources.list
Add this line if it’s not already there:
deb http://deb.debian.org/debian bookworm-backports main non-free-firmware
sudo apt update
sudo apt -t bookworm-backports install firmware-amd-graphics
sudo reboot
and now it looks good:
joaquim@HTPC:~$ sudo dmesg | grep -i firmware
[sudo] password for joaquim:
[ 3.412006] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_mes_2.bin
[ 3.412040] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_mes1.bin
[ 3.412984] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/psp_13_0_4_toc.bin
[ 3.413017] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/psp_13_0_4_ta.bin
[ 3.413166] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/dcn_3_1_4_dmcub.bin
[ 3.413168] [drm] Loading DMUB firmware via PSP: version=0x08003D00
[ 3.413199] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_imu.bin
[ 3.413243] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_pfp.bin
[ 3.413280] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_me.bin
[ 3.413308] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_rlc.bin
[ 3.413347] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_mec.bin
[ 3.413900] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/sdma_6_0_1.bin
[ 3.413974] amdgpu 0000:0f:00.0: firmware: direct-loading firmware amdgpu/vcn_4_0_2.bin
[ 3.413976] [drm] Found VCN firmware Version ENC: 1.21 DEC: 8 VEP: 0 Revision: 2
[ 3.413982] amdgpu 0000:0f:00.0: amdgpu: Will use PSP to load VCN firmware
[ 7.053065] r8169 0000:07:00.0: firmware: direct-loading firmware rtl_nic/rtl8125b-2.fw
joaquim@HTPC:~$
joaquim@HTPC:~$
joaquim@HTPC:~$
joaquim@HTPC:~$
joaquim@HTPC:~$ ls /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin
/lib/firmware/amdgpu/gc_11_0_1_mes_2.bin
Theater View now is working!!! All I need to do is some fine tuning as I see the thumbnails a bit larger than before and of course wait until I'm able to register MC.
I'm so happy I could cry :D
Thank you all for you help and patience!!!
-
And that's the main reason why I actually recommend not using Debian if using newer hardware that was released since the last stable Debian release, especially since the firmware isn't available/installed by default. Definitely not a fan of that.
Glad you got it sorted in the end. :)
-
Thanks! Every time I have to reinstall the OS and put MC on top I shiver...
-
I have another serious issue!
I can't play any video.
My HTPC is connected through HDMI to my Sony TV so this is what I chose:
(https://i.ibb.co/hFhRVvpc/Screenshot-from-2025-03-19-13-24-29.png) (https://ibb.co/hFhRVvpc) (https://i.ibb.co/k2Knw0Hs/Screenshot-from-2025-03-19-13-25-09.png) (https://ibb.co/k2Knw0Hs)
(https://i.ibb.co/jPt71tVM/error.jpg) (https://ibb.co/jPt71tVM)
I've tried all the other options where I see SONY TV to no avail as they all give the same fault.
I've even rebooted the PC...
-
Does it work in other apps like VLC, MPV, etc? I suspect it might be amdgpu driver related.
-
Let me install VLC and I'll let you know in a moment.
-
Does it work in other apps like VLC, MPV, etc? I suspect it might be amdgpu driver related.
VLC plays it just smoothly.
(https://i.ibb.co/LXxhD28p/Screenshot-from-2025-03-19-13-59-23.png) (https://ibb.co/LXxhD28p)
-
I have another serious issue!
I can't play any video.
My HTPC is connected through HDMI to my Sony TV so this is what I chose:
(https://i.ibb.co/hFhRVvpc/Screenshot-from-2025-03-19-13-24-29.png) (https://ibb.co/hFhRVvpc) (https://i.ibb.co/k2Knw0Hs/Screenshot-from-2025-03-19-13-25-09.png) (https://ibb.co/k2Knw0Hs)
(https://i.ibb.co/jPt71tVM/error.jpg) (https://ibb.co/jPt71tVM)
I've tried all the other options where I see SONY TV to no avail as they all give the same fault.
I've even rebooted the PC...
Is it connected to the internet? MC needs to download the libav video component to play video.
-
Is it connected to the internet? MC needs to download the libav video component to play video.
Yes, of course. I just got some cover art from the Internet a few minutes ago for some other files.
-
I may have found something in the Log or at least I see some error messages, namely this one in particular:
0035990: Playback: CJRVideoEngine::Open: FFmpeg DLLs are not available.
0035934: 140234557650880: Playback: CPlayerZone::Play: Start
0035934: 140232645514944: Playback: CPlayerZoneDisplayInfoLoadImageThread::Thread: Start
0035934: 140232645514944: Playback: CPlayerZoneDisplayInfoLoadImageThread::Thread: Image: 0000000000000000
0035934: 140232645514944: Playback: CPlayerZoneDisplayInfoLoadImageThread::Thread: Finish (0 ms)
0035934: 140234557650880: Playback: CPlayerZoneDisplayInfoUpdateThread::Destructor: Start
0035934: 140232263526080: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Finish (599138 ms)
0035954: 140234557650880: Playback: CPlayerZoneDisplayInfoUpdateThread::Destructor: Finish (20 ms)
0035957: 140234557650880: Playback: CPlayerZone::Play: Handling exclusive playback zones
0035957: 140234557650880: Playback: CPlayerZone::Play: Getting actual playback track
0035958: 140234557650880: Playback: CPlayerZone::Play: Processing play for '/mnt/Movies/Ficção científica/Venom - Let There Be Carnage (2021)/Venom - Let There Be Carnage (2021).mkv'
0035958: 140234557650880: Playback: CPlayerZone::Play: Updating internal track info
0035959: 140234557650880: Playback: CPlayerZone::Play: Playing: <XMLFN version="1.0"><Item Name="Filename">/mnt/Movies/Ficção científica/Venom - Let There Be Carnage (2021)/Venom - Let There Be Carnage (2021).mkv</Item><Item Name="FPS">23.9760208129882812</Item><Item Name="PlaylistIndex">0</Item><Item Name="AlbumSequentialWithLastTrack">0</Item><Item Name="HDR">DolbyVision Profile 8.1, HDR10-compatible</Item><Item Name="AspectRatio">1.78</Item><Item Name="DurationSeconds">5836</Item><Item Name="CenterFocusMixing">1</Item><Item Name="VolumeReset">1</Item><Item Name="ErrorFreeMode">0</Item><Item Name="VolumePeakLevels"></Item><Item Name="MediaType">Video</Item><Item Name="DatabaseKey">2570623</Item><Item Name="CompressionInfo">mkv video (video: hevc, audio: truehd)</Item><Item Name="VolumeTrackMaxSafeGain">-1</Item><Item Name="Bitrate">78075</Item><Item Name="Bookmark"></Item><Item Name="PlaybackInfo"></Item><Item Name="BlackBarCrop"></Item><Item Name="DRMProtected"></Item><Item Name="VolumeLeveling">0</Item><Item Name="DSP"></Item><Item Name="FileType">mkv</Item><Item Name="UserInterfaceModeChangeEventHandle">0000000000000000</Item></XMLFN>
0035959: 140234557650880: Playback: CJRPlaybackEngine::Play: Start
0035959: 140234557650880: Playback: CJRPlaybackEngine::StopInternal: Start
0035959: 140234557650880: Playback: CJRPlaybackEngine::StopInternal: Finish (0 ms)
0035959: 140234557650880: Playback: CJRPlaybackEngine::Play: Volume protection: 0
0035959: 140234557650880: Playback: CJRPlaybackEngine::Play: Playing: /mnt/Movies/Ficção científica/Venom - Let There Be Carnage (2021)/Venom - Let There Be Carnage (2021).mkv
0035959: 140234557650880: Playback: CJRPlaybackEngine::Play: Filetype: mkv; Type: 18; Can play: 1; Playback object: 0x55fab63f57f0
0035959: 140234557650880: Playback: CJRPlaybackEngine::StartPlayFile: Start
0035959: 140234557650880: Playback: DependencyInstaller::GetInstalledFilename: Dependency 'linux_avcodec64' (37) is missing, installing
0035959: 140234557650880: Playback: DependencyInstaller::Install: Start
0035959: 140232263526080: Reader: CCurlINetReader::OpenRange: Start
0035959: 140232263526080: Reader: CCurlINetReader::OpenRange: Opening URL, Position 0
0035959: 140232263526080: Reader: CCurlINetReader::Close: Start
0035959: 140232263526080: Reader: CCurlINetReader::Close: This 7f8a60001bc0, CleanClose 0
0035959: 140232263526080: Reader: CCurlINetReader::Close: Finish (0 ms)
0035966: 140232263526080: Reader: CCurlINetReader::OpenRange: Elapsed MS 5.7638, initial number of headers = 0, number of loops = 0
0035966: 140232263526080: Reader: CCurlINetReader::OpenRange: Open Succeeded. Elapsed MS 5.7730, number of headers = 0, number of loops = 0
0035966: 140232263526080: Reader: CCurlINetReader::OpenRange: CURL open returned error value = 6, error = Error
0035966: 140232263526080: Reader: CCurlINetReader::OpenRange: Finish (6 ms)
0035966: 140232263526080: Reader: CCurlINetReader::GetInfo: Start
0035966: 140232263526080: Reader: CCurlINetReader::GetInfo: Finish (0 ms)
0035966: 140232263526080: Reader: CCurlINetReader::GetInfo: Start
0035966: 140232263526080: Reader: CCurlINetReader::GetInfo: Finish (0 ms)
0035966: 140232263526080: Reader: CCurlINetReader::GetInfo: Start
0035966: 140232263526080: Reader: CCurlINetReader::GetInfo: Finish (0 ms)
0035966: 140232263526080: Reader: CCurlINetReader::Cancel: Start
0035966: 140232263526080: Reader: CCurlINetReader::Cancel: Finish (0 ms)
0035966: 140232263526080: Reader: CCurlINetReader::Close: Start
0035966: 140232263526080: Reader: CCurlINetReader::Close: This 7f8a60001bc0, CleanClose 5
0035966: 140232263526080: Reader: CCurlINetReader::Close: Finish (0 ms)
0035970: 140234557650880: Playback: DependencyInstaller::Install: Downloading package failed
0035970: 140234557650880: Playback: DependencyInstaller::Install: Finish (10 ms)
0035970: 140234557650880: Playback: DependencyInstaller::GetInstalledFilename: Failed installing dependency 37
0035970: 140234557650880: Playback: DependencyInstaller::GetInstalledFilename: Dependency 'linux_libplacebo64' (53) is missing, installing
0035970: 140234557650880: Playback: DependencyInstaller::Install: Start
0035970: 140232263526080: Reader: CCurlINetReader::OpenRange: Start
0035970: 140232263526080: Reader: CCurlINetReader::OpenRange: Opening URL, Position 0
0035970: 140232263526080: Reader: CCurlINetReader::Close: Start
0035970: 140232263526080: Reader: CCurlINetReader::Close: This 7f8a60001bc0, CleanClose 0
0035970: 140232263526080: Reader: CCurlINetReader::Close: Finish (0 ms)
0035976: 140232263526080: Reader: CCurlINetReader::OpenRange: Elapsed MS 4.7865, initial number of headers = 0, number of loops = 0
0035976: 140232263526080: Reader: CCurlINetReader::OpenRange: Open Succeeded. Elapsed MS 4.7959, number of headers = 0, number of loops = 0
0035976: 140232263526080: Reader: CCurlINetReader::OpenRange: CURL open returned error value = 6, error = Error
0035976: 140232263526080: Reader: CCurlINetReader::OpenRange: Finish (5 ms)
0035976: 140232263526080: Reader: CCurlINetReader::GetInfo: Start
0035976: 140232263526080: Reader: CCurlINetReader::GetInfo: Finish (0 ms)
0035976: 140232263526080: Reader: CCurlINetReader::GetInfo: Start
0035976: 140232263526080: Reader: CCurlINetReader::GetInfo: Finish (0 ms)
0035976: 140232263526080: Reader: CCurlINetReader::GetInfo: Start
0035976: 140232263526080: Reader: CCurlINetReader::GetInfo: Finish (0 ms)
0035976: 140232263526080: Reader: CCurlINetReader::Cancel: Start
0035976: 140232263526080: Reader: CCurlINetReader::Cancel: Finish (0 ms)
0035976: 140232263526080: Reader: CCurlINetReader::Close: Start
0035976: 140232263526080: Reader: CCurlINetReader::Close: This 7f8a60001bc0, CleanClose 5
0035976: 140232263526080: Reader: CCurlINetReader::Close: Finish (0 ms)
0035980: 140234557650880: Playback: DependencyInstaller::Install: Downloading package failed
0035981: 140234557650880: Playback: DependencyInstaller::Install: Finish (10 ms)
0035981: 140234557650880: Playback: DependencyInstaller::GetInstalledFilename: Failed installing dependency 53
0035985: 140234557650880: Playback: CJRVideoPlayerWindow::LayoutWindow: Start
0035985: 140234557650880: Playback: CJRVideoPlayerWindow::LayoutWindow: Getting rectangles
0035985: 140234557650880: Playback: CJRVideoPlayerWindow::LayoutWindow: Failed to get video rectangles
0035985: 140234557650880: Playback: CJRVideoPlayerWindow::LayoutWindow: Finish (0 ms)
0035985: 140234557650880: Playback: CJRVideoPlayerWindow::OpenFile: Start
0035985: 140234557650880: Playback: CJRVideoPlayerWindow::OpenFile: Filename: /mnt/Movies/Ficção científica/Venom - Let There Be Carnage (2021)/Venom - Let There Be Carnage (2021).mkv type: mkv. CJRVideoPlayerWindow 0x55fab7076e00
0035989: 140234557650880: General: CMCUICore::UpdateScreenResolution: Start
0035989: 140234557650880: General: CMCUICore::UpdateScreenResolution: Default fullscreen settings:
0035989: 140234557650880: General: CMCUICore::UpdateScreenResolution: Using playback settings: Desktop Settings
0035989: 140234557650880: General: JRMonitor::UpdateInfo: Start
0035990: 140234557650880: General: JRMonitor::UpdateInfo: Screen width = 3840 height = 2160 x = 0, y = 0, rrmode = 35
0035990: 140234557650880: General: JRMonitor::UpdateInfo: 1 non-zero size screens found
0035990: 140234557650880: General: JRMonitor::UpdateInfo: Finish (0 ms)
0035990: 140234557650880: Playback: CDisplaySettingsHelper::ChangeDisplaySettings: Start
0035990: 140234557650880: Playback: CDisplaySettingsHelper::ChangeDisplaySettings: Current Mode: 0x0x0x0, Target Mode: 0x0x0x0
0035990: 140234557650880: Playback: CDisplaySettingsHelper::ChangeDisplaySettings: Finish (result: 1) (0 ms)
0035990: 140234557650880: General: CMCUICore::UpdateScreenResolution: Finish (0 ms)
0035990: 140234557650880: Playback: CJRVideoEngine::Open: Start
0035990: 140234557650880: Playback: CJRVideoEngine::Open: FFmpeg DLLs are not available.
0035990: 140234557650880: Playback: CJRVideoEngine::Open: Finish (0 ms)
0035990: 140234557650880: Playback: CJRVideoPlayerWindow::OpenFile: Failed to open JR Video Player
0035990: 140234557650880: Playback: CJRVideoPlayerWindow::OpenFile: Finish (4 ms)
0035990: 140234557650880: Playback: CJRPlaybackEngine::StopInternal: Start
0035991: 140234557650880: Playback: CJRVideoEngine::~CJRVideoEngine: Start
0035991: 140234557650880: Playback: CJRVideoEngine::~CJRVideoEngine: Finish (0 ms)
0035991: 140234557650880: Playback: CJRPlaybackEngine::StopInternal: Finish (0 ms)
0035991: 140234557650880: Playback: CJRPlaybackEngine::StartPlayFile: Play returned: 0
0035991: 140234557650880: Playback: CJRPlaybackEngine::StartPlayFile: Finish (31 ms)
0035991: 140234557650880: Playback: CJRPlaybackEngine::Play: StartPlayFile returned 0
0035991: 140234557650880: Playback: CJRPlaybackEngine::Play: Finish (32 ms)
0035991: 140234557650880: Playback: CPlayerZone::PlayNextFile: bCanPlayNext=0, m_bPlaybackError=1
0035991: 140234557650880: Playback: CPlayerZoneDisplayInfoUpdateThreadPause::~CPlayerZoneDisplayInfoUpdateThreadPause: Start
0035991: 140234557650880: Playback: CPlayerZoneDisplayInfoUpdateThreadPause::~CPlayerZoneDisplayInfoUpdateThreadPause: Finish (0 ms)
0035991: 140234557650880: Playback: CPlayerZone::Play: Finish (57 ms)
0035991: 140232263526080: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Start
0035991: 140232263526080: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Zone: Video (id: 10001)
0035991: 140232645514944: Playback: CPlayerZoneDisplayInfoLoadImageThread::Thread: Start
0035992: 140234373199552: Import: CWatchFoldersThread::Thread: Wait result (1)
0035992: 140234373199552: Import: CWatchFoldersThread::Thread: Found changes
0035992: 140234373199552: Import: CWatchFoldersThread::Thread: Found changes in '/mnt/Movies/Ficção científica/Venom - Let There Be Carnage (2021)/Venom - Let There Be Carnage (2021).jpg'
0035993: 140234373199552: Import: CWatchFoldersThread::Thread: Success (looping again)
0036028: 140232645514944: Playback: CPlayerZoneDisplayInfoLoadImageThread::Thread: Image: 00007F8AB8010780
0036028: 140232645514944: Playback: CPlayerZoneDisplayInfoLoadImageThread::Thread: Finish (36 ms)
0036067: 140234557650880: General: CMCUICore::SystemPowerManager_UpdateActions: Start
0036067: 140234557650880: General: CMCUICore::SystemPowerManager_UpdateActions: UI Mode: -994; Playing: 1
0036067: 140234557650880: General: CMCUICore::SystemPowerManager_UpdateActions: Disabling screen power and saver for Theater View (based on user option)
0036067: 140234557650880: General: CMCUICore::SystemPowerManager_UpdateActions: Finish (result: 12) (0 ms)
0036067: 140234557650880: General: CSystemPowerManager::ApplyActionsToSystem: Setting screen saver off (timeout=0)
0036070: 140234557650880: General: CSystemPowerManager::OnCmd: Screen Saver Reset
0036070: 140234557650880: General: CSystemPowerManager::OnCmd: Screen Saver Reset
0036070: 140234557650880: General: CSystemPowerManager::OnCmd: Screen Saver Reset
0036070: 140234557650880: Playback: CPlayerZone::Stop: Start
0036070: 140234557650880: Playback: CPlayerZoneDisplayInfoUpdateThread::Destructor: Start
0036070: 140232263526080: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Finish (78 ms)
0036090: 140234557650880: Playback: CPlayerZoneDisplayInfoUpdateThread::Destructor: Finish (20 ms)
0036090: 140234557650880: Playback: CPlayerZone::Stop: Checking for not loaded playback engine
0036090: 140234557650880: Playback: CPlayerZone::Stop: Firing stop to playback engine
0036090: 140234557650880: Playback: CJRPlaybackEngine::StopInternal: Start
0036090: 140234557650880: Playback: CJRPlaybackEngine::StopInternal: Finish (0 ms)
0036090: 140234557650880: Playback: CPlayerZone::Stop: Processing internal previous / next
0036090: 140234557650880: Playback: CPlayerZone::Stop: Clearing display info
0036090: 140234557650880: Playback: CPlayerZone::Stop: Updating statistics
0036090: 140234557650880: Playback: CPlayerZone::Stop: Updating playback state
0036090: 140234557650880: Playback: CPlayerZone::Stop: Updating UI
0036090: 140234557650880: General: CMCUICore::UpdateScreenResolution: Start
0036091: 140234557650880: General: CMCUICore::UpdateScreenResolution: Default fullscreen settings:
0036091: 140234557650880: General: JRMonitor::UpdateInfo: Start
0036091: 140234557650880: General: JRMonitor::UpdateInfo: Screen width = 3840 height = 2160 x = 0, y = 0, rrmode = 35
0036091: 140234557650880: General: JRMonitor::UpdateInfo: 1 non-zero size screens found
0036091: 140234557650880: General: JRMonitor::UpdateInfo: Finish (0 ms)
0036091: 140234557650880: Playback: CDisplaySettingsHelper::ChangeDisplaySettings: Start
0036091: 140234557650880: Playback: CDisplaySettingsHelper::ChangeDisplaySettings: Current Mode: 0x0x0x0, Target Mode: 0x0x0x0
0036091: 140234557650880: Playback: CDisplaySettingsHelper::ChangeDisplaySettings: Finish (result: 1) (0 ms)
0036091: 140234557650880: General: CMCUICore::UpdateScreenResolution: Finish (0 ms)
0036091: 140234557650880: Playback: CPlayerZone::Stop: Applying database changes
0036091: 140234557650880: Playback: CPlayerZoneDisplayInfoUpdateThreadPause::~CPlayerZoneDisplayInfoUpdateThreadPause: Start
0036091: 140234557650880: Playback: CPlayerZoneDisplayInfoUpdateThreadPause::~CPlayerZoneDisplayInfoUpdateThreadPause: Finish (0 ms)
0036091: 140234557650880: Playback: CPlayerZone::Stop: Finish (21 ms)
0036091: 140232263526080: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Start
0036091: 140232263526080: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Zone: Video (id: 10001)
-
This might be the case...
So two essential components failed to download:
linux_avcodec64 → contains FFmpeg codecs
linux_libplacebo64 → used for HDR tonemapping and video rendering
🛠️ What's likely wrong:
JRiver cannot connect to the Internet or their package server, so it fails to auto-install the missing dependencies.
This may be due to:
DNS/network issues on your system
curl or certificate issues
JRiver’s internal download URLs being broken or redirected
JRiver’s Linux dependency servers being temporarily down
You’re running JRiver as a user that doesn’t have access to install files in its own directory tree
You tell me. 8)
-
May be caused by the recent server change:
https://yabb.jriver.com/interact/index.php/topic,140860.0.html
Try changing your DNS to 8.8.8.8.
-
May be caused by the recent server change:
https://yabb.jriver.com/interact/index.php/topic,140860.0.html
Try changing your DNS to 8.8.8.8.
OK. You mean something like this?
joaquim@HTPC:~$ nmcli connection show
NAME UUID TYPE DEVICE
Wired connection 1 79215a07-d88a-4170-9f53-f3a8e3d004e4 ethernet enp1s0f0
lo 85bb27ea-8d94-4cfc-ae99-c456ee8ba3e1 loopback lo
joaquim@HTPC:~$
joaquim@HTPC:~$
nmcli connection modify "Wired connection 1" ipv4.dns "8.8.8.8 8.8.4.4"
nmcli connection modify "Wired connection 1" ipv4.ignore-auto-dns yes
nmcli connection down "Wired connection 1" && nmcli connection up "Wired connection 1"
Well, I tried this and got very bad results as I totally lost internet access and didn't even get an IP assigned.
-
https://serverfault.com/a/1163117
There are different ways depending on your config.
-
Really wish the UI would inform the user when dependencies fail to download instead of silently failing.
-
Really wish the UI would inform the user when dependencies fail to download instead of silently failing.
-
https://serverfault.com/a/1163117
There are different ways depending on your config.
There are several different answers on this page. I've tried this one:
You need to install resolvconf.
sudo apt install resolvconf
Enable and Start the service resolvconf.
systemctl start resolvconf
systemctl enable resolvconf
systemctl status resolvconf
Update the file /etc/resolvconf/resolv.conf.d/head to have lines like:
nameserver 8.8.8.8
nameserver 8.8.4.4
Run the command:
resolvconf --enable-updates
resolvconf -u
Not sure how it went but the results although are different are far from ideal.
The video starts to play but there is this stupid artefact (?) like a water mark or something that simply doesn't go away. WTF is this?
(https://i.ibb.co/7tmT3Ccf/Screenshot-from-2025-03-19-16-52-07.png) (https://ibb.co/7tmT3Ccf) (https://i.ibb.co/0pVW6Qbs/Screenshot-from-2025-03-19-16-52-11.png) (https://ibb.co/0pVW6Qbs) (https://i.ibb.co/WWmZjC0j/Screenshot-from-2025-03-19-16-53-08.png) (https://ibb.co/WWmZjC0j)
-
This error "0035990: Playback: CJRVideoEngine::Open: FFmpeg DLLs are not available." and missing dependencies seem to have disappeared at least but that artefact is crazy. New JRiver logo?
I can upload the log but where to and how?
-
That seems to be another driver/firmware issue.
-
That seems to be another driver/firmware issue.
So what are the drivers/firmware that JRiver requires for Debian 12? Do I need VAAPI or ...?
BTW, I must stress that I didn't see any artifacts when playing the same video with VLC so this certainly looks something intrinsic to JRiver.
-
It may be one of the cases like I mentioned, the amdgpu driver in Debian 12 may be too old/outdated. Again, that's why I personally don't recommend using Debian 12 on newer hardware.
-
It may be one of the cases like I mentioned, the amdgpu driver in Debian 12 may be too old/outdated.
"BTW, I must stress that I didn't see any artifacts when playing the same video with VLC so this certainly looks something intrinsic to JRiver."
-
Well, MC isn't VLC (or MPV or any of those apps).
Have you tried rebooting? Also enable logging again and see if it says anything?
-
Well, MC isn't VLC (or MPV or any of those apps).
Have you tried rebooting? Also enable logging again and see if it says anything?
Yes, I've rebooted and the logging says a lot of things but I'm no developer and simply cannot copy the more than 4000 lines here. Where can I send it to?
-
https://pastebin.com/ is a good place for large logs. :)
-
Log here:
https://drive.google.com/file/d/1UbfFLExTA3S3fh9jjclG-N4MQ_IBa147/view?usp=drive_link
-
I'm about to give up and considering installing Ubuntu Desktop 24.04.2 LTS (I prefer this vs. the 24.10 due to the extended support).
Just for the sake of curiosity I tried to play another video and it started with no artifacts but then I tried to fast forward it to a next chapter and the screen went totally black and I couldn't get out of it! It's too much problems to handle!
Before you say it, again the initial video plays fine with VLC.
-
I prefer this vs. the 24.10 due to the extended support
If you went Ubuntu 24.10 all you'd have to do is just update to Ubuntu 25.04 when it comes out next month, then 25.10 when it comes out in October (this makes support timeframe reset). Personally, I'm not really a fan of the LTS versions of Ubuntu, they can also get a bit too out-of-date quickly if you're using newer hardware.
-
If you went Ubuntu 24.10 all you'd have to do is just update to Ubuntu 25.04 when it comes out next month, then 25.10 when it comes out in October (this makes support timeframe reset). Personally, I'm not really a fan of the LTS versions of Ubuntu, they can also get a bit too out-of-date quickly if you're using newer hardware.
I might do that but considering the nightmare I'm going through with the upgrade and the changing of the HW, will that next upgrade from 24.10 to 25.04 be entirely automatic or do I need to struggle again?
-
Well, you'd be prompted there's an update. The upgrade process is usually pretty straightforward, e.g. this was the process from 24.04 to 24.10: https://www.technewsworld.com/story/upgrading-to-ubuntu-24-10-oracular-oriole-step-by-step-guide-177442.html
-
"BTW, I must stress that I didn't see any artifacts when playing the same video with VLC so this certainly looks something intrinsic to JRiver."
This is irrelevant - different applications can use different features provided by the GPU driver. MC expects a minimum feature set to be present, VLC uses a different set. That's all.
If you run different games on your machine, you may find that some of them don't work. The fact that game A works doesn't mean that game B must also work...
-
I'm sorry to say but I'm totally p*ssed now. >:(
I've installed Ubuntu 24.04.2 LTS and the issue with the artifact remains!!!
(https://i.ibb.co/h1r8yn9R/Screenshot-from-2025-03-19-22-07-33.png) (https://ibb.co/h1r8yn9R)
So, what now?
I've asked ChatGPT for help "This same video plays perfectly fine in VLC as I told you, on the same computer. It is just when JRiver is playing it that I see those." and...
ChatGPT said:
Thanks — that’s a really important clue.
If VLC plays it perfectly on the same system, then we can confidently say: ✅ Your drivers, hardware, and codecs are fine.
❌ The issue is clearly in how JRiver is handling video playback on Linux, either with hardware acceleration or its rendering path.
🔍 What this likely means:
JRiver on Linux still isn't as mature or optimized as its Windows counterpart, especially when it comes to:
Video rendering backends (OpenGL, Vulkan, etc.)
Hardware acceleration layers (VAAPI, VDPAU, DRM/GBM)
Tone mapping / HDR handling
Frame timing / sync
-
Found it, uncheck this:
Options > Video > JRVR Settings > Advanced > Debugging: Visualize Tonemapping LUT
It's showing the HDR tone map that is being applied for HDR files :)
-
Found it, uncheck this:
Options > Video > JRVR Settings > Advanced > Debugging: Visualize Tonemapping LUT
It's showing the HDR tone map that is being applied for HDR files :)
Well done!!! Are these settings OK now?
(https://i.ibb.co/qFCf3X4m/Screenshot-from-2025-03-19-23-36-59.png) (https://ibb.co/qFCf3X4m)
(https://i.ibb.co/7dN9NqTV/Screenshot-from-2025-03-19-23-15-34.png) (https://ibb.co/7dN9NqTV) (https://i.ibb.co/v62bHs6g/Screenshot-from-2025-03-19-23-18-50.png) (https://ibb.co/v62bHs6g)
In the meanwhile I've found some bug with the display of some windows that randomly appear so small than one needs a magnifier to see them.
Check this out:
(https://i.ibb.co/S4gSnrHG/circulo.jpg) (https://ibb.co/S4gSnrHG)
Believe it or not, that "thing" is the window with the settings.
I hope this shows better what I'm trying to say:
(https://i.ibb.co/JWJXQ1wh/circlulo2.jpg) (https://ibb.co/JWJXQ1wh) (https://i.ibb.co/YFRxrpbH/circlulo3.jpg) (https://ibb.co/YFRxrpbH)
-
The thing with dialogs and windows appearing shrunk/small is a known MC issue if you're using the Wayland session of your Linux distro (which is the default now for many distros including Ubuntu). MC only supports X11 and doesn't support Wayland however it can run on Wayland thanks to XWayland, though it has issues like this. If you can live with it and know how to resize the shrunk windows, it's fine. But if it bothers you too much you can 'fix' it by switching to Ubuntu's X11 session.
To switch to the X11 session, all you have to do is log out. Then on the login screen where it asks you to input your password click on the gear on the bottom right and select Ubuntu on Xorg and log in normally. It should be using the X11 session then though you can always switch back to Wayland by repeating the steps and switching from Ubuntu on Xorg to Ubuntu. You can always verify if you're using X11 or Wayland by opening the Settings app and going to the System section then About then System Details. It'll popup a window with information including what windowing system you're using (X11 or Wayland).
Personally, I use the Wayland session (since X11 AKA Xorg Server is basically dead now and Wayland is the future) and so I expect these issues with small dialogs when using MC. I do hope it's something that can somehow be fixed in MC (as I don't think MC supporting Wayland is happening anytime soon realistically) at some point in the future.
-
The thing with dialogs and windows appearing shrunk/small is a known MC issue if you're using the Wayland session of your Linux distro (which is the default now for many distros including Ubuntu). MC only supports X11 and doesn't support Wayland and requires XWayland in order to function on Wayland, though it has issues like this. If you can live with it and know how to resize the shrunk windows, it's fine. But if it bothers you too much you can 'fix' it by switching to the X11 session.
To switch to the X11 session, all you have to do is log out. Then on the login screen where it asks you to input your password click on the gear on the bottom right and select Ubuntu on Xorg and log in normally. It should be using the X11 session then though you can always switch back to Wayland by repeating the steps and switching from Ubuntu on Xorg to Ubuntu. You can always verify if you're using X11 or Wayland by opening the Settings app and going to the System section then About then System Details. It'll popup a window with information including what windowing system you're using (X11 or Wayland).
I've changed to X11 as you can see but the issue remains:
(https://i.ibb.co/QvSSkRjJ/Screenshot-from-2025-03-20-00-01-29.png) (https://ibb.co/QvSSkRjJ) (https://i.ibb.co/BVt0qbBr/Screenshot-from-2025-03-20-00-02-00.png) (https://ibb.co/BVt0qbBr)
(https://i.ibb.co/Z6Z1fMRJ/Screenshot-from-2025-03-20-00-05-56.png) (https://ibb.co/Z6Z1fMRJ)
-
Maybe it's a scaling issue then. Bob would have to chime in on this one.
-
OK. This is something I can live with. It doesn't bother me that much as I won't be doing much configurations after all is set and ready.
I'm more concerned about getting the best settings for my HW, more specifically for video playing as there are a LOT of options to select...
-
This is irrelevant - different applications can use different features provided by the GPU driver. MC expects a minimum feature set to be present, VLC uses a different set. That's all.
If you run different games on your machine, you may find that some of them don't work. The fact that game A works doesn't mean that game B must also work...
Correct and if it's trying to use the noveau X driver it'll never work.