Page 61 of 67
Re: MX-21 beta 1 feedback thread
Posted: Fri Aug 27, 2021 8:22 am
by JayM
dolphin_oracle wrote: Fri Aug 27, 2021 8:15 am
JayM wrote: Fri Aug 27, 2021 8:00 am
On my favorite subject, Docklike Taskbar, is there a way to launch another instance of a pinned item? Left-clicking only opens the instance that's currently running and I don't see anything in the right-click context menu that allows me to open a new instance. I have to use the Whisker menu if I want to open another (for example) instance of Thunar where with real launchers in the panel I'd just have to click on the launcher again to open a second Thunar. I don't see anything in the wiki entry for Docklike about launching multiple instances of pinned apps either.
when we started, it had a "launch another" option in the right click menu, but that's apparently gone.
shift+left_click will do it though.
Shift+left click! Thanks, dolphin!
@Jerry3904 could you add this tip to the wiki? Because I'm bound to forget it and I'm
just smart enough to search the wiki for "docklike" when I have questions or get stuck.
Re: MX-21 beta 1 feedback thread
Posted: Fri Aug 27, 2021 8:44 am
by SwampRabbit
@JayM its already included in the wiki entry.
https://mxlinux.org/wiki/docklike-taskbar/
I miss the ”launch another” option that used to exist. Maybe it can be added back, I think (if I remember right) the reason it was removed was because the right-click menus got out of control with too many options.
I’ve been using the hot keys since, but for new users the menu item could be useful on first use.
Re: MX-21 beta 1 feedback thread
Posted: Fri Aug 27, 2021 9:58 am
by chrispop99
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet video=SVIDEO-1:d splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Portable System: Dell product: Latitude D630 v: N/A serial: <filter> Chassis:
type: 8 serial: <filter>
Mobo: Dell model: N/A serial: <filter> BIOS: Dell v: A07 date: 01/30/2008
Battery: ID-1: BAT0 charge: 48.1 Wh condition: 48.1/56.6 Wh (85%) volts: 12.6/11.1
model: Panasonic DELL DU1548 type: Li-ion serial: <filter> status: Full
CPU: Topology: Dual Core model: Intel Core2 Duo T7250 bits: 64 type: MCP arch: Core Merom
family: 6 model-id: F (15) stepping: D (13) microcode: A4 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 7979
Speed: 798 MHz min/max: 800/2001 MHz boost: enabled Core speeds (MHz): 1: 798 2: 798
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Dell Latitude D630
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a02
Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1280x800~60Hz
OpenGL: renderer: Mesa DRI Intel 965GM (CL) v: 2.1 Mesa 20.3.5 direct render: Yes
Audio: Device-1: Intel 82801H HD Audio vendor: Dell Latitude D630 driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:284b
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Broadcom and subsidiaries NetXtreme BCM5755M Gigabit Ethernet PCI Express
vendor: Dell driver: tg3 v: kernel port: 10c0 bus ID: 09:00.0 chip ID: 14e4:1673
IF: eth0 state: down mac: <filter>
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s
port: 10c0 bus ID: 0c:00.0 chip ID: 8086:4222
IF: wlan0 state: up mac: <filter>
Device-3: Dell Wireless 360 Bluetooth type: USB driver: btusb bus ID: 2-2:2
chip ID: 413c:8140
Drives: Local Storage: total: 62.45 GiB used: 6.21 GiB (9.9%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 58.69 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> scheme: MBR
ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 3.76 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR
Partition: ID-1: / raw size: 55.66 GiB size: 54.49 GiB (97.89%) used: 5.98 GiB (11.0%) fs: ext4
dev: /dev/sda1
ID-2: swap-1 size: 3.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 49.0 C mobo: N/A sodimm: 42.0 C
Fan Speeds (RPM): cpu: 0
Repos: 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 http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 191 Uptime: 1h 45m Memory: 1.93 GiB used: 648.0 MiB (32.8%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
When above machine is left powered up, once the Power Manager Display settings go to blank, it can't be recovered. Black screen. no response from mouse or keyboard.
It's possible to Ctrl-Alt-F1 to start another session, or to reboot.
Setting everything to Never leaves it running.
It hasn't happened with earlier version of MX Linux.
Chris
Re: MX-21 beta 1 feedback thread
Posted: Fri Aug 27, 2021 10:26 am
by Huckleberry Finn
@chrispop99 This may / may not be related but, have you tried when booted without the video=SVIDEO-1:d parameter ?
If still not: What about when "Lock Screen when ... going to sleep" unchecked in Power Manager ?
Re: MX-21 beta 1 feedback thread
Posted: Fri Aug 27, 2021 10:57 am
by chrispop99
Huckleberry Finn wrote: Fri Aug 27, 2021 10:26 am
@chrispop99 This may / may not be related but, have you tried when booted without the
video=SVIDEO-1:d parameter ?
If still not: What about when "Lock Screen when ... going to sleep" unchecked in Power Manager ?
Thanks for the suggestion, but neither of those fixed it.
Interestingly, when booting with post-4.9 kernels this machine needed that boot parameter in order to prevent boot times of more than three minutes, so I just added it out of habit. After removing it, boot time was normal, so it looks like it's not needed with the newer kernel.
(This machine is only a test box; I posted just as a data point.)
Chris
Re: MX-21 beta 1 feedback thread
Posted: Fri Aug 27, 2021 11:24 am
by dolphin_oracle
chrispop99 wrote: Fri Aug 27, 2021 9:58 am
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet video=SVIDEO-1:d splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Portable System: Dell product: Latitude D630 v: N/A serial: <filter> Chassis:
type: 8 serial: <filter>
Mobo: Dell model: N/A serial: <filter> BIOS: Dell v: A07 date: 01/30/2008
Battery: ID-1: BAT0 charge: 48.1 Wh condition: 48.1/56.6 Wh (85%) volts: 12.6/11.1
model: Panasonic DELL DU1548 type: Li-ion serial: <filter> status: Full
CPU: Topology: Dual Core model: Intel Core2 Duo T7250 bits: 64 type: MCP arch: Core Merom
family: 6 model-id: F (15) stepping: D (13) microcode: A4 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 7979
Speed: 798 MHz min/max: 800/2001 MHz boost: enabled Core speeds (MHz): 1: 798 2: 798
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Dell Latitude D630
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a02
Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1280x800~60Hz
OpenGL: renderer: Mesa DRI Intel 965GM (CL) v: 2.1 Mesa 20.3.5 direct render: Yes
Audio: Device-1: Intel 82801H HD Audio vendor: Dell Latitude D630 driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:284b
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Broadcom and subsidiaries NetXtreme BCM5755M Gigabit Ethernet PCI Express
vendor: Dell driver: tg3 v: kernel port: 10c0 bus ID: 09:00.0 chip ID: 14e4:1673
IF: eth0 state: down mac: <filter>
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s
port: 10c0 bus ID: 0c:00.0 chip ID: 8086:4222
IF: wlan0 state: up mac: <filter>
Device-3: Dell Wireless 360 Bluetooth type: USB driver: btusb bus ID: 2-2:2
chip ID: 413c:8140
Drives: Local Storage: total: 62.45 GiB used: 6.21 GiB (9.9%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 58.69 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> scheme: MBR
ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 3.76 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR
Partition: ID-1: / raw size: 55.66 GiB size: 54.49 GiB (97.89%) used: 5.98 GiB (11.0%) fs: ext4
dev: /dev/sda1
ID-2: swap-1 size: 3.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 49.0 C mobo: N/A sodimm: 42.0 C
Fan Speeds (RPM): cpu: 0
Repos: 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 http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 191 Uptime: 1h 45m Memory: 1.93 GiB used: 648.0 MiB (32.8%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
When above machine is left powered up, once the Power Manager Display settings go to blank, it can't be recovered. Black screen. no response from mouse or keyboard.
It's possible to Ctrl-Alt-F1 to start another session, or to reboot.
Setting everything to Never leaves it running.
It hasn't happened with earlier version of MX Linux.
Chris
out of curiousity, is the situation different when booted up with systemd?
Re: MX-21 beta 1 feedback thread
Posted: Fri Aug 27, 2021 1:21 pm
by chrispop99
dolphin_oracle wrote: Fri Aug 27, 2021 11:24 am
chrispop99 wrote: Fri Aug 27, 2021 9:58 am
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet video=SVIDEO-1:d splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Portable System: Dell product: Latitude D630 v: N/A serial: <filter> Chassis:
type: 8 serial: <filter>
Mobo: Dell model: N/A serial: <filter> BIOS: Dell v: A07 date: 01/30/2008
Battery: ID-1: BAT0 charge: 48.1 Wh condition: 48.1/56.6 Wh (85%) volts: 12.6/11.1
model: Panasonic DELL DU1548 type: Li-ion serial: <filter> status: Full
CPU: Topology: Dual Core model: Intel Core2 Duo T7250 bits: 64 type: MCP arch: Core Merom
family: 6 model-id: F (15) stepping: D (13) microcode: A4 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 7979
Speed: 798 MHz min/max: 800/2001 MHz boost: enabled Core speeds (MHz): 1: 798 2: 798
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Dell Latitude D630
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a02
Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1280x800~60Hz
OpenGL: renderer: Mesa DRI Intel 965GM (CL) v: 2.1 Mesa 20.3.5 direct render: Yes
Audio: Device-1: Intel 82801H HD Audio vendor: Dell Latitude D630 driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:284b
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Broadcom and subsidiaries NetXtreme BCM5755M Gigabit Ethernet PCI Express
vendor: Dell driver: tg3 v: kernel port: 10c0 bus ID: 09:00.0 chip ID: 14e4:1673
IF: eth0 state: down mac: <filter>
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s
port: 10c0 bus ID: 0c:00.0 chip ID: 8086:4222
IF: wlan0 state: up mac: <filter>
Device-3: Dell Wireless 360 Bluetooth type: USB driver: btusb bus ID: 2-2:2
chip ID: 413c:8140
Drives: Local Storage: total: 62.45 GiB used: 6.21 GiB (9.9%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 58.69 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> scheme: MBR
ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 3.76 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR
Partition: ID-1: / raw size: 55.66 GiB size: 54.49 GiB (97.89%) used: 5.98 GiB (11.0%) fs: ext4
dev: /dev/sda1
ID-2: swap-1 size: 3.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 49.0 C mobo: N/A sodimm: 42.0 C
Fan Speeds (RPM): cpu: 0
Repos: 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 http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 191 Uptime: 1h 45m Memory: 1.93 GiB used: 648.0 MiB (32.8%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
When above machine is left powered up, once the Power Manager Display settings go to blank, it can't be recovered. Black screen. no response from mouse or keyboard.
It's possible to Ctrl-Alt-F1 to start another session, or to reboot.
Setting everything to Never leaves it running.
It hasn't happened with earlier version of MX Linux.
Chris
out of curiousity, is the situation different when booted up with systemd?
No.
Chris
Re: MX-21 beta 1 feedback thread
Posted: Fri Aug 27, 2021 7:14 pm
by JayM
SwampRabbit wrote: Fri Aug 27, 2021 8:44 am
@JayM its already included in the wiki entry.
https://mxlinux.org/wiki/docklike-taskbar/
I miss the ”launch another” option that used to exist. Maybe it can be added back, I think (if I remember right) the reason it was removed was because the right-click menus got out of control with too many options.
I’ve been using the hot keys since, but for new users the menu item could be useful on first use.
I must have missed seeing that one line in the wiki too.
A right-click "open new instance" was what I was looking for. If they wanted to unclutter the right-click menu they could turn all of that workspace stuff to hotkeys and put the launch new instance back. It's something that would be looked for by more people than menu choices for moving to various workspaces so it shouldn't have been the one removed just to reduce menu clutter: it's a core functionality IMO.
Re: MX-21 beta 1 feedback thread
Posted: Sat Aug 28, 2021 6:59 am
by chrispop99
chrispop99 wrote: Fri Aug 27, 2021 9:58 am
Code: Select all
System: Host: <filter> Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64
root=UUID=<filter> ro quiet video=SVIDEO-1:d splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-21_beta1_x64 Wildflower July 27 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Portable System: Dell product: Latitude D630 v: N/A serial: <filter> Chassis:
type: 8 serial: <filter>
Mobo: Dell model: N/A serial: <filter> BIOS: Dell v: A07 date: 01/30/2008
Battery: ID-1: BAT0 charge: 48.1 Wh condition: 48.1/56.6 Wh (85%) volts: 12.6/11.1
model: Panasonic DELL DU1548 type: Li-ion serial: <filter> status: Full
CPU: Topology: Dual Core model: Intel Core2 Duo T7250 bits: 64 type: MCP arch: Core Merom
family: 6 model-id: F (15) stepping: D (13) microcode: A4 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 7979
Speed: 798 MHz min/max: 800/2001 MHz boost: enabled Core speeds (MHz): 1: 798 2: 798
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Dell Latitude D630
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a02
Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1280x800~60Hz
OpenGL: renderer: Mesa DRI Intel 965GM (CL) v: 2.1 Mesa 20.3.5 direct render: Yes
Audio: Device-1: Intel 82801H HD Audio vendor: Dell Latitude D630 driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:284b
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Broadcom and subsidiaries NetXtreme BCM5755M Gigabit Ethernet PCI Express
vendor: Dell driver: tg3 v: kernel port: 10c0 bus ID: 09:00.0 chip ID: 14e4:1673
IF: eth0 state: down mac: <filter>
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s
port: 10c0 bus ID: 0c:00.0 chip ID: 8086:4222
IF: wlan0 state: up mac: <filter>
Device-3: Dell Wireless 360 Bluetooth type: USB driver: btusb bus ID: 2-2:2
chip ID: 413c:8140
Drives: Local Storage: total: 62.45 GiB used: 6.21 GiB (9.9%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDP064G size: 58.69 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> scheme: MBR
ID-2: /dev/sdb type: USB vendor: Generic model: Flash Disk size: 3.76 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR
Partition: ID-1: / raw size: 55.66 GiB size: 54.49 GiB (97.89%) used: 5.98 GiB (11.0%) fs: ext4
dev: /dev/sda1
ID-2: swap-1 size: 3.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 49.0 C mobo: N/A sodimm: 42.0 C
Fan Speeds (RPM): cpu: 0
Repos: 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 http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bullseye main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 191 Uptime: 1h 45m Memory: 1.93 GiB used: 648.0 MiB (32.8%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
When above machine is left powered up, once the Power Manager Display settings go to blank, it can't be recovered. Black screen. no response from mouse or keyboard.
It's possible to Ctrl-Alt-F1 to start another session, or to reboot.
Setting everything to Never leaves it running.
It hasn't happened with earlier version of MX Linux.
Chris
[Added]
Not sure if this is expected behaviour, but if you do Ctrl-Alt-F1, then without doing anything else, do Ctrl-Alt-F7, you get back to a working screen.
Chris
Re: MX-21 beta 1 feedback thread
Posted: Sat Aug 28, 2021 7:07 am
by Huckleberry Finn
What if you just turn off "Display Power Management" in Power Manager - Display tab? (Without setting others to never)