Code: Select all
sudo apt install freerdp
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package freerdp is a virtual package provided by:
freerdp2-x11 2.3.0+dfsg1-2
freerdp2-shadow-x11 2.3.0+dfsg1-2OMG, you too. lolmarkol wrote: Sat Oct 09, 2021 8:57 am Started KRDC, got error message: Could not start "xfreerdp"; make sure xfreerdp is properly installed
xfreerdp does not exist, tried freerdp, gotCode: Select all
sudo apt install freerdp Reading package lists... Done Building dependency tree... Done Reading state information... Done Package freerdp is a virtual package provided by: freerdp2-x11 2.3.0+dfsg1-2 freerdp2-shadow-x11 2.3.0+dfsg1-2
I think I know why flatpak isn't installing, it's because I've set up a shortcut to run MXPI via sudo with no password. When I run it normally, flatpak works, and I have to input the password when I click the Flatpak tab, which seems to confuse it if it's in root already.dolphin_oracle wrote: Fri Oct 08, 2021 8:26 pmshouldn't have. skype is downloaded directly from microsoft. and remove of plasma-discover shouldn't have affected flatpak at all. unless it also removed mx-packageinstaller, which might in turn remove the flatpak backend.davemx wrote: Fri Oct 08, 2021 7:38 pm To be honest, I'm not too bothered about not being able to install Skype (via mxpi favourites) or Freetube (via flatpak) as I can install them using the deb files from their sites and they both seem to work just fine. I don't suppose this happened because I uninstalled plasma-discover and added synaptic and apt-notifier?
Code: Select all
[01:28:01.104] (II) DAEMON: Initializing...
[01:28:01.109] (II) DAEMON: Starting...
[01:28:01.109] (II) DAEMON: Logind interface found
[01:28:01.110] (II) DAEMON: Adding new display on vt 7 ...
[01:28:01.110] (II) DAEMON: Loading theme configuration from ""
[01:28:01.110] (II) DAEMON: Display server starting...
[01:28:01.110] (II) DAEMON: Adding cookie to "/var/run/sddm/{046df643-7309-456d-a5ef-a576cb20f65d}"
[01:28:01.112] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{046df643-7309-456d-a5ef-a576cb20f65d} -background none -noreset -displayfd 17 -seat seat0 vt7
[01:28:01.657] (EE) DAEMON: Failed to read display number from pipe
[01:28:01.657] (EE) DAEMON: Could not start Display server on vt 7
[01:28:01.978] (WW) DAEMON: Signal received: SIGHUP
[01:31:41.563] (WW) DAEMON: Signal received: SIGTERM
Something else happened. Please post your quick system information too please.Arnox wrote: Sun Oct 10, 2021 4:21 am After an update by Discover including a kernel update, several things have gone wrong. One minor and one major.
1. All GRUB entries, while correct and working, only now boot with systemd on my machine. Since I run systemd regularly, this isn't really an issue for me at all, personally, but it does seem like Discover was completely disregarding MX Linux's boot defaults.
2. SDDM is hard crashing at the login screen. Bypassing it by opening up another window with Ctrl+Alt+F2 and logging in via the CLI and then typing startx works just fine. Try to log out normally via the GUI and it will crash to the CLI again. Looking at /var/log/sddm.log shows,
Code: Select all
[01:28:01.104] (II) DAEMON: Initializing... [01:28:01.109] (II) DAEMON: Starting... [01:28:01.109] (II) DAEMON: Logind interface found [01:28:01.110] (II) DAEMON: Adding new display on vt 7 ... [01:28:01.110] (II) DAEMON: Loading theme configuration from "" [01:28:01.110] (II) DAEMON: Display server starting... [01:28:01.110] (II) DAEMON: Adding cookie to "/var/run/sddm/{046df643-7309-456d-a5ef-a576cb20f65d}" [01:28:01.112] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{046df643-7309-456d-a5ef-a576cb20f65d} -background none -noreset -displayfd 17 -seat seat0 vt7 [01:28:01.657] (EE) DAEMON: Failed to read display number from pipe [01:28:01.657] (EE) DAEMON: Could not start Display server on vt 7 [01:28:01.978] (WW) DAEMON: Signal received: SIGHUP [01:31:41.563] (WW) DAEMON: Signal received: SIGTERM
Code: Select all
System:
Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64
root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM
Distro: MX-21_KDE_RC1_x64 Wildflower October 5 2021
base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Laptop System: Dell product: Inspiron 15-3567 v: N/A serial: <filter> Chassis:
type: 9 serial: <filter>
Mobo: Dell model: 0XPYYD v: A00 serial: <filter> UEFI: Dell v: 2.16.0
date: 08/18/2021
CPU:
Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Kaby Lake
family: 6 model-id: 8E (142) stepping: 9 microcode: EA L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21599
Speed: 2871 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 2871 2: 2872 3: 2871
4: 2873
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
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: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:5916
Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa
compositor: kwin_x11 resolution: 1366x768~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.2.1
direct render: Yes
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71
Sound Server: ALSA v: k5.10.0-9-amd64
Network:
Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel port: f040 bus ID: 01:00.0
chip ID: 8086:3165
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169
v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8136
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 1.82 TiB used: 566.33 GiB (30.4%)
ID-1: /dev/sda vendor: Western Digital model: WDS100T2B0A-00SM50 size: 931.51 GiB
block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter>
rev: 40WD temp: 23 C scheme: GPT
ID-2: /dev/sdb type: USB model: ATA ST1000LM035-1RK1 size: 931.51 GiB block size:
physical: 4096 B logical: 512 B serial: <filter> rev: SDM3 scheme: GPT
Partition:
ID-1: / raw size: 24.00 GiB size: 23.46 GiB (97.73%) used: 7.75 GiB (33.1%) fs: ext4
dev: /dev/sda3
ID-2: /home raw size: 128.00 GiB size: 119.96 GiB (93.72%) used: 1.31 GiB (1.1%)
fs: ext4 dev: /dev/sda4
Sensors:
System Temperatures: cpu: 73.0 C mobo: 57.0 C
Fan Speeds (RPM): cpu: 4054
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
3: deb-src http://deb.debian.org/debian/ bullseye main contrib non-free
4: deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://it.mxrepo.com/mx/repo/ bullseye main non-free
2: deb http://it.mxrepo.com/mx/testrepo/ bullseye test
3: deb http://it.mxrepo.com/mx/repo/ bullseye ahs
Info:
Processes: 220 Uptime: 4h 30m Memory: 15.38 GiB used: 2.38 GiB (15.5%)
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
Here you go:dolphin_oracle wrote: Sun Oct 10, 2021 7:08 amSomething else happened. Please post your quick system information too please.Arnox wrote: Sun Oct 10, 2021 4:21 am After an update by Discover including a kernel update, several things have gone wrong. One minor and one major.
1. All GRUB entries, while correct and working, only now boot with systemd on my machine. Since I run systemd regularly, this isn't really an issue for me at all, personally, but it does seem like Discover was completely disregarding MX Linux's boot defaults.
2. SDDM is hard crashing at the login screen. Bypassing it by opening up another window with Ctrl+Alt+F2 and logging in via the CLI and then typing startx works just fine. Try to log out normally via the GUI and it will crash to the CLI again. Looking at /var/log/sddm.log shows,
Code: Select all
[01:28:01.104] (II) DAEMON: Initializing... [01:28:01.109] (II) DAEMON: Starting... [01:28:01.109] (II) DAEMON: Logind interface found [01:28:01.110] (II) DAEMON: Adding new display on vt 7 ... [01:28:01.110] (II) DAEMON: Loading theme configuration from "" [01:28:01.110] (II) DAEMON: Display server starting... [01:28:01.110] (II) DAEMON: Adding cookie to "/var/run/sddm/{046df643-7309-456d-a5ef-a576cb20f65d}" [01:28:01.112] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{046df643-7309-456d-a5ef-a576cb20f65d} -background none -noreset -displayfd 17 -seat seat0 vt7 [01:28:01.657] (EE) DAEMON: Failed to read display number from pipe [01:28:01.657] (EE) DAEMON: Could not start Display server on vt 7 [01:28:01.978] (WW) DAEMON: Signal received: SIGHUP [01:31:41.563] (WW) DAEMON: Signal received: SIGTERM
To me it sounds like an incomplete update and that sysvinit was removed.
Regeneration of the boot menus is triggered by the the kernel update not by discover.
Code: Select all
System:
Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64
compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-9-amd64
root=UUID=<filter> ro splash
init=/sbin/init
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM
Distro: MX-21_KDE_RC1_x64 Wildflower October 5 2021
base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
serial: <filter> UEFI: American Megatrends v: 2802 date: 10/22/2020
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: Discharging
CPU:
Topology: 6-Core model: AMD Ryzen 5 3600XT bits: 64 type: MT MCP
arch: Zen family: 17 (23) model-id: 71 (113) stepping: N/A
microcode: 8701021 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 91032
Speed: 2196 MHz min/max: 2200/3800 MHz boost: enabled
Core speeds (MHz): 1: 2196 2: 2196 3: 2195 4: 2187 5: 2196 6: 2195
7: 2247 8: 2193 9: 2191 10: 2195 11: 2196 12: 2196
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown 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: Full AMD retpoline, IBPB: conditional,
STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA TU104GL [Quadro RTX 4000] driver: nvidia v: 470.63.01
bus ID: 09:00.0 chip ID: 10de:1eb1
Display: server: X.Org 1.20.13 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
compositor: kwin_x11 resolution: 1920x1080~60Hz
OpenGL: renderer: Quadro RTX 4000/PCIe/SSE2 v: 4.6.0 NVIDIA 470.63.01
direct render: Yes
Audio:
Device-1: NVIDIA TU104 HD Audio driver: snd_hda_intel v: kernel
bus ID: 09:00.1 chip ID: 10de:10f8
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 0b:00.4 chip ID: 1022:1487
Device-3: Cubeternet Live Streaming USB Device type: USB
driver: snd-usb-audio,uvcvideo bus ID: 2-1:2 chip ID: 1e4e:7102
serial: <filter>
Sound Server: ALSA v: k5.10.0-9-amd64
Network:
Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
v: kernel port: f000 bus ID: 05:00.0 chip ID: 8086:1539
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
IF-ID-2: virbr0 state: down mac: <filter>
Drives:
Local Storage: total: 1.93 TiB used: 20.54 GiB (1.0%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB
size: 931.51 GiB block size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 2B2QEXM7 scheme: GPT
ID-2: /dev/sda vendor: Western Digital model: WD10EZEX-08WN4A0
size: 931.51 GiB block size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 1A01
scheme: MBR
ID-3: /dev/sdb vendor: Kingston model: SUV400S37120G size: 111.79 GiB
block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
serial: <filter> rev: 96R9 scheme: GPT
Partition:
ID-1: / raw size: 105.91 GiB size: 103.69 GiB (97.90%)
used: 20.54 GiB (19.8%) fs: ext4 dev: /dev/sdb2
ID-2: swap-1 size: 5.62 GiB used: 0 KiB (0.0%) fs: swap
swappiness: 15 (default 60) cache pressure: 100 (default)
dev: /dev/sdb3
Sensors:
System Temperatures: cpu: 63.2 C mobo: N/A gpu: nvidia temp: 44 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 30%
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://la.mxrepo.com/mx/repo/ bullseye main non-free
2: deb http://la.mxrepo.com/mx/repo/ bullseye ahs
Info:
Processes: 300 Uptime: 1m Memory: 15.60 GiB used: 1.11 GiB (7.1%)
Init: systemd v: 247 runlevel: 5 default: 5 Compilers: gcc: 10.2.1
alt: 10 Shell: quick-system-in running in: quick-system-in
inxi: 3.0.36
No I don't think I should adjust how I do my keypresses. I think it shouldn't matter if I press `Ctrl` or `Shift` first, especially when the entire desktop environment is telling me to press `Ctrl` first. Plus only shortcuts including `Ctrl` behave like this; others, `Ctrl + Alt + T` to open Konsole for example, work even when inverting `Ctrl` and `Alt`.Eadwine Rose wrote: Sun Oct 10, 2021 8:51 am That is easily solved by just adjusting how you do your keypresses.
Or MAYBE in the keyboard shortcuts section try adjusting the shortcut entries to what you want them to be. Dunno if that works though, but worth a try.