Deluge
Opened 14 years ago
Closed 14 years ago
#1151 closed bug
console ui unable to automatically connect
| Reported by: | quite | Owned by: | |
|---|---|---|---|
| Priority: | trivial | Milestone: | |
| Component: | Console UI | Version: | 1.2.1 |
| Keywords: | Cc: |
Description
When starting up console ui, it fails to connect to the deluged (on localhost, running as a different user). I assumed I had to put the user:pass: in the auth file, but it seems I was wrong. Perhaps that file is only for setting up access to the daemon? Anyhow, it does not work. Moreover, the gtk ui does connect successfully using the same setup, so is the real issue that console ui does not care about the hostlist.conf?
Maybe this is a feature request, or a bug. I did not read the source very well now.
Probably the same issue here:
[ERROR ] 13:38:58 client:375 RPCError Message Received!
--------------------------------------------------------------------------------
RPCRequest: daemon.login(localclient, 8ce5af6592d4043af256be0ec3ffda531378d6cf)
--------------------------------------------------------------------------------
File "/usr/lib/pymodules/python2.6/deluge/core/rpcserver.py", line 245, in dispatch
ret = component.get("AuthManager").authorize(*args, **kwargs)
File "/usr/lib/pymodules/python2.6/deluge/core/authmanager.py", line 93, in authorize
raise BadLoginError("Password does not match")
BadLoginError: Password does not match
Change History (3)
comment:1 Changed 14 years ago by quite
comment:2 Changed 14 years ago by Cas
- Priority changed from major to trivial
- Status changed from new to pending
is this actually still an issue as i can connect to my localhost deluged as a different user without needing to use connect command.
comment:3 Changed 14 years ago by trac-robot
- Status changed from pending to closed
This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.
(ah, yes, issuing the command "connect localhost user pass" does work)