DisplayLink crashes when enabling an external monitor

English Hardware
1

After MalcolmLewis was so kind to help me with getting my DisplayLink to work, my laptop decided it wasn’t happy and died.

I bought a replacement laptop, and I am now running Tumbleweed, but X completely crashes everytime I enable a second or third monitor. I did have a DVI to HDMI adapter that I plugged directly into the laptop, and that works fine. I followed the prompts to submit a bug report, but it seemed to be misdirected. I can reproduce this at will, so if there are specific logs anyone would want to see, I can grab them, but the one I already have is the output from journalctl:

Oct 18 20:32:00 Darkholme kcmshell5[3391]: kscreen: Correcting output positions by: QPoint(-480,-434)
Oct 18 20:32:00 Darkholme kcmshell5[3391]: kscreen: Moved output from QPoint(1440,0) to QPoint(1920,434)
Oct 18 20:32:00 Darkholme kcmshell5[3391]: kscreen: Moved output from QPoint(-480,-434) to QPoint(0,0)
Oct 18 20:32:00 Darkholme kcmshell5[3391]: kscreen: Moved output from QPoint(0,646) to QPoint(480,1080)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: XRandR::setConfig
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: Requested screen size is QSize(3840, 1980)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: Needed CRTCs:  3
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: Actions to perform:
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Primary Output: false
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Change Screen Size: true
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:                 Old: QSize(1920, 1080)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:                 Intermediate: QSize(3840, 1980)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:                 New: QSize(3840, 1980)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Disable outputs: false
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Change outputs: true
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:                  (66)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Enable outputs: true
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:                  (442, 498)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: RRSetScreenSize
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         DPI: 96.2526
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Size: QSize(3840, 1980)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         SizeMM: QSize(1013, 522)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: RRSetCrtcConfig (change output)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Output: 66 ( "eDP-1" )
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         CRTC: 63
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Pos: QPoint(1920,434)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Mode: 70 KScreen::Mode(Id: "70" , Size: QSize(1920, 1080) @ 120.016 )
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Rotation: 1
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Result:  0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: XRandROutput 66 update
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         m_connected: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         m_crtc XRandRCrtc(0x55e1ab67c900)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         CRTC: 63
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         MODE: 70
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Connection: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Primary: true
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: QMap((63, XRandRCrtc(0x55e1ab67c900))(64, XRandRCrtc(0x55e1ab673230))(65, XRandRCrtc(0x55e1ab674940))(441, XRandRCrtc(0x55e1ab6740c0))(497, XRandRCrtc(0x55e1ab6737e0)))
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: Testing CRTC 63
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Free: false
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Mode: 70
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Possible outputs: QVector(66, 67)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Connected outputs: QVector(66)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Geometry: QRect(1920,434 1920x1080)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: Testing CRTC 64
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Free: true
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Mode: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Possible outputs: QVector(66, 67)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Connected outputs: QVector()
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Geometry: QRect(0,0 0x0)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: Testing CRTC 65
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Free: true
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Mode: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Possible outputs: QVector(66, 67)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Connected outputs: QVector()
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Geometry: QRect(0,0 0x0)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: Testing CRTC 441
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Free: true
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Mode: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Possible outputs: QVector(442)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Connected outputs: QVector()
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Geometry: QRect(0,0 0x0)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: RRSetCrtcConfig (enable output)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Output: 442 ( "DVI-I-1-1" )
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         New CRTC: 441
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Pos: QPoint(0,0)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Mode: KScreen::Mode(Id: "444" , Size: QSize(1920, 1080) @ 60 ) Preferred: "444"
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Rotation: 1
Oct 18 20:32:00 Darkholme kernel: evdi: [D] evdi_painter_mode_changed_notify:507 (dev=1) Notifying mode changed: 1920x1080@60; bpp 32; 
Oct 18 20:32:00 Darkholme kernel: evdi: [D] evdi_painter_mode_changed_notify:508 pixel format 875713112
Oct 18 20:32:00 Darkholme kernel: evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Result: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr: XRandROutput 442 update
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         m_connected: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         m_crtc QObject(0x0)
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         CRTC: 441
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         MODE: 444
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Connection: 0
Oct 18 20:32:00 Darkholme kscreen_backend_launcher[3044]: kscreen.xrandr:         Primary: false
Oct 18 20:32:00 Darkholme systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Oct 18 20:32:00 Darkholme systemd[1]: Started Process Core Dump (PID 3477/UID 0).
Oct 18 20:32:00 Darkholme org_kde_powerdevil[3067]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme org.kde.kuiserver[2897]: XIO:  fatal IO error 25 (Inappropriate ioctl for device) on X server ":0"
Oct 18 20:32:00 Darkholme org.kde.kuiserver[2897]:       after 613 requests (613 known processed) with 0 events remaining.
Oct 18 20:32:00 Darkholme org.kde.ActivityManager[2897]: XIO:  fatal IO error 25 (Inappropriate ioctl for device) on X server ":0"
Oct 18 20:32:00 Darkholme org.kde.ActivityManager[2897]:       after 776 requests (776 known processed) with 0 events remaining.
Oct 18 20:32:00 Darkholme krunner[3028]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme kactivitymanagerd[3118]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme kuiserver5[3199]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme xembedsniproxy[3035]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme plasmashell[3030]: The X11 connection broke (error 1). Did the X11 server die?
Oct 18 20:32:00 Darkholme kaccess[2993]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme kwin_x11[3024]: The X11 connection broke (error 1). Did the X11 server die?
Oct 18 20:32:00 Darkholme plasmashell[3030]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme ksmserver[3010]: org.kde.kf5.ksmserver: ksmserver: Fatal IO error: client killed
Oct 18 20:32:00 Darkholme klauncher[2984]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme kdeinit5[2983]: kdeinit5: Fatal IO error: client killed
Oct 18 20:32:00 Darkholme kdeinit5[2983]: kdeinit5: sending SIGHUP to children.
Oct 18 20:32:00 Darkholme bluetoothd[1431]: Endpoint unregistered: sender=:1.46 path=/MediaEndpoint/A2DPSource
Oct 18 20:32:00 Darkholme gmenudbusmenuproxy[3046]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme bluetoothd[1431]: Endpoint unregistered: sender=:1.46 path=/MediaEndpoint/A2DPSink
Oct 18 20:32:00 Darkholme kdeinit5[2983]: kdeinit5: sending SIGTERM to children.
Oct 18 20:32:00 Darkholme kdeinit5[2983]: kdeinit5: Exit.
Oct 18 20:32:00 Darkholme kcmshell5[3391]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme polkit-kde-authentication-agent-1[3032]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme kglobalaccel5[3006]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme kernel: show_signal_msg: 35 callbacks suppressed
Oct 18 20:32:00 Darkholme kernel: kscreen_backend[3044]: segfault at 14 ip 00007ff72e57bdc6 sp 00007ffd360ed8e0 error 4 in KSC_XRandR.so[7ff72e57b000+1b000]
Oct 18 20:32:00 Darkholme kernel: Code: 00 00 00 00 8b 04 25 08 00 00 00 0f 0b 90 8b 04 25 08 00 00 00 0f 0b 8b 04 25 08 00 00 00 0f 0b 8b 04 25 08 00 00 00 0f 0b 90 <8b> 04 25 14 00 00 00 0f 0b 90 8b 04 25 08 00 00 00 0f 0b 90 0f b7 
Oct 18 20:32:00 Darkholme org.kde.kglobalaccel[2897]: XIO:  fatal IO error 25 (Inappropriate ioctl for device) on X server ":0"
Oct 18 20:32:00 Darkholme org.kde.kglobalaccel[2897]:       after 1784 requests (1784 known processed) with 0 events remaining.
Oct 18 20:32:00 Darkholme kdeconnectd[3048]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme baloorunner[3371]: The X11 connection broke: I/O error (code 1)
Oct 18 20:32:00 Darkholme polkitd[1607]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.32, object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Oct 18 20:32:00 Darkholme kernel: evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 3
Oct 18 20:32:00 Darkholme org.kde.runners.baloo[2897]: XIO:  fatal IO error 25 (Inappropriate ioctl for device) on X server ":0"

I entertained the idea of getting a replacement DockingStation, but they all seem to use DisplayLink these days, so I am likely to run into the same thing on a different system. Does anyone know what I can do to get this to work?

2

Hi
If you logout of KDE and use say IceWM, does the issue duplicate?

I think you may have to head off to the QT bugzilla as requested…

3

I tried it with IceWM and it did the same thing.

I started looking at Qt to try to figure out what and where I would be submitting a bug report, but I can’t even find out what part of Qt I am looking at or that we are referring to. Is there a particular package in QT we are talking about so that I can make sure I have the latest version of it?

4

Hi
With a particular application? Or everything in general works in both Desktop Environments?

5

If I sign into KDE with Plasma, then go to Displays, here is the screen I am looking at:

https://pbs.twimg.com/media/DqNB19RWsAA7aWP.jpg

The enabled monitor is an HDMI connection (to an DVI adapter) that works normally. The one that is not enabled is the one plugged into my DisplayLink. If I enable it, then hit Apply, X crashes. I tested the same process when I signed in with IceWM, and the same thing happened the same way.

I keep seeing updates to the DisplayLink package come across, but as of this posting the latest versions in the repositories are still doing the same thing.

Occasionally, when it crashes, KDE gives me the option to submit a bug report, and I did. That was where I got the message to submit a bug report to Qt, but while I see that there is a lot of things associated with Qt in KDE, I don’t even know what Qt means in this context, so I don’t know how to see if I have it, have the latest, or where to go to submit a bug report.

6

On Tue 23 Oct 2018 03:46:03 PM CDT, LexPendragon wrote:

If I sign into KDE with Plasma, then go to Displays, here is the screen
I am looking at:

[image: https://pbs.twimg.com/media/DqNB19RWsAA7aWP.jpg]

The enabled monitor is an HDMI connection (to an DVI adapter) that works
normally. The one that is not enabled is the one plugged into my
DisplayLink. If I enable it, then hit Apply, X crashes. I tested the
same process when I signed in with IceWM, and the same thing happened
the same way.

I keep seeing updates to the DisplayLink package come across, but as of
this posting the latest versions in the repositories are still doing the
same thing.

Occasionally, when it crashes, KDE gives me the option to submit a bug
report, and I did. That was where I got the message to submit a bug
report to Qt, but while I see that there is a lot of things associated
with Qt in KDE, I don’t even know what Qt means in this context, so I
don’t know how to see if I have it, have the latest, or where to go to
submit a bug report.

Hi
When you say updates come across, I’m assuming that’s the binary blob
(displaylink) not the kernel driver?

One wonders if starting with the Displaylink folks first may have some
pointers?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.22-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

7

I meant the regular system updates that come through Zypper or the Software Updates notification through KDE. Either way, one of those included some Kernel Updates and a DisplayLink update, and now everything works as expected. Thanks for all of your help!!

8

Hi
Yes, the evdi update will happen post release of any distribution updates… so can be a lag, so if there are any kernel updates, you may need to check on the the status of the build here and once it matches the updated kernel then install :wink: