July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1188122] New: Latest update to TW breaks Kwallet integration to Kmail
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188122 Bug ID: 1188122 Summary: Latest update to TW breaks Kwallet integration to Kmail Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When starting Kmail now, the password is asked for every server as "it was not able to access kwallet". But Kwallet is open and the passwords are there. copy paste to the password prompt does fix the issue for one session. No new entry is generated in Kwallet. Entries in Kwallet seem normal. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1195393] New: KDE Plasma sound level starts with 74% after every reboot
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195393 Bug ID: 1195393 Summary: KDE Plasma sound level starts with 74% after every reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: 64bit OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: datenteiler(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36 Build Identifier: I want to start with a lower sound level, because 74%, the default level, is too loud. But when I change the sound level in KDE Plasma to e.g. 42% it's back on 74% after the next reboot. When I log out and log back in, the sound level stays at the value I set, but the volume level is back to 74% after reboot. I have configured my sound card in YaST but this didn't changed anything. Reproducible: Always Steps to Reproduce: 1. Set sound level to a different level then 74% in KDE Plasma (maybe other DE are also effected) 2. Restart openSUSE Leap 15.4 3. Sound level is on 74% again Actual Results: Sound level is on 74%, always. After every reboot. Expected Results: Sound level stays at the value I set. Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Device-2: AMD Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] driver: snd_hda_intel Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo Device-4: RODE Microphones RODE NT-USB type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server-1: ALSA v: k5.14.21-150400.3-default running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.39 running: yes ps -e | grep pipewire 2513 ? 00:00:00 pipewire 2514 ? 00:00:00 pipewire-media- -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1199973] New: Regression: samba update to 4.15.7+git.376 broke Nautilus share access for NT1 protocol
by bugzilla_noreply＠suse.com 13 Jan '23

13 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199973 Bug ID: 1199973 Summary: Regression: samba update to 4.15.7+git.376 broke Nautilus share access for NT1 protocol Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: martin.wilck(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- We've got an old NAS server that requires the "NT1" protocol. We can connect using "client min protocol = NT1" in /etc/samba/smb.conf. This used to work also with Nautilus and it's smb:// URI scheme, until the last update of samba-client. Since the update to samba-client 4.15.7+git.376.dd43aca9ab2, accessing shares via nautilus doesn't work any more. Nautilus opens a pop-up showing "invalid argument". In the previous version 4.15.4+git.324.8332acf1a63, Nautilus would show a password prompt and connect successfully with the right password. The password prompt is never shown with 4.15.7+git.376. But I can still connect via command line: # smbclient -d5 //nasobem.local/josefine -U josefine lp_load_ex: refreshing parameters Initialising global parameters rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[global]" doing parameter workgroup = MITTAGSTUNDE doing parameter passdb backend = tdbsam doing parameter printing = cups doing parameter printcap name = cups doing parameter printcap cache time = 750 doing parameter cups options = raw doing parameter map to guest = Bad User doing parameter logon path = \\%L\profiles\.msprofile doing parameter logon home = \\%L\%U\.9xprofile doing parameter logon drive = P: doing parameter usershare allow guests = No doing parameter client min protocol = NT1 pm_process() returned Yes added interface wlan0 ip=fd00::5430:8914:8532:921b bcast= netmask=ffff:ffff:ffff:ffff:: added interface wlan0 ip=fd00::a395:90ab:5502:d78a bcast= netmask=ffff:ffff:ffff:ffff:: added interface wlan0 ip=192.168.1.36 bcast=192.168.1.255 netmask=255.255.255.0 Password for [MITTAGSTUNDE\josefine]: Client started (version 4.15.7-git.376.dd43aca9ab2150300.3.32.1-SUSE-oS15.0-x86_64). Opening cache file at /var/lib/samba/lock/gencache.tdb sitename_fetch: No stored sitename for realm '' namecache_fetch: name nasobem.local#20 found. Connecting to 192.168.1.169 at port 445 socket options: SO_KEEPALIVE=0, SO_REUSEADDR=0, SO_BROADCAST=0, TCP_NODELAY=1, TCP_KEEPCNT=9, TCP_KEEPIDLE=7200, TCP_KEEPINTVL=75, IPTOS_LOWDELAY=0, IPTOS_THROUGHPUT=0, SO_REUSEPORT=0, SO_SNDBUF=87040, SO_RCVBUF=131072, SO_SNDLOWAT=1, SO_RCVLOWAT=1, SO_SNDTIMEO=0, SO_RCVTIMEO=0, TCP_QUICKACK=1, TCP_DEFER_ACCEPT=0, TCP_USER_TIMEOUT=0 session request ok negotiated dialect[NT1] against server[nasobem.local] cli_session_creds_prepare_krb5: Doing kinit for josefine@MITTAGSTUNDE to access nasobem.local Kinit for josefine@MITTAGSTUNDE to access nasobem.local failed: Cannot find KDC for requested realm cli_session_setup_spnego_send: Connect to nasobem.local as josefine@MITTAGSTUNDE using SPNEGO GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego' registered GENSEC backend 'schannel' registered GENSEC backend 'naclrpc_as_system' registered GENSEC backend 'sasl-EXTERNAL' registered GENSEC backend 'ntlmssp' registered GENSEC backend 'ntlmssp_resume_ccache' registered GENSEC backend 'http_basic' registered GENSEC backend 'http_ntlm' registered GENSEC backend 'http_negotiate' registered GENSEC backend 'krb5' registered GENSEC backend 'fake_gssapi_krb5' registered Starting GENSEC mechanism spnego gensec_spnego_client_negTokenInit_start: Server claims it's principal name is NONE Starting GENSEC submechanism gse_krb5 smb_gss_krb5_import_cred ccache[MEMORY:cliconnect] failed with [Es wurden keine Anmeldedaten �bergeben oder die Anmeldedaten waren nicht verf�gbar bzw. ein Zugriff darauf nicht m�glich.: kein Anmeldedatenzwischenspeicher gefunden] -the caller may retry after a kinit. Failed to start GENSEC client mech gse_krb5: NT_STATUS_INTERNAL_ERROR Starting GENSEC submechanism ntlmssp Got challenge flags: Got NTLMSSP neg_flags=0x628a8215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_ALWAYS_SIGN NTLMSSP_TARGET_TYPE_SERVER NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY NTLMSSP_NEGOTIATE_TARGET_INFO NTLMSSP_NEGOTIATE_VERSION NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP: Set final flags: Got NTLMSSP neg_flags=0x62088215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_ALWAYS_SIGN NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY NTLMSSP_NEGOTIATE_VERSION NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x62088215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_ALWAYS_SIGN NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY NTLMSSP_NEGOTIATE_VERSION NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH NTLMSSP Sign/Seal - Initialising with flags: Got NTLMSSP neg_flags=0x62088215 NTLMSSP_NEGOTIATE_UNICODE NTLMSSP_REQUEST_TARGET NTLMSSP_NEGOTIATE_SIGN NTLMSSP_NEGOTIATE_NTLM NTLMSSP_NEGOTIATE_ALWAYS_SIGN NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY NTLMSSP_NEGOTIATE_VERSION NTLMSSP_NEGOTIATE_128 NTLMSSP_NEGOTIATE_KEY_EXCH session setup ok tconx ok Try "help" to get a list of possible commands. smb: \> -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1198530] New: Mouse Pointer flicker and artifacts
by bugzilla_noreply＠suse.com 13 Jan '23

13 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198530 Bug ID: 1198530 Summary: Mouse Pointer flicker and artifacts Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: sjr.apd(a)shaw.ca QA Contact: qa-bugs(a)suse.de Found By: Customer Blocker: --- Using Leap 15.4 Beta: During initial boot to login screen the mouse pointer flickers and moving it over parts of interface leaves graphic artifacts behind. Once logged into X11 Gnome the same mouse pointer flicker/artifact issue persists. Also moving some windows around has square border artifacts--I assume where the translucent shadows would normally be. The work around is log back out and back in and the issue goes away. Another method is immediately setting machine to suspend, then waking it up. The lock screen login also fixes the mouse pointer. What would be the best way to resolve this for intial boot to avoid the secondary logout and login. p.s. (I added the Wayland pattern for Gnome to try via wayland instead of x11, but don't get the choice at the login screen for X11 or Wayland GNOME. It only shows GNOME and GNOME classic) Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1173321] New: Move /etc/skel/* files to /usr/etc/skel ?
by bugzilla_noreply＠suse.com 13 Jan '23

13 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1173321 Bug ID: 1173321 Summary: Move /etc/skel/* files to /usr/etc/skel ? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm currently working on the config file switch /etc --> /usr/etc (find Details on https://en.opensuse.org/openSUSE:Packaging_UsrEtc) and now I'm wondering what should be done with files in /etc/skel/* Thorten Kukuk: Hard to change, as the admin should be able to change them... Me: Hm. Maybe move the distributed ones to /usr/etc/skel and adjust everything needed to priotarize the ones in /etc/skel, i.e. use any file in /etc/skel but also any file, which exists in /usr/etc/skel, but not in /etc/skel? -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1019024] New: Update zone for DNS server doesn't occurs in Yast
by bugzilla_noreply＠novell.com 12 Jan '23

12 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1019024 Bug ID: 1019024 Summary: Update zone for DNS server doesn't occurs in Yast Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: conde.philippe(a)skynet.be QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I tried updating a zone in Yast2. Adding a A record for an IP alias address. When I save it the zone (pce23.net) is not updated in /var/lib/named/dyn I updated again today (10 Jan 2017) adding a new A record and after exit and reload the zone is not changed. The date of the zone file remains the original date -rw-rw-r-- 1 named named 332 Jan 8 09:18 pce23.net I saved the log with save_y2logs and attach it here (it is big > 5mb) Regards Philippe Condé -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1201927] New: calibrate.conf.tumbleweed.s390x does not exist in kdump
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201927 Bug ID: 1201927 Summary: calibrate.conf.tumbleweed.s390x does not exist in kdump Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jbohac(a)suse.com Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- calibrate.conf exists for Leap on s390x. That does not exist for Tumbleweed on s390x, but for the other architecture. The build log is failing with: [ 316s] make: Leaving directory '/home/abuild/rpmbuild/BUILD/kdump-1.0.2+git13.ge715180/build' [ 316s] + mkdir -p /home/abuild/rpmbuild/BUILDROOT/kdump-1.0.2+git13.ge715180-1.1.s390x/var/crash [ 316s] + cp calibrate/calibrate.conf.tumbleweed.s390x /home/abuild/rpmbuild/BUILDROOT/kdump-1.0.2+git13.ge715180-1.1.s390x/usr/lib/kdump/calibrate.conf [ 316s] cp: cannot stat 'calibrate/calibrate.conf.tumbleweed.s390x': No such file or directory How is such a calibrate.conf created for a special architecture? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1100765] New: gimp create from screenshot snap region is missing in french and error
by bugzilla_noreply＠novell.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1100765 Bug ID: 1100765 Summary: gimp create from screenshot snap region is missing in french and error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: conde.philippe(a)skynet.be QA Contact: ke(a)suse.com Found By: --- Blocker: --- Created attachment 776591 --> http://bugzilla.opensuse.org/attachment.cgi?id=776591&action=edit gimp in english with 3 options Hello, in gimp select create image ==> from screenshot in Enclish you have 3 options (see attachment gimp_englishok.png) - take a screenshot of a single window - take screenshot of entire screen - select a region to grab in french the third option is missing (see attachment gimp_frenchbad.png) if I select in french one of the two available options I receive an error (see attachment gimp_error.png Erreur d’exécution « Capture d’écran » : GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path '/Screenshot' -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1201730] New: Upgrade to LEAP 15.4 breaks installing official Vagrant package with vagrant-libvirt
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201730 Bug ID: 1201730 Summary: Upgrade to LEAP 15.4 breaks installing official Vagrant package with vagrant-libvirt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: markus.zimmermann(a)symflower.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just installed a new machine with LEAP 15.4. This is actually the first time I tried it on our development environment stack. One major part of our devenv is broken with 15.4: Vagrant with libvirt as its backend cannot be installed **This worked flawless with LEAP 15.3. We cannot upgrade because of this problem.** Here is a reproducer that works repeatedly for me on a newly installed 15.4 and on a machine where i upgraded from 15.3 to 15.4. We usually install the official version of Vagrant (so we can reproduce bugs for specific versions) and also install specific plugins: E.g.: # Remove everything related to Vagrant and building with bundler: rm -rf .vagrant/ ~/.vagrant.d/ ~/.bundle # Install Vagrant manually from the official source. sudo zypper --no-gpg-checks --non-interactive install https://releases.hashicorp.com/vagrant/2.2.19/vagrant_2.2.19_x86_64.rpm Create a directory "foobar", cd into it, and create a Vagrantfile ``` # -*- mode: ruby -*- # vi: set ft=ruby : VAGRANTFILE_API_VERSION = '2' Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vagrant.plugins = { "vagrant-libvirt" => { "version" => "0.9.0" } } config.vm.box = 'generic/ubuntu2004' config.vm.box_version = '4.0.4' config.vm.box_check_update = false config.vm.hostname = 'foobar' config.vm.provider :libvirt do |libvirt| libvirt.cpus = 2 libvirt.memory = 2048 end end ``` # Create the VM with debugging output. Remember to press Y+ENTER when asked to install the libvirt plugin. vagrant --debug up What you will see is an error that we cannot compile ruby-libvirt (the libvirt dependency). The output references the log file ruby-libvirt-0.8.0/mkmf.log Which mainly failed with ``` "gcc -o conftest -I/opt/vagrant/embedded/include/ruby-2.7.0/x86_64-linux -I/opt/vagrant/embedded/include/ruby-2.7.0/ruby/backward -I/opt/vagrant/embedded/include/ruby-2.7.0 -I. -I/opt/vagrant/embedded/include -I/opt/vagrant/embedded/include -I/opt/vagrant/embedded/include -I./include -O3 -std=c99 -fPIC conftest.c -L. -L/opt/vagrant/embedded/lib -Wl,-rpath,/opt/vagrant/embedded/lib -L/opt/vagrant/embedded/lib -Wl,-rpath,/opt/vagrant/embedded/lib -L. -L/opt/vagrant/embedded/lib -L/opt/vagrant/embedded/lib64 -Wl,-rpath=/opt/vagrant/embedded/lib:/opt/vagrant/embedded/lib64 -fstack-protector-strong -rdynamic -Wl,-export-dynamic -L/opt/vagrant/embedded/lib -Wl,-rpath,/opt/vagrant/embedded/lib -Wl,-rpath,'/../lib' -Wl,-rpath,'/../lib' -lruby -lvirt -lm -lc" /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libssh.so.4: undefined reference to `EVP_KDF_CTX_new_id@OPENSSL_1_1_1d' /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libssh.so.4: undefined reference to `EVP_KDF_ctrl@OPENSSL_1_1_1d' /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libssh.so.4: undefined reference to `EVP_KDF_CTX_free@OPENSSL_1_1_1d' /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libssh.so.4: undefined reference to `EVP_KDF_derive@OPENSSL_1_1_1d' ``` As you can see. We cannot install vagrant-libvirt with LEAP 15.4. Mainly because we cannot compile ruby-libvirt. This worked flawless with LEAP 15.3. Now i was desperate so i looked a little closer and tried different scenarios. The only scenario i found that actually worked: When we add the repositories https://download.opensuse.org/repositories/devel:/languages:/ruby/15.4 and https://download.opensuse.org/repositories/Virtualization:/vagrant/15.4 We can install the the current version of "vagrant" which is 2.2.19 from the virtualization-vagrant repository. The package automatically installs "ruby3.1" (from the ruby repository) and some ruby3.1-* packages (from the virtualization-vagrant repository) AND also "vagrant-libvirt" in an completely outdated version. That we need to deinstall, so we can compile it on our own (please do not install this packages automatically, most users might not even want that package). After deinstalling "vagrant-libvirt". We need to install "ruby3.1-rubygem-ruby-libvirt", "ruby3.1-rubygem-fog-core" and "ruby3.1-rubygem-fog-libvirt" (from the virtualization-vagrant repository). The last one greets us with the problem that "ruby:3.1.0:nokogiri" cannot be found in any repository. We need to install it anyway. We can try again: # Remove everything related to Vagrant and building with bundler: rm -rf .vagrant/ ~/.vagrant.d/ ~/.bundle # Create the VM with debugging output. Remember to press Y+ENTER when asked to install the libvirt plugin. vagrant up This time, the compilation and installation works, even though we are breaking a reference. Conclusion: - We can compile+install+use the vagrant-libvirt plugin on our own. However, we are bound to the Vagrant version in the virtualization-vagrant repository. - Since we are bound to a specific Vagrant version, and we cannot simply install vagrant-libvirt, we cannot upgrade to 15.4. This is a major blocker for us. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1193742] New: go1.18 release tracking
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1193742 Bug ID: 1193742 Summary: go1.18 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- go1.18 (expected February 2022) is a major release of Go. Minor releases of go1.18.x will be provided through February 2023. This issue tracks go1.18.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 15