Page 1 of 2
A problem with gufw
Posted: Mon Dec 05, 2022 4:06 am
by spc
It doesn't run from menu at all. When running from command line (sudo gufw) there is such information in terminal:
"System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: The device is turned off
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: The device is turned off"
/usr/bin/gufw: line 2: [: =: unary operator expected
ls: cannot access '/usr/lib/python*/site-packages/gufw/gufw.py': No such file or directory
and then the gufw window appears
(MX 21 64 bit with all updates)
Re: A problem with gufw
Posted: Mon Dec 05, 2022 4:35 am
by spc
Before the line: "/usr/bin/gufw: line 2: [: =: unary operator expected"
"System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: The device is turned off
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: The device is turned off"
Re: A problem with gufw
Posted: Mon Dec 05, 2022 5:27 am
by Eadwine Rose
Quick system info, please, thank you.
Re: A problem with gufw
Posted: Mon Dec 05, 2022 5:34 am
by spc
Eadwine Rose wrote: Mon Dec 05, 2022 5:27 am
Quick system info, please, thank you.
Code: Select all
System: Kernel: 5.10.0-18-amd64 [5.10.140-1] x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/vmlinuz-5.10.0-18-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7
dm: LightDM 1.26.0 Distro: MX-21.2.1_x64 Wildflower September 18 2022
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: SAMSUNG product: RC410/RC510/RC710 v: N/A serial: <filter>
Chassis: type: 9 serial: <filter>
Mobo: SAMSUNG model: RC410/RC510/RC710 serial: <filter> BIOS: Phoenix
v: 03HU.M008.20110119.KSY date: 01/19/2011
Battery: ID-1: BAT1 charge: 28.5 Wh (80.1%) condition: 35.6/47.5 Wh (75.0%) volts: 10.5
min: 10.8 model: SAMSUNG Electronics type: Li-ion serial: N/A status: Unknown
CPU: Info: Dual Core model: Intel Core i3 M 380 bits: 64 type: MT MCP arch: Nehalem
family: 6 model-id: 25 (37) stepping: 5 microcode: 7 cache: L2: 3 MiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20215
Speed: 1135 MHz min/max: 933/2533 MHz Core speeds (MHz): 1: 1135 2: 1163 3: 1258
4: 1092
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP:
conditional, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Samsung Co driver: i915
v: kernel bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
Device-2: NVIDIA GT218M [GeForce 315M] vendor: Samsung Co driver: N/A
alternate: nouveau bus-ID: 02:00.0 chip-ID: 10de:0a7a class-ID: 0302
Device-3: DigiTech WebCam SCB-1110M type: USB driver: uvcvideo bus-ID: 1-1.4:3
chip-ID: 1210:0909 class-ID: 0e02
Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: loaded: intel
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3286x1080 s-dpi: 96 s-size: 869x285mm (34.2x11.2")
s-diag: 915mm (36")
Monitor-1: LVDS1 res: 1366x768 hz: 60 dpi: 101 size: 344x194mm (13.5x7.6")
diag: 395mm (15.5")
Monitor-2: HDMI1 res: 1920x1080 hz: 75 dpi: 102 size: 480x270mm (18.9x10.6")
diag: 551mm (21.7")
OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.3.5
direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Samsung Co
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403
Device-2: NVIDIA High Definition Audio vendor: Samsung Co driver: snd_hda_intel
v: kernel bus-ID: 02:00.1 chip-ID: 10de:0be3 class-ID: 0403
Sound Server-1: ALSA v: k5.10.0-18-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Broadcom BCM4313 802.11bgn Wireless Network Adapter vendor: Askey driver: wl
v: kernel modules: bcma port: 2000 bus-ID: 03:00.0 chip-ID: 14e4:4727 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Samsung Co
driver: r8169 v: kernel port: 4000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth: Device-1: Broadcom Broadcom BCM2070 Bluetooth Device type: USB driver: btusb v: 0.8
bus-ID: 2-1.3:4 chip-ID: 0a5c:219c class-ID: fe01 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 34 state: up address: <filter> bt-v: 2.0 lmp-v: 3.0
sub-v: 4203 hci-v: 3.0 rev: 274
Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch hold sniff park
link-mode: slave accept service-classes: rendering, capturing, object transfer, audio
Drives: Local Storage: total: 1.59 TiB used: 329.78 GiB (20.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABD075 size: 698.64 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400
serial: <filter> rev: 4M scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Toshiba model: MQ04UBF100
size: 931.51 GiB block-size: physical: 512 B logical: 512 B type: HDD rpm: 5400
serial: <filter> scheme: MBR
Partition: ID-1: / raw-size: 41.51 GiB size: 40.56 GiB (97.71%) used: 8.05 GiB (19.9%) fs: ext4
dev: /dev/dm-0 maj-min: 253:0 mapped: root.fsm
ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 187 MiB (19.2%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 650.59 GiB size: 639.3 GiB (98.27%) used: 90.61 GiB (14.2%)
fs: ext4 dev: /dev/dm-2 maj-min: 253:2 mapped: 1.home.fsm
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 5.48 GiB used: 468.6 MiB (8.3%) priority: -2
dev: /dev/dm-1 maj-min: 253:1 mapped: swap
Sensors: System Temperatures: cpu: 55.0 C mobo: 55.0 C
Fan Speeds (RPM): N/A
Repos: Packages: note: see --pkg apt: 2244 lib: 1210 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirrors.ocf.berkeley.edu/mx-packages/mx/repo/ bullseye main non-free
Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info: Processes: 299 Uptime: 8d 26m wakeups: 12 Memory: 3.64 GiB used: 1.84 GiB (50.6%)
Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A
alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06
Boot Mode: BIOS (legacy, CSM, MBR)
Re: A problem with gufw
Posted: Mon Dec 05, 2022 5:57 am
by linexer2016
Have you tried booting with SystemD as a means of seeing if the problem exists therein too? You seem to be running sysvinit but that error message you received suggests your system is looking for SystemD. Anyway, it would be interesting to see what happens when you boot with SystemD which you should be able to find in your bootup menus under Advanced MX ....
Re: A problem with gufw
Posted: Mon Dec 05, 2022 6:04 am
by Huckleberry Finn
This thread may be useful (it was solved with the patch (posts #11 - 13 )
https://forum.mxlinux.org/viewtopic.php?t=70979
Re: A problem with gufw
Posted: Mon Dec 05, 2022 6:35 am
by spc
Thanx. I've read this thread. In the end, the patch didn't seem to fix problems. It removed the original error but generated new problems.
It's weird by the way. After installing the system from oryginal source, the firewall, one of the most important things in the system, does not work as it should.
Re: A problem with gufw
Posted: Mon Dec 05, 2022 6:39 am
by Huckleberry Finn
In fact , the non-working one is just the gui, probably
ufw is ok (you can try in terminal as in that thread.)
Meanwhile, those errors are normal (ignorable) cause it's the same on live session (official MX iso) and it still gets launched with just
gufw (without sudo) at the end.
Re: A problem with gufw
Posted: Mon Dec 05, 2022 6:45 am
by spc
Huckleberry Finn wrote: Mon Dec 05, 2022 6:39 am
In fact , the non-working one is just the gui, probably
ufw is ok (you can try in terminal as in that thread.)
Meanwhile, those errors are normal (ignorable) cause it's the same on live session (official MX iso) and it still gets launched with just
gufw (without sudo) at the end.
"ignorable" should not be "normal" :)
and it still gets launched with just gufw (without sudo) at the end
Try again. Probably it won't work the second time. For me it worked only the first time.
Re: A problem with gufw
Posted: Mon Dec 05, 2022 6:50 am
by Huckleberry Finn
Yes but, the last lines (... line xx ... xyz expected ... no such file etc.) belong to the gufw itself (non-MX) .. And those related to Systemd are normal (you can see them with some others, too) as a systemd-shim is being used by MX on SysV ..