Unable to open Kmail (or Kontact)

Hi,
I upgraded from Leap 42.2 to 43.3 today. I am using the latest KDE (KDE Plasma: 5.11.4, KDE Frameworks: 5.40.0, Qt Version: 5.10.0). After the upgrade, I am unable to open Kmail or Kontact. When I try to open Kmail in Konsole, I get the following message

userj@user-laptop:~> kmail
Pass a valid window to KWallet::Wallet::openWallet().
The kwalletd service has been registered
org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
org.kde.pim.messagelist: Saved theme loading failed
org.kde.pim.messagelist: Saved theme loading failed
org.kde.pim.messagelist: Saved theme loading failed
org.kde.pim.webengineviewer:  It's not necessary to check database now
[22992:23033:1220/224511.462610:ERROR:gl_implementation.cc(246)] Failed to load /usr/bin/libGLESv2.so: /usr/bin/libGLESv2.so: cannot open shared object file: No such file or directory
this does not work on a KActionCollection containing actions!
QDBusConnection: name 'org.kde.kwalletd5' had owner '' but we thought it was ':1.60'
org.kde.akonadi.ETM: GEN true false false
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: 
org.kde.akonadi.ETM: Subtree:  3 QSet(50, 3, 48, 49, 46, 47)
org.kde.akonadi.ETM: Fetch job took  344 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 6
org.kde.akonadi.ETM: first fetched collection: "Local Folders"
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Fetch job took  377 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 6
org.kde.akonadi.ETM: first fetched collection: "Search"
org.kde.akonadi.ETM: Fetch job took  33 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 0
[22992:23033:1220/224512.207379:ERROR:gl_surface_qt.cpp(701)] Requested OpenGL implementation is not supported. Implementation: 0
Received signal 11 SEGV_MAPERR 000000000000
#0 0x7f62dd5f8af7 <unknown>
#1 0x7f62dc3a541e <unknown>
#2 0x7f62dd5f8e8d <unknown>
#3 0x7f62f2359950 <unknown>
#4 0x7f62dc406f41 <unknown>
#5 0x7f62dc407d05 <unknown>
#6 0x7f62de0255f4 <unknown>
#7 0x7f62de032d6c <unknown>
#8 0x7f62de03899c <unknown>
#9 0x7f62de039941 <unknown>
#10 0x7f62de02be00 <unknown>
#11 0x7f62de0308ba <unknown>
#12 0x7f62de0302c2 <unknown>
#13 0x7f62de031f35 <unknown>
#14 0x7f62dd679771 <unknown>
#15 0x7f62dd614450 <unknown>
#16 0x7f62dd615c6e <unknown>
#17 0x7f62dd616c49 <unknown>
#18 0x7f62dd617019 <unknown>
#19 0x7f62dd633808 <unknown>
#20 0x7f62dd64e6b6 <unknown>
#21 0x7f62dd649a1d <unknown>
#22 0x7f62e815d744 start_thread
#23 0x7f62f240eaad __clone
  r8: 0000000000000003  r9: 00007f6244000078 r10: 00007f6244000070 r11: 0000000000000005
 r12: 0000000000000000 r13: 00007f62617f8c20 r14: 00007f62617f8c70 r15: 00007f624400eb70
  di: 0000000000000000  si: 0000000000000000  bp: 00007f62617f8a60  bx: 00007f624400eb70
  dx: 0000000000000000  ax: 00007f62e22cccc8  cx: 00007f62617f8890  sp: 00007f62617f8890
  ip: 00007f62dc406f41 efl: 0000000000010206 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
user@user-laptop:~> 


I did not have this problem in Leap 42.2 with KDE Plasma: 5.11. I don’t know what went wrong during the upgrade. Any help is appreciated. Thanks

I suppose this is the problem:

I’m just wondering why it tries to load /usr/bin/libGLESv2.so though.
It’s located in /usr/lib64/, like all other system libs.

What do you get when running “glxinfo”? (you might have to install Mesa-demo-x)

I have Mesa-demo-x installed and I am getting


user@user-Laptop:~> glxinfo
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig

My laptop is has Nvidia optimus card and I use Bumblebee to run graphics intensive programs.

That’s very likely the reason for the problem, I’d say.

Though I am surprised that Plasma would even start then…

My laptop is has Nvidia optimus card and I use Bumblebee to run graphics intensive programs.

Did you maybe try to install the nvidia driver?
That replaces the system’s OpenGL libraries with nvidia’s versions that only work if the nvidia driver is used. But on Optimus system’s the intel chip is used by default, so OpenGL will be broken.

Another thing is that the nvidia driver won’t work if drm-kmp-default is installed (which contains backports of the graphics stack from Kernel 4.9). That is new in 42.3, and installed by default.
Try to uninstall it in any case (which would make your system more like 42.2), it may cause problems on some intel chips too.

Can you please post /var/log/Xorg.0.log?

I have installed Nvidia driver

I followed the instructions in the openSUSE page SDB:NVIDIA drivers - openSUSE Wiki for Leap 42.3 and did the following

$ sudo zypper rm drm-kmp-default
 $ sudo zypper addrepo --refresh http://http.download.nvidia.com/opensuse/leap/42.3 NVIDIA
 $ sudo zypper install-new-recommends


so drm-kmp-default is not installed in my system

https://paste.opensuse.org/69668005

And that’s exactly the problem.

From your Xorg.0.log:

    34.436] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
    34.987] (II) Module glx: vendor="NVIDIA Corporation"
    34.987]    compiled for 4.0.2, module version = 1.0.0
    34.987]    Module class: X.Org Server Extension
    34.987] (II) NVIDIA GLX Module  384.98  Thu Oct 26 14:35:55 PDT 2017

 

So nvidia’s GLX module is loaded, which only works with the nvidia driver.
But the system uses the intel chip (as usual with Optimus) and the modesetting driver.
Therefore GLX is broken.

You need to switch to Xorg’s libglx:

sudo update-alternatives --set libglx.so /usr/lib64/xorg/modules/extensions/xorg/xorg-libglx.so

Maybe that will be enough already to fix your problem… (you need to reboot or at least logout/login though)

Actually, the nvidia packages should not activate the nvidia OpenGL/GLX stuff if an intel GPU/Optimus system is detected, but apparently something went wrong on your system.

Great !

sudo update-alternatives --set libglx.so /usr/lib64/xorg/modules/extensions/xorg/xorg-libglx.so

solved the problem ! Thanks wolfi323.

Actually, the nvidia packages should not activate the nvidia OpenGL/GLX stuff if an intel GPU/Optimus system is detected, but apparently something went wrong on your system

Are the instructions for NVIDIA Bumblebee still valid for Leap 42.3 ? The link (SDB:NVIDIA Bumblebee - openSUSE Wiki) says that it has been tested on 42.2. I am unable to use NVIDIA because I am getting errors


user@user-Laptop:~> optirun inkscape 
 1110.998672] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

 1110.998713] [ERROR]Aborting because fallback start is disabled.
user@user-Laptop:~> 


Do I need to start a new thread to address this issue ? Once again, Thank you for your help !

Good. :slight_smile:

Are the instructions for NVIDIA Bumblebee still valid for Leap 42.3 ? The link (SDB:NVIDIA Bumblebee - openSUSE Wiki) says that it has been tested on 42.2.

I’m not using Bumblebee (don’t have such hardware), but there are no changes in 42.3 in this area AFAIK.
(except for the introduction of drm-kmp-default, which doesn’t play well with nvidia in general)

So I do think it would be good to follow those instruction first before trying anything else.

I am unable to use NVIDIA because I am getting errors

user@user-Laptop:~> optirun inkscape
1110.998672] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

1110.998713] [ERROR]Aborting because fallback start is disabled.
user@user-Laptop:~>

Well, the link you mention contains this section:

Problems with GT600M/GT700M series cards (Kepler)

If you cannot load GPU drivers - while bbswitch being loaded - and get an error like this on a Kepler card:

[INFO]Response: No - error: Could not load GPU driver
[ERROR]Cannot access secondary GPU - error: Could not load GPU driver

Try changing value of ‘load_state’ in “/etc/modprobe.d/50-bbswitch.conf” from 0 to -1

echo "options bbswitch load_state=-1 unload_state=1" | sudo tee /etc/modprobe.d/50-bbswitch.conf

More info on github: bbswitch - scroll to Module options.

Maybe that would help?

Do I need to start a new thread to address this issue ?

Probably a good idea, the title of this one is “Unable to open Kmail (Kontact)” which may not necessarily attract people with knowledge about Optimus/Bumblebee…