MX-19.2 KDE Beta 2 Feedback Thread

[bbfuller]

Dolphin file Manager

One of the useful things about the Dolphin file manager is the ability to create entries in the Places Panel for Network machines, or individual shares.

In my installation of the MX KDE Beta, that facility seems to require the manual creation of an entry by right clicking on a heading, selecting "Add" and typing in the address. That also seems to be the default configuration for Mageia and PCLinuxOS.

I've found one distribution so far (Manjaro) that has an "Add to Places" option on the Dolphin "File" menu that automates the whole process.

Any chance that facility could be added to MX?

'Add to places' is available in the context menu by right-clicking the folder directly.

Chris

Yes, I could have put that better.

I see how I can use that to add a folder to Places.

I don't see how I can add a complete machine like that. It would work if KDE Network Browsing showed me a complete list of available machines on the network, but here it doesn't.

The "Add to Places" option I referred to, when you have a listing of all the available shares on a machine, adds the machine to Places.

It was just something I thought "Oh, how useful".

[tony37]

Alt-F1 is not able to be used for the MX Manual as it is set to open the menu, along with the Meta key. If you redefine Alt-F1, the Meta key no longer opens the menu, and can't be configured to do so.

I've found a sort of work-around. If you define Alt-F1 for mx-manual, then change the menu key to the Meta key plus something random (I used Meta + M), it all works as wanted. Meta opens the menu, Alt-F1 opens the manual.

I haven't been able to get this to work in Global Shortcuts, but it seems they are broken to some extent in any case.

Chris

How about using Meta+F1 as default there? Indeed strange that the Meta key to open the menu isn't mentioned in Global Shortcuts, but stops working when you set the shortcut there to 'None'. But in a way Meta is not a normal shortcut because it's also used in other shortcuts (so it's a delayed shortcut I guess, or rather: it's only activated when you release the key)

I was actually just testing another keyboard thing. This is not MX-specific but maybe you can do better than others here: For users of an AZERTY-keyboard (used in France + Belgium) the shortcuts Meta+1, Meta+2, etc. (used to activate task manager entries) are problematic. To have Meta+1 they have to type Meta+shift+&. Now I can try to be smart and input Meta+& as shortcut so I don't have to press the shift key. But when we get to Meta+2, that would have to be Meta+shift+é, or trying to be smart Meta+é. But this simply refuses to work because when I try this the shortcut is given as Meta+É (capital letter). Same story for keys è [+ shift this gives 7], ç [9] and à [0], they can't be used in any shortcut. Maybe there's a sophisticated solution for this, but there's actually an obvious workaround: using the numpad keys.
So I would suggest having Meta+Num+1, Meta+Num+2 etc. as Global Alternate shortcuts, this way at least that works for AZERTY users, and in general it seems logical to me that Meta+1 should also work when you use the numpad to press 1.

[SwampRabbit]

Speaking of the application menu icon, this reminds me that forum user "Mike" once contributed a very nice icon that combines the MX logo with the KDE gears.

I have been using it ever since on my MX18/Neptune install.

Wow that’s so funny, we actually talked about this and I pretty much made the same icon and few others... I didn’t even know it was done already. :)

We had this discussion already and right now there won’t be any MX icon changes.

[tony37]

Ctrl+Alt+T to 'Launch Konsole' doesn't work. I can add a custom entry with action konsole and shortcut Ctrl+Alt+T, now it works.
When I try to add other Application Launchers in Global Shortcuts, they consistently fail to work.

The problem may be that System Settings always adds 'Launch ...' to the name of the program (maybe restart of system settings required to see this). So maybe it thinks the program is called "launch konsole". Because I have some preset application launchers in Kubuntu (Plasma 5.18) and they work fine and don't have 'Launch' in the title. But when I try to make an extra launcher there, it prepends 'Launch' to the name. In KDE Neon (Plasma 5.19) it doesn't do this, but there seems to be another bug there.
Actually it's the first time I notice this because I always made custom entries for starting programs (and websites). Only problem is you sometimes have to search the actual command, like synaptic-pkexec

PS: talking about custom entries: you could add one to the menu (using the menu editor) called 'Dolphin as root' with command

Code: Select all

pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true dolphin

[asqwerth]

....

PS: talking about custom entries: you could add one to the menu (using the menu editor) called 'Dolphin as root' ....

You might want to explore the preinstalled custom actions available in the right click context menu....

[dolphin_oracle]

When you right-click the Application Launcher icon, then select Alternatives to try another type of menu, the MX icon is lost. If you then revert to the Application Launcher, you don't get thew MX icon back.

Can that icon be made the default for all menu types?

Chris

maybe...

[JayM]

The updater auto-opened its right-click context menu again after applying today's update (mx-tweak.) I changed its preferences afterward to use Muon instead of MX Updater View and Upgrade window. I'll find out if it still happens after the next update.

/var/log/apt/term.log:

Code: Select all

Log started: 2020-07-22  12:06:09
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 206088 files and directories currently installed.)
Preparing to unpack .../mx-tweak_20.07.07_amd64.deb ...
Unpacking mx-tweak (20.07.07) over (20.07.06) ...
Setting up mx-tweak (20.07.07) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Log ended: 2020-07-22  12:06:11

/var/log/dpkg.log:

Code: Select all

2020-07-22 12:06:09 startup archives unpack
2020-07-22 12:06:10 upgrade mx-tweak:amd64 20.07.06 20.07.07
2020-07-22 12:06:10 status half-configured mx-tweak:amd64 20.07.06
2020-07-22 12:06:10 status unpacked mx-tweak:amd64 20.07.06
2020-07-22 12:06:10 status half-installed mx-tweak:amd64 20.07.06
2020-07-22 12:06:10 status triggers-pending desktop-file-utils:amd64 0.23-4
2020-07-22 12:06:10 status triggers-pending mime-support:all 3.62
2020-07-22 12:06:10 status triggers-pending hicolor-icon-theme:all 0.17-2
2020-07-22 12:06:10 status unpacked mx-tweak:amd64 20.07.07
2020-07-22 12:06:10 startup packages configure
2020-07-22 12:06:10 configure mx-tweak:amd64 20.07.07 <none>
2020-07-22 12:06:10 status unpacked mx-tweak:amd64 20.07.07
2020-07-22 12:06:10 status half-configured mx-tweak:amd64 20.07.07
2020-07-22 12:06:10 status installed mx-tweak:amd64 20.07.07
2020-07-22 12:06:10 trigproc mime-support:all 3.62 <none>
2020-07-22 12:06:10 status half-configured mime-support:all 3.62
2020-07-22 12:06:11 status installed mime-support:all 3.62
2020-07-22 12:06:11 trigproc hicolor-icon-theme:all 0.17-2 <none>
2020-07-22 12:06:11 status half-configured hicolor-icon-theme:all 0.17-2
2020-07-22 12:06:11 status installed hicolor-icon-theme:all 0.17-2
2020-07-22 12:06:11 trigproc desktop-file-utils:amd64 0.23-4 <none>
2020-07-22 12:06:11 status half-configured desktop-file-utils:amd64 0.23-4
2020-07-22 12:06:11 status installed desktop-file-utils:amd64 0.23-4

QSI:

Code: Select all

System:
  Host: mx-kde-b2 Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2-amd64 
  root=UUID=3de26e4a-56c2-420f-b19b-18102ba13170 ro quiet splash 
  Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-19.2_KDE-beta2_x64 patito feo July 5  2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter> 
  Chassis: Oracle Corporation type: 1 serial: <filter> 
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek v: VirtualBox 
  date: 12/01/2006 
Battery:
  ID-1: BAT0 charge: 49.5 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
  model: innotek 1 type: Unknown serial: N/A status: Unknown 
CPU:
  Topology: Triple Core model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx 
  bits: 64 type: MCP arch: Zen family: 17 (23) model-id: 11 (17) stepping: N/A 
  microcode: 6000626 L2 cache: 1536 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 11977 
  Speed: 1996 MHz min/max: N/A Core speeds (MHz): 1: 1996 2: 1996 3: 1996 
  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, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.17.0.0 bus ID: 00:02.0 
  chip ID: 15ad:0405 
  Display: x11 server: X.Org 1.20.4 driver: vmware unloaded: fbdev,modesetting,vesa 
  compositor: kwin_x11 resolution: 1885x959~60Hz 
  OpenGL: renderer: SVGA3D; build v: 2.1 Mesa 20.0.7 direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio driver: snd_intel8x0 v: kernel bus ID: 00:05.0 
  chip ID: 8086:2415 
  Sound Server: ALSA v: k5.6.0-2-amd64 
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI 
  port: d020 bus ID: 00:03.0 chip ID: 8086:100e 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus 
  v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
Drives:
  Local Storage: total: 25.00 GiB used: 6.59 GiB (26.3%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 25.00 GiB block size: 
  physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 1.0 
  scheme: MBR 
Partition:
  ID-1: / raw size: 22.97 GiB size: 22.48 GiB (97.88%) used: 6.59 GiB (29.3%) 
  fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap 
  swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
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 buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://deb.debian.org/debian buster main contrib non-free
  2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ buster main non-free
  2: deb https://mirror.pregi.net/mx-linux-packages/mx/repo/ buster ahs
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 168 Uptime: 14m Memory: 2.95 GiB used: 851.4 MiB (28.2%) Init: SysVinit 
  v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
  running in: quick-system-in inxi: 3.0.36 

[tony37]

....

PS: talking about custom entries: you could add one to the menu (using the menu editor) called 'Dolphin as root' ....

You might want to explore the preinstalled custom actions available in the right click context menu....

I know they're there, and they're very well done (as I said before btw), but having a custom entry saves some mouse-clicks when you want to open Dolphin in root mode directly. So an entirely optional suggestion.

[chrispop99]

PS: talking about custom entries: you could add one to the menu (using the menu editor) called 'Dolphin as root' with command

Code: Select all

pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true dolphin

I like this; it makes up in part for not having the Xfce ability to open a root file manager via the desktop context menu.

Chris

[tony37]

A few things about the KEC: Extract context menu.
- When you have a .tar.gz file, KEC: Extract shows six options. The first extracts to a .tar file, the second (extracting to subfolder) doesn't work, the third extracts to a .tar file on a chosen location, the fourth, fifth and sixth do what I think most would expect: extracting the whole thing and not just the .gz bit.
- When I extract a .tar.7z file with KEC, it produces a subfolder with a .tar file in it. Extracting with Ark produces just a .tar file.
- KEC can compress to a .tar.xz file, but can't extract it. Ark extracts without problems. Same thing with .tar.lzma files and with 'parallel compress to xz'.
- When KEC extracts a .rar file it produces a subfolder even when I'm not asking for it.
- When I produce a password-protected .zip file with Ark (btw: I don't see an option to do that with KEC), extracting with KEC doesn't work, even though it says: "Extraction done". Small bug with Ark here: when I enter the wrong password, it doesn't say so, but produces an empty file (with the correct name). Plus: with a password-protected .rar file you have to guess if there's a password or not when using KEC (and it doesn't tell you if your guess was right, or whether the password was correct or not), no such problem with Ark.
- With a .tar.bz2 file KEC shows 12 (!) extract options. The first six don't work, 7 to 9 extract to .tar, 10 to 12 do complete extraction. Ark works flawless here. With .bz files, only 9 extract options, first 6 don't work.

I didn't try every possible option, but you get the gist. It may be a non-orthodox idea to use KEC for compressing and Ark for extracting. But Ark also has a lot of option for compressing in 'Compress to...'