October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1203632] New: LibreOffice fails to print Cantarell
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203632 Bug ID: 1203632 Summary: LibreOffice fails to print Cantarell Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: me(a)letsfindaway.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Libreoffice Writer fails to print documents with the Cantarell font. The reason is discussed here: https://bugs.documentfoundation.org/show_bug.cgi?id=130149 In openSUSE this appeared when Cantarell was no longer delivered as individual ttf files (until 15.3) but used the Cantarell-VF.otf variable font (since 15.4). LibreOffice fails to render this font for printing and PDF export. A workaround would be to deliver Cantarell as individual ttf font files until this bug in LO is fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1186930] New: Vidcutter cannot edit or reproduce m4v files
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1186930 Bug ID: 1186930 Summary: Vidcutter cannot edit or reproduce m4v files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 849977 --> http://bugzilla.opensuse.org/attachment.cgi?id=849977&action=edit cli output of vidcutter with mp4 files The program does not specifically complain about anything. It takes a long time to show the thumbnails. When trying to reach a new cut position the program blocks with a black scree (thumbnails remain visible). I join the txt file with the cli output in attachment. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1186360] New: Linphone does not wake up correctly in about 40% of awake from suspend to disk
by bugzilla_noreply＠suse.com 14 Jan '23

14 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1186360 Bug ID: 1186360 Summary: Linphone does not wake up correctly in about 40% of awake from suspend to disk Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- the program itself behaves normally here on one user, but when awaking from suspend to disk or suspend to ram (when system idles for one night on another user) the program shows the account as not connected, searching. When telling to connect explicitly it does not work, however, when exiting the program and opening it again it connects at once problem free. If there is a log or setting were I can see what could be the cause, please advise. I set this to minor because once understood you have to just restart it, it is not really an issue. However,for some user (depending on use case) it may be an annoyance. What the program does: after idling long time on another user account, the application does not manage to log into the voip account, searching constantly to connect. What the program should do: normal reconnect when the user becomes active, according to the settings of the respective account. Reproducible: always Network on this machine is via wicked. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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