Summary: | [kde overlay] kde-base/ksmserver-9999: Failed Patch: ksmserver-4.10.50-noplasmalock.patch ! | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jakub Caban <kuba.iluvatar> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | 1i5t5.duncan, walter.sutter |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=462152 https://bugs.gentoo.org/show_bug.cgi?id=463176 https://bugs.gentoo.org/show_bug.cgi?id=464058 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jakub Caban
2013-11-23 12:43:58 UTC
Needs more review because these patches where made to fix a security problem. Can I help in any way? (In reply to Jakub Caban from comment #2) > Can I help in any way? Any help is welcome of course. If you want you can analyze the latest changes in upstream repo (kde-workspace, Branch KDE/4.11) and test the security problem reported in bug 462152. downstream patching is made in following packages: kde-base/ksmserver kde-base/plasma-workspace kde-base/systemsettings Could someone with summary-change privs add ksmserver-4.11.49.9999 to the summary? Same failed patch with it. Upstream commit 719554 commit 719554e489634d716c92ef2781c554789c88dc70 Author: Aaron Seigo <aseigo@kde.org> Date: Fri Nov 22 22:13:17 2013 +0100 also respect locking manually the code now: * shows the lock GUI immediately if called by dbus or in testing * a new screen is attached after the lock grace * otherwise behaves as it did prior to this commit ... catching those two issues meant additional state tracking, but all the ways i can find to lock work now. Among changes to other files it touches ksldapp.cpp, the same file gentoo's patch touches, in the same area (around line 270, line numbers change a bit). *** Bug 492736 has been marked as a duplicate of this bug. *** Updated the patch for the new code. Not 100% sure if it is still needed but there are conflicting reports on the upstream bug. |