May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1136788] New: Sqlite oserror test fails on ppc64le
by bugzilla_noreply＠novell.com 06 Apr '20

06 Apr '20

http://bugzilla.suse.com/show_bug.cgi?id=1136788 Bug ID: 1136788 Summary: Sqlite oserror test fails on ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: max(a)suse.com Reporter: jbrielmaier(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The oserror.test (https://repo.or.cz/sqlite.git/blob_plain/HEAD:/test/oserror.test) fails sometimes on ppc64le with the following error log: ! oserror-2.1.1 expected: [1 {disk I/O error}] ! oserror-2.1.1 got: [0 {}] ! oserror-2.1.2 expected: [^os_unix.c:\d+: \(\d+\) unlink\(.*test.db-wal\) - ] ! oserror-2.1.2 got: [] Time: oserror.test 194 ms The strange point here is, that it doesn't seem to fail always. So the build in server:database for openSUSE_Factory_PowerPC succeeds without this error. But when I built sqlite from server:database on a local ppc64le machine, it fails with exactly this test. I checked it on another Power machine and there the test also fails (one is POWER8, the other POWER9). In openSUSE:Factory:PowerPC/sqlite3 it fails in a different test (swarmvtab2.test). So I assume these failures are not connected. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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 1089701] New: With kernel 4.16 webcam video is not working with Skype and Google Hangouts
by bugzilla_noreply＠novell.com 03 Apr '20

03 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1089701 Bug ID: 1089701 Summary: With kernel 4.16 webcam video is not working with Skype and Google Hangouts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: tneo(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I boot TW with kernel 4.16 the webcam video in both Skype and Google Hangouts don't have video support. Microphone works. The webcam is not broken as with eg. Ekiga I do have video. Booting kernel 4.15 gives the video output again, though other not relevant issues arise. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[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 1136281] New: Cannot create user directory because /home is not a btrfs sub volume
by bugzilla_noreply＠novell.com 01 Apr '20

01 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1136281 Bug ID: 1136281 Summary: Cannot create user directory because /home is not a btrfs sub volume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: j.r.hudson(a)virginmedia.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When adding a new user, YaST says it cannot create a user directory because /home is not a btrfs sub volume. I still have /home on an XFS partition having done online upgrades from earlier versions. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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

[Bug 911512] New: opensuse boots to terminal
by bugzilla_noreply＠novell.com 01 Apr '20

01 Apr '20

http://bugzilla.opensuse.org/show_bug.cgi?id=911512 Bug ID: 911512 Summary: opensuse boots to terminal Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: illumilore(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 Build Identifier: after an update, opensuse now boots to a terminal. trying to use the command startx gives the output that it cannot open /dev/tty0 no such file or directory. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1136099] New: python-nbconvert fails test on 1-core VM
by bugzilla_noreply＠novell.com 30 Mar '20

30 Mar '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1136099 Bug ID: 1136099 Summary: python-nbconvert fails test on 1-core VM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: toddrme2178(a)gmail.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that osc build --vm-type=kvm -j1 --noservice for python-nbconvert fails 1 test on a 1-core VM 1 failed, 251 passed, 32 skipped, 2 deselected, 59 warnings in 241.06 =================================== FAILURES ========================== ________________________ TestExecute.test_disable_stdin ______________ self = <nbconvert.preprocessors.tests.test_execute.TestExecute testMethod=test_ disable_stdin> def test_disable_stdin(self): """Test disabling standard input""" filename = os.path.join(current_dir, 'files', 'Disable Stdin.ipynb') res = self.build_resources() res['metadata']['path'] = os.path.dirname(filename) > input_nb, output_nb = self.run_notebook(filename, dict(allow_errors=True), res) If you cannot debug this yourself, please work with upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 690867] New: Consider to DNSSEC sign the opensuse.org domain
by bugzilla_noreply＠novell.com 28 Mar '20

28 Mar '20

https://bugzilla.novell.com/show_bug.cgi?id=690867 https://bugzilla.novell.com/show_bug.cgi?id=690867#c0 Summary: Consider to DNSSEC sign the opensuse.org domain Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Infrastructure AssignedTo: mrueckert(a)novell.com ReportedBy: burnus(a)gmx.de QAContact: lrupp(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.0) Gecko/20100101 Firefox/4.0 Currently, the opensuse.org domain is not secured using DNSSEC: http://dnsviz.net/d/opensuse.org/dnssec/ It would be useful, if it could be signed. Other domains are already signed such as: - Fedora: http://dnsviz.net/d/fedoraproject.org/dnssec/ - Mozilla: http://dnsviz.net/d/wiki.mozilla.org/dnssec/ (Side remark: In Firefox, the plugin http://www.dnssec-validator.cz/ can be used to see the DNSSEC status.) Reproducible: Always -- 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 11

[Bug 1093163] New: mdadm: using service templates in preun is wrong:
by bugzilla_noreply＠novell.com 27 Mar '20

27 Mar '20

http://bugzilla.suse.com/show_bug.cgi?id=1093163 Bug ID: 1093163 Summary: mdadm: using service templates in preun is wrong: 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: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in mdadm.spec: %preun %service_del_preun %services mdmon@.service mdadm-last-resort@.service mdadm-grow-continue@.service leads to: # rpm -e mdadm --nodeps Failed to stop mdmon@.service: Unit name mdmon@.service is missing the instance name. See system logs and 'systemctl status mdmon@.service' for details. Failed to stop mdadm-last-resort@.service: Unit name mdadm-last-resort@.service is missing the instance name. See system logs and 'systemctl status mdadm-last-resort@.service' for details. Failed to stop mdadm-grow-continue@.service: Unit name mdadm-grow-continue@.service is missing the instance name. See system logs and 'systemctl status mdadm-grow-continue@.service' for details. Failed to get load state of mdmon@.service: Unit name mdmon@.service is neither a valid invocation ID nor unit name. Failed to get load state of mdadm-last-resort@.service: Unit name mdadm-last-resort@.service is neither a valid invocation ID nor unit name. Failed to get load state of mdadm-grow-continue@.service: Unit name mdadm-grow-continue@.service is neither a valid invocation ID nor unit name. a service template file (foo@.service) can not be used with the %service_add/del macros. -- You are receiving this mail because: You are on the CC list for the bug.

1 3