| arraybolt3[m] | Can someone who has the ability to legally install WIndows 10 or 11 try to do a Lubuntu installation alongside Windows? I see someone having problems with that on Discourse and I've noticed that os-prober isn't trying to detect other operating systems on my system, so I'm wondering if maybe the os-prober problem that was fixed early on in the 22.04 cycle has resurfaced. | 00:05 |
|---|---|---|
| arraybolt3[m] | (I'd do it myself but I don't own any Windows 10 licenses or hardware with a Windows 10 license.) | 00:07 |
| arraybolt3[m] | (Also things have calmed down in $PERSONAL_LIFE so I should be back.) | 00:09 |
| kc2bez[m] | I could probably do it in a VM tomorrow. I am not wanting Windows on any of my bare metal hardware though. | 00:11 |
| arraybolt3[m] | Yeah me neither. | 00:11 |
| arraybolt3[m] | I should probably buy a license at some point in the future so I can do testing, but I don't ever want any version of Windows to touch my bare-metal hardware again. Blech. | 00:12 |
| kc2bez[m] | Technically you can install it you just can't activate it. | 00:12 |
| guiverc | arraybolt3[m], lubuntu kinetic (22.10)? | 00:12 |
| tsimonq2 | Here's the thing about that... | 00:13 |
| tsimonq2 | That's on purpose | 00:13 |
| arraybolt3[m] | guiverc: Nope, Jammy. | 00:13 |
| tsimonq2 | I think juliank sent an email to the ML? | 00:13 |
| tsimonq2 | Basically, we need to enable Calamares to run it once in the installer with a disclaimer | 00:13 |
| tsimonq2 | They discovered a new attack vector in GRUB which allows sideloading of malicious code onto the partition that contains GRUB | 00:14 |
| guiverc | give me a little; I'll boot jammy (daily at most a few days old; SRU testing) and see if it detects a w10 I think I have on samsung thing | 00:14 |
| tsimonq2 | I work around this on my local system by explicitly defining a config variable in GRUB | 00:14 |
| tsimonq2 | But unfortunately this one isn't a bug... it's by design, and we know the situation isn't ideal right now | 00:14 |
| tsimonq2 | If anyone has the chance to find the mailing list archives associated with this issue I'd appreciate it, probably either ubuntu-release or ubuntu-devel. Otherwise I'll likely look tomorrow | 00:15 |
| arraybolt3[m] | Simon Quigley: I thought that it was purposefully disabled in GRUB and that Ubuntu purposefully enabled it again. | 00:15 |
| tsimonq2 | I'd appreciate some context on the latter, if you could | 00:15 |
| arraybolt3[m] | Simon Quigley: Context about the re-enabling of it? | 00:16 |
| tsimonq2 | Correct, pretty please :) | 00:16 |
| arraybolt3[m] | Simon Quigley: I actually don't know, I believe guiverc told me that it was behaving the current, secure but bad way early on in the Jammy cycle and then later on it started auto-detecting things right again. I may have misunderstood. | 00:17 |
| tsimonq2 | I know you can re-enable it, and I do simply for my own use | 00:18 |
| tsimonq2 | I'm not sure about the decision that was reached | 00:18 |
| kc2bez[m] | I am subscribed to -devel and I can't find it. It must be -release. | 00:18 |
| arraybolt3[m] | One moment... | 00:19 |
| arraybolt3[m] | I can't find it in -release either. | 00:19 |
| tsimonq2 | No rush, I need to get back to $sidejob (in spite of current circumstances) so I'll catch you guys a bit later/here and there | 00:19 |
| arraybolt3[m] | Searched from October 2021 to April 2022. | 00:19 |
| kc2bez[m] | Hmm | 00:20 |
| tsimonq2 | But I do remember seeing something about this... | 00:20 |
| tsimonq2 | Maybe it was on debian-devel? | 00:20 |
| tsimonq2 | If you guys can't find it I can search debian-private too... | 00:20 |
| tsimonq2 | I know I saw an email about this though. | 00:20 |
| guiverc | arraybolt3[m], booting recent daily of jammy (SRU'd calamares from proposed) detects the windows 10 install (original OEM install though was factory reset prior to be given to me) on `samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000)` | 00:20 |
| kc2bez[m] | I believe you my search wasn't too exhaustive | 00:20 |
| tsimonq2 | No worries. Take care :) | 00:21 |
| arraybolt3[m] | guiverc: OK. I meant that when you install alongside W10 it doesn't detect it and put it in the boot menu. Though you probably don't want to risk nuking that system. | 00:21 |
| kc2bez[m] | It would have included debian-develop though too. I can look more tomorrow after some time spent horizontal. | 00:22 |
| kc2bez[m] | s/develop/devel/ | 00:22 |
| arraybolt3[m] | December 2021 on ubuntu-devel, found it. | 00:23 |
| arraybolt3[m] | Hey look: https://lists.ubuntu.com/archives/ubuntu-devel/2021-December/041769.html | 00:23 |
| guiverc | not really; so you mean update-grub isn't detecting it... My system has jammy installed & w10 is detected (never really select it though; last time was just to prove to someone I did have a windows but not knowing password I couldn't login) | 00:23 |
| kc2bez[m] | Ah, I didn't go far enough back. | 00:23 |
| guiverc | update-grub on my install detects & offers the w10... My w10 has fastboot off & hibernate disabled | 00:23 |
| arraybolt3[m] | guiverc: Hmm. Any chance you can show the contents of /etc/default/grub? | 00:24 |
| guiverc | arraybolt3[m], from installed system? (I'm on live currently; only looked what calamares offered)... I can reboot & provide what is installed if helpful | 00:24 |
| arraybolt3[m] | Yeah, from the installed system. Just to see if maybe OS-PROBER was manually reenabled or something. | 00:25 |
| guiverc | arraybolt3[m], https://pastebin.ubuntu.com/p/7ZKPKzcsnm/ | 00:28 |
| arraybolt3[m] | guiverc: Hmm, thanks, and that's weird. I wonder what makes GRUB decide when to use the prober and when not to. | 00:30 |
| guiverc | yeah I recall issues early in the cycle (tracking doc is where I'd look for clues), but they were resolved & I ignored it as I tested all releases with a winXP (my d755-5 has a copy still) but rarely on that samsung (w10)... I commonly test with other GNU/Linuxes (which suffered same issue with prober when it impacted jammy) | 00:35 |
| * guiverc rebooted samsung & selected checked grub (if windows didn't show, I'd likely not notice!) & yep 'windows boot manager' is there & when selected got to w10 greeter... rebooted again at that point | 00:37 | |
| Roberalz[m] | <arraybolt3[m]> "Yeah, from the installed system...." <- edit /etc/default/grub and add the line GRUB_DISABLE_OS_PROBER=false | 00:51 |
| Roberalz[m] | You try that? | 00:52 |
| Roberalz[m] | With a update-grub2 | 00:53 |
| arraybolt3[m] | Roberalz: I know that doing that will fix the problem, but my issue is with whether the problem exists at all by default. Also, my laptop only has one OS installed, I just notice that it tells me that os-prober isn't being used. I don't need it, but others who dual-boot do. | 00:53 |
| arraybolt3[m] | (Well, OK, only one host OS installed, I have an entire zoo of VMs but that's different.) | 00:53 |
| Roberalz[m] | <arraybolt3[m]> "Roberalz: I know that doing that..." <- It has been disabled by default | 00:58 |
| Roberalz[m] | https://askubuntu.com/questions/1414245/why-do-i-get-warning-os-prober-will-not-be-executed-to-detect-other-bootable-p | 01:00 |
| arraybolt3[m] | Yeah. I thought they changed their minds but I guess not. | 01:00 |
| Roberalz[m] | A script call has been added as posted on askubuntu. | 01:02 |
| tsimonq2 | <arraybolt3[m]> "Hey look: https://lists.ubuntu...." <- YES that's the one | 01:26 |
| Roberalz[m] | <tsimonq2> "YES that's the one" <- Thanks for the info | 01:35 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!