Summary: | konsole flashes for attention on session restore | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Szokovacs Robert <szo> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | adaptee, thijs22nospam, thomas.luebking |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Screenshot immediately after login
After clicking on shells 5-7 |
Description
Szokovacs Robert
2012-02-07 19:55:08 UTC
Does something similar happen to other programs? If not, this is likely a Konsole issue, not a Taskbar issue. Looks like it's konsole specific. Please reassign, if you can! Could you provide a screenshot? It would make it easier to tell exactly what you are referring to. Created attachment 68644 [details]
Screenshot immediately after login
Note that the taskmanager shows 7 konsoles, but only 1-4 are on the current desktop, 5-7 are on the second one. 5-7 have a blue, flashing border, which is used to demand attention if something happens in a window.
Created attachment 68645 [details]
After clicking on shells 5-7
After clicking on shells 5-7, acknowledging their attention request, everything goes back to normal
Thanks for the screenshot. That really helps clarifying the problems. So this report contains two (related) problems: 1). taksbar contains entries for Konsole windows on other virtual desktops 2). the flashing border for some Konsole entries I'm pretty sure the first problem is out of the control of Konsole. As for the second problem, it is also unlikely a problem of Konsole. AFAIK, the only way for Konsole to mark taskbar entry for attention is using its monitoring feature together with notification. But when you just login, the monitoring feature is always disabled by default. So that flashing border is unlikely caused by Konsole itself. Actually, I think this report looks quite similar to bug 290392, which has been fixed a few days ago. And I failed to reproduce the reported problem using kde-workspace built from git repo yesterday. @Thomas, do you think this is a duplicate? Yes, this comment: https://bugs.kde.org/show_bug.cgi?id=290392#c15 describes my situation exactly too. *** This bug has been marked as a duplicate of bug 290392 *** |