Crouton install failure - Keyring file not available #2387
Comments
|
I am able to reproduce this issue. Enter-chroot, edit-chroot seem to work; crouton is able to update itself and an instance of trusty; but crouton is not able to bootstrap sana, sid, or precise to built-in SSD or chroots dir on external device. The error is the same each time: |
|
Hi! Same issue here, any ideas how to resolve it? |
|
same here. worked fine for me yesterday, now I can't install any new chroots. I have tried with both trusty and precise. the error is always the same as those noted above. |
|
Same issue, I have installed several hours ago, but failed for this now... it was mentioned here for solutions to similar issue, don't know how it can be resolved for Crouton |
|
This problem will probably be resolved in due time (see e.g. #1868) :) |
|
dang... well i hope it gets fixed :/ |
|
anyone know a workaround which doesn't rely on braindead debian maintainers? I'm hoping we don't have to wait for them... |
|
Add me to the crowd. Just stated playing with crouton yesteday and was able to do a basic install. Today trying to learn more and insall with some variations but stuck on this issue. Don't know enough yet to try to find a workaround. |
|
https://github.com/hsoft/lxc/commit/f16fb156bb2ac6ff288900b8cc3b374d06fa80e8 and also this |
|
@Linux-Distros it's kernel dot org, two e's. and the website is working fine. I think the point is that they moved the gpg file location on that server. |
|
Same problem here. |
|
I have no internet connection besides my phone, so im not able to test the chroot please say something if it starts working again thanks! |
|
My Chromebook just came in today, which I've been looking forward to, especially installing Linux (yay!) and I am having this same issue. Sad day! |
|
I don't know how keyring files work, but this really is an issue out of our control right? My understanding is simply that the mirrors.kernel.org doesn't have the keyring file that says that the downloaded components are safe. I also don't know how useful this is, but, when I run curl mirrors.kernel.org/debianI get a 403 Moved Permanently. Obviously, this is resolved using the -L flag, so I get the right response with curl -L mirrors.kernel.org/debian |
|
i just tried the same thing without -L on the keyring file it shows that its there? its obviously just not fetching the file? maybe im wrong im a noob here so is it possible to wget that file then do finish install? update if this helps any? |
|
I got ubuntu-archieve-keyring,gpg file from http://mirrors.kernel.org/ubuntu/project/ and copy it /usr/local/chroots/precise/usr/share/keyrings/. Installing unmount-chroot into the host... Notice that Keyring file not available message is not shown but an error keeps happening |
|
one step forward then you run into another brick wall i guess lol |
|
@dpelluzi I think that to try this, you would have to place the keyring file not relative to the chroot, but into /usr/share/keyrings/ which is where it expects to be found. This doesn't work, however, as the filesystem is readonly and you can't create a /usr/share/keyrings directory even with sudo. Take a look here: https://www.chromium.org/chromium-os/poking-around-your-chrome-os-device |
|
@dem-waffles I think tht keyring file should not be in /usr/share/keyrings/ because crouton install script also can't write in this directory. |
|
I didn't have a good understanding of where the keyrings location was or what a chroot actually is - I'm starting to get that now. Sorry - you're right! I didn't realize that it creates an entire filesystem there and then does executions relative to that. |
|
See, I don't have a /usr/share/keyrings/ directory at all. |
|
I can't make one in the ChromeOS filesystem, as it is readonly for me. I can make one, however, in /mnt/stateful_partition/crouton/chroots/precise/usr/share/keyrings |
|
I'm to the point where I have manually placed the keyrings at http://mirrors.kernel.org/ubuntu/project/ into the /mnt/stateful_partition/crouton/chroots/precise/usr/share/keyrings directory, and I get the same output as @dpelluzi This is odd, because, it doesn't complain about not being able to find the keyring files anymore. Which is why I don't think that mounting the ChromeOS root filesystem as read-write is the right thing to do. |
|
i moved the file but still got I: Keyring file not available at /usr/share/keyrings/ubuntu-archive-keyring.gpg; switching to mirror https://mirrors.kernel.org/debian |
|
I did it as well, I can copy no problem buut if I try to access /usr/share/keyrings it says it's a file. I get the same error. |
|
Agreed. |
|
seems like an easy fix? maybe its not? who knows...untill then ill keep looking for a solution |
|
Have anyone found a solution?? |
|
tried like @dem-waffles, and am stuck just like he is. i do see this in my /var/log/messages (though I don't see much of any use, no other log files updated around time it failed): 2016-01-24T16:30:47.806271-05:00 INFO chrom[662]: --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=20.0.0.267-r1 --ppapi-flash-args=enable_hw_video_decode=1 --enable-fixed-position-compositing --enable-impl-side-painting --max-tiles-for-interest-area=512 --ui-enable-per-tile-painting --ui-prioritize-in-gpu-process --use-gl=egl --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --system-developer-mode --login-profile=user --has-chromeos-keyboard --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --enable-prefixed-encrypted-media --enterprise-enrollment-initial-modulus=14 --enterprise-enrollment-modulus-limit=18 --vmodule=screen_locker=1,webui_screen_locker=1,ui/display/chromeos=1,ash/display=1,ui/ozone=1,zygote=1,plugin=2 --login-manager --first-exec-after-boot: set rlimit success |
|
No, that's the pull request. This issue is still occuring, though, @drinkcat. |
|
so its still not working? darn it |
|
Yep |
|
@TheJoshCalibur and @masterpaper maybe if they reopen it you could go ahead and not contribute to spamming the shit out of the issue. |
|
yep tried again |
|
How do I use @drinkcat 's fix? Do I just reinstall crouton...? |
|
|
|
As far as I can tell, it isn't fixed @oninez |
|
i think it fixed |
|
i redownloaded crouton script (not sure it took a build or not, just did to be safe) and deleted my chroot. not sure that all was necessary, but it did the trick. thanks @drinkcat for the quick help. |
|
thanks @drinkcat |
|
@matyb : And again, exactly what I was going to post ,-) You need to wipe the installer cache (which is what your command does). Thanks! |
|
SO it works now AWesome im going to try it |
|
good job guys |
|
install waiting for the gibberish of code i dont understand to finish doing its thing |
|
👍 |
|
@drinkcat Can you explain to me how to fix it? |
|
yay but now i have to sleep |
|
@Syntechboy if I see from your other post, the installer left the files there |
|
Awesome, props for the quick fix |
|
@techdude154 Thanks, it seems to be working now |
|
so that means i can play cod from wine? |
|
@TheJoshCalibur maybe if you use steam's streaming from your rig, but good luck trying to play anything on integrated graphics lol |
|
IM so happy it worked!!! thx guys |
|
just incase someone out there is confused just do your regular download like you always do |
|
Locking this thread, because, um, wow. It is flattering to hear, though, that crouton is so critical that nobody knows what to do with themselves when it goes down for a day :) Anyway, thanks to @drinkcat for firefighting and giving everyone their livelihood back, and apologies again for the slow response. |
and others
Hi. Firstly, thanks to all the contributors for this amazing project! Yesterday, my chroots were installing and working beautifully (was trying out DEs). Today however, I can't install anything. I have powerwashed and re-enabled dev mode. I'm in the stable channel. I'm guessing that an external change has broken something within a script, but I can't claim to be knowledgeable enough to be sure.
Edit: I saw #2362 but honestly couldn't make sense of the proposed solution. Sorry if beating dead horse.
Output follows:
Not sure if the following is significant or not:
I also tried using
but this didn't help.
Another user reported same issue: https://www.reddit.com/r/Crouton/comments/42fch9/crouton_bug/
Thanks again
The text was updated successfully, but these errors were encountered: