Bug 450982 - buttons don't work with qt-4.3.5.1
buttons don't work with qt-4.3.5.1
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: qt4 (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-11 22:33 EDT by Bill C. Riemers
Modified: 2008-06-11 23:01 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-06-11 23:01:09 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 Bill C. Riemers 2008-06-11 22:33:05 EDT
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):

qt-4.3.5.1

How reproducible:

100%

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
widget.

Expected results:

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


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-11 23:01:09 EDT
Curious.  Reverting back to qt-4.3.4.11 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.