Page 14 of 21
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 1:36 pm
by markol
SwampRabbit wrote: Wed Sep 22, 2021 12:37 pm
@markol I noticed this issue goes back awhile for you, is that right?
You did a fresh install of MX-21 Beta 2 not an upgrade from Beta 1 right?
In a stock but updated MX-21 KDE Beta 2 VM, I have always had all the icons in the Applications menu.
To try and replicate that manually updating Libreoffice does or does not cause this problem, I...
- downloaded 7.2.1 from the site
- installed all the .debs, BUT did not remove anything prior
Libreoffice 7.2.1 starts fine and still have all the icons in the Applications menu.
I don't think regular updates or manually updating Libreoffice caused this, I think something is wrong with your initial installation. Going back through the thread I see it was mentioned this should not be an issue anymore. So hopefully when you install again (another Beta, RC, or Final) you won't have this issue.
Yes, this was a clean install. I believe
@uncle mark had this problem in beta1.
I don't believe LibreOffice had anything to do with it either.
I will try to reinstall (clean) tonight and retrace the steps.
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 1:44 pm
by davemx
richb wrote: Wed Sep 22, 2021 11:45 am
Not sure what you mean by Load/Save dialog. I use Vivaldi in MX 21 B2 as well, and would like to check your issue. I have Vivaldi version 4.2.2406.48. I think that is the latest stable version.
I just did the general upgrade which took vivaldi to 4.2.2406.58. I did that in both distros. At present, I don't seem to be getting the keyboard delay, but for whatever reason, I can still hear the fan, which I cannot on the other distro. I have a modified MX-asq/GeekyTower which shows the top 10 CPU users instead of 3 and vivaldi-bin was taking too much, over three instances shown. But now it is hardly taking anything after I did a "killall vivaldi-bin" and restarted it without facebook and now it's running silently. Yet in my other distro Facebook doesn't cause a problem.
Load/Save dialogs. Like "Open File" when you want to upload an attachment.
This is the KDE dialog box as used by the other distro:
Screenshot_20210922_180927.png
This is the Vivaldi dialog box as used by MX
ksnip_20210922-181358.png
I'm sure that before I reinstalled MX21ß2-KDE a couple of days ago, that MX was using the first of these, and I had no problems on Facebook.
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 2:26 pm
by richb
I am afraid you lost me. Those dialog boxes appear to be from Dolphin not the Vivaldi browser. If that is the case the appearance of the window is controlled by the theme chosen in System Settings and how Dolphin is configured.
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 3:16 pm
by davemx
richb wrote: Wed Sep 22, 2021 2:26 pm
I am afraid you lost me. Those dialog boxes appear to be from Dolphin not the Vivaldi browser. If that is the case the appearance of the window is controlled by the theme chosen in System Settings and how Dolphin is configured.
OK, I'll have a look at that when I'm next on the computer. Cheers!
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 4:12 pm
by davemx
No, I am pretty sure I was right. The first dialog box is a KDE File selector, it even says KDialog at the top. The second one is different. It works differently, and has different options, not just a stylistic difference. I went through the options in both Systemsettings and Dolphin, and if you can tell me how to set the style of the dialog box, I'll give it a try.
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 5:19 pm
by markol
markol wrote: Wed Sep 22, 2021 1:36 pm
I will try to reinstall (clean) tonight and retrace the steps.
@SwampRabbit a fresh install did the trick, everything went well without problems and/or hickups. I installed it from the same image as before.
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 5:24 pm
by dolphin_oracle
davemx wrote: Wed Sep 22, 2021 4:12 pm
No, I am pretty sure I was right. The first dialog box is a KDE File selector, it even says KDialog at the top. The second one is different. It works differently, and has different options, not just a stylistic difference. I went through the options in both Systemsettings and Dolphin, and if you can tell me how to set the style of the dialog box, I'll give it a try.
The second dialog looks more gtk than kdialog. Do you have any gtk settings set up or maybe installed mx-fluxbox?
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 7:28 pm
by davemx
dolphin_oracle wrote: Wed Sep 22, 2021 5:24 pm
The second dialog looks more gtk than kdialog. Do you have any gtk settings set up or maybe installed mx-fluxbox?
That's what I thought. Obviously I have some gtk programs installed, for example GIMP and Inkscape. I haven't installed fluxbox, I really don't like it. Maybe I should look at the Open dialog in a gtk program for comparison. I'm just at a loss as to why I can't get Vivaldi to use kdialog, and also why Vivaldi is misbehaving. I've been looking on the net and so far found nothing that helps.
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Wed Sep 22, 2021 11:45 pm
by bigboppercole
I just got a new work notebook, MSI GE75 Raider, i7 w/ GeForce video, so I decided to give the beta2 a try on it. It's dual boot with Windows.
2 issues
1. no sound
ksnip_20210922-224104.png
The top controller only has Off as an option.
None of the options on the second controller produce sound.
2. no video output to the external HDMI
The TV I'm connecting to detects that something is plugged in, but in the system settings it never shows the second screen. I've tried setting the refresh rate down to 60Hz and changing the resolution with no change.
I tried installing nvidia drivers with the MX installer which did not help with either.
Everything works fine in Windows.
I am currently at an IT conference and don't have access to a spare flash drive to install MX-19.4 from to see if the issues are there as well, so this may not be just MX-21 related.
Al
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 splash
Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM Distro: MX-21_KDE_beta2_x64 Wildflower September 4 2021
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: Micro-Star product: GE75 Raider 10SE v: REV:1.0 serial: <filter> Chassis: type: 10
serial: <filter>
Mobo: Micro-Star model: MS-17E9 v: REV:1.0 serial: <filter> UEFI: American Megatrends v: E17E9IMS.10D
date: 11/17/2020
Battery: ID-1: BAT1 charge: 47.0 Wh condition: 48.3/51.6 Wh (94%) volts: 12.2/10.9 model: MSI BIF0_9 type: Li-ion
serial: N/A status: Unknown
Device-1: hid-00:02:76:06:c7:82-battery model: Si670m Bluetooth Wireless Notebook Mouse serial: N/A charge: N/A
status: Discharging
CPU: Topology: 6-Core model: Intel Core i7-10750H bits: 64 type: MT MCP arch: N/A family: 6 model-id: A5 (165)
stepping: 2 microcode: EA L2 cache: 12.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62399
Speed: 800 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
9: 800 10: 800 11: 800 12: 800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
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: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Micro-Star MSI driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:9bc4
Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Micro-Star MSI driver: nvidia v: 460.91.03
bus ID: 01:00.0 chip ID: 10de:1f15
Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa alternate: nv
compositor: kwin_x11 tty: N/A
OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 21.2.1 direct render: Yes
Audio: Device-1: Intel Comet Lake PCH cAVS vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 00:1f.3
chip ID: 8086:06c8
Device-2: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 01:00.1
chip ID: 10de:10f9
Sound Server: ALSA v: k5.10.0-8-amd64
Network: Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel port: 5000 bus ID: 00:14.3 chip ID: 8086:06f0
IF: wlan0 state: up mac: <filter>
Device-2: Qualcomm Atheros Killer E2500 Gigabit Ethernet vendor: Micro-Star MSI driver: alx v: kernel port: 3000
bus ID: 03:00.0 chip ID: 1969:e0b1
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 1.40 TiB used: 356.25 GiB (24.8%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN730 SDBPNTY-512G-1032 size: 476.94 GiB block size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 11111000 scheme: GPT
ID-2: /dev/sda vendor: Seagate model: ST1000LM048-2E7172 size: 931.51 GiB block size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 0001 scheme: GPT
ID-3: /dev/sdb type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.90 GiB block size: physical: 512 B
logical: 512 B serial: <filter> rev: PMAP scheme: MBR
Partition: ID-1: / raw size: 25.00 GiB size: 24.44 GiB (97.76%) used: 8.65 GiB (35.4%) fs: ext4 dev: /dev/nvme0n1p5
ID-2: /home raw size: 178.00 GiB size: 174.15 GiB (97.84%) used: 467.9 MiB (0.3%) fs: ext4 dev: /dev/nvme0n1p9
ID-3: swap-1 size: 17.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) cache pressure: 100 (default)
dev: /dev/nvme0n1p8
Sensors: System Temperatures: cpu: 54.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/anydesk-stable.list
1: deb http://deb.anydesk.com/ all main
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/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye main non-free
2: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ bullseye ahs
Active apt repos in: /etc/apt/sources.list.d/syncthing.list
1: deb [signed-by=/usr/share/keyrings/syncthing-archive-keyring.gpg] https://apt.syncthing.net/ syncthing stable
Info: Processes: 307 Uptime: 24m Memory: 15.46 GiB used: 2.39 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
Re: MX-21 KDE/plasma beta 2 feedback thread
Posted: Thu Sep 23, 2021 2:54 am
by JayM
I tried installing nvidia drivers with the MX installer which did not help with either.
What happened? Did you get error messages? Your QSI shows that the Nvidia driver 460 was installed, so the driver installation probably succeeded.
If you search the forum you'll find posts about how some laptop manufacturers hard-wire the HDMI port to the Nvidia GPU's bus, and as yours is a bumblebee/optimus system that GPU won't be in use by default. These posts also tell how to work around that so the HDMI port can also be used by the default Intel integrated GPU. That's also explained here:
https://wiki.archlinux.org/title/Bumble ... VIDIA_chip.
As a troubleshooting measure open a terminal and run
with the TV connected and see if it's detected. If it is, then that's what the situation is: HDMI wired to Nvidia's bus. It wouldn't be an MX issue but a hardware design "feature."