September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1190196] New: xfce4-power-manager segmentation fault then try to operate with a icon in system tray
by bugzilla_noreply＠suse.com 05 Sep '21

05 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190196 Bug ID: 1190196 Summary: xfce4-power-manager segmentation fault then try to operate with a icon in system tray Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Then try to operate with a icon in system tray xfce4-power-manager closes with a error: segmentation fault -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120256] [Build 40.3] openQA test fails in grub_test - textmode installation takes longer than others to exiting installer
by bugzilla_noreply＠suse.com 05 Sep '21

05 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1120256 https://bugzilla.suse.com/show_bug.cgi?id=1120256#c66 --- Comment #66 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: yast2_firstboot_custom_textmode https://openqa.suse.de/tests/6999418 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189440] New: openscad: symbol lookup error: /lib64/libopencsg.so.1: undefined symbol: __glewXGetFBConfigAttribSGIX
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189440 Bug ID: 1189440 Summary: openscad: symbol lookup error: /lib64/libopencsg.so.1: undefined symbol: __glewXGetFBConfigAttribSGIX Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: koenig(a)linux.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- trying to start openscad I get openscad: symbol lookup error: /lib64/libopencsg.so.1: undefined symbol: __glewXGetFBConfigAttribSGIX $ rpm -q libopencsg1 openscad libGLEW2_2 libopencsg1-1.4.2-1.14.x86_64 openscad-2021.01-2.3.x86_64 libGLEW2_2-2.2.0-2.1.x86_64 $ rpm -qi libopencsg1 openscad libGLEW2_2 | grep Dis Distribution: openSUSE Tumbleweed Distribution: openSUSE Tumbleweed Distribution: openSUSE Tumbleweed $ ldd -r /usr/bin/openscad ... undefined symbol: __glewXGetFBConfigAttribSGIX (/lib64/libopencsg.so.1) undefined symbol: __glewXChooseFBConfigSGIX (/lib64/libopencsg.so.1) undefined symbol: __glewXDestroyGLXPbufferSGIX (/lib64/libopencsg.so.1) undefined symbol: __glewXGetCurrentDisplay (/lib64/libopencsg.so.1) undefined symbol: __GLXEW_NV_float_buffer (/lib64/libopencsg.so.1) undefined symbol: __glewXCreateGLXPbufferSGIX (/lib64/libopencsg.so.1) undefined symbol: __glewXGetVisualFromFBConfig (/lib64/libopencsg.so.1) undefined symbol: __glewXCreateContextWithConfigSGIX (/lib64/libopencsg.so.1) undefined symbol: __GLXEW_SGIX_fbconfig (/usr/bin/openscad) undefined symbol: __GLXEW_SGIX_pbuffer (/usr/bin/openscad) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1189687] File or folder does not exist error when connecting Android smartphone to computer
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189687 https://bugzilla.suse.com/show_bug.cgi?id=1189687#c29 --- Comment #29 from Swamp Workflow Management <swamp(a)suse.de> --- # maintenance_jira_update_notice openSUSE-RU-2021:1227-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1189687 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP3 (src): kio-extras5-20.04.2-bp153.3.3.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190186] New: Cannot get to console with newer kernel and nvidia driver
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190186 Bug ID: 1190186 Summary: Cannot get to console with newer kernel and nvidia driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fred.blaise(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852296 --> http://bugzilla.opensuse.org/attachment.cgi?id=852296&action=edit dmesg Hi, Since 5.13.12-2-default, my boot sequence does not get to console anymore (I start my i3 desktop with startx). Same now 5.13.13-1-default. Everything worked fine with what I think was 5.13.8, which of course got delete today when I did a zypper dup... need to find that puppy again. Somewhere after I type my home partition encryption password, the screen freezes and never gets to the prompt. I can however ssh to the box. Everything looks normal then. My home partition is mounted. Just my console display seems stuck. Attached my dmesg and a picture of my frozen console. Removing the nvidia driver - thus using nouveau - it works ok. Just lacking vulkan api and graph performance. I know the nvidiadriver is a never ending debate, but here it is anyways. Wondering what changed in between 5.13.8 and .13. Maybe the delta is small enough that it triggers something in someone's mind. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1187332] zypper ignores the ordering constraints specified by OrderWithRequires
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1187332 https://bugzilla.suse.com/show_bug.cgi?id=1187332#c34 --- Comment #34 from Swamp Workflow Management <swamp(a)suse.de> --- # maintenance_jira_update_notice openSUSE-RU-2021:1226-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1186282,1187332 CVE References: JIRA References: Sources used: openSUSE Leap 15.2 (src): systemd-rpm-macros-8-lp152.8.16.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186282] %sysusers_create_inline needs awkward syntax
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1186282 https://bugzilla.suse.com/show_bug.cgi?id=1186282#c9 --- Comment #9 from Swamp Workflow Management <swamp(a)suse.de> --- # maintenance_jira_update_notice openSUSE-RU-2021:1226-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1186282,1187332 CVE References: JIRA References: Sources used: openSUSE Leap 15.2 (src): systemd-rpm-macros-8-lp152.8.16.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190192] New: systemd-tmpfiles-setup doesn't reliably create all configured paths
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190192 Bug ID: 1190192 Summary: systemd-tmpfiles-setup doesn't reliably create all configured paths Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ralf.koelmel(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852303 --> http://bugzilla.opensuse.org/attachment.cgi?id=852303&action=edit boot log of systemd-tmpfiles-setup the last systemd package version 246.15-7.11.1 provides a systemd-tmpfiles-setup service which doesn't reliably create all configured paths. I had to manually execute the underlying commmand of the systemd-tempfiles-setup after the boot to get all paths: /usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev Often affected services were mariadb with missing /run/mysql directory (/usr/lib/tmpfiles.d/mariadb.conf), zabbix_agentd with missing /run/zabbix directory (configuration under /usr/lib/tmpfiles.d/zabbix_agentd.conf). It seems that this is a runtime exception because these services were not always affected. A new boot after manual correction is working without problems and systemd-tmpfiles-setup doesn't harm the system again. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1189599] systemd watchdog sometime disable on physical and virtual machine
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189599 https://bugzilla.suse.com/show_bug.cgi?id=1189599#c2 --- Comment #2 from Michiya Hagimoto <kokeko(a)mac.com> --- Sorry I don't know this bug on 15.2. I think same reason of bsc#1189446 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188866] New: server:http/nginx: Bug in vim syntax plugin
by bugzilla_noreply＠suse.com 04 Sep '21

04 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188866 Bug ID: 1188866 Summary: server:http/nginx: Bug in vim syntax plugin Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: schubi(a)suse.com Reporter: rpm(a)fthiessen.de QA Contact: screening-team-bugs(a)suse.de CC: achernikov(a)suse.com, suse(a)ammler.ch Found By: --- Blocker: --- Created attachment 851368 --> http://bugzilla.opensuse.org/attachment.cgi?id=851368&action=edit Errorlog of vim when editing the nginx config Since the last Tumbleweed update (as of 2021-07-28) the `vim-plugin-nginx` from the nginx package causes a bunch of warnings when editing nginx configuration files. I guess a vim update broke it, the warnings look like this: > Error detected while processing /etc/vimrc[42]../usr/share/vim/vim82/syntax/syntax.vim[42]..BufRead Autocommands for "*/etc/nginx/*"..FileType Autocommands for "*"..Syntax Autocommands for "*"..function <SNR>3_SynSet[25]..script /usr/share/vim/vim82/syntax/nginx.vim: > line 16: > E10: \ should be followed by /, ? or & > ... I attached the full log. -- You are receiving this mail because: You are on the CC list for the bug.

1 2