Summary: | Freeze when trying to select default folder for group | ||
---|---|---|---|
Product: | [Applications] kget | Reporter: | lewiji |
Component: | Core | Assignee: | KGet authors <kget> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | wbauer1 |
Priority: | NOR | ||
Version: | 21.12.2 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Journal filtered by "kwin" saved from KsystemLog |
Created attachment 146997 [details] Journal filtered by "kwin" saved from KsystemLog SUMMARY The first time on this system I have launched KGet, which opened by association when clicking a `.torrent` file, I added some downloads, and then went to settings, Groups section, selected the default "My Downloads" group, and clicked Configure. Then I clicked the "open file dialog" button next to the "default folder" input. This resulted in the UI freezing; no file picker dialog appeared. I could move the "Group settings for my downloads" dialog around, but no UI elements could be selected or clicked, neither would the close button in the window decorations kill the dialog or the KGet main window. After killing the process, I opened KGet again and the downloads I'd added were all missing. On opening the settings again, and attempting to select the default folder again, the file picker UI appeared as normal. Subsequent attempts also worked as expected. STEPS TO REPRODUCE 1. Fresh install of KGet with no previous configuration. 2. Open KGet through opening an associated file such as `.torrent` 3. Add downloads to the list 4. Attempt to configure the default folder for the default group, via the "open file dialog" button OBSERVED RESULT UI freezes and unable to quit KGet by normal means; process must be killed. EXPECTED RESULT File picker dialog opens to select folder. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, Kernel 5.16.10, Plasma, X11 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION No particular errors or warnings outside of the ordinary noticed in the system log, compared to the second run when things worked as expected the log output was the same/similar.