It was not great before, but now under our opensuse 12.3 and factory, I get > Terminal& (aliased to xfce4-terminal) (Terminal:48659): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0) Failed to connect to session manager: Failed to connect to the session manager: networkIdsList argument is NULL How do I shut thse messsages off w/o redirecting all output to /dev/null? And more recently this was added -- indicating a parse of the entire font-config rulebase: > Terminal Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. (Terminal:48659): GLib-WARNING **: (gerror.c:390):g_error_new_valist: runtime check failed: (domain != 0) Failed to connect to session manager: Failed to connect to the session manager: networkIdsList argument is NULL --- They changed locations of your font.conf again, so we get to play catchup -- but again.. not something I need to see on each startup. No doubt you these are coming out of some [becoming sleezy] library you guys are using that used to be good. Now it's just becoming a liability. If I want to see all those messages, let me turn on --verbose, or --debug, or something else...but by default? in a terminal window? (Terminal is far from being the worst offender, just one that I happen to use alot! ;-))... Maybe you guys could tell the lib guys to stop leaving doodoo on my screen? Maybe a log file would be more appropriate place for these, by default? Since the desktop (open desktop and their systemd stuff) is going the way of windows, maybe it's time to start an application log to send application messages to?... (dunno if you are involved in that crowd, but they are such MS-drones -- makes me shiver -- seen MS do this before -- flood open-standard committees and projects with "their own" -- who move the products to be more along lines of what MS wants...UH... (have done this with ID3v2 Music tag group for 10-15 years -- got them to accept Unicode only in UTF-16, and refused to allow them to move forward to ID3v4 that allows UTF-8)...even put in code in their media players to refused to play UTF-8 encoded-tagged songs...GRRR, but that's an aside)... Down with 'doo doo' on user's screen! ;-)
Fixed the GLib-WARNING but the test is just mis-configuration of the system, not much we can do about that.
> "mis-configuration of the system, not much we can do about that.?" ---- Well, that's sorta the point. The old version with the same system configuration didn't put out those errors. The new behavior seems to be looking for something I don't have on my system. You can say my system is misconfigured, but the previous version didn't have issue with the configuration. I remotely login via ssh, and start Terminal. Where's this 'Session manager' it thinks it wants? Does it want to talk to sshd? for what? Does it want to talk to the windows 7 desktop where I am logging in from? I seriously doubt it is any of those. Can you elaborate on why you think my windows desktop is misconfigured? (don't take my question personally -- it seems like alot of new products are creating all sorts of new hurdles to compatibility....).. Did you really fix the incompatibility problem or are you assuming it's a misconfiguration on the part of a remote client logging in?