March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 965242] New: kdesktop, kded and kicker crash every session start
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=965242 Bug ID: 965242 Summary: kdesktop, kded and kicker crash every session start Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 Assignee: anixx(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Initial KDE3 mailing list thread: http://lists.opensuse.org/opensuse-kde3/2015-12/msg00000.html This has been happening in TW for many months, surviving many zypper ups and occasional zypper dups. I don't think any of my twelve KDE3 on TW installations (of which most are i586) fail to exhibit these crashes, triggered by simply opening a KDE3 session. OTOH, I can't remember any of my 13.1, 13.2 or 42.1 KDE3 installations doing same. FWIW, I've tried to get all installed KDE3 packages to be provided by the KDE3:KDE3 repo, but not all exist there (last I checked, at least these do not: kdegraphics3*). -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 783862] "runlevel" switching broken WRT KDM3 (and "KDM" in Trinity)
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=783862 http://bugzilla.opensuse.org/show_bug.cgi?id=783862#c10 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |dimstar(a)opensuse.org Resolution|--- |WONTFIX --- Comment #10 from Dominique Leuenberger <dimstar(a)opensuse.org> --- KDE3 has been removed from openSUSE Tumbleweed during the last year. As such, this bug is no longer relevant to Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084283] New: [glibc-devel] Missing C headers?
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1084283 Bug ID: 1084283 Summary: [glibc-devel] Missing C headers? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: clanig(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 762954 --> http://bugzilla.suse.com/attachment.cgi?id=762954&action=edit Comparison of glibc-devel versions It looks like there were some C header files missing in this version of the package. The Leap version has the needed files in the rpc/ directory (see screenshot). -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1084213] [storage-ng][*15 & TW affected] /home subvolume not created if user opts to not have a /home partition
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1084213 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[storage-ng][*15 affected] |[storage-ng][*15 & TW |/home subvolume not created |affected] /home subvolume |if user opts to not have a |not created if user opts to |/home partition |not have a /home partition -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084213] [storage-ng][*15 affected] /home subvolume not created if user opts to not have a /home partition
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1084213 http://bugzilla.suse.com/show_bug.cgi?id=1084213#c4 --- Comment #4 from Lukas Ocilka <locilka(a)suse.com> --- *** Bug 1084261 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1083213] Please drop unnecessary xorg-x11-fonts requires
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1083213 Stephan Kulow <coolo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |tchvatal(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1063638] btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1063638 Stefan Behlert <behlert(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1037557] New: xterm ignores 'background' color settings
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1037557 Bug ID: 1037557 Summary: xterm ignores 'background' color settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: posix.ru(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- By default xterm's background color is white. By using "XTerm*background: black" in the ~/XTerm file, it should change background color to black. It doesn't happen anymore. Other configuration like font size (XTerm*font: 9x15) or number of save lines (XTerm*saveLines: 2000) works fine for me. > rpm -qa xterm xterm-bin xterm-327-1.1.x86_64 xterm-bin-327-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1084015] Include fixes from en_US "translation" to sources
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1084015 http://bugzilla.suse.com/show_bug.cgi?id=1084015#c3 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED URL| |https://trello.com/c/zW2FSk | |N6 Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de --- Comment #3 from Steffen Winterfeldt <snwint(a)suse.com> --- Tracking in YaST scrum board. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084292] New: [drupal8] Multiple Vulnerabilities - SA-CORE-2018-001
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1084292 Bug ID: 1084292 Summary: [drupal8] Multiple Vulnerabilities - SA-CORE-2018-001 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: kbabioch(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ecsos(a)schirra.net, kbabioch(a)suse.com Found By: --- Blocker: --- This security advisory fixes multiple vulnerabilities in both Drupal 7 and Drupal 8. See below for a list. Comment reply form allows access to restricted content - Critical - Drupal 8 - CVE-2017-6926 Users with permission to post comments are able to view content and comments they do not have access to, and are also able to add comments to this content. This vulnerability is mitigated by the fact that the comment system must be enabled and the attacker must have permission to post comments. JavaScript cross-site scripting prevention is incomplete - Critical - Drupal 7 and Drupal 8 - CVE-2017-6927 Drupal has a Drupal.checkPlain() JavaScript function which is used to escape potentially dangerous text before outputting it to HTML (as JavaScript output is not auto-escaped by either Drupal 7 or Drupal 8). This function does not correctly handle all methods of injecting malicious HTML, leading to a cross-site scripting vulnerability under certain circumstances. The PHP functions which Drupal provides for HTML escaping are not affected. Private file access bypass - Moderately Critical - Drupal 7 - CVE-2017-6928 When using Drupal's private file system, Drupal will check to make sure a user has access to a file before allowing the user to view or download it. This check fails under certain conditions in which one module is trying to grant access to the file and another is trying to deny it, leading to an access bypass vulnerability. This vulnerability is mitigated by the fact that it only occurs for unusual site configurations. jQuery vulnerability with untrusted domains - Moderately Critical - Drupal 7 - CVE-2017-6929 A jQuery cross site scripting vulnerability is present when making Ajax requests to untrusted domains. This vulnerability is mitigated by the fact that it requires contributed or custom modules in order to exploit. For Drupal 8, this vulnerability was already fixed in Drupal 8.4.0 in the Drupal core upgrade to jQuery 3. For Drupal 7, it is fixed in the current release (Drupal 7.57) for jQuery 1.4.4 (the version that ships with Drupal 7 core) as well as for other newer versions of jQuery that might be used on the site, for example using the jQuery Update module. Language fallback can be incorrect on multilingual sites with node access restrictions - Moderately Critical - Drupal 8 - CVE-2017-6930 When using node access controls with a multilingual site, Drupal marks the untranslated version of a node as the default fallback for access queries. This fallback is used for languages that do not yet have a translated version of the created node. This can result in an access bypass vulnerability. This issue is mitigated by the fact that it only applies to sites that a) use the Content Translation module; and b) use a node access module such as Domain Access which implement hook_node_access_records(). Note that the update will mark the node access tables as needing a rebuild, which will take a long time on sites with a large number of nodes. Settings Tray access bypass - Moderately Critical - Drupal 8 - CVE-2017-6931 The Settings Tray module has a vulnerability that allows users to update certain data that they do not have the permissions for. If you have implemented a Settings Tray form in contrib or a custom module, the correct access checks should be added. This release fixes the only two implementations in core, but does not harden against other such bypasses. This vulnerability can be mitigated by disabling the Settings Tray module. External link injection on 404 pages when linking to the current page - Less Critical - Drupal 7 - CVE-2017-6932 Drupal core has an external link injection vulnerability when the language switcher block is used. A similar vulnerability exists in various custom and contributed modules. This vulnerability could allow an attacker to trick users into unwillingly navigating to an external site. Solution: Install the latest version: If you are using Drupal 8 , upgrade to Drupal 8.4.5 If you are using Drupal 7 , upgrade to Drupal 7.57 References: https://www.drupal.org/sa-core-2018-001 -- You are receiving this mail because: You are on the CC list for the bug.

1 1