# Chrome Causes Segmentation Faults in libnvidia-glcore.so.390.25 With KDE neon (Ubuntu with plasma) **URL:** \ **Category:** Linux\ **Created:** [February 26, 2018, 7:17pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570 "2018-02-26T19:17:33Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [February 26, 2018, 7:17pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/1 "2018-02-26T19:17:33Z")
Hi. My desktop keeps crashing. I have a fresh install of KDE neon 5.12 For explanation; KDE neon is an LTS Ubuntu (currently 16.04) without its default GUI (called unity), it uses “Plasma 5” instead. My graphics card is GTX 770 and I’m using the nvidia proprietary drivers 390.25. I installed it from the ubuntu’s graphics drivers ppa (here [https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa](https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) ) so I did: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt update sudo apt install nvidia-390 I get crashes at random times, but here’s what may help reproduce it. I have google chrome. I open many (MANY) chrome windows, and each has many tabs. Try opening a tab with google maps. I get some weird lag in the cursor! Also the crash mostly happens when I “show desktop grid”. To do this you have to have virtual desktops. Just search for “virtual desktops” and add some (I have 16 of them), then press Ctrl+F8 When the crash happens the mouse and keyboard are active. I go to the tty (Ctrl+Alt+F1) and type dmesg and I see segfault in libnvidia-glcore.so.390.25 p.s: I’m re-posting this: [url][https://forums.geforce.com/default/topic/1038512/geforce-drivers/segmentation-faults-with-kde-neon-ubuntu-with-plasma-/?offset=3#5297084[/url]](https://forums.geforce.com/default/topic/1038512/geforce-drivers/segmentation-faults-with-kde-neon-ubuntu-with-plasma-/?offset=3#5297084%5B/url%5D) ![IMG_20180226_140952-min.jpg](https://global.discourse-cdn.com/nvidia/original/2X/a/adfaffa1e9321b6f8b737358529da13d9822f440.jpeg) ![IMG_20180226_140952-min.jpg](https://global.discourse-cdn.com/nvidia/original/2X/a/adfaffa1e9321b6f8b737358529da13d9822f440.jpeg) ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [March 7, 2018, 4:17am UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/2 "2018-03-07T04:17:39Z")
bump :( anything? ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [April 1, 2018, 9:17pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/3 "2018-04-01T21:17:39Z")
bump. it’s still happening ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [August 11, 2018, 12:10pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/4 "2018-08-11T12:10:06Z")
Attaching the output of the debug script. I’m still experiencing the same issue but I can’t locate the segmentation fault in dmesg anymore. [1 nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/tlOLdxHRJXyk2LtnQYc6Ln0VYqv.gz) (116 KB) [2 nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/8FXy5QA5Gajwk9xfviQbFjhcXry.gz) (156 KB) [3 nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/uLeJIvTKUF9EmmpK5BUhJDFe4I3.gz) (157 KB) ---
**Author:** ![generix](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/generix/32/16024_2.png) [@generix](https://forums.developer.nvidia.com/u/generix)\ **Post date:** [August 12, 2018, 2:14pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/5 "2018-08-12T14:14:19Z")
You’re getting kernel oopses regarding ext4 and nvidia and segfaults from thumbnail generation. You should check your memory and harddisk. ---
**Author:** ![ekurzinger](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/ekurzinger/32/10762_2.png) [@ekurzinger](https://forums.developer.nvidia.com/u/ekurzinger)\ **Post date:** [August 16, 2018, 8:22pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/6 "2018-08-16T20:22:16Z")
Hi, we’re currently investigating an issue related to virtual desktop switching in KWin that may be similar to what you’re experiencing. Would you be able to describe in more detail what you see when the crash occurs? Specifically, do all the window decorations (title bars, ect.) dissappear? Another thing that might be helpful - could you run the following command ```auto $ kwin_x11 --replace ``` and then try to trigger the crash and post any output? ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [August 16, 2018, 8:55pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/7 "2018-08-16T20:55:02Z")
> [@](#): > > Hi, we’re currently investigating an issue related to virtual desktop switching in KWin that may be similar to what you’re experiencing. Would you be able to describe in more detail what you see when the crash occurs? Specifically, do all the window decorations (title bars, ect.) dissappear? > > Another thing that might be helpful - could you run the following command > > ```auto > $ kwin_x11 --replace > > ``` > > and then try to trigger the crash and post any output? Thank you for your reply. The display just “freezes” as it is. Only the mouse can move. The rest visually stays the same as if it’s a still frame of a camera. I’ll try the command but the crash happens sort of randomly. But it does seem to happen specifically when I’m either switching the virtual desktop or when I’m displaying the grid of the virtual desktops. I work with 16 desktops. A 4x4 grid. Note that when the crash occurred, I think I tried ```auto $ kwin --replace ``` before but as far as I recall it didn’t work. I got some output that it couldn’t connect to the X server or something. I’m just trying to remember this part from memory. I hope I didn’t confuse situations with each other. Thank again. Much appreciated! ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [August 16, 2018, 9:01pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/8 "2018-08-16T21:01:54Z")
…recently I’ve updated the graphics driver to 396. Do I try with the new version of the drivers or do I need to use 390? ---
**Author:** ![ekurzinger](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/ekurzinger/32/10762_2.png) [@ekurzinger](https://forums.developer.nvidia.com/u/ekurzinger)\ **Post date:** [August 16, 2018, 9:09pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/9 "2018-08-16T21:09:30Z")
Thanks for the info! If this is related to the issue we’ve been investigating, it should reproduce using 396 as well so you should be fine using what you’ve currently got installed. Note that you should try running ```auto kwin_x11 --replace ``` _before_ the crash occurs. This will allow us to have a look at KWin’s output to perhaps get some insight into what’s going wrong. ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [August 16, 2018, 10:35pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/10 "2018-08-16T22:35:40Z")
I understand that. I’ve issued the command and I’ve been playing around for a while. I can’t reproduce it. It’s so random. ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [August 16, 2018, 10:54pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/11 "2018-08-16T22:54:24Z")
Got it! :D [nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/rxCkaZbu9DYETviGcwAfDP2r3Lx.gz) (145 KB) ---
**Author:** ![ekurzinger](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/ekurzinger/32/10762_2.png) [@ekurzinger](https://forums.developer.nvidia.com/u/ekurzinger)\ **Post date:** [August 17, 2018, 12:24am UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/12 "2018-08-17T00:24:10Z")
Would it be possible to get the output from the kwin command? Here is the Kwin bug tracking the issue [386370 – kwin randomly crashes when switching desktops](https://bugs.kde.org/show_bug.cgi?id=386370) and OpenSUSE also has a bug tracking the same thing [Bug 1101560 – kwin frequent crashes with nvidia](https://bugzilla.opensuse.org/show_bug.cgi?id=1101560) Do the comments there align with anything you’re seeing at all? ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [August 21, 2018, 3:27pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/13 "2018-08-21T15:27:40Z")
Hello! Sry I haven’t replied since then. I’ve been away. Next time the crash happens I’ll make sure to capture the output of the console in which I ran the kwin command. Also when I first run the command these are the lines that I get: ```auto kwin_x11 --replace QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setWindow: Painter not active QPainter::setClipRect: Painter not active QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setClipRect: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::drawRects: Painter not active QPainter::restore: Unbalanced save/restore OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 770/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 396.51 OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 396.51 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.19.6 Linux kernel version: 4.15 Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no kf5.kcoreaddons.desktopparser: Property type "Url" is not a known QVariant type. Found while parsing property definition for "X-KWin-Video-Url" in "/usr/share/kservicetypes5/kwineffect.desktop" qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 5428, resource id: 0, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 5438, resource id: 0, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 5440, resource id: 0, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 5441, resource id: 0, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 5442, resource id: 0, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 5443, resource id: 0, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 5444, resource id: 0, major code: 14 (GetGeometry), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5574, resource id: 123732073, major code: 3 (GetWindowAttributes), minor code: 0 ``` ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [August 21, 2018, 3:32pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/14 "2018-08-21T15:32:22Z")
…so actually I don’t know how to do this. The problem is that if I run the `kwin_x11 --replace` command in a regular console window. I will not be able to capture the error because the whole screen freezes when the error happens. …and I can’t run the command in a tty. It just says “fatal error cannot open display” something like that. It’s because I’m not specifying the correct display or something. I think there’s something that I should add to the command for it to work from tty. I tried doing `DISPLAY=0 kwin_x11 --replace` ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [September 3, 2018, 11:26am UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/15 "2018-09-03T11:26:29Z")
I finally learned how to EXACTLY reproduce the bug. I could do it 5 times the same way. It has to do with the notification box that appears on mouse-over. If I can trigger “show desktop grid” while it is appearing, everything just freezes. Here’s a video explaining how to reproduce it. [Nvidia bug with the Plasma desktop. Steps to reproduce it. - YouTube](https://youtu.be/_l1ab_PLP7Y) I think that a different thread should be opened for this topic. It has nothing to do with google chrome now or segfaults. I’ll change the title for now. ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [September 3, 2018, 11:26am UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/16 "2018-09-03T11:26:30Z")
duplicate post ---
**Author:** ![842mono](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@842mono](https://forums.developer.nvidia.com/u/842mono)\ **Post date:** [September 5, 2018, 6:32am UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/17 "2018-09-05T06:32:02Z")
Let’s open a separate thread. ---
**Author:** ![nadeemm](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/nadeemm/32/367020_2.png) [@nadeemm](https://forums.developer.nvidia.com/u/nadeemm)\ **Post date:** [October 14, 2021, 8:17pm UTC](https://forums.developer.nvidia.com/t/chrome-causes-segmentation-faults-in-libnvidia-glcore-so-390-25-with-kde-neon-ubuntu-with-plasma/58570/18 "2021-10-14T20:17:37Z")
Closed on October 14, 2021, 8:17pm UTC