2 May
2016
2 May
'16
6:28 a.m.
Hi list. Requesting verification of a bug:
After upgrading from *buntu 14.04 LTS to 16.x, the LV2 Gtk2 UIs
such as Calf and others crash upon opening them in both
Qt5 QTractor and Qt5 MusE-3, at these similar calls:
QTractor: In qtractorLv2Plugin.cpp
QWidget *pQtContainer = QWidget::createWindowContainer(pQtWindow, pQtWidget);
MusE: In lv2host.cpp:
ewWin = QWidget::createWindowContainer(x11QtWindow);
The crash ultimately happens deep inside the Qt5 libraries at the
same place in both apps :
QXcbWindow::setParent()
I tried building Calf from source release, and tried different
video cards. NG.
But... If I bypass createWindowContainer() in MusE the UIs open and work fine!
(Just that now of course they are outside of the container window.)
It's Qt 5.5.1
I read about a bug fix and revert where they assumed always a valid screen
but then had to revert, but that's supposed to be fixed now.
I'm confused.
Is it just me getting these crashes?
Thanks.
Tim.
2 May
2 May
11:56 a.m.
On 05/02/2016 05:28 AM, Tim E. Real wrote:
Hi list. Requesting verification of a bug:
After upgrading from *buntu 14.04 LTS to 16.x, the LV2 Gtk2 UIs
such as Calf and others crash upon opening them in both
Qt5 QTractor and Qt5 MusE-3, at these similar calls:
QTractor: In qtractorLv2Plugin.cpp
QWidget *pQtContainer = QWidget::createWindowContainer(pQtWindow, pQtWidget);
MusE: In lv2host.cpp:
ewWin = QWidget::createWindowContainer(x11QtWindow);
The crash ultimately happens deep inside the Qt5 libraries at the
same place in both apps :
QXcbWindow::setParent()
I tried building Calf from source release, and tried different
video cards. NG.
But... If I bypass createWindowContainer() in MusE the UIs open and work fine!
(Just that now of course they are outside of the container window.)
It's Qt 5.5.1
I read about a bug fix and revert where they assumed always a valid screen
but then had to revert, but that's supposed to be fixed now.
I'm confused.
Is it just me getting these crashes?
on my boxes, all openSUSE Tumbleweed 20160422, qtractor 0.7.7, Qt 5.5.1,
i often get sth like this on most Calf LV2UI::Gtk2UI's window closing, eg:
QXcbConnection: XCB error: 3 (BadWindow), sequence: 2500, resource id:
111149141, major code: 7 (ReparentWindow), minor code: 0
but NO crashes to date, yet :)
byee
--
rncbc aka. Rui Nuno Capela
4:38 p.m.
On Mon, 2 May 2016, Tim E. Real wrote:
Hi list. Requesting verification of a bug:
After upgrading from *buntu 14.04 LTS to 16.x, the LV2 Gtk2 UIs
such as Calf and others crash upon opening them in both
Qt5 QTractor and Qt5 MusE-3, at these similar calls:
Hmm, was going to say not a problem here... however, the about box tells
me the default qtractor in 16.04 is not qt5 (after they made such a noise
about making sure qjackctl was qt5) My complaint is more along the lines
that so few plugins get listed. I have a lot more lv2 plugins than show
up. So I am wondering where I have plugins that qtractor doesn't look.
I do know that one difference from 14.04 to 16.04 is that gcc5 was
introduced and that complicated things for plugins which need to match the
host, but I have not had that problem either.
--
Len Ovens
www.ovenwerks.net
5:03 p.m.
On 05/02/2016 03:38 PM, Len Ovens wrote:
On Mon, 2 May 2016, Tim E. Real wrote:
this is all about qt5 as being the new yellow brick road.
qt4 is phased out, don't rely on it. period. we're in 2Q2016 already.
problem with some LV2 hosts and their plugin GUIs is that Qt5 is
ditching its former reliance on X11 at the API level, moving one step
up over the stack to XCB. and all that is abstracted enough, sorry to
tell. that wasn't the case with Qt4/X11 back then
strange things happens (and some sort of sh*t often do) when old
landscapes (like qt4) are still under view beneath the mist
myths and conspiracy theories... start to blossom... ;)
cheers
--
rncbc aka. Rui Nuno Capela
Hi list. Requesting verification of a bug:
After upgrading from *buntu 14.04 LTS to 16.x, the LV2 Gtk2 UIs
such as Calf and others crash upon opening them in both
Qt5 QTractor and Qt5 MusE-3, at these similar calls:
Hmm, was going to say not a problem here... however, the about box tells
me the default qtractor in 16.04 is not qt5 (after they made such a
noise about making sure qjackctl was qt5) My complaint is more along the
lines that so few plugins get listed. I have a lot more lv2 plugins than
show up. So I am wondering where I have plugins that qtractor doesn't look.
I do know that one difference from 14.04 to 16.04 is that gcc5 was
introduced and that complicated things for plugins which need to match
the host, but I have not had that problem either.
31 May
31 May
11:51 p.m.
New subject: [FIXED] Re: RFV: LV2 Gtk2 UIs crashing Qt5 QTractor and MusE at same place
Thanks for the replies.
Today updates came down the line for 16.04
and it works now.
openSUSE already had the fixes and it worked fine there,
so now I was just waiting for this.
On with the show...
T.
On Monday, May 2, 2016 12:28:28 AM EDT Tim E. Real wrote:
Hi list. Requesting verification of a bug:
After upgrading from *buntu 14.04 LTS to 16.x, the LV2 Gtk2 UIs
such as Calf and others crash upon opening them in both
Qt5 QTractor and Qt5 MusE-3, at these similar calls:
QTractor: In qtractorLv2Plugin.cpp
QWidget *pQtContainer = QWidget::createWindowContainer(pQtWindow,
pQtWidget);
MusE: In lv2host.cpp:
ewWin = QWidget::createWindowContainer(x11QtWindow);
The crash ultimately happens deep inside the Qt5 libraries at the
same place in both apps :
QXcbWindow::setParent()
I tried building Calf from source release, and tried different
video cards. NG.
But... If I bypass createWindowContainer() in MusE the UIs open and work
fine! (Just that now of course they are outside of the container window.)
It's Qt 5.5.1
I read about a bug fix and revert where they assumed always a valid screen
but then had to revert, but that's supposed to be fixed now.
I'm confused.
Is it just me getting these crashes?
Thanks.
Tim.
3053
days inactive
3082
days old
linux-audio-user@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
Len Ovens -
Rui Nuno Capela -
Tim E. Real