MX Linux Forum

Posted: **Wed Jan 29, 2025 1:16 pm**

Using my non-admin account, as usual, I opened a separate terminal to SU and run "apt autoremove".
Everything seemed to go fine, and the normal prompt was presented. That is all that I did in that terminal window.
I clicked to close it, and it said, effectively, "a process is still running, do you want to kill it?"

After I closed it, I thought it was kinda weird. SU and Apt Autoremove was all that I had run in that terminal.

I thought that I would ask about it. Thank You.

Code: Select all

Snapshot created on: 20241228_1235
System:
  Kernel: 6.12.11-2-liquorix-amd64 [6.12-14~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/vmlinuz-6.12.11-2-liquorix-amd64
    root=UUID=<filter> ro nosplash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7 dm: SDDM
    Distro: MX-23.5_ahs_x64 Libretto October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ProArt X670E-CREATOR WIFI v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 1904 date: 01/29/2024
CPU:
  Info: model: AMD Ryzen 9 7950X3D bits: 64 type: MT MCP MCM arch: Zen 4 gen: 5 level: v4
    note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x61 (97) stepping: 2
    microcode: 0xA601206
  Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 dies: 2 smt: enabled cache: L1: 1024 KiB
    desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB desc: 16x1024 KiB L3: 128 MiB desc: 1x32 MiB, 1x96 MiB
  Speed (MHz): avg: 3319 high: 4200 min/max: 3000/5759 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 3000 2: 2832 3: 3000 4: 3000 5: 4200 6: 3000
    7: 3000 8: 3605 9: 3808 10: 4200 11: 3583 12: 3000 13: 3000 14: 3000 15: 4200 16: 3000 17: 3000
    18: 3000 19: 3000 20: 3000 21: 3000 22: 3000 23: 3000 24: 3000 25: 4200 26: 4200 27: 3000
    28: 4200 29: 3000 30: 4200 31: 3000 32: 3000 bogomips: 268302
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional; STIBP: always-on;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD vendor: Sapphire driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: DP-2 empty: DP-1, HDMI-A-1, HDMI-A-2, Writeback-1 bus-ID: 03:00.0
    chip-ID: 1002:747e class-ID: 0300
  Device-2: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none
    empty: DP-3, DP-4, HDMI-A-3, Writeback-2 bus-ID: 6e:00.0 chip-ID: 1002:164e class-ID: 0300
    temp: 34.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 678x382mm (26.69x15.04") s-diag: 778mm (30.64")
  Monitor-1: DP-2 mapped: DisplayPort-1 model: Dell S3220DGF serial: <filter> built: 2020
    res: 2560x1440 dpi: 93 gamma: 1.2 size: 697x392mm (27.44x15.43") diag: 806mm (31.7") ratio: 16:9
    modes: max: 2560x1440 min: 720x400
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: AMD Radeon RX 7800 XT (radeonsi navi32 LLVM
    15.0.6 DRM 3.59 6.12.11-2-liquorix-amd64) direct-render: Yes
Audio:
  Device-1: AMD driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
  Device-2: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 6e:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 6e:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.12.11-2-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Aquantia AQC113CS NBase-T/IEEE 802.3bz Ethernet [AQtion] vendor: ASUSTeK ProArt
    X570-CREATOR WIFI driver: atlantic v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 1 link-max:
    lanes: 2 port: N/A bus-ID: 0b:00.0 chip-ID: 1d6a:94c0 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  IF-ID-1: nordtun state: unknown speed: 10000 Mbps duplex: full mac: N/A
Drives:
  Local Storage: total: 32.83 TiB used: 10.4 TiB (31.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD BLACK SN770 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 731100WD temp: 20.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: TeamGroup model: TM8FPW004T size: 3.73 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: SN12717 temp: 38.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD101KFBX-68R56N0 size: 9.1 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 0A03 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST20000NM007D-3DJ103 size: 18.19 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: SN01 scheme: GPT
Partition:
  ID-1: / raw-size: 249.98 GiB size: 245 GiB (98.01%) used: 62.5 GiB (25.5%) fs: ext4
    dev: /dev/dm-0 maj-min: 253:0 mapped: luks-<filter>
  ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 537.5 MiB (55.2%) fs: ext4
    dev: /dev/nvme1n1p2 maj-min: 259:5
  ID-3: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 44.4 MiB (8.7%) fs: vfat
    dev: /dev/nvme1n1p1 maj-min: 259:4
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 39.0 C mobo: 25.0 C
  Fan Speeds (RPM): N/A
  GPU: device: amdgpu temp: 35.0 C mem: 53.0 C fan: 0 watts: 16.00 device: amdgpu temp: 34.0 C
Repos:
  Packages: pm: dpkg pkgs: 3005 libs: 1572 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/amdgpu-proprietary.list
  Active apt repos in: /etc/apt/sources.list.d/amdgpu.list
    1: deb https://repo.radeon.com/amdgpu/5.7.2/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://la.mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
    1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/rocm.list
    1: deb [arch=amd64] https://repo.radeon.com/rocm/apt/5.7.2 focal main
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
Info:
  Processes: 666 Uptime: 13m wakeups: 1 Memory: 125.01 GiB used: 2.95 GiB (2.4%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Wed Jan 29, 2025 1:28 pm**

When you open a Terminal, you are creating a bash process owned by your user.
When you su, you are creating another bash process owned by root.
Since there are two processes running and clicking the X only kills the foreground one, you get that message.
Better practice is to use exit to exit the root bash before you close the terminal.
In the scenario you are describing what you did won't cause any problems. There were no processes still running inside the user bash except the root bash.

Posted: **Wed Jan 29, 2025 5:55 pm**

THANKS! @timkb4cq
I hadn't noticed it doing that before. I wasn't too worried, I wondered if it signaled something. I appreciate it.

Posted: **Wed Jan 29, 2025 7:00 pm**

Perhaps easier with using using sudo instead of running another bash as root:
E.g with

Code: Select all

sudo apt update && sudo apt full-upgrade

or

Code: Select all

sudo apt autoremove

b/c when those commadn finsh, you can close the the terminal as no other bash is running.
Also note: running just "su" to get a root-termina prompt

Code: Select all

su

will keep quite a number of environment vars pointing to user home.
E.g here demonstrate with my user "fehlix"

Code: Select all

root@mx234-386:/home/fehlix/Desktop# printenv | grep -E 'fehlix|1000' | sort
LOGNAME=fehlix
PWD=/home/fehlix/Desktop
USER=fehlix
XAUTHORITY=/home/fehlix/.Xauthority
XDG_CACHE_HOME=/home/fehlix/.cache
XDG_CONFIG_HOME=/home/fehlix/.config
XDG_DATA_DIRS=/usr/share/xfce4:/home/fehlix/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/fehlix
XDG_RUNTIME_DIR=/run/user/1000

which can create lot off issues, in case you start from the su-root prompt a GUI app,
Look here what I got now, after running two apps:

Code: Select all

find ~ -user root -ls
   529842      4 -rw-r--r--   1 root     root          237 Jan 30 00:52 /home/fehlix/.config/MX-Linux/mx-packageinstaller.conf
   529915      4 -rw-r--r--   1 root     root          202 Jan 30 00:53 /home/fehlix/.config/MX-Linux/mx-repo-manager.conf

You suddenly have root-owned files within your home. In this case probably not big issue,
but can create a lot of issues if other files are involved.
Bottom line:
Better run just with "sudo" any terminal command, try to avoid root-terminal.

Posted: **Wed Jan 29, 2025 7:18 pm**

Hi @fehlix,

Sometime in the last couple of years, xfce terminal's sudo stopped accepting any password other than the current user, for sudo.
Using my non-admin account, my usual one, makes that a problem. I suppose that I could try another emulator for sudo-ing....

Thanks!

Posted: **Wed Jan 29, 2025 7:40 pm**

jj 5117 wrote: Wed Jan 29, 2025 7:18 pm Hi @fehlix,

Sometime in the last couple of years, xfce terminal's sudo stopped accepting any password other than the current user, for sudo.
Using my non-admin account, my usual one, makes that a problem. I suppose that I could try another emulator for sudo-ing....

Thanks!

sudo requires to enter your users login password, which is your user password - not roots password.

Posted: **Thu Jan 30, 2025 12:16 am**

Is your non admin account in the sudoers group?

Posted: **Thu Jan 30, 2025 2:58 am**

jj 5117 wrote: Wed Jan 29, 2025 7:18 pm Sometime in the last couple of years, xfce terminal's sudo stopped accepting any password other than the current user, for sudo.
Using my non-admin account, my usual one, makes that a problem. I suppose that I could try another emulator for sudo-ing....

sudo isn't an xfce-terminal feature. It's a program, same as "ps" or "ls". Any terminal emulator you run is going to run the same "ps" and the same "ls" and the same "sudo". The passwords that sudo accepts are controlled through /etc/sudoers, as are the privileges that those passwords grant, so i can't imagine a situation where you'd want a password to work that wasn't the current user's password.

Posted: **Fri Jan 31, 2025 8:01 pm**

@DukeComposed
"sudo isn't an xfce-terminal feature" -- I am well aware of that, thank you. You don't seem to have heard me aright.

@timkb4cq hanks
"Is your non admin account in the sudoers group?" -- Thanks Tim! I'll try that out and see if it works the way that I would like.

Thanks, all!

Posted: **Fri Jan 31, 2025 8:12 pm**

Oops, missed one.

@fehlix

"sudo requires to enter your users login password, which is your user password - not roots password." -- Yes, and for that non-admin account, the user password does no good. At one time, while on a non-admin account, xfce would prompt for and accept the password of an admin account to sudo. Xfce terminal now takes only the password of the current user.

Thank you very much!

Posted: **Fri Jan 31, 2025 9:09 pm**

jj 5117 wrote: Fri Jan 31, 2025 8:12 pm At one time, while on a non-admin account, xfce would prompt for and accept the password of an admin account to sudo. Xfce terminal now takes only the password of the current user.

This isn't about changes in Xfce or a particular terminal - but it might be that you are referring to the change in the policy of how user privileges are elevated in MX Linux, a change that took place in mid-2021. That is when the switch to accepting the current user password (given that the current user is authorized to sudo) was made. If you've been using an older version and semi-recently started using a new one, this change might seem more recent than it is.

Posted: **Fri Jan 31, 2025 9:23 pm**

@Nokkaelaein

Yes, I am aware of That, too. I described the effect, not the cause. Thank you.

Posted: **Fri Jan 31, 2025 9:27 pm**

jj 5117 wrote: Fri Jan 31, 2025 9:23 pm Yes, I am aware of That, too. I described the effect, not the cause. Thank you.

There probably still is a setting in MX Tweak that has something like "password for administrator tasks" and you can change it to "root" if that mode suits you better. I am not 100% sure if this is still the case, though.

Posted: **Fri Jan 31, 2025 10:31 pm**

That is how it has been set, ever since I noticed the described behavior.

Posted: **Fri Jan 31, 2025 11:27 pm**

jj 5117 wrote: Fri Jan 31, 2025 8:01 pm "sudo isn't an xfce-terminal feature" -- I am well aware of that, thank you. You don't seem to have heard me aright.

"Sometime in the last couple of years, xfce terminal's sudo stopped accepting any password other than the current user... I suppose that I could try another emulator[.]" is pretty clearly assigning ownership of sudo and its behavior to xfce4-terminal.

That's a little like saying "My Honda's radio stations aren't very good, maybe I suppose I could buy a different car."

Posted: **Sat Feb 01, 2025 12:13 am**

@DukeComposed
me: "My wheel fell off of my Dodge."
you: "Dodges aren't wheel features."
me: "really?"
you: "You said they were."

Is it the moon phase, or what?

Posted: **Sat Feb 01, 2025 12:38 am**

jj 5117 wrote: Sat Feb 01, 2025 12:13 am @DukeComposed
me: "My wheel fell off of my Dodge."
you: "Dodges aren't wheel features."
me: "really?"
you: "You said they were."

Is it the moon phase, or what?

This is nonsense.

Posted: **Sat Feb 01, 2025 12:44 pm**

@timkb4cq
@siamhie

Hi Guys,

This non-admin account was NOT in the sudo group. Future related problems SOLVED! ... After learning chmod and chown well enough to fix THOSE problems that have been piling up.

Thanks bunches!

Jim

Posted: **Sat Feb 01, 2025 5:55 pm**

jj 5117 wrote: Sat Feb 01, 2025 12:44 pm @timkb4cq
@siamhie

Hi Guys,

This non-admin account was NOT in the sudo group. Future related problems SOLVED! ... After learning chmod and chown well enough to fix THOSE problems that have been piling up.

Thanks bunches!

Jim

You're welcome but I'm not sure what I did?

Posted: **Sun Feb 02, 2025 12:16 am**

(chuckles) Hi @siamhie, @fehlix ,

Too many cats.

At a minimum, fehlix kept me mindful of file ownership and permissions problems, and gave me some commands to explore with.

:-)

MX Linux Forum

Curious? Xfce-4 terminal window.

Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window. [Solved]

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.

Re: Curious? Xfce-4 terminal window.