Bug 656071 - Password-protected mt-daapd shares inaccessible from Rhythmbox
Summary: Password-protected mt-daapd shares inaccessible from Rhythmbox
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-23 00:40 UTC by Bill Kvasnikoff
Modified: 2011-06-28 10:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 476388
Environment:
Last Closed: 2011-06-28 10:27:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
rhythmbox log requested (1.59 KB, application/octet-stream)
2010-11-23 00:40 UTC, Bill Kvasnikoff
no flags Details
wireshark of tcp conversation (931 bytes, text/plain)
2010-11-23 00:44 UTC, Bill Kvasnikoff
no flags Details

Description Bill Kvasnikoff 2010-11-23 00:40:28 UTC
Created attachment 462190 [details]
rhythmbox log requested

This is occurring on a fedora 13 x64 machine connecting to a fedora 13 x86 machine.

Without password option daap connection works.

I've attached rhythmbox log (the relevant portion).

I'm also going to attach the tcp stream text from captured via wireshark.


+++ This bug was initially created as a clone of Bug #476388 +++

Description of problem:
Rhythmbox (and Exaile) is unable to connect to a password-protected DAAP share served from Firefly, a.k.a. mt-daapd in Fedora. It doesn't ask for a password. On the other hand, Banshee and iTunes have any problem connecting.

Version-Release number of selected component (if applicable):
banshee-1.4.1-1.fc10.x86_64
rhythmbox-0.11.6-17.r6096.fc10.x86_64
mt-daapd-0.2.4.2-4.fc10.x86_64
exaile-0.2.14-1.fc10.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Configure mt-daapd with a password protecting the music.
2. Attempt to play music with Rhythmbox.
  
Actual results:
No password prompt. No media found.

Expected results:
Prompted for password, media retrieved.

--- Additional comment from bnocera on 2008-12-18 04:14:24 EST ---

Please attach the output of "rhythmbox -d daap" to this bug.

--- Additional comment from theholyettlz on 2008-12-18 08:02:57 EST ---

Created attachment 327321 [details]
Output of rhythmbox -d daap

--- Additional comment from fedora-triage-list on 2009-11-18 05:27:52 EST ---


This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from fedora-triage-list on 2009-12-18 02:17:13 EST ---


Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 1 Bill Kvasnikoff 2010-11-23 00:44:05 UTC
Created attachment 462191 [details]
wireshark of tcp conversation

Comment 2 Bug Zapper 2011-05-30 13:31:58 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2011-06-28 10:27:05 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.