openSUSE Bugs June 2019

bugs@lists.opensuse.org

1 participants
3880 discussions

[Bug 1103671] New: Full encryption multiple password tries
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1103671 Bug ID: 1103671 Summary: Full encryption multiple password tries Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: massimo.burcheri(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- New installation of LEAP 15.0 with full encryption including /boot does only prompt once for a password and falls back to shell for a wrong password. 3 password tries with a reasonable error message would be useful for laymen. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1137066] New: Podman: --systemd containers freeze
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137066 Bug ID: 1137066 Summary: Podman: --systemd containers freeze Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: rtorreromarijnissen(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I'm trying to follow https://developers.redhat.com/blog/2019/04/24/how-to-run-systemd-in-a-conta… to run a systemd container (I know systemd inside a container doesn't usually make much sense, but for some development use cases, it does). When following that guide, after starting the container that I just build, I get: $ podman run --systemd=true -ti -p 8000:80 systemd systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Detected virtualization container-other. Detected architecture x86-64. Welcome to Fedora 29 (Container Image)! Set hostname to <92dd1d256183>. Initializing machine ID from random generator. Failed to install release agent, ignoring: Permission denied Failed to create /user.slice/user-1000.slice/session-1.scope/init.scope control group: Permission denied Failed to allocate manager object: Permission denied [!!!!!!] Failed to allocate manager object, freezing. Freezing execution I'm suspecting the +SELINUX -APPARMOR have something to do. Some additional details: $ podman version Version: 1.3.1 RemoteAPI Version: 1 Go Version: go1.12.5 OS/Arch: linux/amd64 $ podman info host: BuildahVersion: 1.8.2 Conmon: package: podman-1.3.1-1.2.x86_64 path: /usr/lib/podman/bin/conmon version: 'conmon version 0.2.0, commit: ' Distribution: distribution: '"opensuse-tumbleweed"' version: "20190529" MemFree: 5762859008 MemTotal: 33643986944 OCIRuntime: package: runc-1.0.0~rc8-1.2.x86_64 path: /usr/bin/runc version: |- runc version 1.0.0-rc8 spec: 1.0.1-dev SwapFree: 0 SwapTotal: 0 arch: amd64 cpus: 4 hostname: nobill-desktop kernel: 5.1.3-1-default os: linux rootless: true uptime: 6h 24m 3.76s (Approximately 0.25 days) registries: blocked: null insecure: null search: - docker.io store: ConfigFile: /home/rtorrero/.config/containers/storage.conf ContainerStore: number: 4 GraphDriverName: vfs GraphOptions: null GraphRoot: /home/rtorrero/.local/share/containers/storage GraphStatus: {} ImageStore: number: 5 RunRoot: /tmp/1000 VolumePath: /home/rtorrero/.local/share/containers/storage/volumes This happens on latest amd64 tumbleweed snapshot. Are there any other details I can provide that might be useful? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133267] LTO: MozillaThunderbird build fails
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1133267 http://bugzilla.suse.com/show_bug.cgi?id=1133267#c5 --- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2019:1484-1: An update that fixes 16 vulnerabilities is now available. Category: security (important) Bug References: 1130694,1133267,1135824 CVE References: CVE-2018-18511,CVE-2019-11691,CVE-2019-11692,CVE-2019-11693,CVE-2019-11694,CVE-2019-11698,CVE-2019-5798,CVE-2019-7317,CVE-2019-9797,CVE-2019-9800,CVE-2019-9815,CVE-2019-9816,CVE-2019-9817,CVE-2019-9818,CVE-2019-9819,CVE-2019-9820 Sources used: openSUSE Leap 42.3 (src): MozillaThunderbird-60.7.0-92.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1130694] rust 1.33.0 breaks Firefox and Thunderbird
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1130694 http://bugzilla.suse.com/show_bug.cgi?id=1130694#c11 --- Comment #11 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2019:1484-1: An update that fixes 16 vulnerabilities is now available. Category: security (important) Bug References: 1130694,1133267,1135824 CVE References: CVE-2018-18511,CVE-2019-11691,CVE-2019-11692,CVE-2019-11693,CVE-2019-11694,CVE-2019-11698,CVE-2019-5798,CVE-2019-7317,CVE-2019-9797,CVE-2019-9800,CVE-2019-9815,CVE-2019-9816,CVE-2019-9817,CVE-2019-9818,CVE-2019-9819,CVE-2019-9820 Sources used: openSUSE Leap 42.3 (src): MozillaThunderbird-60.7.0-92.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1116458] [HPC, macros] Handle Dependencies properly when providers are available both in the default and HPC Module Path
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116458 http://bugzilla.suse.com/show_bug.cgi?id=1116458#c11 --- Comment #11 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2019:1483-1: An update that has 6 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1098653,1102421,1116458,1129421,1133797,934090 CVE References: Sources used: openSUSE Leap 15.0 (src): mvapich2-2.2-lp150.5.3.1, mvapich2-psm-2.2-lp150.5.3.1, mvapich2-psm2-2.2-lp150.5.3.1, mvapich2-psm2_2_2-gnu-hpc-2.2-lp150.5.3.1, mvapich2-psm_2_2-gnu-hpc-2.2-lp150.5.3.1, mvapich2_2_2-gnu-hpc-2.2-lp150.5.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1098653] updating openmpi erases mpi-selector settings
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1098653 http://bugzilla.suse.com/show_bug.cgi?id=1098653#c21 --- Comment #21 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2019:1483-1: An update that has 6 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1098653,1102421,1116458,1129421,1133797,934090 CVE References: Sources used: openSUSE Leap 15.0 (src): mvapich2-2.2-lp150.5.3.1, mvapich2-psm-2.2-lp150.5.3.1, mvapich2-psm2-2.2-lp150.5.3.1, mvapich2-psm2_2_2-gnu-hpc-2.2-lp150.5.3.1, mvapich2-psm_2_2-gnu-hpc-2.2-lp150.5.3.1, mvapich2_2_2-gnu-hpc-2.2-lp150.5.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084792] New: Unplug and replug Keyboard leads to unusable Keyboard for native KDE-Applications
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1084792 Bug ID: 1084792 Summary: Unplug and replug Keyboard leads to unusable Keyboard for native KDE-Applications Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: mail+novell(a)branleb.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using a Thinkpad T520i (Intel(R) Core(TM) i3-2310M CPU @ 2.10 GHz; 16 GiB RAM, 500 GB SSD Disk) with openSuSE Leap 42.3 (Currently Kernel 4.4.114-42-default, X.org X Server 1.118.3, KDE Framework 5.32.0, QT 5.6.2, xf86-input-libinput-0.25.1-1.1.x86_64, libinput-udev-1.5.0-3.5.x86_64, libinput10-1.5.0-3.5.x86_64) and a while ago I first encountered the problem, that native KDE-Applications don't get any keyboard input after unpluggin and replugging the keyboard (e.g. when undocking and redocking the thinkpad to a dock with an usb keyboard) Using the Thinkpad with a dock and a USB-Keyboard connected to it makes this usage quite uncomfortable. The only workaround I could find is logging out and logging in again. Then everything is working again, but as it requires me to stop my work and restart all applications this is not a feasible workaround. This only happens with KDE Applications (plasmarunner, plasmamenu, kate, konsole, etc) not with X, GTK or even simple QT Applications), all other applications just work fine with any keyboard (internal Thinkpad, external USB, virtual Keyboard application) wheres KDE applications with none of those keyboards, not even the virtual keyboard. The keyboard is also listed in the xinput output after replugging it (run from an xterm as konsole isn't taking any keyboard input anymore). The USB mouse is just working fine. So it definitely doesn't look like a hardware, driver or X problem, but like something caused by the common code used by kde applications for doing input. The Bug is probably also already present in older code as I never used an USB keyboard or the dock before I didn't encounter those problems. I even tried the workaround from the almost similar sounding bug description of BUG 988792 by running 'killall plasmashell ; kstart plasmashell' but this doesn't work for me. Neither does deactivating /etc/X11/xorg.conf.d/40-libinput.conf and using evdev driver instead of libinput as BUG 1044820 suggests as a solution/better workaround. Frankly I'm not sure which log files, config files, config settings, command output paste or other information I could provide to make tracing this bug behaviour to specific code lines easier, but If you point me in a direction, I'll provide that information gladly. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1136772] New: Kernel bug triggered when mounting btrfs file system
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1136772 Bug ID: 1136772 Summary: Kernel bug triggered when mounting btrfs file system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: gottfried.necker(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 806382 --> http://bugzilla.opensuse.org/attachment.cgi?id=806382&action=edit dmesg output The btrfs file system on the system disk suddenly got damaged. The reason is unknown. Subsequent attempts to reboot and mount led to messages in the system log: kernel BUG at fs/btrfs/ctree.h:3524! Using a recent rescue disk didn't really help. I attached the output of dmesg. I was trying to mount the disk using the tumbleweed rescue disk. 'btrfs scrub' was not helpful. I can mount the file system on the disk, but I can't do anything useful with it. All operations seem to block. Any ideas what I could do with this file system are welcome -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1136295] yast2-control-center-qt3 No icons in yast2 or sw_single
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136295 http://bugzilla.suse.com/show_bug.cgi?id=1136295#c6 --- Comment #6 from Stasiek Michalski <hellcp(a)mailbox.org> --- Eh, in case of qt5 control center, it doesn't use a set directory, instead relying on DE setting icon theme and using a native qt function (that exist since qt4) to set icon from icon theme. I have no idea how this should be solved for ycc-qt3, but there is probably a reason why it and qt3 are no longer supported ;) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136295] yast2-control-center-qt3 No icons in yast2 or sw_single
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136295 http://bugzilla.suse.com/show_bug.cgi?id=1136295#c5 --- Comment #5 from David Rankin <drankinatty(a)suddenlinkmail.com> --- I believe I have found the bottom line and there are two-options. (1) restore the png icons from yast2-opensuse-branding available in 15.0 as part of yast-theme; or (2) write a .svg handler and renderer to Qimage in Qt3 so you can use QimageConvertTo to create a Qpixmap from the rendered Qimage. Why? QImageIO contains a QIODevice object that is used for image data I/O. The programmer can install new image file formats in addition to those that Qt provides. Qt currently supports the following image file formats: PNG, BMP, XBM, XPM and PNM. It may also support JPEG, MNG and GIF, if specially configured during compilation. The different PNM formats are: PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or P6). There is no native support for .svg images or icons in Qt3. I don't know how difficult option (1) is, but there are a number of svg handling Qt3 apps the .svg image read and render -- like scribus where the .svg code could be pulled. Or (2) simply include the yast .png icons along with the .svg images in the current yast2-theme package. (they are only a few 100k of size total, so the impact would be negligible and restore icons for yast2-control-center-qt3 without having to patch anything or add svg rendering code. You guys make the call. I already have yast2-control-center-qt3 building, so I'm happy to help and verify whatever way you want to go. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs June 2019