14:00:28 <bcotton> #startmeeting Prioritized bugs and issues 14:00:28 <zodbot> Meeting started Wed Apr 19 14:00:28 2023 UTC. 14:00:28 <zodbot> This meeting is logged and archived in a public location. 14:00:28 <zodbot> The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 14:00:28 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:28 <zodbot> The meeting name has been set to 'prioritized_bugs_and_issues' 14:00:28 <bcotton> #meetingname Fedora Prioritized bugs and issues 14:00:28 <zodbot> The meeting name has been set to 'fedora_prioritized_bugs_and_issues' 14:00:37 <bcotton> #topic Purpose of this meeting 14:00:37 <bcotton> #info The purpose of this process is to help with processing backlog of bugs and issues found during the development, verification and use of Fedora distribution. 14:00:44 <bcotton> #info The main goal is to raise visibility of bugs and issues to help contributors focus on the most important issues. 14:00:44 <bcotton> #link https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_process_description 14:00:51 <bcotton> #topic Roll Call 14:00:58 <bcotton> who's ready to prioritize some bugs! 14:02:50 <amoloney> Hi all! 14:03:09 * bcotton waves to amoloney 14:04:35 <bcotton> nudge nudge mattdm 14:07:12 <bcotton> okay, amoloney well i guess it's up to us :-) 14:07:25 <bcotton> #topic Common Bugs review 14:07:25 <bcotton> #info Let's start with a check of the Common Bugs pages for supported releases and see if any should be nominated as Prioritized Bugs 14:07:25 <bcotton> #link https://ask.fedoraproject.org/c/common-issues/141/none/l/latest?order=votes 14:07:45 <bcotton> oh no, the link is broken post-site-merge 14:07:58 <amoloney> oh lawd 14:09:10 <bcotton> #link https://discussion.fedoraproject.org/c/ask/common-issues/82/none/l/latest?order=votes 14:09:26 <bcotton> (I'm not sure "votes" is still a thing, but that's a mattdm question for later) 14:11:14 <mattdm> votes is no longer a thing 14:11:25 <bcotton> RIP votes 14:11:27 <mattdm> sorry had a conflicting meeting but we canceled it and then I got distracted 14:11:58 <bcotton> should we sort views/activity or not bother sorting? 14:13:41 <mattdm> Views, maybe? 14:14:29 <bcotton> ack 14:15:10 <bcotton> so i'm not seeing anything that jumps out here. let's move on to the ones that are nominated 14:15:29 <bcotton> #topic Nominated bugs 14:15:29 <bcotton> #info 4 nominated bugs 14:15:29 <bcotton> #link https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=flagtypes.name&f2=OP&list_id=10871664&o1=substring&query_format=advanced&v1=fedora_prioritized_bug%3F 14:15:39 <bcotton> #topic English keyboard layout is erroneously used during initramfs phase (e.g. decrypting encrypted storage devices) instead of native layout, on Silverblue / ostree installs 14:15:39 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1890085 14:16:08 <mattdm> bugzilla is SO SLOW 14:17:57 <mattdm> So... that does sounds annoying and longstanding. We'll need this fixed if we want Silverblue to be mainstream 14:18:28 <AndreiManzhov[m]> Hi everyone! Ben, thanks a lot for adding the bug 1890085 for consideration. This one is very annoying and locks the system completely. But it seems easy to fix 14:19:09 <bcotton> agreed. this is really bad experience for people who use different keyboard layouts 14:19:58 <bcotton> proposed #agreed 1890085 is accepted as a prioritized bug. Using the wrong keyboard layout during the boot process is a bad user experience. 14:21:28 <mattdm> +1 14:21:35 <bcotton> #agreed 1890085 is accepted as a prioritized bug. Using the wrong keyboard layout during the boot process is a bad user experience. 14:21:45 <bcotton> #topic Cannot copy/paste to/from KDE VMs 14:21:45 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2016563 14:21:48 <AndreiManzhov[m]> It could be a wider issue in silverblue setup (configuration) process as workstation is installed and functions correctly, while silverblue does not have keyboard settings applied on boot, and also is something missing in power settings (on my thinkpad power profiles do not function correctly in silverblue either, while in workstation everything is fine). So perhaps this could be looked into 14:23:00 <AndreiManzhov[m]> i'm referring to this separate bug: https://bugzilla.redhat.com/show_bug.cgi?id=2175435 14:24:25 <bcotton> AndreiManzhov[m]: that's off-topic right now 14:25:00 <bcotton> so this copy/paste bug is not great. i've hit it a few times. but upstream is aware and there doesn't seem to be a lot of movement 14:25:08 <bcotton> #link https://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/26 14:25:20 <bcotton> so i'm not sure us calling it prioritized will get us anywhere 14:26:17 <danpb> bear in mind that spice as a project and community is practically dead 14:27:16 <bcotton> that does not encourage me 14:28:42 <mattdm> yeah, that :( 14:29:09 <mattdm> Does "don't use spice" solve it? 14:30:30 <danpb> the best recomendation is to run a remote desktop service inside the VM either RDP or VNC 14:30:30 <bcotton> no idea. kamil is not in here to ask, apparently 14:31:26 <bcotton> okay, so based on what danpb has told us... 14:32:29 <bcotton> proposed #agreed 2016563 is rejected as a prioritized bug. The upstream project is not active, so prioritizing won't get us very far. Use of a remote desktop service in the VM is the suggested workaround 14:33:28 <mattdm> Is that true for GNOME as well? 14:33:38 <mattdm> I mean, if not using spice, will copy/paste break? 14:34:09 <bcotton> if it does, they can keep using spice 14:34:22 <danpb> for a hypervisor hosted remote desktop, spice was the only option that provided cut+paste 14:34:26 <mattdm> Until that falls apart.... 14:34:48 <mattdm> Welll, that's unfortunate. But I guess we'll prioritize that bug when we get to it? :) 14:34:51 <danpb> there has been work in QEMU to enable cut+paste with VNC, but we've not got the corresponding client side implemented for VNC and the QEMU side is quite buggy / crash prone 14:34:52 <bcotton> right, but if upstream is effectively dead, that doesn't change our decision here 14:35:21 <danpb> so regardless of GNOME/KDE/whatever i'd recommend a guest hosted remote desktop service as likely to be more reliable 14:37:01 <bcotton> last call for objections to proposed #agreed 2016563 is rejected as a prioritized bug. The upstream project is not active, so prioritizing won't get us very far. Use of a remote desktop service in the VM is the suggested workaround 14:37:55 <mattdm> I guess I don't object. It's pretty bad if people can't just run a VM and copy and paste from it -- vmware and virtualbox (and kvm with spice, I guess!) have made that a normal expectation 14:38:28 <bcotton> it is bad. but we cant' fix it on our own :-) 14:38:29 <bcotton> #agreed 2016563 is rejected as a prioritized bug. The upstream project is not active, so prioritizing won't get us very far. Use of a remote desktop service in the VM is the suggested workaround 14:38:38 <mattdm> I don't want to get a lot more people trying to install virtualbox and dealing with kernel module pain :( 14:38:58 <bcotton> #topic Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader 14:38:58 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2049849 14:40:16 <mattdm> I think we should ask the bootloader team what they're planning. 14:40:49 <mattdm> I know there's some plan in the works to change bootloaders entirely 14:41:01 <mattdm> Maybe worth prioritizing this so to make sure it gets included as a use case 14:42:21 <bcotton> yeah, i can get on board with that 14:42:59 <bcotton> proposed #agreed 2049849 is accepted as a prioritized bug as it makes dual boot with some Windows installations more difficult 14:44:39 <bcotton> #agreed 2049849 is accepted as a prioritized bug as it makes dual boot with some Windows installations more difficult 14:44:58 <bcotton> #action mattdm to follow up with bootloader team on their plans 14:45:15 <bcotton> #topic Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards 14:45:15 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2113005 14:45:41 <bcotton> so this one is blocked on features being added to the upstream kernel, as i understand it 14:46:06 <bcotton> but also 14:46:10 <bcotton> #info This is an accepted F39 Beta Blocker 14:46:33 <bcotton> i'm not sure calling it prioritized adds any additional oomph that the blocker status doesn't 14:47:51 <bcotton> proposed #agreed 2113005 is rejected as a prioritized bug. It's already an accepted F39 Beta blocker, and that's a bigger hammer 14:50:08 <bcotton> well, since i seem to be the only one still here... 14:50:11 <bcotton> #agreed 2113005 is rejected as a prioritized bug. It's already an accepted F39 Beta blocker, and that's a bigger hammer 14:50:22 <bcotton> #topic Accepted bugs 14:50:22 <bcotton> #info 1 accepted bugs 14:50:22 <bcotton> #link https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=flagtypes.name&f2=OP&list_id=10871665&o1=substring&query_format=advanced&v1=fedora_prioritized_bug%2B 14:50:30 <bcotton> #topic It is possible to go through the initial setup without creating a root and without adding a user to the wheel group 14:50:30 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2015490 14:50:36 <bcotton> #info A fix to initial-setup is available, so now we need to re-enable the oz change 14:50:36 <bcotton> #link https://github.com/clalancette/oz/pull/307 14:50:46 <bcotton> this one is still making progress, so i don't think any follow-up is needed this time 14:50:53 <bcotton> #topic Bugs fixed since last meeting 14:50:53 <bcotton> #info This is to remind ourselves that the process works 14:50:58 <bcotton> #info Recent kernels cause problem with microphone LED on Thinkpad X1 Carbon gen. 9 14:50:58 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2134824 14:51:03 <bcotton> #info gtk3-3.24.35 broke double click to maximize in many apps (regression from gtk3-3.24.34) 14:51:03 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2149632 14:51:10 <bcotton> #topic Next meeting 14:51:11 <bcotton> #info We will meet again on 3 May at 1400 UTC in #fedora-meeting-1 14:51:19 <bcotton> #topic Open floor 14:51:21 <bcotton> anything else? 14:52:05 <amoloney> nothing from me, thank you for running this meeting! 14:52:11 <amoloney> bcotton++ 14:52:11 <zodbot> amoloney: Karma for bcotton changed to 7 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:52:25 <bcotton> okay, the end! 14:52:27 <bcotton> #endmeeting