Bug 302194 - Skype 4.0: systray icon keeps indicating new chat message event although message has been read from kopete
Summary: Skype 4.0: systray icon keeps indicating new chat message event although mess...
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Skype Plugin (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-19 15:47 UTC by revinary
Modified: 2023-02-01 05:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description revinary 2012-06-19 15:47:48 UTC
When a message is received from a Skype contact (no existing chat window for that contact) the Skype systray icon indicates the event.
After opening the message with Kopete, the systray icon does not change back to normal (i.e. dicard event as read).
Checkbox "Mark as read" in account configuration dialog is set.
Skype is set to disable events for any incoming message events.

The Button "Disable Skype notifications and set up English language in Skype client"
breaks Skype's config.xml preventing Skype to start.

Kopete Version is 1.2.3 on KDE 4.8.4

Reproducible: Always

Steps to Reproduce:
1. Receive initial Skype chat message
2. Read message using Kopete 
Actual Results:  
Skype continues to indicate event until it message is marked as read using Skype.

Expected Results:  
Skype systray icon should go back to normal (i.e. green, no exclamation mark)

I realize Skype 4.0 for Linux is brand new and not officially supported, yet.
Comment 1 Lamarque V. Souza 2012-06-21 16:43:24 UTC
Well, here Skype 4.0's systray icon goes back to normal when I read messages from Kopete. OBS: I set the Skype's icon to hidden in the systray plasmoid.
Comment 2 michele mazza 2013-01-28 11:33:22 UTC
The problem is still present on Kopete 1.3.5, KDE 4.9.5
Comment 3 Andrew Crouthamel 2018-11-09 01:06:10 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-20 04:09:53 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2023-01-02 02:04:31 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-17 05:14:56 UTC
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
mark the bug 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!
Comment 7 Bug Janitor Service 2023-02-01 05:04:33 UTC
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!