Bug 135616 - kopete connect to same IRC only us root
Summary: kopete connect to same IRC only us root
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: IRC Plugin (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-14 11:31 UTC by Aidar
Modified: 2023-01-07 05:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aidar 2006-10-14 11:33:43 UTC
Version:           0.12.3 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
Compiler:          gcc-3.4 -march=athlon-xp -O2 -pipe -fomit-frame-pointer
OS:                Linux

can not connect to same irc via kopete
Kopete can connect to Yahoo and other protocols.
Other IM (like Ksirc, xchat) connecting succes, but kopete cannot connect to IRC (to other irc server conecting succeful)

Translation: Kirc error - Analysis error:
You are now labeled connected
You are now labeled disconnected. 

However, I can connect to this irc, if I'm using kopete as root
Comment 1 Philip Rodrigues 2006-10-15 13:58:19 UTC
Sounds like a configuration problem. Try creating a new user. Run kopete as that user. Does it connect to irc?
Comment 2 Aidar 2006-10-16 08:42:45 UTC
I create a new user, did all as you say, but is dont connect to this server.

however, i can connect to other irc servers as all users.
this is a bug of 2003 year - http://forums.gentoo.org/viewtopic-t-468341-start-0-postdays-0-postorder-asc-highlight-kopete+root.html
Comment 3 Aidar 2006-10-17 14:51:21 UTC
Now i try to run kopete with --nofork option, and it connect! I dont understand this...
Comment 4 Andrew Crouthamel 2018-11-02 04:16:35 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 5 Andrew Crouthamel 2018-11-16 02:44:27 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 6 Justin Zobel 2022-12-08 00:00:28 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 7 Bug Janitor Service 2022-12-23 05:21:22 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 8 Bug Janitor Service 2023-01-07 05:24:03 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!