https://bugs.kde.org/show_bug.cgi?id=371513
--- Comment #14 from Sergey Kondakov <virtuous...@gmail.com> --- (In reply to Alex Bikadorov from comment #13) > Sorry, but its hard to debug as everything is working fine for me. Can you > test this in a KDE environment or with another pre-build package of 2.5.0? > Anything that can pinpoint the actual problem is helpful. If devs always could reproduce bugs just by launching their stuff, there wouldn't be any. I will not risk launching Plasma because the last time I did, it wrote a bunch of useless KDE configs and somehow broke startup of LXQt session altogether. Official openSUSE builds present the same problem. I have KDE_FULL_SESSION=false KDE_SESSION_VERSION=4 exported on LXQt session startup but launching krusader with any other values changes nothing. By the way, some KDE apps think that if KDE_FULL_SESSION exist with any non-empty value then it's equal to "true". That's dumb. > Also, can you rule out that something went wrong during building? I've put out full build and strace so *you* could answer that question to me. But if it would, OBS surely would fail the build. So, how about looking at which icons and in which order it tries to access in that krusader.strace.zip or comparing krusader's icon-loading code to dolphin ? -- You are receiving this mail because: You are watching all bug changes.
