Bug 396061 - [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is turned on/driver is changed in NVIDIA X Sever Settings.
Summary: [GitStable][Nvidia-384] ksmserver crashes after proprietary nvidia driver is ...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-01 18:53 UTC by Jakub Strzelecki
Modified: 2018-07-02 00:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
KCrash with debugging symbols in place (5.92 KB, text/plain)
2018-07-01 18:53 UTC, Jakub Strzelecki 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Strzelecki 2018-07-01 18:53:19 UTC 
Created attachment 113688 [details]
KCrash with debugging symbols in place

kubast2@Aspire-F5-573G:~$ ksmserver --version
Qt: Session management error: networkIdsList argument is NULL
ksmserver 0.4
Worth noting:
I'm running a custom kernel to get zstd compression on btrfs
kubast2@Aspire-F5-573G:~$ uname -a
Linux Aspire-F5-573G 4.17.0-3.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.17-1ubuntu1~xenial (2018-06-28) x86_64 x86_64 x86_64 GNU/Linux
Comment 1 Jakub Strzelecki 2018-07-01 19:01:43 UTC 
How to reproduce:
1.Get Nvidia Optimus laptop.
2.sudo ubuntu-drivers autoinstall && reboot
3.Launch nvidia x settings.
4.Switch to Nvidia driver.
5.The driver change requires(for some reason) to logout and login ,rebooting doesn't change the driver.
6.ksmserver crashed.
Comment 2 Jakub Strzelecki 2018-07-01 19:08:25 UTC 
Discover also affected due to this bug:
https://transfer.sh/JjHCw/plasma-discover.kcrash.txt
Comment 3 Christoph Feck 2018-07-02 00:58:17 UTC 
Please don't:
- confirm your own bugs, unless you investigated the root of the issue,
- set flags that you don't know what they do

If this issue is still reproducible after a reboot, please ask for help in a forum of your distribution to find a suitable NVIDIA driver for your kernel.