MX-19.2 KDE Beta 1 feedback thread
Re: MX-19.2 KDE Beta 1 feedback thread
It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
MX Linux Asus F552, 12GB RAM, 500GB WD SSD MX19.2
Dell Inspiron 7559 16GB RAM 1X 256GB SSD & 1TB SSD MX KDE 21.1 & Windows 11
Mini Tower PC 2X 256GB SSD MX KDE21.1
Dell Inspiron 7559 16GB RAM 1X 256GB SSD & 1TB SSD MX KDE 21.1 & Windows 11
Mini Tower PC 2X 256GB SSD MX KDE21.1
- dolphin_oracle
- Developer
- Posts: 22251
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-19.2 KDE Beta 1 feedback thread
where does it ask?Sparky wrote: Tue Jul 07, 2020 7:39 am It looks great and runs great. I only had a side effect. When I startup the computer It asks for what kind of session I want, XFCE, Plasma, or fluxbox. Not sure how fluxbox got there.
only plasma is on the iso.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
- uncle mark
- Posts: 857
- Joined: Sat Nov 11, 2006 9:42 pm
Re: MX-19.2 KDE Beta 1 feedback thread
Any chance Synaptic could be added and MX-Update call that instead of Muon?
Custom build Asus/AMD/nVidia circa 2011 -- MX 19.2 KDE
Acer Aspire 5250 -- MX 21 KDE
Toshiba Satellite C55 -- MX 18.3 Xfce
Assorted Junk -- assorted Linuxes
Acer Aspire 5250 -- MX 21 KDE
Toshiba Satellite C55 -- MX 18.3 Xfce
Assorted Junk -- assorted Linuxes
Re: MX-19.2 KDE Beta 1 feedback thread
I believe that fehlix worked on mx-updater so that if SYnaptic is on your system in place of muon, apt-notifier will call it.uncle mark wrote: Tue Jul 07, 2020 7:49 am Any chance Synaptic could be added and MX-Update call that instead of Muon?
You could test these changes to mx-updater by installing Synaptic yourself and removing muon - if you don't mind the risk of messing with this beta. After all, this is the testing period.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400
Re: MX-19.2 KDE Beta 1 feedback thread
That is the way it works for me. Synaptic installed and that is what apt-updater shows.But I left Muon installed for testing purposes.asqwerth wrote: Tue Jul 07, 2020 7:52 amI believe that fehlix worked on mx-updater so that if SYnaptic is on your system in place of muon, apt-notifier will call it.uncle mark wrote: Tue Jul 07, 2020 7:49 am Any chance Synaptic could be added and MX-Update call that instead of Muon?
You could test these changes to mx-updater by installing Synaptic yourself and removing muon - if you don't mind the risk of messing with this beta. After all, this is the testing period.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: MX-19.2 KDE Beta 1 feedback thread
The logic changed within apt-notifer: If synaptic is installed, apt-notifier will use it. Otherwise if muon is found it will use muon. The right-click menu in apt-notifier, will change accordingly after installing synaptic, but you would need to close apt-notifier and start MX Updater again, to see the changes. You don't need to remove muon.asqwerth wrote: Tue Jul 07, 2020 7:52 amI believe that fehlix worked on mx-updater so that if SYnaptic is on your system in place of muon, apt-notifier will call it.uncle mark wrote: Tue Jul 07, 2020 7:49 am Any chance Synaptic could be added and MX-Update call that instead of Muon?
You could test these changes to mx-updater by installing Synaptic yourself and removing muon - if you don't mind the risk of messing with this beta. After all, this is the testing period.
Re: MX-19.2 KDE Beta 1 feedback thread
As it apprears the KDE Beta1 ISO does not contain most the changelog files, probably due to space constrains.baldyeti wrote: Tue Jul 07, 2020 4:04 am One tiny thing I noticed (not even KDE-specific): if one clicks the About/Changelog button of apt-notifier, one gets a big *empty* window
So if you want to try it out, reinstall apt-notifer:
Code: Select all
sudo apt install --reinstall apt-notifier
- dolphin_oracle
- Developer
- Posts: 22251
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-19.2 KDE Beta 1 feedback thread
according to the log, grub was not installed.sunrat wrote: Mon Jul 06, 2020 9:10 pm Sorry, I meant to include QSI.
^^ This copied automatically to the clipboard fine as it's supposed to.Code: Select all
System: Host: mxbrain-plasma 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=/dev/sda7 Desktop: KDE Plasma 5.14.5 wm: kwin_x11 dm: SDDM Distro: MX-19.2_KDE-beta1_x64 patito feo July 5 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> Mobo: Gigabyte model: H170-HD3-CF v: x.x serial: <filter> UEFI: American Megatrends v: F4 date: 10/16/2015 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter> charge: 50% (should be ignored) rechargeable: yes status: N/A CPU: Topology: Quad Core model: Intel Core i5-6500 bits: 64 type: MCP arch: Skylake-S family: 6 model-id: 5E (94) stepping: 3 microcode: DC L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 25599 Speed: 800 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled Type: mds mitigation: Clear CPU buffers; SMT disabled 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: disabled, RSB filling Type: srbds mitigation: Microcode Type: tsx_async_abort mitigation: Clear CPU buffers; SMT disabled Graphics: Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: ASUSTeK driver: nvidia v: 440.82 bus ID: 01:00.0 chip ID: 10de:13c2 Display: x11 server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv compositor: kwin_x11 resolution: 3840x2160~30Hz OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 440.82 direct render: Yes Audio: Device-1: NVIDIA GM204 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fbb Device-2: VIA ICE1712 [Envy24] PCI Multi-Channel I/O driver: snd_ice1712 v: kernel bus ID: 03:00.0 chip ID: 1412:1712 Sound Server: ALSA v: k5.6.0-2-amd64 Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel port: c000 bus ID: 04:00.0 chip ID: 10ec:8168 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 3.18 TiB used: 6.82 GiB (0.2%) ID-1: /dev/sda vendor: Western Digital model: WDS100T2B0B size: 931.51 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 90WD scheme: GPT ID-2: /dev/sdb vendor: Western Digital model: WD2002FAEX-007BA0 size: 1.82 TiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1D05 scheme: MBR ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: MBR Partition: ID-1: / raw size: 51.81 GiB size: 50.74 GiB (97.95%) used: 6.82 GiB (13.4%) fs: ext4 dev: /dev/sda7 Sensors: System Temperatures: cpu: 37.0 C mobo: 29.8 C gpu: nvidia temp: 38 C Fan Speeds (RPM): N/A gpu: nvidia fan: 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 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 http://mx.mirror.ausnetservers.net.au/packages/mx/repo/ buster main non-free 2: deb http://mx.mirror.ausnetservers.net.au/packages/mx/repo/ buster ahs No active apt repos in: /etc/apt/sources.list.d/various.list Info: Processes: 186 Uptime: 7m Memory: 15.60 GiB used: 1.13 GiB (7.3%) 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
It's a UEFI install using existing partitions with / on sda7 and ESP on sda1, no other partitions used for MX.
Here's minstall.log , I couldn't make sense of it as I don't quite know what to look for: http://paste.debian.net/1155421/
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
- dolphin_oracle
- Developer
- Posts: 22251
- Joined: Sun Dec 16, 2007 12:17 pm
Re: MX-19.2 KDE Beta 1 feedback thread
all our Xfce settings are in the desktop-defaults-mx-xfce packages. there must be someting screwy with your copy from /etc/skel. I don't know how you did it, but don't do it while running Xfce...it won't work that way.JayM wrote: Tue Jul 07, 2020 1:55 am Just as an experiment I installed the xfce and desktop-defaults-mx-xfce metapackages hoping to be able to log out, select an Xfce session, log back in and get the same look and feel as in the current MX with Xfce but I just got a regular Debian-looking Xfce desktop and panel. Then I tried copying/pasting the contents of /etc/skel including hidden files from my host OS into my home directory in my MX KDE guest OS but it's still not looking like I want. I wonder if there's a way of bundling everything needed to give me an almost-complete MX Xfce DE as well as KDE? I don't care about things like the greeter or boot splash screen, just my Xfce desktop after I log in. Either an mx-xfce metapackage in one of the repos or an MX Xfce entry in Popular Apps/Desktop Environments. This would make it easier for support helpers: we could easily switch between the two DEs on a single installed system rather than taking up extra disk space for a dual-boot between two installed versions of MX then having to boot back and forth between them, plus logging out and in is faster than rebooting. Is it possible to have both default desktops in MX KDE?
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
Re: MX-19.2 KDE Beta 1 feedback thread
Thanks I went into the bios it looks like there is a switch to allow virtual machine (I have it turned off)fehlix wrote: Mon Jul 06, 2020 6:51 pmSuch warning can be ignored. OTOH, have you disable VM-bits (VT-x in intel) in bios. You might try to anable VT / Vm in bios.rrhobbs wrote: Mon Jul 06, 2020 10:13 am On boot there is a notice ... in Grub I guess? "(VMX) outside text not allowed per bios"
Here some patch discussion on kerenel.org:
https://patchwork.kernel.org/patch/11250771/
So probably nothing to worry about ...