March 2016 - openSUSE Bugs - openSUSE Mailing Lists

[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 966057] New: RPM pacakges won't regenerate initrd on removal
by bugzilla_noreply＠novell.com 29 May '20

29 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=966057 Bug ID: 966057 Summary: RPM pacakges won't regenerate initrd on removal Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently there are two macros in /etc/rpm/macros.initrd: %regenerate_initrd_post, to be called in the %post and %postun sections and %regenerate_initrd_posttrans, to be called in %posttrans. %regenerate_initrd_post simply sets a flag that the initrd has to be rebuilt after the transaction. The posttrans macros takes care of that. Now, that works fine for installation (%post -> %posttrans) and upgrades (%postun -> %post -> %posttrans), but on removal, %posttrans is never run. How could that be implemented properly? -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 954505] New: yast ruby msg extractor (xgettext) does not support format marker
by bugzilla_noreply＠novell.com 06 May '20

06 May '20

http://bugzilla.suse.com/show_bug.cgi?id=954505 Bug ID: 954505 Summary: yast ruby msg extractor (xgettext) does not support format marker Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: ke(a)suse.com QA Contact: jsrain(a)suse.com CC: 5yrnyk(a)myway.com, ancor(a)suse.com, dimstar(a)opensuse.org, ke(a)suse.com Depends on: 954357 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #954357 +++ When installing Leap 42.1 (or 13.2) with Ukrainian localization the page of user account setup is skipped with error: Details: malformed format string - %*[0-9] Caller: /usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.9.2/lib/fast_gettext/vendor/string.rb:70:in `%' Other tried localizations show user account page correctly. y2logs is attached ============================================================================= Karl Eichwalder 2015-11-10 17:36:40 CET (In reply to Ancor Gonzalez Sosa from comment #5) > Silly me! I was looking at Estonian .po file (et) and checking the effect in > Greek language (el). But turns out el!=et. :-) > > In Estonian it's not broken just because the translation is marked as fuzzy > (so not included in the .mo file)... a missing translation that is not that > obvious when you are staring at a Greek screen and you see no English text. > :-D > > So, in the end, it's a bug in the uk/users.po, as expected from the very > beginning. So reassigning to translations. Ok, thanks for debugging. It would work better, if the ruby xgettext extractor would add formatting markers as it does for other languages such as c or even ycp: #, c-format #, ycp-format I'm not sure whether that's a general issue or whether our yast xgettext extractor just does not know about this. Without such markers we are not (easily) able to validate the translations -- we usually do this with msgfmt. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 894783] New: CA management: Sign Request: Don't use sequential serial numbers
by bugzilla_noreply＠novell.com 26 Apr '20

26 Apr '20

https://bugzilla.novell.com/show_bug.cgi?id=894783 https://bugzilla.novell.com/show_bug.cgi?id=894783#c0 Summary: CA management: Sign Request: Don't use sequential serial numbers Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 (In openssl tradition certificates use sequential serial numbers) YaST's certificate signing function uses sequential serial numbers to issue (sign) certificates (like 01, 02, 03, ... 09, 0A, 0B, ...) Due to some weaknesses in SHA-1, there's a recommendation to use serial numbers with a higher entropy. See https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/ElekSignatur/BSI_SHA1_Z… (German): ---BEGIN quote--- Kollisionsangriffe gegen die Zertifikaterstellung mit SHA-1 können von vornherein verhindert werden, wenn folgendes gilt: 1) Es wird das X.509v3 Format gemäß ISIS-MTT verwendet. 2) Die Seriennummer ("serialNumber") des Zertifikats hat eine genügend hohe Entropie h für den Angreifer. D.h. die Unsicherheit des Angreifers über die Seriennummer eines zu erstellenden Zertifikats ist mindestens h Bits. (...) ---END quote--- Reproducible: Always Steps to Reproduce: 1. Sign a certificate request (CSR) in YaST's CA management Actual Results: The certificate gets a serial number that can easily be guessed Expected Results: The serial number should not be easy to guess See also http://www.heise.de/security/meldung/Fragwuerdige-Hash-Funktion-SHA-1-immer… (German) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 963323] New: Making Maven officially available in openSUSE
by bugzilla_noreply＠novell.com 16 Apr '20

16 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=963323 Bug ID: 963323 Summary: Making Maven officially available in openSUSE Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: p.drouand(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a kind of metabug to track progress made by people actually involved in Maven packaging. We will update this bug progressively according to progresses done themselves. -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 911286] New: mc/midnight commander lost shell/fish support
by bugzilla_noreply＠novell.com 10 Apr '20

10 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=911286 Bug ID: 911286 Summary: mc/midnight commander lost shell/fish support Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: richlv(a)nakts.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- this is a recent regression. midnight commander/mc after a recent upgrade has lost fish/"shell link" support. upstream report suggests that it should be built with fish support : https://www.midnight-commander.org/ticket/3294 sftp support in mc does not use ssh keys, thus it is not a proper replacement for fish/shell link support. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 959025] New: mate-tweak completely broken
by bugzilla_noreply＠novell.com 05 Apr '20

05 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=959025 Bug ID: 959025 Summary: mate-tweak completely broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "/usr/lib/python2.7/site-packages/gi/overrides/Gtk.py:50: RuntimeWarning: You have imported the Gtk 2.0 module. Because Gtk 2.0 was not designed for use with introspection some of the interfaces and API will fail. As such this is not supported by the pygobject development team and we encourage you to port your app to Gtk 3 or greater. PyGTK is the recomended python module to use with Gtk 2.0" Possibly related reports: https://forum.antergos.com/topic/1898/mintmenu-is-broken-again/6 https://github.com/linuxmint/mintmenu/issues/130 https://bugs.launchpad.net/linuxmint/+bug/1261862 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 597673] New: fetchmail: DoS in -v -v mode in multibyte
by bugzilla_noreply＠novell.com 02 Apr '20

02 Apr '20

http://bugzilla.novell.com/show_bug.cgi?id=597673 http://bugzilla.novell.com/show_bug.cgi?id=597673#c0 Summary: fetchmail: DoS in -v -v mode in multibyte Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: puzel(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de CC: security-team(a)suse.de Found By: Other Blocker: --- Your friendly security team received the following report via oss-security. Please respond ASAP. The issue is public. Factory only sufficient ------------------------------------------------------------------------------ Date: Sun, 18 Apr 2010 18:58:30 +0200 From: "Matthias Andree" <matthias.andree(a)gmx.de> Subject: [oss-security] CVE request: fetchmail 4.6.3...6.3.16 DoS in -v -v mode in multibyte locales on invalid input Please assign a CVE id for the issue described below. (Best viewed in non-proportional font with 8 space tabs): Draft announcement: - DRAFT - XXX - DRAFT - fetchmail-SA-2010-02: Denial of service in debug mode w/ multichar locales Topics: Denial of service in debug output. Author: Matthias Andree Version: 0.1 XXX Announced: XXX Type: malloc() Buffer overrun with printable characters Impact: Denial of service. Danger: low CVE Name: CVE-2010-XXXX CVSSv2: XXX URL: http://www.fetchmail.info/fetchmail-SA-2010-02.txt Project URL: http://www.fetchmail.info/ Affects: fetchmail releases 4.6.3 up to and including 6.3.16 Not affected: fetchmail release 6.3.17 and newer Corrected: 2010-04-18 Git (XXX) 0. Release history ================== 2010-04-18 0.1 first draft (visible in SVN and through oss-security) XXX 1. Background ============= fetchmail is a software package to retrieve mail from remote POP2, POP3, IMAP, ETRN or ODMR servers and forward it to local SMTP, LMTP servers or message delivery agents. It supports SSL and TLS security layers through the OpenSSL library, if enabled at compile time and if also enabled at run time. 2. Problem description and Impact ================================= In debug mode (-v -v), fetchmail prints information that was obtained from the upstream server (POP3 UIDL lists) or from message headers retrieved from it. If printing such information fails, for instance because there are invalid multibyte character sequences in this information (message headers), fetchmail will misinterpret this condition, and believe that the buffer was too small, and reallocate a bigger one (with linearly increasing buffer size), and repeat, until the allocation fails. At that point, fetchmail will abort. Note that the "Affects:" line above may be inaccurate, and it may be that versions before 5.6.6 are actually unaffected. The author was unable to compile such old fetchmail versions to verify the existence of the bug. Given that other security issues are present in such versions, those should not be used, and the wider version range was listed as vulnerable to err towards the safe. 3. Solution =========== There are two alternatives, either of them by itself is sufficient: a. Apply the patch found in section B of this announcement to fetchmail 6.3.14 or newer, recompile and reinstall it. b. Install fetchmail 6.3.17 or newer after it will have become available. The fetchmail source code is always available from <http://developer.berlios.de/project/showfiles.php?group_id=1824>. 4. Workaround ============= Run fetchmail with at most one -v (--verbose) option. A. Copyright, License and Warranty ================================== (C) Copyright 2010 by Matthias Andree, <matthias.andree(a)gmx.de>. Some rights reserved. This work is licensed under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Germany License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-nd/3.0/de/ or send a letter to Creative Commons 171 Second Street Suite 300 SAN FRANCISCO, CALIFORNIA 94105 USA THIS WORK IS PROVIDED FREE OF CHARGE AND WITHOUT ANY WARRANTIES. Use the information herein at your own risk. B. Patch to remedy the problem ============================== Note that when taking this from a GnuPG clearsigned file, the lines starting with a "-" character are prefixed by another "- " (dash + blank) combination. Either feed this file through GnuPG to strip them, or strip them manually. You may want to use the "-p1" flag to patch. Whitespace differences can usually be ignored by invoking "patch -l", so try this if the patch does not apply. diff --git a/rfc822.c b/rfc822.c index 6f2dbf3..dbcda32 100644 --- a/rfc822.c +++ b/rfc822.c @@ -25,6 +25,7 @@ MIT license. Compile with -DMAIN to build the demonstrator. #include <stdlib.h> #include "fetchmail.h" +#include "sdump.h" #ifndef MAIN #include "i18n.h" @@ -74,9 +75,10 @@ char *reply_hack( } #ifndef MAIN - if (outlevel >= O_DEBUG) - report_build(stdout, GT_("About to rewrite %.*s...\n"), - (int)BEFORE_EOL(buf), buf); + if (outlevel >= O_DEBUG) { + report_build(stdout, GT_("About to rewrite %s...\n"), (cp = sdump(buf, BEFORE_EOL(buf)))); + xfree(cp); + } /* make room to hack the address; buf must be malloced */ for (cp = buf; *cp; cp++) @@ -211,9 +213,12 @@ char *reply_hack( } #ifndef MAIN - if (outlevel >= O_DEBUG) - report_complete(stdout, GT_("...rewritten version is %.*s.\n"), - (int)BEFORE_EOL(buf), buf); + if (outlevel >= O_DEBUG) { + report_complete(stdout, GT_("...rewritten version is %s.\n"), + (cp = sdump(buf, BEFORE_EOL(buf)))); + xfree(cp) + } + #endif /* MAIN */ *length = strlen(buf); return(buf); diff --git a/uid.c b/uid.c index fdc6f5d..d813bee 100644 --- a/uid.c +++ b/uid.c @@ -20,6 +20,7 @@ #include "fetchmail.h" #include "i18n.h" +#include "sdump.h" /* * Machinery for handling UID lists live here. This is mainly to support @@ -260,8 +261,11 @@ void initialize_saved_lists(struct query *hostlist, const char *idfile) if (uidlcount) { report_build(stdout, GT_("Scratch list of UIDs:")); - for (idp = scratchlist; idp; idp = idp->next) - report_build(stdout, " %s", idp->id); + for (idp = scratchlist; idp; idp = idp->next) { + char *t = sdump(idp->id, strlen(idp->id)); + report_build(stdout, " %s", t); + free(t); + } if (!idp) report_build(stdout, GT_(" <empty>")); report_complete(stdout, "\n"); @@ -517,8 +521,11 @@ void uid_swap_lists(struct query *ctl) report_build(stdout, GT_("Merged UID list from %s:"), ctl->server.pollname); else report_build(stdout, GT_("New UID list from %s:"), ctl->server.pollname); - for (idp = dofastuidl ? ctl->oldsaved : ctl->newsaved; idp; idp = idp->next) - report_build(stdout, " %s = %d", idp->id, idp->val.status.mark); + for (idp = dofastuidl ? ctl->oldsaved : ctl->newsaved; idp; idp = idp->next) { + char *t = sdump(idp->id, strlen(idp->id)); + report_build(stdout, " %s = %d", t, idp->val.status.mark); + free(t); + } if (!idp) report_build(stdout, GT_(" <empty>")); report_complete(stdout, "\n"); @@ -567,8 +574,11 @@ void uid_discard_new_list(struct query *ctl) /* this is now a merged list! the mails which were seen in this * poll are marked here. */ report_build(stdout, GT_("Merged UID list from %s:"), ctl->server.pollname); - for (idp = ctl->oldsaved; idp; idp = idp->next) - report_build(stdout, " %s = %d", idp->id, idp->val.status.mark); + for (idp = ctl->oldsaved; idp; idp = idp->next) { + char *t = sdump(idp->id, strlen(idp->id)); + report_build(stdout, " %s = %d", t, idp->val.status.mark); + free(t); + } if (!idp) report_build(stdout, GT_(" <empty>")); report_complete(stdout, "\n"); -- Matthias Andree -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 921570] New: after dist upgrade system boots to emergency mode
by bugzilla_noreply＠novell.com 01 Apr '20

01 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=921570 Bug ID: 921570 Summary: after dist upgrade system boots to emergency mode Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: steffen.hau(a)rz.uni-mannheim.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've started upgrading systems from openSUSE 13.1 to 13.2. Virtual machines without special stuff like mdadm raid devices oder multipathed FC LUN's went fine. But systems (IBM HS22 Blades) with mdadm raid devices are booting to emergency mode. The systems have three raid 1 devices (swap, / and /srv or /home), swap and / are correctly assembled but the third md device is missing and it also does not appear in /proc/mdstat. Manually running "mdadm -A --scan" brings it up and "systemctl default" continues booting. To dig deeper into this issue, I've installed openSUSE 13.2 from scratch on a spare blade and here md2 is correctly assembled. This is the content of /etc/systemd/system/ of the upgraded system: /etc/systemd/system/dbus-org.opensuse.Network.AUTO4.service /etc/systemd/system/dbus-org.opensuse.Network.DHCP4.service /etc/systemd/system/dbus-org.opensuse.Network.DHCP6.service /etc/systemd/system/dbus-org.opensuse.Network.Nanny.service /etc/systemd/system/default.target /etc/systemd/system/default.target.wants/sysstat.service /etc/systemd/system/default.target.wants/systemd-readahead-collect.service /etc/systemd/system/default.target.wants/systemd-readahead-replay.service /etc/systemd/system/getty.target.wants/getty(a)tty1.service /etc/systemd/system/multi-user.target.wants/acpid.service /etc/systemd/system/multi-user.target.wants/apache2.service /etc/systemd/system/multi-user.target.wants/auditd.service /etc/systemd/system/multi-user.target.wants/cron.service /etc/systemd/system/multi-user.target.wants/dsmc.service /etc/systemd/system/multi-user.target.wants/irqbalance.service /etc/systemd/system/multi-user.target.wants/mcelog.service /etc/systemd/system/multi-user.target.wants/ntpd.service /etc/systemd/system/multi-user.target.wants/postfix.service /etc/systemd/system/multi-user.target.wants/remote-fs.target /etc/systemd/system/multi-user.target.wants/smartd.service /etc/systemd/system/multi-user.target.wants/sshd.service /etc/systemd/system/multi-user.target.wants/syslog-ng.service /etc/systemd/system/multi-user.target.wants/wicked.service /etc/systemd/system/network-online.target.wants/wicked.service /etc/systemd/system/network.service /etc/systemd/system/sysinit.target.wants/multipathd.service /etc/systemd/system/syslog.service /etc/systemd/system/system-update.target.wants/systemd-readahead-drop.service /etc/systemd/system/timers.target.wants/logrotate.timer /etc/systemd/system/wickedd.service.wants/wickedd-auto4.service /etc/systemd/system/wickedd.service.wants/wickedd-dhcp4.service /etc/systemd/system/wickedd.service.wants/wickedd-dhcp6.service /etc/systemd/system/wickedd.service.wants/wickedd-nanny.service /etc/systemd/system/wicked.service.wants/wickedd.service I've made the scratch system identical to the problematic system (identical installed packages, conf files in /etc, active systemd services, and so on) and it still assembles md2. I've no more ideas where to search for possible causes. Please let me know what kind of information I should provide in order to help you to find the cause. -- You are receiving this mail because: You are on the CC list for the bug.

1 15