https://bugs.kde.org/show_bug.cgi?id=378445
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
CC|
https://bugs.kde.org/show_bug.cgi?id=378445
r...@alum.mit.edu changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
--- Comment #18 from r...@alum.mi
https://bugs.kde.org/show_bug.cgi?id=378445
Justin Zobel changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #16 from r...@alum.mit.edu ---
Happened again in charge_state_changed.
This *may* have been at the time my laptop reached full charge but I have no
logs.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #15 from r...@alum.mit.edu ---
And another one, involving chargePercentChanged. The laptop had been on AC for
an extended period of time prior, and was likely at 100% charged, but that
doesn't mean that ACPI can't report changes.
Installing
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #14 from r...@alum.mit.edu ---
Happened again:
#0 0x7ff984e2d13b in __lll_lock_wait_private () from /lib64/libc.so.6
#1 0x7ff984db262a in malloc () from /lib64/libc.so.6
#2 0x7ff985170e38 in operator new(unsigned long) () from
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #13 from r...@alum.mit.edu ---
That's not likely what happened here; this most often happens overnight when I
had shut the laptop's lid, and it's not right after I shut it either (I have my
lid set to lock when shut, not suspend).
I wasn't a
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #12 from Martin Gräßlin ---
Assuming the signal handler is the reason the steps to reproduce are:
Let screen lock through idle timeout and during grace period lock the screen
through shortcut
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #11 from Martin Gräßlin ---
In the case of sigusr1 it could happen that memory gets allocated from the
signal handler.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #10 from r...@alum.mit.edu ---
Note that frame 5 is a signal handler, so it's hardly surprising that frame 4
and frame 7 are unrelated.
I don't know this code, but it sure looks to me like something (in the second
trace, isValidBusName; in t
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #9 from Martin Gräßlin ---
or another explanation could be memory corruption or even defect RAM.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=378445
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=378445
--- Comment #7 from r...@alum.mit.edu ---
Still happens with kscreenlocker (and powerdevil) 5.9.4.
It's rare, so I can't reproduce it reliably. And I don't have the debuginfo
packages -- my normal source for KDE packages doesn't have the debuginfo
pack
https://bugs.kde.org/show_bug.cgi?id=378445
Martin Gräßlin changed:
What|Removed |Added
Status|NEEDSINFO |UNCONFIRMED
Resolution|FIXED
14 matches
Mail list logo