On Wednesday 19 March 2003 06:40 am, jpre wrote: > http://qa.mandrakesoft.com/show_bug.cgi?id=3081 > > > > > > ------- Additional Comments From [EMAIL PROTECTED] 2003-03-19 12:40 ------- > > I confirmed the effect also on beeing on X-consoles of Solaris 8, AIX > 4.4.3 and HP-UX 11.11. As an example it wasn't possible to start kpat > and kcontrol on original CDE windows managers. > > Following messages (from HP-UX 11i Console): > > [EMAIL PROTECTED] jpre]$ kpat& > [1] 21248 > [EMAIL PROTECTED] jpre]$ Xlib: extension "GLX" missing on display "localhost > > :10.0". > > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > kbuildsycoca running... > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "RENDER" missing on display "localhost:10.0". > Mutex destroy failure: Device or resource busy > > [1]+ Exit 253 kpat > [EMAIL PROTECTED] jpre]$ kcon > kconf_update kcontrol > [EMAIL PROTECTED] jpre]$ kcontrol & > [1] 21300 > [EMAIL PROTECTED] jpre]$ kbuildsycoca running... > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "RENDER" missing on display "localhost:10.0". > DCOP aborting call from 'anonymous-21300' to 'kcontrol' > ERROR: KUniqueApplication: DCOP communication error! > Mutex destroy failure: Device or resource busy > > [1]+ Exit 255 kcontrol > > This is to add to my formerly opened bug report #3129. Note the > different return codes. > > It's possibly an "misuse" of XF86free features by developers, witch > makes it incompatible to X11 industry standards. May be an qt/Xlib-Problem. > > With regards. > > Juergen > > > I confirmed the effect also on beeing on X-consoles of Solaris 8, AIX > 4.4.3 and HP-UX 11.11. As an example it wasn't possible to start kpat > and kcontrol. > > Following messages (from HP-UX 11i Console) with different return code: > > [EMAIL PROTECTED] jpre]$ kpat& > [1] 21248 > [EMAIL PROTECTED] jpre]$ Xlib: extension "GLX" missing on display "localhost > > :10.0". > > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > kbuildsycoca running... > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "RENDER" missing on display "localhost:10.0". > Mutex destroy failure: Device or resource busy > > [1]+ Exit 253 kpat > [EMAIL PROTECTED] jpre]$ kcon > kconf_update kcontrol > [EMAIL PROTECTED] jpre]$ kcontrol & > [1] 21300 > [EMAIL PROTECTED] jpre]$ kbuildsycoca running... > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "GLX" missing on display "localhost:10.0". > Xlib: extension "RENDER" missing on display "localhost:10.0". > DCOP aborting call from 'anonymous-21300' to 'kcontrol' > ERROR: KUniqueApplication: DCOP communication error! > Mutex destroy failure: Device or resource busy > > [1]+ Exit 255 kcontrol > > This is to add to my formerly opened bug report #3129. Note the > different return codes. > > It's possibly an "misuse" of XF86free features of developers, witch > makes it incompatible to X11 industry standards. > > With regards. > > [EMAIL PROTECTED] > > ---------- > Gesendet: Mittwoch, 19. März 2003 05:40 > An: [EMAIL PROTECTED] > Betreff: [Bug 3081] [galaxy-kde] Galaxy causing problems with KDE and > GNOME running in tightvnc-server > > http://qa.mandrakesoft.com/show_bug.cgi?id=3081 > > > > > > ------- Additional Comments From [EMAIL PROTECTED] 2003-03-19 05:40 > ------- > setting QT_XFT=no didn't work. > > > > > ------- 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? > > > > > ------- 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?
I re-installed libqt3.1.1-11 and libqt3-common from RC-1 and TightVnc works fine with KDE and Gnome now..
