[Cooker] [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-31 06:39 --- What is the deal with every kde app giving: mutex destroy failure: Device or resource busy ? If I knew I'd file a separate bug report. --- 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?
[Cooker] [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-31 06:58 --- It seems you are in the right bug. DOes your video card not support render? --- 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?
[Cooker] [Bug 3081] [galaxy-kde] Galaxy causing problems with KDE and GNOME running in tightvnc-server
http://qa.mandrakesoft.com/show_bug.cgi?id=3081 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-03-29 20:25 --- *** Bug 3599 has been marked as a duplicate of this bug. *** --- 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?
[Cooker] [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-29 21:57 --- Backing out patch16 and rebuilding the qt source rpms fixes the vnc problem but you will take a small hit on the look of your fonts. Still AA but not as crisp. --- 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?
Re: [Cooker] [Bug 3081] [galaxy-kde] Galaxy causing problems with KDE and GNOME running in tightvnc-server
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 253kpat [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 255kcontrol 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 253kpat [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 255kcontrol 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
[Cooker] [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 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 253kpat [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 255kcontrol 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 253kpat [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 255kcontrol 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
[Cooker] [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 04:50 --- I've been told to go into sessions under GNOME and check to see if pam-panel is running. It is. Every time I do anything that requires root access, it starts a new instance of it. Even if I go in and turn it off. I need to know how to fix this permanently so that I only get one keyset instead of many. --- 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?
[Cooker] [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 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?
[Cooker] [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:10 --- On Tue, 2003-03-18 at 19:55, cybercfo wrote: Cyber, I've run xnest with version 8mdk and it worked there for the same reason... Xft is not on by default. hmmm. sounds like a fallback of some kind is needed but not sure what. James --- 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?
[Cooker] [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:30 --- I wonder if just making the QT_XFT environment variable false will solve the problem also. I should reinstall libqt3-3.1.1-13mdk and try export QT_XFT=no and see what happens. --- 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?
[Cooker] [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?
[Cooker] [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-17 07:10 --- Should this bug be reported to KDE? I don't see it in their bugzilla. --- 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?
[Cooker] [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-16 03:30 --- This still is a problem and what would seem like a dealbreaker. Not only will KDE apps not run in vncserver, but kde apps won'r run under a different window manager. It's going to be a real problem for me to not be able to run Konq and kmail in my fluxbox session through vnc. Does this have a workaround? Is it an XFree or a KDE bug? What can I do to help debug the source of the problem? This is a very big bug. --- 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?
[Cooker] [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-16 04:50 --- I agree that this is serious. It should be fixed before the 9.1 release. -Bob _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus --- 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?
[Cooker] [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-14 04:00 --- Still valid. Please don't tell me 9.1 is going to ship with KDE that cannot start in Xnest. On Thu, 2003-03-13 at 08:20, qa wrote: --- 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?
[Cooker] [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-14 04:20 --- Whenever I access something (such a control panel), and it asks for the root password, the keys no longer appear on the task bar. I checked in sessions and pam is not running. How do I get it to run again? --- 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?
[Cooker] [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-14 04:30 --- is this just using vncserver for a new X session or using rfbdrake to share out the :0 display? I was able to get tightvnc to work fine with Gnome and KDE just today using cooker from last night with no problems. Just curious :) Scott --- 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?
[Cooker] [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-14 06:40 --- The problem had been only using vncserver for a new X session. rfbdrake could be used to share out the :0 display. -Bob _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail --- 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?
[Cooker] [Bug 3081] [galaxy-kde] Galaxy causing problems with KDE and GNOME running in tightvnc-server
http://qa.mandrakesoft.com/show_bug.cgi?id=3081 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-03-11 14:42 --- *** Bug 3129 has been marked as a duplicate of this bug. *** --- 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?
[Cooker] [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-10 22:37 --- Do you use the nv driver? because I've noticed that it does exactly that same thing in mdkkdm. Take a look at http://qa.mandrakesoft.com/show_bug.cgi?id=2601 --- 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?
[Cooker] [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-10 22:50 --- --- Additional Comments From [EMAIL PROTECTED] 2003-03-10 22:37 I am using the Trident driver for an embedded CyberBlade --- 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?
[Cooker] [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-11 03:50 --- Fluxbox doesn't work with vncserver here. Fluxbox runs normally on the local 9.1rc2 computer, but a remote tightvnc viewer shows the same unusable desktop graphic displayed when using KDE or GNOME, rather than the Fluxbox desktop image. -Bob _ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail --- 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?
[Cooker] [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-11 04:10 --- If you are seeing the standard Mandrake wallpaper, you are not actually using fluxbox. If you were running fluxbox, you'd see this in your vncviewer: http://www.gkmweb.com/images/fluxbck.jpg Make sure your ~/.desktop file is set to fluxbox --- 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?
[Cooker] [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-11 05:00 --- My ~/desktop file is set to fluxbox. I see the fluxbox.jpg image on the local Mandrake 9.1rc2 computer, but I see the standard Mandrake wallpaper on a remote tightvnc viewer running under Windows XP. -Bob _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail --- 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?
[Cooker] [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-11 05:10 --- vncserver on linux runs on a seperate xserver, so it does not work like in windows where you can see the same desktop remotely as you do locally. Your local display is :0 and your vnc display should be :1 What user did you start vncserver as? possibly root? Check /root/.desktop file or /etc/sysconfig/desktop. If you are seeing the default Mandrake wallpaper, you are not running fluxbox in vnc. If you don't see any functional desktop at all, most likely you are running KDE in your vncserver and are experiencing the same bug as the rest of us. --- 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?
[Cooker] [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-11 05:40 --- My local display is :0 and my vnc display is :1. vncserver was started under my personal user account, not under the root account. It appears you are correct that my vnc display :1 is not running fluxbox. What determines which GUI vncserver uses? -Bob _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail --- 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?
[Cooker] [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-11 06:00 --- The settings in ~/.desktop or /etc/sysconfig/desktop --- 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?
[Cooker] [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-11 06:10 --- On Mon, 2003-03-10 at 20:40, bb_plus wrote: in the MDK modified version it reads your .desktop file in the user who started the session. In th stock tight vnc it's in the .vnc/xstartup file. --- 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?
[Cooker] [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-10 03:57 --- GNOME seems to be okay now. Trying to start any KDE app from the GNOME terminal is a bust. Grey window flashes by. Perhaps not a Galaxy error now, but others have reported problems with KDE under vnc and xnest. [EMAIL PROTECTED] greg]$ konqueror Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. kbuildsycoca running... Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. Xlib: extension RENDER missing on display :1.0. [EMAIL PROTECTED] greg]$ Mutex destroy failure: Device or resource busy [EMAIL PROTECTED] greg]$ kmail kbuildsycoca running... Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. Id '1' was already in done-list! Id '4' was already in done-list! Id '5' was already in done-list! Id '6' was already in done-list! Id '7' was already in done-list! Id '8' was already in done-list! Id '9' was already in done-list! Id '3.1-update-identities' was already in done-list! Id '3.1-use-identity-uoids' was already in done-list! Id '3.1-new-mail-notification' was already in done-list! Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. Xlib: extension RENDER missing on display :1.0. *** KMail got signal 11 (Crashing) DCOP aborting (delayed) call from 'anonymous-5977' to 'kmail' ERROR: KUniqueApplication: DCOP communication error! [EMAIL PROTECTED] greg]$ mcop warning: user defined signal handler found for SIG_PIPE, overriding Mutex destroy failure: Device or resource busy [EMAIL PROTECTED] greg]$ knode kbuildsycoca running... Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. Xlib: extension GLX missing on display :1.0. Xlib: extension RENDER missing on display :1.0. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. DCOP aborting (delayed) call from 'anonymous-6033' to 'knode' ERROR: KUniqueApplication: DCOP communication error! [EMAIL PROTECTED] greg]$ Mutex destroy failure: Device or resource busy --- 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: UNCONFIRMED 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?
[Cooker] [Bug 3081] [galaxy-kde] Galaxy causing problems with KDE and GNOME running in tightvnc-server
http://qa.mandrakesoft.com/show_bug.cgi?id=3081 [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 --- Additional Comments From [EMAIL PROTECTED] 2003-03-10 04:00 --- *** This bug has been confirmed by popular vote. *** --- 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?
[Cooker] [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-10 04:48 --- After starting Xnest on :1, xdpyinfo -display :1 -ext RENDER tells me: RENDER extension not supported by server GLX is there though. XFree86 problem? I tried to set a default flat theme in KDE, but I still could not start it. --- 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?
[Cooker] [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-10 05:10 --- If it were an Xserver issue, why would only KDE be affected? Unless KDE is using a function of the server that noone else is. It doesn't seem to be the theme after all, but it does not just affect vnc. I recall it did work a few weeks ago. --- 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?
