Hardware: small dell server Software: Current version of Linux Centos with current version of KDE for Centos Note: This bug does not occur in KDE for RedHat On Centos machines, if I export display from two different servers using same username on both servers, Kwrite can only display Klauncher and list out files in the file open dialogue for the first server I attempt to open a file on. I have tried this with 2 different xclients -- this is not an xclient issue. However, if I am ssh'd into one server as "uname1" and ssh'd into the other server as "uname2", then the file open dialogue works for both exported kwrite windows. In Kwrite, when I ctrl-o to bring up the file open dialogue, a pop displays the following message: "Could not start process Cannot talk to klauncher: not connected to D-Bus server" Here are the errors on the second server when Kwrite is launched on the other server using the same username: kdeinit4: Communication error with launcher. Exiting! Xlib: extension "SYNC" missing on display "localhost:10.0". QPainter::setCompositionMode: PorterDuff modes not supported on device QPainter::setCompositionMode: PorterDuff modes not supported on device Xlib: extension "SYNC" missing on display "localhost:10.0". QPainter::setCompositionMode: PorterDuff modes not supported on device QPainter::setCompositionMode: PorterDuff modes not supported on device QPainter::setCompositionMode: PorterDuff modes not supported on device Xlib: extension "SYNC" missing on display "localhost:10.0". QPainter::setCompositionMode: PorterDuff modes not supported on device QPainter::setCompositionMode: PorterDuff modes not supported on device QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.ServiceUnknown" QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.ServiceUnknown" QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.ServiceUnknown" QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.ServiceUnknown" It appears when Kwrite is launched on the second server, it is attempting to talk to Dbus on the first server. Here is why I think this is the case: if I force kde to launch dbus first, and then bring up kwrite, it works fine: dbus-launch kwrite Until this bug is fixed, the workaround for Centos is to always launch kwrite using "dbus-launch kwrite" or "dbus-launch kwrite &". Reproducible: Always Steps to Reproduce: 1. See above 2. 3. Actual Results: See Details
Another way of putting this: It appears that when a kwrite session is launched from one server under a particular username, Kwrite does not see a new kwrite session launched from another server under the same username as being a new session requiring dbus to be launched.
Generic kdelibs problem I think :/
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
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!