April 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1183767] libvirt segfault in qemuDomainDefAddDefaultDevices when invoked via vagrant
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183767 https://bugzilla.suse.com/show_bug.cgi?id=1183767#c6 Dan ��erm��k <dcermak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID Flags|needinfo?(dcermak(a)suse.com) | --- Comment #6 from Dan ��erm��k <dcermak(a)suse.com> --- (In reply to James Fehlig from comment #5) > (In reply to Dan ��erm��k from comment #3) > > Yes, this is definitely a regression. I have been using vagrant to spin up > > libvirt based VMs on that machine for ~2 years now and it just started to > > fail recently. > > Something must have changed on the host to make kvm unavailable. Your > capabilities file only has cpus and machines of type tcg. If kvm was > available you would see similar lines with e.g. > > <cpu type='kvm' .../> > ... > <machine type='kvm' .../> > > Trying to start a VM with <domain type='kvm' .../> is doomed to fail when > kvm is not available on the host. Is the kvm module loaded? Does the > user:group qemu is running under (qemu:qemu by default) have access to > /dev/kvm? Hm, /dev/kvm is missing�� Looks like that is the issue here, sorry for the noise. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144527] Virtualization/libvirt: Bug Call to virDomainCreateWithFlags failed: internal error: Process exited prior to exec: libvirt: error : Failed to bind /dev/null on to /var/run/libvirt/qemu/496-tests_testing-15.0-a.dev/null: Permission denied
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1144527 https://bugzilla.suse.com/show_bug.cgi?id=1144527#c11 --- Comment #11 from Dan ��erm��k <dcermak(a)suse.com> --- (In reply to James Fehlig from comment #10) > (In reply to Dan ��erm��k from comment #9) > > Should we forward this to the libvirt and/or apparmor maintainers? > > IMO we need a better understanding of the problem first. In the original > description you said you "frequently" encounter the problem, so I assume it > does work on occasion? I just had to reinstall a good portion of the virtualization stack on the host in question and all the jobs started to fail immediately. So my answer to that would be a "no". > > > I have the suspicion that once one user creates a domain, any other user (including root) can no longer create them > > Can you verify this suspicion? :-) That does appear to be a wrong suspicion, I have just tried it and root could re-create the domain that the jenkins user created previously. > > > Call to virDomainCreateWithFlags failed: internal error: Process exited prior to exec: libvirt: error : Failed to bind /dev/null on to /var/run/libvirt/qemu/496-tests_testing-15.0-a.dev/null: Permission denied > > This error, along with your DENIED messages from audit.log, indicate > building the VM's namespace failed. /dev/null on the host could not be bind > mounted to the VM's private namespace. However a lot has changed in libvirt > since 6.0.0, including moving the namespace creation from the qemu process > to the libvirtd process > > https://gitlab.com/libvirt/libvirt/-/commit/ > 8da362fe62766b4eee209cd3ce591ceb62299d13 > https://gitlab.com/libvirt/libvirt/-/commit/ > 9048dc4e627ddf33996084167bece7b5fb83b0bc > > The first commit describes the rational, the second one uses it for basic > /dev nodes. There are several subsequent commits doing the same for disks, > hostdevs, chardevs, etc. Bottom line is the patch I suggested in #8 is not > needed with libvirt >= 6.7.0 since mounting is done within the libvirtd > process. > > Is it possible for you to verify the issue does not exist on TW, or SLES15 > SP3 betas if that is easier? I will try to update the machine to SLES15 SP3. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1029961] [META] Finalize /bin -> /usr/bin merge
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1029961 https://bugzilla.suse.com/show_bug.cgi?id=1029961#c71 --- Comment #71 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1029961) was mentioned in https://build.opensuse.org/request/show/883212 Factory / ksh -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1134688] New: Bug with German Umlauts on desktop
by bugzilla_noreply＠novell.com 06 Apr '21

06 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1134688 Bug ID: 1134688 Summary: Bug with German Umlauts on desktop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: office(a)hantsch.co.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I use openSUSE Leap 15.0 with KDE/Plasma5. The same problem exists also on openSuSE 42.x My system wide locale settings are: de_DE@euro (German, no UTF8). All files/folders (their names) are correctly encoded in iso-8859-1. Since Plasma5 I experience the following mis-behavior, while this smoothly worked on KDE4 (openSuSE 13.x): I am able to open Dolphin. Inside Dolphin I can navigate without any problem into folders having German Umlauts in their names. I also can click a file with German Umlauts in its name. I also can copy/paste and/or drag/drop such files/folders from Dolphin directly onto the desktop. Everything is fine here. I am also able to right-click such file/folder on the desktop to rename it (this also works as it should). When trying to click such file/folder on the desktop (to open it), I get an error: (translated German->English by me): "This command cannot be executed. The file or folder <.....> does not exist" Surprisingly the correct filename is showing up in <....>! As an example, a testing filename is: /home/rainer/Desktop/miniLÖT-Deckel.pdf (notice the "Ö" inside the file name. When renaming the file (right-click -> rename) to i.e. miniLOeT-Deckel.pdf, I am able to open the file afterwards. This happens with any kind of file/folder (also symlinks, etc..., even over NFS mounts). converting the entire system (and also all servers) is no option. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1134688] Bug with German Umlauts on desktop
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1134688 https://bugzilla.suse.com/show_bug.cgi?id=1134688#c5 --- Comment #5 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1134688) was mentioned in https://build.opensuse.org/request/show/883204 Backports:SLE-15-SP3 / kio -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1167982] New: texlive-filesystem fails to update with invalid group 'root:mktex'
by bugzilla_noreply＠novell.com 06 Apr '21

06 Apr '21

http://bugzilla.suse.com/show_bug.cgi?id=1167982 Bug ID: 1167982 Summary: texlive-filesystem fails to update with invalid group 'root:mktex' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: thomas.schraitle(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 834127 --> http://bugzilla.suse.com/attachment.cgi?id=834127&action=edit Excerpt from /var/log/YaST2/y2log Hi, I've tried an online update today. The YaST Online Update module offered me to update the package "texlive-filesystem". So I confirmed but after the installation, YaST showed me the following error messages after hitting the "Details" button: Subprocess failed. Error: RPM fehlgeschlagen: chown: invalid group: 'root:mktex' chown: invalid group: 'root:mktex' chown: invalid group: 'root:mktex' chown: invalid group: 'root:mktex' error: %prein(texlive-filesystem-2017.135-lp151.8.3.1.noarch) scriptlet failed, exit status 1 error: texlive-filesystem-2017.135-lp151.8.3.1.noarch: install failed error: texlive-filesystem-2017.135-lp151.7.1.noarch: erase skipped I've attached an excerpt of the /var/log/YaST2/y2log how YaST sees the above error. Hope this helps. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1155685] useradd created wrong home directory
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1155685 Thorsten Behrens <thorsten.behrens(a)allotropia.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thorsten.behrens@allotropia | |.de Assignee|thorsten.behrens(a)cib.de |screening-team-bugs(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159726] shadow-4.7-4.1.i586.rpm: wrong installation path /usr/etc/pam.d
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1159726 Thorsten Behrens <thorsten.behrens(a)allotropia.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thorsten.behrens@allotropia | |.de Assignee|thorsten.behrens(a)cib.de |screening-team-bugs(a)suse.de OS|openSUSE Factory |All -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183566] New: HyperKitty on https://lists.opensuse.org/: no Message ID
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183566 Bug ID: 1183566 Summary: HyperKitty on https://lists.opensuse.org/: no Message ID Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: werner(a)suse.com QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- This MUA does not set any Message-ID and hence stigmatize mails as SPAM -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1183865] Azure CLI failure: az container fails with unexpected error
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183865 https://bugzilla.suse.com/show_bug.cgi?id=1183865#c7 Robert Munteanu <rombert(a)apache.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #7 from Robert Munteanu <rombert(a)apache.org> --- Works great with Tumbleweed version 20210401. Thank you for the fix! -- You are receiving this mail because: You are on the CC list for the bug.

1 0