Re: no OSK in Plasma Mobile

2018-03-17 Thread Martin Flöser


Am 17. März 2018 02:01:24 MEZ schrieb Heather Ellsworth 
:
>On 03/15/2018 09:10 PM, Bhushan Shah wrote:
>> Hello Heather,
>> 
>> On Thu, Mar 15, 2018 at 06:57:27PM -0600, Heather Ellsworth wrote:
>>> I've been running Plasma Mobile on my iMX6 dev board (precursor to
>the
>>> dev kit for the Librem 5) and I've notices there's no onscreen
>keyboard.
>>> Is it there and I'm just not initializing it? Or what is the story
>with
>>> the OSK in Plasma Mobile?
>> 
>> For OSK, you just need to install qtvirtualkeyboard-plugin package,
>it
>> should give you working on-screen-keyboard for the Qt applications.
>It
>> is however possible that QtVirtualKeyboard is disabled by default if
>you
>> have keyboard attached. In that case you can enable it by clicking on
>> virtualkeyboard icon in top drawer.
>> 
>> You can also "export QT_VIRTUALKEYBOARD_STYLE=Plasma" for better
>theming
>> integration with Plasma Mobile.
>
>After installing qtvirtualkeyboard-plugin and exporting
>QT_VIRTUALKEYBOARD_STYLE, we still do not see a keyboard icon in the
>top
>left of the Plasma Mobile desktop.
>
>Similarly, we do not see the icon after manually enabling the keyboard
>with:
>
>$ qdbus org.kde.KWin /VirtualKeyboard
>org.kde.kwin.VirtualKeyboard.enable
>
>However, after enabling the keyboard with the above qdbus command, we
>see the keyboard pop up when a text field is clicked (like the search
>bar, kwrite, konsole) but then the keyboard immediately goes away.
>
>Also in the lock screen, I see the virtual keyboard icon in the bottom
>left. When I click it, the virtual keyboard appears and does not
>disappear. Then I can type in the password (using Ctrl+Super to guide
>my
>mouse) to log back in.
>
>So the virtual keyboard works, but when in the desktop session the
>keyboard goes away right after it appears. Any troubleshooting advice
>you have would be helpful.
>

It might sound stupid, but just unplug the physical keyboard. Then it should 
work best. If the keyboard still hides, run the apps with WAYLAND_DEBUG=1 then 
we can see what's going on and why it hides. It should only hide if the 
application requests it and that's something we can see in the debug output.


D11413: Fix build with Qt 5.11 (missing headers)

2018-03-17 Thread Andreas Sturmlechner
asturmlechner created this revision.
asturmlechner added a reviewer: ivan.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.
asturmlechner requested review of this revision.

REPOSITORY
  R845 Plasma Vault

BRANCH
  master

REVISION DETAIL
  https://phabricator.kde.org/D11413

AFFECTED FILES
  kded/ui/mountdialog.cpp
  kded/ui/vaultconfigurationwizard.cpp

To: asturmlechner, ivan
Cc: plasma-devel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, 
sebas, apol, mart


D10251: [RFC] Use mipmap filtering in window thumbnails

2018-03-17 Thread Julian Wolff
progwolff added a comment.


  Could you please rebase on current master?

REPOSITORY
  R242 Plasma Framework (Library)

REVISION DETAIL
  https://phabricator.kde.org/D10251

To: fredrik, #plasma, #vdg
Cc: progwolff, broulik, ngraham, hein, plasma-devel, #frameworks, michaelh, 
ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart


D10251: [RFC] Use mipmap filtering in window thumbnails

2018-03-17 Thread Fredrik Höglund
fredrik added a comment.


  In D10251#227092 , @broulik wrote:
  
  > What's the state of this? Bug 391915 just cropped up
  
  
  There are still some issues with the cubic filter, and I've been distracted 
by other things lately.
  I think we should consider landing the current version in the meantime, 
because like @ngraham said, it is a big visual win even in its current state.
  
  It would also be nice to get some testing before the release.

REPOSITORY
  R242 Plasma Framework (Library)

REVISION DETAIL
  https://phabricator.kde.org/D10251

To: fredrik, #plasma, #vdg
Cc: broulik, ngraham, hein, plasma-devel, #frameworks, michaelh, ZrenBot, 
lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart


Re: no OSK in Plasma Mobile

2018-03-17 Thread Heather Ellsworth
On 03/15/2018 09:10 PM, Bhushan Shah wrote:
> Hello Heather,
> 
> On Thu, Mar 15, 2018 at 06:57:27PM -0600, Heather Ellsworth wrote:
>> I've been running Plasma Mobile on my iMX6 dev board (precursor to the
>> dev kit for the Librem 5) and I've notices there's no onscreen keyboard.
>> Is it there and I'm just not initializing it? Or what is the story with
>> the OSK in Plasma Mobile?
> 
> For OSK, you just need to install qtvirtualkeyboard-plugin package, it
> should give you working on-screen-keyboard for the Qt applications. It
> is however possible that QtVirtualKeyboard is disabled by default if you
> have keyboard attached. In that case you can enable it by clicking on
> virtualkeyboard icon in top drawer.
> 
> You can also "export QT_VIRTUALKEYBOARD_STYLE=Plasma" for better theming
> integration with Plasma Mobile.

After installing qtvirtualkeyboard-plugin and exporting
QT_VIRTUALKEYBOARD_STYLE, we still do not see a keyboard icon in the top
left of the Plasma Mobile desktop.

Similarly, we do not see the icon after manually enabling the keyboard with:

$ qdbus org.kde.KWin /VirtualKeyboard org.kde.kwin.VirtualKeyboard.enable

However, after enabling the keyboard with the above qdbus command, we
see the keyboard pop up when a text field is clicked (like the search
bar, kwrite, konsole) but then the keyboard immediately goes away.

Also in the lock screen, I see the virtual keyboard icon in the bottom
left. When I click it, the virtual keyboard appears and does not
disappear. Then I can type in the password (using Ctrl+Super to guide my
mouse) to log back in.

So the virtual keyboard works, but when in the desktop session the
keyboard goes away right after it appears. Any troubleshooting advice
you have would be helpful.

Cheers,
Heather



signature.asc
Description: OpenPGP digital signature


D11410: [RFC] Add option to make applet fixed width

2018-03-17 Thread Radek Hušek
Pitel added a comment.


  Also do we want this or two options instead:
  
  - no expanding: `maximumWidth = preferredWidth`, and
  - no shrinking: `minimumWidth = preferredWidth`?
  
  Because when attempting to use `fillWidth = false` with full version of task 
manager it will probably overflow the panel.

REPOSITORY
  R119 Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D11410

To: Pitel
Cc: mart, hein, plasma-devel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, 
abetts, sebas, apol


[Breeze] [Bug 369676] White lockscreen text's readability depends on background

2018-03-17 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=369676

--- Comment #24 from Martin Flöser  ---
I really like the idea presented by Marco to use a slideshow and then
transition to our "existing" lock screen. I see this as a clear evolution over
the current state without losing why we did the current existing lock screen in
the first place.

What I would like to be considered is the impact on the environment when doing
a slideshow. If a system is locked, it's most likely because nobody is in front
of the system. That means we show an animation nobody sees, which of course has
a negative impact on the climate. We shouldn't downplay this factor as this
change will hopefully affect millions of systems.

But I think it's possible to get a compromise here:
 * stop the animation as soon as the screen goes into power saving (for this we
might need a hook from powerdevil) and restart on user interaction
 * increase the time between every transition (e.g. fibonacci style, so the
longer nobody interacting with the system, the longer it takes for an animation
to be shown).

For those wondering why an animation is a big deal: in the locked case we have
KWin (Wayland compositor) pretty much sleeping, the system can go into the
lowest power mode. But animations mean that the compositor is woken up and the
system needs to go into a higher power state. The transition between wallpapers
is animated so our system is at least woken up 60 times per second for the
duration of the transition.

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

D11220: option to force FolderView icon-only presentation

2018-03-17 Thread Michail Vourlakos
mvourlakos added a comment.


  
  
  In D11220#223836 , @hein wrote:
  
  > Hmm I don't like the approach about putting this into individual applets - 
I think the containment should force constraints on the applets instead, and 
the applets need to follow the constraints. That's more Plasma-idiomatic to me. 
Marco?
  
  
  what containment constraint can block an applet to go to FullRepresentation?
  how do you imagine this to work?

REPOSITORY
  R119 Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D11220

To: mvourlakos, #plasma, mart
Cc: sebas, broulik, hein, plasma-devel, ZrenBot, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, apol, mart


D10944: [taskmanager applet] Do not fill width

2018-03-17 Thread Radek Hušek
Pitel abandoned this revision.
Pitel added a comment.


  Replaced by D11410 .

REPOSITORY
  R119 Plasma Desktop

REVISION DETAIL
  https://phabricator.kde.org/D10944

To: Pitel, ngraham, mart
Cc: hein, mart, ngraham, plasma-devel, #plasma, ZrenBot, lesliezhai, 
ali-mohamed, jensreuterberg, abetts, sebas, apol


D11410: [RFC] Add option to make applet fixed width

2018-03-17 Thread Radek Hušek
Pitel created this revision.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.
Pitel requested review of this revision.

REVISION SUMMARY
  @hein refused D10944  with wish to move 
the config option to contaiment level.
  This patch does it: It adds a `IntList` config option `fixedSizeOverride`
  to panel containment, checkbox in config overlay to modify it, and
  sets `fillWidth` and `fillHeight` of an applet to `false` if it is
  in `fixedSizeOverride` array.
  
  Note that the checkbox introduced by this patch still needs some polishing.

REPOSITORY
  R119 Plasma Desktop

BRANCH
  fixedSizeOverride

REVISION DETAIL
  https://phabricator.kde.org/D11410

AFFECTED FILES
  containments/panel/contents/config/main.xml
  containments/panel/contents/ui/ConfigOverlay.qml
  containments/panel/contents/ui/main.qml

To: Pitel
Cc: mart, hein, plasma-devel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, 
abetts, sebas, apol


D11402: Use KDEInstallDir variables instead of custom calculated install paths

2018-03-17 Thread Friedrich W . H . Kossebau
This revision was automatically updated to reflect the committed changes.
Closed by commit R856:60bcbd38be36: Use KDEInstallDir variables instead of 
custom calculated install paths (authored by kossebau).

REPOSITORY
  R856 Plasma Browser Integration

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D11402?vs=29718=29737

REVISION DETAIL
  https://phabricator.kde.org/D11402

AFFECTED FILES
  CMakeLists.txt
  chrome_install_locally_policy.in
  org.kde.plasma.chrome_integration.json.in
  org.kde.plasma.firefox_integration.json.in

To: kossebau, davidedmundson, broulik, apol
Cc: plasma-devel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, 
sebas, apol, mart


KDE CI: Plasma plasma-framework kf5-qt5 FreeBSDQt5.9 - Build # 77 - Still unstable!

2018-03-17 Thread CI System
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Plasma%20plasma-framework%20kf5-qt5%20FreeBSDQt5.9/77/
 Project:
Plasma plasma-framework kf5-qt5 FreeBSDQt5.9
 Date of build:
Sat, 17 Mar 2018 07:45:09 +
 Build duration:
3 min 3 sec and counting
   JUnit Tests
  Name: (root) Failed: 1 test(s), Passed: 13 test(s), Skipped: 0 test(s), Total: 14 test(s)Failed: TestSuite.plasma-packagestructuretest