openSUSE Users November 2021

users@lists.opensuse.org

52 participants
46 discussions

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Yesterday I wanted to update my small laptop (on Leap 15.2), and I connected it to the ethernet cable, but the laptop did not recognize it. If run "rcnetwork restart" it would appear, but would not connect to anything. At first I thought "dns trouble", but then I found that a ping 8.8.8.8 failed as well. I left it at that and switched ti WiFi, and performed the update, hoping that would cure the problem. Today I rebooted, with a newer kernel, and the cable connected from the start. After opening the desktop (I'm using Network Manager), I observed ini gkrellm that the interface eth0 was appearing and disapearing every minute or so. After a while, it became stable. It is not the cable, moving it has no effect. Message log: <https://susepaste.org/51821193> (I see the interface is going on and off again, in the log) Obviously, I have tried another cable, connected to another port of the switch. Same trouble. The switch led is solid green, but the computer does not see it. "rcnetwork restart" makes it appear with the correct IP, but a ping to the router (by number) fails. In fact, after removing the cable completely and issuing the command again, ifconfig reports that eth0 keeps the same address, but wlan has no address, and I can no longer connect to it. Ping to router from machine fails. Manually telling NM to dissconnect the ethernet (which cable was removed minutes ago) allows the wifi to work again. Second part of messages log: <https://susepaste.org/63312588> What is going on? This laptop worked previously, days ago. With the same cables. Another laptop works fine with one of those cables. - -- Cheers Carlos E. R. (from 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYZ4p/Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV3pAAn3ji0olpKPHiklGVVp/5 sPFsVbO9AKCV/fG9rlt9K0khax47qv2dswWz4g== =5vrF -----END PGP SIGNATURE-----

1 month, 4 weeks

[oS-en] time rarity

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I was running a backup job, and I timed it. The output is weird: (here some other times out of the screen, about 3 minute total) real 161m35.208s user 216m2.220s sys 36m30.599s real 10m27.555s user 14m33.090s sys 2m37.550s real 11m7.647s user 14m39.255s sys 1m55.313s total real 184m27.589s user 247m7.060s sys 41m20.225s Now, how can be the "real" time less than the user time? I don't remember seeing it before. It is happening on a new 15.2 install. Perhaps the sum of times on the two cores of the machine? In case the job is relevant, it is this: function hacer() { echo echo "Haciendo la particion $1 ($2) en $3" echo "copiando, comprimiendo, y calculando md5..." mkfifo mdpipe dd if=/dev/$1 status=progress bs=16M | tee mdpipe | pigz > $3.gz & md5sum -b mdpipe | tee -a md5checksum_expanded wait rm mdpipe echo "$3" >> md5checksum_expanded echo "Verificando..." pigz --test $3.gz echo echo "·········" } echo time hacer sda3 "161M" "sda3__Windows" echo time hacer sda4 "10M" "sda4__LENOVO" echo time hacer sda6 "11M" "sda6__LENOVO_PART" - -- Cheers Carlos E. R. (from 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYaFeeRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVZN8An3+T7XOnkPIYam64elLm zJIX5os5AJ9KGI+o0AZluPSZH1PhNsq5ds+JiQ== =MLSm -----END PGP SIGNATURE-----

1 month, 4 weeks

preserving a kernel

by George from the tribe

So I updated tumbleweed and now my bluetooth doesn't work. After some investigation, I plan to file a bug report. It seems the firmware worked with kernel 5.14, but now it doesn't work with 5.15. But for now, as long as I boot into the old kernel, I still can use my bluetooth headphones, and this is important for multiple applications. The kernel I want to use is the 2nd kernel in the list, which is 5.14. I want to preserve this kernel so that on future updates, if they have not solved the bug, the 15.4 kernel will be preserved, but the default kernel, which is 5.15, will be replaced by the next kernel update. Is there a way to do this? At one time in the past I expanded the number of kernels that were in the list of available kernels so that I kept like 6 kernels. I don't remember why I did that, and I don't need that many in any case. However, I don't know how to preserve just one kernel, so that that particular kernel won't be erased, but that updates for other kernels will still load and I will be able to try them. Any ideas? -- George Box: 15.2 | Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 15.2 | Plasma 5 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: TW | Plasma 5 | Core i7 | 64 | 16GB

2 months

puzzled by opensuse repo paths

by Istvan Gabor

Hello: In openSUSE 15.3 I see a lot of packages indicated by red text in Yast software manager. This lead me to check my configured repos and I am puzzled by what I found. For example I have configured openSUSE Leap 15.3 OSS update repo as: https://download.opensuse.org/update/leap/15.3/oss I checked the above path and found that is does not have the update packages. For example it does not have any kernel updates. But I have updated kernel package installed: kernel-default-5.3.18-59.27.1.x86_64 which is shown red in Yast software manager, indicating that I have no repo configured that has that package. The updated kernel package was installed by Yast Online Update Tool before I manually adjusted the repos (as I did before in earlier openSUSE versions). I am now puzzled by where the updated packages indicated by red text came from. Why not the update/leap/15.3/oss path contains these updates? Where can I find the Leap 15.3 specific updated repo? I see under opensuse/update/ path there are leap/ openSUSE-current/ openSUSE-non-oss-current/ openSUSE-stable/ tumbleweed/ tumbleweed-non-oss/ paths, but there are no version numbers given. What is stable, what is current? Where are they defined? Thanks, Istvan

2 months

Swapping ThinkPad drive

by James Knott

I've bought a 1 TB SSD drive to replace the 750 GB drive in my ThinkPad. I was considering using the opportunity to change to UEFI. I'll be mounting the old drive in an external case so that I can copy over the partitions, one of them NTFS. Anything I should worry about in converting to UEFI? Any suggestions? tnx jk

2 months

Tumbleweed: All windows start in lower right corner

by mh＠mike.franken.de

Hi *, since the before last Tumbleweed update every new window's lower right corner is set to the lower right corner of the actual screen - except for apps or windows for which I have defined special windows rules. Especially for Firefox and KMail this is really annoying. Any idea, what might cause this? TIA. Bye. Michael.

2 months

procno - like top, but not as we know it.

by Michael Hamilton

Is anyone you interested in a GUI process monitoring utility? I've been working on one for my own use. It as has somewhat similar aims as "top", but takes a different approach concentrating more on the "overview" and less on the numbers. I wanted to be more aware of processes that were active and their patterns of activity. I wanted desktop notifications for processes that consume resources excessively (PROCess NOtifications - procno). Procno partly hearkens back to the days of mainframes with rows of blinking lights. If that rings any bells for you, please have a look at: https://github.com/digitaltrails/procno There's a video and screen shot, so you need not waste much time reading. It's still a work in progress, but it does much of what I want. Development will likely slowdown from now on, perhaps adding more validation, or a few more features, such as a nice/renice control or more process info. BTW, procno is partly based on jouno (another pet project of mine). If you're interested in a "different" take on monitoring the journal, one that also makes use of desktop notifications, you should take a look at https://github.com/digitaltrails/jouno As explained at github, both of these are available as community packages at https://software.opensuse.org/ Both are just stand-alone Qt python scripts that can also just be grabbed from github (all the install options are explained at github). Enjoy, or not, as you see fit :-) Michael

2 months

Win 10 > Win 11 in VirtualBoz?

by Robin Klitscher

Running Virtual Box ver 6.1.30 in host Leap 15.2 with Win 10 as guest. Googling around produces much advice on installing Win 11 afresh in a VBox VM, but nothing about upgrading from Win 10 to Win 11 as one can do on original iron. Is the upgrade path in a VBox VM possible? If not at present, is it going to be? Anybody know???? -- Robin K Wellington "Harbour City" New Zealand

2 months

Tumbleweed 20211121 - No PIDs left to attach to the scope's control group, refusing: Success

by Michael Hamilton

Since updating to the latest TW 20211121 I've noticed some a new journal messages, three are logged for each occurrence of the issue: app-org.kde.kate-63c391d3ef34412d857871d30b4280c7.scope: No PIDs left to attach to the scope's control group, refusing: Success app-org.kde.kate-63c391d3ef34412d857871d30b4280c7.scope: Failed with result 'resources'. Failed to start Kate - Advanced Text Editor. The last is logged at priority 3, the first two at priority 4. The applications do start, despite the logged failure. This seems is happening with anything I start from the start-menu, or anything that gets started during session login. It doesn't happen if I start the same application from a shell. Is this a known new feature of 20211121? Can this be safely ignored? Full details from one of the messages: Journal Entry 2021-11-23 16:44:10.028759 CODE_FILE : src/core/scope.c CODE_FUNC : scope_start CODE_LINE : 378 MESSAGE : app-org.kde.kate-63c391d3ef34412d857871d30b4280c7.scope: No PIDs left to attach to the scope's control group, refusing: Success PRIORITY : 4 SYSLOG_FACILITY : 3 SYSLOG_IDENTIFIER : systemd TID : 1956 _CAP_EFFECTIVE : 0 _CMDLINE : /usr/lib/systemd/systemd --user _COMM : systemd _EXE : /usr/lib/systemd/systemd _GID : 500 _HOSTNAME : kosmos1 _PID : 1956 _SELINUX_CONTEXT : unconfined _SOURCE_REALTIME_TIMESTAMP: 2021-11-23 16:44:10.028724 _SYSTEMD_CGROUP : /user.slice/user-500.slice/user(a)500.service/init.scope _SYSTEMD_OWNER_UID : 500 _SYSTEMD_SLICE : user-500.slice _SYSTEMD_UNIT : user(a)500.service _SYSTEMD_USER_SLICE : -.slice _SYSTEMD_USER_UNIT : init.scope _TRANSPORT : journal _UID : 500 __REALTIME_TIMESTAMP : 2021-11-23 16:44:10.028759

2 months

YaST, zypper and packagekit

by J Leslie Turriff

I know how to use YaST and zypper to manage my software packages, but the other day I discovered that something called packagekit was also active on my system. (I have disabled it.) How does packagekit relate to YaST and zypper? Are they aware of each other? Does packagekit have access to my repository list, and does it update things in the background without my knowledge? I wonder, because my desktop has been behaving strangely, and a new release of it has been published, to which I have not yet explicitly upgraded. Leslie -- Distribution: openSUSE Leap 15.3 x86_64

2 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users November 2021