May 2021 - openSUSE Support - openSUSE Mailing Lists

A stop job is running ......
by Robin Klitscher 13 May '21

13 May '21

If this has been asked before, I’ve missed it and apologise. It’s certainly been asked elsewhere, though with no clear answer. Frequently, but not always, when closing (or rebooting) Leap 15.2, the shutdown stalls for 90 seconds with a message “A stop job is running for Session 2 of user <xxxx>”, together with a register counting down from 1 minute 30 seconds. When the countdown reaches zero the shutdown completes. There’s no other diagnostic information. I can’t invoke a terminal at that point to establish what’s what. But I have captured what could be useful info with systemctl -b -<x> across boots/shutdowns. Case 1. Excerpt from journal, “clean” shutdown, no significant delay: May 09 13:58:02 Corgi systemd[1]: Started Session 2 of user robin. May 09 15:08:45 Corgi systemd[1]: Stopping Session 2 of user robin. May 09 15:08:45 Corgi systemd-logind[1108]: Session 2 logged out. Waiting for processes to exit. May 09 15:08:48 Corgi systemd[1]: Stopped Session 2 of user robin. Case 2. Excerpt from journal, shutdown with "stop job running" and 90-sec delay: May 09 15:09:52 Corgi systemd[1]: Started Session 2 of user robin. May 09 15:15:51 Corgi systemd[1]: Stopping Session 2 of user robin. May 09 15:15:51 Corgi systemd-logind[1064]: Session 2 logged out. Waiting for processes to exit. May 09 15:17:21 Corgi systemd[1]: Stopped Session 2 of user robin. The timestamps of the last two lines in Case 1 show an inconsequential 3 second delay. Those for Case 2 show the full 90 second wait, seeming also to finger systemd-logind as the culprit. The most common suggestion in other forums is to reduce the default for DefaultTimeoutStopSec in /etc/systemd/system.conf from 90 seconds to 10. This works, but it only addresses the symptom, not the cause. Assuming the problem does lie somehow with systemd-logind on shutdown, is there something else I can do to fix it? Anyone? -- Robin K Wellington "Harbour City" New Zealand

6 9

Question for Asian font user.
by Stakanov 08 May '21

08 May '21

I am using in my emails (kmail) normally the default (noto I think). But recently I am getting mails from a HK provider using html mail with a story part in mandarin. While the normal writing is "beautified" easily by using e.g. AR PL Sungtil GB, the mail itself, using html, is apparently not making reference to this setting. So the letters are ugly and primitive (looking like hit into stone by some caveman) So: is there a way to influence how Kontact/Kmail renders 汉语 embedded in html with the font of my choice? And where would be that setting? Would that be "QT web engine"? Thank you in advance.

1 0

Reporting saved kernel logs on system that stalls during boot?
by -pj 05 May '21

05 May '21

I am wondering if it would be possible to maybe get a couple of pointers on what to do next as far as a bug report. I don't know if it is correct to ask more questions in Bugzilla at this point. First off the bug report is here: -> https://bugzilla.opensuse.org/show_bug.cgi?id=1185542 My computer was able to boot fine with kernel 5.11.16-1-pae I was asked to install kernel-default for testing purposes 5.12.1-1.g9bb8944-default which I did. kernel-default failed to boot. So now 3 kernels are installed/listed in the bootmenu as follows. 1. 5.12.1-1.g9bb8944-default 2. 5.12.0-2-pae 3. 5.12.0-1-pae kernel 5.11.16-1-pae <- Is now gone. Computer is unable to boot to splash screen with any of the 3 above listed kernels. It makes little/some sense since in /etc/zypp/zypp.conf - line 554 multiversion.kernel the kernel 5.11.16-1-pae must have been removed <- I do not understand though because when I installed KOTD the 5.11.16-1-pae was the running kernel. Quoting the bug report now as per Comment #7 is as follows: "OK, thanks, then it's a generic problem of 32bit Intel kernel. Feel free to uninstall kernel-default again. Now, we need more details about the crash. Any chance that you have the relevant kernel Oops or panic in the saved kernel logs? Or if not, try to boot without quiet boot option, and check whether you get the stack traces on screen, and take a picture. That's often helpful as a start.". What does the kernel Oops or saved kernel logs mean? I have the openSUSE https://en.opensuse.org/openSUSE:Report_a_YaST_bug#How_can_I_setup_network_… 1. Is this y2logs? What is the best way to retrieve these logs that are needed? 2. I do not want to install the operating system again as it will not help the situation at all most likely. 3. Sometimes I do get stack traces on the screen and am not booting with quiet boot option I believe. 4. I decided to take a photo of the "stack traces" and I have attached the image to this email. 5. The 32 bit computer does have 4 gigabytes of memory installed. <- Do not know if that was necessary to say. :| I would really appreciate your input as I am quite inexperienced with this situation. I think it would be really neat to get some of the bugs fixed for 32 bit TW for the: Dual Core model: Intel T2400 bits: 32 type: MCP arch: M Yonah rev: 8 cache: L2: 2 MiB flags: nx pae sse sse2 sse3 vmx bogomips: 7314 Speed: 997 MHz min/max: 1000/1833 MHz Core speeds (MHz): 1: 997 2: 997 -Best Regards

6 11

Availability of old Leap repositories on download.opensuse.org
by Robert Munteanu 05 May '21

05 May '21

Hi, I have some woefully out of date machines that I can't upgrade right now. I noticed that, thankfully, older Leap repositories are still available from [1] . Is there a policy on how long they are kept or at least an intent to announce removal in advance? I'd like to know if I should preemptively mirror those repos. Thanks, Robert [1]: https://download.opensuse.org/distribution/leap/

2 2

Re: Reporting saved kernel logs on system that stalls during boot?
by Carlos E. R. 05 May '21

05 May '21

On 05/05/2021 02.12, -pj wrote: > On 5/4/21 3:26 PM, Carlos E. R. wrote: >> On 04/05/2021 22.07, -pj wrote: >>> I am wondering if it would be possible to maybe get a couple of pointers >>> on what to do next as far as a bug report. I don't know if it is correct >>> to ask more questions in Bugzilla at this point. >>> >>> First off the bug report is here: -> >>> https://bugzilla.opensuse.org/show_bug.cgi?id=1185542 >>> >>> My computer was able to boot fine with kernel 5.11.16-1-pae >>> >>> I was asked to install kernel-default for testing purposes >>> 5.12.1-1.g9bb8944-default which I did. kernel-default failed to boot. >>> >>> So now 3 kernels are installed/listed in the bootmenu as follows. >>> >>> 1. 5.12.1-1.g9bb8944-default >>> 2. 5.12.0-2-pae >>> 3. 5.12.0-1-pae >>> >>> kernel 5.11.16-1-pae <- Is now gone. Computer is unable to boot to >>> splash screen with any of the 3 above listed kernels. It makes >>> little/some sense since in /etc/zypp/zypp.conf - line 554 >>> multiversion.kernel the kernel 5.11.16-1-pae must have been removed <- I >>> do not understand though because when I installed KOTD the 5.11.16-1-pae >>> was the running kernel. >>> >>> Quoting the bug report now as per Comment #7 is as follows: >>> "OK, thanks, then it's a generic problem of 32bit Intel kernel. >>> Feel free to uninstall kernel-default again. >>> >>> Now, we need more details about the crash. Any chance that you have the >>> relevant kernel Oops or panic in the saved kernel logs? Or if not, try >>> to boot without quiet boot option, and check whether you get the stack >>> traces on screen, and take a picture. That's often helpful as a start.". >>> >>> What does the kernel Oops or saved kernel logs mean? I have the openSUSE >>> https://en.opensuse.org/openSUSE:Report_a_YaST_bug#How_can_I_setup_network_… >>> >>> >>> >>> >>> 1. Is this y2logs? What is the best way to retrieve these logs that are >>> needed? >> >> No. Those are the YaST logs. >> >> >> >> You first run: >> >> journalctl --list-boots >> >> For this to work, the directory "/var/log/journal/" must exist. If it >> doesn't, create it, for the next time. > > Great..I see here: -> > https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-re… > > "section 11.1:". Which is the best way to perform this step (due to > having kernels that are not allowing boot to Splash screen or desktop)? > Will I need to create a Rescue-CD perhaps so that I can check for this > "/var/log/journal" directory? I do see "C: Command Line E: Edit Entry" > at the bottom left corner of the "boot menu" screen. It is far simpler than all that: you just boot the kernel that works, and ask journalctl to display the log of one, two, three boots before. The only condition is that "/var/log/journal" directory must exist before you start testing. If it doesn't, as you are already using the machine, just create the directory when the machine is running. After you create the directory you have to attempt to boot the kernel that fails so that it log things - if it gets far enough to write anything. (I see you had to take photos instead) > > 1. Is it best in my reply here to snip off the remainder (bottom > portion) of this message before sending? Yes :-) -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)

1 0

gimp
by Simon Becherer 05 May '21

05 May '21

Hi, i do support for some older people, - since years. they like to have a more easy graphic program as gimp is. - they remember the "paint shop pro" in dos days. (maybe its also not so easy in this days if it is still available) the functions who would neccesarry would be: 1) make a collage from a couple of pictures (put them together) (and rotate) 2) cut of people from pictures (or other parts from pictures) an put them to a other picture. did anybody here know some easy program who is able to do this? simoN -- www.becherer.de

4 4

openSuse 15.2: What is the intended way to stop Package kit nagging
by TomasK 04 May '21

04 May '21

What is the intended way to stop Package kit nagging user(s) in KDE and openSuse 15.2? This started with openSuSE 15.2 and it has reached critical mass today - so this is sort of SOS before I take hammer at it an uninstall packageKit "with all of its dependencies". What I mean by nagging: 1. Requests for Admin privileges in KDE to refresh repositories - I do not know how to stop this without breaking anything else. 2. KDE notifications - I disabled those in KDE - so no probs here. The setup is remote multi user (do I need to say that) VNC server with long-ish uptime - typically few weeks until it needs critical updates. Thank you, Tomas

5 11