jockey-kde failed to upgrade dependency problems - leaving unconfigured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
lex@kubuntu:~$ sudo apt-get upgrade
[sudo] password for lex:
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso
Reading state information... Fatto
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
3 non completamente installati o rimossi.
After this operation, 0B of additional disk space will be used.
Continuare [S/n]? s
Configuro python-apt (0.7.4ubuntu5) ...
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
rv = action.
File "/usr/bin/
self.
File "/usr/bin/
rt.
AttributeError: 'NoneType' object has no attribute 'byte_compile'
dpkg: errore processando python-apt (--configure):
il sottoprocesso post-installation script ha restituito un codice di errore 1
Configuro jockey-common (0.2-0ubuntu5) ...
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
rv = action.
File "/usr/bin/
self.
File "/usr/bin/
(self.
TypeError: int argument required
dpkg: errore processando jockey-common (--configure):
il sottoprocesso post-installation script ha restituito un codice di errore 1
dpkg: problemi con le dipendenze impediscono la configurazione di jockey-kde:
jockey-kde dipende da jockey-common (= 0.2-0ubuntu5); comunque:
Il pacchetto jockey-common non è ancora configurato.
dpkg: errore processando jockey-kde (--configure):
problemi con le dipendenze - lasciato non configurato
Sono occorsi degli errori processando:
python-apt
jockey-common
jockey-kde
E: Sub-process /usr/bin/dpkg returned an error code (1)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 192992, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.