This problem has appeared since I installed the latest upgrade yesterday. The issue appears to be with KDEInit rather than Dolphin. Several applications won't launch from the Kickoff Application Launcher, for example System Settings, Kate, Konsole, sqliteman (one of mine), .... The applications are not corrupted: they can be launched from an xterm, or (once I have launched one from an xterm) a Konsole window. Some other applications will launch, for example FreeCAD, Evolution, Dolphin, FireFox, xterm, KPatience, xclock, Character Map, Ark, Calculator, KCalc, LibreOffice, .... Reproducible: Always Steps to Reproduce: 1. Right click in a directory window 2. Mouse press on Actions... and slide to Open Terminal Here Actual Results: Sometimes it does nothing: more often it pops up a window saying KDEInit could not launch '/usr/bin/konsole' When attempting to launch other applications from the Kickoff Application Launcher, it either does nothing or pops up a window saying KDEInit could not launch '<application file name>' Expected Results: Should open a Konsole window When attempting to launch other applications from the Kickoff Application Launcher, should launch the application. uname -a Linux rparkins48 3.13.0-96-generic #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux cat /etc/issue Ubuntu 14.04.5 LTS \n \l /home/rparkins/.kde/share/config/konsolerc [$Version] update_info=konsole.upd:2.9.0-global-options [Desktop Entry] DefaultProfile=Shell.profile [Favorite Profiles] Favorites=Hebrew.profile,Shell.profile [MainWindow] Height 1200=665 Height 1800=903 Height 2160=1044 State=AAAA/wAAAAD9AAAAAAAAA44AAAP4AAAABAAAAAQAAAAIAAAACPwAAAAA ToolBarsMovable=Disabled Width 1600=670 Width 3200=999 Width 3840=910
This was on the first reboot after installing the upgrade. Since then I've switched off my computer and rebooted it again. Now I can launch the applications that I couldn't launch before. This of course does not necessarily mean that the problem has gone away altogether, merely that it doesn't appear every time the system is booted up, or it may be specific to the upgrade process. I don't know how to check exactly what the upgrade installed, but I presume there is a log somewhere. If you can tell me where it is, I'll attach it. In case you ask about my hardware configuration (the bug submit form didn't) it's a Dell Precision M4800 with 16GB of memory 750Gb hard drive, and factory installed Ubuntu. I think they didn't install Kubuntu: I did that myself. I run it connected to the docking station with the lid closed and external mouse, keyboard, and monitor. The monitor is an AOC U2868PQU 28 Inch Ultra HD 4K, connected directly to the DP port on the laptop (it doesn't work well if connected through the docking station). I'm using NVIDIA drivers.
(In reply to Richard Parkins from comment #0) > This problem has appeared since I installed the latest upgrade yesterday. > The issue appears to be with KDEInit rather than Dolphin. Several > applications won't launch from the Kickoff Application Launcher, for example > System Settings, Kate, Konsole, sqliteman (one of mine), .... > > The applications are not corrupted: they can be launched from an xterm, or > (once I have launched one from an xterm) a Konsole window. > > Some other applications will launch, for example FreeCAD, Evolution, > Dolphin, FireFox, xterm, KPatience, xclock, Character Map, Ark, Calculator, > KCalc, LibreOffice, .... > > Reproducible: Always > > Steps to Reproduce: > 1. Right click in a directory window > 2. Mouse press on Actions... and slide to Open Terminal Here > > > Actual Results: > Sometimes it does nothing: more often it pops up a window saying > KDEInit could not launch '/usr/bin/konsole' > > When attempting to launch other applications from the Kickoff Application > Launcher, it either does nothing or pops up a window saying > KDEInit could not launch '<application file name>' > > (truncated quote) @Richard Parkins Could you reproduce such issue in latest version of Konsole and KDE platform? If not, cold you please close this bug as resolved? For your information, I see no such problem on my system, which has the following environment, ``` openSUSE Tumbleweed: 20181116 KDE Plasma: 5.14.3 Qt: 5.11.2 KDE Frameworks: 5.52.0 KDE Applications: 18.08.3 Kernel: 4.19.1-1-default ```
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!
I think NEEDSINFO here is a little unkind. I gave you all the information I knew how to get about the system at the time. I'm a user, not a developer: I can only install the software that Kubuntu provides for my system (actually I can't even do that at the moment since the upgrade path from Kubuntu 14.04 is still broken). I can't install an unspecified latest version, and to reproduce the problem I would need to restore my system to its state before the upgrade (this requires a full hard drive image which of course I don't have) and install the upgrade again. I wouldn't expect the problem to show up on a normally running system. It appears to be specifically triggered by the upgrade. It was hard reproducible on the first reboot after the upgrade. It disappeared when I rebooted again and has not reappeared since. This suggests something wrong with the script that gets executed on the first reboot after the upgrade. Possibly something isn't being initialised properly or it is trying to replace a file which has already been opened by another process. The fact that there are several programs which it can't launch, and others which it can launch, suggests a problem with a shared library. In a sense the underlying issue is the unhelpful error message. Presumably KDEinit got some specific error from some lower level library, but it threw away that information and just reported that it could not launch the program. This isn't very helpful for me as a user to work out what to do about it, or for the KDE developers to work out what was going wrong. If you need info, you need better error reporting from KDE itself, not info from the user. Perhaps we should recharacterise this bug as "uninformative error message".
> the upgrade path from Kubuntu 14.04 is still broken Please test if upgrading to 18.04 works.
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!
This bug report has not been considered for so long (more than six years) that I have changed my Linux distro in the meantime and I no longer have an Ubuntu system on which to try to reproduce it. It really is something of an insult to bug reporters to ask for reproduction information after six years of no action. Why should I bother to report problems?
I reported this bug in October 2016. No attempt was made to investigate it until December 2018. This is positively insulting to me as a bug reporter. If requests for further info are not made within a reasonable time there is no realistic prospect of the bug reporter being able to reproduce the environment in which the problem was observed. As reported in a previous comment, I no longer have the Linux distribution on which I saw it, so I cannot determine whether it is still present.
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!