On Sunday 25 September 2005 09:27 pm, Brad Pepers wrote:
There is a bug in the Qt/KDE integration patches to Qt in SuSE 9.3 which is causing third-party applications such as Quasar, Scribus, and LinCVS to fail to work properly. Its easy to duplicate and show and is a problem in the patch to redirect Qt QMessageBox static methods to KDE message boxes. The basic problem is that there are two ways to call the QMessageBox functions. One way you pass in the text for the buttons on the message box and it should return which button was pressed (0, 1, or 2). The other way to call something like QMessageBox::warning though is to pass in a list of button ids such as QMessageBox::Yes/No/Cancel/... and in this case what should be returned is the button id that was clicked. The replacement code added in SuSE 9.3 that passes these functions off to KDE treats these both the same and will return the button number (0/1/2) in each case. So any code that uses Qt and calls QMessageBox::warning with button ids of QMessageBox::Yes and QMessageBox::No and then checks the result to make sure it matches QMessageBox::Yes will now fail and the user is left with an application that won't do the work regardless of whether they choose Yes or No!
I reported this to SuSE support and then to the Technical Feedback and have not yet seen a fix or any acknowledgment of the problem so I thought I would have one last kick at trying to get through to someone at SuSE to get this fixed. The only other alternative for applications effected is to static compile the application with our own copy of Qt which doesn't have the KDE integration patches but this is a pain and means the application doesn't have the native look and feel and SuSE should fix this problem! [...]
Brad Pepers brad@linuxcanada.com
Shouldn't have to static compile things to get around an easily fixable bug SuSE should fix. Even in 9.2, the Yes & No buttons are switched, but still seem to work correctly from my tests. Let's hope someone is
Brad, Seems this same problem was carried over to SuSE 10 as well, so it either wasn't reported to the OpenSuSE guys in time for it to be fixed and they just disregarded it. This seems like a bug SuSE has created tweaking things they didn't really need to touch. Hopefully someone is making an effort to correct it? --------- paying attention and will provide us some bug free QT & KDE files soon. Many of us that are preparing to move to 10.0 use the programs you mentioned and losing things due to this bug would certainly make us swear! ;o) end of line Lee