19:01:54 <wilcal> #startmeeting 19:01:54 <Inigo_Montoya`> Meeting started Thu Apr 18 19:01:54 2019 UTC. The chair is wilcal. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:54 <Inigo_Montoya`> Useful Commands: #action #agreed #help #info #idea #link #topic. 19:02:04 <wilcal> welcom to another qa meeting 19:02:21 <wilcal> #topic Who's new? 19:02:27 <wilcal> Anyone new here today 19:03:00 <wilcal> No hands 19:03:07 <hviaene> If I suffer from amnesia, would that count? 19:03:13 <wilcal> So lets go to the heart of todays meeting 19:03:15 <wilcal> #topic M7 Beta 3, Status & Testing 19:03:23 <bri_an> it's in the wild now 19:03:39 <wilcal> Hi TJ 19:03:46 <bri_an> HI TJ - just started M7 beta 3 topic 19:03:49 <wilcal> So M7 is still pretty dynamic 19:03:51 <MageiaTJ> Hi. 19:04:01 <bri_an> yes 19:04:03 <wilcal> but only about 100 updates today 19:04:16 <wilcal> that's down from 300/day a week ago 19:04:29 <MageiaTJ> It will be for the next week or so, while the devs rush to beat version freeze. 19:04:39 <wilcal> discussion that we are headed for a freeze 19:04:57 <wilcal> release end of May so plenty of wiggle room 19:05:21 <wilcal> I think I settled the Vbox window size problem 19:05:31 <wilcal> and that was a big one for me 19:05:40 <bri_an> good - anything you can sure wilcal? 19:05:46 <bri_an> or Email 19:06:15 <wilcal> I've still a few criticals but it's become quite useful for me 19:06:44 <MageiaTJ> The vbox shared folder problem is still bothering me. 19:06:49 <bri_an> hi Tarazed 19:07:01 <wilcal> move the bug to release blocker? 19:07:06 <tarazed> Hi there - evening all 19:07:20 <MageiaTJ> I thought it was "fixed" but the latest update broke it again. 19:07:25 <wilcal> All of my Vbox clients have at least one share that needs to be loaded at boot 19:08:01 <wilcal> Is your test platform "fast" or "slow" 19:08:10 <bri_an> ditto - critical for me in testing 19:08:25 <wilcal> so move that to release blocker I think 19:08:42 <MageiaTJ> Mine seems fast... 19:09:22 <wilcal> #chair MageiaTJ 19:09:22 <Inigo_Montoya`> Current chairs: MageiaTJ wilcal 19:09:41 <wilcal> I've always thought that the share mount is a timing issue 19:09:58 <wilcal> ya kinda have to tune it for working with the most platforms 19:10:22 <MageiaTJ> As explained in the bug, nfs shares and vbox shared folders are not the same thing. 19:10:55 <bri_an> restarting the service fix it for you TJ? 19:11:02 <wilcal> So the shared folder is in the Vbox client? 19:11:25 <bri_an> vboxadd-timesync 19:11:32 <MageiaTJ> The foler resides on the host, and is shared with the client. 19:11:41 <MageiaTJ> foler=folder 19:12:36 <MageiaTJ> Brian, I had shared folders working with that command, but then after updating the guest additions it was broken. 19:13:27 <MageiaTJ> Now, there are two copies of the shared folder mounted, and the user can' 19:13:34 <MageiaTJ> t access either of them. 19:14:24 <MageiaTJ> It was late last night, and I have more investigation to do. 19:15:04 <wilcal> Shared folder on Host, is that host M6 or M7? 19:15:28 <MageiaTJ> Last night, M7. 19:15:43 <MageiaTJ> Haven't checked M6 yet. 19:16:00 <bri_an> it happened in both host versions for me. M6 and M7 19:16:31 <wilcal> My main system here is M6, it runs Vbox, and it runs M6 & M7 clients that mount a shared folder that is on the host 19:16:35 <MageiaTJ> Yes. I meant I haven't checked the new wrinkle on M6 yet. 19:16:36 <bri_an> it seemed to be more related to the client starting version. M6 was fine. Upgrade from M6 to M7 was fine. Fresh M7 - failed 19:17:11 <bri_an> but I stepped back when TJ and Chris took it on. 19:17:13 <wilcal> I've never run an M7 Client on a M7 host where the client mounts a folder on the host 19:17:42 <wilcal> I'm now in a situation here where I can try that 19:18:10 <MageiaTJ> The client mounts the folder in the client, but it resides on the host. 19:18:28 <bri_an> yes - I confirmed in all cases the client user-id was in vboxsf (nf) I can't remember group 19:20:29 <bri_an> MageiaTJ - correct and folder permission on that folder on the host has been confirmed as well. 19:20:58 <wilcal> could you post a link to the bug here for the record please 19:21:53 <MageiaTJ> bug 24141 19:21:56 <[mbot> Bug: ['Mageia 7 guests not auto-mounting shared folders in VirtualBox', 'NEW', 'Thomas Backlund'] https://bugs.mageia.org/show_bug.cgi?id=24141 19:21:56 <[mbot`> Bug: ['Mageia 7 guests not auto-mounting shared folders in VirtualBox', 'NEW', 'Thomas Backlund'] https://bugs.mageia.org/show_bug.cgi?id=24141 19:21:58 <[mbot> [ 24141 – Mageia 7 guests not auto-mounting shared folders in VirtualBox ] 19:21:58 <[mbot`> [ 24141 – Mageia 7 guests not auto-mounting shared folders in VirtualBox ] 19:22:03 <wilcal> thanks 19:22:54 <MageiaTJ> It's an extremely useful feature. 19:23:25 <wilcal> I'm still having problems with this 19:23:27 <wilcal> https://bugs.mageia.org/show_bug.cgi?id=24468 19:23:29 <[mbot> [ 24468 – M7 in a Vbox client, loses connection to keyboard ] 19:23:29 <[mbot`> [ 24468 – M7 in a Vbox client, loses connection to keyboard ] 19:23:41 <wilcal> mouse works keyboard does not 19:24:15 <MageiaTJ> wireless deskset? One receiver? 19:25:08 <MageiaTJ> I have one from logitech - no problems whatsoever, as long as the batteries are good. 19:25:17 <wilcal> Sorry yes it's a logitec wireless keyboard and mouse but the bug appears on wire keyboards 19:25:37 <wilcal> very ghosty 19:26:31 <wilcal> https://bugs.mageia.org/show_bug.cgi?id=24429 19:26:33 <[mbot> [ 24429 – The best resolution on a Vbox client I can get is 640x480 ] 19:26:33 <[mbot`> [ 24429 – The best resolution on a Vbox client I can get is 640x480 ] 19:26:38 <wilcal> may be fixed 19:27:00 <wilcal> actually will probably be a comment in the release notes 19:27:54 <wilcal> so we kinda wait for things to freeze 19:28:10 <wilcal> then work on the final critical bugs 19:28:57 <wilcal> Anyone done this: 19:28:58 <wilcal> #topic M6 -> M7 upgrade process 19:29:09 <dvg> yep 19:29:34 <tarazed> Yeah, I tried that the other day - no real problems 19:29:43 <dvg> Indeed 19:29:57 <MageiaTJ> Yes, in vbox. No really significant problems. 19:30:22 <MageiaTJ> One script failure - reported. 19:30:35 <wilcal> to M6 19:30:50 <wilcal> that's a difference from M5 to M6 19:31:02 <wilcal> remember all that KDE to Plasma 19:32:10 <MageiaTJ> Updating from M6.1 Xfce to M7 using the iso - mtink script failure. Didn't really affect me, as that's an Epson printer configuration tool. 19:33:17 <wilcal> I use a special tool when I upgrade from one version to the next. It's called: 19:33:18 <wilcal> https://www.killdisk.com 19:33:19 <[mbot> [ How to erase hard drive by Active@ KillDisk? Disk Eraser, Disk Wiper, Disk Format & Disk Sanitizer. ] 19:33:20 <[mbot`> [ How to erase hard drive by Active@ KillDisk? Disk Eraser, Disk Wiper, Disk Format & Disk Sanitizer. ] 19:35:15 <wilcal> Lets move on 19:35:16 <wilcal> #topic Testing Updates 19:35:20 <dvg> Yes I have one riseup pad question: Till now Classical Installer had sections after "Reboot..." like: *Plasma install *GNOME Install *Xfce Install etc., but I can hardly imagine that testers use the Classical Iso to install the whole Mageia with only one Desktop Manager and then again to test the next install. I for one never do: I select all Dekstops under the "Manual selection" and once done I try each one in turn to check they 19:35:20 <dvg> work satisfactorily. But the Riseup Pad suggests they are all different "Installs". Now I deleted the word "Install" for the 64 bits iso and left them for the 32 bit iso (which does not boot for me). My question is: do we need to keep the words "Install" with every subsection or do want them out... ? I will adjust pad and templates accordingly 19:36:18 <dvg> (End of beta3 subject....) 19:36:28 <tarazed> I think the pad is supposed to cover both interpretations - user will say if it is a multiple DE. 19:36:45 <wilcal> I've always installed multiple DE in one install. I use Plasma, Xfce & Mate 19:36:46 <dvg> Alright... 19:37:02 <dvg> So we keep calling it "...Install" ? 19:37:33 <tarazed> There was some discussion in the past where it was thought that separate installs guranteed no cross talk. 19:38:14 <wilcal> Wouldn't it be better to make sure that Mate does not disturb Plasma? 19:38:42 <dvg> Plasma can take care of itself I guess :))) 19:39:00 <tarazed> But sometimes one chooses to use a kde application in Mate. 19:39:16 <dvg> Of course 19:39:47 <wilcal> So we have a major critical app in updates_testing 19:39:48 <wilcal> https://bugs.mageia.org/show_bug.cgi?id=24683 19:39:50 <[mbot> [ 24683 – virtualbox new security issues CVE-2019-2574, CVE-2019-265[67], CVE-2019-267[89], CVE-2019-2680, CVE-2019-269[06], CVE-2019-2703, CVE-2019-272[1-3] ] 19:39:51 <[mbot`> [ 24683 – virtualbox new security issues CVE-2019-2574, CVE-2019-265[67], CVE-2019-267[89], CVE-2019-2680, CVE-2019-269[06], CVE-2019-2703, CVE-2019-272[1-3] ] 19:40:02 <dvg> Thanks 19:40:05 <wilcal> I've started that testing here today 19:40:19 <wilcal> I should be through it all tomorrow 19:41:14 <wilcal> The Java thing is make sure it installs without error unless your a Java expert 19:41:47 <wilcal> Oh!!! BTW...Bluegriffon has replaced komposer in M7 and it works just fine 19:41:53 <tarazed> Just did that one - it was confusing because the two bugs have some interdependencwe. 19:41:56 <hviaene> I'll do some more 32 bit testing tomorrow 19:42:02 <wilcal> thks 19:42:52 <wilcal> I have no 32-bit hw here anymore so any 32-bit testing here is in a Vbox client 19:43:28 <wilcal> Any other comments on updates testing 19:43:49 <hviaene> No 19:44:07 <bri_an> None 19:44:07 <tarazed> I think it would be premature to drop support for 32-bit testing. 19:44:37 <MageiaTJ> 32-bit testing on 64-bit hardware is OK. 19:45:03 <tarazed> OK 19:45:17 <hviaene> On M6? As long the laptop holds, I'll keep doing 19:45:21 <bri_an> good, because that's all I have. I do have 16bit machine lying around somewhere 19:45:37 <MageiaTJ> Trying to type too fast for my fingers bjt=bit. 19:46:08 <wilcal> no using a 32 bit platform as a Vbox host 19:46:29 <hviaene> I vaguely remember a case where real 32-bit HW was called for. 19:46:35 <MageiaTJ> Interesting. Appears I have something on my monitor that makes an "i" look like a "j." 19:46:35 <wilcal> Client ok but not host 19:47:27 <wilcal> Anything else on updates other then keep doing what you can do 19:47:44 <MageiaTJ> I believe Oracle says Vbox 6 doesn't support 32-bit hosts - yet we seem to have the 32-bit packages in testing. 19:47:45 <tarazed> No.... 19:47:55 <wilcal> so lets move on 19:47:57 <wilcal> #topic Anything else? 19:48:18 <wilcal> The NAB ( National Association of Broadcasters ) show here was huge. About 50,000 visiters to Sin City USA. 19:48:28 <hviaene> None here 19:48:45 <wilcal> Got to meet some really inside tech people in a couple off broadcasting companies 19:48:55 <tarazed> wilcal: no video this time? 19:49:14 <hviaene> Oh, yes 19:49:25 <wilcal> I needed every minute to cover some narrowly focused issues 19:49:51 <wilcal> not much video subjects from last year 19:50:05 <wilcal> Oh one thing 19:50:06 <hviaene> Has anyone experience in running an M$ Access application in emulation? 19:50:37 <wilcal> AWS ( Amazon Web Services ) wants it all. They want everything and they are agressive to get it all 19:50:39 <bri_an> hviaene - I haven't tried that 19:50:50 <bri_an> AWS - yes. 19:51:08 <bri_an> Did Google push their hosted Graphics Engines? 19:51:26 <wilcal> The new Disney+ channel is hosted in AWS 19:52:07 <bri_an> I think NetFlix is the same - pushed through AWS now 19:52:15 <wilcal> You saw my post to the QA mailing list that Intel still has yet to fix specter 19:52:26 <bri_an> yes - thanks for the update 19:52:43 <wilcal> Yes, Netflix and Hulu are admitting they are on AWS 19:52:59 <wilcal> anything else 19:53:12 <bri_an> not here - everyone have a good Easter 19:53:30 <wilcal> You all have a great Easter weekend 19:53:46 <tarazed> Sure thing. Happy Easter. 19:53:49 <wilcal> count down time 19:53:53 <wilcal> T-5 19:53:59 <wilcal> T-4 19:54:05 <wilcal> T-3 19:54:10 <wilcal> T-2 19:54:13 <wilcal> Bye all 19:54:17 <wilcal> T-1 19:54:21 <wilcal> #endmeeting