July 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1040812] New: KDE:Qt5/libqt5-qtbase: Bug: KDE:Qt5 has been upgraded to QT 5.9, publishing is OFF
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1040812 Bug ID: 1040812 Summary: KDE:Qt5/libqt5-qtbase: Bug: KDE:Qt5 has been upgraded to QT 5.9, publishing is OFF Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: hrvoje.senjan(a)gmail.com Reporter: Mathias.Homann(a)opensuse.org QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Again KDE:Qt5 has been up- or downgraded, this time to Qt 5.9, but publishing is OFF, so AGAIN all repositories that build using Qt5 are broken. FIX ASAP. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1173619] New: VUL-0: unbound: LPE from unbound to root
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1173619 Bug ID: 1173619 Summary: VUL-0: unbound: LPE from unbound to root Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: darin(a)darins.net Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- via security(a)suse.de: I believe to have found a configuration issue in the Unbound package. Or, depending on how you look at it, in the Unbound server itself. 1. Before starting the Unbound server, systemd routinely runs unbound-anchor. From 'systemctl cat unbound': ExecStartPre=/usr/bin/sudo -u unbound /usr/sbin/unbound-anchor -a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem As you can see this process is run as user unbound. 2. The Unbound server writes a pid file before dropping privileges, i.e. as root. It then chown's the file in a second step. 'grep username /etc/unbound/unbound.conf': username: "unbound" And from the Unbound source: https://github.com/NLnetLabs/unbound/blob/2a90e8fa1e22aa75d1cf67a1f71ebbf3f… As you can see in the source, Unbound doesn't check if there is already a symbolic link in place of the pid file. 3. openSUSE configures Unbound to create the pid file in a directory owned by the unbound user. 'grep pidfile /etc/unbound/unbound.conf': pidfile: "/var/run/unbound/unbound.pid" 'cat /usr/lib/tmpfiles.d/unbound.conf': D /run/unbound 0755 unbound unbound - 4. unbound-anchor is a nice little "do-one-thing-and-do-it-right" tool. But if it is compromised, and as it has write permission in the pid file directory and reliably runs before the server, an attacker could easily gain full root privileges by just creating a symbolic link /run/unbound/unbound.pid. 5. IMHO this would be best fixed in openSUSE by creating a root owned /run/unbound directory, or changing the pid file path to /run/unbound.pid or something like that. I think this would have the added advantage that openSUSE could ship and maybe enforce the Unbound AppArmor profile used in Debian and Ubuntu: https://gitlab.com/apparmor/apparmor-profiles/-/blob/master/ubuntu/20.04/us… With the current openSUSE setup there is the problem that if AppArmor filters CAP_DAC_OVERRIDE, Unbound has no permission to create a pid file in /run/unbound anymore. If you have questions please don't hesitate to contact me. Thanks for taking a look. Kind regards, Detlef -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1174051] New: opensuse-community.org links not working
by bugzilla_noreply＠suse.com 19 Feb '23

19 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1174051 Bug ID: 1174051 Summary: opensuse-community.org links not working Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Wiki Assignee: suse-beta(a)cboltz.de Reporter: e-dimas(a)yandex.ru QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- I am trying to install codecs using "opensuse-community.org" But links to "KDE Codecs", "GNOME Codecs", "NVIDIA Graphics Card Driver" do not work. I use the browser Firefox. If you enter "https://opensuse-community.org/codecs-kde.ymp" in the address bar, the installation of codecs starts. Please fix the links "1 Click Install". -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1174184] New: mozilla/firefox78: Bug
by bugzilla_noreply＠suse.com 19 Feb '23

19 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1174184 Bug ID: 1174184 Summary: mozilla/firefox78: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software Assignee: wolfgang(a)rosenauer.org Reporter: bauglir(a)fsfe.org QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 839753 --> http://bugzilla.opensuse.org/attachment.cgi?id=839753&action=edit Error message openSuSE Leap 15.2: After upgrading to latest Firefox 78.0.2 version, current profile opens once and then it starts showing an error window with attatched message. There's no problem opening new profiles, just opening old profiles. -- You are receiving this mail because: You are on the CC list for the bug.

1 57

[Bug 1165830] New: [TRACKER] grand distro cleanup
by bugzilla_noreply＠novell.com 15 Feb '23

15 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1165830 Bug ID: 1165830 Summary: [TRACKER] grand distro cleanup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: lnussel(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- track efforts to clean up the distro like /usr move /etc cleanup dependency cleanup -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 1167519] New: VUL-1: CVE-2020-10870: zim: creates temporary directories with predictable names, enabling malicious users to prevent other users from being able to start Zim
by bugzilla_noreply＠novell.com 15 Feb '23

15 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1167519 Bug ID: 1167519 Summary: VUL-1: CVE-2020-10870: zim: creates temporary directories with predictable names, enabling malicious users to prevent other users from being able to start Zim Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/255622/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: luke(a)ljones.dev Reporter: wolfgang.frisch(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2020-10870 Zim through 0.72.1 creates temporary directories with predictable names. A malicious user could predict and create Zim's temporary directories and prevent other users from being able to start Zim, resulting in a denial of service. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-10870 https://github.com/zim-desktop-wiki/zim-desktop-wiki/issues/1028 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10870 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1170553] New: [Build 20200425] gnuhealth UI looks broken with GNOME 3.36
by bugzilla_noreply＠novell.com 12 Feb '23

12 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1170553 Bug ID: 1170553 Summary: [Build 20200425] gnuhealth UI looks broken with GNOME 3.36 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1245677/modules/gnuh ealth_client_preconfigure/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-gnuhealth@64bit fails in [gnuhealth_client_preconfigure](https://openqa.opensuse.org/tests/1245677/mo… ## Test suite description Maintainer: okurz(a)suse.de Test scenario for gnuhealth software stack ## Reproducible Fails since (at least) Build [20200423](https://openqa.opensuse.org/tests/1245318) ## Expected result Last good: [20200422](https://openqa.opensuse.org/tests/1243312) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1131707] New: VUL-1: CVE-2019-10868: In trytond/model/modelstorage.py in Tryton 4.2 before 4.2.21, 4.4 before 4.4.19, 4.6 before 4.6.14, 4.8 before 4.8.10, and 5.0 before 5.0.6, an authenticated user can order records based on a field for which he has no
by bugzilla_noreply＠novell.com 12 Feb '23

12 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1131707 Bug ID: 1131707 Summary: VUL-1: CVE-2019-10868: In trytond/model/modelstorage.py in Tryton 4.2 before 4.2.21, 4.4 before 4.4.19, 4.6 before 4.6.14, 4.8 before 4.8.10, and 5.0 before 5.0.6, an authenticated user can order records based on a field for which he has no Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/228999/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: axel.braun(a)gmx.de Reporter: atoptsoglou(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2019-10868 In trytond/model/modelstorage.py in Tryton 4.2 before 4.2.21, 4.4 before 4.4.19, 4.6 before 4.6.14, 4.8 before 4.8.10, and 5.0 before 5.0.6, an authenticated user can order records based on a field for which he has no access right. This may allow the user to guess values. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-10868 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10868 https://hg.tryton.org/trytond/rev/f58bbfe0aefb https://discuss.tryton.org/t/security-release-for-issue8189/1262 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1131096] New: [Build 20190329] GNUHealth no longer installable
by bugzilla_noreply＠novell.com 12 Feb '23

12 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1131096 Bug ID: 1131096 Summary: [Build 20190329] GNUHealth no longer installable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/895777/modules/gnuhe alth_client_install/steps/19 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-gnuhealth@64bit fails in [gnuhealth_client_install](https://openqa.opensuse.org/tests/895777/modules/… ## Test suite description Maintainer: okurz(a)suse.de Test scenario for gnuhealth software stack ## Reproducible Fails since (at least) Build [20190328](https://openqa.opensuse.org/tests/894742) ## Expected result Last good: [20190327](https://openqa.opensuse.org/tests/894056) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?flavor=DVD&version=Tumblew… The package python-GooCalendar no longer exists due to changes in https://build.opensuse.org/request/show/689360 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1173919] New: Hawk backend fails to start
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1173919 Bug ID: 1173919 Summary: Hawk backend fails to start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: john.goutbeck(a)newsignal.ca QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0 Build Identifier: did another fresh clean server install of openSUSE Leap 15.2, use openSUSE repositories set IP zypper in hawk2 zypper in ha-cluster-bootstrap ha-cluster-init - no sbd systemctl restart hawk systemctl restart hawk-backend with the browser (from a Win 10 laptop) https://192.168.12.242:7630/ - get certificate error - accept BLANK screen -- systemctl status hawk ● hawk.service - HA Web Konsole Loaded: loaded (/usr/lib/systemd/system/hawk.service; enabled; vendor preset> Active: active (running) since Mon 2020-07-06 21:43:25 MDT; 17min ago Main PID: 1903 (hawk-apiserver) But not the hawk-backend systemctl status hawk-backend ● hawk-backend.service - HA Web Konsole Backend Loaded: loaded (/usr/lib/systemd/system/hawk-backend.service; static; vendor> Active: failed (Result: exit-code) since Mon 2020-07-06 22:01:52 MDT; 5s ago Process: 14663 ExecStart=/usr/bin/puma.ruby2.5 -C /usr/share/hawk/config/puma> Main PID: 14663 (code=exited, status=1/FAILURE) So, looking at the /var/log/messages file, this is what I get --- 2020-07-06T21:52:07.277099-06:00 nss-leap152 systemd[1]: Started HA Web Konsole Backend. 2020-07-06T21:52:07.393681-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] Puma starting in cluster mode... 2020-07-06T21:52:07.393886-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Version 3.11.0 (ruby 2.5.8-p224), codename: Love Song 2020-07-06T21:52:07.393999-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Min threads: 0, max threads: 1 2020-07-06T21:52:07.394113-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Environment: production 2020-07-06T21:52:07.394231-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Process workers: 1 2020-07-06T21:52:07.394350-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Preloading application 2020-07-06T21:52:07.710011-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] ! Unable to load application: Gem::ConflictError: Unable to activate sass-rails-5.1.0, because railties-5.1.4 conflicts with railties (>= 5.2.0) 2020-07-06T21:52:07.710267-06:00 nss-leap152 puma.ruby2.5[10033]: /usr/lib64/ruby/2.5.0/rubygems/specification.rb:2327:in `raise_if_conflicts': Unable to activate sass-rails-5.1.0, because railties-5.1.4 conflicts with railties (>= 5.2.0) (Gem::ConflictError) 2020-07-06T21:52:07.710480-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/specification.rb:1438:in `activate' 2020-07-06T21:52:07.710599-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' 2020-07-06T21:52:07.710749-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `synchronize' 2020-07-06T21:52:07.710878-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem' 2020-07-06T21:52:07.710991-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/boot.rb:35:in `<top (required)>' 2020-07-06T21:52:07.711074-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 2020-07-06T21:52:07.711158-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 2020-07-06T21:52:07.711239-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/application.rb:4:in `<top (required)>' 2020-07-06T21:52:07.711320-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/environment.rb:5:in `require_relative' 2020-07-06T21:52:07.711400-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/environment.rb:5:in `<top (required)>' 2020-07-06T21:52:07.711477-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 2020-07-06T21:52:07.711573-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 2020-07-06T21:52:07.711650-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:4:in `block in <main>' 2020-07-06T21:52:07.711726-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:55:in `instance_eval' 2020-07-06T21:52:07.711804-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:55:in `initialize' 2020-07-06T21:52:07.711880-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:in `new' 2020-07-06T21:52:07.711957-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:in `<main>' 2020-07-06T21:52:07.712037-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:49:in `eval' 2020-07-06T21:52:07.712114-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:49:in `new_from_string' 2020-07-06T21:52:07.712186-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:40:in `parse_file' 2020-07-06T21:52:07.712257-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/configuration.rb:318:in `load_rackup' 2020-07-06T21:52:07.712327-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/configuration.rb:243:in `app' 2020-07-06T21:52:07.712401-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/runner.rb:138:in `load_and_bind' 2020-07-06T21:52:07.712472-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/cluster.rb:397:in `run' 2020-07-06T21:52:07.712540-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/launcher.rb:183:in `run' 2020-07-06T21:52:07.712611-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/cli.rb:77:in `run' 2020-07-06T21:52:07.712680-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/bin/puma:10:in `<top (required)>' 2020-07-06T21:52:07.712772-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/bin/puma.ruby2.5:23:in `load' 2020-07-06T21:52:07.712848-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/bin/puma.ruby2.5:23:in `<main>' 2020-07-06T21:52:07.713821-06:00 nss-leap152 systemd[1]: hawk-backend.service: Main process exited, code=exited, status=1/FAILURE 2020-07-06T21:52:07.714104-06:00 nss-leap152 systemd[1]: hawk-backend.service: Unit entered failed state. 2020-07-06T21:52:07.714242-06:00 nss-leap152 systemd[1]: hawk-backend.service: Failed with result 'exit-code'. --- query the rpm nss-leap152:~ # rpm -qa | grep railties ruby2.5-rubygem-railties-5_1-5.1.4-lp152.3.3.x86_64 ruby2.5-rubygem-railties-5.2-5.2.3-lp152.2.3.x86_64 nss-leap152:~ # rpm -qa | grep sass ruby2.5-rubygem-sass-3.5.3-lp152.3.3.x86_64 ruby2.5-rubygem-sass-rails-5.1-5.1.0-lp152.1.1.x86_64 ruby2.5-rubygem-sass-listen-4.0.0-lp152.3.3.x86_64 --- nss-leap152:~ # zypper up Loading repository data... Reading installed packages... Nothing to do. nss-leap152:~ # zypper in -force hawk The flag o is not known. nss-leap152:~ # update-alternatives --config rails There are 2 choices for the alternative rails (providing /usr/bin/rails). Selection Path Priority Status ------------------------------------------------------------ * 0 /usr/bin/rails.ruby2.5-5.2.3 50203 auto mode 1 /usr/bin/rails.ruby2.5-5.1.4 50104 manual mode 2 /usr/bin/rails.ruby2.5-5.2.3 50203 manual mode - I chose option 1, 2 and back to 0, still no joy - restart hawk and hawk-backend in-between options. --- zypper in -f hawk2 Loading repository data... Reading installed packages... Forcing installation of 'hawk2-2.1.1+git.1585238036.fab19246-lp152.1.9.x86_64' from repository 'Main Repository'. Resolving package dependencies... The following package is going to be reinstalled: hawk2 1 package to reinstall. Overall download size: 9.3 MiB. Already cached: 0 B. No additional space will be used or freed after the operation. Continue? [y/n/v/...? shows all options] (y): Retrieving package hawk2-2.1.1+git.1585238036.fab19246-lp152.1.9.x86_64 (1/1), 9.3 MiB ( 20.6 MiB unpacked) Retrieving: hawk2-2.1.1+git.1585238036.fab19246-lp152.1.9.x86_64.rpm ..............................................[done (3.7 MiB/s)] Checking for file conflicts: ..................................................................................................[done] (1/1) Installing: hawk2-2.1.1+git.1585238036.fab19246-lp152.1.9.x86_64 ........................................................[done] Additional rpm output: Updating /etc/sysconfig/hawk ... systemctl restart hawk systemctl restart hawk-backend - still BLANK whit screen - no joy Reproducible: Always Steps to Reproduce: 1. Install Server based openSUSE Leap 15.2 2. zypper in hawk2 3. zypper in ha-cluster-bootstrap 4. ha-cluster-init with the browser (from a Win 10 laptop) https://192.168.12.242:7630/ - get certificate error - accept BLANK white screen Actual Results: BLANK whit screen no HAWK2 login Expected Results: HAWK2 Login screen & HAWK 2 UI -- You are receiving this mail because: You are on the CC list for the bug.

1 9