INTERACT FORUM

Please login or register.

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

Author Topic: segmentation fault on Ubuntu 14.04 64 bit [Solved]  (Read 5725 times)

linuxuser200

  • Recent member
  • *
  • Posts: 12
segmentation fault on Ubuntu 14.04 64 bit [Solved]
« on: January 22, 2015, 11:31:54 pm »

Hi,

I am running Ubuntu 14.04 64 bit with KDE. I am using NVidia proprietary drivers and have 2 monitors attached.

I have a licensed copy of Media Center 20 with a universal licence. The licence appears to be accepted.

I have followed the instructions on this page: http://yabb.jriver.com/interact/index.php?topic=87051.0
I am running Media Center version 20.0.58.

The program crashes after about 9 seconds when I start it from the command line. I see no windows at all - although I can see the Media Center icon in the task bar so it's possible that the window is offscreen.

This is what I get at the command line:

$ mediacenter20
Found 0 devices (devices will be listed below)

Total time: 2 ms
Result: 0
Segmentation fault (core dumped)


This is logged in syslog:

Jan 23 18:18:36 ciprian-desktop kernel: [923393.150933] mediacenter20[10640]: segfault at 0 ip 00000000f5261a49 sp 00000000ff818d10 error 4 in libJRReader.so[f51c8000+48b000]


I tried opening the core file generated - this is the call stack I get, which of course does not have any symbols so I'm not sure of how much use it will be:

ciprian@ciprian-desktop:~$ gdb  `which mediacenter20` ./core
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/mediacenter20...(no debugging symbols found)...done.
[New LWP 10149]
[New LWP 10161]
[New LWP 10158]
[New LWP 10177]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `mediacenter20'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xf52dfa49 in ?? () from /usr/lib/jriver/Media Center 20/libJRReader.so
(gdb) bt
#0  0xf52dfa49 in ?? () from /usr/lib/jriver/Media Center 20/libJRReader.so
#1  0x089745a7 in ?? ()
#2  0x089f7b07 in ?? ()
#3  0x089f808f in ?? ()
#4  0x08972f9b in ?? ()
#5  0x089733f9 in ?? ()
#6  0x084b11aa in ?? ()
#7  0x0807452c in ?? ()
#8  0x0847677b in ?? ()
#9  0x08476f2a in ?? ()
#10 0x08103e6f in ?? ()
#11 0xf68d3d04 in ?? () from /usr/lib/jriver/Media Center 20/libJRTools.so
#12 0xf6946409 in ?? () from /usr/lib/jriver/Media Center 20/libJRTools.so
#13 0xf6945d38 in ?? () from /usr/lib/jriver/Media Center 20/libJRTools.so
#14 0xf68bb38b in ?? () from /usr/lib/jriver/Media Center 20/libJRTools.so
#15 0xf68cb33b in ?? () from /usr/lib/jriver/Media Center 20/libJRTools.so
#16 0x08c034bc in ?? ()
#17 0x08c02d5a in ?? ()
#18 0x08056a7d in ?? ()
#19 0xf6ec8a83 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#20 0x08057251 in ?? ()



Any ideas?

Thanks.
Logged

linuxuser200

  • Recent member
  • *
  • Posts: 12
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #1 on: January 23, 2015, 12:00:55 am »

Hi,

Another note: I was able to see the main window by right-clicking on the icon in the KDE task bar and selecting "full screen". However the window closes very quickly (under 10 seconds) and I can't do much in that time. I was able to click on some menus - I opened the registration info dialog and the licence info appears fine.

Any tests I can do to narrow down this problem?

Thanks.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71470
  • Where did I put my teeth?
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #2 on: January 23, 2015, 06:35:34 am »

Welcome to the forum and thanks for the purchase.  Here is a thread on Ubuntu.
http://yabb.jriver.com/interact/index.php?topic=87051.0
Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5177
  • "Linux Merit Badge" Recipient
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #3 on: January 23, 2015, 07:22:04 am »

The most common cause of a segfault on start is missing dependencies; you might want to have a look at some of the other segfault threads on the board, in particular this one looks similar: http://yabb.jriver.com/interact/index.php?topic=92149.0.

What's the output of the following commands:

Code: [Select]
ldd /usr/bin/mediacenter20
ldd /usr/lib/jriver/Media\ Center\ 20/libJRReader.so
ldd /usr/lib/jriver/Media\ Center\ 20/libJRTools.so
Logged

linuxuser200

  • Recent member
  • *
  • Posts: 12
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #4 on: January 25, 2015, 11:02:35 pm »

Hi Jim, mwillems,

Thanks for your responses.

I have followed the instructions on the Ubuntu page - I think I have installed all dependencies but if there are any I have missed I have not been able to determine what's missing.

Here's the ldd output of the main libraries and executable:

Code: [Select]
$ ldd /usr/bin/mediacenter20
        linux-gate.so.1 =>  (0xf76fa000)
        libcryptlib.so => /usr/lib/jriver/Media Center 20/libcryptlib.so (0xf738c000)
        libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7340000)
        librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf7336000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7331000)
        libboost_regex.so.1.54.0 => /usr/lib/jriver/Media Center 20/libboost_regex.so.1.54.0 (0xf727e000)
        libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf714a000)
        libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xf7144000)
        libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf705a000)
        libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7014000)
        libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf6ff7000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf6e48000)
        /lib/ld-linux.so.2 (0xf76fb000)
        libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf6e26000)
        libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf6e21000)
        libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf6e1a000)

Code: [Select]
$ ldd /usr/lib/jriver/Media\ Center\ 20/libJRReader.so
        linux-gate.so.1 =>  (0xf7783000)
        libcryptlib.so => /usr/lib/jriver/Media Center 20/libcryptlib.so (0xf6f6b000)
        libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf6f1f000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf6f19000)
        librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf6f10000)
        libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xf6f0a000)
        libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf6dd6000)
        libboost_regex.so.1.54.0 => /usr/lib/jriver/Media Center 20/libboost_regex.so.1.54.0 (0xf6d23000)
        libp11-kit.so.0 => /usr/lib/i386-linux-gnu/libp11-kit.so.0 (0xf6ce6000)
        libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf6bfd000)
        libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf6bb7000)
        libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf6b9a000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf69eb000)
        /lib/ld-linux.so.2 (0xf7784000)
        libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf69c8000)
        libffi.so.6 => /usr/lib/i386-linux-gnu/libffi.so.6 (0xf69c1000)
        libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf69bd000)
        libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf69b6000)

Code: [Select]
$ ldd /usr/lib/jriver/Media\ Center\ 20/libJRTools.so
        linux-gate.so.1 =>  (0xf7797000)
        libcryptlib.so => /usr/lib/jriver/Media Center 20/libcryptlib.so (0xf6ff8000)
        libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf6fac000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf6fa6000)
        librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf6f9d000)
        libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xf6f97000)
        libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf6e63000)
        libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf6e50000)
        libboost_regex.so.1.54.0 => /usr/lib/jriver/Media Center 20/libboost_regex.so.1.54.0 (0xf6d9c000)
        libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 (0xf692d000)
        libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 (0xf6821000)
        libgobject-2.0.so.0 => /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 (0xf67cf000)
        libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf66e6000)
        libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf669f000)
        libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf6682000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf64d3000)
        /lib/ld-linux.so.2 (0xf7798000)
        libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf64b1000)
        libgdk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 (0xf6402000)
        libgmodule-2.0.so.0 => /usr/lib/i386-linux-gnu/libgmodule-2.0.so.0 (0xf63fc000)
        libpangocairo-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0 (0xf63ef000)
        libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xf63e9000)
        libatk-1.0.so.0 => /usr/lib/i386-linux-gnu/libatk-1.0.so.0 (0xf63c8000)
        libcairo.so.2 => /usr/lib/i386-linux-gnu/libcairo.so.2 (0xf62a5000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/i386-linux-gnu/libgdk_pixbuf-2.0.so.0 (0xf6281000)
        libgio-2.0.so.0 => /usr/lib/i386-linux-gnu/libgio-2.0.so.0 (0xf6100000)
        libpangoft2-1.0.so.0 => /usr/lib/i386-linux-gnu/libpangoft2-1.0.so.0 (0xf60ea000)
        libpango-1.0.so.0 => /usr/lib/i386-linux-gnu/libpango-1.0.so.0 (0xf609d000)
        libfontconfig.so.1 => /usr/lib/i386-linux-gnu/libfontconfig.so.1 (0xf6062000)
        libpcre.so.3 => /lib/i386-linux-gnu/libpcre.so.3 (0xf6023000)
        libffi.so.6 => /usr/lib/i386-linux-gnu/libffi.so.6 (0xf601c000)
        libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf6018000)
        libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf6011000)
        libXrender.so.1 => /usr/lib/i386-linux-gnu/libXrender.so.1 (0xf6006000)
        libXinerama.so.1 => /usr/lib/i386-linux-gnu/libXinerama.so.1 (0xf6001000)
        libXi.so.6 => /usr/lib/i386-linux-gnu/libXi.so.6 (0xf5ff0000)
        libXrandr.so.2 => /usr/lib/i386-linux-gnu/libXrandr.so.2 (0xf5fe5000)
        libXcursor.so.1 => /usr/lib/i386-linux-gnu/libXcursor.so.1 (0xf5fda000)
        libXcomposite.so.1 => /usr/lib/i386-linux-gnu/libXcomposite.so.1 (0xf5fd6000)
        libXdamage.so.1 => /usr/lib/i386-linux-gnu/libXdamage.so.1 (0xf5fd1000)
        libfreetype.so.6 => /usr/lib/i386-linux-gnu/libfreetype.so.6 (0xf5f31000)
        libpixman-1.so.0 => /usr/lib/i386-linux-gnu/libpixman-1.so.0 (0xf5e87000)
        libpng12.so.0 => /lib/i386-linux-gnu/libpng12.so.0 (0xf5e5f000)
        libxcb-shm.so.0 => /usr/lib/i386-linux-gnu/libxcb-shm.so.0 (0xf5e5b000)
        libxcb-render.so.0 => /usr/lib/i386-linux-gnu/libxcb-render.so.0 (0xf5e50000)
        libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf5e36000)
        libselinux.so.1 => /lib/i386-linux-gnu/libselinux.so.1 (0xf5e13000)
        libresolv.so.2 => /lib/i386-linux-gnu/libresolv.so.2 (0xf5dfb000)
        libharfbuzz.so.0 => /usr/lib/i386-linux-gnu/libharfbuzz.so.0 (0xf5da5000)
        libthai.so.0 => /usr/lib/i386-linux-gnu/libthai.so.0 (0xf5d9a000)
        libexpat.so.1 => /lib/i386-linux-gnu/libexpat.so.1 (0xf5d71000)
        libgraphite2.so.3 => /usr/lib/i386-linux-gnu/libgraphite2.so.3 (0xf5d55000)
        libdatrie.so.1 => /usr/lib/i386-linux-gnu/libdatrie.so.1 (0xf5d4c000)

I have also attached the log file, in case it helps.

I have had a look at other segfault posts, two of which appear similar to mine:

1. http://yabb.jriver.com/interact/index.php?topic=92149.0
In this thread there is a mention of p11-kit. However I have the library installed here:
/usr/lib/i386-linux-gnu/libp11-kit.so.0 (symlink to /usr/lib/i386-linux-gnu/libp11-kit.so.0.0.0)

2. http://yabb.jriver.com/interact/index.php?action=printpage;topic=93611.0
This crash appears to be identical to mine. The other similarity is that I also have an NVidia card.
However I think I have the right libGL library installed:
/usr/lib32/nvidia-331-updates/libGL.so.1 (symlink to /usr/lib32/nvidia-331-updates/libGL.so.331.113).


Thanks for your help.
Logged

linuxuser200

  • Recent member
  • *
  • Posts: 12
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #5 on: January 25, 2015, 11:16:54 pm »

I have also run strace as one of the other posters has done, which helped him identify the problem.

I have attached the full strace output but here's the last part:

Code: [Select]
...
clock_gettime(CLOCK_MONOTONIC, {1181299, 837477250}) = 0
setsockopt(17, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
setsockopt(17, SOL_SOCKET, SO_RCVBUF, [32768], 4) = 0
bind(17, {sa_family=AF_INET, sin_port=htons(52100), sin_addr=inet_addr("0.0.0.0")}, 16) = 0
listen(17, 128)                         = 0
clone(child_stack=0xefdff3e4, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0xefdffba8, tls=0xefdffba8, child_tidptr=0xff850ad0) = 12502
gettimeofday({1422248200, 127540}, NULL) = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 19
socket(PF_NETLINK, SOCK_RAW, 0)         = 20
bind(20, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
getsockname(20, {sa_family=AF_NETLINK, pid=12451, groups=00000000}, [12]) = 0
time(NULL)                              = 1422248200
sendto(20, "\24\0\0\0\22\0\1\3\10\311\305T\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"d\4\0\0\20\0\2\0\10\311\305T\2430\0\0\0\0\4\3\1\0\0\0I\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 3388
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"l\4\0\0\20\0\2\0\10\311\305T\2430\0\0\0\0\1\0\4\0\0\0C\20\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 3420
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"T\4\0\0\20\0\2\0\10\311\305T\2430\0\0\0\0\0\2\24\0\0\0\321\20\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 1108
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\10\311\305T\2430\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
sendto(20, "\24\0\0\0\26\0\1\3\t\311\305T\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"D\0\0\0\24\0\2\0\t\311\305T\2430\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 540
recvmsg(20,  ;D{msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"@\0\0\0\24\0\2\0\t\311\305T\2430\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 256
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\t\311\305T\2430\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
close(20)                               = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++


The last message appears related to receiving messages from the socket. 

Is it possible to configure MediaCenter to only listen/use a certain network interface?

Logged

linuxuser200

  • Recent member
  • *
  • Posts: 12
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #6 on: January 25, 2015, 11:37:06 pm »

The problem is definitely related to network interfaces - in particular to my VPN connection. If I run MediaCenter with the VPN disconnected, it does not crash.

I have tried listing the networks that are accessible via the VPN in MediaCenter's "Interfaces to ignore" setting (under Settings -> Media Network -> Advanced). However this did not prevent the crash if I start MediaCenter while connected to the VPN.. Any suggestions?

Other than that, great program! I am still busy learning its features..


Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5177
  • "Linux Merit Badge" Recipient
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #7 on: January 26, 2015, 06:52:52 am »

The problem is definitely related to network interfaces - in particular to my VPN connection. If I run MediaCenter with the VPN disconnected, it does not crash.

I have tried listing the networks that are accessible via the VPN in MediaCenter's "Interfaces to ignore" setting (under Settings -> Media Network -> Advanced). However this did not prevent the crash if I start MediaCenter while connected to the VPN.. Any suggestions?

Other than that, great program! I am still busy learning its features..




Good work hunting it down!  I don't have a lot of experience with VPNs on linux (although I've used MC with openvpn on Arch in the past with no problems).  Maybe Bob (or someone more knowledgeable about linux networking) can offer some help here?
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13526
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #8 on: January 26, 2015, 02:30:59 pm »

The problem is definitely related to network interfaces - in particular to my VPN connection. If I run MediaCenter with the VPN disconnected, it does not crash.

I have tried listing the networks that are accessible via the VPN in MediaCenter's "Interfaces to ignore" setting (under Settings -> Media Network -> Advanced). However this did not prevent the crash if I start MediaCenter while connected to the VPN.. Any suggestions?

Other than that, great program! I am still busy learning its features..
The "interfaces to ignore" field should be populated with the LOCAL address and netmask of the VPN interface.
something like
192.168.4.200/24

Not sure what to say if it doesn't work. I've got about 10 interfaces on my home machine and it MC works fine on it.
Logged

linuxuser200

  • Recent member
  • *
  • Posts: 12
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #9 on: January 26, 2015, 05:22:27 pm »

Hi Bob,

I have tried entering just the local address that I get from ifconfig (for the ppp0 interface) along with the bits corresponding to the mask but it still crashes.

For example:
Code: [Select]
ppp0      Link encap:Point-to-Point Protocol                                                                                                                                                                   
          inet addr:10.22.1.11  P-t-P:10.22.1.1  Mask:255.255.255.255                                                                                                                                       
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1400  Metric:1                                                                                                                                           
          RX packets:417 errors:0 dropped:0 overruns:0 frame:0                                                                                                                                                 
          TX packets:581 errors:0 dropped:0 overruns:0 carrier:0                                                                                                                                               
          collisions:0 txqueuelen:3                                                                                                                                                                           
          RX bytes:48245 (48.2 KB)  TX bytes:67544 (67.5 KB)

I entered the following in the "interfaces to ignore":
Code: [Select]
10.22.1.11/32

Do you run Linux on your machine where you have those 10 network interfaces? Just trying to figure what what's different in my case.. I also have a few other virtual network interfaces (docker, Virtual Box, VMWare) but only the VPN seems to be causing issues.

I have also tried disabling DLNA services altogether. If I do this and then start MC while connected to the VPN, MC runs for a lot longer (about 5 min as opposed to under 10 seconds in the other case) but it still crashes eventually. Before it crashes I can interact with it and everything appears to be working normally.

This crash (the one when DLNA services are disabled) also appears to be related to communicating over the network (VPN?) according to the strace messages logged just before the crash:

Code: [Select]
...
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 19
socket(PF_NETLINK, SOCK_RAW, 0)         = 20
bind(20, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
getsockname(20, {sa_family=AF_NETLINK, pid=9366, groups=00000000}, [12]) = 0
time(NULL)                              = 1422313661
sendto(20, "\24\0\0\0\22\0\1\3\275\310\306T\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"d\4\0\0\20\0\2\0\275\310\306T\226$\0\0\0\0\4\3\1\0\0\0I\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 3388
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"l\4\0\0\20\0\2\0\275\310\306T\226$\0\0\0\0\1\0\4\0\0\0C\20\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 3420
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"T\4\0\0\20\0\2\0\275\310\306T\226$\0\0\0\0\0\2\37\0\0\0\321\20\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 1108
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\275\310\306T\226$\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
sendto(20, "\24\0\0\0\26\0\1\3\276\310\306T\0\0\0\0\0\0\0\0", 20, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 20
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"D\0\0\0\24\0\2\0\276\310\306T\226$\0\0\2\10\200\376\1\0\0\0\10\0\1\0\177\0\0\1"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 540
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"@\0\0\0\24\0\2\0\276\310\306T\226$\0\0\n\200\200\376\1\0\0\0\24\0\1\0\0\0\0\0"..., 4096}], msg_controllen=0, msg_flags=0}, 0) = 256
recvmsg(20, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000}, msg_iov(1)=[{"\24\0\0\0\3\0\2\0\276\310\306T\226$\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 20
close(20)                               = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++

I am happy to run a debug version that contains symbols (or to upload the core dump somewhere) if you need more info to debug this.

Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13526
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #10 on: January 27, 2015, 12:55:03 pm »

It's fixed in the next build. It was the point to point interface...
Logged

linuxuser200

  • Recent member
  • *
  • Posts: 12
Re: segmentation fault on Ubuntu 14.04 64 bit
« Reply #11 on: January 27, 2015, 09:14:28 pm »

That's great Bob. Thanks!

Update: I've just tested v. 20.0.63 and it fixes the crashes.
Logged
Pages: [1]   Go Up