Bug 365016 - it is impossible to enter the credentials for the jabber transport
Summary: it is impossible to enter the credentials for the jabber transport
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-02 19:49 UTC by Evgeeny
Modified: 2022-11-20 05:12 UTC (History)
1 user (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 Evgeeny 2016-07-02 19:49:51 UTC
I tried to register a service (transport mrim.jabber.ru) on jabber.ru but it does not work in kopete, because of the input field of username is not visible (and the password field overlaps the text label). It is impossible to specify a username.
Pictures: https://www.dropbox.com/sh/krur6n3v7k4rd2n/AABYRkYez3q894efjiOaXC8Ya?dl=0
(Russian Language)

Reproducible: Always

Steps to Reproduce:
1. Right click on the account jabber.ru and select "Service..."
2. Specify the server jabber.ru and click on "Request".
3. Click right button on "mrim.jabber.ru" and choose "Register".

Actual Results:  
Opens a window in which it is impossible to enter the username.

Expected Results:  
I need to enter a username and password for mrim.mail.ru.
Comment 1 Pali Rohár 2016-07-27 16:47:37 UTC
Sorry but linked pictures cannot be shown. In future attach all materials to bugzilla and not link to external services which can trash data...

Anyway, from your description it looks like a problem from bug 331705 which was fixed in Kopete version 1.9.0. Can you verify it?
Comment 2 Justin Zobel 2022-10-21 23:59:56 UTC
Thank you for reporting this bug 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 "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-11-05 05:08:43 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 4 Bug Janitor Service 2022-11-20 05:12:59 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!