Bug 359646 - Accessing the device fs via status bar icon launches dolphin recursively ad-infinitum: fork-bomb
Summary: Accessing the device fs via status bar icon launches dolphin recursively ad-i...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdeconnect
Classification: Applications
Component: plasmoid (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-21 18:46 UTC by TonyP
Modified: 2018-09-26 23:47 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description TonyP 2016-02-21 18:46:05 UTC
ver = 0.9git 20160214...(and more numbers)

1. Click on icon in taskbar, get KDE Connect 'notification' pane with device statuses.
2. Click on file browser icon
3. Get 'open with' dialog: select dolphin.
4. Get Dolphin instance and another 'open with' dialog :select dolphin.
5. GOTO 4.....
Do something else, then try again.
6. Repeat above, but, on 3, absent-mindedly check 'remember application association...' checkbox.
7. Frantically attempt to close dolphin instances faster than they propagate.
8. Seek treatment for RSI of mouse button finger.

File browsing works OK for me from a normally opened Dolphin instance when I click on one of the Kdeconnect  device icons in the places sidebar.

Reproducible: Always

Steps to Reproduce:
See details

Actual Results:  
OMFG

Expected Results:  
Visibility of paired device storage

This is nasty. Of course, if it happens to someone else it's potentially very funny.
I've called this a crash: I guess if I don't click fast enough, the Dolphin instances will take my session down.
Comment 1 Albert Vaca Cintora 2016-02-29 21:52:15 UTC
How do you get that "open with" dialog to appear? Is it because you have more than one file browser installed? To me that button just launches dolphin, I don't get that dialog at all.

Can try running "xdg-open $HOME" and say if it triggers the same message?
Comment 2 Nicolas Fella 2018-09-26 23:47:44 UTC
Closing as outdated. If the problem persists in recent version please reopen