April 2023 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1210492] New: Gnome Settings -> Color option is not available in the default install
by bugzilla_noreply＠suse.com 17 Apr '23

17 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210492 Bug ID: 1210492 Summary: Gnome Settings -> Color option is not available in the default install Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: silviucc(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0 Build Identifier: On a default install of MicroOS this option is missing. Reproducible: Always Steps to Reproduce: 1.Start Settings. There should be a "Color" option on the left column that allows installing and managing color profiles for various devices like displays, printers, etc. Actual Results: The "Color" option is missing. Expected Results: There should be a "Color" option on the left column that allows installing and managing color profiles for various devices like displays, printers, etc. The workaround is to install the missing package in transactional-update shell gnome-control-center-color Maybe the package should be part of the OS image. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1210330] New: MicroOS Desktop Plasma: Kate Project plugin doesn't work
by bugzilla_noreply＠suse.com 13 Apr '23

13 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210330 Bug ID: 1210330 Summary: MicroOS Desktop Plasma: Kate Project plugin doesn't work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: herzenschein(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kate is not installed as a flatpak. I think it came with the default snapshot, as there's no Kate on flathub, only flathub-beta and kdeapps. When I initialize or clone any git repository and open its files with Kate, the Project pane on the left provided by the Projects plugin doesn't update to show the contents of the repository. Additionally, the Git pane, also provided by the Projects plugin, doesn't show any changes if I edit and save any files in the repository, even when I click the Refresh button. This works fine with Kate installed in a distrobox container, as well as Kate compiled from within a distrobox container. Unsure if this is related, but the experimental Kate flatpak doesn't have a functional Projects plugin either. I wonder if something is missing from both. https://github.com/flathub/org.kde.kate/issues/32 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1210026] New: Delay of portal service start on MicroOS Desktop KDE delays flatpak application startup.
by bugzilla_noreply＠suse.com 13 Apr '23

13 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210026 Bug ID: 1210026 Summary: Delay of portal service start on MicroOS Desktop KDE delays flatpak application startup. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: touko.alasavikota(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running MicroOS Desktop KDE snapshot 20230330 (originally 20230212). Proprietary nvidia drivers and wayland. My install comes automatically with multiple xdg-desktop-portal backends: xdg-desktop-portal-gnome, xdg-desktop-portal-kde and xdg-desktop-portal-gtk. The problem is that the GNOME backend is started first and it times out and fails. I think that this delays the start of xdg-desktop-portal and flatpak applications like Firefox won't start during the delay. The portal service is able to start after the timeout and everything works normally after that. This github issue might be related: https://github.com/flatpak/xdg-desktop-portal/issues/656 I tested installing a fresh MicroOS Desktop 20230330 with both GNOME and KDE flavors. They only had the their respective backends installed with no flatpak application launch delays on startup. My other MicroOS Desktop KDE is originally from snapshot 20230212 so that might have had the GNOME implementation included from the start. I'm not sure if multiple xdg-desktop-portal implementations should even be installed in the first place but in this state the system will have a consistent timeout with every boot. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1210302] New: Snapshot entries aren't being created for grub
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210302 Bug ID: 1210302 Summary: Snapshot entries aren't being created for grub Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: lilfrogg(a)posteo.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is my second MicroOS install in a row where new snapshots at some point stopped showing up in the grub menu. The snapshots themselves are created as normal and it appears that the script of the grub2-snapper-plugin fails to create the entries because my snapshots appear to be writable for some reason. Here are some terminal outputs I was asked to create in the oS support channel: sudo find /.snapshots -maxdepth 2 -type f -name grub-snapshot.cfg �/.snapshots/91/grub-snapshot.cfg /.snapshots/grub-snapshot.cfg� Snapshot 91 is one I manually created with 'snapper create' which creates a grub entry. all the other snapshots don't show up Using 'sh -o xtrace usr/lib/snapper/plugins/grub --enable' in a transactional-update shell �+ set -e + grub_mkconfig=/usr/sbin/grub2-mkconfig + grub_mkrelpath=/usr/bin/grub2-mkrelpath + grub_script_check=/usr/bin/grub2-script-check + grub_setting=/etc/default/grub + grub_cfg=/boot/grub2/grub.cfg + grub_snapshot_cfg=/boot/grub2/snapshot_submenu.cfg + snapper_snapshot_path=/.snapshots + snapshot_submenu_name=grub-snapshot.cfg + snapper_snapshots_cfg=/.snapshots/grub-snapshot.cfg + hotkey= ++ uname -m + machine=x86_64 + case "$machine" in + cmdline='/usr/lib/snapper/plugins/grub --enable hotkey='\'''\''' + test 1 -gt 0 + option=--enable + shift + case "$option" in + opt_enable=true + test 0 -gt 0 + '[' xtrue = xtrue ']' + snapper_snapshots_cfg_refresh + '[' '!' -d /.snapshots ']' + cs= + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/79/snapshot + '[' '!' -d /.snapshots/79 -o -w /.snapshots/79/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/80/snapshot + '[' '!' -d /.snapshots/80 -o -w /.snapshots/80/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/81/snapshot + '[' '!' -d /.snapshots/81 -o -w /.snapshots/81/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/82/snapshot + '[' '!' -d /.snapshots/82 -o -w /.snapshots/82/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/83/snapshot + '[' '!' -d /.snapshots/83 -o -w /.snapshots/83/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/84/snapshot + '[' '!' -d /.snapshots/84 -o -w /.snapshots/84/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/85/snapshot + '[' '!' -d /.snapshots/85 -o -w /.snapshots/85/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/86/snapshot + '[' '!' -d /.snapshots/86 -o -w /.snapshots/86/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/87/snapshot + '[' '!' -d /.snapshots/87 -o -w /.snapshots/87/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/88/snapshot + '[' '!' -d /.snapshots/88 -o -w /.snapshots/88/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/89/snapshot + '[' '!' -d /.snapshots/89 -o -w /.snapshots/89/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/90/snapshot + '[' '!' -d /.snapshots/90 -o -w /.snapshots/90/snapshot ']' + continue + for s_dir in ${snapper_snapshot_path}/* + snapshot=/.snapshots/grub-snapshot.cfg/snapshot + '[' '!' -d /.snapshots/grub-snapshot.cfg -o -w /.snapshots/grub-snapshot.cfg/snapshot ']' + continue + hk= + '[' -z '' ']' ++ printf %s '' ++ sort -Vr + cat + /usr/bin/grub2-script-check /.snapshots/grub-snapshot.cfg.new + mv -f /.snapshots/grub-snapshot.cfg.new /.snapshots/grub-snapshot.cfg + '[' x = xtrue ']' + '[' x = xtrue ']'� ls -lad /.snap* �drwxr-x---. 1 root root 98 Apr 11 11:02 /.snapshots� mount | grep snapshots �/dev/mapper/cr_root on / type btrfs (ro,relatime,seclabel,space_cache=v2,subvolid=363,subvol=/(a)/.snapshots/90/snapshot) /dev/mapper/cr_root on /.snapshots type btrfs (rw,relatime,seclabel,space_cache=v2,subvolid=266,subvol=/@/.snapshots)� -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210207] New: selinux: missing policy for dbus allow msg for xdm_t
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210207 Bug ID: 1210207 Summary: selinux: missing policy for dbus allow msg for xdm_t Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: luca.dimaio1(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 866166 --> https://bugzilla.suse.com/attachment.cgi?id=866166&action=edit generated rule for selinux with audit2allow After latest update of either gpg or selinux, now communication with gpg-agent is denied by selinux: Apr 06 09:47:58 localhost dbus-daemon[1914]: avc: denied { send_msg } for msgtype=method_return dest=:1.1048 spid=1892 tpid=5585 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:system_r:spc_t:s0 tclass=dbus permissive=0 Running audit2why avc: denied { send_msg } for msgtype=method_return dest=:1.1048 spid=1892 tpid=5585 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:system_r:spc_t:s0 tclass=dbus permissive=0 Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. In fact, audit2allow generates a valid module, and everything works like before Attaching here the generated modules, loading them fixes the issue -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1210125] New: Unable to mount network Shares from within dolphin
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210125 Bug ID: 1210125 Summary: Unable to mount network Shares from within dolphin Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: sfalken(a)cloverleaf-linux.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Likely due to lacking kio_fuse and/or kdenetwork-filesharing. Currently poking at things and testing in VM -- You are receiving this mail because: You are the assignee for the bug.

1 1