|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 sw_single gtk: search window writes in white on white | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Dominique Leuenberger <dimstar> |
| Component: | YaST2 | Assignee: | Forgotten User h13THG8RK1 <forgotten_h13THG8RK1> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_h13THG8RK1, schaefer.frank |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Dominique Leuenberger
2009-08-06 11:30:24 UTC
looks like a theme / color issue. I'm not certain it's a theme issue. Especially very often you can't even get into the search field at all. Try to reproduce: - Start yast2 sw_single (gtk mode) - The filter field containts the 'searching glass icon' - click in the field. The icon disappears. - Start typing. Nothing 'writes' but the keyboard input seems to have it's effect. - Select any package from the list (any) - click again the filter field in the upper right area. - Type anything. --> The text input does NOT go into the filter field on top, but it launches the dynamic search. Having of course a different result. i'm tempted to raise this to a higher status. We should not want to have a package manager again with 'broken' functionality. I can confirm this. Looks more like a package-dependeny-problem. I tried with a KDE-Installation of 11.2 M6 + yast2-gtk-packages installed. In this constellation also no icons are shown in the search-text-edit. Then I installed the yast2-control-center-gnome-package, which also triggers the installation of several GTK/GNOME-packages and at least the icon is shown then (the edit still doesn't work). Frank, what style do you use? Dominique, your style is not bundled by opensuse, is it? Can you tell me where it is from? Or could you see if it fails in one of the standard ones? Frank, please tell me what system you're using as well. Ricardo: Sonar... I thought it was the new default :-) As I said, I tried with a standard KDE-Installation of 11.2 M6 + yast2-gtk-packages - no GNOME. KDE-Style is "Air" (default) and KDE-Gtk-Style is "Cleanlooks", but that shouldn't matter ? I seem no longer able to reproduce this with the yast packages updated this morning. Frank, how is the situation for you? I've fixed a related bug which could be the root of this one as well. (with regard to comment 8, I fixed this one just now so...) Would be great if you guys could give a try to svn -- you guys just have to run the following commands, and possibly install any dependencies it complains about: svn checkout http://svn.opensuse.org/svn/yast/trunk/gtk/ make -f Makefile.cvs make && sudo make install Thanks! Thank you Ricardo, I will test it with M7 or M8 when I'm back at home at the end of this month. Package request for Factory accepted. Interesting to note that GTK 2.16, which will be bundled with opensuse 11.2, makes our find entry implementation obsolete. I'd rather slow down this trend of swift changes, so do tell me whether the current yast2-gtk version works for you. If not, I will go ahead and replace our find entry. Btw, please do a query on yast2-gtk version (rpm -q yast2-gtk) to make sure you really do have the 2.19 version. We had some issues pushing it up there... Frank & Dominique: yast2-gtk-2.19.15-1.1.i586.rpm (and respective 64-bit RPM) is now available on Factory. Give them a byte while they're hot! And tell me whether the entry box works for you. Ricardo, I didn't forget you ! M8 is already on the the way to my harddisk and I hope I will find some time this week to set up another test-system. Frank, great, but please notice M8 doesn't yet ship yast2-gtk-2.19. You want to add Factory as a repo and upgrade it, or manually download the yast2-gtk-2.19.15 RPM: http://download.opensuse.org/factory/repo/oss/suse/i586/ I can't reproduce it anymore with M8 (package-version 2.18.13). 2.19.15 works fine, too. Thanks for your work Ricardo ! Alrighty. Let's re-open the report if anyone re-experiences the issue. |