More > JRiver Media Center 24 for Linux

MC24 Crash on Folder Import [Solved]

<< < (5/7) > >>

bob:
Try this build please, I couldn't get it to crash but I made a change off of an educated guess...
http://files.jriver.com/mediacenter/test/MediaCenter-24.0.45-2-amd64.deb

Scobie:
Thanks Bob I will try that update later this morning.

In answer to your earlier query, I grabbed the following:

server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
    Vendor: VMware, Inc. (0xffffffff)
OpenGL vendor string: VMware, Inc.

00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04)
   Subsystem: Red Hat, Inc QEMU Virtual Machine
   Kernel driver in use: qxl
   Kernel modules: qxl
   
   Linux JRiverMC 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux

   /usr/bin/cinnamon-session  /usr/bin/dbus-run-session

Scobie:
Thanks Bob but no joy.

Updated to 45-02 but behaviour is the same.

MC crashes and the following gets written to the messages.log:

Aug  1 10:18:04 JRiverMC /cinnamon-killer-daemon: Bound Cinnamon restart to <Control><Alt>Escape.
Aug  1 10:20:10 JRiverMC gvfsd-network[1400]: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
Aug  1 10:20:10 JRiverMC gvfsd-network[1400]: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
Aug  1 10:20:10 JRiverMC gvfsd-network[1400]: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Operation not supported by backend
Aug  1 10:20:17 JRiverMC kernel: [ 1729.951982] mediacenter24[1088]: segfault at 0 ip 0000000001250a38 sp 00007ffea1cb1558 error 4 in mediacenter24[400000+1619000]

Scobie:
Quick update, the error in the log is not peculiar to MC, a google search shows it occurs for other apps / use cases.

One of these was fixed by a Python package, installed this no change.

Another was samba related. To check this I loaded the debian host with no NAS folder mount point and pointed the import to a local folder and MC still crashed.

The log entry may be a red herring, or a normal crash entry.

Cheers

Scobie:


After changing the video resolution of the Debian host the import actually worked a couple of times...but has now crashed again. Maybe something to do with reinitialising the video settings?

Navigation

[0] Message Index

[#] Next page

[*] Previous page