https://bugzilla.novell.com/show_bug.cgi?id=715265
https://bugzilla.novell.com/show_bug.cgi?id=715265#c15
--- Comment #15 from Wolfgang Bauer
The crash is not the only bug that removes remote login functionality, hence fixing it makes zero difference to the functionality being available, the problem being fixed and this bug being dealt with!
So what? To follow your reasoning: The input focus issue and the automatic display of remote hosts have not been the only bugs that remove remote login funcionality, hence fixing them would have made zero difference to the functionality being available... (if that crash would still be present, that is) Anyway, it was KDE upstream who fixed that crash. Do you want openSUSE to revert that? :-P If you argue that way, nothing at all should be fixed here. I don't think that's what you have in mind. You have your open bug report anyway with bnc#859711. What sense does this discussion make? None at all. So that's it now for me.
Yes I expect it to be just a kdm problem as well. Changes that caused the crash also caused other (still to be fixed) problems. Difficult to test whether XDMCP still works if one doesn't even get as far as opening that connection...
As I said, you could test XDMCP by using a different display manager f.e. That would be more productive than this discussion here.
From looking at login managers some while back I got the distinct impression that suse always uses kdm, regardless of desktop. I may have been wrong, and it may be different now.
I doubt that you ever got KDM when choosing GNOME during installation or installed from the GNOME LiveCD. Btw, if there only ever was KDM on (open)SUSE, then why have there been all those display manager settings in /etc/sysconfig/? People even complained and filed bug reports for years that KDM's settings are not respected. The purpose of that was to have one configuration place for _all_ different display managers. That would not have been necessary or even reasonable if (open)SUSE always used KDM.
Big bitmap block rendering errors, requiring turning off various of the VNC protocol features. Unusable UI, useless performance. Both vncviewer and krdc clients. Would like to know what clients and servers you used - thanks!
As server whatever was installed/used by default when you enabled VNC in YaST. As client I mostly used KRDC, but also the Java client you get when you open http://host:5901 in a web browser. With both I didn't see rendering errors and never had to change any server or client settings. And it was usable, even via HTTP/java. And then of course I often used (and still use) ssh with X forwarding.
Anyway, further details and information about the bug should be posted in other bug reports now that are still open.
Other than bug 859711?
No, exactly in 859711 e.g. if it is fitting there. But you may of course also add something to an upstream bug report. And if for example you find out that there's a problem with the XDCMP _server_ part, you should open a new bug report for that though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.