Bug 253180 - kopete starts not accepting accents in the firsts tab, when two or more are open
Summary: kopete starts not accepting accents in the firsts tab, when two or more are open
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-04 01:04 UTC by Alessandro Ghersi
Modified: 2023-01-11 05:19 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alessandro Ghersi 2010-10-04 01:04:56 UTC
Version:           unspecified
OS:                Linux

Bug reported here:
https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/383900

I've installed Kopete 0.70.4 under Ubuntu Jaunty, using the KDE 4.2.4 Kubuntu repository, and I configured two accounts: one for MSN and another for Jabber. Next, I changed the options so all the chats get grouped in one window, with tabs.

When I open only one conversation with one of my contacts, either from MSN or Jabber, the accents are displayed correctly. But if someone else talks to me or I open another conversation, the accents in the firts tab will stop displaying correcty. Instead of an "á", I'll get and "´a". The same thing happens with three or more tabs.

This is extremely irritating because it basically make Kopete useless and unusable to me.

Description: Ubuntu 9.04
Release: 9.04
Qt: 4.5.0
KDE: 4.2.4 (KDE 4.2.4)
Kopete: 0.70.4

With version 0.70.90, under Gnome, the accents are displayed correctly, but not with MSN Messenger contacts.

Reproducible: Didn't try
Comment 1 Andrew Crouthamel 2018-11-05 03:06:52 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 2 Andrew Crouthamel 2018-11-16 05:33:08 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?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-12 01:56:06 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 4 Bug Janitor Service 2022-12-27 05:21:40 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 5 Bug Janitor Service 2023-01-11 05:19:37 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!