March 2021 - openSUSE Users - openSUSE Mailing Lists

Sharing same /home/<user> directory
by Frans de Boer 11 Mar '21

11 Mar '21

LS, Has anyone experience with using a shared home directory while using different versions of OpenSuse (Leap and TW)? After all, having a working TW is great, but sometimes you need a fallback, for which I use one of the Leap15.x versions. I already use the same directories for Firefox and Thunderbird and as long as the versions under the various OpenSuse versions do not differ to much from each other, it works. The above approach is to avoid setting-up filters and other parameters each time there is a new version. However, I do notice some differences under - for instance - Ksysguard. Representing correct voltages (.sgrd file is always reset) is not working under Leap 15.1, 15.2. So, for those instances I needed to adjust the startup sequence to keep a working display under TW. So, maybe there are more issues, of which I am currently not aware? Regards, Frans. -- A: Yes, just like that A: Ja, net zo Q: Oh, Just like reading a book backwards Q: Oh, net als een boek achterstevoren lezen A: Because it upsets the natural flow of a story A: Omdat het de natuurlijke gang uit het verhaal haalt Q: Why is top-posting annoying? Q: Waarom is Top-posting zo irritant?

6 8

Update from Leap 15.0 to 15.2
by Terry Eck 11 Mar '21

11 Mar '21

Is it possible to do an update (without complete reinstall)? Thanks, Terry Eck

8 12

15.3 boot problem
by Mark Misulich 11 Mar '21

11 Mar '21

Hi, I'm having trouble getting a 15.3 installation to boot properly. I've tried it two different ways on two installation locations on the hard drive, and it has failed to boot either time. The installation is with KDE desktop environment in both cases. I'll just detail the first case in this thread, and when it gets fixed I'll diferentiate it from the second case and tackle it to get it working too. I installed 15.3 from a dvd iso that I downloaded and used Suse Studio Imagewriter to write it to a USB stick. I haven't had a problem installing the image to the hard drive, but when I have finished and try to start the new installation from the hard drive, it doesn't boot properly. I installed / to one partition, /home to another partition, and /boot to another small partition. All of the installation partitions are ext4. The bios is set to bios boot (legacy). The boot loader is Grub2 and the master boot record is on /dev/sda. I have several other installed and working linux operating systems in this way and Grub 2 recognizes all of them and they boot normally (including an operating 15.2 system on this computer; I'm using it to write this thread). But I haven't had to include a separate /boot partition in the past on any of the other distros that I have installed previously. When I try to boot the 15.3 system, it boots up to terminal. I am able to log in as user, then to try to get the graphical system up I have typed tried several methods that I researched in the forum or otherwise online, but the only one that works is "sudo startx". After typing in the root password, the graphical desktop environment starts (KDE), but it starts in the wrong resolution. It comes up in 640x480 resolution, and there is no graphical selection to change it to the screen's native resolution of 1366x768 in System Settings>Display configuration. I thank you in advance for your input to correct what I'm doing wrong, and allow me to fix this issue. Mark

9 25

Supported way, ala 'zypper dup' not working...what does it need?
by L A Walsh 10 Mar '21

10 Mar '21

On 2021/02/23 01:46, Simon Lees wrote: > On 2/23/21 5:31 PM, L A Walsh wrote: > >> Simon Lees wrote: >> >>> http://download.opensuse.org/distribution/leap/15.0/repo/oss/x86_64/rpm-4.1… >>> >> --- >> >> Another FWIW, I working on my download script being workable >> with leap-15.0 .... >> > > Well the supported way to update a system is `zypper dup` we will make > sure that works there should rarely be a need for an openSUSE user to > call rpm directly, especially when installing / removing / upgrading > packages. > ---- Well, having pulled down that repo and the files in oss/repodata (repomd.xml, primary.xml, et al) I pointed zypper's "add-repo" with the "--check" flag at the 'repo', but it seems to be missing something: > sudo zypper up Error building the cache: [Leap15.0_OSS|file:/home/cache/suse/distribution/leap/15.0/repo/oss] Valid metadata not found at specified URL Warning: Skipping repository 'Leap15.0_OSS' because of the above error. Error building the cache: [Leap15.0_oss_src|file:/home/cache/suse/source/distribution/leap/15.0/repo/oss/] Valid metadata not found at specified URL Warning: Skipping repository 'Leap15.0_oss_src' because of the above error. Loading repository data... Reading installed packages... Nothing to do. ====== I tried tracing zypper's actions, but don't see any attempt to open any files (or any failures associated with such): # strace -ff -e open zypper up |& more strace: Process 72710 attached [pid 72710] +++ exited with 0 +++ --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=72710, si_uid=0, si_status=0, si_utime=1, si_stime=0} --- strace: Process 72711 attached strace: Process 72712 attached [pid 72712] +++ exited with 0 +++ [pid 72711] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=72712, si_uid=0, si_status=0, si_utime=56, si_stime=16} --- [pid 72711] +++ exited with 0 +++ --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=72711, si_uid=0, si_status=0, si_utime=0, si_stime=0} --- Error building the cache: [Leap15.0_OSS|file:/home/cache/suse/distribution/leap/15.0/repo/oss] Valid metadata not found at specified URL Warning: Skipping repository 'Leap15.0_OSS' because of the above error. Error building the cache: [Leap15.0_oss_src|file:/home/cache/suse/source/distribution/leap/15.0/repo/oss/] Valid metadata not found at specified URL Warning: Skipping repository 'Leap15.0_oss_src' because of the above error. Loading repository data... Reading installed packages... Nothing to do. +++ exited with 0 +++ ---- What files is zypper trying to find that are missing? It doesn't seem to be trying to open any files (!!?)...I'm not sure why strace isn't showing any open file attempts, though I admit to being a novice on using the "-e open" switch to limit filtering to open calls. Still any idea what files it might be wanting? It's not very specific... Thanks...

5 8

How do you handle high utimes with patches coming in, replacing libraries and gui parts - odd highlevel application behaviors
by cagsm 10 Mar '21

10 Mar '21

Hi there all hello list dwellers, i am not very fluent on the gui side of opensuse. When using current opensuse 15.2 systems but also in the years before, every now and then some test machine, simple standard kde gui level opensuse installation, no fancy setups. having such a machine on and up a long time, a kde user logged in, the screen locked, e.g. simple kde desktop gui application itself (dunno whats it even called or concepts for sure, think: this plasma desktop and whatever), eventually this kind of a system become erratic on its gui side of things. revisiting such a machinery, unlocking the desktop shows mess e.g. in a left open firefox gui, tabs becoming unklickable unchangeable, for example mething i remember a situation (dont really take my word for this everything as 100% but you get the idea, roughly ballpark, anyways continue the story) that i could still surf and use that one tab of that fricken firefox, but pretty much everything of it in the sense of frames, borders, resizing, moving around or its menues and elements that (my understanding of it, over the somewhat lengthy experience i myself had in the unix world, all about window managers, gui layers of the linux universe and such stuff) are triggering the operating system layers and libraries.... so these libariers might get exchanged and replaced by up- and in-coming opensuse patches, they get applied so far so fine. I always admired the unix world for being kind of able to overwrite and replace of nearly almost everything in its way in some still working healthy stable ways. in stark contrast to the windows world. so anyhow, these recent years i work myself the gui parts of linux a bit, and i kind of see (or guess) the downsize of all this. so these high level applications such as the desktop plasma application itself and the firefoxen for example, become erratic, only parts of them staying up working, the rest refusing their parts of work. during such times, only a restart of a mal functioning firefox helped, or even a restart of the display.service via systemctl, or even a reboot of a whole machine if that hadnt helped. i figured that it was some very deep down libraries or when kernel updates itself become applied, i think kernel packages also bring in files where some select externalized drivers reside and so on. So simple question is, how do other gui opensuse users live with this. How do you have a nice and incomplicated life where your desktop machine just continues to work. Recently whenever resorting to opensuse, I sometimes think, I reboot the opensuse at a higher frequency than some average windows machine (just kidding, no seriously, you like reboot windows at least once a month when the nightmare microsoft update day finally has arrived or you forced or lulled yourself into allowing yourself to go down that path). Anyone experience same erratics every now and then with high long uptime opensuse machines with gui usage? Is this a know behavior of opensuse, or am I doing it wrong? If the stuff is normal, can one resort to some replace-in-use-files in a different manner, that might avoid such behavior of the high level apps? After reboots and restarts of the various possible layers of the opensuse system, stuff comes back working normally. I observe this type of incidents with the gui opensuse machine, when I forget coming back to it for a number of weeks. Mostly I am still able to work around the little mess with it, sometimes I end up needing to reboot the machine in the end after all. Thanks for your insights on this matter on how you lead a long uptime and happy life with your gui opensuse system. TY.

6 6

Handbrake
by Stakanov 09 Mar '21

09 Mar '21

is there a reason why handbrake vanished for all versions of opensuse?

5 13

Static IP For Container in Rootless Pod? And Other n00b Questions
by colony.three＠protonmail.ch 09 Mar '21

09 Mar '21

Just hand-built a pod from the docker-compose.yaml for mailu/postfix. But two problems: - Is the correct way to set the CIDR for a pod: --network=slirp4netns:cidr=10.2.21.0/24 ? - One of the containers in the pod is unbound, which provides DNS for the other containers. So it must have a static IP, but in pod run --ip= does not work. "Error: invalid config provided: rootless containers and pods cannot be assigned static IP addresses" What do you do about this? - How does unbound get its queries out of the pod to an authoritatative nameserver? - The pod is not auto-starting on boot. There is no --restart-always when creating a pod, so systemd? -

2 2

Leap 15.0 oss repo w/odd location (boot/x86_64) for a font repo in primary.xml
by L A Walsh 08 Mar '21

08 Mar '21

In the repodata dir for the oss repo, the primary.xml file usually lists all the packages and their locations for that repo. In the repo D/l area, its listed as some long hex# "<hex#>-primary.xml.gz" in the "oss/repodata/" dir. The rpm package referred to is has name "arphic-uming-fonts" of type "noarch". Files in the oss repo are in the x86_64 or noarch subdirs. One file, a chinese font file (that usually would be under 'noarch') is under "oss/boot/x86_64/". 1) why is a file in the oss repo referring to a "boot" dir? 2) why is a font under an x86_64 dir (under a boot dir) instead of a 'noarch' dir? 2a) Does it have executable code in the rpm package? (unlikely) But why, at least, not under "boot/noarch", but that is given that it is also under some dir named 'boot'. Weird location: <location href="boot/x86_64/arphic-uming-fonts.rpm"/> I don't know about anyone else, but if I look for a pkg in a distro, I usually look under 'oss/x86_64|noarch', never under 'oss/boot/x86_64' for a package with no ver/rel in its pathname. Other data in primary.xml indicates it's version is: <version epoch="0" ver="0.2.20080216.1" rel="lp150.1.7"/> Anyway, likely no big deal, but seemed odd.

4 4

kDE3 resolution problem in Leap 15.2
by Carl Spitzer {L Juno} 08 Mar '21

08 Mar '21

has anyone found a solution for the limits Leap has for KDE3 resolution. Seems to have a silly limit of 1024x768 which is nonsense. I have more than that on a monitor on my achient HP Kayak which runs 10.0 and Legacy DOS/Win311. Sorry if this is the wrong place but no sign of the KDE3 list for a month now. CWSIV ____________________________________________________________ Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=rss_tag… Prosecutor About Doctor: 'Basically, He's a Serial Killer' http://thirdpartyoffers.juno.com/TGL3131/6045781618dee78153112st04duc1 On the Hunt for an Animal Serial Killer http://thirdpartyoffers.juno.com/TGL3131/604578163d19f78153112st04duc2 Buyers Bid Millions For Jack Dorsey's First Tweet http://thirdpartyoffers.juno.com/TGL3131/60457816614bf78153112st04duc3

5 11

packman for 15.1
by jdd＠dodin.org 07 Mar '21

07 Mar '21

Hello :-) I see that there are problem since the migration with packman. For some reasons my main computer is still under Leap 15.1. Is packman still available for this old version and is 15.1 already out of support? thanks jdd -- http://dodin.org

3 3