Bug 17583 - An attempt to open file selector dialog in KWrite/Kate made immediately close of appliaction
Summary: An attempt to open file selector dialog in KWrite/Kate made immediately close...
Status: RESOLVED DUPLICATE of bug 17545
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-23 02:04 CET by Piotr Mierzwinski
Modified: 2016-01-23 10:43 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
environment in konsole (4.22 KB, text/plain)
2016-01-23 02:06 CET, Piotr Mierzwinski
Details
environment in krunner (1.89 KB, text/plain)
2016-01-23 02:06 CET, Piotr Mierzwinski
Details

Description Piotr Mierzwinski 2016-01-23 02:04:55 CET
Description of problem:
When I run kwrite or kate and invoke option Open or Save as then application is closing immediately. I run both application using Alt+F2 or using KMenu. But when I run these applications from konsole then everything is OK - I get file selector dialog.
I attached my setting of all environment variables (generated from konsole and from krunner).

Version-Release number of selected component (if applicable):
kate/kwrite 15.12.1
KDE Releases Frameworks 5.18.0
Qt-5.6.0

How reproducible:
everytime

Steps to Reproduce:
1. Alt+F2
2. type kwrite
3. invoke Open option


Reproducible: 

Steps to Reproduce:
Comment 1 Piotr Mierzwinski 2016-01-23 02:06:01 CET
Created attachment 7371 [details]
environment in konsole
Comment 2 Piotr Mierzwinski 2016-01-23 02:06:24 CET
Created attachment 7372 [details]
environment in krunner
Comment 3 Frank Griffin 2016-01-23 02:53:44 CET
probable dup of https://bugs.mageia.org/show_bug.cgi?id=17443

CC: (none) => ftg

Comment 4 Rémi Verschelde 2016-01-23 10:43:14 CET
(In reply to Frank Griffin from comment #3)
> probable dup of https://bugs.mageia.org/show_bug.cgi?id=17443

Probably related, but at least it's likely a dup of bug 17545.

*** This bug has been marked as a duplicate of bug 17545 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.