after use you click the close box ,after system restart each instance is at the start screen! if you have renamed 5 directory's 5 instances appear on system restart! if you rename enough directory's dolphin will slow down and crash ! restart login is also very slow ,after closing running instances all is good! STEPS TO REPRODUCE 1. use program 2. close with dialog box 3. restart system OBSERVED RESULT program start screen running at log in and instances running in task bar EXPECTED RESULT program closes with close dialog SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: Ubuntu Studio 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-53-lowlatency OS Type: 64-bit Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 970/PCIe/SSE2 ADDITIONAL INFORMATION krename
Which version of krename? If it's 5.0.0 it's likely a duplicate of https://bugs.kde.org/show_bug.cgi?id=398429 which should be fixed in 5.0.1.
Created attachment 138980 [details] attachment-933-0.html ________________________________ From: Heiko Becker <bugzilla_noreply@kde.org> Sent: 03 June 2021 14:44 To: mvggg@hotmail.com <mvggg@hotmail.com> Subject: [krename] [Bug 438034] program remains running after system restart https://bugs.kde.org/show_bug.cgi?id=438034 Heiko Becker <heiko.becker@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #1 from Heiko Becker <heiko.becker@kde.org> --- Which version of krename? If it's 5.0.0 it's likely a duplicate of https://bugs.kde.org/show_bug.cgi?id=398429 which should be fixed in 5.0.1. Yes Thanks i look forward to the next upgrade in a few months! mike -- You are receiving this mail because: You reported the bug.
Thanks for the confirmation. You should ask your distro to add it. 5.0.1 was released 8 months ago. *** This bug has been marked as a duplicate of bug 398429 ***