Bug 24027 - dolphin 'places' panel no longer shows network
Summary: dolphin 'places' panel no longer shows network
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-17 20:41 CET by Barry Jackson
Modified: 2020-06-07 01:54 CEST (History)
2 users (show)

See Also:
Source RPM: dolphin-18.08.3-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Barry Jackson 2018-12-17 20:41:13 CET
Description of problem:
In Mga6 the Places side panel shows Network accessible machines. This has been missing in Cauldron for some time.
This was really useful and I find myself re-booting into Mga6 when I want this feature.

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


How reproducible:
Always

Steps to Reproduce:
1. Open Dolphin, 
2. Hit F9 to open Places panel
3. Network option is missing
Comment 1 James Kerr 2018-12-17 21:12:30 CET
I have a section "Remote" which includes "Network".

Have you perhaps hidden the "Remote" section? If you right-click on "Places" you should see toggles to show all entries and to hide/unhide sections.

CC: (none) => jim

Comment 2 Barry Jackson 2018-12-18 01:27:19 CET
Hi Jim,
Well no, I don't have that either, however in a new user, which I had not tried I do have remote, and it shows network and appears to work.

It's not worked in my normal profile in cauldron at all since one of the plasma updates in Mga7 cauldron, but using the same /home for Mga6 it works fine, so I assumed it was a bug in plasma which would eventually be fixed. :(

I will leave this open for a while in case someone knows how to fix it. I don't want to trash .KDE or similar as it will break my settings for Mga6.

Thanks for your help.

Barry
Marja Van Waes 2018-12-19 08:41:13 CET

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

Comment 3 Barry Jackson 2020-06-07 01:54:51 CEST
Problem seems fixed now, so closing.

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


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