Open Cris70 opened 4 years ago
It works in my system, please remove the comments from these lines in /usr/bin/zypper-dup-wrapper
# /bin/cp -p /tmp/twupdater-check-xml-out /tmp/twupdater-check-xml-out_${exitcode}_$(date +%Y-%m-%d.%H%M%S).log
and
# /bin/cp -p /tmp/twupdater-xml-out /tmp/twupdater-xml-out_${exitcode}_$(date +%Y-%m-%d.%H%M%S).log
Then some log file will be created in /tmp after execution with more info on what's happening.
Hi @ConteZero, here are my observations this morning.
I have the problem both on my desktop and on my laptop.
Yesterday I modified the zypper-dup-wrapper script on the desktop pc, but then I had no time to test.
This morning I modified that script on my laptop, but since plasma was already up and running (and thus the applet too) I do not have logs to show yet (I'll post them as soon as I can do a logout/login).
Anyway, here are some observations that may help.
~ > ps -ef|grep -i twupd
cristia+ 3628 2631 0 08:46 ? 00:00:00 tail -f -n +1 /tmp/twupdater-check-xml-out
cristia+ 3641 1 0 08:46 ? 00:00:00 SCREEN -d -m -S twupdater-zypper-dup pkexec /usr/bin/zypper-dup-wrapper check
root 3655 3642 0 08:46 pts/1 00:00:00 tee /tmp/twupdater-check-xml-out
cristia+ 12623 2918 0 09:01 pts/0 00:00:00 grep --color=auto -i twupd
~ > screen -ls
There is a screen on:
3641.twupdater-zypper-dup (Detached)
1 Socket in /run/uscreens/S-cristiano.
~ > screen -r 3641
<description>Codice di installazione del sistema come presente nei supporti di installazione.</description></solvable>
<solvable type="package" name="yast2-logs" edition="4.2.27-1.1" arch="x86_64" edition-old="4.2.24-1.1" arch-old="x86_64" summary="Scripts for handling YAST logs">
<description>Questo pacchetto contiene gli script per gestire i log di YAST.</description></solvable>
<solvable type="package" name="yast2-network" edition="4.2.23-1.1" arch="noarch" edition-old="4.2.19-1.1" arch-old="noarch" summary="YaST2 - configurazione di rete">
<description>Questo pacchetto contiene il componente YaST2 per la configurazione di rete.</description></solvable>
<solvable type="package" name="yast2-ntp-client" edition="4.2.5-1.1" arch="noarch" edition-old="4.2.4-1.1" arch-old="noarch" summary="YaST2 - configurazione del client NTP">
<description>Questo pacchetto contiene il componente YaST2 per la configurazione di client NTP.</description></solvable>
<solvable type="package" name="yast2-security" edition="4.2.4-1.1" arch="noarch" edition-old="4.2.3-1.1" arch-old="noarch" summary="YaST2 - configurazione della sicurezza">
<description>Il componente YaST2 per la configurazione delle impostazioni di sicurezza.</description></solvable>
<solvable type="package" name="yast2-storage-ng" edition="4.2.47-1.1" arch="x86_64" edition-old="4.2.46-1.1" arch-old="x86_64" summary="YaST2 - configurazione della memorizzazione">
<description>This package contains the files for YaST2 that handle access to disk
devices during installation and on an installed system.
This YaST2 module uses libstorage-ng.</description></solvable>
<solvable type="package" name="yast2-trans-en" edition="84.87.20191014.7227f0a5d8-1.1" arch="noarch" edition-old="84.87.20190929.78c47708d4-1.1" arch-old="noarch" summary="YaST2 - traduzioni inglesi">
<description>YaST2 - traduzioni in inglese.</description></solvable>
<solvable type="package" name="yast2-trans-en_US" edition="84.87.20191014.7227f0a5d8-1.1" arch="noarch" edition-old="84.87.20190929.78c47708d4-1.1" arch-old="noarch" summary="YaST2 - traduzioni">
<description>YaST2 - traduzioni per inglese americano.</description></solvable>
<solvable type="package" name="yast2-tune" edition="4.2.1-1.1" arch="x86_64" edition-old="4.2.0-1.1" arch-old="x86_64" summary="YaST2 - regolazione dell'hardware">
<description>Questo pacchetto contiene il componente YaST2 per la configurazione dell'hardware.</description></solvable>
<solvable type="package" name="yast2-update" edition="4.2.7-1.1" arch="x86_64" edition-old="4.2.6-1.1" arch-old="x86_64" summary="YaST2 - aggiornamento">
<description>Usare questo componente se si vuole aggiornare il sistema.</description></solvable>
<solvable type="product" name="openSUSE" edition="20191016-0" arch="x86_64" edition-old="20191014-0" arch-old="x86_64" summary="openSUSE Tumbleweed">
<description>openSUSE Tumbleweed is the rolling distribution by the openSUSE.org project.</description></solvable>
</to-upgrade>
</install-summary>
<prompt id="0">
<text>Continuare?</text>
<option default="1" value="s" desc="Si, accetta il riepilogo e procedi con l'installazione/rimozione dei pacchetti."/>
<option value="n" desc="No, annulla l'operazione."/>
<option value="v" desc="Alternare la visualizzazione delle versioni dei pacchetti."/>
<option value="a" desc="Alternare la visualizzazione delle architetture dei pacchetti."/>
<option value="r" desc="Alternare la visualizzazione dei repository dai quali saranno installati i pacchetti."/>
<option value="f" desc="Alternare la visualizzazione dei nomi dei fornitori dei pacchetti."/>
<option value="d" desc="Alternare tra la visualizzazione di tutti i dettagli e del minor numero di dettagli possibili."/>
<option value="g" desc="Visualizzare il riepilogo nel cercapersone."/>
</prompt>
n
</stream>
[screen is terminating] ~ > ps -ef|grep -i twudp cristia+ 22255 14565 0 09:03 pts/2 00:00:00 grep --color=auto -i twudp
- the "orb" continues spinning anyway
- here is what I find in /tmp:
~ > ll /tmp/tw* -rw-r--r-- 1 cristiano users 53149 21 ott 09.05 /tmp/twupdater-check-xml-out
- you can find the contents of that file attached here
Later I'll send you the logs.
Thank you in advance!
[twupdater-check-xml-out.zip](https://github.com/ConteZero/tw-updater-plasmoid/files/3749512/twupdater-check-xml-out.zip)
Here are a couple logs. First time I connected to the screen session and replied "n" to the prompt. Second time I connected to the screen session and replied "s" to the prompt. If I do not connect to the screen session and reply manually, the process remains stuck. twupdater-check-xml-out_0_2019-10-21.101314.zip twupdater-check-xml-out_4_2019-10-21.101125.zip
What happen after you manually replied? It continue to show the spinning wheel or it show the list of package to update?
I've updated with the applet some minutes ago without problems, it looks like in you system the screen session does not receive the messages sent from the applet.
During the initial check for updates the applet should send the following command to auto accept the default value:
screen -S twupdater-zypper-dup -p 0 -X stuff "^M"
The "^M" should be interpreted as the Enter key, but is possible that in your system it does not behave like it should. It could be related to charset configuration or something else, I really don't know. Can you try to send the previous command during the update check from a different console to see if it works?
It apparently works, as the screen session is ended upon executing that command. However, the applet does not show any updates, while 'zypper lu' is showing a lot of updates. Here are the logs in the /tmp directory:
~ > ll /tmp/twu* -art
-rw-r--r-- 1 cristiano users 56112 21 ott 10.11 /tmp/twupdater-check-xml-out_4_2019-10-21.101125.log
-rw-r--r-- 1 cristiano users 56604 21 ott 10.13 /tmp/twupdater-check-xml-out_0_2019-10-21.101314.log
-rw-r--r-- 1 cristiano users 56604 21 ott 11.55 /tmp/twupdater-check-xml-out_0_2019-10-21.115528.log
-rw-r--r-- 1 cristiano users 56604 21 ott 11.57 /tmp/twupdater-check-xml-out_0_2019-10-21.115736.log
The last two are from the tests I just did. I am attaching those. logs.zip
When the update check is not running, the file /tmp/twupdater-check-xml-out is present in the system? (It should not)
It is not present
Try to update from command line with zypper dup for now, perhaps an update to the latest Tumbleweed will solve the problem. Do you remember when it stopped working for you? Have you changed something in the system config or installed some new packages?
I've seen from your previous comments that your system is at version 20191016 but in the log it try to install
<solvable type="product" name="openSUSE" edition="20191016-0" arch="x86_64" edition-old="20191014-0" arch-old="x86_64" summary="openSUSE Tumbleweed">
It's not possible that a previous update was interrupted or not completed?
Can you try to execute:
rpm --rebuilddb
From your log I've seen the package plasma5-session-wayland, are you using wayland with kde?
I've seen from your previous comments that your system is at version 20191016 but in the log it try to install
<solvable type="product" name="openSUSE" edition="20191016-0" arch="x86_64" edition-old="20191014-0" arch-old="x86_64" summary="openSUSE Tumbleweed">
It's not possible that a previous update was interrupted or not completed?
Can you try to execute:
rpm --rebuilddb
It may be that I sent you some output that I had saved before the latest update. Anyway, just to be on the safe side, I rebuilt the rpm db as per your instructions, without problems.
From your log I've seen the package plasma5-session-wayland, are you using wayland with kde?
I've been willing to do some tests with Wayland, but I haven't managed to do so until now. I'm using plasma on X11.
Try to update with zypper dup and then let me know if on following tumbleweed updates the applet has the same problem.
Updating did not improve the situation. However, on my laptop I was able to fix the problem by uninstalling and reinstalling tw-updater-plasmoid.
On my desktop however the problem was worse (though the plasmoid showed the orb spinning, there was no process behind it) and I have been unable to fix it by unistalling/reinstalling. I'll try again later and I'll let you know.
On your desktop pc verify if you have some packages installed from different repositories that could cause problems.
You can also try to create a new temporary user with a clean kde profile to see if it makes difference.
Delete /tmp/twupdater* files if they exist.
Hi, I was able to fix it on the desktop too:
Now it works ok. Let's see if the problem resurfaces later... hope not! Thank you
The plasmoid is not working anymore since a few days. If you expand it, you always see the "checking" animation. If you connect to the screen sessions, you see zypper is stuck on a question that does not get answered automatically.