qjackctl main window doesn't show on fiesty

Bug #114720 reported by Darrick
4
Affects Status Importance Assigned to Milestone
qjackctl (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: qjackctl

qjackctl launches but the main window never shows up. Using gnome with fiesty. Did an upgrade from dapper to edgy to fiesty.

Tried compiling 0.2.22 which mentioned something about the wflags but that didn't work.

Found if I comment out the wflags it works fine. Here's the patch of what I did to get it working.

diff -x '*.Po' -x autom4te.cache -urBb qjackctl-0.2.21/src/main.cpp qjackctl-0.2.21.me/src/main.cpp
--- qjackctl-0.2.21/src/main.cpp 2006-09-24 05:29:31.000000000 -0700
+++ qjackctl-0.2.21.me/src/main.cpp 2007-05-14 18:42:05.000000000 -0700
@@ -75,7 +75,7 @@
        if (settings.bKeepOnTop)
                wflags |= Qt::WStyle_Tool;
        // Construct the main form, and show it to the world.
- qjackctlMainForm w(0, 0, wflags);
+ qjackctlMainForm w(0, 0 );
        app.setMainWidget(&w);
     w.setup(&settings);
     // If we have a systray icon, we'll skip this.

Revision history for this message
Emmet Hikory (persia) wrote :

Are you sure it doesn't appear? For me, it doesn't show in any of the various windows selection tools available, but if I switch to a clean virtual desktop and start qjackctl, it appears. Simiarly, if I start qjackctl in a normal working environment, and then carefully minimise each app (not using minimise all), I eventually find the GUI in the background somewhere.

Revision history for this message
Darrick (darrick) wrote :

You're right. It does show up behind everything and doesn't show up on the toolbar. Very confusing. Led me astray.

Revision history for this message
Emmet Hikory (persia) wrote :

Thanks for confirming the behaviour. While the window appears, I still believe his to be a bug (as I've had more than one qjackctl open on more than one occasion as a result). On the other hand, I'm not entirely comfortable with the suggested patch, as I'm not sure all the window flags should be omitted. I'd suggest one of 1) using WStyle_StaysOnTop (which may have unpleasant side effects), 2) trying other flags from http://doc.trolltech.com/3.3/qt.html#WidgetFlags-enum to see if you can find a combination that works, or 3) investigating how Settings.bKeepOnTop is set, and perhaps using that to set WStyle_Tool at runtime.

Changed in qjackctl:
status: Unconfirmed → Confirmed
Revision history for this message
Darrick (darrick) wrote :

It's a low priority for me but I will keep the fix in mind. I'll see if I can't work it out with the main developer.

Revision history for this message
Darrick (darrick) wrote :

Under "Setup->Misc" there is a option: "Keep child windows always on top"

By unchecking it upon restart qjackctl displays in the toolbar and on top of any other windows.

This is the flag causing the problem.
if (settings.bKeepOnTop)
    wflags |= Qt::WStyle_Tool;

Revision history for this message
Emmet Hikory (persia) wrote :

This issue is resolved with qjackctl 0.2.22-2ubuntu1)

Changed in qjackctl:
status: Confirmed → Fix Released
Revision history for this message
Robert Persson (ireneshusband) wrote :

I've been having this problem and I have also been having a problem with the connection and patchbay windows only staying open very briefly when I open them. I don't know if these problems are related but they are certainly both very disrputive.

I use KDE, by the way.

Revision history for this message
Krzysztof Foltman (kfoltman) wrote :

Happens here too. I think the author's intention was to make the window topmost and a tool window at the same time - but he forgot about the topmost thing so the window lurks near the bottom of Z-order on a crowded desktop. The only way to get to it is minimizing other windows one by one. Confusing at first, even more to novice users I guess.

Unchecking "Keep child windows always on top" and restarting eliminates (or sidesteps) the problem.

I don't know Ubuntu policies about those minor bugs - is there any hope it will be fixed as an update to Feisty (at least by unchecking "keep on top" by default)?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.