September 2020 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] Slow shutdown - "stop job running for /run/user/<user_id>"
by Rodney Baker 23 Sep '20

23 Sep '20

Hi all, For some time I've been seeing shutdown delays of up to 2min 30 sec on Tumbleweed. The system reports, "A stop job is running for /run/user/<user_id> min:sec (counting down)", where min:sec can be anywhere up to 2-3 minutes. Once this timer runs down, shutdown proceeds as normal. If I log out of the desktop session first, then log into a VTY session as root and enter "Poweroff", shutdown takes less than 10 seconds. My guess is that there is a race condition going on with some process still holding a file open in /run/user/<user_id> (whcih is a tmpfs file system, when the system is attempting to destroy it, but I have been so far completely unsuccessful in identifying what that could be. I've even tried enabling a debug terminal session on VTY9 but that's given no clue, either. How should I go about debugging this? So far, I don't even have enough information to raise a useful bug report (if one is even justified, given that it could be a local config issue rather than something systemic with Tumbleweed). Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker(a)iinet.net.au CCNA #CSCO12880208 ============================================================== -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

10 23

[opensuse-support] systemd-sysctl.service fails after todays update
by Peter Suetterlin 18 Sep '20

18 Sep '20

Hi, I just DUPed my TW system (from 20200906->20200916). During boot I could see some red lines, and indeed I get [FAILED] Failed to start Apply Kernel Variables. (first time this happens, following the logs). Likely related to this line in the journal(?): Sep 18 12:36:40 woodstock systemd-sysctl[291]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument Is that due to a change in the kernel (dup did move 5.8.4->5.8.7)? -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 2

Re: [opensuse-support] upgrade fails
by Tomas Kuchta 15 Sep '20

15 Sep '20

Doug, What time zone are you in? I am in PST at the moment - so if you are in US time - and willing to work out your issues over the on-line meeting - I would be happy to help. I do not use Tumbleweed, but I am pretty familiar with leap releases and general opensuse administration tools, documentation and troubleshooting. If that is something you would be interested in. Let me know off the list, so that we can organize how to connect. Tomas On Mon, Sep 14, 2020, 09:14 Tomas Kuchta <tomas.kuchta.lists(a)gmail.com> wrote: > > > On Mon, Sep 14, 2020, 02:57 Carlos E. R. <robin.listas(a)telefonica.net> > wrote: > >> On 14/09/2020 04.14, Doug McGarrett wrote: >> > On 9/13/20 8:43 PM, Darryl Gregorash wrote: >> >> On 2020-09-13 4:56 p.m., Doug McGarrett wrote: >> >>> On 9/13/20 6:04 PM, Knurpht-openSUSE wrote: >> >>>>>> Check your repos and remove the one that refers to the cd:/ or hd:/ >> >>>> >> >>> How do I do that, please? >> >> YaST/Software Repositories >> > 1. I found that file manager--a style of software editor I haven't seen >> > in about 20 years, and I forget how to use it. >> > I could not move the high-lighted line down to the one with cd in it, >> > and I wound up zapping the top three, >> >> Gosh. You just had to click with the mouse on the line having the CD. >> . >> > > Doug might be using yast instead of yast2. In that case mouse would not > help. > > > which I am sure is not good. However, the system is still working, so I >> > guess I haven't done any serious >> > harm. >> >> Yes you did, very serious damage. >> >> > 2. At the end of doing that, the zypper dub still wanted the 0824 disk. >> > I figured I have nothing to lose at this >> > point, so I put in the 0826 disk, and it was happy. This is probably >> > something that should be published in >> > large letters, somewhere: USE THE LATER DISK--IT WILL SATISFY THE >> > REQUIREMENT! >> >> And destroy your system. >> >> >

6 5

[opensuse-support] Re: openSUSE-RU-2020:1426-1: moderate: Recommended update for shim-leap
by Ralph 15 Sep '20

15 Sep '20

Hello! Why are the bugzilla reference links in this message all 'Access Denied'? Ralph On Tue, 15 Sep 2020 00:29:08 +0200 (CEST) maintenance(a)opensuse.org wrote: > openSUSE Recommended Update: Recommended update for shim-leap > ______________________________________________________________________________ > > Announcement ID: openSUSE-RU-2020:1426-1 > Rating: moderate > References: #1119762 #1119763 #1153953 #1174320 #1175626 > #1175656 > Affected Products: > openSUSE Leap 15.1 > ______________________________________________________________________________ > > An update that has 6 recommended fixes can now be installed. > > Description: > > This update for shim-leap fixes the following issues: > > Update shim to 15+git47-lp152.4.5.1 from openSUSE Leap 15.2 > > + shim-install: install MokManager to \EFI\boot to process the > pending MOK request (boo#1175626, boo#1175656) > > > - Update the path to grub-tpm.efi in shim-install (boo#1174320) > - shim-install: add check for btrfs is used as root file system to > enable relative path lookup for file. (boo#1153953) > - Update shim-install to handle the partitioned MD devices > (boo#1119762, boo#1119763) > - Update grub2 path in shim-install > > > Patch Instructions: > > To install this openSUSE Recommended Update use the SUSE > recommended installation methods like YaST online_update or "zypper > patch". > > Alternatively you can run the command listed for your product: > > - openSUSE Leap 15.1: > > zypper in -t patch openSUSE-2020-1426=1 > > > > Package List: > > - openSUSE Leap 15.1 (x86_64): > > shim-15+git47-lp151.2.11.1 > > > References: > > https://bugzilla.suse.com/1119762 > https://bugzilla.suse.com/1119763 > https://bugzilla.suse.com/1153953 > https://bugzilla.suse.com/1174320 > https://bugzilla.suse.com/1175626 > https://bugzilla.suse.com/1175656 > > -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

7 10

[opensuse-support] upgrade fails
by Doug McGarrett 14 Sep '20

14 Sep '20

Was trying to upgrade my OpsnSUSE-Tumbleweed, version 2020-0826, which is the install disk I have and used to create this system. Got message: Retrieving package boost-license1_71_0-1.71.0-9.5.noarch (654/729), 71.2 KiB ( 1.3 KiB unpacked) Failed to mount cd:/?devices=/dev/disk/by-id/usb-HL-DT-ST_DVDRAM_GP08LU11_P01090612025848-0:0 on /var/tmp/AP_0xFBhdmy: Mounting media failed (mount: /var/tmp/AP_0xFBhdmy: no medium found on /dev/sr0.) Please insert medium [openSUSE-20200824-0] #1 and type 'y' to continue or 'n' to cancel the operation. [yes/no] (no): n Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. linux1:~ # I obviously don't have the earlier medium. Is it now impossible to run the updates any more? What am I supposed to do? --doug -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 5

[opensuse-support] repositories from /home:/plater/
by Constant 13 Sep '20

13 Sep '20

Cannot remember when I started including the plater repositories in my repositories list but it has given me a stable result. Today I wanted to check for the latest update for my Tumbleweed when I found out that the platter list did not want to download the normal list but faulted with "dowbload. ...................... Retrieving: http://dowbload.opensuse.org/repositories/home:/plater/ Tumbleweed/repo/repoindex.xml?cookies=0 ........[done (1.2 KiB/s how may I contact plater?

6 11

[opensuse-support] where should .ppd files be put
by Doug McGarrett 12 Sep '20

12 Sep '20

I'm trying to install two printers, for which I have .ppd.gz files. The printers that apparently exist in TW dated 2020-0826 are mostly obsolete. There is nothing listed for Epson at all. It seems that in a previous generation of TW, there was at least a listing of my HP printer, and someone on the list pointed out where it was, but the Find Files app cannot find any other listing now. (There is only one HP--a color laser.) I need to install an HP LaserJet Pro M201dw and an Epson WP4530 all-in-one, including the scanner on it. All input greatly appreciated. --doug -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] leap 15.2 - what controls access from remote session (ssh/vnc) to local sound devices?
by tomas.kuchta.lists＠gmail.com 12 Sep '20

12 Sep '20

Hi, I am trying to play local sound initiated from remote shell (vnc and ssh). Imagine using headless PC connected to speakers. Can someone point me in the right direction as to what prevents the local audio devices being visible in vncserver on leap 15.*? All I see is dummy sound output device and I cannot make any sound through that. Thank you, Tomas -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

7 17

[opensuse-support] Where does Leap 15.2 store the UTC/local status of the bios clock?
by Carlos E. R. 11 Sep '20

11 Sep '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, In YaST we can configure whether the BIOS clock stores the local time or the UTC time. In the past, this status was stored in /etc/sysconfig/{something}. It is not there now - where is it? Background: <https://en.opensuse.org/SDB:Configuring_the_clock> - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX1oFJhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVC/0AoJUsm/E2tdwqgWgJ3TDR q/mhv9PBAJ9BNZOyp3tOrverPyal7HLdmuyTyA== =tW2K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

6 16

[opensuse-support] LEAP 15.2 - journald and udevd won't start after last update
by mh＠mike.franken.de 11 Sep '20

11 Sep '20

Hi *, yesterday I updated one of my LEAP 15.2 machines. The machine rebootet into maintenance mode afterwards, but I wasn't able to do anything, because the keyboard also wasn't functional. There were error messages on the console regarding systemd-journald and systemd-udevd, which both failed to start. I was not able to recover from this situation, except by recovering the machine from the latest backup. Afterwards everything was back to normal - the machine came up as usual. I then retried the update and saw, that systemd-journald and systemd-udevd even refused to restart during this update. So I have a running machine now without those services, but I suppose, it won't reboot any more as before. Both services gave errors like this: Main PID: 18098 (code=exited, status=228/SECCOMP) Is that only my machine that shows those errors? I didn't read anywhere here in the lists about a problem like that. The internet, though, lists a few occasions, where problems like that happened. Any idea, what to do besides recovering again and don't update for a while? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 4