Bug 365466 - one of 3 nodes ins printed in red colour
Summary: one of 3 nodes ins printed in red colour
Status: RESOLVED INTENTIONAL
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.6
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-12 12:09 UTC by Toralf Förster
Modified: 2016-07-22 10:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (136.39 KB, image/png)
2016-07-12 12:09 UTC, Toralf Förster
Details
konversation screen shot (332.01 KB, image/png)
2016-07-22 08:18 UTC, Toralf Förster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster 2016-07-12 12:09:18 UTC
as seen in the attached screen shot.
If I click onto it, it will be black, but after a restart it is red again.

Reproducible: Always
Comment 1 Toralf Förster 2016-07-12 12:09:40 UTC
Created attachment 100034 [details]
screenshot
Comment 2 Eike Hein 2016-07-12 12:58:50 UTC
That means there's a highlight in the tab.
Comment 3 Toralf Förster 2016-07-12 13:10:05 UTC
"hackint" is the node - not a channel. it is always red. And never ever another node is red.
Comment 4 Toralf Förster 2016-07-22 08:18:48 UTC
Created attachment 100241 [details]
konversation screen shot

So if this is not a bug and will not be fixed - may i ask why that node is printed in red ?
A typical welcome message is attached
Comment 5 Eike Hein 2016-07-22 09:53:22 UTC
Because the messages contain your nickname "toralf". You can right-click the tab and disable notifications for it.
Comment 6 Toralf Förster 2016-07-22 10:02:03 UTC
(In reply to Eike Hein from comment #5)
> Because the messages contain your nickname "toralf". You can right-click the
> tab and disable notifications for it.

gah - that's the culprit - thx.

For *some* reasons during upgrade from 1.5.1 to 1.6 this settings was activated for the last node entry whereas for the first 2 nodes this settings was unchanged.

Either I made  a mistake or ... ?