https://bugs.kde.org/show_bug.cgi?id=427924
--- Comment #7 from Christoph Feck ---
It is a bit unclear if Octave developers confirmed the issue is in Octave or in
KIO/kdialog. From what I understand, they are using QProcess to launch an
external kdialog application, and have issues with the proce
https://bugs.kde.org/show_bug.cgi?id=427924
Patrick Silva changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=427924
--- Comment #5 from Ian Proudler ---
Sorry about that I thought I had uploaded it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427924
--- Comment #4 from Ian Proudler ---
Created attachment 133463
--> https://bugs.kde.org/attachment.cgi?id=133463&action=edit
Screenshot of browser window
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427924
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #3 from Patrick
https://bugs.kde.org/show_bug.cgi?id=427924
--- Comment #2 from Ian Proudler ---
Christoph,
Screenshot attached.
Note I also raised the issue with the Octave people. This is a known issue:
___
Update of bug #59311 (project octave):
https://bugs.kde.org/show_bug.cgi?id=427924
Christoph Feck changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
