Post 1032182 by cdmnky@niu.moe
 (DIR) More posts by cdmnky@niu.moe
 (DIR) Post #1031939 by cdmnky@niu.moe
       2018-11-07T12:48:48Z
       
       5 likes, 7 repeats
       
       PSA: If you're running Arch, DO NOT UPDATE FOR THE TIME BEING!!!- Anyone running Dell XPS 15 laptops will have a bricked system- Systemd hibernate is broken on laptopsYou have been warned
       
 (DIR) Post #1031977 by Normandy@niu.moe
       2018-11-07T12:50:31Z
       
       0 likes, 0 repeats
       
       @cdmnky thanks for the heads up
       
 (DIR) Post #1031998 by Skoll3@pleroma.site
       2018-11-07T12:51:31.407548Z
       
       0 likes, 0 repeats
       
       @cdmnky oh shitIs :manjaro: affected?
       
 (DIR) Post #1032010 by jeff@social.i2p.rocks
       2018-11-07T12:52:04.915791Z
       
       0 likes, 0 repeats
       
       @cdmnky arch linux maintainers strike again!
       
 (DIR) Post #1032015 by cdmnky@niu.moe
       2018-11-07T12:52:11Z
       
       1 likes, 0 repeats
       
       @Skoll3 no, Manjaro has its own repos and is usually 2 weeks or so behind Arch stable
       
 (DIR) Post #1032030 by acrylicjam@pleroma.acrylicjam.xyz
       2018-11-07T12:52:08.142056Z
       
       0 likes, 0 repeats
       
       @cdmnky wtf are you serious?!
       
 (DIR) Post #1032031 by acrylicjam@pleroma.acrylicjam.xyz
       2018-11-07T12:52:37.353469Z
       
       0 likes, 0 repeats
       
       @cdmnky got a link?
       
 (DIR) Post #1032032 by cdmnky@niu.moe
       2018-11-07T12:53:12Z
       
       0 likes, 1 repeats
       
       @acrylicjam https://www.reddit.com/r/archlinux/comments/9uyoql/arch_update_warning/https://www.reddit.com/r/archlinux/comments/9uys10/systemd_update_breaks_hibernation/
       
 (DIR) Post #1032033 by igeljaeger@the.hedgehoghunter.club
       2018-11-07T12:53:16.660529Z
       
       0 likes, 0 repeats
       
       @cdmnky maybe I should go back to fuckin ubuntu at this point
       
 (DIR) Post #1032116 by acrylicjam@pleroma.acrylicjam.xyz
       2018-11-07T12:56:48.478383Z
       
       0 likes, 0 repeats
       
       @cdmnky Thanks for the heads-up. I'm on a Dell XPS 13 but still heeding this warning. This made me think I should really subscribe to somesuch channels to get such warnings in future.(just made my update script un-executable in case I attempt to run it for now! (force of habit))
       
 (DIR) Post #1032117 by cdmnky@niu.moe
       2018-11-07T12:57:37Z
       
       0 likes, 0 repeats
       
       @acrylicjam I only randomly saw a thread while browsing Reddit. There's nothing on any of the official news feeds or the forums right nowhttps://www.reddit.com/r/archlinux/comments/9uyoql/arch_update_warning/
       
 (DIR) Post #1032156 by ivesen@miniwa.moe
       2018-11-07T12:59:32.342660Z
       
       0 likes, 0 repeats
       
       @cdmnky are both of these caused by systemd? :thinking_cirno:
       
 (DIR) Post #1032171 by fred@niu.moe
       2018-11-07T13:00:29Z
       
       0 likes, 0 repeats
       
       @cdmnky Thanks. I suppose I should subscribe to the announcement mailing list.
       
 (DIR) Post #1032174 by cdmnky@niu.moe
       2018-11-07T13:00:35Z
       
       0 likes, 0 repeats
       
       @ivesen probably. The hibernation issue is definitely systemdthe XPS issue returns the error/sbin/init: not executable
       
 (DIR) Post #1032177 by kurisu@iscute.moe
       2018-11-07T13:00:58.050923Z
       
       0 likes, 0 repeats
       
       @ivesen @cdmnky reddit posts are an hour old, not enough time for a full investigation. We'll find out when its fixed.But of course people will jump to conclusions prematurely
       
 (DIR) Post #1032182 by cdmnky@niu.moe
       2018-11-07T13:01:22Z
       
       0 likes, 0 repeats
       
       @kurisu @ivesen better safe than sorry though
       
 (DIR) Post #1032185 by kurisu@iscute.moe
       2018-11-07T13:01:50.974999Z
       
       0 likes, 0 repeats
       
       @cdmnky @ivesen oh of course warning people is the right thing to do
       
 (DIR) Post #1032206 by kurisu@iscute.moe
       2018-11-07T13:03:40.711308Z
       
       0 likes, 0 repeats
       
       @cdmnky @ivesen that systemd breaks hibernation is almost certainly correctthat it breaks boot seems to be a lot less certain, we'll see
       
 (DIR) Post #1032216 by ivesen@miniwa.moe
       2018-11-07T13:04:26.731775Z
       
       1 likes, 0 repeats
       
       @Skoll3 @cdmnky they will be in 2 weeks :^)
       
 (DIR) Post #1032371 by quad@weeaboo.space
       2018-11-07T13:12:12.254147Z
       
       2 likes, 2 repeats
       
       @cdmnky Jokes on you, I run a non-systemd distro. So hibernation didn't work in the first place
       
 (DIR) Post #1032426 by shibayashi@communicating.cypherpunk.observer
       2018-11-07T13:14:47.582367Z
       
       1 likes, 1 repeats
       
       @cdmnkymfw I updated Arch on a Dell XPS just minutes ago
       
 (DIR) Post #1032444 by cdmnky@niu.moe
       2018-11-07T13:16:26Z
       
       0 likes, 0 repeats
       
       @shibayashi here's the reddit thread if you're interested:https://www.reddit.com/r/archlinux/comments/9uyoql/arch_update_warning/
       
 (DIR) Post #1032445 by selea@social.linux.pizza
       2018-11-07T13:16:28Z
       
       0 likes, 0 repeats
       
       @cdmnky Great,
       
 (DIR) Post #1036934 by waifu@pikachu.rocks
       2018-11-07T17:57:28.263758Z
       
       0 likes, 0 repeats
       
       @cdmnky not again
       
 (DIR) Post #1037593 by Wolf480pl@niu.moe
       2018-11-07T18:41:24Z
       
       0 likes, 0 repeats
       
       @cdmnky I wouldn't call it bricked if the problem is "/sbin/init is not executable".The system is corrupted/unbootable, yes.But for me, the word "bricked" means "beyond repair", or, at least, "the hardware is unable to boot ANY external software".In this case, as far as I understand, the hardware/firmware is perfectly fine, it will still boot from a livecd/liveusb, with which you can fix your Arch installation.
       
 (DIR) Post #1037744 by MountainJ@fosstodon.org
       2018-11-07T18:56:11Z
       
       0 likes, 0 repeats
       
       @cdmnkyWell, I do have a dell xps 15, thank you :)
       
 (DIR) Post #1052958 by shellkr@mstdn.io
       2018-11-08T08:45:17Z
       
       0 likes, 0 repeats
       
       @kurisu @ivesen @cdmnky Yep, looks like it was.... I was going to write a similar reply as you. I was thinking corruption on user install. Can happen for kernels too. In this case it might be on a mirror but seems to be fixed already.If corruption the machine definitely is not bricked. A quick fix with arch-chroot is usually the only thing that is needed.
       
 (DIR) Post #1052960 by cdmnky@niu.moe
       2018-11-08T11:26:42Z
       
       0 likes, 0 repeats
       
       @shellkrlooks like the encrypt module was removed from the kernel configs https://bbs.archlinux.org/viewtopic.php?id=241788@kurisu @ivesen
       
 (DIR) Post #1061985 by shellkr@mstdn.io
       2018-11-08T21:00:03Z
       
       0 likes, 0 repeats
       
       @cdmnky @kurisu @ivesen That doesn't sound right... if everyone got their /etc/mkinitcpio.conf replaced with a pacnew (or something) it would show. Not sure what kernel that is. The kernel use by default 'CONFIG_FS_ENCRYPTION=m'... 'zcat /proc/config.gz | grep -i fs_enc'It is more likely a user made change or specific non-common package the user use. It is probably easy to check.