User login |
Errors when launching SynapticI keep seeing the following errors each time I launch Synaptic. Are they anything to be worried about..?
|
Search this site:In the forums:Today's poll:What format would you prefer for downloading 64 Studio? (Register or log in to vote) DVD install image 39% DVD live image with install option 43% I don't have a DVD burner so I have to use CD-R 14% I installed version 0.1 and only used apt since :-) 4% Total votes: 170 |
Apart from the original
Apart from the original problem, I'm finding that any attempt to install s/ware using Synaptic is giving me this error:-
E: bcm43xx-fwcutter: subprocess post-installation script returned error exit status 1
which appears at the end of every installation. The installations appear to succeed though.....
bcm43xx-fwcutter
I too am seeing this error:
dpkg: error processing bcm43xx-fwcutter (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
bcm43xx-fwcutter
jh65737 - can I ask you
jh65737 - can I ask you something to see if it coincides with my system...?
If you open Synaptic and go to Settings->Repositories, what does the Repository window look like? Is it a simple dialog with a list box and some buttons etc - or is it a property sheet, with the controls distributed between 3 x tab pages?
can I ask you
It is a simple list box. I have no tabs.
You may already have answered this question.
Hmmm....
That's interesting. I currently have 2 installations of 64studio. The one on my laptop is version 2.0 (installed from CD) and the one on my desktop PC is version 2.0 (but upgraded from a previous installation of 1.0). The upgrade is the one that doesn't work - and it's also the one with a simple list box (and no tabs).
Did you upgrade your current version from a previous version?
My advice
If you can reinstall 2.0 from a disk, back up your data and do it. You will save yourself a lot of grief. On the other hand, there is some small problems with that release (2.0) that will be addressed in the 2.1 release (planned to release in four weeks - hopefully!)