Closed (fixed)
Project:
Entity API
Version:
7.x-1.x-dev
Component:
Code - misc
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Apr 2012 at 16:58 UTC
Updated:
9 Oct 2013 at 22:10 UTC
Backups were saved into the directory /root/drush-backups/foo/20120406165612/modules/entity. [ok]
The command could not be executed successfully (returned: Segmentation fault [error]
, code: <em class="placeholder">139</em>)
Comments
Comment #1
hass commentedJust run "drush up" if the DEV is outdated.
Comment #2
e2thex commentedit appear to happen in
http://drupalcode.org/project/entity.git/commit/654876282fecaf669e4e2152...
or at least that is what git bisect said
Comment #3
carn1x commentedUpgraded from 7.x-1.0-rc1 to latest dev (7.x-1.0-rc1+46-dev).
Site WSODs, and "drush cc all" gives:
"drush up" does nothing.
Comment #4
carn1x commentedAs fago mentioned in another queue, I had to update entity AND i18n to new dev, which gets rid of the segfault.
See: #1447946: Recent entity API dev version requires a recent i18n dev version
Comment #5
hass commentedAs E comes before I - the next update will WSOD thousands of sites and bring them offline. Entity API need to workaround for sure if this is really the readon. A system down is not acceptable. I know the sites I've updated had i18n installed, but it took me hours to discover Entity API as root cause.
Comment #6
iamEAP commentedThis potentially affects people using non-dev modules. The latest Field Collection beta (4) relies on this dev version of Entity API.
If they happend to be using i18n as well, and not the latest dev, they'll experience this.
Also relevant: #1530018: Create a new stable release 7.x-1.5
Comment #7
Ace Cooper commentedHad the same problem, bashing my head for several hours.
Turned out that i18n was at fault. As soon as I updated to i18n-1.7 the "Segmentation fault" error went away (woohoo!).
Thank you, iamEAP.
Comment #8
tuwebo commented#7 worked for me too.
Thanks Ace Cooper
Comment #9
martinbo commentedThanks Ace Cooper and iamEAP, it really helped me!!
Comment #10
andrea.cavattoni commented#7 works form me
Comment #11
slown commented#7 worked for me too. Yeepah! Thx A Lot
Comment #12
alexander allen commentedMarking as closed since various users reported the bug as fixed more than a year ago.
Comment #13
alexander allen commentedFixed status.