Ну спасибо всем, что объяснили , просто во всех туторах по установке на рут больше 15ти не ставят и не объясняют. Вопрос решен
Удалил свапфайл освободилось место, думаю пока хватит. а в gparted я не могу менять размер /home из-за того что он btrfs
vs220
У вас это виртуалка еще или реальное железо? И как выше заметили вынесите swap из корня
Пока что еще виртуалка, а есть инструкции о том как свап из корня вынести либо рут увеличить?
Aivar
Вот и виновник найден.
Если я свапфайл удалю у меня ничего не полетит? Зачем то ж его ставил
vs220
sudo ncdu /
ncdu 1.16 ~ Use the arrow keys to navigate, press ? for help
--- / ------------------------------------------------------------------------------------------------------------------------
    6.0 GiB [##################]  swapfile
    3.5 GiB [##########        ] /usr
  422.2 MiB [#                 ] /var
  110.6 MiB [                  ] /boot
   99.7 MiB [                  ] /home
    6.8 MiB [                  ] /etc
  720.0 KiB [                  ] /run
  512.0 KiB [                  ] /tmp
  272.0 KiB [                  ] /root
e  16.0 KiB [                  ] /lost+found
   12.0 KiB [                  ] /srv
e   4.0 KiB [                  ] /opt
e   4.0 KiB [                  ] /mnt
.   0.0   B [                  ] /proc
    0.0   B [                  ] /sys
    0.0   B [                  ] /dev
@   0.0   B [                  ]  sbin
@   0.0   B [                  ]  lib64
@   0.0   B [                  ]  lib
@   0.0   B [                  ]  bin
sudo ls -a1 /
[a1bion@APC ~]$ sudo ls -a1 /
.
..
bin
boot
dev
etc
home
lib
lib64
lost+found
mnt
opt
proc
root
run
sbin
srv
swapfile
sys
tmp
usr
var

А есть способ увеличить раздел /root без переустановки?
sudo du -hxd1 /
[a1bion@APC ~]$ sudo du -hxd1 /
2.8G /usr
1.2G /var
12K /srv
4.0K /mnt
4.0K /opt
111M /boot
16K /lost+found
6.6M /etc
272K /root
11G /
[a1bion@APC ~]$


ну даже если пару гигабайт очиститься, не хотелось бы позже еще раз столкнуться с такой проблемой потому что в планах было еще много чего скачать
У меня под раздел /root выделенно 11.5G и после установки оболочки и некоторых программ осталось 122M и теперь я не могу установить даже gcc по причине нехватки места (кеш/логи чистил). Как изменить в pacman место установки на /home либо какой другой пакетный менеджер выбрать чтоб он устанавливал в хоум где есть куча места.
vs220
в крайнем случае можете вообще без dm настроить
https://archlinux.org.ru/forum/topic/16498/
Зделал как здесь, теперь всё вроде работает. Большое спасибо, что помогаете новичкам разобраться в арч. Никнейм vs220 запомню на всю жизнь.
(а как тему закрыть на форуме?)
[i]** Message: 23:59:41.094: 1631825981: add xserver watch
X.Org X Server 1.20.13
X Protocol Version 11, Revision 0
Build Operating System: Linux Archlinux
Current Operating System: Linux APC 5.14.3-arch1-1 #1 SMP PREEMPT Sun, 12 Sep 2021 20:51:34 +0000 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=8bd50928-9ef5-42c3-8d70-a24843028d21 rw loglevel=3 quiet
Build Date: 04 August 2021  08:13:54AM

Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 16 23:59:41 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86BrightnessAuto
> Warning:          Could not resolve keysym XF86DisplayOff
> Warning:          Could not resolve keysym XF86Info
> Warning:          Could not resolve keysym XF86AspectRatio
> Warning:          Could not resolve keysym XF86DVD
> Warning:          Could not resolve keysym XF86Audio
> Warning:          Could not resolve keysym XF86ChannelUp
> Warning:          Could not resolve keysym XF86ChannelDown
> Warning:          Could not resolve keysym XF86Break
> Warning:          Could not resolve keysym XF86VideoPhone
> Warning:          Could not resolve keysym XF86ZoomReset
> Warning:          Could not resolve keysym XF86Editor
> Warning:          Could not resolve keysym XF86GraphicsEditor
> Warning:          Could not resolve keysym XF86Presentation
> Warning:          Could not resolve keysym XF86Database
> Warning:          Could not resolve keysym XF86Voicemail
> Warning:          Could not resolve keysym XF86Addressbook
> Warning:          Could not resolve keysym XF86DisplayToggle
> Warning:          Could not resolve keysym XF86SpellCheck
> Warning:          Could not resolve keysym XF86ContextMenu
> Warning:          Could not resolve keysym XF86MediaRepeat
> Warning:          Could not resolve keysym XF8610ChannelsUp
> Warning:          Could not resolve keysym XF8610ChannelsDown
> Warning:          Could not resolve keysym XF86Images
> Warning:          Could not resolve keysym XF86NotificationCenter
> Warning:          Could not resolve keysym XF86PickupPhone
> Warning:          Could not resolve keysym XF86HangupPhone
> Warning:          Could not resolve keysym XF86Fn
> Warning:          Could not resolve keysym XF86Fn_Esc
> Warning:          Could not resolve keysym XF86FnRightShift
> Warning:          Could not resolve keysym XF86Numeric0
> Warning:          Could not resolve keysym XF86Numeric1
> Warning:          Could not resolve keysym XF86Numeric2
> Warning:          Could not resolve keysym XF86Numeric3
> Warning:          Could not resolve keysym XF86Numeric4
> Warning:          Could not resolve keysym XF86Numeric5
> Warning:          Could not resolve keysym XF86Numeric6
> Warning:          Could not resolve keysym XF86Numeric7
> Warning:          Could not resolve keysym XF86Numeric8
> Warning:          Could not resolve keysym XF86Numeric9
> Warning:          Could not resolve keysym XF86NumericStar
> Warning:          Could not resolve keysym XF86NumericPound
> Warning:          Could not resolve keysym XF86NumericA
> Warning:          Could not resolve keysym XF86NumericB
> Warning:          Could not resolve keysym XF86NumericC
> Warning:          Could not resolve keysym XF86NumericD
> Warning:          Could not resolve keysym XF86CameraFocus
> Warning:          Could not resolve keysym XF86WPSButton
> Warning:          Could not resolve keysym XF86CameraZoomIn
> Warning:          Could not resolve keysym XF86CameraZoomOut
> Warning:          Could not resolve keysym XF86CameraUp
> Warning:          Could not resolve keysym XF86CameraDown
> Warning:          Could not resolve keysym XF86CameraLeft
> Warning:          Could not resolve keysym XF86CameraRight
> Warning:          Could not resolve keysym XF86AttendantOn
> Warning:          Could not resolve keysym XF86AttendantOff
> Warning:          Could not resolve keysym XF86AttendantToggle
> Warning:          Could not resolve keysym XF86LightsToggle
> Warning:          Could not resolve keysym XF86ALSToggle
> Warning:          Could not resolve keysym XF86Buttonconfig
> Warning:          Could not resolve keysym XF86Taskmanager
> Warning:          Could not resolve keysym XF86Journal
> Warning:          Could not resolve keysym XF86ControlPanel
> Warning:          Could not resolve keysym XF86AppSelect
> Warning:          Could not resolve keysym XF86Screensaver
> Warning:          Could not resolve keysym XF86VoiceCommand
> Warning:          Could not resolve keysym XF86Assistant
> Warning:          Could not resolve keysym XF86BrightnessMin
> Warning:          Could not resolve keysym XF86BrightnessMax
> Warning:          Could not resolve keysym XF86KbdInputAssistPrev
> Warning:          Could not resolve keysym XF86KbdInputAssistNext
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgroup
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgroup
> Warning:          Could not resolve keysym XF86KbdInputAssistAccept
> Warning:          Could not resolve keysym XF86KbdInputAssistCancel
> Warning:          Could not resolve keysym XF86RightUp
> Warning:          Could not resolve keysym XF86RightDown
> Warning:          Could not resolve keysym XF86LeftUp
> Warning:          Could not resolve keysym XF86LeftDown
> Warning:          Could not resolve keysym XF86RootMenu
> Warning:          Could not resolve keysym XF86MediaTopMenu
> Warning:          Could not resolve keysym XF86Numeric11
> Warning:          Could not resolve keysym XF86Numeric12
> Warning:          Could not resolve keysym XF86AudioDesc
> Warning:          Could not resolve keysym XF863DMode
> Warning:          Could not resolve keysym XF86NextFavorite
> Warning:          Could not resolve keysym XF86StopRecord
> Warning:          Could not resolve keysym XF86PauseRecord
> Warning:          Could not resolve keysym XF86VOD
> Warning:          Could not resolve keysym XF86Unmute
> Warning:          Could not resolve keysym XF86FastReverse
> Warning:          Could not resolve keysym XF86SlowReverse
> Warning:          Could not resolve keysym XF86Data
> Warning:          Could not resolve keysym XF86OnScreenKeyboard
> Warning:          Could not resolve keysym XF86PrivacyScreenToggle
> Warning:          Could not resolve keysym XF86SelectiveScreenshot
> Warning:          Could not resolve keysym XF86Macro1
> Warning:          Could not resolve keysym XF86Macro2
> Warning:          Could not resolve keysym XF86Macro3
> Warning:          Could not resolve keysym XF86Macro4
> Warning:          Could not resolve keysym XF86Macro5
> Warning:          Could not resolve keysym XF86Macro6
> Warning:          Could not resolve keysym XF86Macro7
> Warning:          Could not resolve keysym XF86Macro8
> Warning:          Could not resolve keysym XF86Macro9
> Warning:          Could not resolve keysym XF86Macro10
> Warning:          Could not resolve keysym XF86Macro11
> Warning:          Could not resolve keysym XF86Macro12
> Warning:          Could not resolve keysym XF86Macro13
> Warning:          Could not resolve keysym XF86Macro14
> Warning:          Could not resolve keysym XF86Macro15
> Warning:          Could not resolve keysym XF86Macro16
> Warning:          Could not resolve keysym XF86Macro17
> Warning:          Could not resolve keysym XF86Macro18
> Warning:          Could not resolve keysym XF86Macro19
> Warning:          Could not resolve keysym XF86Macro20
> Warning:          Could not resolve keysym XF86Macro21
> Warning:          Could not resolve keysym XF86Macro22
> Warning:          Could not resolve keysym XF86Macro23
> Warning:          Could not resolve keysym XF86Macro24
> Warning:          Could not resolve keysym XF86Macro25
> Warning:          Could not resolve keysym XF86Macro26
> Warning:          Could not resolve keysym XF86Macro27
> Warning:          Could not resolve keysym XF86Macro28
> Warning:          Could not resolve keysym XF86Macro29
> Warning:          Could not resolve keysym XF86Macro30
> Warning:          Could not resolve keysym XF86MacroRecordStart
> Warning:          Could not resolve keysym XF86MacroRecordStop
> Warning:          Could not resolve keysym XF86MacroPresetCycle
> Warning:          Could not resolve keysym XF86MacroPreset1
> Warning:          Could not resolve keysym XF86MacroPreset2
> Warning:          Could not resolve keysym XF86MacroPreset3
> Warning:          Could not resolve keysym XF86KbdLcdMenu1
> Warning:          Could not resolve keysym XF86KbdLcdMenu2
> Warning:          Could not resolve keysym XF86KbdLcdMenu3
> Warning:          Could not resolve keysym XF86KbdLcdMenu4
> Warning:          Could not resolve keysym XF86KbdLcdMenu5
Errors from xkbcomp are not fatal to the X server
** Message: 23:59:42.152: 1631825982: start xserver in 1 retry
** Message: 23:59:45.016: find greeter (nil)

** Message: 23:59:45.016: find idle 0x562c2b83c1b0

** Message: 23:59:45.016: add 0x562c2b83c1b0

** Message: 23:59:45.016: prepare greeter on /var/run/lxdm/lxdm-:0.auth

** Message: 23:59:45.026: start greeter on /var/run/lxdm/lxdm-:0.auth

** Message: 23:59:45.084: greeter 971 session 0x562c2b83c1b0

** Message: 23:59:45.084: user 971 session 0x562c2b83c1b0 cmd USER_LIST

** Message: 23:59:51.771: find greeter (nil)

** Message: 23:59:51.771: find idle 0x562c2b83c1b0

** Message: 23:59:51.771: add 0x562c2b83c1b0

** Message: 23:59:51.771: prepare greeter on /var/run/lxdm/lxdm-:0.auth

** Message: 23:59:51.772: start greeter on /var/run/lxdm/lxdm-:0.auth

** Message: 23:59:51.805: greeter 971 session 0x562c2b83c1b0

** Message: 23:59:51.805: user 971 session 0x562c2b83c1b0 cmd USER_LIST

(II) AIGLX: Suspending AIGLX clients for VT switch

** (process:328): CRITICAL **: 00:01:49.431: QUIT BY SIGNAL 15

** Message: 00:01:49.431: quit code 0

** Message: 00:01:49.431: exit cb

(II) Server terminated successfully (0). Closing log file.
** Message: 00:01:49.611: free session

[a1bion@APC ~]$[/i]

а где process:328 глянуть изза которого оно закрылось?