[RISOLTO] linux 4.4.0.59 generic

Compilazione del kernel, gestione moduli, servizi attivi, e tutti gli interventi per l'ottimizzazione del sistema operativo.

Re: linux 4.4.0.59 generic

Messaggioda daigo » domenica 15 gennaio 2017, 17:09

Codice: Seleziona tutto
sudo rm /var/lib/dpkg/info/unattended-upgrades.postinst

Codice: Seleziona tutto
sudo apt-get install -f
daigo
Tenace Tecnocrate
Tenace Tecnocrate
 
Messaggi: 18871
Iscrizione: maggio 2011

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 17:19

Codice: Seleziona tutto

antonio@antonio-EasyNote-TK85:~$ sudo apt-get install -f
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
6 non completamente installati o rimossi.
Dopo quest'operazione, verranno occupati 0 B di spazio su disco.
Configurazione di lightdm (1.18.3-0ubuntu1)...
insserv: warning: script 'S99panasoniclpd-init' missing LSB tags and overrides
insserv: warning: script 'panasoniclpd-init' missing LSB tags and overrides
insserv: There is a loop between service panasoniclpd-init and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Max recursions depth 99 reached
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop at service plymouth if started
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: There is a loop at service panasoniclpd-init if started
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service plymouth and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv:  loop involving service networking at depth 4
insserv:  loop involving service checkroot at depth 4
insserv:  loop involving service mountdevsubfs at depth 2
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service panasoniclpd-init and urandom if started
insserv:  loop involving service urandom at depth 4
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service plymouth and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: errore nell'elaborare il pacchetto lightdm (--configure):
 il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Configurazione di ifupdown (0.8.10ubuntu1.2)...
insserv: warning: script 'S99panasoniclpd-init' missing LSB tags and overrides
insserv: warning: script 'panasoniclpd-init' missing LSB tags and overrides
insserv: There is a loop between service panasoniclpd-init and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop at service plymouth if started
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: There is a loop at service panasoniclpd-init if started
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service plymouth and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv:  loop involving service networking at depth 4
insserv:  loop involving service checkroot at depth 4
insserv:  loop involving service mountdevsubfs at depth 2
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service panasoniclpd-init and urandom if started
insserv:  loop involving service urandom at depth 4
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: There is a loop between service plymouth and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: errore nell'elaborare il pacchetto ifupdown (--configure):
 il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Configurazione di apport (2.20.1-0ubuntu2.4)...
insserv: warning: script 'S99panasoniclpd-init' missing LSB tags and overrides
insserv: warning: script 'panasoniclpd-init' missing LSB tags and overrides
insserv: There is a loop between service panasoniclpd-init and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop at service plymouth if started
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: There is a loop at service panasoniclpd-init if started
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service plymouth and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv:  loop involving service networking at depth 4
insserv:  loop involving service checkroot at depth 4
insserv:  loop involving service mountdevsubfs at depth 2
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service panasoniclpd-init and urandom if started
insserv:  loop involving service urandom at depth 4
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service plymouth and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: errore nell'elaborare il pacchetto apport (--configure):
 il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
dpkg: problemi con le dipendenze impediscono la configurazione di apport-gtk:
 apport-gtk dipende da apport (>= 0.41); comunque:
  Il pacchetto apport non è ancora configurato.

dpkg: errore nell'elaborare il pacchetto apport-gtk (--configure):
 problemi con le dipendenze - lasciato non configurato
Segnalazione apport non scritta poiché è stato raggiunto il valore massimo di MaxReports
        Configurazione di cups-browsed (1.8.3-2ubuntu3.1)...
insserv: warning: script 'S99panasoniclpd-init' missing LSB tags and overrides
insserv: warning: script 'panasoniclpd-init' missing LSB tags and overrides
insserv: There is a loop between service panasoniclpd-init and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!

insserv: Max recursions depth 99 reached
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop at service plymouth if started

insserv: There is a loop at service panasoniclpd-init if started
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service plymouth and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv:  loop involving service networking at depth 4
insserv:  loop involving service checkroot at depth 4
insserv:  loop involving service mountdevsubfs at depth 2
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service panasoniclpd-init and urandom if started
insserv:  loop involving service urandom at depth 4
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service plymouth and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: errore nell'elaborare il pacchetto cups-browsed (--configure):
 il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Segnalazione apport non scritta poiché è stato raggiunto il valore massimo di MaxReports
        Configurazione di unattended-upgrades (0.90ubuntu0.3)...
Si sono verificati degli errori nell'elaborazione:
 lightdm
 ifupdown
 apport
 apport-gtk
 cups-browsed
E: Sub-process /usr/bin/dpkg returned an error code (1)
antonio@antonio-EasyNote-TK85:~$
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 17:20

ho dovuto tagliare qualcosa,ma sono solo righe che si ripetono.
Cmq ha impiegato meno tempo e mi pare che vada meglio
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda daigo » domenica 15 gennaio 2017, 17:25

Codice: Seleziona tutto
sudo rm /var/lib/dpkg/info/lightdm.postinst
sudo rm /var/lib/dpkg/info/ifupdown.postinst
sudo rm /var/lib/dpkg/info/apport.postinst
sudo rm /var/lib/dpkg/info/cups-browsed.postinst

Codice: Seleziona tutto
sudo apt-get install -f
daigo
Tenace Tecnocrate
Tenace Tecnocrate
 
Messaggi: 18871
Iscrizione: maggio 2011

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 17:28

Codice: Seleziona tutto
antonio@antonio-EasyNote-TK85:~$ sudo apt-get install -f
[sudo] password di antonio:
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze       
Lettura informazioni sullo stato... Fatto
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
5 non completamente installati o rimossi.
Dopo quest'operazione, verranno occupati 0 B di spazio su disco.
Configurazione di lightdm (1.18.3-0ubuntu1)...
Configurazione di ifupdown (0.8.10ubuntu1.2)...
Configurazione di apport (2.20.1-0ubuntu2.4)...
Configurazione di apport-gtk (2.20.1-0ubuntu2.4)...
Configurazione di cups-browsed (1.8.3-2ubuntu3.1)...
antonio@antonio-EasyNote-TK85:~$
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 17:29

A questo punto pensi che il sistema dovrebbe funzionare?
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda daigo » domenica 15 gennaio 2017, 17:31

adesso mi pare tutto a posto, ha configurato tutto, prova ad avviare da quel kernel
daigo
Tenace Tecnocrate
Tenace Tecnocrate
 
Messaggi: 18871
Iscrizione: maggio 2011

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 17:32

Ci provo e ti faccio sapere.
Grazie molte
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 17:37

Hai risolto riparte bene senza più bloccarsi.
SEI UN GRANDE
GRAZIE MILLE

Adesso l'unica cosa che fa,ogni tanto mi si apre una finestra con dentro scritto
SI È VERIFICATO UN ERRORE. SEGNALARE
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda daigo » domenica 15 gennaio 2017, 17:56

di solito è apport che segnala errori a cavolo, se il sistema va bene, prova a disabilitare apport
Codice: Seleziona tutto
gksudo gedit /etc/default/apport
e alla riga enabled=1 imposta valore zero enabled=0 e fatta la modifica, salva il file e chiudilo e riavvia il sistema
daigo
Tenace Tecnocrate
Tenace Tecnocrate
 
Messaggi: 18871
Iscrizione: maggio 2011

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 17:58

Codice: Seleziona tutto
antonio@antonio-EasyNote-TK85:~$ gksudo gedit /etc/default/apport
Il programma "gksudo" non è attualmente installato. È possibile installarlo digitando:
sudo apt install gksu
antonio@antonio-EasyNote-TK85:~$



Che faccio installo?
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda daigo » domenica 15 gennaio 2017, 17:59

si
daigo
Tenace Tecnocrate
Tenace Tecnocrate
 
Messaggi: 18871
Iscrizione: maggio 2011

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 18:02

OK Fatto
ti faccio sapere se tutto va bene.

Grazie ancora
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda mai_nat » domenica 15 gennaio 2017, 18:04

O.T. grande @daigo; è un piacere vedere come tiri fuori dai casini le persone.
Seguendo i Tuoi interventi c'è sempre da imparare...
Sono "molto" in sintonia con le tue affermazioni:
L'é megio avei e braghe sguaræ 'nto cù che o cù sguaròu 'nte brâghe
end O.T.
mai_nat
Prode Principiante
 
Messaggi: 151
Iscrizione: ottobre 2012
Località: Rivoli TO
Desktop: Xfce/Mate
Distribuzione: Ubuntu 16.04 LTS x86_64
Sesso: Maschile

Re: linux 4.4.0.59 generic

Messaggioda tonipapa » domenica 15 gennaio 2017, 18:09

Vorrei chiudere con esito positivo questo post mettendo RISOLTO.
Come faccio?
tonipapa
Prode Principiante
 
Messaggi: 57
Iscrizione: marzo 2009

Re: linux 4.4.0.59 generic

Messaggioda giulux » domenica 15 gennaio 2017, 19:08

Se non hai più problemi modifica il titolo del prim post mettendoci davanti [Risolto].

Se vuoi puoi installare questo script che aggiunge un pulsante per mettere [Risolto] con un solo click, utile in future occasioni.
Ciao.
con l'aiuto della comunità le cose si mettono quasi sempre a posto (e non apposto), a parte (e non apparte) qualche caso ...
Avatar utente
giulux
Amministratore
Amministratore
 
Messaggi: 19546
Iscrizione: gennaio 2010
Località: Roma
Desktop: xubuntu - ubuntu gnome
Distribuzione: Ubuntu 16.04.1 LTS x86_64
Sesso: Maschile

Precedente

Torna a Kernel e servizi di sistema

Chi c’è in linea

Visualizzano questa sezione: 0 utenti registrati e 2 ospiti