March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1052592] New: iBus daemon crashes when changing runlevel
by bugzilla_noreply＠novell.com 09 Jun '20

09 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1052592 Bug ID: 1052592 Summary: iBus daemon crashes when changing runlevel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sonichedgehog_hyperblast00(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The iBus daemon crashes whenever switching to a different runlevel and back. To reproduce this problem: - Make sure the iBus daemon is running. By default, you should have an icon in the system tray indicating the selected language. - Press Control + Alt + F1 to switch to a console. - Press Control + Alt + F7 to switch back to your session. - Look at the system tray, and you will notice the iBus icon disappears in a few seconds. If you open the iBus preferences panel, you will be told the daemon is not running and be prompted to start it back up. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1042136] New: Is OOO_FORCE_DESKTOP=gnome still required in /etc/X11/xim.d/ibus?
by bugzilla_noreply＠novell.com 09 Jun '20

09 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1042136 Bug ID: 1042136 Summary: Is OOO_FORCE_DESKTOP=gnome still required in /etc/X11/xim.d/ibus? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kyrimis(a)alumni.princeton.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In /etc/X11/xim.d/ibus, the OOO_FORCE_DESKTOP is explicitly set to gnome. I remember that, a while back, if I set OOO_FORCE_DESKTOP to kde4, switching keyboard languages would stop working in LibreOffice. However, I just tried it today, and switching keyboard languages works fine. Is this setting still required, or can it now be removed safely? -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1033626] New: pam_securetty in /etc/pam.d/login or not
by bugzilla_noreply＠novell.com 08 Jun '20

08 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1033626 Bug ID: 1033626 Summary: pam_securetty in /etc/pam.d/login or not Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: sbrabec(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jengelh(a)inai.de Found By: --- Blocker: --- pam_securetty was removed from /etc/pam.d/login with the argument that remote logins use /etc/pam.d/remote anyways. However, when using a serial line with getty that is usually not the case and I think the original use case for pam_securetty. So in order to keep existing configs working and make use cases like machinectl work at the same time I'd suggest to put pam_securetty back into the config file but not ship an /etc/securetty by default anymore. Without /etc/securetty pam_securetty would just fall through. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1078485] New: python-base test_multiprocessing on self.assertTrue(got_signal[0]) failure ppc64le
by bugzilla_noreply＠novell.com 08 Jun '20

08 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1078485 Bug ID: 1078485 Summary: python-base test_multiprocessing on self.assertTrue(got_signal[0]) failure ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 758227 --> http://bugzilla.suse.com/attachment.cgi?id=758227&action=edit python_base_ring1_failure_20180131.log.gz python-base test_multiprocessing on self.assertTrue(got_signal[0]) failure ppc64le in ring1 (1) (1) https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC:… === [ 3443s] 0:06:51 load avg: 0.63 [223/395] test_multiprocessing [ 3443s] /home/abuild/rpmbuild/BUILD/Python-2.7.14/Lib/threading.py:846: DeprecationWarning: sys.exc_clear() not supported in 3.x; use except clauses [ 3443s] self.__exc_clear() [ 3505s] test test_multiprocessing failed -- Traceback (most recent call last): [ 3505s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.14/Lib/test/test_multiprocessing.py", line 2346, in test_poll_eintr [ 3505s] self.assertTrue(got_signal[0]) [ 3505s] AssertionError: False is not true [ 3505s] [ 3505s] 0:07:53 load avg: 0.70 [224/395/1] test_mutants -- test_multiprocessing failed in 1 min 2 sec === -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 948280] New: windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add hardening options?
by bugzilla_noreply＠novell.com 06 Jun '20

06 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=948280 Bug ID: 948280 Summary: windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add hardening options? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: gerald(a)wireshark.org QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, idonmez(a)suse.com, mkbosmans(a)gmail.com, tlillqvist(a)suse.com Found By: --- Blocker: --- It doesn't appear that any of the mingw:win32 or mingw:win64 packages are built with hardening options enabled, e.g. --dynamicbase, --nxcompat, and --highentropyva. Would it be possible to do so? -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 974835] New: bluetooth conflict between 2 users
by bugzilla_noreply＠novell.com 05 Jun '20

05 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=974835 Bug ID: 974835 Summary: bluetooth conflict between 2 users Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- i open a kde session for user1 i enable bluetooth with bluedevil. i need this permanently for user1. then i open a kde session for users2 i disable bluetooth with bluedevil. i don't need this for user2. i close the session for user2 then i return to user1 kde session. i tried to connect my bluetooth headset to see a video. this fails. i search in the systray. no more bluetooth icon. bluetooth is disabled ! -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 911001] New: dnsmasq apparmor profile prevents libvirt default network to start
by bugzilla_noreply＠novell.com 05 Jun '20

05 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=911001 Bug ID: 911001 Summary: dnsmasq apparmor profile prevents libvirt default network to start Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: cbosdonnat(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This commit in libvirt forces dnsmasq to actually use the leaseshelper program: http://libvirt.org/git/?p=libvirt.git;a=commit;h=421406808abaf7eb66abd27d71… The problem is that the dnsmasq apparmor profile prevents the libvirt default network to start due to: * Not allowing /bin/bash to be run * Not allowing leaseshealper contained in /usr/lib64 folder to be run. Note that this bug may hit 13.2 if an updated libvirt is shipped there. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 972668] New: XServer and raspberrypi-userland don't work together on openSUSE-Tumbleweed-ARM
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=972668 Bug ID: 972668 Summary: XServer and raspberrypi-userland don't work together on openSUSE-Tumbleweed-ARM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: notavailable(a)posteo.de QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 670514 --> http://bugzilla.suse.com/attachment.cgi?id=670514&action=edit Xorg.0.log When you install raspberrypi-userland on TW ARM images with a desktop environment, XServer doesn't start anymore. I could not use any of the latest images (2016.03.24) with E20, LXQt and Xfce. These are the errors I get with Xfce. Instead Xorg.0.log simply shows the following message at the end: "Server terminated successfully (0). Closing log file." Starting programs from the command-line gives the output: "nohostname:~ # yast2 /usr/lib/YaST2/bin/y2controlcenter: error while loading shared libraries: libGLESv2.so.2: cannot open shared object file: No such file or directory" "nohostname:~ # firefox XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so: libEGL.so.1: cannot open shared object file: No such file or directory Couldn't load XPCOM." During the installation process of raspberrypi-userland there are two messages: "/sbin/ldconfig: /usr/lib/libEGL.so is not a symbolic link" "/sbin/ldconfig: /usr/lib/libGLESv2.so is not a symbolic link" When you reinstall raspberrypi-userland with the -f option, you get this output: nohostname:~ # yast2 Unable to find an X11 visual which matches EGL config 20 Could not initialize OpenGL for RasterGLSurface, reverting to RasterSurface. /sbin/yast2: line 440: 1382 Speicherzugriffsfehler (core dumped) $y2ccbin $Y2UI_ARGS "$@" nohostname:~ # firefox XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so: /usr/lib/libEGL.so.1: undefined symbol: glDiscardFramebufferEXT Couldn't load XPCOM. The second installation creates two symlinks in /usr/lib/: libEGL.so.1 and libGLESv2.so.2 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1000507] New: cannot boot encrypted disk installed on one PC on another
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1000507 Bug ID: 1000507 Summary: cannot boot encrypted disk installed on one PC on another Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 693700 --> http://bugzilla.suse.com/attachment.cgi?id=693700&action=edit initrd log I installed a system with disk encryption in one PC. Tried to move it to another PC and it would not boot. It asks for the passphrase, waits a long time, and then prints Failed to start Cryptography Setup for cr_ata_<disk manufacturer and model>_part2. I suspect it may be trying to use a crypto accelerator that does not exist. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1087151] New: No options to switch DisplayManager with /etc/sysconfig Editor
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1087151 Bug ID: 1087151 Summary: No options to switch DisplayManager with /etc/sysconfig Editor Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: terje(a)nordland-teknikk.no QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The Leap 15 YaST2 /etc/sysconfig Editor on Leap 15.0 with Gnome installed as Desktop and Plasma software pattern added, contains no option to switch between GDM and typical SDDM: Desktop > Display manager > DISPLAYMANAGER : gdm (option Xorg only, no sddm) Desktop > Windows manager > Default_WM: gnome (no other options like Plasma5) In comparision on Leap 42.3: DISPLAYMANAGER : gdm (options: kdm, xdm, wdm, entrance, console, lightdm, sddm) Default_WM: gnome (options: kde4, kde, lxde, xfce, twm, icewm etc) This bug is related to Bug 1082713 https://bugzilla.suse.com/show_bug.cgi?id=1082713 -- You are receiving this mail because: You are on the CC list for the bug.

2 5