When I run krusader on fluxbox the tray icon is blank, it appears again when I dock another application, so krusader icon moves. If I run some applications in tray (some using kdocker) and try to change workspace with mouse wheel on toolbar, fluxbox crashes and I'm back to gdm. Still krusader didn't crash with fluxbox - it's running and takes almost 100% of cpu power. I can only guess that it has something to do with this tray icon - a click on this icon should minimalize krusader, but it stops working after some time=/ I've tried latest unstable version and stable one, I've compiled it with kde and javascript and without - every time it crashes. Kdocker used on krusader seems to stop this crash issue - at least if I don't use krusader's original tray icon. Reproducible: Always
krusader version? fluxbox version? emerge --info?
(In reply to comment #1) > krusader version? fluxbox version? emerge --info? > Krusader - both 1.80.0_beta2 and 1.70.1 Fluxbox - 1.0_rc3_p4949
Created attachment 124739 [details] emerge --info
More info given.
krusader crashes both x11-wm/fluxbox-1.0_rc3-r3 and x11-wm/fluxbox-1.0_rc3_p4949
This is not a krusader problem=( I didn't have any running and my system crashed again - I was right-clicking on amarok icon to turn it off. Maybe docking kde apps crash the system.
Well, not all KDE dockapps... I just docked the keyboard layout switcher (kxkb) with no problems. I was able to change desktops with the scrollwheel on the fluxbox toolbar, and right-click the kxkb icon with impunity. I'll try krusader once I get a chance to emerge it.
Okay, I actually emerged and ran krusader. However, I didn't get a krusader icon in the fluxbox systemtray at all, even after adding and removing kxkb a number of times. My current krusader install has for USE flags: -arts -debug -javascript kde xinerama Can you please explain to me exactly how to replicate this bug? Please make this as minimal as possible, such as "With fluxbox running an NO other apps, start <this app>, make sure <these options are set> and <do this> -> then it crashes"
At first I thought it was krusader - because of it using 100% of cpu after crash, but a few times a crash just happened, not connected to anything. I have: firestarter and ksynaptics (this two I had a long time ago, so probably it is not the point) and klipper in autostart. I start firefox and gnome-terminal and dock it with kdocker, start akregator (with dock icon enabled) and start krusader - I deleted my krusader configuration, so it is "fresh", and I get a tray icon - with kde flag in fluxbox and without it. I've tested it 5 minutes ago and it crashed eventually, but after a quite long time, use wheel, minimalize to tray and unminimalize apps, probably just use it for some time - I dock almost every application I use (most of the time the list above+amarok) and my system crashed more than 5 times today=( But I can't be more specific as I really don't know what it is - I hope that it isn't some kde configuration that is just set by me... krusader options (tested with other too) -arts -debug -elibc_FreeBSD javascript kde -xinerama
Well, maybe kdocker is the culprit then, as it seems to be present in all your bug reports. Could you try running for a while without it and see how it goes? I will try to run it here and see what happens, if anything.
Without kdocker nothing happened... So you may be right. Probably it won't be useful but this is log from my X session that crashed.
Created attachment 124778 [details] X server log
Without kdocker my system is stable now, so it is not krusader's fault.
I have my system running right now with kdocker and fluxbox (and very little else), and have experienced no problems (around 4 hours so far) I'll let it run overnight, but I'm not sure I'm going to be able to replicate this crash.
No crash yet, running kdocker in fluxbox for over 8 hours now. Any tips you can give me on how exactly to cause the crash would be helpful. Alternatively, you could perhaps try: - Attach your .xsession-errors file after a crash - Run fluxbox inside 'strace' and attach the output here - Compile fluxbox with debug symbols, run inside 'gdb' and send the backtrace of the crash here - Put 'ulimit -c unlimited' in your .fluxbox/startup just before fluxbox is actually started, then attach the core file here.
I've used my pc for whole day now with all programs running that were running before and no crash happened... Probably software update fixed the problem or removing firestarter (which is no longer in portage). Sorry for reporting a bug that miraculously fixed itself in a few days, I really don't know what produced the crashes, but they are gone now I think.
(In reply to comment #16) > Sorry for reporting a bug that miraculously fixed itself in a few days, I > really don't know what produced the crashes, but they are gone now I think. No, trust me... this is the best kind of bug to get :) Take care.
