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 672652 - Enable UPnP on Windows result in crash
Enable UPnP on Windows result in crash
Status: RESOLVED DUPLICATE of bug 672744
Product: banshee
Classification: Other
Component: Other Extensions
2.4.0
Other Windows
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-22 20:45 UTC by Trond Andersen
Modified: 2012-05-19 18:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Log file (2.27 KB, application/octet-stream)
2012-03-22 20:45 UTC, Trond Andersen 		Details
Banshee log file (5.52 KB, text/x-log)
2012-03-29 05:52 UTC, Ely Lizaire 		Details

Description Trond Andersen 2012-03-22 20:45:35 UTC 
Created attachment 210381 [details]
Log file

Steps to reproduce:
- Download last Banshee version for Windows and install
- Start Banshee and enable the UPnP extension from preferences

Result: Banshee crashes

Restarting Banshee result eventually in a new crash.
Comment 1 Ely Lizaire 2012-03-29 05:52:11 UTC 
Created attachment 210844 [details]
Banshee log file
Comment 2 Ely Lizaire 2012-03-29 05:52:57 UTC 
I reproduced it on linux.
Comment 3 Richard Foster 2012-04-11 23:25:04 UTC 
Can confirm that I can reproduce this on linux too.

Running:
Linux LiquidBuntu 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Banshee 2.4 (2.4.0) http://banshee.fm
Copyright 2005-2012 Novell, Inc. and Contributors.


I have piped the terminal output and uploaded this to the ubuntu launchpad tracker. 
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/974743
Comment 4 Bertrand Lorentz 2012-05-19 18:46:22 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version.

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