I run kmail over SSH at times when I have a desktop system available. I connect to my laptop via: $ ssh -C -Y username@<ip> When I log in, I currently have to issue 'akonadictl stop' from the laptop keyboard. At this point, I can usually launch kmail via SSH: $ dbus-launch kmail akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontable OK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelation OK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK org.kde.pim.webengineviewer: It's not necessary to check database now QSystemTrayIcon::setVisible: No Icon set this does not work on a KActionCollection containing actions! QDBusConnection: name 'org.kde.kwalletd5' had owner '' but we thought it was ':1.3' QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted It seems that when I do this, there are no icons or any type of theme applied to the UI. Text labels are visible, but no icons.
On a possibly related issue, I notice I have issues marking messages as read when using kmail via this method.
I also note that with the latest kmail, I get the following crash when trying to start kmail and forward its UI to my desktop via SSH: Application: kmail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #4 0x00007f28cc5766bb in raise () from /lib64/libc.so.6 #5 0x00007f28cc578447 in abort () from /lib64/libc.so.6 #6 0x00007f28cd2a5941 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #7 0x00007f289e540004 in QGLXContext::init(QXcbScreen*, QPlatformOpenGLContext*) () from /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #8 0x00007f289e53dd87 in QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #9 0x00007f28a0e49971 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /lib64/libQt5XcbQpa.so.5 #10 0x00007f28cd9d08bf in QOpenGLContext::create() () from /lib64/libQt5Gui.so.5 #11 0x00007f28c3425b44 in QtWebEngineCore::initialize() () from /lib64/libQt5WebEngineCore.so.5 #12 0x00007f28cd457f8f in QCoreApplicationPrivate::init() () from /lib64/libQt5Core.so.5 #13 0x00007f28cd995e6c in QGuiApplicationPrivate::init() () from /lib64/libQt5Gui.so.5 #14 0x00007f28ce09c8a9 in QApplicationPrivate::init() () from /lib64/libQt5Widgets.so.5 #15 0x00007f28d291e9a4 in KontactInterface::PimUniqueApplication::PimUniqueApplication(int&, char***) () from /lib64/libKF5KontactInterface.so.5 #16 0x0000558b7a3e1a42 in main ()
Output from the shell: $ dbus-launch kmail libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Could not initialize GLX KCrash: Application 'kmail' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5_localhost_10 kf5.kwidgetsaddons: Invalid pixmap specified. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast No XVisualInfo for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(SingleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Falling back to using screens root_visual. [1]+ Stopped dbus-launch kmail
> libGL error: No matching fbConfigs or visuals found > libGL error: failed to load driver: swrast You're missing mesa-dri-drivers on the remote machine.
On the laptop I ssh into to run kmail: # dnf list mesa* Last metadata expiration check: 0:38:08 ago on Wed 04 Oct 2017 12:56:14 AEDT. Installed Packages mesa-dri-drivers.x86_64 17.2.1-1.fc27 @updates-testing mesa-filesystem.x86_64 17.2.1-1.fc27 @updates-testing mesa-libEGL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libGL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libGLU.x86_64 9.0.0-13.fc27 @fedora mesa-libOpenCL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libgbm.x86_64 17.2.1-1.fc27 @updates-testing mesa-libglapi.x86_64 17.2.1-1.fc27 @updates-testing mesa-libwayland-egl.x86_64 17.2.1-1.fc27 @updates-testing mesa-libxatracker.x86_64 17.2.1-1.fc27 @updates-testing On the machine I'm SSH'ing FROM: # dnf list mesa* Last metadata expiration check: 0:22:26 ago on Wed 04 Oct 2017 13:11:39 AEDT. Installed Packages mesa-dri-drivers.i686 17.2.1-1.fc27 @updates-testing mesa-dri-drivers.x86_64 17.2.1-1.fc27 @updates-testing mesa-filesystem.i686 17.2.1-1.fc27 @updates-testing mesa-filesystem.x86_64 17.2.1-1.fc27 @updates-testing mesa-libEGL.i686 17.2.1-1.fc27 @updates-testing mesa-libEGL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libGL.i686 17.2.1-1.fc27 @updates-testing mesa-libGL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libGLU.x86_64 9.0.0-13.fc27 @fedora mesa-libOpenCL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libgbm.i686 17.2.1-1.fc27 @updates-testing mesa-libgbm.x86_64 17.2.1-1.fc27 @updates-testing mesa-libglapi.i686 17.2.1-1.fc27 @updates-testing mesa-libglapi.x86_64 17.2.1-1.fc27 @updates-testing mesa-libwayland-egl.i686 17.2.1-1.fc27 @updates-testing mesa-libwayland-egl.x86_64 17.2.1-1.fc27 @updates-testing mesa-vulkan-drivers.x86_64 17.2.1-1.fc27 @updates-testing
Thank you for reporting this issue 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 "REPORTED" when replying. Thank you!
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!
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!