January 2024 - openSUSE Users - openSUSE Mailing Lists

Dovecot/Pigeonhole, Leap 15.5
by joe a 23 Jan '24

23 Jan '24

Installed Dovecot23 package via YAST. Dovecot configured and working for some months now. Added Roundcube along the way. Attempting to configure Sieve/Manageseive, found Roundcube could not contact managesieve. Reason being the port, 4190, managesieve is configured to listen on, is not bound. Cannot telnet to it, on the local box, nor does it show via socklist or other port listing means. Does not appear to be a misconfiguration of dovecot. Anyone have such a thing working?

2 4

EFI bootable gpt disk made in Legacy-boot Tumbleweed?
by Ben T. Fender 23 Jan '24

23 Jan '24

Is this possible? I tried with the TW installer to make such a disk to be used on another computer but when I set "grub2-efi" for boot it was rejected because "the current system was Legacy boot" or words to that effect.

4 11

Thoughts on installing Jinka 720 plotter driver:
by -pj 23 Jan '24

23 Jan '24

Hi, I am curious if anyone has some good starting points for installing a Jinka 720 plotter? -Regards

1 0

T470-w10+Tumbleweed/Slowroll
by Ben T. Fender 23 Jan '24

23 Jan '24

I got me a used Lenovo T470 with w10 preinstalled and using uefi or whatecver they call that fancy boot crap. In order to stay on the safe side of the alley I just installed Tumbleweed on a 1tb usb-ssd prepartitioned the same as the 1tb ssd of my desktop to eventually just host a copy of it. This way I can make a 'dd' copy of the entire laptop ssd for a backup of the entire on-board built-in hsithouse with windows included. I 'think' in case of a mishap I would just dd that file back to that or another same size ssd and be done with it. 3 questions - is the above a workable arrangement? - can I plug the linux ssd into the thunderbolt port and get better speed than with just a usb port (reason, I need all the usb ports)? - is there another and simple way of doing it all on an internal 1tb+ ssd with grub and not run the risk of windows screwing it all up? TIA

2 10

NVIDIA dmesg *ERRORS* Failed to grab modeset ownership:
by -pj 23 Jan '24

23 Jan '24

Hi, I have Nvidia 470-223.02 drivers installed on a openSUSE Tumbleweed machine: Thinkcentre-M57p:~> nvidia-smi Mon Jan 22 18:33:51 2024 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 470.223.02 Driver Version: 470.223.02 CUDA Version: 11.4 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| | 0 Quadro K600 Off | 00000000:01:00.0 On | N/A | | 26% 53C P8 N/A / N/A | 847MiB / 974MiB | 1% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ I just noticed these following error messages coming from dmesg: Thinkcentre-M57p:~> sudo dmesg | tail -20 [sudo] password for root: [ 9877.754230] fdc_busy=1 [ 9877.754231] do_floppy=reset_interrupt [floppy] [ 9877.754246] cont=000000001f1ca541 [ 9877.754248] current_req=0000000000000000 [ 9877.754249] command_status=-1 [ 9877.754253] floppy0: floppy timeout called [ 9878.075905] OOM killer enabled. [ 9878.082021] Restarting tasks ... done. [ 9878.123429] random: crng reseeded on system resumption [ 9878.131540] PM: suspend exit [ 9879.844104] e1000e 0000:00:19.0 enp0s25: NIC Link is Down [ 9881.991771] e1000e 0000:00:19.0 enp0s25: NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [16922.430620] perf: interrupt took too long (4933 > 4928), lowering kernel.perf_event_max_sample_rate to 40500 [17256.808982] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership [17258.354266] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership [17258.452799] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership [20057.865870] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership [20058.659971] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership [20058.741065] [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership Thinkcentre-M57p:~> What's going on here regarding the errors? Is this something that can be corrected? Is this something that is critical? -Best Wishes

2 1

libicuuc.so.73()(64bit) ??
by Carl Spitzer 22 Jan '24

22 Jan '24

Nothing provides this/ Has anyone found a fix or is this in a repo I do not have installed?? Strange though I downloaded separately the latest seamonkey and it works but the update trys to use the repo's I have installed and I run into this missing peice. CWSIV

5 12

Disable IPv6?
by joe a 22 Jan '24

22 Jan '24

While chasing other issues, noticed that listing ports in use (open) using socklist shows some services have tcp6 and udp6 listed. This puzzles me as IPv6 is disabled, not checked as enabled, in network config via YAST. I thought that disabled IPv6 entirely? Not so?

4 11

Changing group ownership for entire home folder:
by -pj 22 Jan '24

22 Jan '24

Hi, I am looking to change group ownership for the entire user paul's home folder, it's subdirectories and also all symlinks. Thinkcentre-M57p:/home> ls -lah total 0 dr-xr-xr-x 1 root root 14 Jan 21 18:18 . drwxr-xr-x 1 root root 142 Jun 3 2021 .. drwx------ 1 deb deb 318 Jan 21 15:12 deb drwxr-xr-x 1 paul users 868 Jan 21 18:14 paul paul@paul-Thinkcentre-M57p:/home> Passing: chgrp -LR paul users Is how I believe chgrp should be used in this case. Does this look correct to you? If not why and is there a better command for this purpose? -Best Regards Thinkcentre-M57p:~> groups paul paul : paul audio cdrom

4 10

Tumbleweed new users:
by -pj 21 Jan '24

21 Jan '24

I notice that a new user creation (YaST), automatically adds the new user to the users group. I created another user here about a month ago and this is not the case (groups username outputs username username, i.e. deb : deb). The su/sysadmin account I just noticed is also a member of the users group. YaST2 > User and Group Administration > Defaults for New Users > Default Group > /users/ , is stuck on anything but the desired here. Example creating a new user, Hyn the only group I wish Hyn to be in is Hyn and does not exist. I attached a paste to better display this. https://paste.opensuse.org/pastes/1f7650450f4a test, test2 and paul have been added to users group. Passing: groups deb output deb : deb. Am I going to have to somehow use groupadd to add a group for user paul since there is no group paul existing? What should the default group be set to in YaST, in order to simply have /groups test/ display /test : test/ after user is created? #usermod -G paul audio cdrom usermod: group 'paul' does not exist Thinkcentre-M57p:~ # What's the best way to remove user paul from users group and have user paul only be a member of currently nonexistent group paul? ugh, Thanks

3 3

x11vnc/vncviewer guru wanted for help
by Marc Chamberlin 20 Jan '24

20 Jan '24

Hi, I am not sure where to turn for help with x11vnc and (Tiger) vncviewer that I got from the OpenSuSE 15.4 and 15.5 repositories. Google search does not show any forums dedicated to x11vnc, so I thought I would take a stab at it here. If anyone knows of a better forum or a better place to find documentation that would help be with my issue, I would greatly appreciate links! What documentation I can find just sucks and is incomplete in describing HOW x11vnc actually works... I have been a happy camper using x11vnc and vncviewer for years now to bounce around between computers and desktops on my own SOHO network. (Not always easy to configure, but I have managed...) Recently I bought a new laptop with a high res screen 3456x2160 to add to my network mix, running OpenSuSE15.5. Most of the other computers are older (OpenSuSE15.4) and running using 1920x1080 screens. All systems are running the KDE with Plasma desktops. What I want to do is to be able to VNC from my laptop (client) to display :0 on my other systems, and get a full screen display of the desktop from my remote VNC server systems. I haven't been able to figure out how to do this successfully, God only knows how many hours I have spent trying! The closest I have come is to configuring the x11vnc server and vncviewer client as follows - Remote VNC server - /usr/bin/x11vnc -display :0 -auth /run/user/1000/xauth_DFOoYd -forever -loop -noxdamage -repeat -rfbauth /etc/vncpasswd -o /var/log/x11vnc.log -rfbport 5900 -noipv6 -shared -scale 3456x2160 -quiet; Local VNC client - vncviewer -geometry 3456x2160 -DesktopSize 3456x2160 remote.mydomain.com::5900 This gives me a brief glimpse of a full screen desktop, like I want, but vncviewer immediately crashes. Vncviewer reports the following error messages - Mon Jan 8 10:05:24 2024 CMsgReader: Rect too big: 3223x2102 at 0,65535 exceeds 3456x2160 CConn: Rect too big I feel like I am starting to get above my pay grade now, there is not a lot of helpful information about "Rect" or how to configure, encode, or work with them. It seems that only an x11vnc guru can really deal with this part of the VNC model. Is there anyone on this mail list who can tackle this problem for me and help shed some light on what is going on? A command line example(s) like a picture is worth a thousand words! Much appreciate all offers of help and suggestions. Marc...

4 10