September 2021 - openSUSE Users - openSUSE Mailing Lists

Leap 15.2 no GUI login screen
by Mark Hounschell 24 Sep '21

24 Sep '21

This is a system that was just updated from leap-15 using proprietary nvidia drivers to leap-15.2 using nouveau drivers. It was done using the "zypper dup" method. When I boot to level-3 then login as user, I can startx and I have my desktop. Where the GUI login screen usually is is just my mount pointer. I'm pretty sure I got rid of all the nvidia stuff. The nouveau kernel driver is loaded. #journalctl shows a problem but what do I do to fix it. Sep 24 14:44:04 harley sddm-greeter[1500]: failed to acquire GL context to resolve capabilities, using defaults.. Sep 24 14:44:05 harley sddm-greeter[1500]: Adding view for "DVI-I-1" QRect(0,0 1600x1200) Sep 24 14:44:05 harley sddm-greeter[1500]: Loading file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml... Sep 24 14:44:05 harley sddm-greeter[1500]: failed to acquire GL context to resolve capabilities, using defaults.. Sep 24 14:44:05 harley sddm-greeter[1500]: Adding view for "DVI-I-2" QRect(1600,0 1600x1200) Sep 24 14:44:05 harley sddm-greeter[1500]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Sep 24 14:44:05 harley systemd[1]: Created slice system-systemd\x2dcoredump.slice. Sep 24 14:44:05 harley systemd[1]: Started Process Core Dump (PID 1578/UID 0). Sep 24 14:44:05 harley sddm-helper[1485]: [PAM] Closing session Sep 24 14:44:05 harley sddm-helper[1485]: pam_unix(sddm-greeter:session): session closed for user sddm Sep 24 14:44:05 harley sddm-helper[1485]: [PAM] Ended. Sep 24 14:44:05 harley sddm[1451]: Auth: sddm-helper exited with 6 Sep 24 14:44:05 harley sddm[1451]: Greeter stopped. Sep 24 14:44:05 harley systemd-logind[754]: Session 1 logged out. Waiting for processes to exit. Sep 24 14:44:05 harley systemd-logind[754]: Removed session 1. Sep 24 14:44:05 harley systemd-coredump[1579]: Process 1500 (sddm-greeter) of user 461 dumped core. Stack trace of thread 1500: #0 0x00007fb209545420 raise (libc.so.6) #1 0x00007fb209546a01 abort (libc.so.6) #2 0x00007fb209f647fb _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) #3 0x00007fb20c1654cd _ZN13QSGRenderLoop28handleContextCreationFailureEP12QQuickWindowb (libQt5Quick.so.5) #4 0x00007fb20c1662bd n/a (libQt5Quick.so.5) #5 0x00007fb20c16705a n/a (libQt5Quick.so.5) #6 0x00007fb20a775675 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5) #7 0x00007fb20c1e4a45 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5) #8 0x00007fb20a163328 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #9 0x00007fb20a76b5ea _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5) #10 0x00007fb20a76b83d _ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE (libQt5Gui.so.5) #11 0x00007fb20a74523b _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5) #12 0x00007fb1ffe451da n/a (libQt5XcbQpa.so.5) #13 0x00007fb2059cf624 g_main_context_dispatch (libglib-2.0.so.0) #14 0x00007fb2059cf9c0 n/a (libglib-2.0.so.0) #15 0x00007fb2059cfa4c g_main_context_iteration (libglib-2.0.so.0) #16 0x00007fb20a1c03af _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #17 0x00007fb20a16157a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #18 0x00007fb20a16a780 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #19 0x000055aebca19a2d main (sddm-greeter) #20 0x00007fb20953034a __libc_start_main (libc.so.6) #21 0x000055aebca19e3a _start (sddm-greeter) Stack trace of thread 1573: #0 0x00007fb209602759 syscall (libc.so.6) #1 0x00007fb209f8a794 _ZN10QSemaphore7acquireEi (libQt5Core.so.5) #2 0x00007fb1f746ab9a n/a (libQt5HunspellInputMethod.so.5) #3 0x00007fb209f880b2 n/a (libQt5Core.so.5) #4 0x00007fb206fee754 n/a (libGL.so.1) #5 0x00007fb2080164f9 start_thread (libpthread.so.0) #6 0x00007fb209607ecf __clone (libc.so.6) Stack trace of thread 1502: #0 0x00007fb2095fd5fb __poll (libc.so.6) #1 0x00007fb2059cf939 n/a (libglib-2.0.so.0) #2 0x00007fb2059cfa4c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb20a1c03af _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007fb20a16157a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007fb209f8690a _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007fb1ff914e65 n/a (libQt5DBus.so.5) #7 0x00007fb209f880b2 n/a (libQt5Core.so.5) #8 0x00007fb206fee754 n/a (libGL.so.1) #9 0x00007fb2080164f9 start_thread (libpthread.so.0) #10 0x00007fb209607ecf __clone (libc.so.6) Stack trace of thread 1572: #0 0x00007fb2095fd5fb __poll (libc.so.6) #1 0x00007fb2059cf939 n/a (libglib-2.0.so.0) #2 0x00007fb2059cfa4c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb20a1c03af _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007fb20a16157a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007fb209f8690a _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007fb20c0fe686 n/a (libQt5Quick.so.5) #7 0x00007fb209f880b2 n/a (libQt5Core.so.5) #8 0x00007fb206fee754 n/a (libGL.so.1) #9 0x00007fb2080164f9 start_thread (libpthread.so.0) #10 0x00007fb209607ecf __clone (libc.so.6) Stack trace of thread 1501: #0 0x00007fb2095fd5fb __poll (libc.so.6) #1 0x00007fb20bd80307 n/a (libxcb.so.1) #2 0x00007fb20bd81f3a xcb_wait_for_event (libxcb.so.1) #3 0x00007fb1ffe44130 n/a (libQt5XcbQpa.so.5) #4 0x00007fb209f880b2 n/a (libQt5Core.so.5) #5 0x00007fb206fee754 n/a (libGL.so.1) #6 0x00007fb2080164f9 start_thread (libpthread.so.0) #7 0x00007fb209607ecf __clone (libc.so.6) Stack trace of thread 1577: #0 0x00007fb20801c87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fb209f8f1fb _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5) #2 0x00007fb209f8f509 _ZN14QWaitCondition4waitEP6QMutexm (libQt5Core.so.5) #3 0x00007fb1d7313c5b n/a (libqmlfolderlistmodelplugin.so) #4 0x00007fb209f880b2 n/a (libQt5Core.so.5) #5 0x00007fb206fee754 n/a (libGL.so.1) #6 0x00007fb2080164f9 start_thread (libpthread.so.0) #7 0x00007fb209607ecf __clone (libc.so.6) Stack trace of thread 1575: #0 0x00007fb2095fd5fb __poll (libc.so.6) #1 0x00007fb2059cf939 n/a (libglib-2.0.so.0) #2 0x00007fb2059cfa4c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb20a1c03af _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007fb20a16157a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007fb209f8690a _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007fb20b533565 n/a (libQt5Qml.so.5) #7 0x00007fb209f880b2 n/a (libQt5Core.so.5) #8 0x00007fb206fee754 n/a (libGL.so.1) #9 0x00007fb2080164f9 start_thread (libpthread.so.0) #10 0x00007fb209607ecf __clone (libc.so.6) Stack trace of thread 1504: #0 0x00007fb2095fd5fb __poll (libc.so.6) #1 0x00007fb2059cf939 n/a (libglib-2.0.so.0) #2 0x00007fb2059cfa4c g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb20a1c03af _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007fb20a16157a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007fb209f8690a _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007fb20b533565 n/a (libQt5Qml.so.5) #7 0x00007fb209f880b2 n/a (libQt5Core.so.5) #8 0x00007fb206fee754 n/a (libGL.so.1) #9 0x00007fb2080164f9 start_thread (libpthread.so.0) #10 0x00007fb209607ecf __clone (libc.so.6) Stack trace of thread 1574: #0 0x00007fb20801c87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fb209f8f1fb _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5) #2 0x00007fb209f8f509 _ZN14QWaitCondition4waitEP6QMutexm (libQt5Core.so.5) #3 0x00007fb1d7313c5b n/a (libqmlfolderlistmodelplugin.so) #4 0x00007fb209f880b2 n/a (libQt5Core.so.5) #5 0x00007fb206fee754 n/a (libGL.so.1) #6 0x00007fb2080164f9 start_thread (libpthread.so.0) #7 0x00007fb209607ecf __clone (libc.so.6) Stack trace of thread 1576: #0 0x00007fb209602759 syscall (libc.so.6) #1 0x00007fb209f8a794 _ZN10QSemaphore7acquireEi (libQt5Core.so.5) #2 0x00007fb1f746ab9a n/a (libQt5HunspellInputMethod.so.5) #3 0x00007fb209f880b2 n/a (libQt5Core.so.5) #4 0x00007fb206fee754 n/a (libGL.so.1) #5 0x00007fb2080164f9 start_thread (libpthread.so.0) #6 0x00007fb209607ecf __clone (libc.so.6) Any ideas? I see nothing abnormal in /var/log/Xorg.0.log Thanks Mark

2 6

problem with install of openSUSE-Tumbleweed-DVD-x86_64-Snapshot20210916-Media.iso
by George R Goffe 24 Sep '21

24 Sep '21

Hi, I just got through the install of this iso. There is a problem though. I can not login. I think I'm using the right password but the tty(?) is behaving as though the typmatic keys are on steroids. When I type one character many characters appear, sometimes MANY MANY appear. I'm VERY new to Tumbleweed and do not know what to do. Can I get some help with this please? Best regards and STAY SAFE! George...

1 0

Multiple monitors in oS 15.3
by Roger Oberholtzer 23 Sep '21

23 Sep '21

We have generally had no trouble setting up multiple monitors on openSUSE. It has been working for quite a while. I have a oS 15.3 install with KDE and an intel GPU. On this computer, booting, say, 42,3 works perfect in this respect. However, on 15.3, the settings for multiple displays do not stay after logging out. All is always set back to just using the display in HDMI1. The other two on HDMI2 and HDMI3 are forgotten. I have to fiddle with the group and then the three displays are available for arrange. But all is gone after a logout/login. I see this bug: https://bugs.kde.org/show_bug.cgi?id=436648 Could this be what is happening here? I don't see a solution. But it sounds like it is in the same area. Does anyone else have an issue with multiple monitors (settings not remembered across logins) in oS 15.3 and KDE? -- Roger Oberholtzer

1 2

TW with kernel 5.14.5 can't detect Realtek network devices
by Ariez Vachha - openSUSE 23 Sep '21

23 Sep '21

Folks! Did the upgrade latest TW upgrade with kernel 5.14.5 - Does not recognise either my Ethernet or Wifi devices. I have used grub to boot back to Kernel: 5.14.2-1-default. "hwinfo --network" only returns the loopback!!! Waiting for Realtek r8168 Ethernet and rtw89pci Wifi modules on Sauerland hardware repo, but I wonder if this will work if the kernel can't even detect the HW. Anyone else had this problem? -- Regards, Ariez ajv(a)opensuse.org

2 5

replacing RAID drive
by George from the tribe 23 Sep '21

23 Sep '21

So I have had these 2 drives in RAID 1 configuration for 5 separate partitions on each drive. It was a holdover to previous linux versions - one of the partitions was an installation of opensuse 13.2! Well, one of the hard drives failed, putting all 5 RAIDed partitions into degraded status. So I thought, what the heck, these drives are 5 years old, I am just going to replace both hard drives instead of only the one that failed, and at the same time upgrade them from 1TB size to 2TB size since they are so cheap now. The challenge was, one of the RAID partitions was also my root partition. So I bought the 2 new drives, and took out the old failed drive, and started the process. My plan was to put in the new 2TB drive, partition it with 4 of the 5 partitions (I certainly don't need 13.2 anymore), hook them to the RAID arrays, wait until they sync, then reboot to check that it works. Reinstall grub on the new drive, then remove the 2nd old drive (the one that works), and reboot to check that I can boot up on the new drive, now with all 4 partitions running in degraded RAID configuration. Then, once that is verified to work, put in the 2nd new drive, partition it, add the new partitions to the RAID arrays, and then be back up and running. I ran into a bit of a problem on the way, though everything is finally resolved, but it raised a question I hope someone can answer. After I had connected the 1st new drive to the RAID arrays, I did this: - I went to a terminal and installed grub on the 1st new drive, - modified fstab to make sure all the appropriate partitions would be loaded and removed the calls to the older drive, - modified the mdadm.conf file to have it reflect only 4 RAID partitions instead of 5 which I had previously, - ran mkinitrd to get the raid configuration into the intial ramdisk So then I powered off, disconnected the 2nd older drive, and tried to boot up again. Once it got past grub, it ran into a problem and would only boot to emergency mode. In emergency mode, it only had a very small very basic system installed, so I couldn't do much of anything. In order to get my system up and running again, I had to use an installation USB, go to the rescue system, and run through the procedure to reinstall grub, which includes running mkinitrd and the grub configuration. After I did that, my system booted up fine and I was able to get the new RAID partitions fully working on both of my new drives. But I don't understand why I had to use the rescue system? Why wouldn't running mkinitrd from the operating system when the RAID configuration was half on the old drive and half on the new drive be good enough? I think I don't fully understand what I did here. -- 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

1 0

Q: Raspi / TW Fixed Headless Resolution
by Andrei Verovski 22 Sep '21

22 Sep '21

Hi, I installed Tumbleweed on Raspberry Pi 3 and so far was unable to setup fixed headless resolution. Using x0vncserver (time to time I also connect real monitor). With Debian Buster this worked fine (/boot/config.txt) hdmi_edid_file=1 hdmi_edid_filename:0=edid-1920x1080.bin "edid-1920x1080.bin" located on /boot partition. On Tumbleweed I had to add this in order to get signal on monitor: hdmi_force_hotplug=1 config_hdmi_boost=4 Instead of "/boot/config.txt" Tumbleweed uses “/boot/efi/extraconfig.txt” Copied "edid-1920x1080.bin” into both “/boot” and “/boot/efi”. Unfortunately, it doesn’t work. Also tried: hdmi_force_hotplug=1 hdmi_group=2 hdmi_mode=82 No success either. Anyone know how to to fix this? Thanks in advance. Andrei

1 1

How does one contact an OBS package maintainer?
by J Leslie Turriff 20 Sep '21

20 Sep '21

I found a package for a program I want to use in | obs://build.opensuse.org/editors but I want to contact the maintainer to improve its usability. Using RPM -qi, I get the following: | ● rpm -q -i THE-3.3~RC7 | Name : THE | Version : 3.3~RC7 | Release : lp153.22.57 | Architecture: x86_64 | Install Date: Sat Sep 18 16:53:31 2021 | Group : Unspecified | Size : 1273234 | License : GFDL-1.1-only AND GPL-2.0-or-later AND SUSE-Freeware | Signature : DSA/SHA1, Thu Sep 9 08:44:07 2021, Key ID fd45d89e24f1ba50 | Source RPM : THE-3.3~RC7-lp153.22.57.src.rpm | Build Date : Thu Sep 9 08:43:37 2021 | Build Host : lamb53 | Relocations : (not relocatable) | Vendor : obs://build.opensuse.org/editors | URL : http://hessling-editor.sourceforge.net/ | Summary : The Hessling Editor (z/VM-CMS xedit clone) | Description : | THE is a text editor that uses both command line commands and key bindings | to operate. It is intended to be similar to the z/VM-CMS system editor, | XEDIT, and to Mansfield Software's, KEDIT | Distribution: editors / openSUSE_Leap_15.3 | @16:54:51,root@pinto rc=0 There seems not to be any contact information here (unless it is Build Host?). How can I get in contact with a real person? Leslie -- Distribution: openSUSE Leap 15.3 x86_64

3 4

TW - i2c permissions for normal users?
by Michael Hamilton 20 Sep '21

20 Sep '21

My i2c devices /dev/i2c-* are all set to 0660, yet non-root users logged into the desktop appear to have access. How is this achieved? Background: During a covid-19 lockdown I wrote vdu_controls, a GUI front end to ddcutil that I use to adjust the backlights on my external monitors: Ddcutil uses VESA DDC/MCCS over i2c to interact with external monitors. Details here: https://forums.opensuse.org/showthread.php/559401-Desktop-control-of-extern… https://www.ddcutil.com/ I recently had an enquiry from someone attempting to use vdu_controls on a non-SUSE distro. Clearly their problem is lack of permissions to /dev/i2c-* On other distributions the permissions seem to be granted by an entry in /etc/udev/rules.d such as KERNEL=="i2c-[0-9]*", MODE="0666" ( https://www.ddcutil.com/i2c_permissions/ ). I can't find where anything similar is set in Tumbleweed. But ddcutil is working fine, so how it a normal user getting access to /dev/i2c-*? I suspect it's due to an apparmor rule, but I can't find it. Puzzled.

7 10

EROFS within CFEngine
by Ansgar Esztermann-Kirchner 16 Sep '21

16 Sep '21

Hello List, with one of the recent updates, CFEngine starts getting EROFS whenever it tries to write a file. Since writing works just fine from a shell, I assume this is the result of some security measure that isn't properly configured. Does anyone have an idea where to look? Thanks, A. -- Ansgar Esztermann Sysadmin Dep. Theoretical and Computational Biophysics http://www.mpibpc.mpg.de/grubmueller/esztermann

2 3

Re: no ip address
by Carlos E. R. 16 Sep '21

16 Sep '21

On 12/09/2021 00.40, Douglas McGarrett wrote: > On 9/12/2021 12:08 AM, Carlos E. R. wrote: >> On 11/09/2021 22.14, Douglas McGarrett wrote: >> To find a networked hp printer, you probably want to do: >> >> nmap -p 9100 -n 192.168.1.* > > ran that in Windows, but got no answers: > > C:\Users\Douglas McGarrett>nmap -p 9100 -n 192.168.1.* > Starting Nmap 7.92 ( https://nmap.org ) at 2021-09-11 20:57 GMT Summer Time > Nmap done: 256 IP addresses (0 hosts up) scanned in 208.53 seconds > > Then tried with the third entry set to 0 and got this: > > C:\Users\Douglas McGarrett>nmap -p 9100 -n 192.168.0.* > Starting Nmap 7.92 ( https://nmap.org ) at 2021-09-11 23:34 GMT Summer Time > Nmap scan report for 192.168.0.1 > Host is up (0.0029s latency). > > PORT STATE SERVICE > 9100/tcp closed jetdirect > MAC Address: 1C:AF:F7:DD:AE:FF (D-Link International) That's the router. > Nmap scan report for 192.168.0.102 > Host is up (0.0020s latency). > > PORT STATE SERVICE > 9100/tcp filtered jetdirect > MAC Address: F0:4D:A2:0F:81:CF (Dell) > > Nmap scan report for 192.168.0.103 > Host is up (0.0029s latency). > > PORT STATE SERVICE > 9100/tcp open jetdirect > MAC Address: 48:0F:CF:C3:33:B7 (Hewlett Packard) The HP printer, probably. > Nmap scan report for 192.168.0.104 > Host is up (0.0023s latency). > > PORT STATE SERVICE > 9100/tcp closed jetdirect > MAC Address: 00:26:B9:D4:42:2D (Dell) > > Nmap scan report for 192.168.0.100 > Host is up (0.00s latency). > > I am not familiar with the value of the third number in the ips. I seem > to remember that 5 or 6 years ago, all my ips had a 1 in the third > position; now they all seem to want a 0. Well, your router changed, didn't it? Then the numbers can change, 0 and 1 are typical, but it could be 132, or 83, or 200, for instance. > > Anyway, not discovering the Epson printer ip, if any. Well, I told you the trick for HPs, not Epson. I don't know what port the Epson uses. Google "what port uses an epson printer" <https://epson.com/faq/SPT_C11CD16201~faq-0000525-shared?faq_cat=faq-8796127…> ok, try: nmap -p 3289,515,9100,631 -n 192.168.0.* -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))

8 34