January 2021 - openSUSE Users - openSUSE Mailing Lists

pip and python packages without info
by Peter Suetterlin 07 Jan '21

07 Jan '21

Hi, I am installing (as user) some software via pip3. I noticed that it also installs some of the requirements into my private folder where I *do* have the respective software installed system-wide. In this case, notably the opencv package for python: speedy:~% rpm -q python3-opencv python3-opencv-4.5.0-3.19.x86_64 but speedy:~% pip3 list|grep cv speedy:~% So pip doesn't see that it is installed, and therefore downloads and installs a private version. I noticed that most python packages come with some egg-info, either a file or a directory. The opencv package doesn't have that. Is this the reason pip does not see the package? And if so, would this be a packaging error that asks for a bug report? Any other recommendations how to handle this? Right now I do a 'pip uninstall opencv-python' to get rid of the additional one... This is an oS Tumbleweed 20201228

2 2

Ouch KDE - Qt5 goes Closed-Source, Qt6 not ready... Bummer
by David C. Rankin 07 Jan '21

07 Jan '21

I follow this loosely, but... Yesterday, Qt 5.15 we closed source for LTS. Qt6 is not ready (not to mention binary backward compatibility will be broken with 6.1). What this means is there will be no further bug fix commits allowed to Qt5. So this leaves KDE in a bit of a pickle. https://go.reg.cx/tdml/dfd67/601ddbff/1720a1e6/3Y87 El Reg is on it... Anton's look for an alternative desktop may be well timed... -- David C. Rankin, J.D.,P.E.

2 1

Oops! Looks like LXQt and KDE have a problem
by Dave Howorth 05 Jan '21

05 Jan '21

"The Qt Company has followed up on its plan to make long-term support releases commercial-only by closing the source for 5.15 today, earning protests from open-source contributors" https://www.theregister.com/2021/01/05/qt_lts_goes_commercial_only/ "That's some brilliant timing, given that no actual qt 6 release even exists yet (yeah, 6.0 is a joke given that you intend to break binary compat in 6.1)," said one developer. Another said: "Qt6 has half of the modules required by my project not yet available, so upgrading is not possible. On the other hand, 5.15 LTS is closed for the open source users – this is quite a heavy restriction for me since my project is non-profit and open source. Buying a commercial license is not an option." Open-source contributor Thiago Macieira, an Intel software architect, said of the decision: "That means I will not be participating in the development of those fixes, commenting on what's appropriate or not, reviewing backports, or bug reports." "Tend to agree," said Konstantin Ritt, another developer.

1 0

GLIBC 2.27
by Bernd Ritter 05 Jan '21

05 Jan '21

Hello fellow chameleons and happy new year everyone, I use openSUSE Leap 15.2 for gaming. And since the new Ubuntu release more and more titles fail to start because they require a newer GLIBC version than openSUSE provides (2.26). Is there a way to upgrade it somehow without breaking all the other applications? I would have considered openSUSE TW but I like the stable part of the system for work and stuff. Cheers, Bernd

10 14

Kernel 4.x
by Alvin 05 Jan '21

05 Jan '21

Hello, I have an old Dell E521 (circa 2007) computer that I took out of storage. It has an nvidia geforce 8400 video card. I installed opensuse Leap 15.2 KDE, but the G03 driver isn't available for the stock 5.3 kernel. It's using the nouveau driver but that causes some weird screen blanking (even with XRenderer), random screen corruption and system freezes. I have used opensuse on it 10.0-11.3. Been so long I forget, but it has always been suse/opensuse. Is there a repo that I can use to downgrade the kernel to 4.3 (or any 4.x) that I can use with 15.2? I know it's a weird question, but I figure the machine is so old that it wouldn't benefit from any kernel after 4.x any way. Thanks. Alvin

5 6

grub boot from raid1 question
by Istvan Gabor 02 Jan '21

02 Jan '21

Hello: I would like to set up a Leap 15.1 system that boots from a md raid1 array. I have a sample configuration from a working debian system that boots from raid1 array. However there are 2 things in the sample configuration I don't understand. The working debian grub.cfg has this: ### BEGIN /etc/grub.d/10_linux ### menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-686-pae' --class debian --class gnu-linux --class gnu --class os { load_video insmod gzio insmod raid insmod mdraid1x insmod part_msdos insmod part_msdos insmod ext2 set root='(mduuid/4245........a8)' search --no-floppy --fs-uuid --set=root 68b........26e echo 'Loading Linux 3.2.0-4-686-pae ...' linux /boot/vmlinuz-3.2.0-4-686-pae root=UUID=68b........26e ro nomodeset quiet echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.2.0-4-686-pae } My questions: 1. It seems that grub sets the root device using the array's uuid (mduuid). Than it searches for file-system id, and sets the root to that file system. Isn't it enough to set the root using only one of these methods? Either by mduuid or by fs-uuid? Is it necessary to use both? What occurs if the the fs-uuid of the mduuid device's file system is not equal to the one given in the search command? 2. insmod part_msdos command is given 2 times. I guess it would be OK to use only once. Is this correct? Thanks, Istvan

3 7