Arch Linux

iamlixiao

Member

Registered: 2013-11-18

Posts: 3

Strange D-BUS error causing ffplay & many Steam games to crash

Every time I run ffplay as a normal user it fails like this:

$ ffplay /scratch/video.mp4 
ffplay version 3.3.2 Copyright (c) 2003-2017 the FFmpeg developers
  built with gcc 7.1.1 (GCC) 20170516
  configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-avisynth --enable-avresample --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libass --enable-libbluray --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxvid --enable-shared --enable-version3
  libavutil      55. 58.100 / 55. 58.100
  libavcodec     57. 89.100 / 57. 89.100
  libavformat    57. 71.100 / 57. 71.100
  libavdevice    57.  6.100 / 57.  6.100
  libavfilter     6. 82.100 /  6. 82.100
  libavresample   3.  5.  0 /  3.  5.  0
  libswscale      4.  6.100 /  4.  6.100
  libswresample   2.  7.100 /  2.  7.100
  libpostproc    54.  5.100 / 54.  5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/scratch/video.mp4':=0/0   
  Metadata:
    major_brand     : isom
    minor_version   : 1
    compatible_brands: isomavc1
    creation_time   : 2017-04-25T13:45:06.000000Z
  Duration: 00:23:59.89, start: 0.000000, bitrate: 1606 kb/s
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1411 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default)
    Metadata:
      creation_time   : 2017-04-25T13:45:06.000000Z
    Stream #0:1(jpn): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 192 kb/s (default)
    Metadata:
      creation_time   : 2017-04-25T12:38:13.000000Z
process 23664: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1371.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted (core dumped)

But when I run it with sudo, every thing works fine:

$ sudo ffplay /scratch/video.mp4

Inspecting with gdb, it looks like this problem may be SDL2-related.

$ gdb --args ffplay /scratch/video.mp4 
GNU gdb (GDB) 8.0
Copyright (C) 2017 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-pc-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 ffplay...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/ffplay /scratch/video.mp4
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
ffplay version 3.3.2 Copyright (c) 2003-2017 the FFmpeg developers
  built with gcc 7.1.1 (GCC) 20170516
  configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-avisynth --enable-avresample --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libass --enable-libbluray --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxvid --enable-shared --enable-version3
  libavutil      55. 58.100 / 55. 58.100
  libavcodec     57. 89.100 / 57. 89.100
  libavformat    57. 71.100 / 57. 71.100
  libavdevice    57.  6.100 / 57.  6.100
  libavfilter     6. 82.100 /  6. 82.100
  libavresample   3.  5.  0 /  3.  5.  0
  libswscale      4.  6.100 /  4.  6.100
  libswresample   2.  7.100 /  2.  7.100
  libpostproc    54.  5.100 / 54.  5.100
[New Thread 0x7fffe4797700 (LWP 1267)]
[New Thread 0x7fffdbe31700 (LWP 1268)]
[New Thread 0x7fffdacb1700 (LWP 1269)]
[New Thread 0x7fffda2ab700 (LWP 1270)]
[New Thread 0x7fffd9aaa700 (LWP 1271)]
[New Thread 0x7fffd92a9700 (LWP 1272)]
[New Thread 0x7fffd8aa8700 (LWP 1273)]
[New Thread 0x7ffff7ecd700 (LWP 1274)]
[New Thread 0x7fffc7fa0700 (LWP 1275)]
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/scratch/video.mp4':=0/0   
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41isomM4A 
    creation_time   : 2017-05-10T09:10:13.000000Z
    encoder         : Nero AAC codec / 1.5.4.0
  Duration: 00:24:30.14, start: 0.000000, bitrate: 1065 kb/s
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv), 1280x720, 908 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default)
    Metadata:
      creation_time   : 2017-05-10T09:10:13.000000Z
      handler_name    : L-SMASH Video Media Handler
      encoder         : AVC Coding
    Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 152 kb/s (default)
    Metadata:
      creation_time   : 2017-05-10T09:10:13.000000Z
      handler_name    : Sound Media Handler
[New Thread 0x7fffc7314700 (LWP 1276)]
[New Thread 0x7fffc6b13700 (LWP 1277)]
[New Thread 0x7fffc6312700 (LWP 1278)]
[New Thread 0x7fffc5b11700 (LWP 1279)]
[New Thread 0x7fffc5310700 (LWP 1280)]
[New Thread 0x7fffc4b0f700 (LWP 1281)]
[New Thread 0x7fffbffff700 (LWP 1282)]
[New Thread 0x7fffbf7fe700 (LWP 1283)]
[New Thread 0x7fffbeffd700 (LWP 1284)]
[New Thread 0x7ffff7fc6700 (LWP 1285)]
[New Thread 0x7fffbe7fc700 (LWP 1286)]
[New Thread 0x7fffbdffb700 (LWP 1287)]
[New Thread 0x7fffbd7fa700 (LWP 1288)]
[New Thread 0x7fffbcff9700 (LWP 1289)]
[New Thread 0x7fffa3fff700 (LWP 1290)]
[New Thread 0x7fffa37fe700 (LWP 1291)]
[New Thread 0x7fffa2ffd700 (LWP 1292)]
[New Thread 0x7fffa27fc700 (LWP 1293)]
[New Thread 0x7fffa1ffb700 (LWP 1294)]
[New Thread 0x7fffa17fa700 (LWP 1295)]
[New Thread 0x7fffa0ff9700 (LWP 1296)]
[Thread 0x7fffbeffd700 (LWP 1284) exited]
[Thread 0x7fffbf7fe700 (LWP 1283) exited]
[Thread 0x7fffc4b0f700 (LWP 1281) exited]
[Thread 0x7fffc5310700 (LWP 1280) exited]
[Thread 0x7fffc5b11700 (LWP 1279) exited]
[Thread 0x7fffc6312700 (LWP 1278) exited]
[Thread 0x7fffc6b13700 (LWP 1277) exited]
[Thread 0x7fffc7314700 (LWP 1276) exited]
[Thread 0x7fffbffff700 (LWP 1282) exited]
[New Thread 0x7fffbeffd700 (LWP 1297)]
[New Thread 0x7fffbf7fe700 (LWP 1298)]
[New Thread 0x7fffbffff700 (LWP 1299)]
[New Thread 0x7fffc4b0f700 (LWP 1300)]
[New Thread 0x7fffc7314700 (LWP 1301)]
[New Thread 0x7fffc6b13700 (LWP 1302)]
[New Thread 0x7fffc6312700 (LWP 1303)]
[New Thread 0x7fffc5b11700 (LWP 1304)]
[New Thread 0x7fffc5310700 (LWP 1305)]
[New Thread 0x7fff77fff700 (LWP 1306)] vq=  111KB sq=    0B f=0/0   
[New Thread 0x7fff777fe700 (LWP 1307)]
[New Thread 0x7fff76ffd700 (LWP 1308)]
[New Thread 0x7fff767fc700 (LWP 1309)]
[New Thread 0x7fff75ffb700 (LWP 1310)]
[New Thread 0x7fff757fa700 (LWP 1311)]
[New Thread 0x7fff74ff9700 (LWP 1312)]
[New Thread 0x7fff6ffff700 (LWP 1313)]
[New Thread 0x7fff6f7fe700 (LWP 1314)]
process 1263: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1371.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace

Thread 1 "ffplay" received signal SIGABRT, Aborted.
0x00007ffff44e7670 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff44e7670 in raise () from /usr/lib/libc.so.6
#1  0x00007ffff44e8d00 in abort () from /usr/lib/libc.so.6
#2  0x00007fffeab8832b in ?? () from /usr/lib/libdbus-1.so.3
#3  0x00007fffeab7e378 in _dbus_warn_check_failed () from /usr/lib/libdbus-1.so.3
#4  0x00007fffeab6d416 in dbus_message_new_method_call () from /usr/lib/libdbus-1.so.3
#5  0x00007ffff4e56e5b in ?? () from /usr/lib/libSDL2-2.0.so.0
#6  0x00007ffff4e45156 in ?? () from /usr/lib/libSDL2-2.0.so.0
#7  0x00007ffff4e45f90 in ?? () from /usr/lib/libSDL2-2.0.so.0
#8  0x00007ffff4dd1367 in ?? () from /usr/lib/libSDL2-2.0.so.0
#9  0x000055555555c1db in main ()

Many games in my Steam library also crash on startup, showing errors similar to this:

process 23664: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1371.

I searched for this error and was unable to dig out any useful information. I think at least I should be able to find out what arguments were passed to dbus_message_new_method_call() and failed the check. Could anyone point out a way for me? Thanks.

Last edited by iamlixiao (2017-06-24 08:56:10)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,672

Re: Strange D-BUS error causing ffplay & many Steam games to crash

Works here, IS your dbus session set up correctly? output of

printenv DBUS_SESSION_BUS_ADDRESS

if this doesn't return something like unix:path=/run/user/1000/bus you should setup your session correctly, many threads are around on this issue so you might want to check the boards for session related problems - e.g. https://bbs.archlinux.org/viewtopic.php?id=227275

iamlixiao

Member

Registered: 2013-11-18

Posts: 3

Re: Strange D-BUS error causing ffplay & many Steam games to crash

Works here, IS your dbus session set up correctly? output of

printenv DBUS_SESSION_BUS_ADDRESS

if this doesn't return something like unix:path=/run/user/1000/bus you should setup your session correctly, many threads are around on this issue so you might want to check the boards for session related problems - e.g. https://bbs.archlinux.org/viewtopic.php?id=227275

$ printenv DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

Looks like the session is set up correctly.

I don't think it's a "global" dbus issue because most of my system is running normally, with only a few apps crashing due to this "assertion '_dbus_check_is_valid_path (path)' failed" error. Hopefully there's a way to learn exactly what "path" is passed to this _dbus_check_is_valid_path(path) function and why it failed the validation.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,672

Re: Strange D-BUS error causing ffplay & many Steam games to crash

Go through the thread I posted anyway, there are a few other possible causes, like local gnupg services causing a conflict.