Bug 356346 - Optimus KDE SESSION - ksplashqml: segfault in libnvidia-glcore.so.340.96
Summary: Optimus KDE SESSION - ksplashqml: segfault in libnvidia-glcore.so.340.96
Status: RESOLVED WORKSFORME
Alias: None
Product: ksplash
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-06 23:44 UTC by ioann
Modified: 2022-11-18 05:17 UTC (History)
1 user (show)

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


Attachments
glxinfo from optirun plasma session (38.16 KB, text/x-log)
2015-12-08 15:35 UTC, ioann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ioann 2015-12-06 23:44:06 UTC
I get error, if I try run KDE session under optirun.
I try it, for disabling comositing for FullScreen applications and for having graphical effects on my desktop.

Reproducible: Always
Comment 1 Thomas Lübking 2015-12-07 08:34:26 UTC
ksplashqml isn't KWin and we'll also require a complete backtrace.

However, the solution is likely much simpler: entirely disable the intel chip, if you run the entire desktop session (or even just KWin) under the nvidia blob, the GPU is loaded all the time anyway and having the intel IGP active *in addition* just wastes battery.
Comment 2 ioann 2015-12-07 09:20:19 UTC
I always use the laptop to the connected power cable. The fact that Nvidia discrete graphics card is not able to display the image directly (it's what I recently learned). Why disappear effects? Even the translucency. This error message I took from dmesg
Comment 3 Thomas Lübking 2015-12-07 09:24:29 UTC
The setup will be screwed, ie. a mix of MESA and nvidia libraries is used and you likely won't be able to even just run "glxinfo" (resp. it prints an error or segfaults) - if you can run "glxinfo", please attach the output.

The sheer dmesg entry doesn't say too much about the cause, sorry.
You'll often find a switch to bypass the intel chip in the BIOS.
Comment 4 Thomas Lübking 2015-12-07 09:28:04 UTC
PS: fullscreen unredirection isn't worth it, the feature is permanent subject of removal discussions anyway.
Simply suspend the compositor if you don't want it active (also supported by rules and scripts, "kcmshell5 kwinrules" resp. http://kde-look.org/content/show.php/GameMode?content=156659)

This will *really* free resources for performance improvements in other locations (games etc.)
Comment 5 ioann 2015-12-08 15:35:49 UTC
Created attachment 95937 [details]
glxinfo from optirun plasma session
Comment 6 ioann 2015-12-08 15:36:20 UTC
(In reply to Thomas Lübking from comment #3)
> The setup will be screwed, ie. a mix of MESA and nvidia libraries is used
> and you likely won't be able to even just run "glxinfo" (resp. it prints an
> error or segfaults) - if you can run "glxinfo", please attach the output.
> 
> The sheer dmesg entry doesn't say too much about the cause, sorry.
> You'll often find a switch to bypass the intel chip in the BIOS.

At now, I ran Plasma session as "vblank_mode=0 /usr/bin/primusrun /usr/bin/startkde". I can not see visual effects, e. g. transparenty or smoothing.
Comment 7 Thomas Lübking 2015-12-08 15:49:02 UTC
(In reply to ioann from comment #6)

> At now, I ran Plasma session as "vblank_mode=0 /usr/bin/primusrun
> /usr/bin/startkde".

I kinda doubt this works - startkde just forks a bunch of processes.
Since your core interest seems kwin, shadow it with a bash script in ~/bin or /usr/local/bin
(depending on whether you're on KDE4 or 5 it's "kwin" or "kwin_x11"

#!/bin/sh
vblank_mode=0 /usr/bin/primusrun /usr/bin/kwin_x11

Don't forget to chmod +x that, but again: 
a) you rather want to disable the intel IGP in BIOS
b) fullscreen unredirection is no way worth it.
Comment 8 ioann 2015-12-08 16:03:04 UTC
(In reply to Thomas Lübking from comment #7)
> (In reply to ioann from comment #6)
> 
> > At now, I ran Plasma session as "vblank_mode=0 /usr/bin/primusrun
> > /usr/bin/startkde".
> 
> I kinda doubt this works - startkde just forks a bunch of processes.
> Since your core interest seems kwin, shadow it with a bash script in ~/bin
> or /usr/local/bin
> (depending on whether you're on KDE4 or 5 it's "kwin" or "kwin_x11"
> 
> #!/bin/sh
> vblank_mode=0 /usr/bin/primusrun /usr/bin/kwin_x11
> 
> Don't forget to chmod +x that, but again: 
> a) you rather want to disable the intel IGP in BIOS
> b) fullscreen unredirection is no way worth it.

My BIOS not provide select for primary card. Please, tell me, where need add your script for run KWin on descrete card?
Comment 9 Thomas Lübking 2015-12-08 16:09:34 UTC
check the output of "echo $PATH" - the more left, the more preferred the binary path is.
"/usr/local/bin" is usually there and should shadow "/usr/bin"

If unsure about kwin ./. kwin_x11, check "ps ax | grep kwin"
Comment 10 ioann 2016-01-27 11:15:17 UTC
Dear developers!
Why do not you do the following additions:
1. Check whether the computer Optimus technology;
2. If this laptop with two graphics cards (Intel + Nvidia) to the video control panel, add a checkbox that enables or disables support for discrete graphics for compositing.

I'll try to explain with an example of code (more precisely, the logic):
[code]
// have Optimus thech. on the board.
if (funcForOptimusDetect() == true)
{
    // The renderer OpenGL 2.0 or OpenGL 3.1 selected
    if ( RENDER_ENGINE != "XRender")
    {
         // Add QCheckBox object for activation discrete videocard.
         // This option need for provide Nvidia OpenGL drivers (not MESA)
         // for comfort playing games in full screen.
    }
}
[/code]
Comment 11 Thomas Lübking 2016-01-27 11:37:00 UTC
This bug has nothing to do with compositing or kwin, you need something like bumblebee installed to even be able to select the GPU and that in addition has nothing to do with the compositing backend.

Also, if you intend to run kwin on the nvidia chip, just disable the intel chip altogether.
The idea of optimus is to save battery by only using the nvidia chip when it's required - if you run a persistent process on it, it's moot itfp. - you're actually *wasting* battery by keeping the intel chip enabled.
Comment 12 ioann 2016-01-27 12:27:03 UTC
(In reply to Thomas Lübking from comment #11)
> This bug has nothing to do with compositing or kwin, you need something like
> bumblebee installed to even be able to select the GPU and that in addition
> has nothing to do with the compositing backend.
> 
> Also, if you intend to run kwin on the nvidia chip, just disable the intel
> chip altogether.
> The idea of optimus is to save battery by only using the nvidia chip when
> it's required - if you run a persistent process on it, it's moot itfp. -
> you're actually *wasting* battery by keeping the intel chip enabled.

Thank for your reply!
But my laptop have hybrid graphics. The Nvidia card not have direct output and my BIOS do not provide settings for change primary output. In other words, it is impossible to use only Nvidia.
Comment 13 Justin Zobel 2022-10-19 22:10:46 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 14 Bug Janitor Service 2022-11-03 05:06:55 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 15 Bug Janitor Service 2022-11-18 05:17:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!