Bug 406396

Summary:	The Kate snap does not open files
Product:	[KDE Neon] neon	Reporter:	galileo.sartor
Component:	Snaps	Assignee:	Harald Sitter <sitter>
Status:	RESOLVED FIXED
Severity:	normal	CC:	dtrabazo, jr, neon-bugs-null, rocco.pietrini, sitter, wazhai
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description galileo.sartor 2019-04-10 08:14:52 UTC

I installed the kate snap. 

STEPS TO REPRODUCE
1. Install snap version
2. try opening a file

OBSERVED RESULT
I cannot find the project manager (to open a folder).
Also the open command in the menu does not open the dialog.
If I try opening an existing file from the terminal (kate example.txt) it will open a new file.
It will open the correct file only with a full path (This same issue affects the okular snap)

EXPECTED RESULT
Files and folders should open normally


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Ubuntu 18.10
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 
Up to date snap frameworks

ADDITIONAL INFORMATION

Comment 1 galileo.sartor 2019-04-15 09:40:56 UTC

The Ctrl-O and open command in the menu now work, although the dialog opens not selected, so in a lower level. If the application (kate) is fullscreen the dialog is not visible.
The same issue is present in Ubuntu Mate.

Comment 2 wazhai 2019-04-21 08:58:07 UTC

I am also experiencing this bug on Ubuntu 16.04. Neither the open nor save file dialog box show up. Channel stable 19.04.0

$ snap version
snap    2.38
snapd   2.38
series  16
ubuntu  16.04
kernel  4.15.0-47-generic

Comment 3 Jonathan Riddell 2019-04-26 10:14:48 UTC

file open and save do show.  the problem now is default directories are wrong.

Comment 4 rocco.pietrini 2019-07-24 20:36:33 UTC

same here.. Okular don't open any dialog clicking file->open, the same for every menu entry supposed to open a file dialog..

snap version 
snap    2.39.3
snapd   2.39.3
series  16
ubuntu  16.04
kernel  4.4.0-154-generic

Comment 5 rocco.pietrini 2019-08-08 18:32:55 UTC

one of the kernels between 4.4.0-155-generic and 4.4.0-157-generic
 have solved the problem