Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 450982 - buttons don't work with qt-
Summary: buttons don't work with qt-
Alias: None
Product: Fedora
Classification: Fedora
Component: qt4
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-12 02:33 UTC by Bill C. Riemers
Modified: 2008-06-12 03:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-06-12 03:01:09 UTC

Attachments (Terms of Use)

Description Bill C. Riemers 2008-06-12 02:33:05 UTC
Description of problem:

After running 'yum update' today, buttons are not working for the qt version of
vlc under my gnome desktop.   The buttons worked just fine yesterday. 
Rebuilding does not help.

Note: I am using the vlc-0.9.0-git source I downloaded on Monday...

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


How reproducible:


Steps to Reproduce:
1. download vlc source from the vlc website or it's git repository and build the
qt4 version of the gui.
2. Play ANY video.
3. Press pause or any other button.
Actual results:

The verbose output from vlc shows there is an event occuring when the button is
pressed, but it does not look like the signal or event is passed to the correct

Expected results:

Pressing a button should cause the desired action.  For example, pause should

Additional info:

I will attempt to regress to the version of qt I have on DVD, just to verify
this rpm really is the cause of the problem.

Comment 1 Bill C. Riemers 2008-06-12 03:01:09 UTC
Curious.  Reverting back to qt- has no effect.  So I am suspecting
something else has changed besides just the version of QT.

Unless someone else adds a me-too message, I think it would be safe to conclude
there is some other cause.

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