Bug 211145 - UI stops responding when adding custom genre in simple mode
Summary: UI stops responding when adding custom genre in simple mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tagtool
Version: 5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-17 17:26 UTC by Tim Waugh
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-17 19:33:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Fix genre drop-down box on vorbis files (660 bytes, patch)
2006-10-17 18:43 UTC, Brian Pepple
no flags Details | Diff

Description Tim Waugh 2006-10-17 17:26:39 UTC
Description of problem:
I'm seeing a bug that seems to have similar symptoms to a bug the 0.12.2
changelog suggests is meant to be already fixed.  The UI no longer responds to
input events, only window refreshes.

Version-Release number of selected component (if applicable):
0.12.2-6.fc5

How reproducible:
100%

Steps to Reproduce:
1. Click on an ogg file
2. Put '1999' in the Year field and 'Ballad' in the Genre field
3. Click 'Save Changes'
  
Actual results:
UI stops responding and changes are not saved.

Expected results:
Changes are saved.

Comment 1 Brian Pepple 2006-10-17 17:53:09 UTC
Verified that the bug is definitely reproducable.

It appears the bug happens when a custom genre is entered in its drop-down box
in simple mode.  The genre can be modified in the advanced editing, but if the
ui is switched back to simple mode with the new genre it will freeze the ui.

Comment 2 Brian Pepple 2006-10-17 18:43:32 UTC
Created attachment 138705 [details]
Fix genre drop-down box on vorbis files

This patch should fix the problem.  I did a couple of quick tests to verify
that this fixed it.  I'll apply this is a bit.

Comment 3 Brian Pepple 2006-10-17 19:33:25 UTC
This fix should be available with the next push of signed extra packages.

tagtool-0.12.2-7.fc5
tagtool-0.12.2-9.fc6


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