June 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1137147] New: [doc] 1.1.2.1 Booting the Installation System
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137147 Bug ID: 1137147 Summary: [doc] 1.1.2.1 Booting the Installation System Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: drsoaring(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- 1.1.2.1 Booting the Installation System https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.star… Hello - This is a bug description with a workaround that can be added to the OpenSUSE documentation on installation. The bug is: "installation fails (hangs or crashes) on Asus G20/GB20 ROG models and may also affect other recent x86_64 machines with dual Intel and nVidia graphics" The version tested is: openSUSE-Tumbleweed-DVD-x86_64-Snapshot20190425-Media.iso Notes: 1. PCI Advanced Error Reporting (AER) floods system logs making system and installer unresponsive, also makes copying log files in the last steps of installation (from USB updater) frequently fail. 2. Hard crash occurs typically at last steps of installation, which causes the hard drive to become corrupted. The cause is unknown to me, but acpi=off solves the problem. Work-around for Installation and Upgrade: For both "Installation" and "Upgrade" options on the USB stick or DVD boot, press 'e' and add these kernel parameters: acpi=off nomodeset I recommended that these parameters be defaulted for the installation and upgrade boot loaders from USB or DVD. Otherwise installation will fail with hard crash at the end (after a lot of time was already taken). Work-around for hard-drive boot: After the new system is booted, add these kernel parameters using YaST / system / boot loader / kernel paramters: acpi=pci pci=noaer This will make the work-around fix permanent. Tested on a 2017 ASUS GB20 x86_64 with both Intel and nVidia graphics. Thank you for checking this. Comment: I think OpenSUSE is a great Linux product. The installation process on newer machines with complex ACPI and dual graphics cards seems partly broken, since it fails out of the box, and a lot of time and reading is needed to get it to work. I saw at least one press article lamenting this problem and downgrading OpenSUSE. Therefore, to encourage new users, who perhaps cannot solve this problem at all, it would be great if this can be checked soon! perhaps with the suggested documentation note above added until this can be fixed in a more automatic way. Maybe documentation section 1.1.2.1 isn't the perfect place for such a note, but it should be near the top so new users will see it! Again, many thanks - on behalf on the new users installing OpenSUSE on these kinds of machines. Regards, David drsoaring(a)gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1136950] Kernel 5.2-rc2 relocation overflow errors breaking boot
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136950 http://bugzilla.suse.com/show_bug.cgi?id=1136950#c3 --- Comment #3 from Michal Kubeček <mkubecek(a)suse.com> --- Kernel:HEAD won't get 5.2-rc3 until tomorrow (I came to the office later so that I didn't update the branch before OBS submission deadline) but QA/aarch64 build of kernel-obs-qa in IBS project Devel:Kernel:master which used to fail with error like in the initial description now succeeds with 5.2-rc3 kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1131330] pthread_mutex_destroy occasionally returns EBUSY even though mutex is unlocked
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1131330 Andreas Schwab <schwab(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://sourceware.org/bugz | |illa/show_bug.cgi?id=23275 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1131330] New: pthread_mutex_destroy occasionally returns EBUSY even though mutex is unlocked
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1131330 Bug ID: 1131330 Summary: pthread_mutex_destroy occasionally returns EBUSY even though mutex is unlocked Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: asbeer(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 Build Identifier: I'm running the latest patched/updated OpenSUSE LEAP 15.0. My glibc version is 2.26-lp150.11.9.1. When I compile and run the following program on my system and let it run for a while (normally less than 30 seconds) it exits indicating that pthread_mutex_destroy() returned 16 (EBUSY). However, it's obvious from the code that pthread_mutex_unlock() was called right before pthread_mutex_destroy() and thus the mutex is not locked. So I believe the EBUSY value is being erroneously returned in this case. g++ -g -O2 -o test_ebusy_bug -lpthread test_ebusy_bug.cpp test_ebusy_bug.cpp: #include <vector> #include <thread> #include <pthread.h> #include <iostream> static const size_t tCnt = 10; struct test_struct { pthread_mutex_t mutex; pthread_cond_t cond1; pthread_cond_t cond2; bool run; std::vector<bool> runningList; test_struct() : run(false) , runningList(tCnt) { } void run_func(size_t index) { pthread_mutex_lock(&mutex); runningList[index] = true; pthread_cond_broadcast(&cond1); while (run) { pthread_cond_wait(&cond2, &mutex); } runningList[index] = false; pthread_mutex_unlock(&mutex); } bool spawn_join_threads() { std::vector<std::thread> tList; // Initialize the pthread variables pthread_mutex_init(&mutex, NULL); pthread_cond_init(&cond1, NULL); pthread_cond_init(&cond2, NULL); // Start all of the threads run = true; for (size_t i = 0; i < tCnt; i++) { runningList[i] = false; } for (size_t i = 0; i < tCnt; i++) { tList.push_back(std::thread(&test_struct::run_func, this, i)); } // Wait for all of the threads to start pthread_mutex_lock(&mutex); for (size_t i = 0; i < tCnt; i++) { while (!runningList[i]) { pthread_cond_wait(&cond1, &mutex); } } pthread_mutex_unlock(&mutex); // Stop all of the threads run = false; pthread_cond_broadcast(&cond2); for (int i = 0; i < tCnt; i++) { tList[i].join(); } tList.clear(); // Verify that all of the threads have stopped pthread_mutex_lock(&mutex); for (size_t i = 0; i < tCnt; i++) { if (runningList[i]) { std::cerr << "A thread hasn't stopped" << std::endl; pthread_mutex_unlock(&mutex); return false; } } pthread_mutex_unlock(&mutex); // Destroy the pthread variables int ret = pthread_cond_destroy(&cond2); if (ret) { std::cerr << "pthread_cond_destroy returned " << ret << std::endl; return false; } ret = pthread_cond_destroy(&cond1); if (ret) { std::cerr << "pthread_cond_destroy returned " << ret << std::endl; return false; } ret = pthread_mutex_destroy(&mutex); if (ret) { std::cerr << "pthread_mutex_destroy returned " << ret << std::endl; return false; } return true; } }; int main() { test_struct t; while (t.spawn_join_threads()); return 0; } Reproducible: Always Steps to Reproduce: Compile and run the above program. Actual Results: The program runs for awhile and then exits with the message: pthread_mutex_destroy returned 16 Expected Results: The program runs indefinitely without exiting. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1137143] patch openSUSE-2019-1495 does not contain sles12sp3-docker-image, sles12sp4-image
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1137143 http://bugzilla.suse.com/show_bug.cgi?id=1137143#c1 --- Comment #1 from Marcus Meissner <meissner(a)suse.com> --- i should have edited the patchinfo. sorry. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1112920] [Build 20181022] openQA test fails in start_install as plasma5-desktop package not built for ppc64 (BE)
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1112920 http://bugzilla.suse.com/show_bug.cgi?id=1112920#c23 --- Comment #23 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1112920) was mentioned in https://build.opensuse.org/request/show/707212 15.1 / openSUSE-release-tools -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137143] New: patch openSUSE-2019-1495 does not contain sles12sp3-docker-image, sles12sp4-image
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137143 Bug ID: 1137143 Summary: patch openSUSE-2019-1495 does not contain sles12sp3-docker-image, sles12sp4-image Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The sle* stuff doesnt apply on Leap obviously # zypper info -t patch openSUSE-2019-1495 [...] Summary : Recommended update for sles12sp3-docker-image, sles12sp4-image, system-user-root Description : This update for sles12sp3-docker-image, sles12sp4-image, system-user-root fixes the following issues: - CVE-2019-5021: Include an invalidated root password by default, not an empty one (bsc#1134524) This update was imported from the SUSE:SLE-15:Update update project. Provides : patch:openSUSE-2019-1495 = 1 Conflicts : [2] system-user-root.noarch < 20190513-lp151.3.3.1 system-user-root.src < 20190513-lp151.3.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1135319] New: Upgrading arpwatch: Failed to try-restart arpwatch@.service: Unit name arpwatch@.service is missing the instance name.
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1135319 Bug ID: 1135319 Summary: Upgrading arpwatch: Failed to try-restart arpwatch@.service: Unit name arpwatch@.service is missing the instance name. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just ran `zypper dup` on a (nearly) current Tumbleweed system and got the following error message: Installing: arpwatch-2.1a15-165.1.x86_64 ....................... Additional rpm output: Updating /etc/sysconfig/arpwatch ... Failed to try-restart arpwatch@.service: Unit name arpwatch@.service is missing the instance name. See system logs and 'systemctl status arpwatch@.service' for details. systemctl status arpwatch@.service gives: Failed to get properties: Unit name arpwatch@.service is neither a valid invocation ID nor unit name. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1134068] docker: update to 18.09.5
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1134068 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:10218:important |obs:running:10290:important |obs:running:10290:important | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1097869] Shift overflow in libkmod.h
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1097869 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:11301:moderate |ibs:running:11301:moderate | |obs:running:10338:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0