Archived thread 2356719 from Forum Members Chat. Markdown source: Forum_Members_Chat/thread_2356719_Unable_to_add_new_page_on_Community_Help_Wiki.md
I've created my new Help page in my sandbox and tested it thoroughly, and now I'm ready to add it to the Community Help Wiki.
https://help.ubuntu.com/community
This is something that I've done before, but interestingly I don't have the authorisation to edit my old pages :(
Anyway, trying to create a new page on the Community Help Wiki gives me the message, "You are not allowed to edit this page."
Please help.
Only the Ubuntu Community Help Wiki Editors team have have editorial rights on the Ubuntu Community Help Wiki at https://help.ubuntu.com/community. See https://wiki.ubuntu.com/DocumentationTeam/Organization for more details.
If you want, I can help you add the page for you. Just PM me with its content.
slickymaster said: Only the Ubuntu Community Help Wiki Editors team have have editorial rights on the Ubuntu Community Help Wiki at https://help.ubuntu.com/community. See https://wiki.ubuntu.com/DocumentationTeam/Organization for more details.
If you want, I can help you add the page for you. Just PM me with its content. Thanks, I'll PM you.
It will be a hassle when I want to amend it, though. Once it's up, I'm sure that the odd bug will surface, as well as the occasional workaround for certain situations.
Ok Paddy, all done. Please check them all to make sure everything is as you want.
https://help.ubuntu.com/community/ManualFullSystemEncryption/
Very nice work Paddy, congrats.
howefield said: Very nice work Paddy, congrats.
Indeed it is, very thorough but objective.
Thanks for this great wiki page :-)
slickymaster said: Ok Paddy, all done.
David, thank you so much for taking the time to do this.
It looks all correctly done.
I have noticed one oddity, which would be something to do (I imagine) the setting up of the Moinmoin. The system has converted all of my bullet points to numbered points! I know that you haven't changed the text, because the Raw Text shows that they are identical.
For example, compare the following two areas:
Anyway, now I can call for testers.
Thank you all for your positive comments!
Paddy Landau said: David, thank you so much for taking the time to do this.
It looks all correctly done.
I have noticed one oddity, which would be something to do (I imagine) the setting up of the Moinmoin. The system has converted all of my bullet points to numbered points! I know that you haven't changed the text, because the Raw Text shows that they are identical.
For example, compare the following two areas:
Anyway, now I can call for testers.
Thank you all for your positive comments!
I also noticed that. I believe that for some reason, which I haven't yet figured out, the pragma isn't being enforced.
The only changes I made was to add code tags in a few command lines that you probably forget to.
slickymaster said: The only changes I made was to add code tags in a few command lines that you probably forget to.
Oh! I didn't realise! I'll go through and correct my backup. Thanks for correcting them.
Paddy that is awesome work and it will be very helpful to people wanting to use encryption.:)
Thank you, wildmanne39.
slickymaster said: The only changes I made was to add code tags in a few command lines that you probably forget to.
I realise what happened. I have been adding four spaces before the lines in order to turn them into code, which does work, but your method highlights it better. :)
I notice that you are switching between relative and absolute path for example at
sudo rm --force etc/crypttabPress Alt+F2. In the prompt, enter this command (you can copy from here and paste in the prompt with Ctrl+V).
sudo -H gedit /mnt/root/etc/crypttabIf it is by intention (because you are switching between normal and chroot mode), please explain that you are switching and why. Otherwise I suggest that you use relative or absolute path all the time.
sudodus said: I notice that you are switching between relative and absolute path…
If it is by intention (because you are switching between normal and chroot mode), please explain that you are switching and why. Otherwise I suggest that you use relative or absolute path all the time. There is a specific reason. I can explain why, but I can't edit the page. Shall I edit my own page and then you can copy it over?
Also, I think that the Community Installation page might benefit from a reference to these instructions. What do you think?
Paddy Landau said: There is a specific reason. I can explain why, but I can't edit the page. Shall I edit my own page and then you can copy it over?
Paddy, poke me whenever you have any corrections and/or edits you need done and I'll take care of it.
I've taken your suggestion to change everything to absolute, as this is safer.
The pages are:
Unfortunately, I have to change the image for the last page because it is now inconsistent. It will take me a while to work through the whole thing again; I'll let you know once the image is updated.
Thank you yet again for your time and effort.
Paddy Landau said: I've taken your suggestion to change everything to absolute, as this is safer.
The pages are:
Unfortunately, I have to change the image for the last page because it is now inconsistent. It will take me a while to work through the whole thing again; I'll let you know once the image is updated.
Thank you yet again for your time and effort.
Sure, no problem.
As soon as you have the image updated I'll do the changes.
Impressive action! I was away from keyboard for a while and you are already fixing it together with slickymaster :-)
sudodus said: Impressive action! I was away from keyboard for a while and you are already fixing it together with slickymaster :-)
Ha ha!
I see that I've been given permission to edit. So, I'll edit the pages and then let you know for quality-assurance.
I have made the changes, including the screen-shot, to the two pages. Please feel free to check them. Thank you.
It *looks* good. I should try to use it and create system according to your instructions too, but there is no time for it tonight.
sudodus said: It *looks* good. I should try to use it and create system according to your instructions too, but there is no time for it tonight.
Cool. Let me know how it goes, if you get time.
I tried to follew the tutorial (with a data partition but without the paranoid tricks. All partitions (EFI, system and data) are in one SSD connected via USB).
One step failed for me:
In 'Allow Ubuntu to boot' ``` mv Boot Boot-backup
I might have done something wrong in an earlier step, but cannot identify it.
After finishing I tried to boot. The system booted, I entered one passphrase, had the plymouth screen with dots, and arrived at Busybox and the 'initramfs' prompt. So I failed to make a working system.
Can you suggest what to fix, or is the only advice to try from the beginning again?Thank you for the feedback, sudodus.
sudodus said: In 'Allow Ubuntu to boot' ```
mv Boot Boot-backup
On some systems, that will fail; it's not a problem if it does. The instructions for that step say, "The second line may generate an error message, which you can safely ignore." Perhaps that was easy to miss? I have [highlighted the line]("https://help.ubuntu.com/community/ManualFullSystemEncryption/DetailedProcessSetUpBoot#Allow_Ubuntu_to_boot") so that it's easy to spot.
> **sudodus said:**
> The system booted, I entered one passphrase, had the plymouth screen with dots, and arrived at Busybox and the 'initramfs' prompt. So I failed to make a working system.
Have you tried the [Troubleshooting section for initrafms]("https://help.ubuntu.com/community/ManualFullSystemEncryption/Troubleshooting#Boot_goes_to_initramfs")? Let me know if that works. If it doesn't, we'll try to diagnose and fix it.
I appreciate your time with this.OK, I will use the troubleshooting tips.
I think I found a step that you forgot:
The UUID in fstab should match that of the actual EFI partition. I should have seen it, but overlooked it when you did not mention it. I fixed it in one of the steps for the relevant case 'Boot goes to initramfs'.
My attempts to fix the system actually borked it, so now it does not boot at all. I think the best option is to start all over (but it will be another day).
-o-
It would be nice, if you could wrap all these steps into a shellscript. Maybe I am not the only 'sloppy user', who gets lost at some of the hundred command lines ;-)
sudodus said: The UUID in fstab should match that of the actual EFI partition.
You've found a bug! In my system, the UUID was correctly set by the installer.
I'll adjust the instructions to check for it.
EDIT: I have fixed the instructions.
sudodus said: My attempts to fix the system actually borked it…
Sorry. If the only file that you changed was [FONT=lucida console]/etc/fstab[/FONT], it should be fairly easy to repair. If you changed anything else, it will be more complicated.
sudodus said: It would be nice, if you could wrap all these steps into a shellscript.
Yes, agreed, but that is beyond my available time. There are too many variables to have to check for; it would be a mammoth task. If I had the time, or if I were to be paid for it, I would consider it :)
I've got a question about editing wiki pages, it seems I have no problem editing any page, but others like Paddy don't seem to have the access needed. Does it have something to do with the length of time I've been an Ubuntu Member, or is there something else going on. When I applied for membership in the Wiki editors group, I was told I didn't need it as I was an Ubuntu member, even though I was granted membership in the team.
To be able to edit community wiki's you have to be a member of this team: https://launchpad.net/~ubuntu-wiki-editors
You apply for membership, we are not automatically in that group because of Ubuntu Membership, but paddy can edit community wiki's now because his membership to the wiki team has been approved.
My experience,was exactly like cariboo's. Starting during the spam fiasco I couldn't edit, asked to be in wiki editors, was told I didn't need to be because I was a Member, was added anyway and then I was able to edit again.
I'm getting the feeling that the real deal is this: You have to be a member of the editors team. To be a member of that team, Ubuntu Membership is a qualifying credential. However, inclusion in the team does not happen automatically on being granted Ubuntu Membership.
One hand not talking to the other or something like that ...
Paddy Landau said: You've found a bug! In my system, the UUID was correctly set by the installer.
I'll adjust the instructions to check for it.
EDIT: I have fixed the instructions.
Sorry. If the only file that you changed was [FONT=lucida console]/etc/fstab[/FONT], it should be fairly easy to repair. If you changed anything else, it will be more complicated.
Yes, agreed, but that is beyond my available time. There are too many variables to have to check for; it would be a mammoth task. If I had the time, or if I were to be paid for it, I would consider it :)
I think we are all affected by lack of time to do everything we would like to do. We have to live with it, and try to do the most important things (not only computer stuff) :-)
I hope there will be time during this weekend to make another try. But isotesting of Zesty Zapus will probably need testing too.
sudodus said: … isotesting of Zesty Zapus will probably need testing too.
I shall do this, and report back here.
BTW, am I the only one who finds the names confusing? I had to look up zesty to find out which version it is (17.04).
sudodus said: The UUID in fstab should match that of the actual EFI partition.
I have been testing quite a lot, and I am flummoxed as to how your UUID for the ESP was incorrect. The only thing that I can think of is that you missed out a single step: notify the installer of the ESP partition.
sudodus said: But isotesting of Zesty Zapus will probably need testing too.
I have now tested 16.04, 16.10 and 17.04 beta. If I have time, I shall also test Lubuntu and other flavours.
Hi Paddy,
I am sorry that I have not been able to continue the testing, and that I will not be able to do so, at least not in the near future. I hope *someone else can chip in* and test your wiki page.
sudodus said: I am sorry that I have not been able to continue the testing, and that I will not be able to do so, at least not in the near future. I hope *someone else can chip in* and test your wiki page.
No problem, and thanks for what you've already done!