Posts: 8
Joined: Feb 2011
Reputation:
0
Folks,
I get this error...
"pkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem."
every time I try to install XBMC two ways....using NitoTV (the install XBMC portal) and through Terminal.
I searched Google for answers, but did not find anyone else with the same issue. I have no clue as to what this error is about.
Any help would be greatly appreciated!
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
how about showing the entire results from the apt-get install ?
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
I'd say do what it's telling you to do.
Posts: 442
Joined: Jul 2008
Reputation:
5
was just about to say.. It's giving you instructions on how to fix the problem.. how about trying them?
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
gezz
ssh in
type the following without the quotes
"dpkg --configure -a"
Posts: 8
Joined: Feb 2011
Reputation:
0
.....I tried that. Next?
Instead of explaining ....therefore answering my question... why that happened (apparently) only to me, you give that answer.
No XBMC for me. You are an idiot. Sorry.
Posts: 669
Joined: Jul 2008
Reputation:
1
2011-02-08, 01:13
(This post was last modified: 2011-02-08, 01:17 by dtviewer.)
"Again, insulting comments like: "you had some particles fall from the universe through your CPU." do not help, are not funny, "
I thought it was funny..............
BTW, the poster you just got snarky with was trying to help you and mentioned a couple possible explanations (net drop, computer hiccup).
If you know what happened that you can tell him that it wasnt a net drop or a computer hiccup, then you should fix the problem yourself.
Posts: 25
Joined: Jan 2011
Reputation:
0
2011-02-08, 02:43
(This post was last modified: 2011-02-08, 02:47 by wedgehead.)
Hey smart ass. Since you are not getting the answer you want or can not do as instructed, why don't you just go into itunes and restore back to original apple firmware. Then you can either walk away or give it another try from scratch and see if the same error happens again.
Seriously the only ass here is you. And then going into other threads to simply spread your bile is not cool.