October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1115455] New: rkhunter: migrate from cron to systemd timers
by bugzilla_noreply＠novell.com 20 Nov '22

20 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1115455 Bug ID: 1115455 Summary: rkhunter: migrate from cron to systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kstreitova(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kstreitova(a)suse.com Found By: --- Blocker: --- This bug is part of TRACKERBUG bug#1115430. Based on fate#323635 (Reduce usage of cron package in favor of systemd timers) we would like to minimize the number of packages that use cron in favour of systemd timers. It seems that your package uses cron. Please take a look at it and evaluate if it's possible to migrate your package to use systemd timers without impacting behaviour. If it's not possible, please write down the reason. Please note that by default, services are not enabled when the package is installed. You probably want your service to be enabled by default so you should create a submit request on systemd-presets-branding-openSUSE package, modifying default-openSUSE.preset file by adding "enable your_service_name.service". -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1115430] New: [TRACKERBUG-OPENSUSE] FATE#323635: Reduce usage of cron in favour of systemd timers
by bugzilla_noreply＠novell.com 20 Nov '22

20 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1115430 Bug ID: 1115430 Summary: [TRACKERBUG-OPENSUSE] FATE#323635: Reduce usage of cron in favour of systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: kstreitova(a)suse.com Reporter: kstreitova(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker bug for fate#323635 (Reduce usage of cron package in favor of systemd timers). It tracks openSUSE packages only (for SLE packages see bug#1115399). The goal is to minimize the number of openSUSE:Factory packages that use cron in favour of systemd timers. See dependent bugs for more information about particular packages that should be migrated. -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1191170] New: No RDP possible from any KDE app
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191170 Bug ID: 1191170 Summary: No RDP possible from any KDE app Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After an update, I found that I am not able to connect to local network machines through RDP. I have 3 machines, all of them are accesible from a Windows OS without any issues. Using remmina or KRDC I instantly get Cannot connect to the "192.168.1.248" RDP Server. I've tried disabling NLA on the RDP servers, even though it worked before the update without any issues. Connecting to port 3389 using nc works: nc -zv 192.168.1.248 3389 Connection to 192.168.1.248 3389 port [tcp/ms-wbt-server] succeeded! Starting remmina from konsole, I get: Load modules from /usr/lib64/remmina/plugins Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000. The glibsecret secret plugin has been initialized and it will be your default secret plugin (org.remmina.Remmina:4333): Gtk-WARNING **: 11:23:25.205: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem (org.remmina.Remmina:4333): Gtk-CRITICAL **: 11:23:31.454: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (org.remmina.Remmina:4333): Gtk-CRITICAL **: 11:23:31.455: gtk_toggle_tool_button_set_active: assertion 'GTK_IS_TOGGLE_TOOL_BUTTON (button)' failed (org.remmina.Remmina:4333): Gtk-CRITICAL **: 11:23:31.455: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed [11:23:31:056] [4333:4347] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state [11:23:31:056] [4333:4347] [ERROR][com.freerdp.common.settings] - [freerdp_settings_set_bool] Invalid key index 2816 [11:23:31:056] [4333:4347] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [11:23:31:056] [4333:4347] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [11:23:31:056] [4333:4347] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [11:23:31:056] [4333:4347] [INFO][com.freerdp.client.common.cmdline] - loading channelEx drdynvc [11:23:31:365] [4333:4347] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized [11:23:31:365] [4333:4347] [ERROR][com.freerdp.codec] - Failed to find libav H.264 codec [11:23:31:365] [4333:4347] [ERROR][com.freerdp.core.codecs] - Failed to create h264 codec context libfreerdp returned code is 00000000 So, it seems an update broke something related to libav H.264 codec library. I added the Packman essential repository and switched to this repo so the avcodecs are installed. After this operation everything is working fine. So it means some update broke something that was working before. I only added the Packman repo after I've noticed this issue. Please let me know if there is the need to send you the zypper logs. The issue happened few days ago and I still have the logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1103805] New: No access to mysql/mariadb databases using jdbc driver
by bugzilla_noreply＠novell.com 17 Nov '22

17 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1103805 Bug ID: 1103805 Summary: No access to mysql/mariadb databases using jdbc driver Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: LibreOffice Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: r.cabane(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please look a this bug I filed : https://bugs.documentfoundation.org/show_bug.cgi?id=119091 The mysql-connector-java (version 5.1.43) as supplied by the OpenSUSE 15.0 distribution is either flawed or incompatible with Libreoffice 6. I solved the case installing the Mariadb connector from the Mariadb website. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 987114] New: Bluetooth headset connected but not showing under 'Sound Settings'
by bugzilla_noreply＠novell.com 16 Nov '22

16 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 Bug ID: 987114 Summary: Bluetooth headset connected but not showing under 'Sound Settings' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: damien.lloyd21(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build Identifier: On openSUSE Tumbleweed, my bluetooth headset pairs and connects successfully through GNOME's bluetooth interface, but after going to the 'Sound Settings' my bluetooth headset doesn't show up, even though it is paired up. Because I can't see my bluetooth headset under 'Sound Settings' it's not possible to re-route sound through it, which means I can't use my bluetooth headset. Reproducible: Always Steps to Reproduce: 1. Make bluetooth headset discoverable; 2. Open up GNOME's bluetooth interface and select bluetooth headset; 3. Connect to bluetooth headset; 4. Once paired, access 'Sound Settings': bluetooth headset doesn't show up. Actual Results: The bluetooth headset doesn't show up under 'Sound Settings' even though it is connected and paired. Expected Results: The bluetooth headset should appear under 'Sound Settings' so that sound can be re-routed through it. My headset is a UE MEGABOOM and it worked under Ubuntu 14.04/16.04 extremely well. It doesn't work under openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1180037] New: X11:Utilities/WoeUSB: Version upgrade
by bugzilla_noreply＠suse.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180037 Bug ID: 1180037 Summary: X11:Utilities/WoeUSB: Version upgrade Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: nopeinomicon(a)posteo.net QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- This software is reasonably outdated as of now. The version packaged is the last version from the project's old git repo, but development has progressed much further. This would be an easy issue to take care of to resubmit the newer package, but the problem is the GUI component is no longer maintained, only the CLI tool. This should be resolved in some way, either by stripping the GUI entirely, or packaging the newer version separately, or some other way at the discretion of the maintainer of course. At the following link is the old Git repo, the readme explains the current state of development, including the depreciation of the GUI found in the package here: https://github.com/slacka/WoeUSB -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1110245] New: Connection to online repositories should be HTTPS
by bugzilla_noreply＠novell.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1110245 Bug ID: 1110245 Summary: Connection to online repositories should be HTTPS Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: digitalmon(a)rambler.ru QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Although the online repository servers support HTTPS connection, downloading of packets still occurs via the HTTP protocol. This compromises the security of users. If their connection to the Internet is intercepted, if they work through any proxy server, the attackers can modify the packages on the fly during the download. To install malware and spyware into target system. At the moment, you can only manually change the URLs of the repositories to https so that the packets are downloaded over a secure channel. I want that by default in the operating system the connection to the online-repositories, the downloading of packets, should be with HTTPS connection. This will make users' safety a step higher. I'm sure there will be less glitches, bugs in user systems. But Https is not a panacea. She is also vulnerable to the attack of MITM. The private surveilance service known to me, generates its own RSA-keys to encrypt the HTTPS, brute-force for them a digital signature so that the browser of user does not suspect forgery. The attacker's computer connects to the remote server by https, downloads packages, replaces executable files, infects them with a virus, and the user gives https traffic with his encryption key and a digital signature. But such an attack is not for everyone. To make it more difficult, you need to use long encryption keys and digital signatures on the repository servers. RSA4096 at least. I know that even LTE-connection to the Internet can be intercepted with using of special technical means and OpenLTE, so I do not trust to LTE. LTE-connection can work without encryption, and 3G connection seems to be always encrypted. A wired connection to the Internet, to intercept - generally easy. As PPPoe, as DHCP (DHCP is without authorization and verification of provider access point). The 3G modem with a good antenna has the same speed as the LTE. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1170409] New: update-test-trivial: TW test maintenance updates do not work
by bugzilla_noreply＠novell.com 14 Nov '22

14 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1170409 Bug ID: 1170409 Summary: update-test-trivial: TW test maintenance updates do not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The test maintenance update is broken in openSUSE:Factory:Update. Installing update-test-trivial from the TW OSS repository does make the zypper maintenance update available/needed, despite it being in the repository. This indicates that the maintenance update stack is not being tested in Tumbleweed. Same for (at least) update-test-security. Install the non-updated package: $ zypper in --from tw-oss update-test-trivial $ zypper search -s -t package update-test-trivial.x86_64 S | Name | Type | Version | Arch | Repository ---+---------------------+---------+---------+--------+----------- v | update-test-trivial | package | 5-5.1 | x86_64 | tw-update i+ | update-test-trivial | package | 5-4.11 | x86_64 | tw-oss v | update-test-trivial | package | 5-4.1 | x86_64 | tw-update Update is not available: $ zypper lp No updates found. But a newer packages is available: $ zypper lu S | Repository | Name | Current Version | Available Version | Arch --+------------+---------------------+-----------------+-------------------+------- v | tw-update | update-test-trivial | 5-4.11 | 5-5.1 | x86_64 The patch seems to refer a previous package $ zypper info -t patch update-test-trivial Information for patch update-test-trivial: ------------------------------------------ Repository : tw-update Name : update-test-trivial Version : 1 Arch : noarch Vendor : BenniBrunner Status : applied Category : recommended Severity : low Created On : Thu Mar 1 11:28:21 2018 Interactive : --- Summary : Test-update for openSUSE Tumbleweed Description : This is a trivial test-update for openSUSE Tumbleweed. Provides : patch:update-test-trivial = 1 Conflicts : [4] update-test-trivial.src < 5-4.1 update-test-trivial.noarch < 5-4.1 update-test-trivial.x86_64 < 5-4.1 update-test-trivial.i586 < 5-4.1 -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1189003] New: Yast is unable to handle encrypted disk
by bugzilla_noreply＠suse.com 14 Nov '22

14 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 Bug ID: 1189003 Summary: Yast is unable to handle encrypted disk Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 851486 --> http://bugzilla.opensuse.org/attachment.cgi?id=851486&action=edit Screenshot showing problem and details When trying an update or installation, Yast detects an encrypted disk, asks for the password, and unlocks it, but then is unable to continue (see attachment). The device /dev/mapper/cr-auto-1 is there when Yast claims it is not. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1179492] New: Test grub booting using pe/coff boot entry to support shim and MOK
by bugzilla_noreply＠suse.com 12 Nov '22

12 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1179492 Bug ID: 1179492 Summary: Test grub booting using pe/coff boot entry to support shim and MOK Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: mchang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To support shim lock protocol and use MOK (Machine Owner Key), grub has to load and boot the kernel on it's own without resorting to firmware protocols, namely UEFI LoadImage and StartImage protocols, which would only know about keys in db and dbx and thus would reject image with signature of MOK. To finalize UEFI Secure Boot to fully utilize the capability of shim, the grub package with needed implementation to achieve that is available here. https://build.opensuse.org/package/show/home:michael-chang:arm64-linuxefi/g… In a nut shell, it will call out shim_lock protocol to verify the image, and then jump directly to the PE/COFF entry to boot the image if preceding verification goes successfully. This ticket is opened to track any issue in grub with respect to needed change to adopt shim and MOK on aarch64. -- You are receiving this mail because: You are on the CC list for the bug.

1 6