search

ConteZero / tw-updater-plasmoid

KDE Plasmoid software updater for openSUSE Tumbleweed
https://www.contezero.com/linux/kde-plasma-software-updater-opensuse-tumbleweed
GNU General Public License v2.0
12 stars 0 forks source link

Not working anymore #4

Open Cris70 opened 4 years ago

Cris70 commented 4 years ago

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.

~> zypper se -s tw-updater-plasmoid
Caricamento dati del repository in corso...
Lettura dei pacchetti installati in corso...

S  | Nome                | Tipo               | Versione   | Arch.  | Repository
---+---------------------+--------------------+------------+--------+---------------------
i+ | tw-updater-plasmoid | pacchetto          | 1.0.2-2.11 | x86_64 | home:alucardx:plasma
   | tw-updater-plasmoid | pacchetto sorgente | 1.0.2-2.11 | noarch | home:alucardx:plasma

~> cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20191016"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20191016"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20191016"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
LOGO="distributor-logo"
ConteZero commented 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.

Cris70 commented 4 years ago

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.

[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)
Cris70 commented 4 years ago

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

ConteZero commented 4 years ago

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.

ConteZero commented 4 years ago

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"

ConteZero commented 4 years ago

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?

Cris70 commented 4 years ago

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

ConteZero commented 4 years ago

When the update check is not running, the file /tmp/twupdater-check-xml-out is present in the system? (It should not)

Cris70 commented 4 years ago

It is not present

ConteZero commented 4 years ago

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?

ConteZero commented 4 years ago

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

ConteZero commented 4 years ago

From your log I've seen the package plasma5-session-wayland, are you using wayland with kde?

Cris70 commented 4 years ago

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.

Cris70 commented 4 years ago

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.

ConteZero commented 4 years ago

Try to update with zypper dup and then let me know if on following tumbleweed updates the applet has the same problem.

Cris70 commented 4 years ago

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.

ConteZero commented 4 years ago

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.

Cris70 commented 4 years ago

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