July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201125] New: power-profiles-daemon DBus service configuration file moved from /etc to /usr/share
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201125 Bug ID: 1201125 Summary: power-profiles-daemon DBus service configuration file moved from /etc to /usr/share Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com, matthias.gerstner(a)suse.com Depends on: 1189900 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1189900 +++ With version 0.12, power-profiles-daemon has moved its dbus conf file to /usr/share/dbus-1/ instead of /etc/dbus-1/, so rpmlint complains again: > power-profiles-daemon.x86_64: E: dbus-file-unauthorized (Badness: 10) /usr/share/dbus-1/system.d/net.hadess.PowerProfiles.conf Requesting a modification of the white-listing in rpmlint before I submit this package to Factory. Test packages here: https://build.opensuse.org/package/show/home:badshah400:branches:Base:Syste… Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1200344] New: AUDIT-WHITELIST: dnsmasq: move dbus system.d file to /usr
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200344 Bug ID: 1200344 Summary: AUDIT-WHITELIST: dnsmasq: move dbus system.d file to /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: gmbr3(a)opensuse.org QA Contact: qa-bugs(a)suse.de CC: max(a)suse.com Found By: --- Blocker: --- Move /etc/dbus-1/system.d/dnsmasq.conf to /usr/share/dbus-1/system.d/dnsmasq.conf Devel prj: network Maintainer: Reinhard Max <max(a)suse.com> -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1197978] New: Qt Creator (qt5-creator-plugin-devel) has no QtCreatorConfig.cmake
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197978 Bug ID: 1197978 Summary: Qt Creator (qt5-creator-plugin-devel) has no QtCreatorConfig.cmake 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: w01dnick(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With Qt Creator 7 plugin qmake support was removed and only cmake is supported. I've tried to move my plugin to cmake, but there are no plugin cmake files in `qt5-creator-plugin-devel` (or `qt5-creator`) packages. qt.io binaries have `lib/cmake/QtCreator` directory with `QtCreatorConfig.cmake` and other cmake files, but there is no similar directory (`/usr/lib64/cmake/qt5-creator` or `/usr/lib64/cmake/QtCreator` or `/usr/lib64/cmake/Qt5Creator`) in our RPMs. So I can't build even "empty" plugin just created by QtCreator's wizard. I've tried to dig slightly into it (almost zero cmake knowledge), on build stage there is cmake folder with `QtCreatorConfig.cmake` in it created by `src/CMakeLists.txt` but for some reason they are not present in install (though they seem should be there as `install()` is present in that CMakeLists). It'd be nice to have them in RPMs to be able to build Qt Creator plugins. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1201015] [SELinux] transactional-update can't run with selinux=permissive under cloud-init
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201015 https://bugzilla.suse.com/show_bug.cgi?id=1201015#c4 --- Comment #4 from Johannes Segitz <jsegitz(a)suse.com> --- I can't get cloud-init to execute this. I followed https://en.opensuse.org/Portal:MicroOS/cloud-init but it ignores my config file. I tried it with my existing VM and with a fresh qcow2 downloaded from official sources. I feel dumb for asking, but I need a step by step instruction on how to get this running. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198214] New: 15.3, firewalld mostly doesnt autostart on bootup any more - since february 2022,
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198214 Bug ID: 1198214 Summary: 15.3, firewalld mostly doesnt autostart on bootup any more - since february 2022, Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 15.3, x64, multiple ethernet interfaces, simple ipv4 router nat machine. ever since sometime in february 2022, when rebooting the machine, firewalld doesnt succeed to start up on reboot or startup any more even though its set as enabled. using wicked on this machine, been a long history of previous opensuse suse updates and upgrades with this machine, right now its on opensuse 15.3 leap. one ethernet interface (its address) is on dhcp4 shown in yast, the other ethernet interface is fixed ipv4 assigned to it. journalctl -u firewalld.service shows the following in february 2022, and then ever since, but not always all the time warning not enabled eth0 warning not enabled eth1 and as of end of march 2022 even such red lines and details about: firewalld[2914]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'INIT', Fals> I need to ssh connect to the machine then and fire up the firewalld service manually. Even though it is at enabled (vendor preset disabled). What happened as of february 2022 and what happend at the end of march for those red status lines? this machine and its firewalld worked perfectly for many years, and a long time in 15.3 up until february 2022. how to find out more about whats happening? ty. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c15 --- Comment #15 from Alan Hughes <alanhants(a)gmail.com> --- (In reply to Thomas Zimmermann from comment #13) > (In reply to Stefan Dirsch from comment #11) > > Hmm. Please try with kernel boot option 'nosimplefb'. Does this issue also > > occur with older kernels? > > Please try this option on the kernel's command line. I tried this, and also tried adding it to the boot options in GRUB (using YaST). As previously stated, this had no effect. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c14 --- Comment #14 from Alan Hughes <alanhants(a)gmail.com> --- Forgot to mention, this problem does not occur with the previous kernel (5.18.9-1); in fact I am roll back to this kernel to allow me to continue to use the system. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c13 Thomas Zimmermann <tzimmermann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #13 from Thomas Zimmermann <tzimmermann(a)suse.com> --- (In reply to Stefan Dirsch from comment #11) > Hmm. Please try with kernel boot option 'nosimplefb'. Does this issue also > occur with older kernels? Please try this option on the kernel's command line. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c12 --- Comment #12 from Alan Hughes <alanhants(a)gmail.com> --- (In reply to Stefan Dirsch from comment #10) > (In reply to Stefan Dirsch from comment #6) > > Hmm. modeset driver gets loaded, but I don't think it's really getting > > active. nvidia is already loaded and is the higher prioritized driver. But > > you can try with > > > > options nvidia-drm modeset=0 > > > > in /etc/modprobe.d/50-nvidia-default.conf to prevent modeset driver loaded. > > I mean replace the line > > options nvidia-drm modeset=1 > > then run 'mkintird' afterwards and reboot the machine. Does this help? That is what I did. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c11 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tzimmermann(a)suse.com --- Comment #11 from Stefan Dirsch <sndirsch(a)suse.com> --- Hmm. Please try with kernel boot option 'nosimplefb'. Does this issue also occur with older kernels? -- You are receiving this mail because: You are on the CC list for the bug.

1 0