- openSUSE Support

15.4 RC suddently asks for decision on suse packages signing key when going into yast2 online_update_configuration gui?
by cagsm 18 May '22

18 May '22

Support, a freshly updated 15.4 RC (via zypper dup some day(s) ago) suddenly asks for a decision on this suse packages signing key in yast2 module when going into the online update configuration gui. what the heck? YaST2 - online_update_configuration @ tux01 Loading the Package Manager... x Load Sources => Refresh Sources - Rebuild Cache - Load Data ┌──────────────────────────────────────────────────────────────────────────────────────────────────┐ │┌──────────────────────────────────┐ Import Untrusted GnuPG Key │ ││The owner of the key may ┬ The following GnuPG key has been found in repository │ ││distribute updates, packages, and │ Update repository with updates from SUSE Linux Enterprise 15│ ││package repositories that your │ (http://download.opensuse.org/update/leap/15.4/sle/) │ ││system will trust and offer for │ ┌──────────────────────────────────────────────────────────┐│ ││installation and update without │ │ID: 70AF9E8139DB7C82 ─│ ││any further warning. In this way, │ │Name: SuSE Package Signing Key ││ ││importing the key into your │ │Fingerprint: FEAB 5025 39D8 46DB 2C09 61CA 70AF 9E81 39DB ││ ││keyring of trusted keys allows the┴ └──────────────────────────────────────────────────────────┘│ ││key owner to have a certain amount│ You can choose to import it into your keyring of trusted │ ││of control over the software on │ public keys, meaning that you trust the owner of the key. │ ││your system. │ You should be sure that you can trust the owner and that │ ││ │ the key really belongs to that owner before importing it. │ ││A warning dialog opens for every │ │ │└──────────────────────────────────┘ [Trust] [Cancel] │ └──────────────────────────────────────────────────────────────────────────────────────────────────┘ Downloading: 3 KiB/s (on average 3 KiB/s) - http://download.opensuse.org/update/.../repodata/repomd.xml i have not clicked or selected anything i only fired up yast2 and went into that module to check the state of online updates and if they were configured etc. what now? why? :( what IS the advices and best practices work flow actually for the END USER on these matters deciding about keys and their acceptance and trust when messing or just working with the normal default repos on the various opensuse leap systems? I just fail to understand how a normal user would need to make up decisions of trust and everything that goes into this. I am very dissatistfied with these matters :( frustrated. ty.

1 0

Re: OBS build failure w/o code change
by Axel Braun 17 May '22

17 May '22

Hello Bernhard Am Dienstag, 17. Mai 2022, 17:23:51 CEST schrieben Sie: > I've seen this kind of stuck jobs a couple of times in the past years. > Just running the job will very likely succeed. > > Not sure about the reason, but the following seems to give a hint: > > [ 5439s] or the build host has a kernel or hardware problem... this occurs as well on localhost. As Andreas wrote, this started some ~2 month ago, after it initially build fine (otherwise it would not make its way into Factory). Cheers Axel

1 0

Shrink an resize of file systems
by Axel Braun 17 May '22

17 May '22

Hi, I would like to collect some ideas about shrinking and resizing (expanding) of file systems. Background: On a SD card, e.g. 16GB for a Raspi, the last partition is empty for the most part: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 14,8G 0 disk ├─mmcblk0p1 179:1 0 64M 0 part ├─mmcblk0p2 179:2 0 2G 0 part └─mmcblk0p3 179:3 0 12,8G 0 part resize2fs -M should do the job of manual shrinking (in case of ext4) When the system is started again, the file system should be automatically expanded to the max available size on the SD card. Any proposal how to achieve this? Thanks Axel

5 4

15.4 beta, every few days updates trickle in, how and why are these packages released?
by cagsm 17 May '22

17 May '22

Support, ever since my trial with 15.4 beta clean install, there were a few packages that only gotton installed hours days etc after the initial deployment of 15.4beta. why where these packages trickling into this system, I had thought the publishing concept was to release a beta and then again the whole deal of packages for RC stage and for final goldmaster or something? was the set of packages for beta not very much completed or released as whole as these select packages came trickling in? ty

3 2

TW fish filesystem bug in Dolphin.
by Ariez Vachha - openSUSE 17 May '22

17 May '22

TW fish filesystem bug in dolphin. Dolphin tries to open directories such as conf.d as a regular file when clicked on. Navigating via the address bar works fine. The underlying sshfs fused filesystem is working fine i.e. F4 open terminal in Dolphin and changing directory works fine. How to reproduce: 1. Open fish://server.com/some-dir/ 2. Open directory with .d extension by clicking Expected result; directory opens in dolphin Observed result; dolphin tries to open the directory as a regular file. Regards, Ariez ajv(a)opensuse.org

1 1

Re: 15.4 Beta - cancelling "zypper se" with [ctrl + c] SEGFAULTS ??
by Felix Miata 16 May '22

16 May '22

David C composed on 2022-05-16 16:07 (UTC-0500): > This was unexpected (to me), but may be normal. Canceling "zypper se" with > [ctrl + c] results in a Segmentation Fault. E.g. > $ zse octabe > ^C^CSegmentation fault > (I meant to type octave, but had a typo so I canceled the search) > Shouldn't the interrupt handler in zypper handle this in a more graceful way? > The 'zse' alias for users is: > alias zse='sudo zypper se -s' > (not sure whether that would make any difference, but included anyway) Happened to me less than an hour ago running up, with 200 packages remaining to update/grade. No damage found. # inxi -SIaz System: Kernel: 5.14.21-150400.19-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: root=LABEL=<filter> ipv6.disable=1 net.ifnames=0 noresume mitigations=auto consoleblank=0 Desktop: Trinity v: R14.0.12 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0 vt: 7 dm: TDM Distro: openSUSE Leap 15.4 Beta Info: Processes: 161 Uptime: 0h 4m wakeups: 174 Memory: 1.8 GiB used: 411 MiB (22.3%) Init: systemd v: 249 runlevel: 5 target: multi-user.target tool: systemctl Compilers: gcc: N/A Packages: N/A note: see --pkg Shell: Bash v: 4.4.23 running-in: konsole pinxi: 3.3.15-14 -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

1 0

Not receiving emails from lists since 5 May
by Ianseeks 16 May '22

16 May '22

HI I've not received any emails from Factory or Support since 5th May. Have i missed something that changed on that date? I've checked the lists and emails are going to it but i'm not picking them up. Lists like kdepim-users seem to work ok. regards Ian -- opensuse:tumbleweed:20220502 Qt: 5.15.2 KDE Frameworks: 5.93.0 - KDE Plasma: 5.24.4 - kwin 5.24.4 kmail2 5.20.0 (22.04.0) - akonadiserver 5.20.0 (22.04.0) - Kernel: 5.17.4-1-default - xf86-video-nouveau: 1.0.17

3 5

Persistent problem with filesystem-84.87-4.2.x86_64 on Tumbleweed Update
by Gokul Chittaranjan 15 May '22

15 May '22

I get an error (which is ignored every time I do zypper dup) that's given below. How do I fix this issue? error: unpacking of archive failed on file /var/mail;6280971a: cpio: File from package already exists as a directory in system error: filesystem-84.87-4.2.x86_64: install failed ( 48/479) Installing: filesystem-84.87-4.2.x86_64 ..............................................................[error] Installation of filesystem-84.87-4.2.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): i

2 1

what is the best practices work flow on pgp pubkeys handling when adding repos?
by cagsm 12 May '22

12 May '22

I was adding some non default repos on 15.4 just recently, and zypper ar .... comes up with three fold question on whether to add some gpg key temporary or decline or add permanently or something. some longer key fingerprint is given. how are the users supposed to check? also I still fail to understand where one can actually find this key with a second alternate means, I often try to fetch them from pgp.mit.edu but which is often overloaded and barely gives out suse build infrastructure keys. I often submit suse keys there whenever they are lacking them at mit. anyhow as far as I remember there are some pubkeyfiles in the repo itself where zypper and rpm and whatnot fetch the keys from, but where else are they originally to be found? what would be the primary source for these projects and subprojects and buildinfrastructure etc? is there a pgp keyserver at opensuse actually for all their projects and users and staff keys and so on? what is the way a normal user is to behave with that zypper user dialog or also yast dialogs when adding repos, be it open/suse public pgp keys or others? how are you guys doing this step of establishing and verifying trusts? ty

2 1

KOTD for or on 15.4, what are the great many directories in the repo and what about optionals and extra?
by cagsm 10 May '22

10 May '22

Support, trying to figure out the KOTD stuff, extra repository URL etc. <https://en.opensuse.org/openSUSE:Kernel_of_the_day> speaks about .../HEAD/standard but there are many more and other path names on that repo over there even though I only see 15.2 as directory name so even 15.3 is missing, but maybe due to more and better ties to SLES and whatnot? and there is no 15.4 directory there also what about the additional kernel-default-.... ...-extra and ....-optional packages that are also installed on a leap 15.4 system, and the many -firmware packages as well? the wiki KOTD article speaks about the other way of also installing just the single .rpm of kernel-default towards the end of the article, I wonder what happens with the -extra and -optional packages in such a situation then? Can anyone explain a few bits about the KOTD repo its folders and how this works approximately? ty lots.

2 1