Bug 2479 - the blankness of the frysk GUI on PPC64
Summary: the blankness of the frysk GUI on PPC64
Status: RESOLVED INVALID
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P3 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on:
Blocks: 2188
  Show dependency treegraph
 
Reported: 2006-03-23 15:38 UTC by Wu Zhou
Modified: 2006-10-19 19:01 UTC (History)
2 users (show)

See Also:
Host: powerpc-redhat-linux-gnu
Target:
Build: powerpc64-unknown-linux-gnu & powerpc-redhat-linux-gnu
Last reconfirmed:


Attachments
I attach the final screeshot here for your reference. (88.57 KB, image/jpeg)
2006-03-23 15:42 UTC, Wu Zhou
Details
Screenshot for GNOME blankness (138.43 KB, image/png)
2006-07-05 08:19 UTC, Yao Qi
Details
no blankness on RHEL4 U3 for PPC64 (49.78 KB, image/jpeg)
2006-07-06 03:36 UTC, Wu Zhou
Details
screenshot when system theme is set to high-contrast-inverse: white-on-black text and icons (382.57 KB, image/png)
2006-07-12 01:13 UTC, Wu Zhou
Details
the screenshot of pressing menu (389.11 KB, image/png)
2006-07-26 08:11 UTC, Wu Zhou
Details
the source file of menu.c (1.70 KB, text/plain)
2006-07-26 08:15 UTC, Wu Zhou
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wu Zhou 2006-03-23 15:38:43 UTC
I can now build frysk on PPC64 / Fedora 5, both in 32-bits and 64-bits mode. 
(In 32-bits mode, I need to apply a workaround for a GCJ ICE error on
frysk-imports/tests/cniinner).

After the building, Frysk can follow fork syscall now.  But it is a little
inconvenient to do so.  Some windows are blank in this process.

At the very beginning of startup, all other windows but the processes view are
blank (including threads window, the right timeline windows and observer
windows). When I choose one process (to say a bash process) to add a fork
observer, the popped out menu is also blank. After moving the mouse to the "add
observer" menu, it return to normal case. After choosing "fork observer", all
these windows (except the right downside window is still blank) return back to
normal again.
Comment 1 Wu Zhou 2006-03-23 15:42:35 UTC
Created attachment 939 [details]
I attach the final screeshot here for your reference.
Comment 2 Phil Muldoon 2006-06-27 16:01:56 UTC
With all the recent changes, I am revisiting this bug. 

There have been a number of 64 bit safe changes made to Java-GNOME over this
last year, so I'm wondering if the change there may have incidentally helped the
sitation

So two quick questions:

What are the windows that are blank in the current CVS HEAD? 

What versions of the Java-GNOME RPMS are you using?

Thanks for your help!
Comment 3 Wu Zhou 2006-06-28 09:19:46 UTC
Hi, Phil

(In reply to comment #2)
> With all the recent changes, I am revisiting this bug. 
> 
> There have been a number of 64 bit safe changes made to Java-GNOME over this
> last year, so I'm wondering if the change there may have incidentally helped the
> sitation

No.  I still see this with a frysk build from the latest cvs tree.

> So two quick questions:
> 
> What are the windows that are blank in the current CVS HEAD? 
> 
> What versions of the Java-GNOME RPMS are you using?
> 

I don't have access to that machine right now.  Will update you asap.

> Thanks for your help!

No problem at all.  :-)
Comment 4 Yao Qi 2006-07-05 08:18:19 UTC
build frysk cvs head, and update packages on FC5, this problem still exists.

Current relative packages version are listed as follows,
[qiyao@plinuxt18 build-frysk-5-23]$ rpm -qa | grep libgtk-java
libgtk-java-2.8.5-0.FC5
libgtk-java-devel-2.8.5-0.FC5
[qiyao@plinuxt18 build-frysk-5-23]$ rpm -qa | grep gtk2
pygtk2-libglade-2.8.4-1.1
pygtk2-2.8.4-1.1
gtk2-engines-2.7.4-3
pygtk2-devel-2.8.4-1.1
gtk2-2.8.19-2
gtk2-2.8.15-1
gtk2-devel-2.8.19-2
gtk2-engines-2.7.4-3
libswt3-gtk2-3.1.2-1jpp_13fc

It seems that it is the GNOME problem, since  "File Browser" and "Panel" is also
blank.
Comment 5 Yao Qi 2006-07-05 08:19:49 UTC
Created attachment 1138 [details]
Screenshot for GNOME blankness

Here is a screenshot for your reference.
Comment 6 Wu Zhou 2006-07-06 03:36:51 UTC
Created attachment 1142 [details]
no blankness on RHEL4 U3 for PPC64
Comment 7 Wu Zhou 2006-07-06 03:40:27 UTC
We are now believing that this is a problem specific to Fedora Core for PPC64. 
Because on RHEL4 update3 for PPC64, there is no blankness in the windows of
"file browser" and "panel" (please refer to the above attachment for detail). We
don't try Frysk though, because we are not sure if frysk can be built
successfully on RHEL4 for PPC64.

Maybe we need to involve some GNOME guys into this bug? I guess it is easy for
them to know where the problem is.

Thanks. 
Comment 8 Wu Zhou 2006-07-12 01:11:19 UTC
When I set the theme to "Hign Contrast Inverse": white-on-black text and icons,
we can get a somewhat better display. No blank in the menu, no blank in the edit
window of gedit.  But the black timeline in eventviewer window is still hidden.

So I guess this might be related to the white or gray color redering in menu,
edit window or other graphic object.

I will attach the screen snapshot below.
Comment 9 Wu Zhou 2006-07-12 01:13:53 UTC
Created attachment 1153 [details]
screenshot when system theme is set to high-contrast-inverse: white-on-black text and icons
Comment 10 Wu Zhou 2006-07-26 08:04:44 UTC
Phil,

I find a testcase in gtk2-devel:
/usr/share/doc/gtk2-devel-2.8.19/examples/menu/menu.c, which can reproduce a
similar problem.  After building it into executable and pressing the root menu,
it will show that the menu entry items are all blank. If you move the mouse to
them, you can see the hidden text. 

But when you set the theme to Smokey-blue, it is ok.

I will attache the screenshot and source code below for your reference.

Thanks.
Comment 11 Wu Zhou 2006-07-26 08:11:56 UTC
Created attachment 1183 [details]
the screenshot of pressing menu
Comment 12 Wu Zhou 2006-07-26 08:15:25 UTC
Created attachment 1184 [details]
the source file of menu.c
Comment 13 Wu Zhou 2006-08-02 16:59:03 UTC
I opened a gtk+ bug for this.  Here is the link:
http://bugzilla.gnome.org/show_bug.cgi?id=349685
Comment 14 Yao Qi 2006-08-31 16:03:06 UTC
As discussed in maillist, it is a bug of VNC, not GNOME or X11.
Close this bug.