On Sunday, May 1, 2016 2:47:52 PM EDT Tim E. Real wrote:
> On Sunday, May 1, 2016 2:05:20 AM EDT Tim E. Real wrote:
> > Can you check if for example LV2 Calf, say Calf Organ's
> > 
> >  UI can be opened or crashes?
> > 
> > I'm getting a crash at line 1402 in lv2host.cpp:
> >     LV2Synth::lv2ui_ShowNativeGui (...)
> >     {
> >     
> >             ...
> > 
> > HERE:    ewWin = QWidget::createWindowContainer(x11QtWindow);
> > 
> >             ...
> >     
> >     }
> > 
> > I recompiled our lv2GtkHelper library but same thing.
> > 
> > I built Calf from source and verified that MusE was opening
> > 
> >  my installed Calf version in /usr/local but same thing.
> > 
> > I had suspected it was similar to the Qt4 / Qt5 difference thingy
> > 
> >  which causes synthv1(qt4) and friends' UIs to crash upon dlopen(),
> >  where the plugin was built with Qt4 and your system is running Qt5,
> >  except here it would be caused by a Gtk-2 / Gtk-3 difference.
> > 
> > But no, it does not seem to be the same type of issue here,
> > 
> >  it is not crashing at dlopen().
> > 
> > The code seems to be the correct way from what I have researched.
> > I tried passing a parent to createWindowContainer(),
> > 
> >  and passing some flags as I saw suggested.
> > 
> > Calf was definitely working before I distro upgraded.
> > 
> > I will try to fire up the old distro but thought I would ask here.
> > 
> > Thanks.
> > Tim.
> 
> Thanks for the replies.
> 
> That's what I get for upgrading to cutting edge instead of LTS, eh ;-)
> It's Kubuntu 16.
> 
> Tried some more things. Created my own parent and passed it
>  to createWindowContainer(). NG.
> 
> At this moment here's where I'm at:
> 
> I thought I read about some troubles with QWindow initial sizes and so on.
> The geometry of variable x11QtWindow is zero at first.
> I give it some geometry so that I might see something, with:
>       x11QtWindow->setGeometry(100, 100, 200, 200);
> Just to be sure, I also do:
>       x11QtWindow->show();
> 
> * Only by removing the line that I mentioned:
>       ewWin = QWidget::createWindowContainer(x11QtWindow);
>  (and removing this one too, of course)
>       win->setCentralWidget(ewWin);
>  do I get somewhere.
> 
> Presto !
> Calf UI up and running fine and showing at the geometry above.
> 
> The container parent (variable 'win') is also showing,
>  but is blank of course since I rem'd createWindowContainer().
> 
> Oddly, I can expand the Calf window /outward/ but not inward.
> I guess it'll allow inward once I go /past/ Calf's desired minimum size,
>  which I didn't bother trying.
> 
> Hm. You know, it crashes on an actual x11 xCB_something_or_other
>  call to setParent(). (That's why I was trying parent stuff.)
> I recently swapped my video card due to severe instability with KDE
>  and now everything seemed fine. Or not ...
> These cards are a wee bit old eh... Out of the five or so I have
>  all of them are really touch and go with modern KDE - this one was
>  the only one that gave solid stability for a week now.
> 
> Stay tuned...

Booted my 14.04 LTS distro. Everything fine. Check. Calf OK.

So two video cards and an actual Qt5 build of QTractor later and...

Same problem in all cases in the latest 16.x distro :-(

Remember, this is now KDE5 - a major step from 14.04's KDE4.

Dig this:
QTractor (the Qt5 version) crashes in the very same place, 
 a call to QXcbWindow::setParent() !

Researching that yields a lot about some recent fixes about Qt
 assuming always a valid screen when it turned out to be not true
 so they had to revert or something. 
I'm not sure if these fixes made it into this Qt 5.5.1 release or actually 
 may have made it worse or something's overlooked or what...
Some of the chitchat back and forth among the patchers seemed
 not confident and worrisome. The revert seemed scary for them.

Yet so far I can find no others complaining of QTractor(Qt5) crashing.
Weird. Not sure what's going on.

Ah well. Wait (pray) for the next Qt upgrades and for now produce 
 actual music on 14.04 LTS, I guess.

Is no one else running a similar distro having these problems?
Maybe I'll ask on LAU...

Cheers and thanks.
Tim.


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer

Reply via email to