https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c1 --- Comment #1 from Fritz Hudnut --- Back in TW today zypper running 247 packages . . . ran through fast and no problems with using GUI while running the update as was the case with Leap 15.5 the other day. Same machine . . . same drive. SSD sata. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 Chenzi Cao changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |libzypp Assignee|screening-team-bugs@suse.de |zypp-maintainers@suse.de -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c4 --- Comment #4 from Fritz Hudnut --- Michael: Thanks for the reply . . . zypper-log was apparently already installed, but running your command brought back "nothing found"?? I opened the /var/log/zypper.log and it showed a bunch of data from the 21st, tried to attach it and the server could not complete the action?? Tried it twice. I'll try again later . . . . -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c6 --- Comment #6 from Michael Andres --- @Fritz, maybe the file is too big. Bugzilla AFAIK has a 10M limit for uploads. If that's the reason, you can use `split` to cut the file into pieces. Then it should be possible to attach each part individually via the `Add an attachment` link abobe yout initial description. To spit the file:

cd /tmp cat /var/log/zypper.log | gzip | split -b 10M --additional-suffix=-zypper.log.gz

The created pieces will be named like this:

xaa-zypper.log.gz xab-zypper.log.gz xac-zypper.log.gz ...

-- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c8 --- Comment #8 from Michael Andres --- Not sure if I understood you correctly. Maybe a permission issue:

# ls -l /var/log/zypper.log -rw-r----- 1 root root <SIZE> <DATE> /var/log/zypper.log ^^^ (u)ser (AKA owner) permission ^^^ (g)roup permission ^^^ (o)thers permission

Per default the logfile has 'rw' permission for user 'root' (only 'r'ead permission for group 'root') and no permission for other users. If you are logged in as an 'ordinary' user your browser may indeed not be allowed to read the file. If you can 'cat' the file, then this shell is running as user 'root'. You can check this by using the 'id' command:

# id uid=0(root) gid=0(root) groups=0(root)

As user 'root' you are the owner of the file and you can grant read access to other users by using 'chmod' (adding (+r)ead permission for (o)thers):

# chmod o+r /var/log/zypper.log

Check it wit 'ls'; the additional 'r' indicates read access for other users:

# ls -l /var/log/zypper.log -rw-r--r-- 1 root root <SIZE> <DATE> /var/log/zypper.log

Now you should be able to access the file from within your browser. (After some while the system may reset the permission to it's default. If you want to do this manually after you uploaded the file: 'chmod o-r /var/log/zypper.log') -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c10 --- Comment #10 from Fritz Hudnut --- Michael Andres: Thanks for the ownership hints . . . I did think that was why it was working, but didn't know how to change it in the terminal . . . . -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c12 --- Comment #12 from Fritz Hudnut --- Michael A: So, the only compressed file is from 11/21 ?? named zypper.log-20221121.xz and there is the "log file" which you say isn't showing much data. The problem with the GUI "freezing" is still continuing . . . happened again last night, had to use the power button to shut it down. It's not a RAM issue, machine has 16 GB RAM . . . and "free -h" supports that: [CODE]# zypper log -l LOOGFILE ================================================================================ Collect from LOOGFILE ... No such file No files to collect! '/usr/sbin/zypper-log' exited with status 1 # zypper log -l LOGFILE ================================================================================ Collect from LOGFILE ... No such file No files to collect! '/usr/sbin/zypper-log' exited with status 1 # free -h total used free shared buff/cache available Mem: 15Gi 1.7Gi 13Gi 34Mi 1.1Gi 13Gi Swap: 14Gi 0B 14Gi -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c14 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #14 from Michael Andres --- (In reply to Fritz Hudnut from comment #12)

[CODE]# zypper log -l LOOGFILE

Sorry, LOOGFILE was meant to be a placeholder for the real filename:

# zypper log -l zypper.log-20221121 |prefix ================================================================= Collect from zypper.log-20221121 ...

TIME PID VER CMD 2022-10-21 17:11 2176 1.14.57 zypper ref 2022-10-21 17:12 2308 1.14.57 zypper dup -l 2022-10-21 17:32 15584 1.14.57 zypper dup -l 2022-10-24 07:44 6397 1.14.57 sudo zypper ref 2022-10-24 07:44 6428 1.14.57 sudo zypper dup -l 2022-10-30 17:39 2874 1.14.57 zypper ref 2022-10-30 17:40 3106 1.14.57 zypper dup -l 2022-10-30 17:52 10281 1.14.55 zypper ref 2022-10-30 18:04 22102 1.14.55 zypper ref 2022-10-30 18:04 22132 1.14.55 zypper dup -l 2022-10-30 18:14 20743 1.14.55 zypper clean --all 2022-10-30 18:15 20786 1.14.55 zypper ref 2022-10-30 18:17 737 1.14.55 /usr/bin/zypper -n purge-kernels 2022-11-07 07:58 8738 1.14.55 zypper ref 2022-11-07 07:58 8768 1.14.55 zypper dup -l 2022-11-14 07:53 6526 1.14.55 sudo zypper ref 2022-11-14 07:53 6558 1.14.55 sudo zypper dup -l 2022-11-14 08:51 740 1.14.57 /usr/bin/zypper -n purge-kernels

-- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c16 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #16 from Michael Andres --- Created attachment 863319 --> https://bugzilla.suse.com/attachment.cgi?id=863319&action=edit Execution times of the install steps

2022-11-14 07:53 6558 1.14.55 sudo zypper dup -l

2022-11-14 07:53:54 - zypper start 2022-11-14 07:55:14 - install start 2022-11-14 08:18:17 - install end So we have less than 2 min. for solving and downloading 184 packages. 23 min. for installing the packages, BUT only 2 actions took long: - 9 min for installing kernel-default-5.14.21-150500.34.1.x86_64 - 8 min for %posttrans of grub2-i386-pc-2.06-150500.15.1.noarch The remaining 182 packages took 6 min. That's not too bad. Whether kernel-default/grub2-i386-pc were responsible for the slow UI is something I cant tell. Both tasks are known to consume memory and CPU power, but this should not persist until reboot. The log at least contains no hint to a problem the installer had recognized. An by now We did not receive any similar reports. The log lets me assume that you are using xfce? If that's right we can move the bug to the xfce maintainers. Maybe they have some more ideas on how to check the reason for the slow UI. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c18 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |Xfce Assignee|zypp-maintainers@suse.de |bnc-team-xfce@forge.provo.n | |ovell.com Summary|Running zypper dup -l in |[XFCE] Running zypper dup |Leap 15.5 freezes GUI |-l in Leap 15.5 freezes GUI --- Comment #18 from Michael Andres --- Maybe the XFCE maintainers can help to figure out what slows down XFCE so badly. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c20 Maurizio Galli changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maurizio.galli@suse.com --- Comment #20 from Maurizio Galli --- Tumbleweed Xfce is fine for me and I am not able to reproduce the issue. Unfortunately I don't have a chance to test Leap 15.5 on baremetal at the moment -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1205452 https://bugzilla.suse.com/show_bug.cgi?id=1205452#c22 --- Comment #22 from Fritz Hudnut --- (In reply to Stefan Seyfried from comment #21)

Things I have seen in the past: Updates of font packages cause the X server to basically stall for quite some time, especially (this is a guess) on older/slower CPUs and graphics adapters.

This lead to display "hangs" of about a minute without content updates, don't remember if the mouse pointer still moved. A text console login showed, that the xorg processes were consuming lots of CPU. AFAIR the update process continued in the background, it was just no progress visible on the desktop.

So especially if this is an "older" machine where this happens, just waiting longer for it to finish would be my first option. In order to debug this, I would have a ready-logged-in text console handy and in case the GUI hangs would check if the last installed packages (should be visible in journal or with "rpm -qa --last|head" are font packages indeed.

I'm not sure who is "to blame" for this issue, if it is the X server dynamically reloading the changed fonts or the graphics toolkits, but that's a secondary question, once you find out it is actually the same problem I was seeing.

@maurizio: OK, well, this is Leap 15.5 XFCE, whether the XFCE is relevant or not is another story . . . . I have several rolling tumbleweed based systems and no issues there on the same machine . . . . '12 cMP i7 4core @stefan s: Yes, in the long history of using XFCE, back to approx '07 or earlier, there has been issues of GUI "freezing" . . . in PPC based systems, etc. This is longer than 1 minute AND can not get to a TTY from with the freeze . . . . -- You are receiving this mail because: You are on the CC list for the bug.