- This topic has 211 replies, 22 voices, and was last updated May 8-8:48 pm by einpoklum.
-
Posts
-
Xecure
Thanks for the info I can only compare with the programs install sorry, as they are the same as I use all the time with 19.2.1 with maybe a few different versions. The only service program installed would be mpd the rest should not be running at all on bootup.
Beware that, if not configured previously by you, a lot of services launch on bootup, including cups and others.
Check with
sudo service --status-all | grep +
All running services on your system, and compare with your previous custom installation of antiX 19.2.1. You can then disable all those you don’t want to start with your system.antiX Live system enthusiast.
General Live Boot Parameters for antiX.ex_Koo
Thanks Xecure
Was surprised to fine not much difference.21-alfa sudo service --status-all | grep + [sudo] password for koo: [ + ] acpid [ ? ] alsa-utils [ + ] bluetooth [ + ] brightness [ + ] connman [ ? ] cpufrequtils [ + ] cron [ ? ] cryptdisks [ ? ] cryptdisks-early [ + ] cups [ + ] dbus [ ? ] dundee [ + ] elogind [ + ] gpm [ + ] haveged [ ? ] hwclock.sh [ ? ] kmod [ ? ] loadcpufreq [ ? ] mount-configfs [ + ] mpd [ ? ] networking [ + ] nfs-common [ + ] ntp [ ? ] ofono [ + ] resolvconf [ + ] rpcbind [ + ] rsyslog [ + ] saned [ + ] slim [ + ] smartmontools [ + ] ssh [ + ] tlp [ + ] udev [ ? ] umountnfs-alternative.sh --------------------------- 19.2.1 $sudo service --status-all | grep + [sudo] password for koo: [ + ] acpid [ ? ] alsa-utils [ + ] battery-stats [ + ] bluetooth [ ? ] bootchart-done [ + ] brightness [ + ] connman [ ? ] cpufrequtils [ + ] cron [ ? ] cryptdisks [ ? ] cryptdisks-early [ + ] cups [ + ] dbus [ + ] elogind [ + ] gpm [ + ] haveged [ ? ] hwclock.sh [ ? ] kmod [ ? ] loadcpufreq [ + ] mpd [ ? ] networking [ + ] nfs-common [ ? ] pppd-dns [ + ] resolvconf [ + ] rpcbind [ + ] rsyslog [ + ] slim [ + ] thinkfan [ + ] tlp [ + ] udev [ + ] ufw [ ? ] umountnfs-alternative.sh- This reply was modified 2 years, 3 months ago by ex_Koo.
Xecure
If there are not much change in the services, compare the RAM usage of programs with sudo ps_mem.py
Maybe you can pin down which programs are using way more RAM than they use to.antiX Live system enthusiast.
General Live Boot Parameters for antiX.
ile
rokytnji Thanks. old archive nothing. and
Ouch.= my tree is on its side at tapatalk-antiX; nothing for: How to print an image. (?)Anonymous
@ile searching “mirage print” at MX forum refreshed my memory.
Back in 2016, I had configured (here locally) a mirage SendTo action, sending the image to a program named “photoprint”. IIRC, that program is no longer usable due to its incompatibility with newer versions of libcups.You might try the xpp utility and reply stating whether it is suitable https://packages.debian.org/buster/xpp
If there are not much change in the services, compare the RAM usage of programs with sudo ps_mem.py
Maybe you can pin down which programs are using way more RAM than they use to.FIXED with a version change of conky.
Run sudo ps_mem.py and the total was under 400mb then opened htop it also was under 400mb.
The strange thing was bpytop was showing ram over 700mg’s and so was conky version 1.11.6-2 (testing), I had no choice but to change conky versions to test, changed repo to buster was the only way I could force versions from testing installed 1.10.8-1+b1 now the reading is about 350mb. [Solved](Is there a way to stop conky upgrading again as I will still be running and testing bullseye on the next update.) Or just unmark conky each time.
Thanks for your help. Happy days
- This reply was modified 2 years, 3 months ago by ex_Koo.
You are so good Thanks yet again.
You just don’t know what to think sometimes have a look at this screenshot.. But on boot now it is only 336mb conky 🙂
conky = 483 mb
htop = 483 mb
sudo ps_mem.py = 310.5 mb
bpytop = 756 mbsudo apt-mark hold conky-all conky-all set on hold. antiX-21a * 35 files = 35M ~ >$conky -v conky 1.10.8 compiled Tue May 15 07:41:15 UTC 2018 for Linux 4.9.0-6-amd64 x86_64- This reply was modified 2 years, 3 months ago by ex_Koo.
Here you go..
koo@antix21a:~ $ inxi -F System: Host: antix21a Kernel: 5.8.16-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 2.1.1 Distro: antiX-bullseye-a1_x64-full Grup Yorum 3 January 2021 Machine: Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-I GAMING v: Rev 1.xx serial: <root required> UEFI: American Megatrends v: 4204 date: 01/28/2021 CPU: Topology: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 2200 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 2199 2: 2198 3: 2200 4: 2201 5: 2199 6: 2199 7: 2199 8: 2200 9: 2200 10: 2196 11: 2194 12: 2196 Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.10 driver: fbdev resolution: 2560x1440~N/A OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.4 Audio: Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel Device-3: TEAC US-2x2 type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server: ALSA v: k5.8.16-antix.1-amd64-smp Network: Device-1: Intel I211 Gigabit Network driver: igb IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 04:d4:c4:4e:44:63 Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: rtw_8822be IF: wlan0 state: down mac: 80:91:33:7e:87:6d Drives: Local Storage: total: 480.66 GiB used: 6.31 GiB (1.3%) ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB ID-2: /dev/sdb type: USB vendor: Toshiba model: TOSHIBA USB DRV size: 14.90 GiB Partition: ID-1: / size: 24.09 GiB used: 4.93 GiB (20.5%) fs: ext4 dev: /dev/sda8 ID-2: /home size: 94.00 GiB used: 117.3 MiB (0.1%) fs: ext4 dev: /dev/sda9 ID-3: swap-1 size: 16.17 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda7 Sensors: System Temperatures: cpu: 37.4 C mobo: N/A gpu: amdgpu temp: 36 C Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 Info: Processes: 255 Uptime: 9m Memory: 15.62 GiB used: 823.8 MiB (5.2%) Shell: bash inxi: 3.0.36The testing server is not working was fine last night..
https://mirrors.evowise.com/mxlinux-packages/antix//testing/ testing main nonsytsemd nonfreeXecure
The testing server is not working was fine last night..
Confirmed bug of repo-manager (now launched from Control Centre > Software)
After selecting antix mirror, there are two “//” between antix” and “testing”.
I am trying to find the reason in the code (starting line 336 in mainwindow.cpp), but I am not proficient enough in C++ to find the reason.Talking about the repo, should we change it to bullseye repo or keep on the testing repo?
After upgrading today, the “desktop-defaults-follow-fm.desktop” only launches Rox-filer even if the current desktop is Spacefm.
line 66 of /usr/local/bin/desktop-defaults-run
case 'head -1 $desktop_file' in
rox-*) Exec="rox-filer" ;;
space-*) Exec="spacefm" ;;
*) Exec="$fallback_fm" ;;
esac
The variable desktop_file was never set. Maybe it could be set at the top of the file, but I think there is a session variable that was previously exported, but I am no expert of how desktop-session works, so no idea how to solve this.- This reply was modified 2 years, 3 months ago by Xecure. Reason: fix code tags
- This reply was modified 2 years, 3 months ago by Xecure. Reason: second time trying to fix the code tags
- This reply was modified 2 years, 3 months ago by Xecure. Reason: I had to change the code, sorry
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
Dave
Fixed by adding
DESKTOP_SESSION_CODE=${DESKTOP_SESSION_CODE:-$(head -1 $HOME/.desktop-session/desktop-code.$disp)} DESKTOP_SESSION_IM=${DESKTOP_SESSION_IM:-${DESKTOP_SESSION_CODE%-*}}and changing the case statement variable to
case $DESKTOP_SESSION_IM inChanges in gitlab, should make it to the repo some time.
This was caused by separating desktop-session, desktop-menu, and desktop-defaults to their own packages and making them less dependent on each other.Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Xecure
Changes in gitlab, should make it to the repo some time.
Thanks, Dave.
This was caused by separating desktop-session, desktop-menu, and desktop-defaults to their own packages and making them less dependent on each other.
It seems I will have to study up. Anything we should test to see that the separation is working as intended?
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Dave
Ideally everything should still work as it used to.
This is the main need for testing; that the system upgrades to include the packages desktop-session-antix, desktop-defaults-antix, and desktop-menu-antix without loosing function.The major change/idea (so far) is that if you are making a custom core install you can install one without the other (or remove them from full/base)
Example, you could install desktop-menu and have automatic menus if that is all you want in your install.
This is the secondary testing needed; to make sure each will run independent of the other.Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Xecure
This is the secondary testing needed; to make sure each will run independent of the other.
I will see if I can experiment a bit during the week only keeping one package at a time to test that its features work properly.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
- You must be logged in to reply to this topic.
