After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 515999 - Does't work with password-protected shares against mt-daapd
Does't work with password-protected shares against mt-daapd
Status: RESOLVED DUPLICATE of bug 501389
Product: rhythmbox
Classification: Other
Component: DAAP
0.11.x
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-12 12:32 UTC by Anton Lundin
Modified: 2008-07-04 21:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Anton Lundin 2008-02-12 12:32:12 UTC
Please describe the problem:
The connect thread hangs and does't get the answer from mt-daapd.



Steps to reproduce:
1. start mt-daapd with password-protect
2. start rhythmbox with -D daap
3. try to connect and you se it hang


Actual results:
Its unable to login

Expected results:


Does this happen every time?
yes

Other information:
(13:22:08) [0x80db408] [rb_daap_connection_connect] rb-daap-connection.c:1310: Creating new DAAP connection to xxx.xxx.xxx.xxx:3689
(13:22:08) [0x80db408] [rb_daap_connection_do_something] rb-daap-connection.c:1489: Doing something for state: 0
(13:22:08) [0x80db408] [rb_daap_connection_do_something] rb-daap-connection.c:1495: Getting DAAP server info
(13:22:08) [0x80db408] [http_get] rb-daap-connection.c:677: Queued message for http://xxx.xxx.xxx.xxx:3689//server-info
(13:22:08) [0x80db408] [actual_http_response_handler] rb-daap-connection.c:451: Received response from http://xxx.xxx.xxx.xxx:3689/server-info: 200, OK

(13:22:08) [0x80db408] [rb_daap_connection_state_done] rb-daap-connection.c:1432: Transitioning to next state from 0
(13:22:08) [0x80db408] [emit_progress_idle] rb-daap-connection.c:705: Emitting progress
(13:22:08) [0x80db408] [connection_connecting_cb] rb-daap-source.c:418: DAAP connection status: 1/1.000000
(13:22:08) [0x80db408] [rb_daap_connection_do_something] rb-daap-connection.c:1489: Doing something for state: 1
(13:22:08) [0x80db408] [rb_daap_connection_do_something] rb-daap-connection.c:1530: Logging into DAAP server
(13:22:08) [0x80db408] [http_get] rb-daap-connection.c:677: Queued message for http://xxx.xxx.xxx.xxx:3689//login


And caught by wireshark:

GET /server-info HTTP/1.1
Host: xxx.xxx.xxx.xxx:3689
Client-DAAP-Version: 3.0
Accept-Language: en-us, en;q=5.0
Accept-Encoding: gzip
Client-DAAP-Access-Index: 2

HTTP/1.1 200 OK
Content-Length: 136
Content-Type: application/x-dmap-tagged
DAAP-Server: mt-daapd/0.2.4.1
Accept-Ranges: bytes
Date: Tue, 12 Feb 2008 12:22:08 GMT

msrv....mstt........mpro........apro........minm....gandhimsau.....mstm........msex.....msix.....msbr.....msqy.....msup.....msdc........GET /login HTTP/1.1

Host: xxx.xxx.xxx.xxx:3689
Client-DAAP-Version: 3.0
Accept-Language: en-us, en;q=5.0
Accept-Encoding: gzip
Client-DAAP-Access-Index: 2

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Basic realm="webserver"
Date: Tue, 12 Feb 2008 12:22:08 GMT

<HTML>
<TITLE>401 Unauthorized</TITLE>
<BODY>
<H1>Unauthorized</H1>
Error 401
<hr>
<i>mt-daapd: 0.2.4.1
<br></i></BODY>
</HTML>
Comment 1 Guillaume Desmottes 2008-07-04 21:26:22 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 501389 ***