Trouble with pacman, and octopi im sure they are related (SOLVED)

Ok So my pacman installer from terminal is having trouble finding packages that i know for sure are in the repo that i have. I already checked my pacman config its good. ive updated everything and all that. My other issue is because pacman is acting up i tried octopi installer.
That thing is even worse. It keeps starting to install but then says there is conflicting packages and asks if i would like to hit Yes or no to chose what package. I say yes then nothing happens. The log shows it goes ahead with the install and freezes up as the end never stooping so i am forced to close wich in tern means i dont get the installed software.

Where's your Garuda Inxi or any kind of logs or examples?

3 Likes

what one should i be interested in? the pacman one basically just shows what it prints out

Here is some journalD logs a ton of stuff. Also yesterday I tried out the F-word command tool that fixes mistakes you make and i ran it and it sent my system into a real loop. The cpu spun out to max ton of errors nothing I did would stop it. even rebooting. so I finally had to delete my shell config file and that stopped it. 36:29 | @/.snapshots/62/snapshot | pre | pacman -S community/npm - Pastebin.com

Just type the command into your terminal:

garuda-inxi

Paste the output into the thread.

If you are talking about fsck, it does not fix mistakes you make. It can detect and attempt to repair damaged filesystems. Also Btrfs is not really supported. In general, it is uncommon for it to be explicitly run in user space. I would advise not running it at all until you read more about what it does and how it is intended to be invoked. fsck - ArchWiki

Paste into the thread also the input and output of:

garuda-update
2 Likes

No not fssck its actually called TheF^&*, its pretty neat plugin TheF^&*^ plugin for linux command line about the btrs ive ran it with arch for a long time now never had an issue I do like the feature that it gives with snap shot backups very useful

 ā•­ā”€[email protected] in ~ took 157ms
 ā•°ā”€Ī» garuda-inxi
System:
  Kernel: 6.2.2-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=1b59b63f-1cb6-4f1e-af2a-6ae6d9d0b5b1 rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3
  Desktop: KDE Plasma v: 5.27.2 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: B250M-DS3H v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: B250M-DS3H-CF v: x.x serial: <superuser required>
    UEFI: American Megatrends v: F9 date: 04/10/2018
CPU:
  Info: model: Intel Core i5-7600 bits: 64 type: MCP arch: Kaby Lake
    gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 9 microcode: 0xF0
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 800/4100 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 27999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: eVga.com. driver: nvidia
    v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
    status: current (as of 2023-02) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:1b80 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
    compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,nouveau
    alternate: fbdev,nv,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x272mm (19.02x10.71")
    s-diag: 554mm (21.82")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 102
    size: 479x269mm (18.86x10.59") diag: 549mm (21.63") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce GTX
    1080/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: NVIDIA GP104 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Sound API: ALSA v: k6.2.2-zen2-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.66 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  IF-ID-1: enp0s20f0u8 state: unknown speed: -1 duplex: half mac: <filter>
Bluetooth:
  Device-1: Samsung GT-I9070 (network tethering USB debugging enabled)
    type: USB driver: rndis_host v: kernel bus-ID: 1-8:4 chip-ID: 04e8:6864
    class-ID: 0a00 serial: <filter>
  Report: bt-service: enabled,stopped note: tool can't run
Drives:
  Local Storage: total: 1.38 TiB used: 187.25 GiB (13.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SDSSDA-1T00
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 40RL scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: SK Hynix model: HFS512G39TNF-N2A0A
    size: 476.94 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 0P10 scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 187.25 GiB (20.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 608 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 187.25 GiB (20.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 187.25 GiB (20.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 187.25 GiB (20.1%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 31.31 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.0 C mobo: N/A gpu: nvidia temp: 52 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 265 Uptime: 1h 18m wakeups: 0 Memory: 31.31 GiB
  used: 6.06 GiB (19.3%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: 1782
  pm: pacman pkgs: 1775 libs: 391 tools: octopi,paru pm: snap pkgs: 7
  Shell: Bash v: 5.1.16 running-in: alacritty inxi: 3.3.25
Garuda (2.6.15-1):
  System install date:     2023-03-07
  Last full system update: 2023-03-10 ā†»
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

 ā•­ā”€[email protected] in ~ took 2s
 ā•°ā”€Ī»

BluishHumility was only commenting about how BTRFS isn't supported using fsck, not BTRFS as a whole, as that what Garuda Linux ships with.

If you are getting errors from that, what commands were you running? It gives confirmation by default on what it tries to "fix". You shouldn't be blindly accepting what it fixes.

Quote from Github about its default being requiring confirmation:
If you're not afraid of blindly running corrected commands, the require_confirmation settings option can be disabled

1 Like

:laughing: I did not know about this project, I thought you were doing something else!

Don't forget to post when you get a chance:

garuda-update
1 Like

for sure I only used it twice, and from what i understand it just fixes stuff like forgetting to sudo. stuff like that but I was getting these before ever using that. I am just trying to think of things that I did that could have cuased something to change. I changed from fish shell to bash, thats one thing I was thinkig could cause the issue but if that was the case I would have issues with my shell or errors pointing that direction like bashrc or something. I never did like the octopi installer It always kinda confused me how they do things. panmac is nice fallback when you dont use pacman,

haha yea here is the output
garuda-update
[:zap:] Ɨ garuda-update
[sudo] password for llama:
:: Synchronizing package databases...
garuda is up to date
core is up to date
extra 1744.7 KiB 316 KiB/s 00:06 [------------------------------] 100%
community 7.3 MiB 1288 KiB/s 00:06 [------------------------------] 100%
multilib is up to date
blackarch is up to date

--> Refreshing mirrorlists using rate-mirrors, please be patient..:tea:

:: Synchronizing package databases...
garuda downloading...
core downloading...
extra downloading...
community downloading...
multilib downloading...
blackarch downloading...
:: Starting full system upgrade...
warning: ckbcomp: local (1.210-1) is newer than blackarch (1.207-2)
warning: paru: local (1.11.1-1.3) is newer than blackarch (1.9.3-1)
there is nothing to do

System updated! :penguin:

ā•­ā”€[email protected] in ~/.config as :mage: took 52s
āœ¦ ā•°ā”€Ī»

whats going on here this is what it was doing.

...skipping...
+     ln -sf /usr/lib/systemd/system/pamac-cleancache.timer /etc/systemd/system/timers.target.wants/pamac-cleancache.timer
+     # ln -sf /usr/lib/systemd/system/pamac-mirrorlist.timer /etc/systemd/system/timers.target.wants/pamac-mirrorlist.timer
+  fi
+}
+
+post_remove() {
+  # disable systemd timers
+  rm -f /etc/systemd/system/timers.target.wants/pamac-cleancache.timer
+  # rm -f /etc/systemd/system/timers.target.wants/pamac-mirrorlist.timer
+}
~
~
~
~
~
~
~
...skipping...
+     msg "Updating timer symlinks"
+     [[ -e /etc/systemd/system/multi-user.target.wants/pamac-cleancache.timer ]] && rm -f /etc/systemd/system/multi-user.target.wants/pamac-cleancache.timer
+     # [[ -e /etc/systemd/system/multi-user.target.wants/pamac-mirrorlist.timer ]] && rm -f /etc/systemd/system/multi-user.target.wants/pamac-mirrorlist.timer
+     # enable systemd timers
+     mkdir -p /etc/systemd/system/timers.target.wants
+     ln -sf /usr/lib/systemd/system/pamac-cleancache.timer /etc/systemd/system/timers.target.wants/pamac-cleancache.timer
+     # ln -sf /usr/lib/systemd/system/pamac-mirrorlist.timer /etc/systemd/system/timers.target.wants/pamac-mirrorlist.timer
+  fi
+}
+
+post_remove() {
+  # disable systemd timers
+  rm -f /etc/systemd/system/timers.target.wants/pamac-cleancache.timer
+  # rm -f /etc/systemd/system/timers.target.wants/pamac-mirrorlist.timer
+}
...skipping...
+  mkdir -p /etc/systemd/system/timers.target.wants
+  ln -sf /usr/lib/systemd/system/pamac-cleancache.timer /etc/systemd/system/timers.target.want
s/pamac-cleancache.timer
+  # restore old conf
+  restore_conf
+}
+
+post_upgrade() {
+   # enable flatpak repo
+  if [ -f /usr/bin/flatpak ]; then
+    flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
+  fi
+  # restore old conf
+  if [ "$(vercmp $2 7.3.5-3)" -lt 0 ]; then
+     restore_conf
+  fi
+
+  if [ "$(vercmp $2 8.0.3-5)" -lt 0 ]; then
+     # remove wrong placed symlinks
+     msg "Updating timer symlinks"
+     [[ -e /etc/systemd/system/multi-user.target.wants/pamac-cleancache.timer ]] && rm -f /etc/systemd/system/multi-user.target.wants/pamac-cleancache.timer
+     # [[ -e /etc/systemd/system/multi-user.target.wants/pamac-mirrorlist.timer ]] && rm -f /etc/systemd/system/multi-user.target.wants/pamac-mirrorlist.timer
+     # enable systemd timers
+     mkdir -p /etc/systemd/system/timers.target.wants
+     ln -sf /usr/lib/systemd/system/pamac-cleancache.timer /etc/systemd/system/timers.target.wants/pamac-cleancache.timer
+     # ln -sf /usr/lib/systemd/system/pamac-mirrorlist.timer /etc/systemd/system/timers.target.wants/pamac-mirrorlist.timer
+  fi
+}
+
+post_remove() {
+  # disable systemd timers
+  rm -f /etc/systemd/system/timers.target.wants/pamac-cleancache.timer
+  # rm -f /etc/systemd/system/timers.target.wants/pamac-mirrorlist.timer
+}

sorry that didnt paste well here it is. that is all from trying to install pamac via yay ā”€[email protected] in ~ as šŸ§™ took 16sāœ¦ ā•°ā”€Ī» yay -S pamac-aur:: Checking for conf - Pastebin.com

wait I just hit q to exit and now its installing . freaking odd. ive never seen that before

I wouldn't say "odd", that is typical after showing a review.

1 Like

I agree, that looks normal. All that output is the PKGBUILD, so you can review it before installing. Press Q to exit the PKGBUILD and start installing.

Next time, you can format terminal output by adding three tildes (~) before and after
~~~
like this.
~~~
I edited yours above, you can see it looks much better.

Anyway, glad you got it working but be careful installing packages with Pamac--it has a reputation for causing problems. Now that you are familiar with Yay, a safe method would be to use Pamac to search for a package, but install with Yay.

2 Likes

i mean maybe on garuda but ive been on arco linux fedora and others and never got sent to one of those screens when just dealing with conflicts but maybe im lucky or something if that is normal to not see them till now

yea thanks, i usualy dont and just use pacman I just wanted it over the octopi one, yea not sure what i did to change the format of the output to make t look like something was wrong, I did just install garuda a few days ago so maybe thats default? but in anycase thanks for walking me through the steps i appreciate you both for taking the time

Since you aren't used to pacman, I'll leave this here to read. It is an extremely well done chart of commands, and what they are for different distros too.
https://wiki.archlinux.org/title/Pacman/Rosetta

2 Likes

oh I think i wrote that wrong I mean i dont normally use pamac and usually use pacman but I always love a good read. can always learn more thanks :slight_smile:

1 Like

hehe, okay good! Pacman is typically more preferable to install things with anyways.
For a GUI package manager, I typically go with bauh, even if I mostly use Pacman. It's a good way to see information on packages a bit easier. Somebody I know uses bauh extensively with Garuda and seems to love it (and hasn't experienced issues with it long as they use garuda-update first )

1 Like