Bug 18836 - konqueror gets stuck the second time it is invoked as the current user.
Summary: konqueror gets stuck the second time it is invoked as the current user.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-01 16:54 CEST by Shlomi Fish
Modified: 2017-03-18 08:35 CET (History)
2 users (show)

See Also:
Source RPM: kdebase4-16.04.1-1.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Shlomi Fish 2016-07-01 16:54:24 CEST 
Description of problem:

If I invoke "konqueror ~/Music/mp3s/Grayscale/" and exits it properly, then the second time it gets stuck. Also happens in a new user in JWM.

Version-Release number of selected component (if applicable):

Cauldron.

How reproducible:

Always.

Steps to Reproduce:
1. startx as a new user.
2. invoke konqueror on a local directory from a terminal.
3. Exit it.
4. invoke it again.
Marja Van Waes 2016-07-03 05:39:52 CEST

CC: (none) => marja11
Assignee: bugsquad => mageia

Samuel Verschelde 2016-08-25 16:25:13 CEST

Assignee: mageia => kde

Comment 1 Nicolas Lécureuil 2017-03-18 01:45:10 CET 
is it still valid with current cauldron ?

CC: (none) => mageia

Comment 2 Shlomi Fish 2017-03-18 08:35:41 CET 
(In reply to Nicolas Lécureuil from comment #1)
> is it still valid with current cauldron ?

No, this use case is working fine here. I'm going to close this bug report. Thanks!

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.