good morning (as it is here)

I have chosen at this stage to not attach all the errors or file dumps and to see what 'you' think initially and some ideas about whats going on and indeed, if any one else has come across the problem.

asus 1225b radeon 6290 brazos apu 4gb ram

scenario:
Starting desktop (only xfce4) using startx from init3.

experience:
I gave up on XFCE4 .... so many errors displayed on console once logged out. Glib errors, console errors, XIO etc.

This is with a 'default' from iso install in essence.

Has any one else had this ?


scenario:

xwmconfig to switch to openbox wm (compiled and installed from slackbuilds)

openbox on its own (not loading any apps) is fine and when logout, no errors on console - yipee!

Try Firefox..... Glib error CRITICAL all the time

Try conky (interesting this)....
- from within openbox, open xterm and run conky & , no problems
- from within autostart, or within .xinitrc , once logged out there are XIO errors reported regarding X trying to shutdown (conky i think)


I am guessing this is not a slackware (or kernel) problem, but one of various bits of software just not hanging together.

I am a little dismayed (i can only be challenged so far, being limited experience in linux) before it gets tedious.

On other distros, I do not recall experiencing this.... orseeing similar messages in logs or on console. Why is that ?

However, I will persevere.....it teaches one a bit about underpinnings of linux and setup etc.... something the other distros hide for you. Plus it seems quite snappy once booted.

I'm sorry for the ramble, but out of chaos comes order and clarity (hopefully). Any high level views, comments, similar experiences really welcome. I will then go away and explore some more.

Thank you

Like this?
Many upstream projects include debug and warning messages that they have forgotten or ignored. Or (for example) XFCE might misuse GTK in an unanticipated but harmless way. Or (for example) Glib might have changed something, and the messages are an ineffective, clumsy, but sadly very common way of bringing the change to other projects' attention.

Other Linux distributions may well hide these messages from you -- and Windows hides them too, in the case of cross-platform applications -- by throwing away all the error and warning messages (which is one reason why many of these messages have been forgotten or ignored).

Slackware, however, tries "to bring software to you in the condition that the authors intended". Such messages are one consequence of that policy. If you choose to disrespect software that produces such incontinent messages, then that is a perfectly rational judgment that is empowered by Slackware's policy. Or, if the software works perfectly well apart from the messages, you could just ignore the messages; that also is a perfectly rational judgment.

Or, if you do see actual bad behaviour, you are welcome to report the messages to us or to the relevant upstream project. If the messages were thrown away, we'd all have to guess what was going wrong -- just like Windows

i quite agree, its better to see useful important messages..and wonder if they are of issue (CRITICAL would give that impression to a relative slackware [or any distro, if they were as obvious] newbie) . I was just concerned at the amount after a session... but i am a little reassured (on face value) by your comments.. .... and yes i gave up using micro$haft quite some time ago :-)

thank you for your reply.

I also get these messages, and have gotten them for quite a while with many different programs. Just ignore them if you don't also see any actual problems associated with the messages. You can also try to identify the program which caused them, say by process id, and investigate further.

Yes, you're right. But developers (and, where applicable, managers) are basically drama queens, and they create software in their own image. Alas.

1 members found this post helpful.