https://bugs.kde.org/show_bug.cgi?id=302295
--- Comment #19 from michael.zug...@college-de-france.fr --- While I see the developers' point, namely that the bug is actually outside Dolphin itself and would be better solved upstream, a more pragmatical approach may nonetheless be relevant. For average users (e.g. any of the 15 people in my team), it does not really matter in which library the bug is actually located: what they see is that Dolphin is frozen and does not work. It would therefore make a lot of sense to develop a temporary workaround within Dolphin until the real bug gets fixed. Keep in mind that Dolphin will freeze even when the user is merely trying to browse the local home: because the Places Panel will try to list the stalled share, Dolphin will freeze. For the last several years, the situation has been that people in my team complain that Dolphin does not work and I have to waste time trying to fix the mess. And it is really a pity because as a result, although everybody agrees on the principles of FOSS, none of them is actually able to run GNU/Linux at home because they don't know how to fix this kind of issues themselves. -- You are receiving this mail because: You are watching all bug changes.
