Salix Forums

Dear Salixer,

I noticed that Shotwell did not run under salix 1337. Recently somehow something changed and it did run .
But now under fluxbox or openbox if I run shotwell (from the cli or as a selection from the menu) it will not run
and i get 100% memory usage in htop.

However when I run shotwell in xfce then everything works ok.

I guess that I need some files starting up in the startup sections of fluxbox and openbox but what do i need??

Any suggestions

Marcel Geijsberts
The Netherlands

emgee_1 wrote:I guess that I need some files starting up in the startup sections of fluxbox and openbox but what do i need??

Maybe dbus? It seems weird that this gives you 100% memory usage though. Never seen this and don't see how this should relate to missing dbus. Apart from that one usually gets an error message from the application if it's missing dbus, which is more or less informative.

Actually shotwell starts under fluxbox but nothing in the gui works; it takes the full 100% of one of the two cores of a dual core laptop. Under xfce however it works normally (same problem under openbox).

Since I prefer working under flux or openbox I now do not know if there are some extra programs that need to be started before some apps work properly

Marcel

CPU usage is quite different than memory usage.
That makes a big difference. Getting 100% memory usage would take quite a while, would mean memory allocation continues and thus swap space starts to be used, which would mean the system becomes terribly unresponsive. This does not usually happen because of a small mistake, although on the long run a small memory leak could, but that's a slow process. For high cpu usage an accidental polling loop can be enough, which can happen quite easily.

Also an application that "will not run" is different then an application which does run/start but does not respond. "will not run" is more like it doesn't start at all and though it is less vague than "doesn't work", it's still extremely vague. Please be more precise in the first place.
"nothing in the gui works" is already much more precise than "it doesn't work", but could you describe a bit more exact please what you're experiencing. "Does not work" can be any supposed misbehavior especially to a non-dev.

emgee_1 wrote:Since I prefer working under flux or openbox I now do not know if there are some extra programs that need to be started before some apps work properly

I don't know either. Did you try dbus? I can only tell you that it works here with openbox, but I don't now how your setup is different than mine. Are there any error messages?

Sorry for my late reply. I guess the problem was connected with an upgrade to kde 4.7.1 which fundamentally changed my laptop.

Solved the issue by reinstalling 1337 xfce again and staying at xfce for now

Thanks for your help and ideas, btw dbus was running.

Greetings marcel

Why didn't you tell that in the first place? Would you call a doctor and ask him, what to do about not being able to walk and in the end when he doesn't have anymore ideas you tell him, that both your legs have been amputated?

Yes your are absolutely right. When trying to look for ways why it would run on xfce and not on flux or openbox I had no clue first until I remembered installing kde 4.7.1 which changed the setup of the laptop.

My bad. Sorry

Now running vanilla Salix xfce and loving it.

Thanks

Marcel

Upgrading KDE from non Salix repositories probably changes a lot of libraries which may result in major problems