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 665148 - Banshee 2.3.1 update available fails
Banshee 2.3.1 update available fails
Status: RESOLVED WONTFIX
Product: banshee
Classification: Other
Component: User Interface
2.2.0
Other Windows
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
gnome[unmaintained]
: 672118 690794 702420 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-11-29 18:28 UTC by harris.jimmy
Modified: 2020-03-17 09:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description harris.jimmy 2011-11-29 18:28:06 UTC
Hello there,

I've newly installed Banshee 2.2.0 on Windows XP SP3 and found that the Banshee 2.3.1 update available fails. 

Both on opening Banshee and Check for Updates the automatic update to Banshee 2.3.1 fails as follows:

Opening Banshee
------------------------
1. Double-click Banshee.exe
2. Prompted Banshee update available "A new version of Banshee (2.3.1) is available. Do you want to update?"

3. Click Yes on the prompt.
4. Downloading Banshee-2.3.1.msi fails dialogue box appears in the Source List.
5. Prompted Update download failed "The download failed. Please try again later."
6. Click OK

Check for Updates
------------------------
1. Go to Help > Check for Updates
2. Prompted Banshee update available "A new version of Banshee (2.3.1) is available. Do you want to update?"

3. Click Yes on the prompt.
4. Downloading Banshee-2.3.1.msi fails dialogue box appears in the Source List.
5. Prompted Update download failed "The download failed. Please try again later."
6. Click OK

Getting Event ID 5000 and 1000 in the event log as follow:

Event ID 5000 
------------------
Event Type:	Error
Event Source:	.NET Runtime 2.0 Error Reporting
Event Category:	None
Event ID:	5000
Date:		11/29/2011
Time:		13:10
User:		N/A
Computer:	L-101266-P11
Description:
EventType clr20r3, P1 nereid.exe, P2 2.2.0.0, P3 4e790acd, P4 banshee.thickclient, P5 0.0.0.0, P6 4e790acb, P7 1ad, P8 1c, P9 system.typeinitialization, P10 NIL.

Event ID 1000 
------------------
Event Type:	Error
Event Source:	.NET Runtime 2.0 Error Reporting
Event Category:	None
Event ID:	1000
Date:		11/29/2011
Time:		11:01
User:		N/A
Computer:	L-101266-P11
Description:
Faulting application nereid.exe, version 2.2.0.0, stamp 4e790acd, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x084e5f43.

Hope this helps :)

Regards,

Jimmy (pak33m)
Comment 1 Bertrand Lorentz 2011-12-03 11:24:38 UTC
Thank you for your bug report.

The problem is caused by the way the update system currently works :
It checks the latest version available by looking at our doap file :
http://ftp.gnome.org/pub/GNOME/sources/banshee/banshee.doap

But that file only contains information about source releases. As we haven't published a Windows installer for version 2.3.1 or 2.3.2, the update thinks there's a new version available, but then fails as it can't find it on the server.

We definitely need to improve that.
Comment 2 Bertrand Lorentz 2012-03-15 17:47:44 UTC
*** Bug 672118 has been marked as a duplicate of this bug. ***
Comment 3 Bertrand Lorentz 2012-12-30 18:46:02 UTC
*** Bug 690794 has been marked as a duplicate of this bug. ***
Comment 4 Bertrand Lorentz 2013-06-17 05:43:18 UTC
*** Bug 702420 has been marked as a duplicate of this bug. ***
Comment 5 Ján Sokoly 2014-05-16 13:56:32 UTC
Bertrand, what do you think is the best place to check for new releases instead of .doap? Maybe listing the ftp.gnome.org/pub/GNOME/binaries/win32/banshee/ and finding the latest file?
Comment 6 André Klapper 2020-03-17 09:26:38 UTC
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project
to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the
responsibility for active development again.
See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.