INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: MC 34.24 failing to start  (Read 336 times)

Ekpen

  • Citizen of the Universe
  • *****
  • Posts: 693
MC 34.24 failing to start
« on: May 16, 2025, 07:16:39 pm »
hello:
Ubuntu 25.04.
MC failed to start.
No luck with re installing.
thanks.
George Omoregie
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 8411
  • The color of Spring!
Re: MC 34.24 failing t start
« Reply #1 on: May 16, 2025, 07:55:23 pm »
Start it from the terminal with the /BuiltInBrowser switch.

mediacenter34 /BuiltInBrowser
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 25.04 Plucky Puffin 64-bit (AMD 7900X CPU/AMD 7800 XT GPU/64GB RAM/2TB M.2 NVMe SSD)
macOS Sequoia 15.4.1 (M4 Mac Mini 16GB RAM/256GB SSD)
Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 34 (Windows + Mac + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

Ekpen

  • Citizen of the Universe
  • *****
  • Posts: 693
Re: MC 34.24 failing t start
« Reply #2 on: May 17, 2025, 02:33:03 pm »
Thanks for the quick response and help.

Below is the result.

Segmentation fault (core dumped)

George Omoregie

Logged

rexb1971

  • Recent member
  • *
  • Posts: 6
Re: MC 34.24 failing t start
« Reply #3 on: May 18, 2025, 01:44:20 pm »
I receive the same segmentation fault error when using the /BuiltInBrowser option on Ubuntu Studio 24.10
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 8411
  • The color of Spring!
Re: MC 34.24 failing t start
« Reply #4 on: May 18, 2025, 02:46:51 pm »
What GPU is being used? You'll probably have to wait for Bob to respond.

Segfaults are sometimes hard to track down and may require you to run MC through gdb in the terminal to get more info about where it's failing exactly. How to run MC34 through gdb you do the following in a Terminal...

Code: [Select]
gdb mediacenter34
If it asks whether or not to enable debuginfod for the session put in y and hit Enter, then you'll see it say (gdb). When you see this type in run and press Enter and it should start to run MC34 and then it should segfault again but this time it should display more information about the segfault. Copy and paste and post that info here.
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 25.04 Plucky Puffin 64-bit (AMD 7900X CPU/AMD 7800 XT GPU/64GB RAM/2TB M.2 NVMe SSD)
macOS Sequoia 15.4.1 (M4 Mac Mini 16GB RAM/256GB SSD)
Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 34 (Windows + Mac + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

rexb1971

  • Recent member
  • *
  • Posts: 6
Re: MC 34.24 failing to start
« Reply #5 on: May 20, 2025, 10:35:27 am »
My GPU is a NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

Here is the output of the gdb command:
                                                                                                                                         
[New Thread 0x7ffff37ff6c0 (LWP 161929)]                                                                                                                                                                                                       
[New Thread 0x7ffff2ffe6c0 (LWP 161930)]
[Thread 0x7ffff37ff6c0 (LWP 161929) exited]
[Detaching after vfork from child process 161931]
Downloading separate debug info for /usr/lib/jriver/Media Center 34/libJRDisc.so
[New Thread 0x7ffff37ff6c0 (LWP 161938)]                                                                                                                                                                                                       
[Detaching after fork from child process 161940]
[New Thread 0x7ffff198e6c0 (LWP 161955)]

Thread 1 "mediacenter34" received signal SIGSEGV, Segmentation fault.
0x00005555561c20a9 in ?? ()
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 8411
  • The color of Spring!
Re: MC 34.24 failing to start
« Reply #6 on: May 20, 2025, 10:57:55 am »
Bob said the segfaults could because of corrupt settings files. Try what he suggested here: https://yabb.jriver.com/interact/index.php/topic,141310.msg980605.html#msg980605
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 25.04 Plucky Puffin 64-bit (AMD 7900X CPU/AMD 7800 XT GPU/64GB RAM/2TB M.2 NVMe SSD)
macOS Sequoia 15.4.1 (M4 Mac Mini 16GB RAM/256GB SSD)
Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 34 (Windows + Mac + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

rexb1971

  • Recent member
  • *
  • Posts: 6
Re: MC 34.24 failing to start
« Reply #7 on: May 20, 2025, 11:09:36 am »
Removed both of the settings files, ran gdb mediacenter34 with the built in browser option and got this:

0520/110809.842526:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
FFF9F9F9 Start bcolor F9F9F9 nColor
[0520/110809.915611:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[0520/110809.918005:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[0520/110809.970289:WARNING:policy_logger.cc(151)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(88) Could not create policy manager as CBCM is not enabled.
[0520/110810.057085:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[0520/110810.127879:WARNING:angle_platform_impl.cc(49)] RendererVk.cpp:1962 (initialize): ANGLE VMA version: 2003000
[New Thread 0x7fffe9b816c0 (LWP 181351)]
[0520/110810.163094:WARNING:sandbox_linux.cc(400)] InitializeSandbox() called with multiple threads in process gpu-process.

Thread 1 "mediacenter34" received signal SIGSEGV, Segmentation fault.
0x00005555561c20a9 in ?? ()
Logged

rexb1971

  • Recent member
  • *
  • Posts: 6
Re: MC 34.24 failing to start
« Reply #8 on: May 20, 2025, 05:03:40 pm »
Tried it again, and in addition to the previous output, it included these lines after the segmentation fault:
(gdb) [0520/152951.107775:WARNING:angle_platform_impl.cc(49)] RendererVk.cpp:1962 (initialize): ANGLE VMA version: 2003000
free(): double free detected in tcache 2
[0520/152951.229402:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[0520/153006.232016:INFO:child_thread_impl.cc(926)] ChildThreadImpl::EnsureConnected()

And it just kind of hung there at that point, never closing out the command, indicating that it might not be a 'crash' so much as a process gone out of control. Perhaps.
Logged

rexb1971

  • Recent member
  • *
  • Posts: 6
Re: MC 34.24 failing to start
« Reply #9 on: Yesterday at 05:07:04 pm »
After looking through some other recent forum questions about segmentation faults, I decided to try loading X11 instead of Wayland - and JRiver Media Center loaded up without issue. Just figured I'd let you know my resolution.
Logged
Pages: [1]   Go Up
« previous next »