Unusable desk pc
- Inicie sesión ou rexístrese para enviar comentarios
Hi to everyone!
Yesterday I have updated my 64 bit desk pc and it was all perfect. With the last updates of today the desk pc is unusable, even via LXTerminal. On the contrary, no problem with the last update of today on my old 32 bit notebook. Mystery of faith [to the free (as in freedom) software]!!
Is it perhaps a revision issue of the Ubuntu packages?
I am a translator!
> the desk pc is unusable, even via LXTerminal
I haven't noticed anything on my x86 laptop. What happens exactly?
I just installed etiona (mini) on a 32-bit notebook, the main things work but gajim and seafile seem not to work. Do you use any of them?
I installed trisquel mini in dual-boot with Parabola, but neither dino nor gajim work on Parabola for 32-bit computers (for some reason, the gssdp package in archlinux32 repository is old and gajim and dino use a function that does not exist in that version, there is a newer version in the testing repository, I assume it is because something is broken with it).
My problem is related to my X86_64 desk pc, not X86.
Are you talking about the following upgrade?
$ grep ^Upgrade /var/log/apt/history.log | tail -1
Upgrade: poppler-utils:amd64 (0.86.1-0ubuntu1, 0.86.1-0ubuntu1.1), gir1.2-gdkpixbuf-2.0:amd64 (2.40.0+dfsg-3ubuntu0.3, 2.40.0+dfsg-3ubuntu0.4), libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-3ubuntu0.3, 2.40.0+dfsg-3ubuntu0.4), gir1.2-poppler-0.18:amd64 (0.86.1-0ubuntu1, 0.86.1-0ubuntu1.1), libgdk-pixbuf2.0-bin:amd64 (2.40.0+dfsg-3ubuntu0.3, 2.40.0+dfsg-3ubuntu0.4), libgdk-pixbuf2.0-common:amd64 (2.40.0+dfsg-3ubuntu0.3, 2.40.0+dfsg-3ubuntu0.4), libpoppler-cpp0v5:amd64 (0.86.1-0ubuntu1, 0.86.1-0ubuntu1.1), libpoppler-glib8:amd64 (0.86.1-0ubuntu1, 0.86.1-0ubuntu1.1), libpoppler97:amd64 (0.86.1-0ubuntu1, 0.86.1-0ubuntu1.1)
You can execute the above command from a text session you log into after typing Ctrl+Alt+F2... or does these sessions fail too? If so, I doubt the upgrade caused the problem. Indeed, it only deals with Poppler and the Pibux GDK library. Poppler is a PDF rendering library. The GDK Pixbuf library deals with loading/scaling/animating images.
EDIT: I have just realized you are certainly referring to Trisquel 9, because you mention as well a 32-bit machine and Trisquel 10 does not support that architecture. Anyway, it is a good idea to log in a text session and take a look at the last upgrade you believe is the cause of your problem. If you cannot log in a text session, you can still read /var/log/apt/history.log from a live system, after mounting the partition hosting that file.
Hello! Yes,I use Trisquel 9 mini on my 64 bit desk pc. This is the output of the command " sudo apt update && sudo apt upgrade":
piriponzolo@Xxxxxxxxxxxx:~$ sudo apt update && sudo apt upgrade
[sudo] password di piriponzolo:
Errore:1 https://archive.trisquel.info/trisquel etiona InRelease
Risoluzione di "archive.trisquel.info" temporaneamente non riuscita
Errore:2 https://archive.trisquel.info/trisquel etiona-security InRelease
Risoluzione di "archive.trisquel.info" temporaneamente non riuscita
Errore:3 https://archive.trisquel.info/trisquel etiona-updates InRelease
Risoluzione di "archive.trisquel.info" temporaneamente non riuscita
Errore:4 https://archive.trisquel.info/trisquel etiona-backports InRelease
Risoluzione di "archive.trisquel.info" temporaneamente non riuscita
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Tutti i pacchetti sono aggiornati.
W: Impossibile recuperare https://archive.trisquel.info/trisquel/dists/etiona/InRelease Risoluzione di "archive.trisquel.info" temporaneamente non riuscita
W: Impossibile recuperare https://archive.trisquel.info/trisquel/dists/etiona-security/InRelease Risoluzione di "archive.trisquel.info" temporaneamente non riuscita
W: Impossibile recuperare https://archive.trisquel.info/trisquel/dists/etiona-updates/InRelease Risoluzione di "archive.trisquel.info" temporaneamente non riuscita
W: Impossibile recuperare https://archive.trisquel.info/trisquel/dists/etiona-backports/InRelease Risoluzione di "archive.trisquel.info" temporaneamente non riuscita
W: Impossibile scaricare alcuni file di indice: saranno ignorati o verranno usati quelli vecchi.
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Fatto
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
piriponzolo@Xxxxxxxxxxxx:~$
Thank you for the attention!
I am a translator!
Looks like you have a network problem, either network access or name resolution.
Can you access any non-local URL on a web browser?
What do "ping archive.trisquel.org" and "ping 209.51.188.51" say?
I wonder if this could be related to the systemd security update etiona got yesterday?
Update: Please share the recent lines at the update log at /var/log/apt/history.log
Ark74, I think you are right, it could be a problem of systemd update.
As by you requested,these are the last update lines:
Start-Date: 2022-09-14 08:58:23
Commandline: apt upgrade
Requested-By: piriponzolo (1000)
Upgrade: libsystemd0:amd64 (237-3ubuntu10.43, 237-3ubuntu10.56+9.0trisquel1), udev:amd64 (237-3ubuntu10.43, 237-3ubuntu10.56+9.0trisquel1), libudev1:amd64 (237-3ubuntu10.43, 237-3ubuntu10.56+9.0trisquel1), libudev-dev:amd64 (237-3ubuntu10.43, 237-3ubuntu10.56+9.0trisquel1), systemd-sysv:amd64 (237-3ubuntu10.43, 237-3ubuntu10.56+9.0trisquel1), libpam-systemd:amd64 (237-3ubuntu10.43, 237-3ubuntu10.56+9.0trisquel1), systemd:amd64 (237-3ubuntu10.43, 237-3ubuntu10.56+9.0trisquel1), libnss-systemd:amd64 (237-3ubuntu10.43, 237-3ubuntu10.56+9.0trisquel1)
End-Date: 2022-09-14 08:59:38
Magic Banana, Ark74
what is possible to do in order to solve this problem?
Understanding the problem is usually a necessary first step. You only wrote that "the desk pc is unusable". What exactly happens? Can you log into a text session (as I have already asked you)? Can you get a root terminal selecting a recovery entry in the menu of the bootloader. Have you taken a look at the logs with journalctl?
Magic Banana, I can now open LXTerminal, see, please, the outputs. And then? In my opinion the cause of this problem is systemd.
.jpg "15092022(001).jpg")
We already knew you cannot access Internet, at least through URLs. Any other problem? In https://trisquel.info/forum/unusable-desk-pc#comment-168347 Avron asked you questions (to see if it is a DNS issue) you have not answered. The following command aims to restart NetworkManager:
$ systemctl restart network-manager
Any error message if you do so?
In fact, as I have already suggested, errors reported by journalctl may identify the problem. To only see errors or worse (not warnings, notices, infos, etc.) of the current boot and write them to a file, here named "err":
$ journalctl -b -p 3 > err
After typing "systemctl restart network-manager" I have the same error.
Please take a look at these jpg files.
After typing "journalctl -b -p 3 > err", I have received a Leafpad file with the following content:
-- Logs begin at Wed 2022-04-20 23:10:35 CEST, end at Fri 2022-09-16 22:47:09 CEST. --
set 16 21:27:12 Reggiane-2005 kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared 5, ACPI requires 4 (20170831/nsarguments-198)
set 16 21:27:12 Reggiane-2005 kernel: ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dsfield-212)
set 16 21:27:12 Reggiane-2005 kernel: ACPI Error: Method parse/execution failed \_SB.PCI0._OSC, AE_ALREADY_EXISTS (20170831/psparse-550)
set 16 21:27:22 Reggiane-2005 [567]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6 1 3': No such file or directory
set 16 21:27:27 Reggiane-2005 systemd[1]: Failed to start AppArmor initialization.
set 16 21:27:38 Reggiane-2005 lightdm[1133]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
set 16 21:27:38 Reggiane-2005 lightdm[1133]: PAM adding faulty module: pam_kwallet.so
set 16 21:27:38 Reggiane-2005 lightdm[1133]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
set 16 21:27:38 Reggiane-2005 lightdm[1133]: PAM adding faulty module: pam_kwallet5.so
set 16 21:27:43 Reggiane-2005 lightdm[1340]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
set 16 21:27:43 Reggiane-2005 lightdm[1340]: PAM adding faulty module: pam_kwallet.so
set 16 21:27:43 Reggiane-2005 lightdm[1340]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
set 16 21:27:43 Reggiane-2005 lightdm[1340]: PAM adding faulty module: pam_kwallet5.so
set 16 21:27:44 Reggiane-2005 ntpdate[1352]: name server cannot be used: Temporary failure in name resolution (-3)
set 16 21:27:55 Reggiane-2005 pulseaudio[1614]: [pulseaudio] pid.c: Daemon already running.
set 16 22:05:13 Reggiane-2005 ntpdate[1919]: name server cannot be used: Temporary failure in name resolution (-3)
set 16 22:10:43 Reggiane-2005 [1987]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-8 1 4': No such file or directory
set 16 22:10:44 Reggiane-2005 kernel: sd 4:0:0:0: [sdc] No Caching mode page found
set 16 22:10:44 Reggiane-2005 kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through
set 16 22:15:16 Reggiane-2005 sudo[2068]: pam_unix(sudo:auth): conversation failed
set 16 22:15:16 Reggiane-2005 sudo[2068]: pam_unix(sudo:auth): auth could not identify password for [piriponzolo]
set 16 22:29:52 Reggiane-2005 [2159]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-8 1 5': No such file or directory
set 16 22:29:53 Reggiane-2005 kernel: sd 4:0:0:0: [sdc] No Caching mode page found
set 16 22:29:53 Reggiane-2005 kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through
.jpg "16092022(001).jpg")
.jpg "16092022(002).jpg")
.jpg "16092022(003).jpg")
.jpg "16092022(004).jpg")
.jpg "16092022(005).jpg")
.jpg "16092022(006).jpg")
As far as I see, we are talking about a Wi-Fi connection. Through USB? I ask because:
set 16 21:27:22 Reggiane-2005 [567]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6 1 3': No such file or directory
Does Ethernet work? It would also be useful to know whether the problem is only in name resolution: please reply to https://trisquel.info/forum/unusable-desk-pc#comment-168347
Among the errors, I do not think the ACPI ones explain anything network-related (they are probably bugs in firmware). Idem for the LightDM ones. That caught my attention:
set 16 21:27:27 Reggiane-2005 systemd[1]: Failed to start AppArmor initialization.
That command may tell us more about that:
$ journalctl -b -u apparmor
Yes, Magic Banana, I have a WI-FI connection through ThinkPenguin wireless long range N USB adapter, model TPE-N150USBL.
""I reply to https://trisquel.info/forum/unusable-desk-pc#comment-168347: Can you access any non-local URL on a web browser? What do "ping archive.trisquel.org" and "ping 209.51.188.51" say?""
No, I can't access to any non local URL on Abrowser. I don't know how to "ping archive.trisquel.org" and "ping 209.51.188.51".
Ethernet doesn't work. I think it is the moment "to plane" my desk pc with Pentium D and to install Trisquel 10 Mini. Thank you very much for your precious suggestions.
I don't know how to "ping archive.trisquel.org" and "ping 209.51.188.51".
They are commands to execute in a terminal. So is 'journalctl -b -u apparmor', by the way. But, sure, if you go for a fresh install of Trisquel 10, understanding the problem you face with Trisquel 9 is not of much practical interest anymore.
El 2022-09-18 09:02, name at domain escribió:
> ""I reply to
> https://trisquel.info/forum/unusable-desk-pc#comment-168347: Can you
> access any non-local URL on a web browser? What do "ping
> archive.trisquel.org" and "ping 209.51.188.51" say?""
>
> No, I can't access to any non local URL on Abrowser. I don't know how
> to "ping archive.trisquel.org" and "ping 209.51.188.51".
Open a terminal. Just press the right mouse button and choose open
terminal from the menu that comes up.
I have updated my etiona VM, and I can't reproduce the error.
By any chance, do you have broken packages?
Looks I don't have broken packages
I think it is the moment "to plane" my desk pc with Pentium D and to install Trisquel 10 Mini. Many thanks to everyone for the precious suggestions.
- Inicie sesión ou rexístrese para enviar comentarios