Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 162324 - track names not appearing in main window
Summary: track names not appearing in main window
Alias: None
Product: Fedora
Classification: Fedora
Component: grip
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Adrian Reber
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-02 16:10 UTC by Jef Spaleta
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-07-07 09:59:02 UTC
Type: ---

Attachments (Terms of Use)

Description Jef Spaleta 2005-07-02 16:10:46 UTC
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):

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?


Comment 1 Adrian Reber 2005-07-03 08:21:05 UTC
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 05:48:52 UTC
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 09:59:02 UTC
A patched version without the error can be found at:


Comment 5 Jef Spaleta 2005-07-08 14:54:07 UTC
That patched versions definitely seems to have fixed it on my development box.


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