[plasmashell] [Bug 399758] Panel not updated after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=399758 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399758] Panel not updated after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=399758 Andrew Crouthamel changed: What|Removed |Added Keywords||triaged --- Comment #2 from Andrew Crouthamel --- 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 set the bug status 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.
[plasmashell] [Bug 399758] Panel not updated after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=399758 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- I can't find the bug (sorry), but I'm almost positive this is a known issue that was fixed with a newer version of the proprietary NVIDIA driver. Can you update to the latest one and let me know if it reproduces? Thanks! -- You are receiving this mail because: You are watching all bug changes.
