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 634145 - Manually entering track information crashes Banshee
Manually entering track information crashes Banshee
Status: RESOLVED DUPLICATE of bug 631277
Product: banshee
Classification: Other
Component: Track Editor
1.8.0
Other Linux
: Normal critical
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-06 04:20 UTC by Brett
Modified: 2010-11-09 00:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
--debug log (11.98 KB, application/octet-stream)
2010-11-06 05:06 UTC, Brett 		Details

Description Brett 2010-11-06 04:20:41 UTC 
Manually entering CD information before import will make Banshee stop responding when pressing save.

Banshee will fail to re-start afterwards. 

Need to either re-start the computer or enter terminal and kill the Banshee process to start Banshee again.

STEPS TO REPRODUCE
1 - Insert new CD
2 - Press Ctrl -A to select all then press E to begin editing
3 - Edit information
4 - Click SAVE

ACTUAL RESULTS
Banshee stops responding or completely crashes.
Occasionally the Banshee process will still be running in the background if you use force quit from the taskbar.

EXPECTED RESULTS
Track information should be updated and saved before importing.

BUILD
Banshee 1.8.0
Ubuntu 10.10
Comment 1 Brett 2010-11-06 05:06:47 UTC 
Created attachment 173934 [details]
--debug log
Comment 2 Richard Mottershead 2010-11-09 00:02:44 UTC 
I can confirm that I have the same issue as this.

Running Banshee 1.8.0 on Ubuntu 10.04.
Comment 3 Michael Martin-Smucker 2010-11-09 00:47:30 UTC 
I'm fairly sure that this is the same issue as Bug 631277.  If you update to git master - or the 1.9.0 release on Wednesday - and you can still reproduce the problem, please don't hesitate to reopen this report.

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. You may want to check for a software upgrade.

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