openSUSE Bugs December 2019

bugs@lists.opensuse.org

1 participants
3698 discussions

[Bug 1109376] [nouveau] Nvidia chip stops turning off on resume from suspend after AC state change
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1109376 http://bugzilla.suse.com/show_bug.cgi?id=1109376#c3 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com --- Comment #3 from Miroslav Beneš <mbenes(a)suse.com> --- Iakov, does the issue still persists? I think we should close with RESOLVED UPSTREAM if I am not missing something. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1105974] Noveau driver dumps many of these and the laptop freezes for 10 seconds
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1105974 http://bugzilla.suse.com/show_bug.cgi?id=1105974#c7 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com --- Comment #7 from Miroslav Beneš <mbenes(a)suse.com> --- Andres, is the issue still present with newer distribution/kernel? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1099315] New: module: nvidia: Unknown rela relocation: 4
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1099315 Bug ID: 1099315 Summary: module: nvidia: Unknown rela relocation: 4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: schwab(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The kernel needs to handle R_X86_64_PLT32, as it seems. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1158096] [Build 20191128] openQA test fails in yast2_firstboot "yast/wfm.rb:253 Client /usr/share/YaST2/clients/firstboot_setup_dhcp.rb failed with 'undefined method `interfaces' for nil:NilClass' (NoMethodError)."
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1158096 http://bugzilla.suse.com/show_bug.cgi?id=1158096#c2 Knut Alejandro Anderssen González <knut.anderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |knut.anderssen(a)suse.com Resolution|--- |DUPLICATE --- Comment #2 from Knut Alejandro Anderssen González <knut.anderssen(a)suse.com> --- Looks like a duplicate of https://bugzilla.opensuse.org/show_bug.cgi?id=1157429 which has been already solved by https://github.com/yast/yast-network/pull/1005 It was fixed in yast2-network-4.2.30, but current test still uses yast2-network-4.2.28 *** This bug has been marked as a duplicate of bug 1157429 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1157429] [Build 20191120] openQA test fails in installation
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1157429 http://bugzilla.suse.com/show_bug.cgi?id=1157429#c3 Knut Alejandro Anderssen González <knut.anderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz(a)suse.com --- Comment #3 from Knut Alejandro Anderssen González <knut.anderssen(a)suse.com> --- *** Bug 1158096 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 1157462] libdbus-1 uses abort() which is an absolute nogo for a system library
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1157462 http://bugzilla.suse.com/show_bug.cgi?id=1157462#c13 --- Comment #13 from Dr. Werner Fink <werner(a)suse.com> --- Beside this fedorea seems to switch to dbus-broker which seems IMHO a better written part of code in comparision to dbus-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1157462] libdbus-1 uses abort() which is an absolute nogo for a system library
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1157462 http://bugzilla.suse.com/show_bug.cgi?id=1157462#c12 --- Comment #12 from Dr. Werner Fink <werner(a)suse.com> --- Then you might do the update to 1.12.16 to get the security issue CVE-2019-12749 fixed for Tumbleweed/Factory as well accordingly to the policy Factory First. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1157462] libdbus-1 uses abort() which is an absolute nogo for a system library
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1157462 http://bugzilla.suse.com/show_bug.cgi?id=1157462#c11 --- Comment #11 from Simon Lees <simonf.lees(a)suse.com> --- (In reply to Dr. Werner Fink from comment #10) > (In reply to Simon Lees from comment #9) > > (In reply to Dr. Werner Fink from comment #8) > > > SR#752324 -- could one have a review? Other than me! > > > > Sorry due to timezones I was done for Friday when you sent this, doing the > > update was on my today list if I hadn't heard a good reason to keep > > --enable-asserts. > > > > I this using --disable-asserts would be better then adding another patch, > > its also now how debian handle it. > > https://salsa.debian.org/utopia-team/dbus/blob/debian/master/debian/rules > > The udeb_configure_flags rule with --disable-asserts is used for the udeb > packages and those type of packages are only for internal build system for > debian packages. > > The patch is also from debian (not utopia!) Utopia is the team maintaining dbus within debian according to there documentation, It can also be confirmed by the fact that almost all the commits there are from debians dbus maintainer @smcv > > --- a/dbus/dbus-internals.c > +++ b/dbus/dbus-internals.c > @@ -185,7 +185,7 @@ const char *_dbus_no_memory_message = "Not enough > memory"; > > static dbus_bool_t warn_initted = FALSE; > static dbus_bool_t fatal_warnings = FALSE; > -static dbus_bool_t fatal_warnings_on_check_failed = TRUE; > +static dbus_bool_t fatal_warnings_on_check_failed = FALSE; > > static void > init_warnings(void) > > could you please explain what is wrong with this approach? If you like to > debug you are able to set the environment variable DBUS_FATAL_WARNINGS to 1. > Currently we do not set DBUS_FATAL_WARNINGS at all, that is with the current > default all customers and users out there do debugging their systems and do > not know about nor can handle this. This causes a lot of trouble and > bugzilla entries. Debian dropped this patch at the start of last year (see below), Red Hat doesn't carry it (atleast centos) which makes me nervous being the only distro using and testing the patch, it means that no one is really looking at what is going on after the abort meaning there could end up being any form of data corruption or security issues hiding after in failure code paths that no one is testing. I wouldn't really be comfortable without going through and having a good look at whats happening after. Currently I don't have time for that. * d/p/debian/Don-t-abort-on-fatal-warnings-by-default.patch: Remove patch. This was committed not long after the addition of the fatal-by-default _dbus_warn_check_failed() checks for programming errors, with the changelog message "This will be set to upstream default again at some point so if you have an application that prints a DBus warning get it fixed". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158159] Leap 15.2 fallout from GNOME update
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1158159 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1158161 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158158] New: openSUSE:Leap:15.2:Staging:B/python3-doc failed
by bugzilla_noreply＠novell.com 02 Dec '19

02 Dec '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1158158 Bug ID: 1158158 Summary: openSUSE:Leap:15.2:Staging:B/python3-doc failed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://build.opensuse.org/package/live_build_log/open SUSE:Leap:15.2:Staging:B/python3-doc/standard/x86_64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE:Leap:15.2:Staging:B/python3-doc failed to build. Please see build log: https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.2:Stagin… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs December 2019