[kopete-bugs] [Bug 165819] New: Generic error message when connecting using Jabber with an empty resource name

[Mathieu Bonnet]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=165819         
           Summary: Generic error message when connecting using Jabber with
                    an empty resource name
           Product: kopete
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kopete-bugs kde org
        ReportedBy: mathieu.bonnet riverside-idealism org


Version:            (using KDE 3.5.8)
Installed from:    Gentoo Packages

Hi,

When configuring Kopete for my Jabber accounts, I set an empty resource name (just felt like it, as I connect only from home, and prefer to avoid publishing information which could lead to identifying my software/system -or where I am just now).

But when connecting, I got the generic «There was an error authenticating with the server: Login failed with unknown reason».

As I was migrating from Psi (I need other protocols, and prefer not to use gateways), I just didn't think it would be a problem with the empty resource name (I used an empty resource name with Psi, without any problem... and now that I check the resource name, when connected, it generates a random number, to use as the resource name), and spent some time, before understanding where the problem was coming from.


When the resource name is empty, Kopete should warn the user about it (a simple «ok» dialog, after having saved the other data, just in case the user is in a hurry, and to avoid any problem if something crashes), and generate a random resource name (and tell the user Kopete did, and show it in the field, for information), or reset it to «Kopete», although people deleting the default resource name, probably wish to avoid any obvious fingerprinting of their software/system, and just didn't think of another name.


Or maybe the resource name is optional, and it is Kopete, which is failing to support it, and not the server? I guess people who remove the resource name, probably don't need one, whether they know what it is used for or not. In this case, Kopete should just support the empty resource name.


Well, of course, this is a pretty minor problem. A specific error message, when connecting, would be quite enough.


Thanks to everyone who will work on this.