[Oxygen] [Bug 403978] New: oxygen theme incompatible with qt5 5.12.1-1 libs

Potomac bugzilla_noreply at kde.org
Wed Feb 6 00:37:41 GMT 2019


https://bugs.kde.org/show_bug.cgi?id=403978

            Bug ID: 403978
           Summary: oxygen theme incompatible with qt5 5.12.1-1 libs
           Product: Oxygen
           Version: 5.14.5
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: mister.freeman at laposte.net
  Target Milestone: ---

SUMMARY
I use archlinux,
since a recent update of qt5 packages (to the 5.12.1-1 version) I notice that
kde-plasma is broken if the oxygen theme is used,

the desktop displays but the mouse doesn't move, and the harddisk led blink for
a long time, the entire system seems frozen (but I can open a terminal with
ctrl-alt-f2),

if I downgrade qt5 to the previous version (5.12.0) then the oxygen theme is
usable, no bugs,

and If I use the default theme (breeze) then no problem with the last version
of qt5 libs (5.12.1-1)

so there is an incompatibility between oxygen 5.14.5 and qt5 5.12.1-1

STEPS TO REPRODUCE
1. install kde plasma 5.14.5
2. use the oxygen theme 5.14.5
3. update to the last qt5 lib release version (5.12.1-1)
4. reboot your system
5. you will notice that kde-plasma hangs when desktop is displayed (mouse
frozen)

OBSERVED RESULT
the desktop is frozen, we can not move the mouse, harddisk led blinks a long
time

EXPECTED RESULT
kde plasma should not frozen when oxygen theme is used with the last version of
qt5 (5.12.1-1)

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: archlinux 64 bits, kde plasma 5.14.5
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.1

ADDITIONAL INFORMATION
I use radeon HD4650 pci-e graphic card, with the open source driver (radeon),
openGL2.0 acceleration in plasma settings for the compositer

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list