Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ilektranik]

MC31 on Ubuntu 22.04 LTS.

Imported a few files then crashed. Crashes when trying to import more files.

Crashes when trying to play any of the few imported files.

This doesn't bode well.

[ilektranik]

MediaCenter-31.0.48-amd64.deb

Uninstalled. Reinstalled. No help.

Crashes in seconds no matter what.

[JimH]

Ubuntu isn't officially supported, but did you try installJRMC?
https://yabb.jriver.com/interact/index.php/topic,135999.0.html

[bob]

Sounds like a corrupt media file. Try turning on logging.

[ilektranik]

I suspect it may be the /path/ to the music files.

By the way, the files I have been using with jriver on Ubuntu for a decade. All play fine on MC26 under Ubuntu 18.04 LTS, which is no longer supported with security updates.

Unfortunately, MC31 won't stay active long enough to change settings.

[mattkhan]

Look in dmesg for any info
Start from shell and see what the error is

[Awesome Donkey]

9 times out of 10 when MC crashes, it's due to bad files. Especially if import is currently running and then it happens.

Enabling logging in MC then reproducing the crash then looking at the log file to see what the last file MC was trying to import will help with narrowing down the bad files.

[BryanC]

I suspect it may be the /path/ to the music files.

By the way, the files I have been using with jriver on Ubuntu for a decade. All play fine on MC26 under Ubuntu 18.04 LTS, which is no longer supported with security updates.

Unfortunately, MC31 won't stay active long enough to change settings.

I'll echo the crowd that reproducible crashes such as yours are usually caused by some malformed file during import. There have been changes in the interim in regards to how "intensely" files are scanned during import to improve metadata extraction, therefore portions of files that may have been silently skipped over in previous versions are now rearing their ugly heads. If you can isolate the problematic file and send it with a log to logs@jriver.com I bet you will get sorted out quickly. If you are having problems keeping MC open, I would temporarily backup (move) the "~/.jriver/Media Center 31" library directory, restart MC, enable logging, and then run an import of your media library to identify the culprit. Once that is done, remove the problematic file and restore your library directory.

[ilektranik]

Here's the crash report. I'd include the /var/crash/_usr_bin_mediacenter31.1000.crash but it's way too large after just one crash.

Memory segmentation fault.

If an application does that, it's programming. If an application can read a file that does that, it's programming. If an application does not fail gracefully ... programming.

Simply no time to comb 11 TB of music so I may partially use a music library on buggy software.

If you fix it someday, great. Till then I'll consider it a $33.98 lesson in caveat emptor.

[Awesome Donkey]

You need to enable logging in MC itself, then reproduce the crash, and then look at the log that MC generates to see what the last file(s) being imported were, which is usually the file(s) causing MC to crash. I don't think a crash report like that can really help that much (other than saying the app it crashing, which is obvious), unless you know what file(s) are causing the crashes.

https://wiki.jriver.com/index.php/Logging

[bob]

Here's the crash report. I'd include the /var/crash/_usr_bin_mediacenter31.1000.crash but it's way too large after just one crash.

Memory segmentation fault.

If an application does that, it's programming. If an application can read a file that does that, it's programming. If an application does not fail gracefully ... programming.

Simply no time to comb 11 TB of music so I may partially use a music library on buggy software.

If you fix it someday, great. Till then I'll consider it a $33.98 lesson in caveat emptor.

Try the latest build. There were some fixes that might be related.