- openSUSE Support

[TW] Systemd/Dbus Broken
by Walddys Emmanuel Dorrejo Céspedes 07 Nov '24

07 Nov '24

Hello, TW - Latest Snapshot. I just did a fresh install in a server and found that Login to the user from SSH is not creating the session nor dbus, so when trying to work with container, systemd, and loginctl appear the user is not existent. What it must happens is: - When connecting through ssh to the machine, a XDG_RUNTIME or user-slice session must be started, which is not happening. loginctl: https://forums.opensuse.org/uploads/default/original/3X/8/3/839eaf47e96e461… systemd: https://forums.opensuse.org/uploads/default/original/3X/a/2/a21b19383dd0bab… podman: https://forums.opensuse.org/uploads/default/original/3X/e/a/ea5bb7885009ec0… Looking into what service exist: https://forums.opensuse.org/uploads/default/original/3X/5/4/54b0e0b0c667cc2… my sshd_config: ``` Port 22 ListenAddress 0.0.0.0 LogLevel VERBOSE # Strong encryption settings Ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes256-ctr MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com KexAlgorithms curve25519-sha256,curve25519-sha256(a)libssh.org,diffie-hellman-group18-sha512 # Key exchange algorithms HostKeyAlgorithms ssh-ed25519,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01(a)openssh.com # Authentication settings PermitRootLogin prohibit-password PasswordAuthentication no ChallengeResponseAuthentication no AuthenticationMethods publickey # Enable only key-based login AuthorizedKeysFile .ssh/authorized_keys # Additional security settings AllowTcpForwarding yes AllowAgentForwarding no StrictModes yes IgnoreRhosts yes X11Forwarding no PermitTunnel no MaxAuthTries 2 UseDNS no PermitUserEnvironment no # Client keep-alive ClientAliveInterval 15 ClientAliveCountMax 6 # Strict HostKey settings HostKey /etc/ssh/ssh_host_ecdsa_key HostKey /etc/ssh/ssh_host_ed25519_key ``` Created a new user and manually start the user(a)id.service, for a moment worked, but after a moment stop working, and got again: https://forums.opensuse.org/uploads/default/original/3X/a/2/a21b19383dd0bab… There is not log and can't found anything related to this.

1 0

Leap CUPS cannot see Tumbleweed CUPS printers
by Larry Len Rainey 07 Nov '24

07 Nov '24

2 1

Problem with input of password in SDDM (in multimonitor system) with Tumbleweed, asking help with debug.
by Stakanov 04 Nov '24

04 Nov '24

Since a few weeks I have a quite curious problem with logging into my system with SDDM to X Session Plasma. The problem is as follows: I have three monitors. The central monitor is being set as principal. When I start up the system, normally I logged into the plasma session via the principal screen (not that this is mandatory, but your eye focuses normally what is in front of you, not to the left or right). When I do input the password, SDDM accepts the input and freezes immediately as if the password would be wrong. But it also does not turn any error and does not return to the password prompt. Instead it stays kind of greyed out and frozen to any interaction. Now if I go the monitor left or right when this happens, then I can input the password, it is accepted and the session starts normally. By trial and error I d find out that the right and left monitor SDDM password is working, whether the first session opens, one user is already open or more user. But all tries to start a session on the central monitor (set in KDE as principal) fail. Now I tried to find any trace in the journal but nothing complains. All seems perfectly fine. So my questions: is there a special log that SDDM writes to? Does anybody has the same issue? Did anybody read about this issue on some bug list or mailing list? Somewhere I have to start, thank you.

3 3

Google Chrome
by Mark D. Neidorff 03 Nov '24

03 Nov '24

For a few very specific sites, I use Google Chrome as the browser. Recently I've gotten the message that "Google Chrome may not function correctly because it is no longer supported on his Linux distribution". When I need it, I use it. I downloaded Chrome through YAST and my version is 130.0.6723.91-1 . There does not seem to be a way to remove this annoying message other than "x"ing out of it each time I start the browser. Does anyone know of a fix for to remove the annoying message? Thank you, Mark -- Abolish mornings...sleep 'til noon!

3 5

[very old: 10.2] mkinitrd,mount,EXT[3,4]
by Felix Miata 03 Nov '24

03 Nov '24

I'm in process of eliminating EXT2 & EXT3 filesystems from old computers, due to the year 2038 date problem that might arrive before my termination. Using: tune2fs -O extents,uninit_bg,dir_index /dev/sdb1 This has worked reliably until arriving at the oldest installation encountered yet, 10.2, the oldest on that PC. I have others yet to do even older. The initial problem seemed to be that the 10.2 kernels simply didn't ship with /lib/modules/<version>/kernel/fs/ext4/. I thought I had this solved by installing a 10.3 kernel, which does provide it. However, I can't find a way to get it into the initrd. Adding ext3 to /etc/sysconfig/kernel's INITRD_MODULES= doesn't help. In order to do these things I must chroot to the installation, as no installed 10.2 kernel's initrd will mount the / filesystem since I added the features for upgrading to EXT4. I'm trying to use 11.4 to do the chroots as the closest installed version of anything else installed. mount -o bind /dev /disks/s102/dev mount -o bind /sys /disks/s102/sys mount -o bind /proc /disks/s102/proc chroot /disks/s102 The only other openSUSE on the PC is current TW. 11.4 on sda9 recognizes 10.2's sda15 as EXT4 and mounts it as such, as does TW, and Debian, and Fedora, but once in 10.2 chroot, it somehow gets switched (e.g. according to mount command output) to EXT3. /etc/mtab contains ext3, while /etc/fstab contains ext4. EXT3 is what the mkinitrd command reports sda15 is mounted as, along with claiming it cannot find an EXT4 module: mkinitrd -i initrd-2.6.22.19-0.4-default -k vmlinuz-2.6.22.19-0.4-default Kernel image: /boot/vmlinuz-2.6.22.19-0.4-default Initrd image: /boot/initrd-2.6.22.19-0.4-default Could not find the filesystem module for root device /dev/sda15 (ext4) cat: /sys/b8:0/dev: No such file or directory cat: /sys/b8:16/dev: No such file or directory cat: /sys/b8:32/dev: No such file or directory cat: /sys/b8:48/dev: No such file or directory cat: /sys/b8:64/dev: No such file or directory I don't see anything helpful in mount or mkinitrd manuals. Any ideas what I can do to get the ext4 module into that old 10.3 2.6.22 kernel's initrd? It puts ext3 there instead (lsinitrd initrd | grep ext). Or, how about some change in chroot setup process that keeps 11.4's EXT4 FS mount type? What is forcing recognition as EXT3? Extra Credit: What is responsible for maintenance or creation of /etc/blkid.tab? What uses it? For what? It and its .old sibling have identical content and current timestamps. -- 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

5 16

Re: libQt6Core.so.6(Qt_6.7.3_PRIVATE_API
by Marco Calistri 01 Nov '24

01 Nov '24

Il 23/10/24 14:53, Patrick Shanahan ha scritto: > * Marco Calistri <PY1ZRJ(a)outlook.com> [10-23-24 13:44]: >> Hello, >> >> I need libQt6Core.so.6(Qt_6.7.3_PRIVATE_API for telegram-desktop. >> >> Last zypper dup produced a lot of dependencies with others libQTs. >> >> So I need this library to be able to reinstall telegram-desktop, but >> apparently is not available within opensuse yet. >> Kernel: 6.11.2-1-default - XFCE: (4.18.4) >> Uptime: 10:00:02 up 10 days 18:12, 1 user, carico medio: 4,52, 5,32, 4,65 > TW offers: libQt6Core6-6.8.0-1.1.x86_64 > kernel: 6.11.3-2-default > > Yes, but telegram-desktop-5.5.5-1.2.x86_64 requires the one I reported above. Otherwise you broke dependencies. --- Marco Calistri Build: openSUSE Tumbleweed 20201201 Kernel: 5.9.11-1-default (Xfce 4.14)

2 3

Tumbleweed packagekitd stuck running for hours on all my tumbleweed systems
by Larry Len Rainey 29 Oct '24

29 Oct '24

2 1

Figured out that provo-mirror is down - that is why Tumbleweed packagekitd is hung
by Larry Len Rainey 28 Oct '24

28 Oct '24

1 0

telegram missing dependency
by Stakanov 23 Oct '24

23 Oct '24

entropy@silversurfer:~> sudo LC_ALL=C zypper in telegram-desktop. [sudo] password di root: Loading repository data... Reading installed packages... Resolving package dependencies... Problem: 1: nothing provides 'libQt6Core.so.6(Qt_6.7.3_PRIVATE_API)(64bit)' needed by the to be installed telegram-desktop-5.5.5-1.2.x86_64 Solution 1: do not install telegram-desktop-5.5.5-1.2.x86_64 Solution 2: break telegram-desktop-5.5.5-1.2.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): I filed a bug, but in the meanwhile: does anybody uses here telegram-desktop and managed to ship around this problem? If yes, how? Thank you.

4 8

libQt6Core.so.6(Qt_6.7.3_PRIVATE_API
by Marco Calistri 23 Oct '24

23 Oct '24

Hello, I need libQt6Core.so.6(Qt_6.7.3_PRIVATE_API for telegram-desktop. Last zypper dup produced a lot of dependencies with others libQTs. So I need this library to be able to reinstall telegram-desktop, but apparently is not available within opensuse yet. Thanks! -- Marco Calistri Build: openSUSE Tumbleweed 20241021 Kernel: 6.11.2-1-default - XFCE: (4.18.4) Uptime: 10:00:02 up 10 days 18:12, 1 user, carico medio: 4,52, 5,32, 4,65

1 0