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 732179 - Banshee crashe/ won't open after Podcast subscription
Banshee crashe/ won't open after Podcast subscription
Status: RESOLVED WONTFIX
Product: banshee
Classification: Other
Component: Podcasting
2.6.2
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2014-06-24 18:59 UTC by Chow Loong Jin
Modified: 2020-03-17 09:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Banshee debug log (11.50 KB, text/plain)
2014-06-24 18:59 UTC, Chow Loong Jin
Details

Description Chow Loong Jin 2014-06-24 18:59:23 UTC
Created attachment 279143 [details]
Banshee debug log

Originally reported at:
  https://bugs.launchpad.net/bugs/1333761

Hi, 

Already 3 times that I make a Clean / New install of Linux 17 X64, under Mate. The first time that i want to start Banshee; it works. Then I subscribe anbd download some podcast; then i stop Banshee and when I want to start it again, it never can be open. In fact it show me a Windows and directly close it, or just open a Windows that stay blank .
For your info it works when i use it shell: sudo banshee.
I tried all solutions i found on Google: still crashing.
File joined for the result of cd ~; banshee --debug 2>&1 | tee banshee-debug-log.txt


Infos: 
Description:	Linux Mint 17 Qiana
Release:	17
Banshee 2.6.2

Thank you so much in advance for your help.

Poyo
Comment 1 André Klapper 2020-03-17 09:52:54 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.