A Port of the default KDE Widget Theme (Oxygen), to GTK 2.x
https://projects.kde.org/projects/playground/artwork/oxygen-gtk/
Oxygen-Gtk2 is a port of the default KDE widget theme (Oxygen), to gtk 2.x.
It's primary goal is to ensure visual consistency between gtk-based and qt-based
applications running under KDE. A secondary objective is to also have a
stand-alone nice looking gtk theme that would behave well on other Desktop
Environments.
Unlike other attempts made to port the KDE oxygen theme to gtk, this attempt does
not depend on Qt (via some Qt to Gtk conversion engine), nor does render the
widget appearance via hard coded pixmaps, which otherwise breaks everytime some
setting is changed in KDE.
- Developed at KDE:Extra
- Sources inherited from project openSUSE:Factory
-
3
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Backports:SLE-15-SP4:FactoryCandidates/oxygen-gtk2 && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| baselibs.conf | 0000000037 37 Bytes | |
|
changeset_rebda9cf5273f62ce226612d3080f49f135f3f2d |
0000000896 896 Bytes | |
| oxygen-gtk2-1.2.5.tar.bz2 | 0000191613 187 KB | |
| oxygen-gtk2.changes | 0000008168 7.98 KB | |
| oxygen-gtk2.spec | 0000004609 4.5 KB |
Revision 9 (latest revision is 30)
Stephan Kulow (coolo)
accepted
request 126866
from
Sascha Peilicke (saschpe)
(revision 9)
Crash fix, fixes #bko 302197, also fixes a crash with the same trace in Java JRE when using Oygen GTK with DB Visualizer 7.1.5: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fb26d987620, pid=1116, tid=140404932077312 # # JRE version: 6.0_31-b04 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.6-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [liboxygen-gtk.so+0x11f620] Oxygen::processTabCloseButton(_GtkWidget*, GtkStateType)+0xb3d0 # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # (forwarded request 126850 from renekrell)
Comments 0