Bug 430519 - 'places: devices' loads out-of-order and can't have items moved otherwise crashes/terminates
Summary: 'places: devices' loads out-of-order and can't have items moved otherwise cra...
Status: RESOLVED DUPLICATE of bug 430441
Alias: None
Product: dolphin
Classification: Applications
Component: panels: places (show other bugs)
Version: 20.12.0
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-18 00:53 UTC by David Chmelik
Modified: 2021-01-09 23:52 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David Chmelik 2020-12-18 00:53:13 UTC 
SUMMARY
The 'places: devices' section loads items out of alphabetical order (if mounted later) and you can't put them in the order you want (as can with 'places: places') or it crashes/terminates dolphin.

STEPS TO REPRODUCE
1. Mount some devices.
2. Mount more until they load out of alphabetical order
3. Try to put them in order (crash/termination.)

OBSERVED RESULT

Devices in some cases aren't mounted in alphabetical order and never can be put in the order the user wants or dolphin crashes/terminates.

EXPECTED RESULT

If you're using alphabetical order, keep using it.  If not--and anyway--let the user put devices in the order they want.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Slackware64 14+current/5.20.4
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Comment 1 Elvis Angelaccio 2020-12-28 20:36:18 UTC 

*** This bug has been marked as a duplicate of bug 430441 ***
Comment 2 David Chmelik 2021-01-05 20:15:00 UTC 
This is not a duplicate, because it happens to all entries under 'devices,' mounted or not.  First  I tried only four unmounted ones, all with the same effect.
Comment 3 Christoph Feck 2021-01-09 17:04:09 UTC 
Please retest with version 20.12.1. If you can still reproduce, please report with an updated backtrace.
Comment 4 David Chmelik 2021-01-09 23:52:24 UTC 
It's fixed now, for both mounted and non-mounted devices!