this post was submitted on 07 Mar 2024
381 points (95.7% liked)

linuxmemes

21222 readers
65 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Titou@feddit.de 19 points 8 months ago (21 children)

    What did you edited ? Arch user here, never had this kind of issue. Also if you managed to install Arch, you should be able to fix it(maybe you switched from terminals, try ctrl+alt+1-9)

    [–] Nisaea@lemmy.sdf.org 20 points 8 months ago (19 children)

    You were just lucky. For some of us ut was just about having the wrong hardware at the wrong time.

    Not complaining, I knew the risks going in and still love my distro, but arch updates totally can brick a PC with no PEBCAK involved. It does happen. :3

    load more comments (16 replies)
    load more comments (17 replies)