Bug 438870 - Opening files wrongly causes the previous opening task to be performed
Summary: Opening files wrongly causes the previous opening task to be performed
Status: RESOLVED DUPLICATE of bug 438313
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.83.0
Platform: Neon Linux
: NOR grave
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-18 14:58 UTC by geisserml
Modified: 2021-06-22 03:24 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description geisserml 2021-06-18 14:58:39 UTC
SUMMARY
Since a recent update (frameworks or plasma), opening files and starting programs is completely flawed:
- Double-clicking on a file to open it takes no effect at first. When trying to open another file, the file that should have been opened before is opened
- starting a program from the application launcher also wrongly performs the previous launching task
- unpacking archives (eg. tar/zip) triggers the previous unpacking task

Probably you are addressing the wrong index of a queue. Quite nasty this distrubing regression slipped into a stable release (sorry).


STEPS TO REPRODUCE
1. Login to a Plasma Wayland session
2. Attempt to launch a program from kickoff
3. Attempt to launch another program

OBSERVED RESULT
First launch: Nothing happens
Second launch: The previous task will be performed.
The same accounts for opening files and unpacking archives, maybe more.

EXPECTED RESULT
The current task should be called, not the previous one.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-55-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000

ADDITIONAL INFORMATION
Might be the wrong product.
Comment 1 Nate Graham 2021-06-22 03:24:57 UTC

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