#1824 closed bug (Fixed)
False (?) authentication failure message
| Reported by: | shnurapet | Owned by: | s0undt3ch |
|---|---|---|---|
| Priority: | minor | Milestone: | Future |
| Component: | GTK UI | Version: | master |
| Keywords: | ConnectionManager | Cc: |
Description
I have two separate daemons in WLAN. When double-clicking on a daemon in the Connections Manager while being connected (and viewing) to another one, a message shows up saying:
Failed To Authenticate 'ConnectionManager' object has no attribute 'connection_manager'
It works the second time I double-click (or when I disconnect from the daemon being viewed first).
This is git master on Fedora 14 x86_64 as of today.
Attachments (2)
Change History (12)
by , 14 years ago
| Attachment: | Снимок-1.png added |
|---|
follow-up: 7 comment:1 by , 14 years ago
follow-up: 4 comment:2 by , 14 years ago
| Keywords: | ConnectionManager added |
|---|---|
| Owner: | set to |
| Status: | new → accepted |
Is this running current master? Also could you re-attach the screenshot in englisn locale? Trac is now allowing me to download it.
comment:4 by , 14 years ago
Replying to s0undt3ch:
Is this running current master? Also could you re-attach the screenshot in englisn locale? Trac is now allowing me to download it.
Yes, of course. Sorry for that. This is master as of April 30th (the latest at the moment of filing this ticket).
by , 14 years ago
comment:5 by , 14 years ago
Ok. So this happens when connected to a daemon and trying to connect to another one. I'll investigate.
follow-up: 8 comment:7 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Sorry for reopening. This one still occurs:
Replying to shnurapet:
Also an empty message "Failed To Authenticate" is shown if clicked "Connect" to a daemon when it is not running.
Though it connects to the daemon and all I gotta do it to click that message away.
comment:8 by , 14 years ago
| Status: | reopened → accepted |
|---|
Replying to shnurapet:
Sorry for reopening. This one still occurs:
Replying to shnurapet:
Also an empty message "Failed To Authenticate" is shown if clicked "Connect" to a daemon when it is not running.
Though it connects to the daemon and all I gotta do it to click that message away.
Weird. You're only allowed to connect to non-running daemons if it's entry in the connection manager is for a localhost daemon.
What's happening on my end is that I'm allowed to click connect for such host entries, but all I'm getting is a connection refused, which is not what's intended, ie, if it's a localhost entry, and it's not running, start it and connect to it. If it's running, just connect to it.
So, although I'm unable to reproduce your issue with a clean config, part of what the connection manager should be doin' it's not. So, I'll keep this open until I fix that. Maybe then I'm able to reproduce your issue.
comment:10 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
Please try master as of a7bd9531698ae47b48acbcefb60c26f85e397dc6.
Re-open if still happening please.
Also an empty message "Failed To Authenticate" is shown if clicked "Connect" to a daemon when it is not running.