https://bugs.kde.org/show_bug.cgi?id=474100
Jim <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Jim <[email protected]> --- (In reply to seth from comment #0) > Created attachment 161369 [details] > GDB trace > > SUMMARY > *** > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > *** > > When starting Dolphin either from terminal or the task bar there is a > noticeable lag/freeze before displaying contents in the main panel. I do not > have any customized shortcuts on the side and have changed it to default to > my home folder which doesn't have a lot of icons. It seems a lot like this > old closed bug https://bugs.kde.org/show_bug.cgi?id=283081 > > I have attached GDB output of Dolphin running with the problem based on > directions I found on the KDE site. > > I do get this error when launching from console, but it appears when Dolphin > is working normally so I am not sure it is related. Qt: Session management > error: networkIdsList argument is NULL > > This also impacts File Picker dialogs. I suspected it had something to do > with suspend but I have noticed it after using the computer for a while from > a fresh boot. > > STEPS TO REPRODUCE > 1. Start KDE and login > 2. Use computer for a bit, launch Dolphin or save a file in Kate. > > OBSERVED RESULT > > Dolphin hangs for a long time before displaying directory contents. > > EXPECTED RESULT > > Files display in a few seconds at max. > > SOFTWARE/OS VERSIONS > Operating System: Slackware 15.0 > KDE Plasma Version: 5.23.5 > KDE Frameworks Version: 5.90.0 > Qt Version: 5.15.3 > Kernel Version: 5.15.117 (64-bit) > Graphics Platform: Wayland > Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz > Memory: 31.1 GiB of RAM > Graphics Processor: Mesa Intel® Xe Graphics > > ADDITIONAL INFORMATION we found a possible solution to a similar issue on Fedora over at bug 513329. Do you have Samba configured on your device or an old smb.conf file sitting around? -- You are receiving this mail because: You are watching all bug changes.
