-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Method http has died unexpectedly during software installation #2688
Comments
Same with sudo apt-get install mono-complete |
It seems, it also happens in the Chrome OS shell. Just tried to install x2goclient: (segmentation fault) |
Same issue on Acer R11 I was able to install a few packages normally from a terminal in xfce before this issue kicked in, since then it has remained. As said above no issue in Chrome OS shell from a chroot |
latest update fixed this issue for me Version 53.0.2785.47 beta (64-bit) |
This just started happening to me as well. On my acer chromebook R11. I installed crouton with -t xfce,xorg,chrome,xiwi and everything was fine at first. I installed some software no problem then suddenly this started happening seemingly out of nowhere. Version 53.0.2785.70 beta (64-bit) |
I got it working again, but I am not sure why it works. Here is what I did: Went to http://packages.ubuntu.com/trusty/amd64/apt/download For some reason 1.0.1ubuntu2.14 seems to be broken. |
Hmm, even stranger. The issue came back after I unmounted and remounted my chroot. Reinstalling apt fixed it again. It seems that apt is somehow being corrupted. |
after the last Chrome update when I run crouton -u I'm seeing this error E: Method https has died unexpectedly! ending up with if I try to enter-chroot I get A chroot setup script still exists inside the chroot. If I choose n or d .. I can enter the chroot and run apt-get update or upgrade fine without any errors |
Update - seems to have been an issue with that particular chroot. I've created a new one which works fine. I've now realised the value of backing them up.. |
Issue has returned again for me after doing a crouton update |
I have had similar errors, also on a Chromebook R11, but with beta channel Chrome v53.0.2785.129. The problem comes and goes, eg if I exit and then restart the chroot the problem often goes away (but so far it always comes back later). |
Just so I might get some responses without everyone having to read this enormous post:
Anyway, on to the issue: Same issues here on Trusty. I installed Precise a while ago with no issues (that I recall, but I wasn’t paying much attention so I can’t say for certain), and used it for a few weeks, but I ended up powerwashing. I did a Trusty install pretty much immediately after that, probably early this month. I don't remember how the initial install went (that night was... hazy...), but there were issues with apt-get right from the beginning, regardless of whether I was using the xfce desktop with xorg, running xterm/other applications in a window with xiwi, or if I was just using the chrome developer shell and enter-chroot'ing. Earlier today, I turned on OS verification, wiping the device, then turned on Developer Mode and did the process of installing Trusty over again (I thought maybe since I had left Developer Mode on when I powerwashed the first time, maybe there was some variable that I wasn't controlling for by leaving it on... I wanted it to be in the same from-the-manufacturer state as when I did my first install, Precise, so that maybe it would work better. Spoilers: it didn't work). The install failed very late, with the same http segmentation fault. It occurred after installing all of the packages associated with the Just to eliminate confusion… I have had three Ubuntu chroots using crouton:
Essentially, this is a comprehensive description of the http/https segfault issue I found while I was on install #2, and the steps/variations taken to trigger them: Chromebook info: Acer R11, 2GB RAM Version 53.0.2785.129 (64-bit) Description of different steps taken to trigger the issues: Method A: as controlled a method as possible
...phase of the apt-get process. Sometimes, but not often, it would fail immediately after the...
...phase of the apt-get process. Either way, it would throw this message:
Or, it would throw the same message, but “ Method B: second-most controlled method
Method C: using a bunch of memory in the chroot
Method D: using a bunch of memory in ChromeOS
Method E: normal use
General observations and fix attempts:
So, that’s pretty much it, I think, at least for install #2. Now for my Trusty install from this morning, or install #3:
...and that’s where I’m at now. You can view the whole installation output here: https://gist.github.com/kjleitz/b140b5845a589f3c3684510b9fb879a6 There are some lines which read:
...or Anyway, I think this is happening to quite a few people, and I’m sure their experiences are similar to mine, especially since I keep seeing the Acer R11 Chromebook mentioned. The issue does not seem to actually go away when you downgrade or reinstall apt (as evidenced by #2688 (comment) ) or by making a new chroot/updating the chroot (as in #2688 (comment) ) and it seems to be the same issue as in some other reports/threads (like: #2778 and possibly #2570 although I haven’t actually tried that solution, I only just found it). SO ANYWAY. Sorry for the enormous wall of text. But that’s my experience. It doesn’t look like anyone has made any headway here and it’s a real pain in the ass, having to restart the chromebook so often, and sometimes (not often, luckily) losing data when it all comes crashing down. Wish I could do something about it, but it’s not exactly my area of expertise, I wouldn’t know the first place to look, or the first thing to do, even if I knew what the issue was. Hope this is helpful. |
Update: Restarted to start with a clean slate, ctrl+alt+t, Told me the chroot hadn't been completed, yada yada. Pressed ran
Not sure what this new error is, or whether it means the same thing. |
I'm on the beta channel on an R11 with 4MB RAM (it's a German model, I couldn't find a 4MB model in the UK) with trusty. The issue comes and goes. I can't figure out a pattern. If I restart it disappears. Sometimes it disappears for some time, but then annoyingly reappears seemingly at random. I don't remember ever seeing this issue before google play and android apps appeared. |
Did you have an error-free trusty install before google play and android apps were available on the beta channel? Because, while it may very well have something to do with it, I wouldn't want to conflate the two by coincidence. We'd need to see a working trusty install before the play store was made available and an error-prone install afterward, to make that case. |
Hm. So, in the last failure I posted, #2688 (comment), I received this error:
instead of the usual
A Another possibility could be that pieces of the executable code are being overwritten in memory with some other mess of data, or that a function pointer in the program points to similar unintelligible data. Disclaimer: I literally know next to nothing about this stuff, and I mostly just read about it for a couple hours this morning, so I might be totally wrong. If the first case is true, and the sub-process If the second case is true, and since there's a decent amount of evidence it's related to memory usage, maybe some RAM is being overwritten when So maybe at high memory usage, zram unknowingly swaps some memory at addresses that the I will try, at some point, to disable swap and see if that helps, and also try recompiling the apt-get binaries (not sure how to do this, but I'm sure I can figure that out) to see if that will work. Again, disclaimer, I don't know if what I'm saying makes sense. I'm a chemist, not a computer scientist. I'm sure as hell not a C programmer, and the extent of my knowledge on operating systems reaches only to the Wikipedia pages, Stack Overflow questions, and various forums that I come across when following a Wild Google Chase. Does anyone have a better understanding of this? |
@kjleitz I did have an error free trusty install before google play appeared. When google play appeared the main issue I had was with google play and any android apps stopping repeatedly whenever I entered the chroot. That issue was resolved. I can't remember clearly when this issue started appearing, but I didn't see it before google play appeared. It is intermittent for me - for example I just accepted a chrome update and followed with a crouton update - the crouton update didn't complete, ending with this issue in an error message.
I ran the crouton update a second time and it completed without any errors. |
I have an Acer R11 4 GB. For me, this issue appeared first BEFORE Google Play was available. And it only happened with Trusty, not with Precise. |
I have an Acer R11 4GB with the N3060 dual-core Celeron. Same issues as being discussed. I've not seemed to have any problems doing the installs for 14.04 or 16.04, it is only when running |
It was driving me crazy, really random issue for me. @fignuts solution earlier in this issue worked well for me, very happy! |
Can't get past this issue since the latest Chrome update Installing target core... |
Tried @fignuts workaround above but no difference. Unable to run crouton update at all. |
Strangely I can run sudo apt-get update and upgrade no problem in an xfce terminal window in a crouton session. But unable to run crouton update |
After a day of failing, crouton update ran without an issue. I really have no idea what this issue is correlated with |
Can't reproduce locally... apt version 1.0.1ubuntu2.14. |
@drinkcat Are you using an Acer R11, with a Trusty chroot? Try opening enough tabs (in ChromeOS) to register >75% memory usage while you are logged into your chroot. Then, in your chroot, try running |
I gave up with workarounds. I just rerun the update script over and over again until it completes. This last time it took 5 tries, but it usually takes 3 or 4. It doesn't take that much time and the only annoying thing is that I have to enter the encryption password each time. |
I got a similar error (Method http has died unexpectedly) and fixed it by changing the EDIT: It worked for only one install, after that continued to return the same error :( |
Any news on this bug ? I'm under trusty. |
+1, same problem here with latest Chrome OS and latest ubuntu LTS. That's quite unrewarding. Any progress by anybody? |
It is a very annoying bug. I'm not prepared to use an unencrypted chroot. Only workaround that works temporarily for me is to re-install apt with dpkg each time I want to run crouton update |
I think the bug only exists on chroots that are converted to encrypted after the initial install. I had a fresh install of Debian wiith encryption enabled during install that I had no issues with. |
Nope. Fresh install, directly encrypted. |
Thanks for confirming. I guess it's just Ubuntu then. |
I've only installed Ubuntu but have had the same bug on fresh encrypted installations. Sometimes a fresh install has meant the bug didn't appear for a few days but for me it has always re-appeared. |
This bug is the reason I do not run crouton on my C302. I'd be grateful to anyone who took the time to dive in and understand what is causing this! |
Just installed Ubuntu-Unity on a Samsung Chromebook and some things worked for a while but I was only able to get one or two things, I did update-upgrade etc and immediately it stopped working with the Signal 4 error. If the problem persist I might just try Power washing the Entire Chromebook and starting from scratch. I just read this whole thread and I guess it is safe to assume no reliable fix has been found yet? |
Power washing will do nothing for this. You can delete the chroot and reinstall if you want, but the outcome will be the same if you choose Ubuntu - which is unsupported. If you want/require encryption choose Debian - it's basically the same but is supported and works with encryption. Also, you do not want a 3D desktop like Unity / KDE / Gnome 3 - as they rely on 3D acceleration which doesn't work in a chroot - it will use software 3D which is slow. Use a 2D window manager like XFCE / LXDE. |
I have the same issue on the latest chrome os with Debian just as with Ubuntu. And the chroots weren't converted. I installed a new second Debian which works for now but this bug has fooled me in the past too often to believe it's just gone, pretty sure this install will also see this bug quite soon.
… On 27.05.2019, at 05:02, Scott Edlund ***@***.***> wrote:
. If the problem persist I might just try Power washing the Entire Chromebook and starting from scratch. I just read this whole thread and I guess it is safe to assume no reliable fix has been found yet?
Power washing will do nothing for this. You can delete the chroot and reinstall if you want, but the outcome will be the same if you choose Ubuntu - which is unsupported.
If you want/require encryption choose Debian - it's basically the same but is supported and works with encryption. Also, you do not want a 3D desktop like Unity / KDE / Gnome 3 - as they rely on 3D acceleration which doesn't work in a chroot - it will use software 3D which is slow. Use a 2D window manager like XFCE / LXDE.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi, I just reinstalled a new chroot using this information that I just found ( I'm an idiot. ): #4026. I no longer have the segmentation/sig 4 problem when I enter-chroot. I can update and install packages with no problems. But when I actually startxfce4 and enter the DE, nothing works. Ever. It used to work if I kept trying. Now it just quits. I'm using an Acer 14, CB3-431 with 4GB and 32GB. Does anyone have any ideas or fixes? Is anyone still checking here? Thanks, Rich |
@sedlund I'm running into this same issue, but I was trying to parse the "unsupported" part of your comment. Is that a "Not supported yet by crouton", "not supported by crouton as a design decision", or "not supported by ubuntu"? Should I put in a PR to update the docs about it? |
@WithoutAnAce Yes - ' Not supported by crouton' I don't know the back story, I assume the main developer was only interested in making the latest Debian work and left the rest to the community to support. The supported releases are listed in the help to the crouton command when you list available releases. You can check which are supported: https://github.com/dnschneid/crouton/wiki/Crouton-Command-Cheat-Sheet
For Ubuntu only trusty and xenial are 'supported' - whatever that means. They are over 8 and 4 years old - respectively - compared to all of the latest and current releases supported for Debian. |
That makes sense. I'm currently using Xenial, but still running into the
issue (for the purposes of more information about this bug)
…On Fri, Jul 12, 2019 at 2:25 PM Scott Edlund ***@***.***> wrote:
@WithoutAnAce <https://github.com/WithoutAnAce> Yes - ' Not supported by
crouton' I don't know the back story, I assume the main developer was only
interested in making the latest Debian work and left the rest to the
community to support. The supported releases are listed in the help to the
crouton command when you list available releases.
You can check which are supported:
https://github.com/dnschneid/crouton/wiki/Crouton-Command-Cheat-Sheet
- List supported Linux releases (-r): sh ~/Downloads/crouton -r list
For Ubuntu only trusty and xenial are 'supported' - whatever that means.
They are over 8 and 4 years old - respectively - compared to all of the
latest and current releases supported for Debian.
https://github.com/dnschneid/crouton/blob/174af0ebd89941a6ed6254f453d5f0c4758eae49/installer/ubuntu/releases
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2688?email_source=notifications&email_token=AH3QC2FTP33RZF6SGCN2IEDP7DLDDA5CNFSM4CJX52IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ2VB3I#issuecomment-511004909>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH3QC2AK4EE4OQHQK2VVQ5TP7DLDDANCNFSM4CJX52IA>
.
|
Hi, guys. I deleted my Xenial cheroot and was running Debian Stretch happily for a while. I wanted to install Atom and followed these instructions: https://flight-manual.atom.io/getting-started/sections/installing-atom/#platform-linux THIS COMMAND is the one that brought that happiness to a screeching and bloody halt: Something about fooling with sources.list.d screws everything up. I immediately threw a seg fault when updating. I added the repository to my /etc/apt/sources.list and updated just fine ( after logging out of the cheroot and restarting my Chromebook ). THE PROBLEM HAS SOMETHING TO DO WITH sources.list.d. Does that make any sense? |
Wanted to share my workaround, along with a minor discovery, in the hope of being helpful. :) I keep a pristine copy of the
Whenever I run into the issue, I just run this script, and I have a working system again, along with a copy of the damaged I have now collected 9 such damaged binaries. Today, I was curious to compare them, and I noticed that two of them were identical:
As you can see, the versions from April 5th and June 12th share the same checksum - which at least demonstrates that the corruption is not entirely random. If this issue starts bugging me enough, I might start running a watchdog process to continuously (maybe once per minute) compare the current checksum of the system's Anyway, hope this may prove helpful or enlightening, and/or be a step toward an eventual resolution. :) |
This is such an annoying bug. Grateful to anyone who looks into it. My workaround is to keep a clean copy of the apt package and to reinstall it every time I get the issue. |
How do you do this ?
Le dim. 27 oct. 2019 à 11:02, pjchamberlain <[email protected]> a
écrit :
… This is such an annoying bug. Grateful to anyone who looks into it.
My workaround is to keep a clean copy of the apt package and to reinstall
it every time I get the issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2688?email_source=notifications&email_token=AAOIVYDTZAJXMFJQ7VKZWADQQVKKDA5CNFSM4CJX52IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECK2VAI#issuecomment-546679425>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOIVYDVHD6OCI44OETLBHDQQVKKDANCNFSM4CJX52IA>
.
|
fellow C302 user here, just wanting to chime in with some of my findings.
anyone with a working hypothesis and/or possible solution besides running unencrypted, feel free to chime in. |
It does seem to be related to encryption. I always used encryption. The frustration with this bug has meant I have given up using crouton. I now have an Asus C434 which supports crostini and so far it's met my need for running linux applications. |
RE: encryption I always install a new chroot without encryption, set everything up the way I want it and then encrypt it with an update afterwards, e.g. -
This seems to work best for me and may just help with this issue too. Hope this helps, |
it works for the most part, but post-encryption, I've often run into some kind of snag afterwards while my DE (usually XFCE) is running, where the terminal will refuse to spawn after Ctrl-Alt-T or the terminal icon in the dock is clicked, usually with some kind of error (I forgot specifically what). I have strong reason to believe it's related to segfaulting as well, as logging out of XFCE will produce an abrupt exit error that prevents a completely graceful shutdown of the chroot. I'll usually be running something like Eclipse (although once in a while, I've had firefox up as well). is there a way to get crouton to expose more debug info than the terminal it spawns in usually provides? |
Sad to see this issue closed, if only due to nostalgia. Five and a half years later, and the bug has never been solved. Unsatisfying, but whatcha gonna do? Thank you, @dnschneid, for this weird and awesome piece of software. |
Please describe your issue:
I have an Acer Chromebook R11, running stable channel Chrome 51.
I had no problems installing precise and installing additional software.
Last week, I wanted to install trusty and always got the mentioned error after crouton was installing software for a while. Tried several times with -u and from scratch. No chance.
I tried a different mirror, but that did not help either.
This week, crouton was able to install trusty with no errors, using the default mirror.
However, when I try to install some packages (for example mesa-utils) inside xfce4 (shell window), I get that error again.
So, I logged out of xfce4 and started chroot console only and there I can install everything.
If known, describe the steps to reproduce the issue:
Install trusty
enter-chroot -n trusty startxfce4
start shell window
apt-get install mesa-utils
The text was updated successfully, but these errors were encountered: