--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian....@packages.debian.org
Usertags: pu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear release team,
KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch.
I've updated the packages that contain fixes in the 5.8.7 plasma point release
in unstable and I would like to upload them to stretch-pu.
The source packages that I would like to update in stretch are:
bluedevil/4:5.8.7-1+deb9u1
breeze-gtk/5.8.7-1+deb9u1
kde-cli-tools/4:5.8.7-1+deb9u1
kscreenlocker/5.8.7-1+deb9u1
libksysguard/4:5.8.7-1+deb9u1
plasma-pa/4:5.8.7-1+deb9u1
systemsettings/4:5.8.7-1+deb9u1
user-manager/4:5.8.7-1+deb9u1
kwin/4:5.8.7-1+deb9u1
plasma-workspace/4:5.8.7-1+deb9u1
plasma-desktop/4:5.8.7.1-1+deb9u1
The corresponding changes includes are:
bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
#########
bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch.
* Document how to run bluedevil in in other DEs (Closes: 781012)
-- Maximiliano Curia <m...@debian.org> Sat, 17 Jun 2017 12:23:14 +0200
bluedevil (4:5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7).
+ ReceiveFileJob: Don't cancel the request right after accepting it
KNotification::closed is emitted also when one of the notification
actions was triggered.
KDE#376773
-- Maximiliano Curia <m...@debian.org> Sun, 28 May 2017 18:35:52 +0200
bluedevil (4:5.8.5-1) experimental; urgency=medium
* New upstream release (5.8.5).
-- Maximiliano Curia <m...@debian.org> Fri, 30 Dec 2016 18:46:11 +0100
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff
breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
##########
breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 08:55:23 +0200
breeze-gtk (5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7)
+ Set no stepper button for GTK3 scrollbars on gtk >=3.20
This is a workaround to mitigate broken (huge wide) scrollbars in
mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
onwards.
Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
The mozilla bug is now 'fixed' and landing in nightlies v55, but may
continue to affect earlier releases if not brought forward upstream.
Regardless of any other concern, applying this brings the appearance
of newer breeze and breeze-gtk scrollars into closer accord.
KDE#377008
-- Maximiliano Curia <m...@debian.org> Tue, 06 Jun 2017 17:14:40 +0200
breeze-gtk (5.8.5-1) experimental; urgency=medium
* New upstream release (5.8.5).
-- Maximiliano Curia <m...@debian.org> Fri, 30 Dec 2016 18:46:12 +0100
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff
kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
#############
kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 09:11:58 +0200
kde-cli-tools (4:5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7)
+ Fix query for available modules
The old query was bad because two reasons:
* it didn't use the same query systemsettings uses
* it didn't use exist so if the first property did not exist the
second one was not evaluated since the parser bailed out
Test Plan: Ran kcmshell5 --list, it's better now
This fixes KDE#378548
-- Maximiliano Curia <m...@debian.org> Thu, 08 Jun 2017 16:15:10 +0200
kde-cli-tools (4:5.8.5-1) experimental; urgency=medium
* New upstream release (5.8.5).
-- Maximiliano Curia <m...@debian.org> Fri, 30 Dec 2016 18:46:13 +0100
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kde-cli-tools_4:5.8.4-2_4:5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kde-cli-tools_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kde-cli-tools_4:5.8.4-2_4:5.8.7-1+deb9u1.debian.diff
kscreenlocker 5.8.6-2 currently in stretch to 5.8.7-1+deb9u1
#############
kscreenlocker (5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 09:27:23 +0200
kscreenlocker (5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7)
+ Implement manual focus on click
Currently only the first created screenlock window gets focus.
On clicks, no focus events are sent, which makes it impossible to input
passwords. This patch now makes it possible to focus to a different
screenlock window (on a different monitor, for example) using a mouse
button press.
This should also fix newly created screenlock windows stealing the focus
of already displayed ones as only the first window gains automatic focus.
Fixes KDE#348789, KDE#374289
-- Maximiliano Curia <m...@debian.org> Thu, 08 Jun 2017 17:14:31 +0200
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6-2_5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6-2_5.8.7-1+deb9u1.debian.diff
libksysguard 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
############
libksysguard (4:5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 09:46:18 +0200
libksysguard (4:5.8.7-1) unstable; urgency=medium
* Add new patch: Drop-html-markup-from-polkit-action-file.patch.
Thanks to Michael Biebl for reporting (Closes: 696905)
* New upstream release (5.8.7)
+ Don't reset the view to the top on gaining focus
when the listview gained focus, it used to reset
the view position to the first element, but this both lost the
previously selected item and was a really weird behavior especially
when the focus was gained by click rather than keyboard
navigation, and was often seen as a bug.
Fixes KDE#363420
* Drop upstream applied patch: Drop-html-markup-from-polkit-action-file.patch
-- Maximiliano Curia <m...@debian.org> Mon, 12 Jun 2017 13:06:27 +0200
libksysguard (4:5.8.5-1) experimental; urgency=medium
* New upstream release (5.8.5).
-- Maximiliano Curia <m...@debian.org> Fri, 30 Dec 2016 18:46:19 +0100
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/libksysguard_4:5.8.4-1_4:5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff
plasma-pa 4:5.8.6-1 currently in stretch to 4:5.8.7-1+deb9u1
#########
plasma-pa (4:5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 09:55:33 +0200
plasma-pa (4:5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7)
+ KCM: Fix 100% volume label position with RTL
+ Context: Use DBus service watcher to reconnect to pulseaudio
Make sure to reconnect to pulseaudio after it crashes.
Fixes KDE#358772
-- Maximiliano Curia <m...@debian.org> Mon, 12 Jun 2017 14:45:01 +0200
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-pa_4:5.8.6-1_4:5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-pa_5.8.6_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-pa_4:5.8.6-1_4:5.8.7-1+deb9u1.debian.diff
systemsettings 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
##############
systemsettings (4:5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 10:12:38 +0200
systemsettings (4:5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7)
+ Set the correct desktop file name when in a KDE session.
System Settings installs two .desktop files:
- kdesystemsettings.desktop setting NotShowIn=KDE, for non-KDE desktops
- systemsettings.desktop, the one we use in Plasma
As of 39e13de3468a, it sets "kdesystemsettings" as its desktop file
name using KAboutData. As this is not the one we show in our menus,
it's not the one used as applicationId for the KStartupInfo provided
to the Task Manager after starting System Settings. With the eventual
window telling the Task Manager to use a different .desktop file, the
Task Manager can no longer match up the startup notification and the
window, causing them to co-exist instead of replace each other.
Telling the environment you're running in to look at a .desktop file
you've also told it to ignore is wrong app behavior, and this should
not be worked around in the Task Manager (especially as it would
cause I/O in a hotpath, requiring it to open and parse the .desktop
file to realize it's crummy and ignore it, falling back from the
window hint to a slow heuristic).
This patch instead makes it use the correct desktop file name when
KDE_FULL_SESSION is set. This completes the original hack of shipping
two .desktop files.
-- Maximiliano Curia <m...@debian.org> Fri, 16 Jun 2017 10:51:05 +0200
systemsettings (4:5.8.5-1) experimental; urgency=medium
* New upstream release (5.8.5).
-- Maximiliano Curia <m...@debian.org> Fri, 30 Dec 2016 18:46:24 +0100
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/systemsettings_4:5.8.4-1_4:5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/systemsettigns_5.8.4_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/systemsettings_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff
user-manager 4:5.8.5-2 currently in stretch to 4:5.8.7-1+deb9u1
############
user-manager (4:5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 10:20:15 +0200
user-manager (4:5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7)
+ Make sure the new avatar is always saved
The KIO job needs to be run synchronously, otherwise the KCM might be
deleted before the job finished. This happens when closing the KCM
module with the Ok button, or when closing the System Settings window
and clicking Apply.
Fixes KDE#350836
-- Maximiliano Curia <m...@debian.org> Fri, 16 Jun 2017 11:06:20 +0200
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/user-manager_4:5.8.5-2_4:5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/user-manager_5.8.5_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/user-manager_4:5.8.5-2_4:5.8.7-1+deb9u1.debian.diff
kwin 4:5.8.6-1 currently in stretch to 4:5.8.7-1+deb9u1
####
kwin (4:5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 10:26:52 +0200
kwin (4:5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7)
+ move the view at the correct index at startup
using the same trick as elsewhere, set the currentIndex
and move the view to currentIndex right at startup
the only way to be sure is onContentHeightChanged
as there are no signals for when "the view has been
populated and settled up"
+ [kcm_kwindecoration] Respect theme colors in buttons
+ Fix crash on dragging titlebar buttons in System Settings
Currently, if user tries to move one of buttons to the left, ending up
dragging one button onto another, crash occurs.
In addition, this patch replaces verbose replacement(remove/insert) with
more elegant QVector<T>::move(int, int)
Fixes KDE#374153
+ [platforms/drm] Explicitly request event context version 2
Libdrm 2.4.78 introduces a version 2 and if KWin gets built against it
our code would break. Given that this change is for Plasma/5.8 branch.
(https://phabricator.kde.org/T5839)
+ Fix KWin decoration KCM showing correct index at startup
The KCM has a context property of the currently set theme index. This is
set before the decorations model is populated, so it is currently always
-1.
This model is populated after the constructor but before
KCModule::load().
KCModule::load is called from KCModule::showEvent so before
QQuickGridView will start doing anything with delegates.
This fixes the problem simply and also avoid parsing the config file
multiple times.
This bug was introduced in 5.9.4:
Someone made a (tested) change to make sure the view scrolled to the
right place on startup.
I then made a (tested) commit fixing the crash on exit
The author then updated his patch to my changes, but now in a way that
didn't work.
+ Sort the themes in decoration KCM
Even though we're using a QSortFilterProxy model, by default it doesn't
actually sort anything until instructed to.
This patch turns sorting on.
+ Improve the x11 timestamp handling
So far KWin only updated the x11 timestamp if the new timestamp is
larger
than the existing one. While this is a useful thing it creates problems
when the 32 bit msec based time stamp wraps around which happens after
running an X server for 49 days. After the timestamp wrapped around KWin
would not update the timestamp any more and thus some calls might fail.
Most prominent victims are keyboard and pointer grab which fails as the
timestamp is either larger than the server timestamp or smaller than the
last grab timestamp.
Another problem related to timestamp handling is KWin getting broken by
wrong timestamps sent by applications. A prominent example is clusterssh
which used to send a timestamp as unix time which is larger than the
x timestamp and thus our timestamp gets too large.
This change addresses these problems by allowing to reset the timestamp.
This is only used from updateXTime (which is normally invoked before we
do things like grabKeyboard). Thus we make QX11Info::getTimestamp the
ultimate trusted source for timestamps.
Fixes KDE#377901 KDE#348569
+ Fix regression for timestamp handling for Xwayland windows
Change 0bec9ad7337536e319c17c5684d97e1156399fdb introduced a regrssion
on Wayland. On Wayland getTimestamp always returns 0, thus the X11
timestamp gets reset again and again. This results in broken interaction
for Xwayland windows as the broken unit tests show.
This change addresses the regression by ignoring a value of 0.
It means the addressed bug is still present on Wayland for X11 windows
as the timestamp doesn't get updated properly. This requires further
changes.
+ fix occassional crash caused by needlessly delayed signals (bko#363224)
As pointed out by the Valgrind trace in #363224, delaying the signal
causes
the EffectWindow* argument to become invalid before the connected slot
is
called (this is because Qt discards only delayed signal->slot calls
where
the receiver gets deleted meanwhile, not the sender and definitely not
a random argument.
If the supposed glitches really happen, they should get fixed correctly,
and for all cases (I doubt only desktop number would be involved but
not e.g. shaded or minimized states).
Related to KDE#363224
-- Maximiliano Curia <m...@debian.org> Fri, 16 Jun 2017 13:43:10 +0200
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kwin_4:5.8.6-1_4:5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kwin_5.8.6_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kwin_4:5.8.6-1_4:5.8.7-1+deb9u1.debian.diff
plasma-workspace 4:5.8.6-2.1 currently in stretch to 4:5.8.7-1+deb9u1
################
plasma-workspace (4:5.8.7-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 10:33:12 +0200
plasma-workspace (4:5.8.7-1) unstable; urgency=medium
* New upstream release (5.8.7)
+ [Logout Screen] Show suspend button only if supported
Fixes KDE#376601
+ try harder to make the selected wallpaper visible
qml gridview don't have an official way to ensure the
current index is visible when the view is first instantiated,
the only way we have is to do positionViewAtIndex when we know the
proper space has already been allocated (Component.onCompleted
is way too early) we used to do that on onCountChanged, but that
too seems to early sometimes, as the selected wallpaper
is visible only sometimes, attaching it to onContentHeightChanged
seems to be more reliable (for all branches)
+ Ignore NoDisplay=true .desktop entries when matching by Name.
We currently match Krita by Name. It's classClass is "krita",
but its DesktopEntryName is org.kde.krita.desktop. However,
Krita also installs numerous additional .desktop entries to
associate more file types by itself, all of which match by
name, and the first one in the list isn't the right one. All
of those extra .desktop files are NoDisplay=true however, so
we can filter them out, which brings the match list down to
the one and only .desktop file we care for.
+ try proper order of corona()->availableScreenRect()
connect to Plasma::Corona::availableScreenRectChanged
instead of using kscreen, this way we should be more sure
that signal is emitted when it's safe to call
corona()->availableScreenRect() as the change of rect
may happen after a screen removal, so may mean
accessing a desktop view while being deleted
Fixes KDE#377298
+ don't emit availableScreenRectChanged when quitting
if applets react to it it can cause a crash, because the corona
may not be valid anymore, and we don't want to relayout
things anyways when tearing down
+ manage mouse events when out of the window
mouseareas must support event grabbing when the mouse is out of the
window too
Fixes KDE#377545
+ [OSD] Allow disabling OSD through config file
+ [Calculator Runner] Use "approximate" approximation mode
The runner calculator isn't entitled for being a scientifically correct
calculator.
This keeps seemingly innocent calculations such as "2^0.333333333" from
eating all RAM until it crashes.
A hint is added to the result if it is only an approximation.
Fixes KDE#277011
+ Fix TasksModel.anyTaskDemandsAttention not updating on window closure.
Previously we updated the prop after checking for
AbstractTasksModel::IsDemandingAttention on window closure, but
as the window is gone, we can't actually get state for it anymore,
so we always need to update.
To make up for it, this patch also optimizes the prop updates to occur
only once per insert/remove batch - this is a bit academic because
the source models currently only insert single rows at a time, but
it's good hygiene.
Fixes KDE#378254
+ Correctly handle when a new primary screen displaces the old
this is for the following setup:
the primary screen is at position 0,0 and gets disconnected.
the other screen will be moved at 0,0 and becomes primary
the screen is reconnected, the events arrive in the followin order:
1) a new screen gets added, at 0,0 position
(not primary yet, it may be markedredundant)
2) the screen becomes primary, both screens still at 0,0
3) the old screen gets moved out of the way
in the end result none of the two need to be redundant.
adding the old one in the redundant list, will cause reconsideroutputs
to consider it and create a view for it.
+ When deleting the panel the notifications applet is in, the containment
is being destroyed but the corona
is still there and rightfully emits availableScreenRectChanged.
This will cause us to crash when we try to access the no-longer
existing containment.
Related to KDE#378508
+ [Media Controller] Use double for length instead of int
Length is in microseconds, so watching a long video (in excess of 33.3
minutes) will break the slider.
CHANGELOG: Media Controller can now properly handle and seek long
tracks (> 30 minutes)
Fixes KDE#377623
+ Fix off-by-one.
Related to KDE#373075
+ [Media Controller] Enforce PlainText format
Unfortunately doesn't apply to toolTipMainText
+ recognize the WM even if given with a full path
Normally kWin is launched simply as "kwin" ("kwin_x11", whatever), but
in some cases it's restart command may be "/usr/bin/kwin", most notably
when KWin restarts itself after a crash. Failing to recognize this
client
as the WM leads to KWin starting without any session management
restoring.
Related to KDE#377756
+ launch autostart apps in ksmserver using KRun, not QProcess
The "move" (copy in fact) of the autostart code from klauncher simply
switched to QProcess. This resulted in a number of problems, as the
incorrect
handling of .desktop file command if it had placeholders (worked around
already), kdeinit is no longer used (not sure how much that matters
nowadays)
and finally QProcess simply eats all stdout/stderr of all such processes
(which, when daemonized, can lead even to the processes getting
SIGPIPE'd).
If the application to start is a KService, simply launch it as such.
Fixes KDE#369391, KDE#370528 (Closes: 840478)
+ use KProcess instead of QProcess to launch apps in ksmserver
Follow-up to the previous commit. KProcess has saner defaults for simply
launching an app and being done with it, no lost stdout/stderr or even
SIGPIPE.
Related to KDE#369391, KDE#370528
+ selecting the topmost klipper item should always set it as clipboard
contents
Without this, that wasn't always the case if the top item was only the
mouse
selection. This was presumably broken by 2e47d84772.
Also explicitly check the popup item, since it's now owned by Klipper.
Fixes KDE#348390, KDE#251222
+ Revert "launch autostart apps in ksmserver using KRun"
KRun::runApplication will show blocking error dialogs if it fails to
find the executable
This means we don't autostart the next app, which could be fatal if it
comes before...
...kwin/plasma
We shouldn't be having blocking calls in ksmserver it can deadlock
And even in the best case we'd still end up blocking ksplash for 30
seconds
We then port to KProcess which was part of the motivation behind the
patch as it
has better stdout handling
This reverts commit 0f19e92f3e85d064de9cebf280fa8e085485c2e0.
Fixes KDE#379254
Also added port of autostarting applications to KProcess
It has better stdout handling
+ Update unit test to match change to reselecting top entry
37014e643cec4ee9aed54421f66c675e1bc91b70 introduced a change in the
behaviour of what happens when you select the top entry in the list.
Change makes some sense. Unit test was not updated, it therefore failed.
+ [Weather] Fix lookup of bbcukmet translations strings, stored in
lowercase
+ [Weather] Remove duplicated/bad strings from bbcukmet data db
+ [Weather] Add missing strings from bbcukmet data db
+ [Weather] Fix term used for thunderstorm in bbcukmet data db
+ don't check for panel visible during startup
if any kscreen related activities occurred
during startup, the panel wouldn't be visible
yet, and this would assert. This often happens
when a screen gets disabled at startup
Related to KDE#377280
+ remove useless debug
* Add new upstream patch: xembedsniproxy-Fix-check-whether-to-use-XTest.patch
* Add missing build dependency (libxtst-dev)
* Add explicit libkf5plasma5 versioned dependency (Closes: 829614)
Thanks to Gard Spreemann and others for reporting and the updates
-- Maximiliano Curia <m...@debian.org> Fri, 16 Jun 2017 18:13:01 +0200
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-workspace_4:5.8.6-2.1_4:5.8.7-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-workspace_5.8.6_5.8.7.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-workspace_4:5.8.6-2.1_4:5.8.7-1+deb9u1.debian.diff
plasma-desktop 4:5.8.6-1 currently in stretch to /4:5.8.7.1-1+deb9u1
##############
plasma-desktop (4:5.8.7.1-1+deb9u1) stretch; urgency=medium
* Upload to stretch
-- Maximiliano Curia <m...@debian.org> Mon, 19 Jun 2017 11:40:56 +0200
plasma-desktop (4:5.8.7.1-1) unstable; urgency=medium
* New upstream release (5.8.7.1)
+ Revert "use KPluginMetaData::readStringList"
This reverts commit 7993cd433ca68a0136a990d3f1710a6360024fe9
+ Set root.dragging to false during reset.
Fixes KDE#376633
+ Fix default fixed font in fonts kcm
Now it is the same as used by plasma-integration.
Also adjust the file name in the comment, which was apparently
forgotten.
Fixes #863243
+ Fix switching categories via the filter listview on touchscreens.
+ Disable editing of 'Global Shortcuts' component names
Fixes KDE#376935
+ [Folder View] Fix action button hover and pressed state
The hover state didn't work because it referenced "pressed" which it
didn't find in the scope.
The pressed graphic suffix was wrong.
+ [AppletAppearance] Silence warning
"applet" is set after the item is created and would result in a warning
on startup.
+ Do apply margin if in right-to-left mode.
Fixes KDE#376529
+ [Folder View] Explicitly set prefix as empty in normal state
Somehow with FrameSvg optimizations State no longer manages to reset
the property back to its original state when state is reset.
Fixes KDE#377441
+ [Kicker] Fix highlighting favorites
ToolTipArea steals mouse events from the MouseEventListener.
Related to KDE#377652
+ Add missing member initialization.
Fixes KDE#378016
+ [Applet Alternatives] Fix icon size
Another regression with new IconItem implicit size handling.
Unintuitively implicit size has precedence over regular size when
placed in a Layout,
since the latter is managed by it.
+ [Applet Alternatives] Don't animate highlight resize
The delegates hardly differ in size leading to ugly jumps when moving
the selection
+ [Folder View] Use toDisplayString which strips passwords
Otherwise we might be leaking sensitive information.
+ [Task Manager] Keep entry highlighted when context menu or group dialog
is open
This makes it easier to see what item the menu or popup is for.
In fact, the item should have stayed highlighted when the context menu
is open but this was broken.
Also, for consistency, use the hover effect also for the group dialog
(it used to be the "active" task).
+ Backport 5.9/Master's GroupDialog code to 5.8.
This brings us to a common baseline on the three active branches
and addresses regressions on the 5.8 branch.
5.9's code added a scrollbar and improved keyboard nav.
Fixes KDE#378042
+ Fix -Wreorder warning.
+ possible to edit the default color scheme
no reason to not allow editing the default color sheme
with an invalid path, everyting falls back to the default,
keeping the dialog fully functional
+ make sure the "default" sheme is actually default
+ Remove implicit use of QtQml in Qt 5.7
The Plasma 5.8 branch should work with Qt 5.6.
This means we don't have the Connections enabled property available.
This moves the enabling logic into the handler.
Fixes KDE#380240 (Closes: 863243)
-- Maximiliano Curia <m...@debian.org> Fri, 16 Jun 2017 19:19:32 +0200
The full debdiff is available in
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-desktop_4:5.8.6-1_4:5.8.7.1-1+deb9u1.debdiff
The full upstream gitlog and the diff for the debian packaging are:
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-desktop_5.8.6_5.8.7.1.upstream.gitlog
https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/plasma-desktop_4:5.8.6-1_4:5.8.7.1-1+deb9u1.debian.diff
Please consider accepting this series of updates for stretch.
Happy hacking,
- -- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'testing'), (50, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCgAuFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAllHng4QHG1heHlAZGVi
aWFuLm9yZwAKCRDHGXaZspsjKn4vEACzoM1RTtw/S1OsncihPJ8Wr/gdniMeLoCw
CZFdBCVkmQIPPGQ0lqx/rFvgeAJXM9SFAPdCrcompMyNZEVeE7ocwwGDvDxiKkwF
tkiZeznuNb+Qk9G/mzes7cLLybo0QxGWAcX8pOQqD+K8NmEamDP3r/aYm/U+ImBT
ypmVR4LaCH2sc7/dgvpivbnt9gTAwGlh3+P6NXMNHKNfUzeVo1GHMvnarF3L28pa
+RwphRk4EVo3uKyZ9s1+Lmtbt8VL6Ty/cskTjJpaFAAoc1uqj22PbKFOiOcszCt1
hJp5BOZx/BJnaSTl9qSpvWbln9SSHSM6IIOLTbdAi2BCa96OSX7q6h27KNeYEALN
nhHFLHvyjgrHTXbp+TLuUW0e8wD1zeb3V5DfFz3ojbR/SUTqE5vxVVOAoozGtbUc
b6T5K1a6Ls083zgUkkLlqqFxxvcBsxbiI92fpVBbqQvE2lVmmLRwwXK15ukjyu8q
w20Kh3ePOpJRHorT6Lvowl6IF+eL1oc89hVxO2IZ/9XOCCO2uNtAxOByMxtOE6RS
m/deE1xIi7VjvFUPC2X9ev0ffh1CWh59L+iAu4TVuvNMZdqMQSbGbS/pL8PuH6HH
r4d7mKwezPP7tk00gvrtDb4ri09UmdlJ3xAFfVXHQPss0XJKIgTsQzxlMlmi/LJj
D6vU2FZtRA==
=/vDC
-----END PGP SIGNATURE-----
--- End Message ---
