Hi everyone,
Is there a way to change the new style for Yast in Opensuse 12.1?
I don’t really like to have it not consistent with Oxygen theme.
Thank you in advance for your help 
Do you have
yast2-theme-openSUSE-Oxygen
installed?
I changed the yast style to Oxygen-like by installing another “branding” packages.
# rpm -qa|grep yast2-qt-branding
yast2-qt-branding-basedonopensuse-12.1-6.1.2.x86_64
# rpm -qa|grep yast2-branding
yast2-branding-basedonopensuse-12.1-6.1.2.x86_64
# rpm -qa|grep yast2-theme
yast2-theme-openSUSE-Oxygen-2.21.18-2.1.1.noarch
yast2-theme-openSUSE-2.21.18-2.1.1.noarch
As far as I remember it required some replacement like “branding-openSUSE” to “branding-basedonopensuse”
Hi,
I have the same problem (namely that Yast turned ugly with 12.1). I do have the Oxygen theme installed. The control center is oxygen themed (and looks normal), but other Yast apps (like software management or lan management) do not pick it up.
Hi,
I have the same problem (namely that Yast turned ugly with 12.1). I do have the Oxygen theme installed. The control center is oxygen themed (and looks normal), but other Yast apps (like software management or lan management) do not pick it up. Installing yast2-branding-bastonopensuse did the trick for me. Can someone say “strange default settings”?
I’ve tryed installing the package you suggested but i got a problem. 
Here is the out… can someone give me a hint? I’ve never received such an output from zypper.
fra@linux-22uv:~> sudo zypper in yast2-branding-basedonopensuse
root's password:
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: yast2-branding-basedonopensuse-12.1-6.1.2.x86_64 conflicts with namespace:otherproviders(yast2-branding) provided by yast2-branding-openSUSE-2.18.0-11.1.1.noarch
Solution 1: deinstallation of yast2-branding-openSUSE-2.18.0-11.1.1.noarch
Solution 2: do not install yast2-branding-basedonopensuse-12.1-6.1.2.x86_64
Choose from above solutions by number or cancel [1/2/c] (c): 1
Resolving dependencies...
Resolving package dependencies...
Problem: yast2-branding-basedonopensuse-12.1-6.1.2.x86_64 requires branding-basedonopensuse, but this requirement cannot be provided
uninstallable providers: branding-basedonopensuse-12.1-6.1.2.i586[repo-oss]
branding-basedonopensuse-12.1-6.1.2.x86_64[repo-oss]
Solution 1: deinstallation of branding-openSUSE-12.1-15.3.9.x86_64
Solution 2: do not install yast2-branding-basedonopensuse-12.1-6.1.2.x86_64
Solution 3: do not install yast2-branding-basedonopensuse-12.1-6.1.2.x86_64
Solution 4: break yast2-branding-basedonopensuse by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c] (c): c
and these are my repos
fra@linux-22uv:~> sudo zypper lr -d
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
--+--------------+--------------------------+---------+---------+----------+--------+--------------------------------------------------------------------------+--------
1 | Tumbleweed | Tumbleweed | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ |
2 | packman | packman | Yes | Yes | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_Tumbleweed |
3 | repo-non-oss | openSUSE-Current-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/ |
4 | repo-oss | openSUSE-Current-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/openSUSE-current/repo/oss/ |
5 | repo-update | openSUSE-Current-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/openSUSE-current/ |
Choose deinstallation of branding-openSUSE (this will cause the installation of branding-basedonopensuse package)
thanks, i was just a little worried of consequences so i preferred to ask to be sure…
all is fine now, thank you!
I made this change this morning and had many ill results.
It basically broke most network related services I have running.
I would have to manually start network, then mysql, apache2, smb, nmb, mythbackend, and on and on…
Firefox continued to work as did skype. That was the strange part.
System related network services were broke.
I reverted back and everything is fine now.
It was odd, but just posting so folks who have system network services running can get a heads up.
No kidding. Poor default choice indeed. I installed 12.1 on a test machine, and I was disappointed at some of the oversights. This one in particular was noticeable: Yast Qt looks cheesy and ugly in the software manager and network manager modules, and it does not honor the user’s theme. On openSUSE 11.4, there was no such problem. Sure, it can be solved by removing a package and replacing it with another, but why? Why was this shipped as the default?
Speaking of poor defaults, don’t even get me started on KPackageKit (now replaced by Apper).
I do completely agree with flansuse.
It’s a really weird and disappointing choice…
I want to add an update to this thread, and I hope this helps. I found out that the offending package is indeed yast2-theme-openSUSE-Oxygen. It is the only package that needs to be removed. (zypper remove yast2-theme-openSUSE-Oxygen)
To illustrate, this is what I have installed (and not installed), and Yast now uses the proper appearance:
Installed:
- yast2-theme-openSUSE
- yast2-branding-openSUSE
- branding-openSUSE
Not installed:
- yast2-theme-openSUSE-Oxygen
- yast2-branding-basedonopensuse
- branding-basedonopensuse
I do not have any -basedonopensuse packages installed, only -openSUSE branding. In other words, the only step that needs to be done (from the beginning) is “zypper remove yast2-theme-openSUSE-Oxygen” and nothing more. No need to change branding.
I do believe the problem is caused by yast2-qt-branding-openSUSE but not yast2-theme-openSUSE-Oxygen.
What’s going on? Now I’m really confused. I think you’re right, because I noticed a few more things:
-
If I only remove yast2-theme-openSUSE-Oxygen, then the package manager looks fine, but the rest of Yast is without icons!
-
If I keep yast2-theme-openSUSE-Oxygen, then the package manager looks ugly, but the rest of Yast looks fine!
-
If I replace yast2-qt-branding-openSUSE with yast2-qt-branding-basedonopensuse and leave yast2-theme-openSUSE-Oxygen installed, then everything looks fine, but I prefer not to mix-and-match branding packages.
Speaking of which, the branding names are ambigious. What’s the difference between “basedonopensuse” and “openSUSE”. Is openSUSE not based on openSUSE?
And once again, why is this shipped as the default for openSUSE 12.1 KDE?
Sorry for my poor English.
I replace yast2-qt-branding-openSUSE with yast2-qt-branding-basedonopensuse. But it’s unuseful.
So I fored remove yast2-qt-branding-openSUSE. Then everything looks fine.
I reinstall yast2-qt-branding-openSUSE, and remove /usr/share/YaST2/theme/openSUSE-Oxygen/wizard witch link to openSUSE/wizard. Everything looks fine too.
The files under wizard define the sytle of YaST2.
Can’t you just login in KDE as root user and change the KDE theme as you would do for a regular user? Then logout and login as normal user and yast should take the root KDE theme. That way you can also match your yast theme if you don’t use oxygen style, but for instance the qtcurve style. At least this works on 11.x series. Haven’t installed 12.1 yet.
On 11/29/2011 08:16 PM, suskewiet wrote:
>
> Can’t you just login in KDE as root user
please -=no=-
you should never log into KDE/Gnome/XFCE or any other *nix-like system’s
graphical user interface desktop environment as root…
doing so 1) opens you up to several different security problems if you
(for example) browse the net, 2) too many, far too easy ways to damage
your system no matter how careful your actions (for
example: well documented cases of unintended change of ownership of
~/.ICEauthority and ~/.Xauthority from user to root sometimes occurs),
3) anyway logging into KDE/etc as root is never required to
do any and all administrative duties, 4) and, not even logging in as
root just to see if it works as root is useful, because the “yes” or
“no” learned is almost always totally useless in finding the
problem giving the symptoms…while, logging into the GUI as root to
learn the yes/no could cause the next adverse symptom encountered.
so, always log in as yourself, and “become root” by using a root powered
application (like YaST, File Manager Superuser Mode) or using “su -”,
sudo, kdesu, or gnomesu in a terminal to launch whatever tool is needed
(like Kwrite to edit a config file)…read more on all that here:
root http://tinyurl.com/593e4c
http://tinyurl.com/ydbwssh
http://tinyurl.com/6bo2cqg
http://tinyurl.com/4nsaqst
http://tinyurl.com/665h5ek
http://tinyurl.com/6ry6yd
additionally: after logging into KDE/Gnome/etc as root, if you
experience problems (for example, with uncommanded file ownership and
permissions changes) and if you can provide us with details of what you
were doing while you were logged in as root, that would help us identify
if there’s a bug that needs to be fixed…thanks for your help…
–
DD http://tinyurl.com/DD-Caveat http://tinyurl.com/DD-Hardware
http://tinyurl.com/DD-Software
openSUSE®, the “German Engineered Automobiles” of operating systems!
It doesn’t work on 12.1.
In fact, we can make our own sytle of YaST2-qt by modify the files under /usr/share/YaST2/theme/*/wizard now.