Bug 162324 - track names not appearing in main window
track names not appearing in main window
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: grip (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Reber
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-02 12:10 EDT by Jef Spaleta
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-07 05:59:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jef Spaleta 2005-07-02 12:10:46 EDT
Description of problem:
tracknames not showing up in main dialog, they do however show up in the
editting dialog.  



Version-Release number of selected component (if applicable):
grip-3.2.0-4

How reproducible:
always on a core development synced box.
works as expected on an fc4 box.

Additional info:
I think this might started when the new gtk 2.7 in the core development tree was
introduced.  I am unaware of any other apps installed from extras or core that
has a similar issue. I've tried rebuilding the grip srpm locally against the
development packages, no change.

Anything specific you want me to do for more information?

-jef
Comment 1 Adrian Reber 2005-07-03 04:21:05 EDT
I will install gtk 2.7 in next days and try to reproduce this error and will
then come back.
Comment 3 Adrian Reber 2005-07-06 01:48:52 EDT
I have reproduced the error and will close it when the new version of gtk will
be available in the development tree.
Comment 4 Adrian Reber 2005-07-07 05:59:02 EDT
A patched version without the error can be found at:

http://extras64.linux.duke.edu/needsign/development/grip/3.2.0-5.fc5/
Comment 5 Jef Spaleta 2005-07-08 10:54:07 EDT
That patched versions definitely seems to have fixed it on my development box.

-jef

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