https://bugs.kde.org/show_bug.cgi?id=369515

Richard Parkins <aleph0hpela-k...@yahoo.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDSINFO                   |REPORTED
         Resolution|WAITINGFORINFO              |---

--- Comment #4 from Richard Parkins <aleph0hpela-k...@yahoo.co.uk> ---
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".

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to