Автор Тема: P9 Simple Linux not shutting down on desktop  (Прочитано 58434 раз)

Оффлайн Δημητριος

  • Давно тут
  • **
  • Сообщений: 276
hello again    this is the continuation of this topic
здравствуйте еще раз это продолжение этого topic

перевод был сделан с помощью Яндекс перевода
the translation has been done with the help of yandex translate
Цитировать
Ελληνικά
αποφάσισα να κανω ξανα εγκατασταση την πλατφορμα P9 με τα Simple Linux P9
όμως αντιμετωπίζω ξανά το ίδιο  πρόβλημα- όπως πάγωμα του υπολογιστή --όμως  αφαίρεσα το  xfce4-plugin-sensor και σταμάτησε, τουλαχιστον τωρα ,τα παγώματα, και έκανα ενημέρωση τον πυρήνα  με την εντωλή update-kernel -- αλλά  και to κυρίως πρόβλημα ειναι, ότι δεν τερματίζει όταν τον κλείνω . το πρόβλημα αυτό το αντιμετωπίζω σε όλες τις διανομές p9 , και η Rosa όχι μόνο δεν τερματίζει αλλά ούτε  επανεκκίνηση   δεν κάνει απο live cd . Εκτελώντας την εντολή
Цитировать
(journalctl -b 0)
βρήκα τις παρακάτω γραμμές , όμως το τραγικό είναι, ότι δεν εχω UPS .. :-o μπορει να διορθωθεί το προβλημα αυτο ??? σας ευχαριστω 
   

Цитировать
Ρωσικά
Я решил переустановить платформу с простой Линукс Р9 Р9
но я с той же проблемой снова -- таких как зависание компьютера --но я удалил xfce4-плагин-сенсор и перестал, по крайней мере, теперь замирает, и я обновил ядро из терминал командой update-kernel-- но основная проблема в том, что не закрыли, когда я закрываю его . с этой проблемой я сталкиваюсь во всех дистрибутивах P9 ,и Rosa не только выключается, но и не перезапускается с Live cd. Выполнив команду 
Цитировать
(journalctl -b 0)
я нашел следующие строки  но самое печальное, что у меня нет взлетов.эту проблему можно исправить.  ???спасибо

Цитировать
Αγγλικά
I decided to reinstall platform P9 with Simple Linux P9
but I'm having the same problem again -- like freezing the computer -- but I removed the xfce4-plugin-sensor and stopped, at least now, the freezes, and I updated the kernel from terminal with command update-kernel -- but the main problem is, it doesn't shut down when I close it . this problem I face in all P9 distributions ,and Rosa not only shutdown, but does not restart from Live cd.Executing the command
Цитировать
(journalctl -b 0) I found the following lines,but the tragic thing is, I don'T have UPS. :-o can fix this problem ??? thanks you

journalctl -b 0
Νοε 21 13:03:25 user-PC apcupsd[3020]: apcupsd FATAL ERROR in smartsetup.c at line 155
                                          PANIC! Cannot communicate with UPS via serial port.
                                          Please make sure the port specified on the DEVICE directive is correct,
                                          and that your cable specification on the UPSCABLE directive is correct.
Νοε 21 13:03:25 user-PC apcupsd[3020]: apcupsd error shutdown completed
Νοε 21 13:03:32 user-PC systemd[1]: systemd-hostnamed.service: Succeeded.
Νοε 21 13:03:38 user-PC nmbd[3041]: [2020/11/21 13:03:38.488337,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Νοε 21 13:03:38 user-PC nmbd[3041]:   *****
Νοε 21 13:03:38 user-PC nmbd[3041]:
Νοε 21 13:03:38 user-PC nmbd[3041]:   Samba name server USER-PC is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.154
Νοε 21 13:03:38 user-PC nmbd[3041]:
Νοε 21 13:03:38 user-PC nmbd[3041]:   *****
Νοε 21 13:03:41 user-PC lightdm[2807]: pam_tcb(lightdm:auth): Authentication passed for user from (uid=0)
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Killing process 2771 (lightdm) with signal SIGTERM.
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Killing process 2782 (lightdm-gtk-gre) with signal SIGTERM.
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Killing process 2800 (at-spi-bus-laun) with signal SIGTERM.
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Killing process 2805 (dbus-daemon) with signal SIGTERM.
Νοε 21 13:03:41 user-PC systemd[1]: Stopping Session 1 of user _ldm.
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Succeeded.
Νοε 21 13:03:41 user-PC systemd[1]: Stopped Session 1 of user _ldm.
Νοε 21 13:03:41 user-PC lightdm[2807]: pam_tcb(lightdm:session): Session opened for user by (uid=0)
Νοε 21 13:03:41 user-PC systemd-logind[2625]: Removed session 1.
Νοε 21 13:03:41 user-PC systemd[1]: Created slice User Slice of UID 500.
Νοε 21 13:03:41 user-PC systemd[1]: Starting User Runtime Directory /run/user/500...
Νοε 21 13:03:41 user-PC systemd-logind[2625]: New session 3 of user user.
Νοε 21 13:03:41 user-PC systemd[1]: Started User Runtime Directory /run/user/500.
Νοε 21 13:03:41 user-PC systemd[1]: Starting User Manager for UID 500...
Νοε 21 13:03:41 user-PC systemd[3058]: pam_tcb(systemd-user:session): Session opened for user by (uid=0)
обновлено 25/11/20 это мое оборудование.
updated 25/11/20 this is my equipment.
Цитировать

my pc


my motherboard

M3N78D FX

    Supports AM3+ Processor, 8-Core CPU
    Solid Capacitor for CPU Power
    Supports Dual Channel DDR3 1800(OC)
    Supports Gigabit LAN 10/100/1000 Mb/s
    7.1 CH HD Audio (VIA® VT1718S Audio Codec)
    Supports ASRock XFast RAM, XFast LAN, XFast USB Technologies
    Supports ASRock Instant Boot, Instant Flash, OC DNA, APP Charger
    Free Bundle : CyberLink MediaEspresso 6.5 Trial
- Support for Socket AM3+ processors
- Support for Socket AM3 processors: AMD Phenom™ II X6 / X4 / X3 / X2 (except 920 / 940) / Athlon II X4 / X3 / X2 / Sempron processors
- Supports 8-Core CPU
- Supports CPU up to 140W
- AMD LIVE!™ Ready
- Supports AMD's Cool 'n' Quiet Technology
- FSB 2600 MHz (5.2 GT/s)
- Supports Untied Overclocking Technology
- Supports Hyper-Transport 3.0 (HT 3.0) Technology
Chipset
- NVIDIA® nForce 720D
Memory
- Dual Channel DDR3 memory technology
- 4 x DDR3 DIMM slots
- Supports DDR3 1800(OC)/1600(OC)/1333/1066/800 non-ECC, un-buffered memory
- Max. capacity of system memory: 16GB*

*Due to the operating system limitation, the actual memory size may be less than 4GB for the reservation for system usage under Windows® 32-bit OS. For Windows® 64-bit OS with 64-bit CPU, there is no such limitation.
BIOS
- 8Mb AMI Legal BIOS
- Supports "Plug and Play"
- ACPI 1.1 Compliance Wake Up Events
- Supports jumperfree
- SMBIOS 2.3.1 Support
- VCCM, NB Voltage Multi-adjustment
- Supports NVIDIA® NVCC (NVIDIA® Clock Calibration)
Graphics
- n/a
Audio
- 7.1 CH HD Audio (VIA® VT1718S Audio Codec)
LAN
- Gigabit LAN 10/100/1000 Mb/s
- Giga PHY Realtek RTL8211CL
- Supports Wake-On-LAN
- Supports PXE
Slots
- 1 x PCI Express 2.0 x16 slot (blue @ x16 mode)
- 3 x PCI Express x1 slots
- 3 x PCI slots
Connector
- 4 x SATA2 3.0 Gb/s connectors, support RAID (RAID 0, RAID 1, RAID 0+1, RAID 5 and JBOD), NCQ, AHCI and Hot Plug functions
- 1 x ATA133 IDE connector (supports 2 x IDE devices)
- 1 x Floppy connector
- 1 x COM port header
- 1 x HDMI_SPDIF header
- 1 x Chassis Intrusion header
- 1 x Power LED header
- CPU/Chassis/Power FAN connector
- 24 pin ATX power connector
- 8 pin 12V power connector
- CD in header
- Front panel audio connector
- 3 x USB 2.0 headers (support 6 USB 2.0 ports)
Rear Panel I/O
I/O Panel
- 1 x PS/2 Mouse Port
- 1 x PS/2 Keyboard Port
- 1 x Coaxial SPDIF Out Port
- 1 x Optical SPDIF Out Port
- 4 x Ready-to-Use USB 2.0 Ports
- 2 x Powered eSATA2/USB Connectors
- 1 x RJ-45 LAN Port with LED (ACT/LINK LED and SPEED LED)
- HD Audio Jack: Side Speaker / Rear Speaker / Central / Bass / Line in / Front Speaker / Microphone
Unique Feature
- ASRock OC Tuner
- ASRock Intelligent Energy Saver
- ASRock Instant Boot
- ASRock Instant Flash
- ASRock OC DNA
- ASRock APP Charger
- ASRock XFast USB
- ASRock XFast LAN
- ASRock XFast RAM
- Hybrid Booster:
- CPU Frequency Stepless Control
- ASRock U-COP
- Boot Failure Guard (B.F.G.)
Support CD
- Drivers, Utilities, AntiVirus Software (Trial Version), CyberLink MediaEspresso 6.5 Trial
Accessories
- Quick Installation Guide, Support CD, I/O Shield
- 2 x SATA Data Cables
Hardware Monitor
- CPU Temperature Sensing
- Chassis Temperature Sensing
- CPU, Chassis, Power Fan Tachometer
- CPU Quiet Fan
- CASE OPEN detection
- Voltage Monitoring: +12V, +5V, +3.3V, CPU Vcore
Form Factor
- ATX Form Factor: 12.0-in x 7.5-in, 30.5 cm x 19.1 cm
- Solid Capacitor for CPU Power
OS
- Microsoft® Windows® 7 / 7 64-bit / Vista™ / Vista™ 64-bit / XP / XP Media Center / XP 64-bit compliant
Certifications
- FCC, CE
- ErP/EuP Ready (ErP/EuP ready power supply is required)

my CPU

AMD  8350FX

of CPU Cores 8

of Threads  8

Base Clock 4.0GHz

Max Boost Clock Up to 4.2GHz

Total L1 Cache 384KB
Total L2 Cache 8MB
Total L3 Cache 8MB

Unlocked Yes

CMOS  32nm SOI

Package   AM3+

PCI Express® Version n/a

Default TDP / TDP   125W

Max Temps     61°C

MY Graphic Card
Nvidia 650ti BOOST
GPU Engine Specs:
768CUDA Cores
980Base Clock (MHz)
1033Boost Clock (MHz)
62.7Texture Fill Rate (billion/sec)
Memory Specs:
6.0 GbpsMemory Clock
2048 MBStandard Memory Config
GDDR5Memory Interface
192-bitMemory Interface Width
144.2Memory Bandwidth (GB/sec)
Feature Support:
GPU Boost, PhysX, TXAA, NVIDIA G-SYNC-readyImportant Technologies
3D Vision, CUDA, DirectX 11, Adaptive VSync, FXAA, NVIDIA Surround, SLIOther Supported Technologies
4.3OpenGL
11Microsoft DirectX 11.2 API
PCI Express 3.0Bus Support1
YesCertified for Windows 7
Yes3D Vision Ready
Display Support:
4096x2160Maximum Digital Resolution2
2048x1536Maximum VGA Resolution
YesHDCP
YesHDMI3
4 DisplaysMulti Monitor
One Dual Link DVI-I, One Dual Link DVI-D, One HDMI, One DisplayPortStandard Display Connectors
InternalAudio Input for HDMI
Standard Graphics Card Dimensions:
9.5 inchesLength
4.376 inchesHeight
Dual-widthWidth
Thermal and Power Specs:
97 CMaximum GPU Temperature (in C)
134 WMaximum Graphics Card Power (W)
450 WMinimum System Power Requirement (W)4
One 6-pinSupplementary Power Connectors
3D Vision Ready
Yes3D Blu-Ray
Yes3D Gaming
Yes3D Vision Live (Photos and Videos)

and 8G memory Ram


« Последнее редактирование: 25.11.2020 18:54:47 от Δημητριος »

Оффлайн gosts 87

  • Завсегдатай
  • *
  • Сообщений: 1 798
  • Дмитрий/Dmitry/德米特里/दिमित्री
Re: P9 Simple Linux not shutting down on desktop
« Ответ #1 : 21.11.2020 15:38:11 »
Объясню. У пользователя Δημητριος не происходит выключение компьютера. На этапе выключения он просто зависает.

Оффлайн Skull

  • Глобальный модератор
  • *****
  • Сообщений: 19 579
    • Домашняя страница
    • Email
Re: P9 Simple Linux not shutting down on desktop
« Ответ #2 : 21.11.2020 21:21:40 »
Объясню. У пользователя Δημητριος не происходит выключение компьютера. На этапе выключения он просто зависает.
acpi=off в параметрах grub пробовали?
Андрей Черепанов (cas@)

Оффлайн Δημητριος

  • Давно тут
  • **
  • Сообщений: 276
Re: P9 Simple Linux not shutting down on desktop
« Ответ #3 : 21.11.2020 21:45:06 »
acpi=off в параметрах grub пробовали?

Цитировать
Ελληνικα
το εχω δοκιμασει με acpi off κατα την  εγκατασταση της διανομής  SimleLinuxP9 πριν πολύ καιρο ,και  το συστημα αναγνώριζε μόνο ένα πυρήνα, και ηταν ασταθες ,θα υπάρξει καποια διαφορα εαν το κανω τωρα απο το grub;

Цитировать
Ρωσικά
Я тестировал его с выключенным acpi при установке дистрибутива SimleLinuxP9 давным-давно ,и система распознала только один основной процессор, и он был нестабильным, будет некоторая разница, если я сделаю это сейчас из grub?


Цитировать
Αγγλικά
I tested it with acpi off when installing the SimleLinuxP9 distribution a long time ago ,and the system  recognized only one core cpu, and it was unstable, there will be some difference if I do it now from grub?

Оффлайн gosts 87

  • Завсегдатай
  • *
  • Сообщений: 1 798
  • Дмитрий/Dmitry/德米特里/दिमित्री
Re: P9 Simple Linux not shutting down on desktop
« Ответ #4 : 21.11.2020 21:51:05 »
Try this and report the results.

Оффлайн Δημητριος

  • Давно тут
  • **
  • Сообщений: 276
Re: P9 Simple Linux not shutting down on desktop
« Ответ #5 : 21.11.2020 23:11:00 »
Try this and report the results.

Цитировать
i modified  grub by during startup from letter E  and I wrote acpi=off and after ctrl-x and   ....he accepted it.
but login not appear all black !!!!

Цитировать
я модифицировал grubby во время запуска из буквы E и написал acpi=off, а после ctrl-x и ....он принял его.
но логин не появляется продолжить черные !!!!

Цитировать
PS: I came up with this method ,because through linux and specifically from the archive GRUB_CMDLINE_LINUX_DEFAULT , I wrote the order acpi=off ,at the end of line,  i saved and after i make update the kernel from oder update-kernels
after all 
 when i restart my pc , I found that there were no changes in grub....
Цитировать
PS: Я придумал этот метод ,потому что через linux и конкретно из архива GRUB_CMDLINE_LINUX_DEFAULT я написал заказ acpi=off, в конце строки я сохранил и после того ,как я сделаю обновление ядра из oder update-kernels
все-таки
когда я перезагрузил свой компьютер , я обнаружил, что в grub не было никаких изменений ... а
# 'default'    - add failsafe entry only for /boot/vmlinuz
# default: default
GRUB_VMLINUZ_FAILSAFE="default"

# Preload specific grub modules
#GRUB_PRELOAD_MODULES=''

# Set normal timeout
#GRUB_TIMEOUT="5"

# Set hidden timeout (do not show menu)
#GRUB_HIDDEN_TIMEOUT="3"

# Show timeout counter when hidden
#GRUB_HIDDEN_TIMEOUT_QUIET="TRUE"

GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=/dev/disk/by-uuid/19a93d64-3eea-4013-ae98-fc1585922f34 panic=30 splash acpi=off"
GRUB_CMDLINE_LINUX="failsafe vga=normal"
GRUB_TERMINAL_OUTPUT="gfxterm"
GRUB_GFXMODE="1280x1024x16"
GRUB_DEFAULT="saved"
GRUB_SAVEDEFAULT="true"
GRUB_BACKGROUND="/boot/grub/themes/slinux/boot.png"
# GRUB_WALLPAPER is a deprecated parameter not supported by upstream
# It's support in OS ALT is not guaranteed in future releases --
# use GRUB_BACKGROUND instead for branding development
GRUB_WALLPAPER="/boot/grub/themes/slinux/boot.png"
GRUB_COLOR_NORMAL="white/dark-gray"
GRUB_COLOR_HIGHLIGHT="black/white"

# This is especially important as EFI Boot Manager label
GRUB_DISTRIBUTOR="ALT Linux"

# This defines /boot/efi/EFI subdir name
GRUB_BOOTLOADER_ID="altlinux"
GRUB_THEME="/boot/grub/themes/slinux/theme.txt"
GRUB_AUTOUPDATE_DEVICE="/dev/disk/by-id/ata-TOSHIBA_HDWD110_Z787HN0FS"
GRUB_AUTOUPDATE_FORCE="no"


« Последнее редактирование: 21.11.2020 23:45:32 от Δημητριος »

Оффлайн gosts 87

  • Завсегдатай
  • *
  • Сообщений: 1 798
  • Дмитрий/Dmitry/德米特里/दिमित्री
Re: P9 Simple Linux not shutting down on desktop
« Ответ #6 : 21.11.2020 23:14:26 »
Those. Is your account not showing up?

Оффлайн gosts 87

  • Завсегдатай
  • *
  • Сообщений: 1 798
  • Дмитрий/Dmitry/德米特里/दिमित्री
Re: P9 Simple Linux not shutting down on desktop
« Ответ #7 : 21.11.2020 23:16:31 »
продолжить черные !!!!
Black screen?

Оффлайн Δημητριος

  • Давно тут
  • **
  • Сообщений: 276
Re: P9 Simple Linux not shutting down on desktop
« Ответ #8 : 21.11.2020 23:36:47 »
Цитировать
да черный экран , во время системного процесса буквы становятся большими ,что означает ,что он не загружает графику
, возможно, именно поэтому экран входа в систему не отображается

Цитировать
yes Black screen , during the systemd process ,letters is to big ,which means it doesn't load the graphics
maybe that's why the login screen is not displayed
« Последнее редактирование: 21.11.2020 23:40:18 от Δημητριος »

Оффлайн gosts 87

  • Завсегдатай
  • *
  • Сообщений: 1 798
  • Дмитрий/Dmitry/德米特里/दिमित्री
Re: P9 Simple Linux not shutting down on desktop
« Ответ #9 : 21.11.2020 23:44:21 »
I am confused by this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=/dev/disk/by-uuid/19a93d64-3eea-4013-ae98-fc1585922f34 panic=30 splash acpi=off"
highlighted in red.

Оффлайн Speccyfighter

  • Мастер
  • ***
  • Сообщений: 9 959
Re: P9 Simple Linux not shutting down on desktop
« Ответ #10 : 22.11.2020 01:15:00 »
journalctl -b 0
...
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Killing process 2771 (lightdm) with signal SIGTERM.
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Killing process 2782 (lightdm-gtk-gre) with signal SIGTERM.
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Killing process 2800 (at-spi-bus-laun) with signal SIGTERM.
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Killing process 2805 (dbus-daemon) with signal SIGTERM.
Νοε 21 13:03:41 user-PC systemd[1]: Stopping Session 1 of user _ldm.
Νοε 21 13:03:41 user-PC systemd[1]: session-1.scope: Succeeded.
Νοε 21 13:03:41 user-PC systemd[1]: Stopped Session 1 of user _ldm.
...

Killing lightdm and dbus-daemon with SIGTERM?
Ok. Good.


journalctl -b 0
...
...
Νοε 21 13:03:41 user-PC lightdm[2807]: pam_tcb(lightdm:session): Session opened for user by (uid=0)
Νοε 21 13:03:41 user-PC systemd-logind[2625]: Removed session 1.
Νοε 21 13:03:41 user-PC systemd[1]: Created slice User Slice of UID 500.
Νοε 21 13:03:41 user-PC systemd[1]: Starting User Runtime Directory /run/user/500...
Νοε 21 13:03:41 user-PC systemd-logind[2625]: New session 3 of user user.
Νοε 21 13:03:41 user-PC systemd[1]: Started User Runtime Directory /run/user/500.
Νοε 21 13:03:41 user-PC systemd[1]: Starting User Manager for UID 500...
Νοε 21 13:03:41 user-PC systemd[3058]: pam_tcb(systemd-user:session): Session opened for user by (uid=0)

Open session after SIGTERM lightdm and SIGTERM dbus-daemon?
Why?! :-)
For what purpose? For what reason?


How it works in xfce -sysv:
Only closed and down - not open!
And only at the end 'dbus-daemon shutdown', - not at the beginning:
# grep -r 2020-11-19T20:36 ./var/log/ | awk '{$2=""; print $0}' | cut -f2- -d ':' | sort
2020-11-19T20:36:20.560174+03:00  UNSPECIFIED (__progname="pkexec" uid=500 euid=0): pam_tcb(polkit-1:session): Session opened for root by user(uid=500)
2020-11-19T20:36:20.560174+03:00  UNSPECIFIED (__progname="pkexec" uid=500 euid=0): pam_tcb(polkit-1:session): Session opened for root by user(uid=500)
2020-11-19T20:36:20.561190+03:00  pkexec[5848]: user: Executing command [USER=root] [TTY=unknown] [CWD=/home/user] [COMMAND=/usr/lib64/xfce4/session/xfsm-shutdown-helper --shutdown]
2020-11-19T20:36:20.561190+03:00  pkexec[5848]: user: Executing command [USER=root] [TTY=unknown] [CWD=/home/user] [COMMAND=/usr/lib64/xfce4/session/xfsm-shutdown-helper --shutdown]
2020-11-19T20:36:20.615141+03:00  shutdown[5857]: shutting down for system halt
2020-11-19T20:36:20.615141+03:00  shutdown[5857]: shutting down for system halt
2020-11-19T20:36:20.806819+03:00  init: Switching to runlevel: 0
2020-11-19T20:36:20.806819+03:00  init: Switching to runlevel: 0
2020-11-19T20:36:20.815984+03:00  gdm-binary[5259]: WARNING: gdm_slave_xioerror_handler: Фатальная ошибка X - Перезапуск :0
2020-11-19T20:36:20.815984+03:00  gdm-binary[5259]: WARNING: gdm_slave_xioerror_handler: Фатальная ошибка X - Перезапуск :0
2020-11-19T20:36:20.840661+03:00  gdm-binary[5259]: pam_tcb(gdm-autologin:session): Session closed for user
2020-11-19T20:36:20.840661+03:00  gdm-binary[5259]: pam_tcb(gdm-autologin:session): Session closed for user
2020-11-19T20:36:20.871819+03:00  su[5619]: pam_tcb(su:session): Session closed for root
2020-11-19T20:36:20.871819+03:00  su[5619]: pam_tcb(su:session): Session closed for root
<skip>
2020-11-19T20:36:23.492673+03:00  dm: rundm shutdown succeeded
2020-11-19T20:36:23.492673+03:00  dm: rundm shutdown succeeded
<skip>
2020-11-19T20:36:23.819771+03:00  crond: crond shutdown succeeded
2020-11-19T20:36:23.819771+03:00  crond: crond shutdown succeeded
2020-11-19T20:36:24.047117+03:00  acpid: exiting
2020-11-19T20:36:24.047117+03:00  acpid: exiting
2020-11-19T20:36:24.963377+03:00  acpid: acpid shutdown succeeded
2020-11-19T20:36:24.963377+03:00  acpid: acpid shutdown succeeded
2020-11-19T20:36:24.987563+03:00  rc: Stopping keytable: succeeded
2020-11-19T20:36:24.987563+03:00  rc: Stopping keytable: succeeded
2020-11-19T20:36:25.007461+03:00  rc: Stopping fbsetfont: succeeded
2020-11-19T20:36:25.007461+03:00  rc: Stopping fbsetfont: succeeded
2020-11-19T20:36:25.050321+03:00  chronyd[4981]: chronyd exiting
2020-11-19T20:36:25.050321+03:00  chronyd[4981]: chronyd exiting
2020-11-19T20:36:25.158593+03:00  chronyd: chronyd shutdown succeeded
2020-11-19T20:36:25.158593+03:00  chronyd: chronyd shutdown succeeded
<skip>
2020-11-19T20:36:25.217668+03:00  dbus-daemon[4105]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.0' (uid=0 pid=4208 comm="/usr/sbin/NetworkManager --pid-file=/var/run/Netwo") (using servicehelper)
<skip>
2020-11-19T20:36:25.362078+03:00  NetworkManager: NetworkManager shutdown succeeded
2020-11-19T20:36:25.362078+03:00  NetworkManager: NetworkManager shutdown succeeded
2020-11-19T20:36:25.388481+03:00  ModemManager[4289]: <info> Caught signal, shutting down...
2020-11-19T20:36:25.388481+03:00  ModemManager[4289]: <info> Caught signal, shutting down...
2020-11-19T20:36:25.390081+03:00  ModemManager[4289]: <info> ModemManager is shut down
2020-11-19T20:36:25.390081+03:00  ModemManager[4289]: <info> ModemManager is shut down
<skip>
2020-11-19T20:36:25.430884+03:00  network: #011Stopping lo:
2020-11-19T20:36:25.430884+03:00  network: #011Stopping lo:
<skip>
2020-11-19T20:36:25.553376+03:00  rc: Stopping network: succeeded
2020-11-19T20:36:25.553376+03:00  rc: Stopping network: succeeded
<skip>
2020-11-19T20:36:25.577488+03:00  bluetoothd[4474]: Disconnected from D-Bus. Exiting.
2020-11-19T20:36:25.577488+03:00  bluetoothd[4474]: Disconnected from D-Bus. Exiting.
<skip>
2020-11-19T20:36:25.578867+03:00  nm-dispatcher: System bus stopped. Exiting
2020-11-19T20:36:25.578867+03:00  nm-dispatcher: System bus stopped. Exiting
2020-11-19T20:36:25.686126+03:00  messagebus: dbus-daemon shutdown succeeded
2020-11-19T20:36:25.686126+03:00  messagebus: dbus-daemon shutdown succeeded
2020-11-19T20:36:25.819590+03:00  udevd: systemd-udevd shutdown succeeded
2020-11-19T20:36:25.819590+03:00  udevd: systemd-udevd shutdown succeeded

The system is completely down.

Оффлайн Δημητριος

  • Давно тут
  • **
  • Сообщений: 276
Re: P9 Simple Linux not shutting down on desktop
« Ответ #11 : 22.11.2020 01:35:52 »
Killing lightdm
when i stop  lightdm with command service lightdm stop ,he threw me out , like shutdown and stuck   how can I do that?
« Последнее редактирование: 22.11.2020 01:40:26 от Δημητριος »

Оффлайн Speccyfighter

  • Мастер
  • ***
  • Сообщений: 9 959
Re: P9 Simple Linux not shutting down on desktop
« Ответ #12 : 22.11.2020 07:23:26 »
Killing lightdm
when i stop  lightdm with command
service lightdm stop,he threw me out , like shutdown and stuck

On systemd systems, service management is done through the systemctl command:
https://wiki.archlinux.org/index.php/Systemd
systemctl $command $unit

how can I do that?

On Xfce systems, if Shut Down is selected from the Xfce menu, the command is executed with root privileges
pkexec /usr/lib{,64}/xfce4/session/xfsm-shutdown-helper --shutdown
$ /usr/lib{,64}/xfce4/session/xfsm-shutdown-helper --help
Usage:
  xfsm-shutdown-helper [OPTION?]
...
Application Options:
  --shutdown       Shutdown the system
  --restart        Restart the system
  --suspend        Suspend the system
  --hibernate      Hibernate the system

The same action can be performed with a command from the Xfce terminal
xfce4-session-logout --halt
LC_ALL=C xfce4-session-logout --help
Usage:
  xfce4-session-logout [OPTION?]
...
Application Options:
  -l, --logout             Log out without displaying the logout dialog
  -h, --halt               Halt without displaying the logout dialog
  -r, --reboot             Reboot without displaying the logout dialog
  -s, --suspend            Suspend without displaying the logout dialog
  --hibernate              Hibernate without displaying the logout dialog
  -f, --fast               Log out quickly; don't save the session
  -V, --version            Print version information and exit
  --display=DISPLAY        X display to use

Running xfce4-session-logout with no parameters brings up the graphical Exit Xfce menu window.
This is the same as Xfce Menu> Exit.
Запуск xfce4-session-logout без параметров, вызывает графическое окно меню Exit Xfce.
Это аналогично Меню Xfce > Выйти.


Shutdown commands executed as root (su -)
# poweroff
# shutdown -h now # Shutdown now
# halt -p # shutdown the system (if possible, otherwise halt)
# init 0 # shutdown the system (if possible, otherwise halt)
# telinit 0 # shutdown the system (if possible, otherwise halt)

Check which commands can shutdown your computer with SimplyLinux.

If the computer does not turn off, you need to boot into another system and look in the log for the reason for the failure to turn off the computer.

If this is not difficult for you, boot from a live USB stick with p9-xfce-sysv, and check the computer shutdown (is it just SimplyLinux or all altlinux problems on your computer?):
http://nightly.altlinux.org/p9/release/alt-p9-xfce-sysv-20200912-i586.iso
http://nightly.altlinux.org/p9/release/alt-p9-xfce-sysv-20200912-x86_64.iso
« Последнее редактирование: 22.11.2020 10:20:06 от Speccyfighter »

Оффлайн Speccyfighter

  • Мастер
  • ***
  • Сообщений: 9 959
Re: P9 Simple Linux not shutting down on desktop
« Ответ #13 : 22.11.2020 09:34:21 »
Загрузка slinux-live-9.0-x86_64 с USB флешки в Legacy mode и lowmem.
Удачное выключение выбором опции Shut Down из меню SimplyLinux 9.0:

Booting slinux-live-9.0-x86_64 from USB stick in Legacy mode and lowmem.
Successful shutdown by selecting the Shut Down option from the SimplyLinux 9.0 menu:
See attachment.
Смотри вложение.

First there was booting to live with saving the session and shutting down the computer through the Xfce SimplyLinux menu.
Then loading without saving the session and dumping the log from the specified directory to a file.

Сначала была загрузка в лайв с сохранением сессии и выключение компьютера через меню Xfce SimplyLinux .
Затем загрузка без сохранения сессии и сброс журнала из указанного каталога в файл.

Оффлайн Speccyfighter

  • Мастер
  • ***
  • Сообщений: 9 959
Re: P9 Simple Linux not shutting down on desktop
« Ответ #14 : 22.11.2020 11:08:06 »
But even with a successful shutdown, incorrect activation with activation failure is observed:
Activation after D-Bus shutdown.

Но даже при успешном выключении наблюдается некорректная активация с отказом активации:
Активация после того как D-Bus завершает работу.

Nov 22 11:43:59 localhost.localdomain dbus-daemon[562]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.
freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=686 comm="/usr/sbin/NetworkManager --no-daemon ")
Nov 22 11:43:59 localhost.localdomain dbus-daemon[562]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.