So I was wondering, is there a place you can make the --debug flag output to or if there was a default location besides the terminal itself?

Like the title says pacman -Syu is occasionally hard locking the computer forcing a power cycle. After restarting the computer the update will go fine after deleting the archives that are corrupted from the failed update.

It always hangs in the :: Running post-transaction hooks... part of the update. This time it hung specifically on the ( 3/19) Reloading system manager configuration...

I have tried to redirect the debug output like: pacman -Syu --debug >> ~/Desktop/pacdebug.txt but it seems that I only get the standard upgrade output.

Is there some other tool or steps I can use to investigate this?

This has been happening since I upgraded to KDE 6 but I don’t think it’s directly related to KDE it’s just when it started.

Thanks!

    • disheveledWallaby@lemmy.mlOP
      link
      fedilink
      arrow-up
      0
      ·
      8 months ago

      pacman -Syu --debug >& ~/Desktop/pacdebug.txt

      Looks like that will almost work, I need to answer :: Proceed with installation? [Y/n] and possibly other questions. Do you think that I should use the --noconfirm flag?

         --noconfirm
             Bypass any and all “Are you sure?” messages. It’s not a good idea to do this unless you want to run pacman from a script.
      
        • disheveledWallaby@lemmy.mlOP
          link
          fedilink
          arrow-up
          0
          ·
          8 months ago

          I’m going to wait for a couple days to see if anyone else has any ideas and use the time to do some more investigating. If all else fails I’ll just have to hope I get an update that doesn’t require an important intervention.

          Thanks again, your advice is much appreciated!