this post was submitted on 07 Mar 2024
1 points (100.0% liked)

linuxmemes

21180 readers
804 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
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    1
    I know that it's rolling release, but 4 times this year seems a bit much (lemmy.world)
    submitted 8 months ago by bali10050@lemmy.world to c/linuxmemes@lemmy.world
    16 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Titou@feddit.de 0 points 8 months ago (1 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 0 points 8 months ago (1 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

    [–] Titou@feddit.de 0 points 8 months ago (1 children)

    Arch dosn't break by itself, i've used bunch of Arch installations and every time it broke it was because of bad manipulation, not pacman -syu

    [–] guskikalola@social.vivaldi.net 0 points 8 months ago (1 children)

    @Titou @Nisaea Well, in my case it once broke due to a conflict between pahole and nvidia that caused errors. Games would crash every now and then. I was going crazy until I found that the update broke nvidia :}

    [–] Titou@feddit.de 0 points 8 months ago (1 children)

    How did you installed it ? Official arch repo or self compiled ? And what nvidia drivers are you using ? Nouveau or proprietary one ?

    [–] guskikalola@social.vivaldi.net 0 points 8 months ago (1 children)

    @Titou proprietary drivers, dkms version.
    Official repos.

    Both my friend and I experienced this, a few minutes later pahole was reverted to previous version on the repos and the update was delayed until fixes were made.

    I migrated from nvidia to amd last summer and no issues since then ( a few crashes in Minecraft, its the only game capable of crashing the GPU, dont know why or how ).

    [–] Titou@feddit.de 0 points 8 months ago

    Conflict issues is not arch-exclusive(happenned to me on debian sid months ago) but glad to heard you switched to amd