https://bugs.kde.org/show_bug.cgi?id=347772
Vadym Krevs changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #76 from Vadym Krevs ---
Created attachment 168152
--> https://bugs.kde.org/attachment.cgi?id=168152&action=edit
qdbus-qt5 org.kde.KWin /KWin supportInformation for comment 75
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=347772
Vadym Krevs changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=347772
Vadym Krevs changed:
What|Removed |Added
CC||vkr...@yahoo.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=347772
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #73 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=347772
Fabian Vogt changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=347772
Thilo-Alexander Ginkel changed:
What|Removed |Added
CC||th...@ginkel.com
Resolution|FI
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
CC||stevenro...@gmail.com
--- Comment #70 from Nate G
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Version Fixed In|5.18.7
https://bugs.kde.org/show_bug.cgi?id=347772
cantf...@gmail.com changed:
What|Removed |Added
CC||cantf...@gmail.com
Status|RESOL
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
Version Fixed In|5.21|5.18.7
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma
https://bugs.kde.org/show_bug.cgi?id=347772
David Edmundson changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest Commit|https://commits.k
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #65 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/556
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #64 from anomaly256 ---
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347772
Bug Janitor Service changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
--- Comment #63 from Bug Janitor
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #62 from Fabian Vogt ---
(In reply to Fabian Vogt from comment #61)
> I can reproduce kscreenlocker_greet taking unreasonable amounts of CPU (but
> not 100%) when the main area is faded out for basically ever.
Surprisingly this appears to b
https://bugs.kde.org/show_bug.cgi?id=347772
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--- Comment #61 from Fabian
https://bugs.kde.org/show_bug.cgi?id=347772
RR changed:
What|Removed |Added
CC||raghu.nos...@gmail.com
--- Comment #60 from RR ---
Defini
https://bugs.kde.org/show_bug.cgi?id=347772
Maximiliano Bertacchini changed:
What|Removed |Added
CC||maxibe...@gmail.com
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #59 from anomaly256 ---
I decided to test on kde neon testing, with libkscreenlocker5
5.19.4+p20.04+git20200818.2051-0 and kscreenlocker_greet appears to actually be
behaving here. There's a separate issue with plasmashell chewing 200% cpu
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #58 from anomaly256 ---
(In reply to Nate Graham from comment #55)
> It may not still even be a thing; Plasma 5.14.5 is almost two years old at
> this point so there's a chance that it's been fixed in a newer version which
> you don't have.
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #57 from talent...@hotmail.com ---
Problem still exists in plasma 5.19.4
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #56 from anomaly256 ---
(In reply to Nate Graham from comment #55)
> It may not still even be a thing; Plasma 5.14.5 is almost two years old at
> this point so there's a chance that it's been fixed in a newer version which
> you don't have.
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #55 from Nate Graham ---
It may not still even be a thing; Plasma 5.14.5 is almost two years old at this
point so there's a chance that it's been fixed in a newer version which you
don't have. You could switch to Debian Testing to give it a
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #54 from anomaly256 ---
nb: I see this on many hosts not just ones using nvidia drivers. To be honest
I don't believe the earlier assertion that this original bug is specific to
nvidia is accurate and has likely been a red herring. Surely
https://bugs.kde.org/show_bug.cgi?id=347772
anomaly256 changed:
What|Removed |Added
CC||anomaly...@gmail.com
--- Comment #53 from anomaly2
https://bugs.kde.org/show_bug.cgi?id=347772
Txutxifel changed:
What|Removed |Added
CC||jesa...@gmail.com
--- Comment #52 from Txutxifel -
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #51 from Sergey ---
I don't know if it's related or not. but with recent updates (kscreen/locker
5.19.3, nvidia drivers 450.57) ctrl+alt+L does not show lock screen anymore,
instead it makes everything untouchable but still visible.
But as
https://bugs.kde.org/show_bug.cgi?id=347772
Jason D. Kelleher changed:
What|Removed |Added
CC||kelle...@grumpydude.com
--- Comment #50 fro
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #49 from Sergey ---
I tried to do same QSG_RENDER_LOOP=basic trick with kscreenlocker-5.18.5 but
after 2 days of testing it seems it doesn't work anymore.
stack trace looks pretty much the same, it stucks somewhere in nvidia libraries
on cr
https://bugs.kde.org/show_bug.cgi?id=347772
Stefano Forli changed:
What|Removed |Added
CC|ntro...@gmail.com |
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=347772
christian.rohm...@gmx.de changed:
What|Removed |Added
CC||christian.rohm...@gmx.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=347772
FeepingCreature changed:
What|Removed |Added
CC||default_357-l...@yahoo.de
--- Comment #48 fro
https://bugs.kde.org/show_bug.cgi?id=347772
Ales Seifert changed:
What|Removed |Added
CC||seif...@alesak.net
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #47 from Sergey ---
after some testing QSG_RENDER_LOOP=basic seems to be the perfect workaround.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #46 from Sergey ---
Created attachment 127682
--> https://bugs.kde.org/attachment.cgi?id=127682&action=edit
qdbus org.kde.KWin /KWin supportInformation
For me the problem is not about CPU but black screen after system resume from
stand-by
https://bugs.kde.org/show_bug.cgi?id=347772
Sergey changed:
What|Removed |Added
CC||rion...@gmail.com
--- Comment #45 from Sergey ---
5.1
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
Priority|NOR |VHI
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
CC||el...@seznam.cz
--- Comment #44 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
CC||talent...@hotmail.com
--- Comment #43 from Nate G
https://bugs.kde.org/show_bug.cgi?id=347772
Bernard Gray changed:
What|Removed |Added
CC||bernard.g...@gmail.com
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=347772
David Kredba changed:
What|Removed |Added
CC|nheghathivhis...@gmail.com |
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #42 from d...@newtech.fi ---
Same here using FC30.
Version: kscreenlocker-5.15.5-1.fc30.x86_64
Connected to it with strace and the time seems to be spent in a poll loop with
very short timeout.
[pid 24752] poll([{fd=5, events=POLLIN}, {fd=
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #41 from ricar...@um.es ---
I am seeing this while running plasma under Xvnc. kscreenlocker_greet is
wasting around 25% of a core.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347772
ricar...@um.es changed:
What|Removed |Added
CC||ricar...@um.es
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=347772
David Kredba changed:
What|Removed |Added
CC||nheghathivhis...@gmail.com
--- Comment #40 from
https://bugs.kde.org/show_bug.cgi?id=347772
fle...@users.sourceforge.net changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=347772
Alexander Potashev changed:
What|Removed |Added
CC||aspotas...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.12.7
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=347772
aux...@gmail.com changed:
What|Removed |Added
CC||aux...@gmail.com
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=347772
David Edmundson changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/ksc |https://commits.kde.org/ksc
https://bugs.kde.org/show_bug.cgi?id=347772
Jaroslav Safka changed:
What|Removed |Added
CC|xken...@seznam.cz |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=347772
David Edmundson changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=347772
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #36 from Gianni ---
(In reply to David Edmundson from comment #35)
> Compositor settings affect only the window manager. GL clients will still use
> GL.
> This setting affects only the clients (plasmashell / systemsettings /
> whatever)
>
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #35 from David Edmundson ---
>I don't know if this is the right place, but I'm interested in knowing what
>difference there is between setting XRender compositor and setting Rendering
>backend = software.
Compositor settings affect only t
https://bugs.kde.org/show_bug.cgi?id=347772
Gianni changed:
What|Removed |Added
Attachment #114379|0 |1
is obsolete||
--
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #34 from Gianni ---
Created attachment 114384
--> https://bugs.kde.org/attachment.cgi?id=114384&action=edit
gdb backtrace output of kscreenlocker_greet on intel GMA950 using OpenGL 2
compositor
gdb backtrace output of kscreenlocker_greet
https://bugs.kde.org/show_bug.cgi?id=347772
Gianni changed:
What|Removed |Added
Attachment #114342|0 |1
is obsolete||
--
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #32 from Gianni ---
(In reply to David Edmundson from comment #31)
> Another thing to try is typing "plasma renderer" into krunner
> from there you can select "Rendering backend = software"
>
> Changes will apply after session restart. I w
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #31 from David Edmundson ---
Another thing to try is typing "plasma renderer" into krunner
from there you can select "Rendering backend = software"
Changes will apply after session restart. I would like to hear back on how good
the perform
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #30 from Christoph Feck ---
You can force OpenGL 2.1 for intel 915+ by enabling ARB_occlusion_query and
ARB_fragment_shader in drirc.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #29 from Martin Flöser ---
I'm sorry but a GPU not providing at least OpenGL 2 does not fulfill the
hardware requirements of Plasma. Please consider using different hardware. I'm
not able to provide you any alternative from software side - e
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #28 from Gianni ---
Created attachment 114379
--> https://bugs.kde.org/attachment.cgi?id=114379&action=edit
gdb backtrace output of kscreenlocker_greet on intel GMA950
I ran gdb after entering via ssh to the machine and gave the bt comman
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #27 from Gianni ---
> You are using xrender compositing. This could indicate that your OpenGL
> drivers are broken. That would explain the high cpu usage.
I am indeed using xrender compositing because my graphic chip (Intel GMA950)
doesn't
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #26 from Martin Flöser ---
(In reply to Gianni from comment #25)
> Created attachment 114342 [details]
> qdbus org.kde.KWin /KWin supportInformation macmini mid 2007
You are using xrender compositing. This could indicate that your OpenGL dr
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #25 from Gianni ---
Created attachment 114342
--> https://bugs.kde.org/attachment.cgi?id=114342&action=edit
qdbus org.kde.KWin /KWin supportInformation macmini mid 2007
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=347772
Gianni changed:
What|Removed |Added
CC||gianni_2...@hotmail.it
--- Comment #24 from Gianni --
https://bugs.kde.org/show_bug.cgi?id=347772
Stefano Forli changed:
What|Removed |Added
CC||ntro...@gmail.com
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=347772
Cyril Chaboisseau changed:
What|Removed |Added
CC||chaboiss...@bigfoot.com
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=347772
Jakub Krajewski changed:
What|Removed |Added
CC||ja...@krajewski.org
--- Comment #22 from Jaku
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #21 from d...@newtech.fi ---
Here an extract of an strace of the bad screenlocker:
[pid 12126] futex(0x5651d612b36c, FUTEX_WAIT_PRIVATE, 459831, NULL
[pid 12251] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed
out)
[pid 122
https://bugs.kde.org/show_bug.cgi?id=347772
d...@newtech.fi changed:
What|Removed |Added
CC||d...@newtech.fi
--- Comment #20 from d...@newt
https://bugs.kde.org/show_bug.cgi?id=347772
ge...@gj.ee changed:
What|Removed |Added
CC||ge...@gj.ee
--- Comment #19 from ge...@gj.ee ---
C
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #18 from Martin Gräßlin ---
The resolution for this bug report is: install the Nvidia driver. As I wrote in
the previous comment: you have a different issue
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #17 from Ralf-Peter Rohbeck ---
As I understood it the resolution is "use a decent GPU."
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=347772
--- Comment #16 from Martin Gräßlin ---
(In reply to Ralf-Peter Rohbeck from comment #15)
> This makes the screen locker unusable on ARM systems without GPU driver,
> e.g. Banana Pi.
This bug report was about an NVIDIA driver not being installed. That
https://bugs.kde.org/show_bug.cgi?id=347772
Ralf-Peter Rohbeck changed:
What|Removed |Added
CC||rohb...@yahoo.com
--- Comment #15 from Ral
https://bugs.kde.org/show_bug.cgi?id=347772
Martin Gräßlin changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=347772
Martin Gräßlin changed:
What|Removed |Added
Component|lockscreen |general
Product|ksmserver
84 matches
Mail list logo
