[plasmashell] [Bug 362531] Plasma panels are not transparent after login

2016-07-27 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #28 from Niels Ole Salscheider --- > * EffectWatcher constructor for "_KDE_NET_WM_BACKGROUND_CONTRAST_REGION" > atom is often !isNull() Does "often" mean that you observed it to be Null sometimes? Because

[plasma-pa] [Bug 366032] plasma-pa should allow to select the sink for volume control

2016-07-24 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366032 --- Comment #1 from Niels Ole Salscheider --- Or maybe it would be enough to recursively query the master sink starting from the default sink and then adjust the volume of the sink you end up with eventually. That would

[plasma-pa] [Bug 366032] New: plasma-pa should allow to select the sink for volume control

2016-07-24 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366032 Bug ID: 366032 Summary: plasma-pa should allow to select the sink for volume control Product: plasma-pa Version: unspecified Platform: Other OS: Linux

[Spectacle] [Bug 362257] spectacle.khotkeys: The specified file is empty or not a configuration file

2016-05-05 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362257 Niels Ole Salscheider changed: What|Removed |Added CC|

[plasmashell] [Bug 362531] Plasma panels are not transparent after login

2016-05-05 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #3 from Niels Ole Salscheider --- Created attachment 98784 --> https://bugs.kde.org/attachment.cgi?id=98784=edit Plasma after being restarted (with transparency) -- You are receiving this mail because:

[plasmashell] [Bug 362531] Plasma panels are not transparent after login

2016-05-05 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #2 from Niels Ole Salscheider --- Created attachment 98783 --> https://bugs.kde.org/attachment.cgi?id=98783=edit Plasma right after login (no transparency) -- You are receiving this mail because: You are

[plasmashell] [Bug 362531] Plasma panels are not transparent after login

2016-05-01 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362531 Niels Ole Salscheider changed: What|Removed |Added CC|

[plasmashell] [Bug 362531] New: Plasma panels are not transparent after login

2016-05-01 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362531 Bug ID: 362531 Summary: Plasma panels are not transparent after login Product: plasmashell Version: 5.6.3 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED

[frameworks-kinit] [Bug 362142] New: The session does not finish cleanly / startkde exits too early?

2016-04-23 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362142 Bug ID: 362142 Summary: The session does not finish cleanly / startkde exits too early? Product: frameworks-kinit Version: 5.20.0 Platform: Exherbo Packages OS:

[Breeze] [Bug 360967] The breeze-plymouth theme contains subdirectories

2016-03-30 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360967 --- Comment #2 from Niels Ole Salscheider --- plymouth-populate-initrd is part of plymouth, though, and is only used by dracut. This means it is either a plymouth bug or that it was an intentional decision by the

[kcalc] [Bug 360105] Doesn't start with Qt 5.6

2016-03-12 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360105 --- Comment #7 from Niels Ole Salscheider --- Please ignore what I said. The real problem is that the window is not visible because of setFixedSize(minimumSize()); where minimumSize() returns (0, 0). -- You are

[kcalc] [Bug 360105] Doesn't start with Qt 5.6

2016-03-12 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360105 Niels Ole Salscheider changed: What|Removed |Added CC|

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-02-01 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #27 from Niels Ole Salscheider --- Yes, this would be sufficient. For mesa at least, since it queries the environment variable in eglGetDisplay. We already use EGL_PLATFORM for the hwcomposer backend and the

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-30 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #22 from Niels Ole Salscheider --- Or even better, use eglGetPlatformDisplayEXT to get a display for the right platform (if available). -- You are receiving this mail because: You are watching all bug

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-30 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #20 from Niels Ole Salscheider --- No, the current code tries all EGL drivers (which is only drm), but it only tries one platform for each driver. This platform is either what is set by the EGL_PLATFORM env

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-30 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #21 from Niels Ole Salscheider --- Maybe KWin should set EGL_PLATFORM to x11 or wayland, depending on where it runs. This is at least what other compositors do. -- You are receiving this mail because: You

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-30 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #24 from Niels Ole Salscheider --- (In reply to Thomas Lübking from comment #23) > The relevant code (initEGL()) is in platform agnostic in libkwineffects - > we'd either have to transfer it into the

[kwin] [Bug 358750] New: KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 Bug ID: 358750 Summary: KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755 Product: kwin Version: 5.5.4 Platform: Exherbo Packages

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #11 from Niels Ole Salscheider --- Thank you for your patience. I have sent a patch to mesa-dev that fixes the crash. I still see "radeon: Failed to get PCI ID, error number -13" (both with KWin and eglinfo)

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #5 from Niels Ole Salscheider --- (In reply to Thomas Lübking from comment #3) > From the mesa troubleshooting guide: > > If see this error message: radeon: Failed to get PCI ID, error number -13, > make

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #4 from Niels Ole Salscheider --- Created attachment 96907 --> https://bugs.kde.org/attachment.cgi?id=96907=edit Backtrace -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #10 from Niels Ole Salscheider --- It segfaults in the same function. So it really seems to be a driver issue. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #13 from Niels Ole Salscheider --- It seems so, this is the output I get: radeon: Failed to get PCI ID, error number -13 EGL API version: 1.4 EGL vendor string: Mesa Project EGL version string: 1.4 (DRI2)

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 Niels Ole Salscheider changed: What|Removed |Added CC|

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 Niels Ole Salscheider changed: What|Removed |Added Attachment #96907|0 |1

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #8 from Niels Ole Salscheider --- I have only tried with mesa master. I can also compile the latest stable version but this will take a bit since I will have to downgrade llvm, clang and maybe some other

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #15 from Niels Ole Salscheider --- The output seems to be missing? I wonder if the problem has something to do with rendernodes. The platform code opens /dev/dri/card0 when no display is supplied but the

[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755

2016-01-29 Thread Niels Ole Salscheider via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #18 from Niels Ole Salscheider --- > The code in question looks like it unconditionally tries /dev/dri/renderD0, > that one's likely occupied and in return it resorts to card0 > > What *should* (probably,