Jenkins-kde-ci: plasma-workspace master kf5-qt5 » Linux,gcc - Build # 875 - Still unstable!

2017-05-01 Thread no-reply

GENERAL INFO

BUILD UNSTABLE
Build URL: 
https://build.kde.org/job/plasma-workspace%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/875/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Tue, 02 May 2017 06:29:10 +
Build duration: 7 min 48 sec

CHANGE SET
No changes


JUNIT RESULTS

Name: (root) Failed: 2 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 
11 test(s)Failed: TestSuite.appstreamtestFailed: TestSuite.klipper-testHistory

COBERTURA RESULTS

Cobertura Coverage Report
  PACKAGES 15/15 (100%)FILES 55/76 (72%)CLASSES 55/76 (72%)LINE 2304/6016 
(38%)CONDITIONAL 1624/5996 (27%)

By packages
  
drkonqi.parser
FILES 6/10 (60%)CLASSES 6/10 (60%)LINE 303/423 (72%)CONDITIONAL 
478/616 (78%)
drkonqi.tests.backtraceparsertest
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 74/74 (100%)CONDITIONAL 
33/50 (66%)
kioslave.desktop
FILES 2/3 (67%)CLASSES 2/3 (67%)LINE 110/144 (76%)CONDITIONAL 
56/90 (62%)
kioslave.desktop.tests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 84/84 (100%)CONDITIONAL 
37/72 (51%)
klipper
FILES 12/13 (92%)CLASSES 12/13 (92%)LINE 259/390 
(66%)CONDITIONAL 113/216 (52%)
klipper.autotests
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 595/693 (86%)CONDITIONAL 
349/820 (43%)
libtaskmanager
FILES 6/21 (29%)CLASSES 6/21 (29%)LINE 196/3341 (6%)CONDITIONAL 
122/3295 (4%)
libtaskmanager.autotests
FILES 2/2 (100%)CLASSES 2/2 (100%)LINE 151/151 
(100%)CONDITIONAL 85/170 (50%)
runners.bookmarks
FILES 8/8 (100%)CLASSES 8/8 (100%)LINE 87/157 (55%)CONDITIONAL 
34/96 (35%)
runners.bookmarks.browsers
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 88/93 (95%)CONDITIONAL 
84/107 (79%)
runners.bookmarks.tests
FILES 2/2 (100%)CLASSES 2/2 (100%)LINE 65/65 (100%)CONDITIONAL 
31/62 (50%)
runners.services
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 128/201 (64%)CONDITIONAL 
117/206 (57%)
runners.services.autotests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 67/70 (96%)CONDITIONAL 
50/90 (56%)
shell
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 57/90 (63%)CONDITIONAL 
20/76 (26%)
shell.autotests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 40/40 (100%)CONDITIONAL 
15/30 (50%)

[Powerdevil] [Bug 378445] kscreenlocker_greet occasionally freezes in malloc in signal handler

2017-05-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=378445

--- Comment #14 from r...@alum.mit.edu ---
Happened again:

#0  0x7ff984e2d13b in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x7ff984db262a in malloc () from /lib64/libc.so.6
#2  0x7ff985170e38 in operator new(unsigned long) () from
/usr/lib64/libstdc++.so.6
#3  0x7ff9867f065d in QQmlProperty::QQmlProperty(QObject*, QString const&)
() from /usr/lib64/libQt5Qml.so.5
#4  0x0040c65e in ?? ()
#5  
#6  0x7ff984daf0b6 in _int_free () from /lib64/libc.so.6
#7  0x7ff984db1980 in _int_realloc () from /lib64/libc.so.6
#8  0x7ff984db2daf in realloc () from /lib64/libc.so.6
#9  0x7ff985590897 in QString::reallocData(unsigned int, bool) () from
/usr/lib64/libQt5Core.so.5
#10 0x7ff9855910d4 in QString::append(QString const&) () from
/usr/lib64/libQt5Core.so.5
#11 0x7ff97f1aa292 in ?? () from /usr/lib64/libQt5DBus.so.5
#12 0x7ff97f1ac253 in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x7ff97f1ac464 in ?? () from /usr/lib64/libQt5DBus.so.5
#14 0x7ff97f1a4013 in QDBusConnection::connect(QString const&, QString
const&, QString const&, QString const&, QObject*, char const*) () from
/usr/lib64/libQt5DBus.so.5
#15 0x7ff97582212b in ?? () from /usr/lib64/libKF5Solid.so.5
#16 0x7ff97581ec04 in ?? () from /usr/lib64/libKF5Solid.so.5
#17 0x7ff9757f387e in
Solid::Device::listFromType(Solid::DeviceInterface::Type const&, QString
const&) () from /usr/lib64/libKF5Solid.so.5
#18 0x7ff9513a24b4 in ?? () from
/usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_powermanagement.so
#19 0x7ff9513a3255 in ?? () from
/usr/lib64/qt5/plugins/plasma/dataengine/plasma_engine_powermanagement.so
#20 0x7ff9856f171c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#21 0x7ff975853c06 in Solid::Battery::chargePercentChanged(int, QString
const&) () from /usr/lib64/libKF5Solid.so.5
#22 0x7ff975856817 in ?? () from /usr/lib64/libKF5Solid.so.5
#23 0x7ff9856f10d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#24 0x7ff975853726 in ?? () from /usr/lib64/libKF5Solid.so.5
#25 0x7ff975824c5d in ?? () from /usr/lib64/libKF5Solid.so.5
#26 0x7ff975855a2d in ?? () from /usr/lib64/libKF5Solid.so.5
#27 0x7ff9856f10d5 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#28 0x7ff97585cce3 in ?? () from /usr/lib64/libKF5Solid.so.5
#29 0x7ff97f1ae49b in ?? () from /usr/lib64/libQt5DBus.so.5
#30 0x7ff9856f2886 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#31 0x7ff9856c930c in QCoreApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Core.so.5
#32 0x7ff9856c9245 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#33 0x7ff9856cb2a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#34 0x7ff985718043 in ?? () from /usr/lib64/libQt5Core.so.5
#35 0x7ff9812b9134 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#36 0x7ff9812b9388 in ?? () from /usr/lib64/libglib-2.0.so.0
#37 0x7ff9812b942c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#38 0x7ff98571788c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#39 0x7ff9856c76ab in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#40 0x7ff9856cf344 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#41 0x00409bf4 in ?? ()
#42 0x7ff984d576e5 in __libc_start_main () from /lib64/libc.so.6
#43 0x00409e49 in _start ()

Again, I don't know this code, but there are some commonalities about the stack
traces:

1) They're always in a signal handler that's invoking
QQmlProperty::QQmlProperty, allocating memory.

2) Above the signal handler, they're allocating or freeing memory (not really
all that surprising; most versions of malloc aren't re-entrant).

3) Above that there are a variety of things, but they all seem to happen from
Solid::Battery::chargePercentChanged or Solid::Battery::chargeStateChanged.

In this case -- it hasn't always been true -- I had just driven home from work
with the laptop suspended, so the battery would have run down a bit.  I had
plugged it back in, resumed it, checked email, and then shut the lid (locking
the screen, but not suspending the laptop).  The hang happened about 10 minutes
after I first resumed it, so it's certainly possible that the laptop's charge
percent might have changed.  In other cases, though, it happened overnight,
when the laptop was surely fully charged.  That doesn't guarantee that the
charge state isn't changing, though.

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

Re: Plasma 5.10 Frameworks version problem

2017-05-01 Thread Marco Martin
On Monday 01 May 2017, Sebastian Kügler wrote:

> > 
> > Me too, we can still tag and branch on the original day, and the final
> > doesn't need to move. It's just the public release of the beta that would
> > need to slip.
> 
> +1, no problem shifting IMO.
+1

-- 
Marco Martin


Re: Minutes Monday Plasma Meeting

2017-05-01 Thread Marco Martin
On Monday 01 May 2017, Sebastian Kügler wrote:
> It's labour day, so the list of people attending was rather short.
> 
> Present: Sho, llucas, romangg, sebas (who has nothing relevant to report)

Adding my part:
* Kirigami 2.1 release
* systemsettings redesign
** adaptive layout
** micro layout fixes
* Kirigami 2:
** warning fixes when used in systemsettings redesign
** rename "Desktop" style to "org.kde.desktop"
** same rename for the desktop QQC2 theme
** kirigami theme called "org.kde.desktop.plasma" for further integration for 
now for animation length



-- 
Marco Martin


[kio-extras] [Bug 376344] cant write to smb shares which has write access

2017-05-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376344

--- Comment #20 from tempel.jul...@gmail.com ---
Two other workarounds:
1.:
Mount a networkfolder to make it look like it was local to Plasma.
Via terminal:
sudo mount -t cifs -o
username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770
//hostname.local/sharename/ /home/user/mountfolder/

Permanent via fstab:
//hostname.local/sharename/ /home/user/mountfolder/ cifs
defaults,username=*,password=*,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0
2

Or 2.:
Install a GTK file browser like Thunar with gvfs + gvfs-smb (+gnome-keyring for
saving login data). With it you can drag & drop stuff from and into SMB shares
or open media files without having to fully copy them first.

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

D5683: Add output scale to Wayland overview

2017-05-01 Thread Bhushan Shah
bshah accepted this revision.
This revision is now accepted and ready to land.

REPOSITORY
  R102 KInfoCenter

BRANCH
  wayland-output-scale

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

To: graesslin, #plasma, bshah
Cc: plasma-devel, spstarr, progwolff, Zren, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas, apol, lukas


D5683: Add output scale to Wayland overview

2017-05-01 Thread Martin Gräßlin
graesslin created this revision.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION SUMMARY
  This change lists the scale factor for the Wayland outputs.

REPOSITORY
  R102 KInfoCenter

BRANCH
  wayland-output-scale

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

AFFECTED FILES
  Modules/base/info_wayland.cpp

To: graesslin, #plasma
Cc: plasma-devel, spstarr, progwolff, Zren, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas, apol, lukas


D4503: Binary clock QML applet

2017-05-01 Thread David Edmundson
This revision was automatically updated to reflect the committed changes.
Closed by commit R114:990d291b8daf: Binary clock QML applet (authored by Joseph 
Wenninger , committed by davidedmundson).

REPOSITORY
  R114 Plasma Addons

CHANGES SINCE LAST UPDATE
  https://phabricator.kde.org/D4503?vs=11066&id=14053

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

AFFECTED FILES
  applets/CMakeLists.txt
  applets/binary-clock/CMakeLists.txt
  applets/binary-clock/Messages.sh
  applets/binary-clock/binaryclock.h
  applets/binary-clock/clockConfig.ui
  applets/binary-clock/package/contents/config/config.qml
  applets/binary-clock/package/contents/config/main.xml
  applets/binary-clock/package/contents/ui/BinaryClock.qml
  applets/binary-clock/package/contents/ui/Dot.qml
  applets/binary-clock/package/contents/ui/DotColumn.qml
  applets/binary-clock/package/contents/ui/configGeneral.qml
  applets/binary-clock/package/contents/ui/main.qml
  applets/binary-clock/package/metadata.desktop
  applets/binary-clock/plasma-applet-binaryclock.desktop

To: davidedmundson, #plasma, mart
Cc: mart, plasma-devel, spstarr, progwolff, Zren, lesliezhai, ali-mohamed, 
jensreuterberg, abetts, sebas, apol, lukas


Jenkins-kde-ci: plasma-desktop master kf5-qt5 » Linux,gcc - Build # 738 - Still Unstable!

2017-05-01 Thread no-reply

GENERAL INFO

BUILD UNSTABLE
Build URL: 
https://build.kde.org/job/plasma-desktop%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/738/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Mon, 01 May 2017 12:19:40 +
Build duration: 15 min

CHANGE SET
Revision cdb3ef1008a2ececea6b2b9213b58a79397ca3cd by David Edmundson: (Set 
correct KF5_MIN_VERSION)
  change: edit CMakeLists.txt


JUNIT RESULTS

Name: (root) Failed: 1 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 7 
test(s)Failed: TestSuite.appstreamtest

COBERTURA RESULTS

Cobertura Coverage Report
  PACKAGES 7/7 (100%)FILES 36/39 (92%)CLASSES 36/39 (92%)LINE 2306/3420 
(67%)CONDITIONAL 1546/3761 (41%)

By packages
  
kcms.cursortheme.xcursor
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 99/192 (52%)CONDITIONAL 
22/98 (22%)
kcms.keyboard
FILES 20/23 (87%)CLASSES 20/23 (87%)LINE 743/1511 
(49%)CONDITIONAL 600/1672 (36%)
kcms.keyboard.preview
FILES 4/4 (100%)CLASSES 4/4 (100%)LINE 500/582 (86%)CONDITIONAL 
431/1110 (39%)
kcms.keyboard.tests
FILES 5/5 (100%)CLASSES 5/5 (100%)LINE 229/231 (99%)CONDITIONAL 
236/358 (66%)
kcms.krdb
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 348/401 (87%)CONDITIONAL 
108/196 (55%)
kcms.lookandfeel
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 282/398 (71%)CONDITIONAL 
95/219 (43%)
kcms.lookandfeel.autotests
FILES 1/1 (100%)CLASSES 1/1 (100%)LINE 105/105 
(100%)CONDITIONAL 54/108 (50%)

Jenkins-kde-ci: plasma-workspace master kf5-qt5 » Linux,gcc - Build # 874 - Failure!

2017-05-01 Thread no-reply

GENERAL INFO

BUILD FAILURE
Build URL: 
https://build.kde.org/job/plasma-workspace%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/874/
Project: PLATFORM=Linux,compiler=gcc
Date of build: Mon, 01 May 2017 12:18:05 +
Build duration: 9 min 1 sec

CHANGE SET
Revision abb6b2ed3ddd17ff354e85fbb0dc9007e2429315 by David Edmundson: (Set 
correct KF5_MIN_VERSION)
  change: edit CMakeLists.txt


Re: Plasma 5.10 Frameworks version problem

2017-05-01 Thread David Edmundson
​Thanks.
I've updated all the CMakeLists.txt to reflect this.

David


Re: Plasma 5.10 Frameworks version problem

2017-05-01 Thread Eike Hein


On 05/01/2017 08:33 PM, Sebastian Kügler wrote:
> On zaterdag 29 april 2017 17:49:42 CEST David Edmundson wrote:
> 
>> We can either:
>>
>>  revert/ifdef those changes
>>
>>  shuffle something above
>>
>> I vote for shuffling around as it sounds like lots of efforts for little
>> gain. The KWin case is rather trivial, but nevertheless probably half an
>> hour of work to ensure it works. The iconSizeHints is even more work.
>>
>> So maybe just move the release by two days and ship together with
>> frameworks?
>>
>> Me too, we can still tag and branch on the original day, and the final
>> doesn't need to move. It's just the public release of the beta that would
>> need to slip.
> 
> +1, no problem shifting IMO.

+1, I'd really like to get the iconSizeHints changes in as they
fix/enable real user setups. It makes a difference.


Cheers,
Eike



Minutes Monday Plasma Meeting

2017-05-01 Thread Sebastian Kügler
It's labour day, so the list of people attending was rather short.

Present: Sho, llucas, romangg, sebas (who has nothing relevant to report)


Sho:
* [General/Launchers] Resurrected the Icons -> Advanced -> Panel size Settings
ow wait ... it's 1st May
** The default applet compact repr, the custom Kicker/Dashboard compact repr 
and the Icon applet now use this setting as maximum size when in a panel
** Fixes major pain point for users of wide vertical panels, where launchers/
icons grow to panel width, taking up major vertical space
** Complements a similar change recently done to the Task Manager applet to 
make the icon size configurable in vertical panels (this config remains as the 
TM applet is still special, e.g. re multi-column vertical layouts)
** Raised the default from 32 to 48 across the KCM code and the Breeze and 
Oxygen icon themes to match the Task Manager default
* [Launchers] Helped Ivan grapple with the Kicker backend for the new "Often 
used" tab in Kickoff by fixing some issues causing infinite loops in both old 
and new code
* [Pager] Tried to make sense of/reproduce a "dragging window to a different 
desktop only works when dragging down first" report, unsuccessfully though
* [Other] Researched Akademy flight plan, waiting for e.V. to book for me
* [Personal] Vacation day tomorrow, Wednesday 20h+ travel for a biz trip, 
recovery unknown :)

llucas 
* the promo team wants to make weekly reports out of our meeting notes, a good 
idea explained at https://phabricator.kde.org/T5741
* speaking about wayland we have a few user visible changes for Plasma 5.10 
https://notes.kde.org/public/plasma_5_10  While i think we should mention them 
in our 5.10 announcement

romangg: 
* working on the redshift for wayland last week, but it's a hard grind to 
split up the stuff on KWin and P-W/P-D
-- 
sebas

http://www.kde.org | http://vizZzion.org


Re: Plasma 5.10 Frameworks version problem

2017-05-01 Thread Sebastian Kügler
On zaterdag 29 april 2017 17:49:42 CEST David Edmundson wrote:

> We can either:
> 
>  revert/ifdef those changes
> 
>  shuffle something above
> 
> I vote for shuffling around as it sounds like lots of efforts for little
> gain. The KWin case is rather trivial, but nevertheless probably half an
> hour of work to ensure it works. The iconSizeHints is even more work.
> 
> So maybe just move the release by two days and ship together with
> frameworks?
> 
> Me too, we can still tag and branch on the original day, and the final
> doesn't need to move. It's just the public release of the beta that would
> need to slip.

+1, no problem shifting IMO.
-- 
sebas

http://www.kde.org | http://vizZzion.org


D5538: Implement QPlatformTheme::fileIconPixmap()

2017-05-01 Thread Eugene Shalygin
eshalygin added a comment.


  I don't have commit rights. Could someone commit this for me, please?

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

To: eshalygin, #plasma, markg
Cc: broulik, markg, plasma-devel, spstarr, progwolff, Zren, lesliezhai, 
ali-mohamed, jensreuterberg, abetts, sebas, apol, lukas