Bug 427927 - Opening Veracrypt file in Kate sometimes causes Kate to immediately quit after launching
Summary: Opening Veracrypt file in Kate sometimes causes Kate to immediately quit afte...
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 19.12.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-18 13:56 UTC by Ian Proudler
Modified: 2022-09-12 07:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Proudler 2020-10-18 13:56:07 UTC
SUMMARY
Double clicking on volume in the VeraCrypt window launches a Dolphin window but double clicking on an file icon does not open the file. 


STEPS TO REPRODUCE
1. Start VeraCrypt.
2. Select and mount encrypted file.
3. Double click on volume in VeraCrypt widow (Dolphin windows appears)
4. In Dolphin windows double click on text file icon.

OBSERVED RESULT
A Kate icon appears next to Mouse cursor and an entry for Kate appears in the task manger for a fraction of a second then they both disappear.


EXPECTED RESULT
Kate is launched with the selected file open.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: plasmashell 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: Qt: 5.12.8

ADDITIONAL INFORMATION
Kunbuntu 20.04.1

If instead of clicking on the VeraCrypt window to launch Dolphin, one starts Dolphin manually and moves to the mount point of the VeraCrypt volume, double clicking on the file icon works. 

If one dismounts the VeraCrypt volume but leaves VeraCrypt running, and then remounts the volume, everything works as expected.
Comment 1 Nate Graham 2020-10-18 19:33:26 UTC
It sounds like Kate is trying--and failing--to open the file.

Can you do the following?

1. Open Konsole
2. type `kate` and a space
3. Drag the file in question into the Konsole window
4. Hit the return key


Can you describe what happens, and paste in the contents of the Konsole window after doing this?
Comment 2 Ian Proudler 2020-10-19 10:02:33 UTC
I did the following:
1. Open Konsole
2. type `kate` and a space
3. Drag the file in question into the Konsole window
4. Hit the return key

Kate opened the file successfully. There were no error/warning messages.

I started over again but this time I started kate from a terminal before starting veracrypt from another terminal. The file opened successfully. There were no error/warning messages in either terminal.

I checked the systemd log. There was nothing in the log that had a suitable timestamp that seemed appropriate.

I started over again but this time I started dolphin from a terminal before starting veracrypt. Clicking on the volume in the VeraCrypt window launched a new tab in the Dolphin window. Double clicking on an file icon successfully open the file in kate. There were some messages in the terminal:

Skipped method "changeUrl" : Type not registered with QtDBus in parameter list: QUrl
Skipped method "slotTerminalDirectoryChanged" : Type not registered with QtDBus in parameter list: QUrl
Skipped method "openNewTabAfterCurrentTab" : Type not registered with QtDBus in parameter list: QUrl
Skipped method "openNewTabAfterLastTab" : Type not registered with QtDBus in parameter list: QUrl
Unsupported return type 65 QPixmap in method "grab"
Unsupported return type 65 QPixmap in method "grab"

I did a web search and found that one can look at standout and standerr for a detached process via /proc. I then did the following:
1. Start VeraCrypt.
2. Select and mount encrypted file.
3. Double click on volume in VeraCrypt widow (Dolphin windows appears)
4. In a terminal, I located the pid of the dolphin instance (8223)
5. cd /proc/8223/fd
6. tail -f 2
7. In the Dolphin window double click on text file icon.

Kate started and opened the file.

I then quit the 'tail' process and double clicked on text file icon in the Dolphin window. The bug appeared: a Kate icon appears next to Mouse cursor and an entry for Kate appears in the task manger for a fraction of a second then they both disappear.

I then started a new 'tail' process in the terminal and double clicked on text file icon in the Dolphin window. Kate started and opened the file.
Comment 3 Nate Graham 2020-10-19 14:20:14 UTC
Thanks. Seems like Kate may be doing something a bit odd. Moving the bug there.
Comment 4 Christoph Cullmann 2022-03-05 20:25:11 UTC
Kate uses just normal KIO to access the file.
I don't see how we can do this wrong just for this type of file.
Comment 5 Christoph Cullmann 2022-08-27 18:40:50 UTC
Hi, sorry, I don't think this can be fixed in Kate.

Kate just uses KIO for file handling.

I would rather assume there is something strange happening with the way VeraCrypt mounts the stuff.

Could you re-try with a more recent version. e.g. out of 2022?
Thanks!

(and not just Kate, but the system, too)
Comment 6 Ian Proudler 2022-08-28 17:00:48 UTC
I am now running Kubuntu 22.04. I've just pulled down the latest Veracrypt (1.25.9). 

The problem persists except that I can no longer see any messages by starting dolphin from a terminal  or looking at /proc. I also cannot see any relevant messages in the system logs.

Any suggestions as to how to get more debug info on this issue?

Ian

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-46-generic (64-bit)
Graphics Platform: X11
Comment 7 Christoph Cullmann 2022-08-28 17:27:35 UTC
Hi, sorry, have no idea, I have no clue how VeraCrypt works in that regard.
We do nothing special there, for local files, we just end up using the Qt API and that will use whatever libc provides.
Comment 8 Ian Proudler 2022-08-28 18:57:33 UTC
Fair enough. Thanks for having a look.
Ian
Comment 9 Bug Janitor Service 2022-09-12 04:36:29 UTC
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!