When Konversation is started during boot (using standard KDE session restore capability), it fails to connect to any servers giving an "unknown error", even after endlessly retrying. Reproducible: Sometimes Steps to Reproduce: 1. Start Konversation 2. Configure servers 3. Reboot Actual Results: Konversation reports loops such as this: [Info] Looking for server sendak.freenode.net (port 6697)... [Info] Server found, connecting... [Error] Connection to server sendak.freenode.net (port 6697) lost: Unknown error. [Info] Trying to reconnect to sendak.freenode.net (port 6697) in 10 seconds. Or this: [Info] Trying to reconnect to eu.globalgamers.net (port 6660) in 10 seconds. [Info] Looking for server eu.globalgamers.net (port 6660)... [Error] Connection to server eu.globalgamers.net (port 6660) lost: Unknown error. Expected Results: Connecting should work. If Konversation is manually turned off and then started again, it works fine every time until the next reboot. This happens almost every boot, on both openSUSE 13.2 and openSUSE Tumbleweed, using Plasma 5. Since it feels like a race condition, it might be relevant that my PC uses an SSD for /. Perhaps Konversation gets started before NetworkManager, or such?
Hi, I have the exact same problem, using opensuse 13.2 and kde4. I also have an SSD but I wait until network connectivity is up before I log in (otherwise systemd troubles). Then again wireless network only becomes user accessible after I put in my kwallet password, so it might be related after all.
Hm, I use KWallet as well, but not for networking (in my case it's wired). Also relevant to the bug is that sometimes only the first IRC server fails to connect, whereas the second one works fine almost all the time. It might be that the second server connection process starts just late enough for the network to be up at the time.
I forgot to mention this systemd delay is caused somehow when using autofs, see https://bugzilla.opensuse.org/show_bug.cgi?id=905639 for more info (should be fixed in patch of 4th dec). You may have a similar issue
No, I don't use autofs. And my system has no freezes or delays during boot, it's quite speedy.
I can reproduce this bug here 100% of the time. I'm using networkmanager and it takes a few seconds after login to get a connection, but even after the connection is established, konversation failes to connect to the servers with an "Unknown error". The ownCloud sync client seems to have the same bug somehow.
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!
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!
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!