September 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1175464] New: Cache: failed to add read only location
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175464 Bug ID: 1175464 Summary: Cache: failed to add read only location Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: munix9(a)googlemail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE Tumbleweed 20200817 $ zypper se -si apparmor Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+------------------------+---------+--------------+--------+----------------------- i | apparmor | pattern | 20200505-6.1 | x86_64 | Haupt-Repository (OSS) i | apparmor-abstractions | package | 2.13.4-6.1 | noarch | Haupt-Repository (OSS) i | apparmor-docs | package | 2.13.4-6.1 | noarch | Haupt-Repository (OSS) i | apparmor-parser | package | 2.13.4-6.1 | x86_64 | Haupt-Repository (OSS) i | apparmor-parser-lang | package | 2.13.4-6.1 | noarch | Haupt-Repository (OSS) i | apparmor-profiles | package | 2.13.4-6.1 | noarch | Haupt-Repository (OSS) i | apparmor-utils | package | 2.13.4-6.1 | noarch | Haupt-Repository (OSS) i | apparmor-utils-lang | package | 2.13.4-6.1 | noarch | Haupt-Repository (OSS) i | libapparmor1 | package | 2.13.4-6.1 | x86_64 | Haupt-Repository (OSS) i | patterns-base-apparmor | package | 20200505-6.1 | x86_64 | Haupt-Repository (OSS) i | perl-apparmor | package | 2.13.4-6.1 | x86_64 | Haupt-Repository (OSS) i | python3-apparmor | package | 2.13.4-6.1 | x86_64 | Haupt-Repository (OSS) i | yast2-apparmor | package | 4.2.4-1.1 | noarch | Haupt-Repository (OSS) $ systemctl -a --no-pager status apparmor.service ● apparmor.service - Load AppArmor profiles Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2020-08-18 19:12:30 CEST; 33min ago Main PID: 443 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/apparmor.service Aug 18 19:12:30 xyz apparmor.systemd[776]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz apparmor.systemd[783]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz apparmor.systemd[790]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz apparmor.systemd[804]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz apparmor.systemd[839]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz apparmor.systemd[851]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz apparmor.systemd[858]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz apparmor.systemd[879]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz apparmor.systemd[893]: Warnung aus stdin (Zeile 1): Cache: failed to add read only location '/usr/share/apparmor/cache', does not contain valid cache directory for the specified feature set Aug 18 19:12:30 xyz systemd[1]: Finished Load AppArmor profiles. $ grep -r apparmor/cache /etc/ /etc/apparmor/parser.conf:cache-loc /var/cache/apparmor,/usr/share/apparmor/cache $ ls -l /var/cache/apparmor/ total 4 drwx------ 2 root root 4096 Aug 18 18:59 3d1f2faf.0 $ ls -l /usr/share/apparmor/cache total 4 drwxr-xr-x 2 root root 4096 Aug 18 19:00 5a1d3117.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1176467] New: VirtualBox 6.1.14 from the Virtualization repository doesn't start
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176467 Bug ID: 1176467 Summary: VirtualBox 6.1.14 from the Virtualization repository doesn't start Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: lopa(a)mailbox.org QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- Installed packages: virtualbox-6.1.14-558.3.x86_64 virtualbox-kmp-default-6.1.14_k5.9.0_rc4_2.gf0801b1-558.2.x86_64 virtualbox-qt-6.1.13-1.1.x86_64 VirtualBox can't be started: $ VirtualBox /usr/lib/virtualbox/VirtualBox6: symbol lookup error: /usr/lib/virtualbox/VirtualBox6: undefined symbol: _ZN17QIDialogContainer20setProgressBarHiddenEb The demangled symbol is QIDialogContainer::setProgressBarHidden(bool) and setProgressBarHidden seems to be defined neither in QIDialogContainer nor in any of its superclasses. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1176468] New: /etc/alternatives/man points to a non existing target
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176468 Bug ID: 1176468 Summary: /etc/alternatives/man points to a non existing target Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: lopa(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It seems, that /usr/bin/man is now a symbolic link to /etc/alternatives/man, but this is an dangling link. # ll /usr/bin/man /etc/alternatives/man /usr/lib/man-db/wrapper ls: cannot access '/usr/lib/man-db/wrapper': No such file or directory lrwxrwxrwx 1 root root 23 Aug 17 14:03 /etc/alternatives/man -> /usr/lib/man-db/wrapper lrwxrwxrwx 1 root root 21 Sep 4 12:17 /usr/bin/man -> /etc/alternatives/man /etc/alternatives/man should point to /usr/libexec/man-db/man -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176466] New: virtualbox-6.1.13 doesn't work with USB 2.0 controller enabled
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176466 Bug ID: 1176466 Summary: virtualbox-6.1.13 doesn't work with USB 2.0 controller enabled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: lopa(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Installed packages: virtualbox-kmp-default-6.1.13_k5.8.7_1-1.2.x86_64 virtualbox-qt-6.1.13-1.1.x86_64 virtualbox-6.1.13-1.1.x86_64 Oracle_VM_VirtualBox_Extension_Pack-6.1.12.vbox-extpack A virtual machine doesn't start if the USB 2.0(OHCI+EHCI)-Controller is enabled. There's no 6.1.13 extension pack, therefore I have Extension_Pack 6.1.12 installed. Error messages: Failed to load R0 module /usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxEhciR0.r0: RTLdrGetBits failed (VERR_SYMBOL_VALUE_TOO_BIG). Failed to load ring-0 module 'VBoxEhciR0.r0' for device 'usb-ehci' (VERR_SYMBOL_VALUE_TOO_BIG). Fehlercode: NS_ERROR_FAILURE (0x80004005) Komponente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176418] New: gnome-shell[4553]: Failed to load background 'file:///home/adam': Error opening file /home/adam: Is a directory
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176418 Bug ID: 1176418 Summary: gnome-shell[4553]: Failed to load background 'file:///home/adam': Error opening file /home/adam: Is a directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: adam(a)valkor.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Repeated messages in user journal: Sep 08 18:45:58 think gnome-shell[4553]: Failed to load background 'file:///home/adam': Error opening file /home/adam: Is a directory Sep 08 18:45:58 think gnome-shell[4553]: Failed to load background 'file:///home/adam': Error opening file /home/adam: Is a directory Sep 08 18:45:58 think gnome-shell[4553]: Failed to load background 'file:///home/adam': Error opening file /home/adam: Is a directory Removing this patch removes the error, so it is likely the problem: gnome-shell-fate324570-Make-GDM-background-image-configurable.patch -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1173185] Latest Mesa Update breaks Kaffeine output on Radeon (regression in r600 VAAPI driver?)
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173185 http://bugzilla.opensuse.org/show_bug.cgi?id=1173185#c124 Stakanov Schufter <stakanov(a)freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(stakanov@freenet. | |de) | --- Comment #124 from Stakanov Schufter <stakanov(a)freenet.de> --- OK, I need more advise. I am running kaffeine with the given repo. HD works. But SD does not work any more in b/w but is in color and segfaults without giving backtrace, within 2 seconds. So, konqi one time would have liked to create a backtrace but said I need to install debug libraries, but not which. How should I proceed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176464] New: Make columns set in KSysGuard consistent with the state of Per-process Network Usage plugin in Leap build
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176464 Bug ID: 1176464 Summary: Make columns set in KSysGuard consistent with the state of Per-process Network Usage plugin in Leap build Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: alexander.shchadilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- KSysGuard has a plugin that enables per-process traffic measurement in the Process Table tab and introduces the new "Download" and "Upload" columns for that: https://github.com/KDE/ksysguard/tree/master/plugins/process/network It seems that this plugin is disabled in the current build of KSysGuard for Leap 15.2: - "Download" and "Upload" columns are always empty - /usr/lib/ksysguard/ksgrd_network_helper file is not present in my system so I suggest fixing it either by enabling the plugin or by removing related columns. There is a confirmed bug report on KDE tracker about ksgrd_network_helper causing high CPU usage: https://bugs.kde.org/show_bug.cgi?id=414036 >From this perspective, disabling the plugin looks like a sane decision, actually I just do not fully understand why columns are still present if KSysGuard was built without the plugin. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1174285] New: /.snapshots/grub-snapshot.cfg does not contain entries for snapshots created with transactional-update
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1174285 Bug ID: 1174285 Summary: /.snapshots/grub-snapshot.cfg does not contain entries for snapshots created with transactional-update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: m4ng4n(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is on openSUSE Tumbleweed 20200716, using transactional-update on a _read-write_ btrfs filesystem, _not_ a transactional-server installation. When updating the system with tansactional-update -i cleanup dup any new snapshot created by transactional-update is missing in /.snapshots/grub-snapshot.cfg, making it impossible to boot from a previously working snapshot. When a snapshot is created manually with snapper create it correctly appears in that file and is bootable, so snapper is basically working correctly. It is possible for me to add an entry for an existing transactional-update-snapshot by editing /.snapshots/grub-snapshot.cfg and this - manually added - snapshot shows up in the grub2 menu as bootable snapshot and it can be selected and booted. >From a grub2 cmd-line if entering ls /.snapshots all available snapshots are seen, it is just that these snapshots do not get added to /.snapshots/grub-snapshot.cfg. I cannot imagine that this behaviour is intentional. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1176463] New: X11:RemoteDesktop:x2go/x2goclient: Bug - missing nxproxy
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176463 Bug ID: 1176463 Summary: X11:RemoteDesktop:x2go/x2goclient: Bug - missing nxproxy Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: 64bit OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: mkromer(a)medozas.de Reporter: k.bug(a)vink-slott.dk QA Contact: screening-team-bugs(a)suse.de CC: jengelh(a)inai.de Found By: --- Blocker: --- Trying to install gives the following message on 15.1, 15.2 and maybee other lillos:~ # zypper install x2goclient ... Problem: nothing provides nxproxy needed by x2goclient-4.1.2.2-lp152.1.2.x86_64 Solution 1: do not install x2goclient-4.1.2.2-lp152.1.2.x86_64 The version from Tristan Miller (psych0naut) works: https://build.opensuse.org/package/show/home:psych0naut:x2go/x2goclient -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173630] VUL-0: CVE-2020-15395: libmediainfo, mediainfo: buffer overflow in the MpegPs parser
by bugzilla_noreply＠suse.com 13 Sep '20

13 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1173630 https://bugzilla.suse.com/show_bug.cgi?id=1173630#c4 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Marcus Meissner <meissner(a)suse.com> --- released -- You are receiving this mail because: You are on the CC list for the bug.

1 0