Page 8 of 28
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 1:02 pm
by baldyeti
fehlix wrote: Tue Jul 07, 2020 12:26 pm
Also within the right-click menu: we have already an entry to open MXPI. I think it's a fair enough compromise.
Oh nice, i have to admit i had not paid attention to that menu. MXPI is there, perfect.
BTW the muon help page does not seem to exist yet.
Now for something completely different: in the bling department, would you consider enabling the "cover switch" effect under window mgt/task switcher ? It looks so darn good ;-)
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 1:05 pm
by baldyeti
asqwerth wrote: Tue Jul 07, 2020 12:57 pm
I tried to like Discover. You should see my posts in the dev team private board, heh.
I agree discover is a work in progress and i explicitly stated i was not asking for it. I just thought that maybe MXPI was sufficient in the default install, but muon is alright at least in buster.
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 1:23 pm
by asqwerth
baldyeti wrote: Tue Jul 07, 2020 1:02 pm
Now for something completely different: in the bling department, would you consider enabling the "cover switch" effect under window mgt/task switcher ? It looks so darn good ;-)
Nice! I haven't dug so deeply into the plasma settings yet. I was happy enough with hot-corner windows overview, since I use my mouse more than keyboard controls.
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 2:05 pm
by i_ri
MX Linux has the best installer in the business.
Hello dolphin_oracle and everyone . . Pardon me Sister while I swoon on the verge of swearing, Oh my stars, asked to invent a user account name, mxoid. is installed. second start with wlan0 up automatically. no kwallet dialogue with setting up wifi Thank you for that, though is seen kwallet in the menu.
no kdesu? found gksu yes. This is going to be familiar. Splendid.
Throw a upgrade in the bin, so we can see the little box, crate thingie light up. edit add: done. the notifier frame filled with color. did upgrade. color gone. it was sddm, so a reboot and back up no problem.
I need synaptic with my debian. with muon, fine. kinda like having apt and aptitude. konqueror?
Code: Select all
System: Host: 8440p Kernel: 5.6.0-2-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
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: Laptop System: Hewlett-Packard product: HP EliteBook 8440p v: N/A serial: <root required>
Chassis: type: 10 serial: <root required>
Mobo: Hewlett-Packard model: 172A v: KBC Version 30.35 serial: <root required>
BIOS: Hewlett-Packard v: 68CCU Ver. F.60 date: 11/11/2015
Battery: ID-1: BAT0 charge: 45.6 Wh condition: 46.8/46.8 Wh (100%) volts: 12.3/11.1
model: Hewlett-Packard Primary type: Li-ion serial: 01595 2011/08/15 status: Unknown
Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360 serial: 4004-13-87-a8-bd
charge: 100% (should be ignored) rechargeable: yes status: Discharging
CPU: Topology: Dual Core model: Intel Core i5 M 560 bits: 64 type: MT MCP arch: Nehalem rev: 5
L2 cache: 3072 KiB bogomips: 21284
Speed: 1758 MHz min/max: 1199/2667 MHz boost: enabled Core speeds (MHz): 1: 1758 2: 1897 3: 1864
4: 2633
Flags: acpi aes aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de
ds_cpl dtes64 dtherm dts est flush_l1d fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx monitor
msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pebs pge pni popcnt pse pse36 pti
rdtscp rep_good sep smx ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tsc vme xtopology
xtpr
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:0046
Display: x11 server: X.Org 1.20.4 driver: intel compositor: kwin_x11
resolution: 1600x900~60Hz, 1280x1024~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics (ILK) v: 2.1 Mesa 20.0.7 direct render: Yes
Network: Device-1: Intel 82577LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: 3.2.6-k
port: 5020 bus ID: 00:19.0 chip ID: 8086:10ea
Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 5000 bus ID: 43:00.0
chip ID: 8086:4239
Drives: Local Storage: total: 14.91 GiB used: 6.25 GiB (41.9%)
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://la.mxrepo.com/mx/repo/ buster main non-free
2: deb http://la.mxrepo.com/mx/repo/ buster ahs
No active apt repos in: /etc/apt/sources.list.d/various.list
Weather: Temperature: 29.1 C (84 F) Conditions: Scattered clouds Wind: from E at 1.1 m/s (4 km/h, 2 mph)
Cloud Cover: 75% Humidity: 70% Dew Point: 23.2 C (74 F) Pressure: 1014 mb (34 in)
Location: Washington, D.C., DC, US, 20500 Current Time: Tue 07 Jul 2020 01:51:27 PM EDT
Observation Time: 2020-07-07 12:59:00 (America/New_York -0400) Source: WeatherBit.io
Info: Processes: 188 Uptime: 22m Memory: 3.65 GiB used: 598.0 MiB (16.0%) Init: SysVinit v: 2.93
runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: konsole
inxi: 3.0.36
gone exploring ...
edit add: first start there is a welcome screen. never touched that window. second start no welcome screen. third start no welcome screen. second start there was that xmessage dbus msg. first and third start no xmessage about dbus. I just wait for the display dialogue to fade away. it sets extended monitor each time for dual. fine. ps_mem upon third start.
Code: Select all
Private + Shared = RAM used Program
96.0 KiB + 21.5 KiB = 117.5 KiB start_kdeinit
176.0 KiB + 32.0 KiB = 208.0 KiB acpid
192.0 KiB + 36.0 KiB = 228.0 KiB acpi_fakekeyd
220.0 KiB + 26.5 KiB = 246.5 KiB startkde
280.0 KiB + 49.5 KiB = 329.5 KiB init
316.0 KiB + 78.0 KiB = 394.0 KiB cron
428.0 KiB + 26.0 KiB = 454.0 KiB mdadm
480.0 KiB + 40.0 KiB = 520.0 KiB rpc.idmapd
588.0 KiB + 46.5 KiB = 634.5 KiB ksysguardd
624.0 KiB + 68.0 KiB = 692.0 KiB cgmanager
692.0 KiB + 36.0 KiB = 728.0 KiB ssh-agent
524.0 KiB + 210.5 KiB = 734.5 KiB rpcbind
512.0 KiB + 296.0 KiB = 808.0 KiB kwrapper5
656.0 KiB + 240.5 KiB = 896.5 KiB dconf-service
776.0 KiB + 209.0 KiB = 985.0 KiB dbus-launch (2)
284.0 KiB + 729.0 KiB = 1.0 MiB saned (2)
876.0 KiB + 183.0 KiB = 1.0 MiB rpc.statd
444.0 KiB + 620.5 KiB = 1.0 MiB avahi-daemon (2)
804.0 KiB + 355.0 KiB = 1.1 MiB getty (6)
1.1 MiB + 272.5 KiB = 1.4 MiB sudo
872.0 KiB + 559.0 KiB = 1.4 MiB dbus
1.3 MiB + 207.0 KiB = 1.5 MiB ntpd
1.1 MiB + 577.5 KiB = 1.6 MiB at-spi-bus-launcher
328.0 KiB + 1.4 MiB = 1.7 MiB kdeinit5
1.5 MiB + 369.5 KiB = 1.8 MiB gvfsd
1.7 MiB + 254.0 KiB = 1.9 MiB obexd
1.7 MiB + 621.5 KiB = 2.3 MiB sddm
1.6 MiB + 725.5 KiB = 2.4 MiB sddm-helper
1.8 MiB + 605.5 KiB = 2.4 MiB cupsd
928.0 KiB + 1.6 MiB = 2.5 MiB desktop.so
2.4 MiB + 160.0 KiB = 2.6 MiB bash
2.1 MiB + 587.0 KiB = 2.6 MiB upowerd
2.5 MiB + 428.0 KiB = 2.9 MiB dhclient
1.9 MiB + 1.0 MiB = 2.9 MiB cups-browsed
2.1 MiB + 1.0 MiB = 3.1 MiB xembedsniproxy
2.2 MiB + 999.0 KiB = 3.1 MiB kscreen_backend_launcher
3.0 MiB + 248.0 KiB = 3.3 MiB systemd-udevd
2.3 MiB + 1.1 MiB = 3.4 MiB gmenudbusmenuproxy
3.1 MiB + 471.5 KiB = 3.6 MiB systemd-logind
3.0 MiB + 697.5 KiB = 3.7 MiB dbus-daemon (4)
3.2 MiB + 528.0 KiB = 3.8 MiB gvfsd-fuse
3.3 MiB + 506.0 KiB = 3.8 MiB polkitd
4.0 MiB + 107.5 KiB = 4.1 MiB rsyslogd
3.6 MiB + 757.5 KiB = 4.3 MiB wpa_supplicant
4.2 MiB + 673.0 KiB = 4.9 MiB ModemManager
1.0 MiB + 3.9 MiB = 4.9 MiB file.so (3)
5.1 MiB + 27.0 KiB = 5.1 MiB haveged
4.3 MiB + 914.5 KiB = 5.2 MiB colord
4.7 MiB + 956.0 KiB = 5.6 MiB udisksd
4.2 MiB + 2.3 MiB = 6.5 MiB klauncher
4.3 MiB + 2.3 MiB = 6.6 MiB kaccess
5.4 MiB + 1.4 MiB = 6.8 MiB NetworkManager
4.7 MiB + 2.4 MiB = 7.1 MiB polkit-kde-authentication-agent-1
5.1 MiB + 2.1 MiB = 7.2 MiB kglobalaccel5
5.3 MiB + 1.9 MiB = 7.2 MiB conky
5.8 MiB + 2.0 MiB = 7.9 MiB kactivitymanagerd
5.4 MiB + 3.1 MiB = 8.5 MiB org_kde_powerdevil
7.3 MiB + 3.1 MiB = 10.5 MiB ksmserver
4.7 MiB + 5.9 MiB = 10.6 MiB kwalletd
8.7 MiB + 3.4 MiB = 12.1 MiB kdeconnectd
6.0 MiB + 6.3 MiB = 12.3 MiB kuiserver
11.3 MiB + 1.3 MiB = 12.6 MiB python3.7
13.0 MiB + 1.3 MiB = 14.3 MiB pulseaudio
15.7 MiB + 6.2 MiB = 21.9 MiB yakuake
21.5 MiB + 2.7 MiB = 24.2 MiB Xorg
17.1 MiB + 7.2 MiB = 24.3 MiB krunner
21.2 MiB + 4.3 MiB = 25.5 MiB python2.7
33.3 MiB + 11.9 MiB = 45.3 MiB kded5
39.6 MiB + 7.0 MiB = 46.7 MiB kwin_x11
125.0 MiB + 14.6 MiB = 139.6 MiB plasmashell
---------------------------------
563.3 MiB
=================================
keredmxoid@8440p:~
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 3:07 pm
by fehlix
sunrat wrote: Mon Jul 06, 2020 11:27 am
After booting it mostly seems to be behaving but I struck a minor warning message when using apt from terminal:
Code: Select all
# apt install zim
...
Fetched 1,167 kB in 1s (1,355 kB/s)
Unable to init server: Could not connect: Connection refused
(dpkg-preconfigure:6518): Gtk-WARNING **: 01:06:37.455: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
It then proceeded to complete the task successfully. I don't think it really should be looking for a Gnome frontend.
You might consider to change your way to run command under root, or alternativeyl how to open a root terminal,
If you enter the root-shell using "su -", the DISPLAY variable is not accessible for open a DISPLAY for debcon-front ends:
Here to reproduced the message above:
going into the root shell this (non recommended) way:
and running on the root prompt something to trigger debconf ui:
Code: Select all
# dpkg-reconfigure locales
Unable to init server: Could not connect: Connection refused
(dpkg-reconfigure:12134): Gtk-WARNING **: 20:56:15.522: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
So a better way of running apt which might trigger debconf frontend would be:
either just simple use:
or if you cannot resist to open a root-shell, which I'm rarely doing:
In both cases debconf-frontends get a proper connection to the display.
HTH
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 8:55 pm
by Sparky
The Devs must be very proud. I'm on the beta now and it looks *magnificent*!!!
I was on KDE for 2 years in the past so I am relatively familiar with it and this one looks great so far.
The only thing I know nothing about is Muon.
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 9:08 pm
by Adrian
The only thing I know nothing about is Muon.
It's the closest thing to Synaptic but a native KDE app, we are just trying to match MX-19 (Xfce edition) features, we tried other options but plasma-discover is only half-baked, only MX PackageInstaller is not enough, I would not necessarily like to have Synpatic on a KDE release so Muon is a natural choice. Personally, I mostly use apt in console and at most MX PackageInstaller.
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 9:54 pm
by sunrat
fehlix wrote: Tue Jul 07, 2020 3:07 pm
You might consider to change your way to run command under root, or alternativeyl how to open a root terminal,
If you enter the root-shell using "su -", the DISPLAY variable is not accessible for open a DISPLAY for debcon-front ends:
So I have to use sudo to run root commands? Never had to do that in Debian, don't even have it installed. I don't have DISPLAY variable issues using "su -" in Debian. Wouldn't it be preferable to keep Debian functionality?
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 10:14 pm
by fehlix
sunrat wrote: Tue Jul 07, 2020 9:54 pm
Wouldn't it be preferable to keep Debian functionality?
This thread is about MX-19.2 KDE Beta 1 feedback, so please open a new topic about the issue you have, as it is not related to this thread.
Re: MX-19.2 KDE Beta 1 feedback thread
Posted: Tue Jul 07, 2020 10:37 pm
by andyprough
The boot time on live usb with virtualbox was very slow, and left me with a blank screen for a long time. The first 3 times I tried it I thought it had died and ended the virtualbox session. The 4th time I decided to let it go for awhile and checked htop and found that vbox was very busy, so I let it keep going and KDE did come up. Would there be a way to have some type of graphic on the screen the entire time? The lengthy blank screen before going to the desktop is not uncommon with KDE, but in this case on vbox it just looks dead.
Once it is running it looks beautiful - I love that you themed it like regular MX. I feel like I'm basically in a regular MX XFCE session with lots of KDE tools.
I would recommend changing the default menu to be the whisker-style vertical menu instead of the slab. I very much dislike KDE's slab menu, and it's almost always the first thing I change with a new KDE setup. People not familiar with KDE may not know about their alternative menu options, and going with the whisker-style one that's most like the default MX XFCE menu might be a more comfortable transition.