https://bugs.kde.org/show_bug.cgi?id=391139
Zakhar changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=391139
--- Comment #7 from Zakhar ---
This was an issue with laptop-mode-tools powerdevil was not at fualt here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391139
--- Comment #6 from Zakhar ---
Created attachment 111068
--> https://bugs.kde.org/attachment.cgi?id=111068&action=edit
monitor log from dbus-monitor
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391139
Christoph Feck changed:
What|Removed |Added
Status|CONFIRMED |UNCONFIRMED
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=391139
--- Comment #4 from Kai Uwe Broulik ---
Easiest would be running "dbus-monitor" on console or using "bustle" which lets
you record DBus traffic.
I could imagine two scenarios:
1.) UPower (and/or the kernel driver/or ACPI) taking a while to realize
2.)
https://bugs.kde.org/show_bug.cgi?id=391139
--- Comment #3 from Zakhar ---
I will do it if Im told what commands need issuing to disclose relevant data.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391139
Kai Uwe Broulik changed:
What|Removed |Added
CC||k...@privat.broulik.de
--- Comment #2 from Ka
https://bugs.kde.org/show_bug.cgi?id=391139
Zakhar changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=391139
--- Comment #1 from Zakhar ---
After further testing I verified connecting PC to AC yields notifications far
quicker than disconnecting.
--
You are receiving this mail because:
You are watching all bug changes.
