Bugzilla – Bug 113714
Toshiba Tecra A4 - IAL conflicts with FNFX on Default KDE Install
Last modified: 2005-09-09 07:12:26 UTC
The default install on a Toshiba Tecra A4 laptop required manual intervention to fix a conflict between IAL 0.0.1-17 and fnfx. "ial 0.0.1-17 conflict fnfx conflicts with ial fnfx conflicts with ial ial conflicts with fnfx ial conflicts with fnfx" (I don't know why the conflicts were repeated 2 times each in the dependency resolution dialog.) It seems that fnfx is better tailored for Toshiba laptops. So I think it should probably be defualt for use with special keys.
IAL provides the functionality of FnFX (graphical front end: initial). Thus FnFX will be not default for 10.0. I'll add brightness support to IAL with the next or next but one beta.
OH, so next time I install beta 3 on a Toshiba laptop, I should select IAL and not FNFX. OK, I got it. But what about the conflict. I don't think novices will like being asked to resolve a dependency conflict with programs they know nothing about and on a default install even.
Yepp. I've just implemented that IAL will do brightness up and down out of the box, just like fnfx. Let me know if you're interested in testing, I'll send you update packages. Regarding the conflict: I'll take care that. The installation process on Toshiba laptops should only select and install IAL -- not FnFX.
It seems like IAL is better all around, why even provide fnfx? Anyway, will the updated IAL make it into Beta 4? If so, then I'll just wait for that. :) I wouldn't even know how to install an updated package. ;p
Since IAL does not yet provide the full functionality FnFX provides, we do still ship both solutions. The switch from FnFX to IAL will be completed after SL10.0. I have submitted new packages of acpid and IAL which will be available with Beta 4. I'll close the bug. Please verify and re-open if something does not work as expected.
Sorry, way to quick. The dependency conflict still needs to be fixed. Seife, please attach the YaST log files of your installation.
Created attachment 48011 [details] /var/log/YaST2
1 packages failed Name: ial Edition: 0.0.1-17 From-Input-List: yes Conflicts-With: fnfx-0.3-7 conflicts with ial, fnfx-0.3-7 conflicts with ial, ial-0.0.1-17 conflicts with fnfx, ial-0.0.1-17 conflicts with fnfx Remove-To-Solve-Conflict: fnfx
this is Timo's bug but he is on vacation. Can i do anything to help with this or can we wait until Wednesday? Do i need to change the ial specfile and submit a new package? Do we need to change the selections? Some yast magic that detects a toshiba and adds fnfx? hwinfo?
We do not need to add FnFX if we detect a Toshiba laptop any longer since IAL covers the functionality of FnFX. Reassigning to the YaST team, I have no clue how things work once a Toshiba laptop is detected. Since IAL is in the default selection for laptops it should no be required to be added once a Toshiba laptop is detected.
I think this is done by hwinfo reporting it as needed once a Toshiba is detected. Steffen?
Michael, are you able to "do some magic" here? :)
Check with Beta4, please. *** This bug has been marked as a duplicate of 112949 ***
ad comment 11: yes, hwinfo says toshiba needs fnfx. Remove it?
yes please.
Why? Since Beta4, when hwinfo suggests installing fnfx, ial is deselected. If you want to install always ial, then removing fnfx from hwinfo list is a solution (in this case, please, reopen this bug and reassign to Steffen).
submitted new hwinfo 11.21
IAL and initial were moved to the mobile computing selection (#115849). Hence, we now need to install IAL if a Toshiba laptop is detected -- only IAL, _not_ initial.
Created attachment 49215 [details] proposed patch
You are talking to me?
Think so ;-) Can you please take care of this one?
Sure I can. But note you can 'assign' bugs around. Close this bug, if there's nothing else.
closed
(In reply to comment #22) > Sure I can. But note you can 'assign' bugs around. I thought that the bug was already asigned to you.