REVISITING - More BTRFS fun Multibooting to subvolumes - FIXING GRUB

[steve7233]

I set up Grub as per oshunluvr, but the grub menu dose not appear.

40 custom

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'Kubuntu' {
   insmod part_gpt 
   insmod btrfs
   search --no-floppy --fs-uuid --set=root 27a9a212-d177-4665-b6bc-bf304e8c1f3e
   configfile /@Kubuntu1704/boot/grub/grub.cfg

[kubicle]

Does for me. To be sure I tried it out before I posted and copied it from the terminal. KDE Neon User Edition, fully updated

Nope, unless you have set some fancy aliases for that.

That command will start kate normally with two files, "sudoedit" and "/etc/grub.d/40_custom" ("kate" is the command to run, and "sudoedit" and "/etc/grub.d/40_custom" are interpreted as arguments for the kate command, and sudoedit doesn't work that way...compare to "EDITOR=kate sudoedit /etc/grub.d/40_custom" which first sets the environment variable $EDITOR [which tells sudoedit which editor you wish to use], then runs "sudoedit" as the command and "/etc/grub.d/40_custom" as the argument for the sudoedit command) .

Your command will of course "work" (in up-to-date Neon) in the sense that you can edit the file "/etc/grub.d/40_custom" and save it , since you don't need sudoedit (or any other root invocation) with up-to-date neon, but it will work exactly the same without the sudoedit part, that is just plain "kate /etc/grub.d/40_custom".

[GreyGeek]

...

Also, sudoedit doesn't work like that, "kate sudoedit /etc/grub.d/40_custom" will just open a kate window (as regular user) with two files, an empty new file called "sudoedit" and "/etc/grub.d/40_custom". One could use "EDITOR=kate sudoedit /etc/grub.d/40_custom", but like you said, this isn't really necessary with a relatively new versions of kf5 (ktexteditor) which will ask for password when needed.

Does for me. To be sure I tried it out before I posted and copied it from the terminal. KDE Neon User Edition, fully updated


Sent from my iPhone using Tapatalk

[kubicle]

How do I make custom_40 executable?

It should be executable by default, but if it's not you can make it so by running "sudo chmod +x /etc/grub.d/40_custom"

You also need to run "sudo update-grub" so that your custom_40 will be written in grub config.

NOTE: I haven't read the entire thread, just answering the last questions...so I'm just assuming you know what you're doing and have a valid reason for modifying grub.

[steve7233]

How do I make custom_40 executable?

[steve7233]

I tried to use kdesudo dolphin, to make 40_custom bootable. the properties program crashed! When I told it to report the crash, the crash reporter crashed!

[steve7233]

kubicle's, #1 way worked.

[steve7233]

I could not save the file. I guess greygeek wasn't entirely correct.

[steve7233]

Greygeek's, instructions appear to be working. I launched kparted to get the uuid of my btrfs, Iget the following error message.

Neither the configured ("pmlibpartedbackendplug") nor the default
{"pmlibpartedbackendplugin")
backend plugin could be loaded.

Please check your installation.

[kubicle]

if he is on Kubuntu-17.04 ,,,,he has a kate version that will edit root owned files just fine by it's self ,,,,,,,,when saving the file it will ask for his password .

Does 17.04 come with fresh enough kf5 (5.34), though? it was released with kde-apps 16.12 and kf5 5.31, but newer versions may be available through kubuntu ppas. (but kate 16.12 will also open as root normally, the change came with kate 17.04)

Also, sudoedit doesn't work like that, "kate sudoedit /etc/grub.d/40_custom" will just open a kate window (as regular user) with two files, an empty new file called "sudoedit" and "/etc/grub.d/40_custom". One could use "EDITOR=kate sudoedit /etc/grub.d/40_custom", but like you said, this isn't really necessary with a relatively new versions of kf5 (ktexteditor) which will ask for password when needed.

---

EDIT: To summarize (graphical editing as root)...just to clarify, kate version number is not the same as kubuntu version number:

1. The old way - kate version <17.04 (kate still runs as root)
Use: "kdesudo kate /etc/grub.d/40_custom" or "sudo -i /etc/grub.d/40_custom"

2. The intermediate way - kate >=17.04 (kate won't run as root), but kf5 [ktexteditor] not new enough <5.34 to support polkit file save.
Use: "EDITOR=kate sudoedit /etc/grub.d/40_custom"

3. The new way - new enough kf5 [ktexteditor] version >=5.34:
Use: "kate /etc/grub.d/40_custom" (no need to call root, KAuth/polkit will handle authentication when saving)

[vinnywright]

Use
kate sudoedit /etc/grub.d/40_custom
instead.

if he is on Kubuntu-17.04 ,,,,he has a kate version that will edit root owned files just fine by it's self ,,,,,,,,when saving the file it will ask for his password .

VINNY

[GreyGeek]

Use
kate sudoedit /etc/grub.d/40_custom
instead.

[steve7233]

I used sudo edit /etc/grub.d/40_custom to edit, but I can't enter anything after the period in the comments, where it says to enter the menu entery after the comment.

[oshunluvr]

I can boot into Lubuntu but not Kubuntu. I checked and the Kubuntu volumes are still there. I thought Kubuntu would come up first. I installed grub to sda5 so sda would still be Kubuntu. Isn't sda grub supposed to come up first?

I can't say what happened during install as I wasn't there, obviously, but it's easy enough to fix. When running Lubuntu, edit /etc/grub.d/40_custom and add Kubuntu in there using the process I describe in post #1, run update-grub, re-boot, select Kubuntu from the grub menu. Once you're back and running Kubuntu, run grub-install.

[steve7233]

I can boot into Lubuntu but not Kubuntu. I checked and the Kubuntu volumes are still there. I thought Kubuntu would come up first. I installed grub to sda5 so sda would still be Kubuntu. Isn't sda grub supposed to come up first?