December 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1179744] New: keyboard / mouse not working on openSUSE (leap + tumbleweed) - works on Fedora
by bugzilla_noreply＠suse.com 08 Dec '20

08 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179744 Bug ID: 1179744 Summary: keyboard / mouse not working on openSUSE (leap + tumbleweed) - works on Fedora Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: damianatorrpm(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Not sure if this is the right component to report against. openSUSE Leap and Tumbleweed have the issue on my system that keyboard and mouse is not working *if* IOMMU is disasbled in the BIOS. Even though IOMMU is disabled in BIOS Fedora will detect keyboard and mouse just fine. The keyboard / mouse disappears once the kernel is loaded (works in bootloader). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1179447] VUL-0: CVE-2020-28926: minidlna: before versions 1.3.0 allows remote code execution
by bugzilla_noreply＠suse.com 08 Dec '20

08 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179447 https://bugzilla.suse.com/show_bug.cgi?id=1179447#c7 --- Comment #7 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2020:2204-1: An update that fixes two vulnerabilities is now available. Category: security (moderate) Bug References: 1179447 CVE References: CVE-2020-12695,CVE-2020-28926 JIRA References: Sources used: openSUSE Backports SLE-15-SP2 (src): minidlna-1.3.0-bp152.4.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179536] URL of "crash" package needs updating
by bugzilla_noreply＠suse.com 08 Dec '20

08 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179536 https://bugzilla.suse.com/show_bug.cgi?id=1179536#c2 David Mair <dmair(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from David Mair <dmair(a)suse.com> --- Submitted for Factory. References to the upstream project URL also appear in a few project files. I made corrections but in some cases added a note reporting the new URL to the same material without removing the old one. This is because the old reference is the origin of the source material in the package. The next crash package version upgrade will obsolete the old references as a clean act in the project source. That is released upstream and our upgrade is work I have pending. -- 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 07 Dec '20

07 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1144527 https://bugzilla.suse.com/show_bug.cgi?id=1144527#c8 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dcermak(a)suse.com) --- Comment #8 from James Fehlig <jfehlig(a)suse.com> --- (In reply to Dan ��erm��k from comment #7) > type=AVC msg=audit(1607005863.720:1043): apparmor="DENIED" operation="mount" > info="failed mntpnt match" error=-13 profile="libvirtd" > name="/run/libvirt/qemu/3-tests_15.2-arm.dev/null" pid=23462 comm="libvirtd" > srcname="/dev/null" flags="rw, bind" I'm not an apparmor expert, but a rough translation: the libvirtd apparmor profile denied 'mount -o rw,bind ...' > So do libvirt's apparmor rules need updating? Probably. If I understand the mount rule stuff in apparmor.d man page, allowing the bind option should help. E.g. can you see if the following change in /etc/apparmor.d/usr.sbin.libvirtd helps (reload the profile with 'apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd' after making the change) --- usr.sbin.libvirtd.orig 2020-12-07 16:50:43.027846340 -0700 +++ usr.sbin.libvirtd 2020-12-07 16:51:53.093047089 -0700 @@ -30,7 +30,7 @@ capability sys_resource, mount options=(rw,rslave) -> /, - mount options=(rw, nosuid) -> /{var/,}run/libvirt/qemu/*.dev/, + mount options=(rw, nosuid, bind) -> /{var/,}run/libvirt/qemu/*.dev/, umount /{var/,}run/libvirt/qemu/*.dev/, # libvirt provides any mounts under /dev to qemu namespaces -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179592] tigervnc-x11vnc requires python2
by bugzilla_noreply＠suse.com 07 Dec '20

07 Dec '20

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

1 0

[Bug 1152390] New: lightdm[6334]: segfault at 0 ip b7d81e41 sp bfcdc50c error 4 in libc-2.29.so[b7cff000+152000]
by bugzilla_noreply＠novell.com 07 Dec '20

07 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1152390 Bug ID: 1152390 Summary: lightdm[6334]: segfault at 0 ip b7d81e41 sp bfcdc50c error 4 in libc-2.29.so[b7cff000+152000] Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 32bit OS: Linux Status: NEW Severity: Critical Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: samuelbernardo.mail(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 819889 --> http://bugzilla.opensuse.org/attachment.cgi?id=819889&action=edit dmidecode.txt lscpu.txt lsmod.txt uname.txt dmesg.txt When starting lxde desktop session the segfault happens since it was installed libc-2.29. Looking into .cache/lxsession/LXDE/run.log in user session appears the following errors: ** Message: 17:48:20.753: app.vala:130: /usr/bin/ssh-agent exit with this type of exit: 0 (uint32 1,) Looking in '/etc/xdg/parcellite/parcelliterc' Looking in '/etc/xdg/parcellite/parcelliterc' Flag 0x0001, status 0, EXIT 1 STAT 0 ** (zeitgeist-datahub:9271): WARNING **: 17:48:25.586: zeitgeist-datahub.vala:224: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! Openbox-Message: Unable to find a valid menu file "/usr/share/lxde/openbox/menu.xml" ** (pcmanfm:8964): WARNING **: 17:48:26.800: modules directory is not accessible (lxpanel:8963): GLib-GObject-CRITICAL **: 17:48:27.999: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lxpanel:8963): GLib-GObject-CRITICAL **: 17:48:27.987: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lxpanel:8963): GLib-GObject-CRITICAL **: 17:48:28.005: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lxpanel:8963): GLib-GObject-CRITICAL **: 17:48:28.005: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (nm-applet:8985): nm-applet-WARNING **: 17:48:32.828: NetworkManager is not running (lxpanel:8963): Wnck-WARNING **: 17:48:36.078: Unhandled action type _OB_WM_ACTION_UNDECORATE pcmanfm: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. X connection to :0 broken (explicit kill or server shutdown). ** Message: 17:48:53.745: app.vala:130: xscreensaver exit with this type of exit: 256 ** Message: 17:48:53.745: app.vala:145: Exit normal, don't reload lxpolkit: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. lxclipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** Message: 17:48:53.772: app.vala:130: pcmanfm exit with this type of exit: 256 ** Message: 17:48:53.772: app.vala:145: Exit normal, don't reload opensuse-welcome: Fatal IO error 0 (Success) on X server :0. Gdk-Message: 17:48:53.783: blueberry-obex-agent.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 17:48:53.788: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Gdk-Message: 17:48:53.793: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. lxpanel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. parcellite: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. pk-update-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. X connection to :0 broken (explicit kill or server shutdown). ** Message: 17:48:53.827: app.vala:347: openbox-lxde exit with this type of exit: 256 ** Message: 17:48:53.827: app.vala:369: Exit normal, don't reload lxsession: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. openbox-lxde (null) lxpolkit (null) lxpanel --profile LXDE (null) pcmanfm --desktop --profile LXDE (null) xscreensaver -no-splash (null) /usr/bin/ssh-agent -s (null) -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1179592] tigervnc-x11vnc requires python2
by bugzilla_noreply＠suse.com 07 Dec '20

07 Dec '20

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

1 0

[Bug 1179720] VUL-1: CVE-2017-2910: libxls: Out-of-bounds Write vulnerability in the xls_addCell function of libxls 2.0 can cause a memory corruption resulting in remote code execution
by bugzilla_noreply＠suse.com 07 Dec '20

07 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179720 Maintenance Robot <maint-coord+maintenance_robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179720] New: VUL-1: CVE-2017-2910: libxls: Out-of-bounds Write vulnerability in the xls_addCell function of libxls 2.0 can cause a memory corruption resulting in remote code execution
by bugzilla_noreply＠suse.com 07 Dec '20

07 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179720 Bug ID: 1179720 Summary: VUL-1: CVE-2017-2910: libxls: Out-of-bounds Write vulnerability in the xls_addCell function of libxls 2.0 can cause a memory corruption resulting in remote code execution Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/272633/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2017-2910 An exploitable Out-of-bounds Write vulnerability exists in the xls_addCell function of libxls 2.0. A specially crafted xls file can cause a memory corruption resulting in remote code execution. An attacker can send malicious xls file to trigger this vulnerability. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-2910 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2910 https://talosintelligence.com/vulnerability_reports/TALOS-2017-0417 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179246] Dom0 hangs when pinning CPUs for dom0 with HVM guest
by bugzilla_noreply＠suse.com 07 Dec '20

07 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179246 https://bugzilla.suse.com/show_bug.cgi?id=1179246#c6 Jan Beulich <jbeulich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(g.w.kant@hunenet. | |nl) --- Comment #6 from Jan Beulich <jbeulich(a)suse.com> --- (In reply to Dion Kant from comment #4) > Created attachment 844150 [details] > xl dmesg There's no sign of a problem in this log, afaics. Can you confirm this is covering a hang of the sort you were observing? -- You are receiving this mail because: You are on the CC list for the bug.

1 0