[Konversation-devel] [konversation] [Bug 351136] New: Connection to server lost: unknown error on autostart

[Dainius Masiliūnas]

https://bugs.kde.org/show_bug.cgi?id=351136

            Bug ID: 351136
           Summary: Connection to server lost: unknown error on autostart
           Product: konversation
           Version: 1.6
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: konversation-devel at kde.org
          Reporter: pastas4 at gmail.com

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?

-- 
You are receiving this mail because:
You are the assignee for the bug.