---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120577/#review68345
---
Could we possibly get Suspend button instead? Suspend stores
On Okt. 14, 2014, 7:02 vorm., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On 14.10.2014 01:01, David Edmundson wrote:
On Mon, Oct 13, 2014 at 4:09 PM, Marco Martin notm...@gmail.com
mailto:notm...@gmail.com wrote:
on either case, should be very easy to recycle the complete wallpaper
mechanism of plasmashell, even the qml only wallpapers (that if
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120577/#review68352
---
+1000 from me
- Marco Martin
On Ott. 14, 2014, 5:41 a.m.,
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Okt. 14, 2014, 7:02 vorm., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
Hello,
currently in Plasma5 auto-hidden panels work in a way that it basically
requires mouse slamming either twice or very very hard against the screen
edge which has the panel. Quoting from [1] This is configurable in KWin.
KWin doesn't trigger screen edges directly, but requires a strong push.
On Okt. 14, 2014, 7:02 vorm., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I
On Mon, Oct 13, 2014 at 12:31:19PM -0700, Andrew Lake wrote:
Can anyone confirm that this bug exists in 5.1? I don't think the fix made
it in time, but I wanted to check before adding it to the errata.
https://bugs.kde.org/show_bug.cgi?id=339849
It does exist in the 5.1 tar, you can
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Tuesday 14 October 2014 10:43:42 Martin Klapetek wrote:
Any opinions/objections?
as I implemented it this way I can share the reasons why I did go for re-using
the screen edge activation we have for other things. First of all:
consistency. All edges work the same way and users can expect
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Tuesday 14 October 2014, Martin Klapetek wrote:
I'd like to change this for Plasma panels to not have any resistance or
very minimal one, basically get it into a state that slamming the mouse
against a screen edge will show the panel easily, without requiring an
additional push.
i'm a
On Tue, Oct 14, 2014 at 11:27 AM, Marco Martin notm...@gmail.com wrote:
On Tuesday 14 October 2014, Martin Klapetek wrote:
I'd like to change this for Plasma panels to not have any resistance or
very minimal one, basically get it into a state that slamming the mouse
against a screen edge
On Říj. 14, 2014, 9:02 dop., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120577/#review68365
---
This is related to
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120577/
---
(Updated Oct. 14, 2014, 9:45 a.m.)
Review request for Plasma and Aleix
Thanks for starting this :)
Just to recap, here's the stuff I can see myself needing from
the Task Manager and Kicker side:
* Recently used applications across the entire system.
* Most frequently used applications across the entire system.
* Recently installed applications.
* Recently used
On Tuesday 14 October 2014, David Edmundson wrote:
I'd quite like to use the wallpaper plugins from SDDM too; which means
exposing WallpaperInterface in a slightly different manner than you'd
probably be wanting to use for the lock screen, as I can't go via a
Containment.
doesn't even need
On Oct. 14, 2014, 9:02 a.m., Martin Klapetek wrote:
Could we possibly get Suspend button instead? Suspend stores the session
state into memory and then restores it without any issues (and we lock
screen on wakeup anyway); many times I have found my laptop with locked
screen and I had
On Tuesday 14 October 2014 11:42:13 Martin Klapetek wrote:
On Tue, Oct 14, 2014 at 11:27 AM, Marco Martin notm...@gmail.com wrote:
On Tuesday 14 October 2014, Martin Klapetek wrote:
I'd like to change this for Plasma panels to not have any resistance or
very minimal one, basically get it
On Tue, Oct 14, 2014 at 12:12 PM, Martin Gräßlin mgraess...@kde.org wrote:
huh? all of that should not be needed. Just continue to move into the same
direction and it will trigger. Especially there should not be any need to
do
the same movement twice as the mouse pointer gets repositioned.
I just noticed at the last minute that the Plasma tars didn't have
their internal version numbers updated to 5.1.0, the script I wrote to
make that easier must have only updated master and not branch. I'm
going to reroll the tars now to fix the version number. Sorry folks.
Jonathan
also, once what it can do and can't is explained well, the VDG can go crazy
with ideas for taskbar/launchers
+1
could the generic kpart patch that was at some point in kdelibs4 then
removed be in kf5 kparts? would it work with current architecture?
I'm guessing it would work. Don't know
On Oct. 14, 2014, 12:34 p.m., Aleix Pol Gonzalez wrote:
I think it's unfortunate, you're giving a mix of technical and usability
reasons to back your patch. In any case, I understand that the bug needs to
be solved and if this is what it takes, then do it.
FWIW, I also think
On Tuesday, October 14, 2014 11:22:39 Jonathan Riddell wrote:
I just noticed at the last minute that the Plasma tars didn't have
their internal version numbers updated to 5.1.0, the script I wrote to
make that easier must have only updated master and not branch. I'm
going to reroll the tars
On Tuesday 14 October 2014 12:19:24 Martin Klapetek wrote:
To overcome the panel resistance in one single mouse movement it takes me
moving the mouse across half the table here.
This would indicate that the overall edge triggering code needs to be
improved. I'm certainly not saying that it's
On Oct. 14, 2014, 10:34 a.m., Aleix Pol Gonzalez wrote:
I think it's unfortunate, you're giving a mix of technical and usability
reasons to back your patch. In any case, I understand that the bug needs to
be solved and if this is what it takes, then do it.
FWIW, I also think
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120471/
---
(Updated Oct. 14, 2014, 11:40 a.m.)
Status
--
This change has been
New tars up at
http://starsky.19inch.net/~jr/tmp/plasma-5.1.0/
and coming soon to depot
To save time I cheated and just ran sed on the CMakeLists.txt file of
most of them to fix the version number but I did reroll breeze to fix
the BreezeDark.color filename, oxygen to fix build for the Qt4 and
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120579/#review68383
---
-2, it's not installed as the WaylandServer still needs work
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120579/#review68384
---
that said: I'm happy to take a patch to fix the export header
On Oct. 14, 2014, 11:50 a.m., Martin Gräßlin wrote:
-2, it's not installed as the WaylandServer still needs work and is not in
a state yet to provide ABI.
Well, neither is WaylandServer, the point at this point in time is to allow
sharing code, no?
Is there another way to easily start a
On Oct. 14, 2014, 11:54 a.m., Martin Gräßlin wrote:
that said: I'm happy to take a patch to fix the export header ;-)
Sure, I can push that part separately (with commented INSTALL directive), but
let's sort that thread of the discussion out, first.
- Sebastian
https://bugs.kde.org/show_bug.cgi?id=339391
--- Comment #16 from Vincent Petry pvinc...@yahoo.fr ---
Created attachment 89126
-- https://bugs.kde.org/attachment.cgi?id=89126action=edit
Failed pm-suspend.log
It happened again, when running pm-suspend directly.
I've attached the log.
It looks
On Oct. 14, 2014, 1:50 p.m., Martin Gräßlin wrote:
-2, it's not installed as the WaylandServer still needs work and is not in
a state yet to provide ABI.
Sebastian Kügler wrote:
Well, neither is WaylandServer, the point at this point in time is to
allow sharing code, no?
https://bugs.kde.org/show_bug.cgi?id=339391
--- Comment #17 from Vincent Petry pvinc...@yahoo.fr ---
Just checked dmesg from before the crash but there is no relevant info. The
last entries are from a few hours before... not sure whether they got eaten.
I could imagine that suspending prevents
https://bugs.kde.org/show_bug.cgi?id=339391
--- Comment #18 from Vincent Petry pvinc...@yahoo.fr ---
I raised a ticket in the kernel tracker:
https://bugzilla.kernel.org/show_bug.cgi?id=86241
I suggest to continue the discussion there.
--
You are receiving this mail because:
You are the
https://bugs.kde.org/show_bug.cgi?id=339391
--- Comment #19 from Roberto figj...@libero.it ---
I used powertop a few times in the past weeks, and then switched to tlp. Of
course I have tried to disable tlp to see if that helps (it doesn't).
My filesystem is ext4.
--
You are receiving this mail
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120579/
---
(Updated Oct. 14, 2014, 12:49 p.m.)
Status
--
This change has been
On Oct. 14, 2014, 1:50 p.m., Martin Gräßlin wrote:
-2, it's not installed as the WaylandServer still needs work and is not in
a state yet to provide ABI.
Sebastian Kügler wrote:
Well, neither is WaylandServer, the point at this point in time is to
allow sharing code, no?
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120581/
---
Review request for KDE Frameworks and Plasma.
Repository:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120581/#review68390
---
Ship it!
Inviala!
- Marco Martin
On Ott. 14, 2014, 1:09
On Oct. 14, 2014, 11:50 a.m., Martin Gräßlin wrote:
-2, it's not installed as the WaylandServer still needs work and is not in
a state yet to provide ABI.
Sebastian Kügler wrote:
Well, neither is WaylandServer, the point at this point in time is to
allow sharing code, no?
On Oct. 14, 2014, 1:50 p.m., Martin Gräßlin wrote:
-2, it's not installed as the WaylandServer still needs work and is not in
a state yet to provide ABI.
Sebastian Kügler wrote:
Well, neither is WaylandServer, the point at this point in time is to
allow sharing code, no?
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120581/
---
(Updated Oct. 14, 2014, 1:46 p.m.)
Status
--
This change has been
On Tuesday 14 October 2014 10:43:42 Martin Klapetek wrote:
I'd like to change this for Plasma panels to not have any resistance or
very minimal one, basically get it into a state that slamming the mouse
against a screen edge will show the panel easily, without requiring an
additional push.
I
On Oct. 13, 2014, 1:35 p.m., Marco Martin wrote:
src/quickaddons/managedtexturenode.h, line 52
https://git.reviewboard.kde.org/r/120550/diff/2/?file=318205#file318205line52
even if will always remain just this member, just to me sure, it should
be in a dpointer
Aleix Pol
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120550/#review68396
---
src/quickaddons/imagetexturescache.h
See http://build.kde.org/job/plasma-workspace_master_qt5/973/changes
Changes:
[me] Baloo Runner: Port to newer api
--
[...truncated 2340 lines...]
[ 40%] Building CXX object
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120584/
---
Review request for Plasma.
Repository: plasma-workspace
Description
See http://build.kde.org/job/plasma-workspace_master_qt5/974/changes
Changes:
[mart] Make apply button work correctly
--
[...truncated 2293 lines...]
const QSetSolid::PowerManagement::SleepState spdMethods =
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120584/#review68400
---
looks like a useful change to me (and I hope it fixes the
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120584/#review68401
---
That seems to fix the panel showing on the wrong screen I was
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120584/#review68402
---
Ship it!
Ship It!
- Jeremy Whiting
On Oct. 14, 2014,
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120584/#review68403
---
Ship it!
Sounds sensible.
however, can someone try plasma
On Ott. 14, 2014, 4:36 p.m., Marco Martin wrote:
Sounds sensible.
however, can someone try plasma without this patch and with the Qt patch:
https://codereview.qt-project.org/#/c/97050/
this one may be a workaround for the qt xcb problem adressed in the above,
but i'm not 100%
On Tue, Oct 14, 2014 at 6:51 AM, Àlex Fiestas wrote:
On Tuesday 14 October 2014 10:43:42 Martin Klapetek wrote:
I'd like to change this for Plasma panels to not have any resistance or
very minimal one, basically get it into a state that slamming the mouse
against a screen edge will show
On Oct. 13, 2014, 1:35 p.m., Marco Martin wrote:
src/quickaddons/managedtexturenode.h, line 52
https://git.reviewboard.kde.org/r/120550/diff/2/?file=318205#file318205line52
even if will always remain just this member, just to me sure, it should
be in a dpointer
Aleix Pol
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120564/#review68417
---
Ship it!
Indeed, well spotted.
Can you request a developer
On Monday 13 October 2014, Marco Martin wrote:
I need approval from Marco and other David.
after a quick chat with David E this morning, I would revert that patch
(and then remove the plugin in plasma-workspace master)
*but* this only if there will be a 5.3.1 (there should be a fix in
71 matches
Mail list logo
