openSUSE Bugs July 2020

bugs@lists.opensuse.org

1 participants
3607 discussions

[Bug 1100695] wicked does not handle WIRELESS_POWER switch
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1100695 Marius Tomaschewski <mt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1173468 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173483] rebootmgr service cordump on restart
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173483 https://bugzilla.suse.com/show_bug.cgi?id=1173483#c2 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs(a)opensuse.org |kukuk(a)suse.com --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- The crash is fixed, but rebootmgrd can still not be stopped or restarted with systemctl. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173483] rebootmgr service cordump on restart
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173483 https://bugzilla.suse.com/show_bug.cgi?id=1173483#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com Flags| |needinfo?(rbrown(a)suse.com) --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- The problem is the following pull request: https://github.com/SUSE/rebootmgr/pull/3 Richard, do you remember why rebootmgr should not be killed during shutdown? By looking at the code I see only a log message which could not be printed after systemctl reboot is called. What happens here is: systemctl will not stop rebootmgr during a restart, but starts a second instance. And the second instance will core dump. While a second instance should abort with an error and should not crash, the problem is, if systemctl is not allowed to kill rebootmgr during shutdown, we can never restart it with systemctl. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173549] New: [HPC, mumps] since the advent of Gcc10 requires -std=legacy for building F77 Code
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173549 Bug ID: 1173549 Summary: [HPC, mumps] since the advent of Gcc10 requires -std=legacy for building F77 Code Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: hpc-bugs(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- Add -std=legacy as build flag and mumps will build again. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1165535] System lockup under memory pressure using encrypted swap on SSD (failed command: WRITE FPDMA QUEUED)
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1165535 https://bugzilla.suse.com/show_bug.cgi?id=1165535#c6 Sebastian Chlad <sebastian.chlad(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sebastian.chlad@s | |use.com) | --- Comment #6 from Sebastian Chlad <sebastian.chlad(a)suse.com> --- Since we do not have much logs and there is no easy and known way of reproducing this problem, devising a test case won't be straightforward for sure. However having some look into the relevant code paths and see if we could come up with some stress tests, hitting as similar condition as possible, might be worth doing. I will do so then starting from checking if there is any test touching these specific code paths. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173550] zypper dumps core on specific subcommands lu, lp, pch
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173550 https://bugzilla.suse.com/show_bug.cgi?id=1173550#c1 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Michael Andres <ma(a)suse.com> --- There seem to be history files with embedded NUL charactes which break the parser. Workaround, in case your file is corrupted similar to the reported ones: Backup: cp /var/log/zypp/history /var/log/zypp/history.orig Remove embedded zeros: cat /var/log/zypp/history.orig | tr -d '\000' >/var/log/zypp/history *** This bug has been marked as a duplicate of bug 1170801 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1170801] zypper: core dump with corrupted history file
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1170801 https://bugzilla.suse.com/show_bug.cgi?id=1170801#c11 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcfleck(a)protonmail.ch --- Comment #11 from Michael Andres <ma(a)suse.com> --- *** Bug 1173550 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 1165983] New: zypper packagekit plugin got confused by needing to downgrade libzypp, breaking upgrade using PackageKit CLI or GUI app
by bugzilla_noreply＠novell.com 01 Jul '20

01 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1165983 Bug ID: 1165983 Summary: zypper packagekit plugin got confused by needing to downgrade libzypp, breaking upgrade using PackageKit CLI or GUI app Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: pointedstick(a)zoho.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 832173 --> http://bugzilla.opensuse.org/attachment.cgi?id=832173&action=edit libzypp package breaks the upgrade in Discover I was upgrading my Tumbleweed installation today using KDE's Discover app and got an error message about libzypp having no update candidate (see attachment). I tried again with PackageKit on the command line (`pkcon update`) and it crashed: virtualbox-host-source-6.1.2-2.4.noarch Source files for virtualbox host kernel modules virtualbox-kmp-default-6.1.2_k5.5.6_1-2.4.x86_64 Kernel modules for VirtualBox virtualbox-qt-6.1.2-2.4.x86_64 Qt GUI part for virtualbox Proceed with changes? [N/y] y The daemon crashed mid-transaction! However using the zypper CLI tool with `sudo zypper dup` works fine, and shows the following: The following package is going to be downgraded: libzypp So something about libzypp needing to be downgraded is making PackageKit really unhappy. This seems related to, but not necessarily the same issue as, Bug 1163737. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1165535] System lockup under memory pressure using encrypted swap on SSD (failed command: WRITE FPDMA QUEUED)
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1165535 https://bugzilla.suse.com/show_bug.cgi?id=1165535#c5 Hannes Reinecke <hare(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian.chlad(a)suse.com Flags| |needinfo?(sebastian.chlad@s | |use.com) --- Comment #5 from Hannes Reinecke <hare(a)suse.com> --- I wouldn't discount the possibility that we're not properly for memory allocation problems, or that the code paths catching these issues are improperly done. IE if there's a memory allocation error (in, say, dm-crypt), and dm-crypt improperly handles the failed allocation in that it catches -ENOMEM yet continues with operation we might end up with such a situation. But as you figured, triggering this is extremely hard. But maybe worthwhile a testcase, and maybe our eager QA team can spin off something here. Sebastian? Do you think it would be possible to devise a testcase for testing this situation? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173507] New: mount failed using input from fstab
by bugzilla_noreply＠suse.com 01 Jul '20

01 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173507 Bug ID: 1173507 Summary: mount failed using input from fstab Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: guenter.halt(a)halt-hoenow.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- if an mountpoint has spaces in the name, the binary mount works fine started in a terminal. However, using the same mountpoint in the /etc/fstab, it reports an error. Example: mkdir "test mp" # space between "test" and "mp" mount /dev/sda1 "test mp" successfully! -------------- in /etc/fstab .... (line36) /dev/sda1 "test mp" ext4 defaults 0 0 .... Command: mount -a Report: mount: /etc/fstab: Einlesefehler in Zeile 36 -- ignoriert ( As real mountpoint was "VirtualBox VMs" intended) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs July 2020