Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 331695 - media-video/avidemux-2.5.3-r2 depends on media-plugins/swh-plugins
Summary: media-video/avidemux-2.5.3-r2 depends on media-plugins/swh-plugins
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Markos Chandras (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-08 22:19 UTC by Michael Weber (RETIRED)
Modified: 2010-09-14 09:06 UTC (History)
3 users (show)

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 Michael Weber (RETIRED) gentoo-dev 2010-08-08 22:19:15 UTC
I had an error launching avidemux_gtk, reemerge did not work, e-file revealed media-plugins/swh-plugins as source of /usr/lib{,64}/ladspa/mbeq_1197.so
Emerging media-plugins/swh-plugins solved the problem.

michael@io /tmp % avidemux2_gtk
*************************
  Avidemux v2.5.3
*************************
 http://www.avidemux.org
 Code      : Mean, JSC, Gruntster
 GFX       : Nestor Di , nestordi@augcyl.org
 Design    : Jakub Misak
 FreeBSD   : Anish Mistry, amistry@am-productions.biz
 Audio     : Mihail Zenkov
 MacOsX    : Kuisathaverat
 Win32     : Gruntster

Compiler: GCC 4.5.1
Build Target: Linux (x86-64)
User Interface: GTK+ (2.21.5)

Large file available: 1 offset

Initialising prefs
Creating dir :mkdir /home/michael/.avidemux
Using /home/michael/.avidemux as base directory for prefs/jobs/...
[cpuCaps]Checking CPU capabilities
                MMX detected
                MMXEXT detected
                SSE detected
                SSE2 detected
                SSE3 detected
                SSSE3 detected
[cpuCaps]End of CPU capabilities check (cpuMask :ffffffff)

[SDL] Version: 1.2.13
Failed to load plugin "/usr/lib/ladspa/mbeq_1197.so": /usr/lib/ladspa/mbeq_1197.so: cannot open shared object file: No such file or directory
[SDL] Initialisation %
Comment 1 Markos Chandras (RETIRED) gentoo-dev 2010-08-08 23:33:05 UTC
Fixed

Thanks for reporting
Comment 2 Martin Väth 2010-08-09 15:21:18 UTC
Here, swh-plugins is *not* a runtime dependency of avidemux:

Grepping "mbeq" or "swh" in the avidemux source code reveals nothing.
Moreover, avidemux_qt4 (didn't try avidemux_gtk since I have not compiled it,
but I would be surprised if this makes a difference) runs here without
swh-plugins.

So, I suppose that it is sdl or something else which requires mbeq in some
circumstances (if compiled with a certain USE flag, or by some forgotten automagic dependency); perhaps also some broken .la file is a reason.

It might make a difference that I use libsdl-1.2.14-r3.
It might also make a difference that I removed all .la files containing
shouldnotlink=no (since these are not needed for dynamic linking).

If possible, I would really like to see the swh-plugins dependency removed
from avidemux, since it is obviously not needed unconditionally and depends 
on the huge fftw library...
Comment 3 Markos Chandras (RETIRED) gentoo-dev 2010-08-09 15:36:44 UTC
I don't currently use this package but if you or Michael can work on that and see  if this dep is really needed or not, i will fix it for you
Comment 4 Martin Väth 2010-08-10 08:21:36 UTC
There is nothing which I can check since simply on my whole system nothing
depends on it. Neither the source code of avidemux nor that of sdl-1.2.14
does seem to contain anything related to ladspa or mbeq.

The dependency must have come to Michael's system through
some other package (by a different USE flag in some other package or by
some automagic dependency).

Michael, had you ever installed swh-plugins before?
Please, also grep your *.la files for -lbeq_1197, or even better:
Which packages need to be rebuild for revdep-rebuild -L ".*beq.*1197.*" -p
Comment 5 Michael Weber (RETIRED) gentoo-dev 2010-08-11 13:22:25 UTC
(In reply to comment #4)
> The dependency must have come to Michael's system through
> some other package (by a different USE flag in some other package or by
> some automagic dependency).
> 
> Michael, had you ever installed swh-plugins before?
Yes I had 
     Fri Dec  4 05:28:04 2009 >>> media-video/avidemux-2.4.4-r2
     Sat Dec  5 03:06:47 2009 >>> media-video/avidemux-2.5.1_p5428
     Thu Dec 24 18:28:34 2009 >>> media-video/avidemux-2.5.2
     Tue Jan 12 23:03:31 2010 >>> media-video/avidemux-2.5.2
     Sat Apr 24 23:40:03 2010 >>> media-video/avidemux-2.5.2
     Sun Jun 20 19:12:19 2010 >>> media-video/avidemux-2.5.2
     Sun Jun 20 23:11:38 2010 >>> media-video/avidemux-2.5.3-r1
     Sun Jun 27 21:15:52 2010 >>> media-plugins/swh-plugins-0.4.15
     Thu Jul  1 09:54:25 2010 >>> media-plugins/swh-plugins-0.4.15
     Sun Aug  1 15:20:51 2010 >>> media-video/avidemux-2.5.3-r2
     Mon Aug  9 00:09:28 2010 >>> media-video/avidemux-2.5.3-r2
     Mon Aug  9 00:12:41 2010 >>> media-plugins/swh-plugins-0.4.15

> Please, also grep your *.la files for -lbeq_1197, or even better:
io ~ # find /usr -name "*.la" -exec grep lbeq_1197 {} \;
io ~ # find /usr -name "*.la" -exec grep 1197 {} \; 
no results

> Which packages need to be rebuild for revdep-rebuild -L ".*beq.*1197.*" -p
io ~ # revdep-rebuild -L ".*beq.*1197.*" -p
 * Configuring search environment for revdep-rebuild
 * Environment mismatch from previous run, deleting temporary files...

 * Checking reverse dependencies
 * Packages containing binaries and libraries using .*beq.*1197.*
 * will be emerged.

 * Collecting system binaries and libraries
 * Generated new 1_files.rr
 * Checking dynamic linking 
[ 100% ]                 

 * There are no dynamic links to .*beq.*1197.*... All done. 
no result either.

Funny thing is after avidemux2_gtk startup `lsof | grep mbeq_1197` is empty.
If i remove media-plugins/swh-plugins, i get the exact same error as above.

I'm trying to fine this string ...
Comment 6 Markos Chandras (RETIRED) gentoo-dev 2010-08-11 13:56:00 UTC
I reverted my last commit. Seems like it is a user specific issue so until we figure this out I prefer not to pull this dependency just yet