Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 254369 - media-sound/lmms-0.4.2 version bump
Summary: media-sound/lmms-0.4.2 version bump
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Alexis Ballier
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-10 00:19 UTC by Thomas Kuther
Modified: 2009-01-10 15:25 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Kuther 2009-01-10 00:19:18 UTC
There is a new(er) version of LMMS available.

No new configurable features were at added, looking at the CMakeLists.txt diff, so it's a simple copy of the lmms-0.4.0 ebuild.

Regarding the currently p.use.mask'ed "vst" use flag and its libxcb issue when opening a VST plugin's GUI: this seems fixed in this release. I can successfully load, open and use various vst plugins without having set LIBXCB_ALLOW_SLOPPY_LOCK=1

Could someone (Alexis? :)) please test & confirm this, and if all is fine please remove "media-sound/lmms vst" from profiles/base/package.use.mask?

Cheers!
Thomas

Reproducible: Always

Steps to Reproduce:
Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-01-10 04:38:54 UTC
Reassigning to maintainer.
Comment 2 Alexis Ballier gentoo-dev 2009-01-10 12:21:42 UTC
bumped but vestige still fails here :(

Notice: could not set realtime priority.
there's already a client with name 'lmms', so unique name 'lmms-01' was assigned
unique ID: Amb1

RemotePlugin::DebugMessage: creating editor
RemotePlugin::DebugMessage: creating GUI thread
RemotePlugin::DebugMessage: editor successfully created
Locking assertion failure.  Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x7f9643e7d98c]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x17) [0x7f9643e7daf7]
#2 /usr/lib/libX11.so.6 [0x7f964562cd20]
#3 /usr/lib/libX11.so.6(XGetWindowProperty+0x42) [0x7f9645609ba2]
#4 /usr/lib/qt4/libQtGui.so.4 [0x7f96499ed37c]
#5 /usr/lib/libX11.so.6(XCheckIfEvent+0x79) [0x7f96455fe4d9]
#6 /usr/lib/qt4/libQtGui.so.4(_ZN18QX11EmbedContainer11embedClientEm+0x224) [0x7f96499ed9f4]
#7 /usr/lib64/lmms/libvstbase.so(_ZN9vstPlugin10showEditorEP7QWidget+0xeb) [0x7f963b4c0d0b]
#8 /usr/lib64/lmms/libvestige.so(_ZN17vestigeInstrument8loadFileERK7QString+0x2c2) [0x7f961d1523a2]
#9 /usr/lib64/lmms/libvestige.so(_ZN21vestigeInstrumentView10openPluginEv+0x5b7) [0x7f961d151717]
#10 /usr/lib64/lmms/libvestige.so(_ZN21vestigeInstrumentView11qt_metacallEN11QMetaObject4CallEiPPv+0x4d) [0x7f961d1518fd]
#11 /usr/lib/qt4/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x244) [0x7f96492d4a34]
#12 /usr/lib/qt4/libQtGui.so.4(_ZN15QAbstractButton7clickedEb+0x37) [0x7f9649ee3ce7]
#13 lmms(_ZN12pixmapButton17mouseReleaseEventEP11QMouseEvent+0x9) [0x4d65d9]
#14 /usr/lib/qt4/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x9b1) [0x7f96499b8161]
#15 /usr/lib/qt4/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xbd) [0x7f9649965d6d]
#16 /usr/lib/qt4/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x8fc) [0x7f964996e2fc]
#17 /usr/lib/qt4/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0xd0) [0x7f96492c07b0]
#18 /usr/lib/qt4/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_E+0x108) [0x7f964996d6a8]
#19 /usr/lib/qt4/libQtGui.so.4 [0x7f96499d0d09]
lmms: xcb_xlib.c:73: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
Aborted


of course LIBXCB_ALLOW_SLOPPY_LOCK=1 lets the plugin run fine
Comment 3 Thomas Kuther 2009-01-10 12:57:39 UTC
Interesting. Works fine here.

The only markable change on my box since 0.4.0 is that I had to switch from nvidia to nouveau driver for the graphics device.

Could this have something to do with it?
Comment 4 Alexis Ballier gentoo-dev 2009-01-10 13:03:11 UTC
(In reply to comment #3)
> Interesting. Works fine here.
> 
> The only markable change on my box since 0.4.0 is that I had to switch from
> nvidia to nouveau driver for the graphics device.
> 
> Could this have something to do with it?

no clue, but i'm using radeonhd :)
Comment 5 Thomas Kuther 2009-01-10 15:25:35 UTC
(In reply to comment #4)
> no clue, but i'm using radeonhd :)
> 

OK, then it's unrelated.
There were some changes in SVN to vestige, so let's wait for the next release and see.