Bug 527107

Summary: Non-working LASH Panel desktop menu entry would require libraries to be split off
Product: [Fedora] Fedora Reporter: Michael Schwendt <bugs.michael>
Component: lashAssignee: Anthony Green <green>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: green, oget.fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-15 10:56:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 505421    
Bug Blocks:    
Attachments:
Description Flags
lash_panel console output none

Description Michael Schwendt 2009-10-04 15:39:33 UTC 
Description of problem:
The "lash" does not only install liblash.so.1 as required by several other packages (see output of "repoquery --whatrequires liblash.so.1"), but it also installs /usr/share/applications/fedora-lash-panel.desktop which doesn't work by default. It's a non-functional menu entry, because /usr/bin/lash_panel by default refuses to start. Silently. Without any graphical error dialog.


Version-Release number of selected component (if applicable):
lash-0.5.4-5.fc11.i586
Comment 1 Orcan Ogetbil 2009-10-04 19:26:22 UTC 
Thanks for the report!

(In reply to comment #0)
> Description of problem:
> The "lash" does not only install liblash.so.1 as required by several other
> packages (see output of "repoquery --whatrequires liblash.so.1"), but it also
> installs /usr/share/applications/fedora-lash-panel.desktop 

It is a 160K package. Do we really need to split it up more? Is there any guideline that requires splitting library files?

> which doesn't work
> by default. It's a non-functional menu entry, because /usr/bin/lash_panel by
> default refuses to start. Silently. Without any graphical error dialog.
> 

This is the second lash bug reported in 2 days that I can't reproduce. lash_panel starts fine here. Any more information? Console output, traceback etc?
Comment 2 Michael Schwendt 2009-10-04 19:40:36 UTC 
Created attachment 363612 [details]
lash_panel console output
Comment 3 Orcan Ogetbil 2009-10-04 19:54:47 UTC 
Oh, I see. This is a consequence of the long standing bug 505421. I hope they fix that soon which is not very hard to do. (if you read that bug you will see the unresponsiveness of the maintainer which renders F-11 useless for audio production)

Well, the workaround is to unblacklist snd-seq* modules. Or to issue a
   modprobe snd-seq
and/or
   modprobe snd-seq-oss
which can be put in your /etc/rc.local file. I believe that lash_* applications will start fine afterwards. 


About the splitting problem. Is that a necessity?
Comment 4 Michael Schwendt 2009-10-04 20:26:19 UTC 
> About the splitting problem. Is that a necessity?  

Only if the LASH Panel desktop menu entry continued to not start anything. ;)

I wasn't aware of bug 505421. Once it gets fixed, this one can be closed.
Comment 5 Orcan Ogetbil 2010-02-14 22:31:31 UTC 
Can we close this now? Is everything okay?
Comment 6 Michael Schwendt 2010-02-15 10:56:09 UTC 
Cannot test that on F11 anymore. On F12 it is not reproducible.