[Breeze] [Bug 370484] Lockscreen Breeze theme doesn't have keyboard layout indicator

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Gräßlin  ---
The layout switcher is positioned in the bottom left corner. It should just say
the name of the locale (e.g. "de"), when clicking it a dropdown list should be
shown.

*** This bug has been marked as a duplicate of bug 370220 ***

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

[ksysguard] [Bug 361281] migrate away from qtwebkit (gui)

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
KSysguard is a workspace component. As long as
https://bugreports.qt.io/browse/QTBUG-55384 is not fixed we should not port any
workspace component to WebEngine.

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

[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kwin
   ||/b9c98bd2b977bd68d79240
   ||ac4d60fcadc96b

--- Comment #9 from Martin Gräßlin  ---
Git commit b9c98bd2b977bd68d79240ac4d60fcadc96b by Martin Gräßlin.
Committed on 15/08/2016 at 15:39.
Pushed by graesslin into branch 'master'.

Trigger global shortcuts also on key-repeat

Summary:
Restores feature parity with X11. Global shortcuts need to trigger
also for repeat events. An example is the volume key or screen
brightness.

For other shortcuts like showing yakuake it does not make sense to
trigger on repeat. Thus a long term solution is to add a flag to
global shortcuts whether the key should trigger on repeat.

Reviewers: #kwin, #plasma_on_wayland

Subscribers: plasma-devel, kwin

Tags: #plasma_on_wayland, #kwin

Differential Revision: https://phabricator.kde.org/D2413

M  +1-1input.cpp

http://commits.kde.org/kwin/b9c98bd2b977bd68d79240ac4d60fcadc96b

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

[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
URL||https://phabricator.kde.org
   ||/D2413

--- Comment #8 from Martin Gräßlin  ---
Removing the key-repeat check in https://phabricator.kde.org/D2413

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

[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #6 from Martin Gräßlin  ---
> So KWin/Wayland requires non-Qt applications to link with KGlobalAccel to 
> register shortcuts ?

This is getting off-topic.

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

[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #4 from Martin Gräßlin  ---
KGlobalAccel actions are only triggered on press events. There is no additional
call when they are released.

I played a little bit with my system and there the brightness key sends
press/release combos constantly when being hold.

> I think not repeating global shortcuts is the correct behaviour. Still it 
> would make sense for PowerDevil to be notified when the shortcut is released.

I'm not sure how we can combine those two. I either make it ignore repeat
events or make it always trigger. To support this we would have to extend
kglobalaccel to add a flag "allow repeat".

> Also, where is the KGlobalAccel D-Bus interface documentation ?

Nowhere, it's an internal detail of the KGlobalAccel framework and not a public
and stable dbus interface.

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

[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
Just checked, kwin explicitly ignores key repeat events to trigger global
shortcuts

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

[Powerdevil] [Bug 366608] Brightness keyboard action does not repeat while key is pressed under Wayland

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||mgraess...@kde.org

--- Comment #1 from Martin Gräßlin  ---
oh, on X11 the shortcuts are triggered again?

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

[Powerdevil] [Bug 353032] Add ability to set screen brightness for non-laptop displays so I can adjust to the room's lighting

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|KScreen |Powerdevil
   Assignee|dvra...@kde.org |plasma-devel@kde.org
  Component|Plasma Applet   |general

--- Comment #1 from Martin Gräßlin  ---
Reassign to powerdevil which is responsible for screen brightness

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 354250] "Switch User" sometimes sends computer to Standby

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #27 from Martin Gräßlin  ---
both threads are waiting (X can do multi-threading, that's like wow I'm
impressed). Though the one is a graphics thread and is somewhere in radeon.
That could be an indication for being blocked and waiting for something to
happen when resumed. But overall I'm not familiar enough with the code to make
a guess.

So I just assume that non-root X is not doing anything when the session is
switched away. AFAIU their architecture is very similar to what kwin_wayland
does for that situation.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 354250] "Switch User" sometimes sends computer to Standby

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #24 from Martin Gräßlin  ---
From comment @18 it looks like X freezes while being on the inactive session.
As Fedora is mentioned I assume it's an X not run as root? If X freezes all xcb
requests are going to block. From client side there is nothing which can be
done about that. There is no timeout and no way to cancel.

I would be interested in seeing a backtrace of X at that time as I assume it's
also frozen.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Plasma Workspace Wallpapers] [Bug 364724] Workspace and wallpapers misaligned on multiple monitors in portrait rotation

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #1 from Martin Gräßlin  ---
> 1. Configure multiple monitors from Display Manager or NVidia Application

How does that look like when you use Plasma's configuration tool? Does your
setup support XRandR? If yes, can you add the output of XRandR to this bug
report.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 355687] Powerdevil does not act (e.g. suspend, dim) when switching to battery mode

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #14 from Martin Gräßlin  ---
*** Bug 355732 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 364592] Controller input does not prevent screen from turning off

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Martin Gräßlin  ---
joystick/gamepad input bypasses the normal way of how input is handled. Thus
the relevant framework (KIdleTime) just doesn't see the input.

*** This bug has been marked as a duplicate of bug 328987 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 360766] Powerdevil should wakeup external display after suspend

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||mgraess...@kde.org

--- Comment #2 from Martin Gräßlin  ---
I think that's outside the scope of powerdevil. Waking up the connected outputs
is something the windowing system (e.g. X11, KWin_Wayland) needs to do.
Powerdevil has no control over dpms, that's on X11 completely handled inside
X11, it doesn't know whether the screen is on, whether dpms is in and has no
way to end it.

If the problem is also present on KWin_Wayland the bug can be reassigned to
KWin, for X11 it's outside the scope of our software stack.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 358957] laptop won't hybrid-suspend when KDE is running

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
(In reply to Kai Uwe Broulik from comment #1)
> I think it's just that we don't have an entry for that in Kickoff and the
> like. Probably needs to be added in various places.

or maybe use HybridSuspend instead of Suspend if available. I am not sure
whether it makes sense to expose such a fine grained difference to the user.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[kscreenlocker] [Bug 358859] Screen not always locked when lid closed

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|Powerdevil  |kscreenlocker
Version|5.5.4   |unspecified
 CC||bhus...@gmail.com,
   ||mgraess...@kde.org
   Assignee|plasma-devel@kde.org|plasma-b...@kde.org
  Component|general |general

--- Comment #2 from Martin Gräßlin  ---
Are you using logind?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 358576] Default and Breeze color scheme have different window decoration colors

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #2 from Martin Gräßlin  ---
@Kai: should be defined in kdeglobals on section WM.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 358576] New: Default and Breeze color scheme have different window decoration colors

[Martin Gräßlin via KDE Bugzilla]

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

Bug ID: 358576
   Summary: Default and Breeze color scheme have different window
decoration colors
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-devel@kde.org
  Reporter: mgraess...@kde.org

The "default" color scheme has a blue window decoration color, while breeze has
a dark color. Given that the "default" should be breeze this needs to be the
same color

Reproducible: Always

Steps to Reproduce:
1. Open Systemsettings
2. Open Color
3. Look at preview list

Actual Results:  
Top right color preview of Default and Breeze are not the same

Expected Results:  
Should be the same

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[kwin] [Bug 356863] Blur when docked/maximized

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #5 from Martin Gräßlin  ---
This is not a kwin issue. KWin is doing exactly what it advertises to do if a
window decided that it wants a shadow.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 355892] missing suspend/hibernate with upower 0.99.3 and Devuan

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #13 from Martin Gräßlin  ---
> When you tag this as resolved downstream, you are just making a statement 
> about who is to blame and how much you care about the issue.

huh? You might be interpreting too much into this. Please step a little bit
away from the "systemd conspiracy" if I might call it that way. We absolutely
don't care what init systems our users use - not our business. If you are not
happy with the possibilities for power management provided by Plasma I can only
recommend to do what those who wanted to use ConsoleKit2 did: sit down and
write the code. This is free software: scratch your own itch. Don't expect that
others scratch your itch.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 355892] missing suspend/hibernate with upower 0.99.3 and Devuan

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #17 from Martin Gräßlin  ---
thanks for submitting to slashdot. Next time we can just set to invalid to make
sure there is no stupid discussion which then gets mirrored to slashdot.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #5 from Martin Gräßlin  ---
Sorry, but I have to agree with sebas here. If I consider this for kwin, I must
say it's horrible from the lookup perspective as we need to be fast at startup.
With the proposal we cannot easily check whether a theme is there and where to
get a fallback. It would require stating multiple directories. That's causing
significant slow down during startup which we currently don't need. It's not
much each single time, but it sums up. Here a few milliseconds, there a few and
soon you have a second of waiting for nothing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #7 from Martin Gräßlin  ---
> I'm not missing this. Binary plugins are usually part of engines, and that
> is completely different story. To clarify, Qt styles are analogous to GTK
> engines and are NOT themes. Themes are data.

You reported this here in the breeze component. Breeze consists of multiple
binary plugins - way more than no binary plugins aspects. So this seems a
rather relevant thing to point out in this feature request that it's irrelevant
to the component you propose it to.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #9 from Martin Gräßlin  ---
>  I wonder how the lookup is done in Metacity, Compiz, Openbox and XFWM which 
> are using the themes convention.

honestly: I doubt they do. At least Metacity and Compiz have been dead for
years. Openbox and XFWM are compared to KWin erm stagnating. Maybe we are
comparing apples and oranges here? For them the one look up simple might not
matter, but KWin has more than just one look up for themed elements.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #12 from Martin Gräßlin  ---
Sorry you misunderstood. My point is rather that KWin and those WMs are not
comparable due to size of project. An openbox theme is not comparable to the
theming KWin has in place, because that's areas openbox doesn't even have.
Neither openbox nor xfwm support OpenGL compositing with themeable desktop
effects (yes the close button in Present Windows is themeable, each overlay in
effects is themeable, the +/- button in DesktopGrid is themeable, etc. etc.).
So this is a completely different ball park. Here performance matters, because
each theme element needs to be looked up and it's slowing down the startup.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 355906] Please consider unification for themes' data paths.

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #14 from Martin Gräßlin  ---
The problem with the proposed change is how we look up stuff.

Currently we use an approach of one directory for a "theme element" and all
themes install there. We can do a simple list of it. So we can easily see
whether $theme supports the theme element and we can easily fall back to
$default if it's not present.

With the proposed change we need to go into the directory of the theme, look up
there whether the element is present, if not go to system variant of the theme,
look up there whether the element is present, then start the whole process
again for the default theme. Because in that setup we don't even know whether
the default theme is supported.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 355892] missing suspend/hibernate with upower 0.99.3 and Devuan

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|VERIFIED|RESOLVED

--- Comment #6 from Martin Gräßlin  ---
> Unless KDE is prepared to make a statement that it depends on systemd 

of course not. Powerdevil recently also gained support for ConsoleKit2, see:
http://commits.kde.org/powerdevil/10f2be4f0a2b482008937b1e378e914a637d83be

Which turns it into a distro problem. Your distribution configured the system
in a way that suspend/hibernate is broken. It doesn't come with any of the
supported solutions Plasma provides. Which makes it a distro problem. The
distro integrates various parts of the software stack. This includes it's the
distro's task to ensure that components work together. It failed here by
ripping out systemd and replace it with well nothing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 355892] missing suspend/hibernate with upower 0.99.3 and Devuan

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||mgraess...@kde.org

--- Comment #1 from Martin Gräßlin  ---
This works fine on Debian testing. Please get in contact with your distribution
to figure out why this broke in your Debian fork. You might consider of course
to install systemd.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 355892] missing suspend/hibernate with upower 0.99.3 and Devuan

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #11 from Martin Gräßlin  ---
Setting back to resolved downstream. From our side there is just nothing to do
and to me it's an integration issue (bundling of non-compatible versions) which
means downstream.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 355804] Fresh boot to sddm and a few minutes of inactivity sends computer to Standby

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Martin Gräßlin  ---
If you really think that this is a bug you need to report it to sddm:
https://github.com/sddm/sddm/issues

Personally I think this is expected behavior and not a bug. Anyway marking as
resolved upstream as this belongs to sddm.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Breeze] [Bug 355447] Mouse cursor theme partially fails on first login with new user account

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||mgraess...@kde.org

--- Comment #2 from Martin Gräßlin  ---
Which distribution are you using? The problem here is that the distribution has
not set up the default cursor theme properly causing a fallback to the default
X theme in kwin.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel