[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

2021-01-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=379521

spa...@modanese.net changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from spa...@modanese.net ---
I haven't had the problem for a while now, so I suppose it's been fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

2021-01-03 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=379521

--- Comment #7 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 bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

2020-12-19 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=379521

Justin Zobel  changed:

   What|Removed |Added

 CC||justin.zo...@gmail.com
 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #6 from Justin Zobel  ---
Is this now resolved upstream?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

2017-06-02 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=379521

--- Comment #5 from Christoph Feck  ---
It is related to QQuickWindow (from QtQuick), which is only used by a minority
of applications.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

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

--- Comment #4 from spa...@modanese.net ---
@Christoph Feck
So should I go and file a bug on the Qt tracker?

Right now it happens only with kscreenlocker though. I'll keep an eye open, see
if any other Qt programs show similar behavior.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

2017-05-09 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=379521

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|BACKTRACE   |---

--- Comment #3 from Christoph Feck  ---
Thanks for the update; it looks like a Qt issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

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

--- Comment #2 from spa...@modanese.net ---
Created attachment 105362
  --> https://bugs.kde.org/attachment.cgi?id=105362=edit
GDB backtrace (with symbols)

Ah, I recompiled kscreenlocker with the debug symbols, but forgot about Qt :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive

2017-05-05 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=379521

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Martin Gräßlin  ---
Unfortunately the backtrace is lacking debug symbols. If you are able to
reproduce please install the debug packages and attach a new backtrace. Without
the debug symbols we do not see where it crashes.

-- 
You are receiving this mail because:
You are watching all bug changes.