http://qa.mandrakesoft.com/show_bug.cgi?id=3081
------- Additional Comments From [EMAIL PROTECTED] 2003-03-19 04:55 ------- It looks like the cause of this was not Galaxy, but the patch16 applied for libqt3-3.1.1-13mdk. I rebuilt the src.rpm with the specfile for -12mdk in cvs and the problem has gone away. KDE and KDE apps run fine in vnc. I have not tested Xnest, perhaps someone can do that and report here, but I assume it will be fine. The patched turned on Xft and AA by default. This change required the render extension on the Xserver, which vnc and xnest do not provide. Can this be fixed without turning off default AA? ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: Both KDE and GNOME seem to be having trouble with Galaxy tightvnc-server-1.2.7-2. It seems to be focused on Galaxy-KDE as explained later. Fluxbox works just fine, just GNOME and KDE have exhibited issues. KDE loads the wallpaper and then various components seem to go flashing by like a grey bar where the kicker is supposed to be. Eventually ending up with a screen shot like this. http://www.gkmweb.com/images/9.1-KDE_vnc.jpg The desktop keeps flashing periodically. GNOME has a similar behavior in that it flashes, but the desktop seems to load. Occasionally after one of the flashes, an error message pops up a dialogue box that says KDesktop error. Sorry, i was not able to capture it. I thought maybe the Galaxy theme had something to do with it, so I switched KDE to the Keramik theme, and it still exhibited this behavior, although the the error message and the flashing stopped occurring when GNOME was running. So maybe it does belong to Galaxy, and that led me to post it here as a KDE-Galaxy bug. vnc logs have nothing interesting in them and the system logs are equally bare on this issue. What else can I do to help troubleshoot?
