January 2024 - openSUSE Users - openSUSE Mailing Lists

KDE - Wayland - NVidia -> load
by Klaus Vink Slott 30 Jan '24

30 Jan '24

Just a heads up. After updating my Tumbleweed to day, KDE on Wayland is not longer possible. CPU load goes max and everything slows to crawl. Luckily I still had X-org installed so I was able to switch back. I have not had the time to investigate further, but in case anyone has the same problem they should feel alone :-/ klaus@msien:~> lspci | grep -i vga 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) -- Klaus

2 2

Problem with connecting KMail to dovecot server both in Tumbleweed
by Freek de Kruijf 29 Jan '24

29 Jan '24

Suddenly, probably caused by a recent update, my KMail is unable to connect to the dovecot imap server on the same system. The server has a listening port on 127.0.0.1:143 and support STARTTLS. KMail is configured to connect to that port. On that system "telnet localhost 143" shows: Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN] Dovecot ready. Using "openssl s_client -connect localhost:143 -quiet" I get: 40F756DECB7F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:ssl/record/ssl3_record.c:354: Using "openssl s_client -connect localhost:143 -starttls imap -quiet" I can enter "tag login <username> <password>" and I get: tag NO [AUTHENTICATIONFAILED] Authentication failed. But I am sure username and password are OK. KMail also gets an authentication failure. But yesterday all was OK. -- fr.gr. member openSUSE Freek de Kruijf

2 5

Soundfont options for gzdoom:
by -pj 27 Jan '24

27 Jan '24

Hi, I am wondering about the most extensive soundfonts for use with fluidsynth. I am trying to find something for gzdoom to replace it's gzdoom.sf2whileplaying 30Years.wad -Regards

1 0

TW won't let me mount by device-name
by Ben T. Fender 26 Jan '24

26 Jan '24

After "fdisk -l" to validate that my booting drive is in fact /dev/sda mount /dev/sda8 /0/sa08 because I want to work in partition 8 What I get in response is ========================================================== # mount /dev/sda7 /0/sa07 mount: /0/sa07: /dev/sda7 already mounted or mount point busy. dmesg(1) may have more information after failed mount system call. ========================================================== Why is TW not letting me mount by confirmed device-name? It seem to me that I once removed some package that fixed the issue but I don't remember what that package was, and now it's back to square one. Any other fix? I used disk-labels for a while too but got into trouble with those being used together with uuids :-(

4 31

Yikes! Looks like an update has screwed up my laptop
by Marc Chamberlin 25 Jan '24

25 Jan '24

I am running OpenSuSE 15.5 with KDE/Plasma on my laptop and I, this morning, gave it permission to install the latest set of updates that I was told were waiting. It included a kernel update and as usual those want me to reboot after being installed. So I did and now I can no longer get my desktop up and running. The visual log, seen by using the Esc key during the system startup process, gives the following clues. During a regular (init 5) startup, I see two "start jobs" that seem to run forever - (1 of 2) A start job is running for User Login Management (xxmin xxs / ymin) (2 of 2) A start job is running for Hold until boot process finishes up (xxmin xxsec / no limit) Start job (1 of 2) keeps upping the ymin limit for about 15 to 20 minutes and then the following messages are logged - FAILED] Failed to start User Login Management. See 'systemctl status systemd-logind services' for details. [ OK ] Stopped User Login Management. Starting Load Kernel Module drm... [ OK ] Finished Load Kernel Module drm. Starting User Login Management... Starting Cleanup of Temporary Directories... [ OK ] Finished Cleanup of Temporary Directories. and then this cycle repeats forever. I next tried to start up OpenSuSE to init 3 and only the following error message was simply reported - FAILED to start Command Scheduler I am then allowed to login as root but I don't know what to do or how to proceed. While logged in, I do get repeating message interrupts telling me - kernel:[ nnn.nnnnnnn C0] BUG:workqueue lockup - pool cpus=14 node=0 flags=0x0 nice=0 stuck for xxxs! So how do I get my laptop back to a happy state? Marc C 1 1 -- --... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-. Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before!

5 18

Leap-16/Slowroller/flatpacking
by Ben T. Fender 24 Jan '24

24 Jan '24

What made me wonder was the recent change of grub listing my Slowroller gig as a just another Tumbleweed for some reason. Are both Slowroller and Flat-Leap headed for a merge? In plain english, like? It's just that I like to see the patch of ground where my next step will put foot :-) -- "Nous n'héritons pas de la terre de nos parents, nous l'empruntons à nos enfants." Antoine de Saint-Exupéry

5 7

Strangeness in defining "protocols" in dovecot/pigeonhole/mamagesieve
by joe a 23 Jan '24

23 Jan '24

Well, a strangeness to my view. Since this is an opensuse package and not the "lastest and greatest", not sure if I should post this here or "over there". It is a given that I may have, through some noobiness have bungled something early on that is causing this. I am prepared to accept the semi-public ritual shaming that may follow. All references to results mean per "dovecot -n". One can be assured that dovecot.conf was edited followed by "dovecot -n", then 20-managesieve.conf edited followed by "dovecot -n", for each "set". What happens is, it appears, that if one specifies or alters the "default" protocols in /etc/dovecot/dovecot.conf, any protocols subsequently defined, at least in /etc/dovecot/conf.d/20-managesieve.conf, are not honored. It does not seem to matter if it is specified as "protocols = sieve" or "protocols = $protocols sieve". Further, in /etc/dovecot/dovecot.conf, if one comments out "protocols", one finds protocols is not listed at all, unless there is a protocol defined later such as "sieve" in 20-managesieve.conf. if one lists "protocols = " then "protocols = " is listed even if a protocol is defined later such as "sieve" in 20-managesieve.conf of one lists "protocols = $protocols", nothing is listed, unless if: "protocols = sieve" is defined in 20-managesieve.conf, "protocols = sieve" is listed "protocols = $protocols sieve" is defined in 20-managesieve.conf - then "protocols = imap pop3 lmtp sieve" is listed. Again, all as shown by "dovecot -n" after editing each file(s). I hope this is useful in determining if there is a problem, and helps lead to a solution if one is warranted. I'll send this also to the docecotlist as a distinct email.

1 0

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