Page 1 of 1
MX-19 RC1 Feedback thread
Posted: Tue Oct 15, 2019 4:23 pm
by dolphin_oracle
Now open for business, although sourceforge doens't have many mirrors on it right now, it should be up.
https://sourceforge.net/projects/mx-lin ... ing/MX-19/
Remember:
If posting hardware issues, please post the output of “quick-system-info” from the menu or terminal, at a minimum.
If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting installer issues, please include the contents of /var/log/minstall.log
If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 9:12 am
by Raitsa
Nothing but mxpected to report:
MX 19RC1 64bit downloaded, installed to a NUC D34010WYKH and language/keyboard/Firefox changed to finnish.
Everything just works 100% perfect.
All hail the MX crew.
https://media.giphy.com/media/XreQmk7ETCak0/giphy.gif
mod note: Image changed to link, please observe forum rules: https://forum.mxlinux.org/viewtopic.php?f=32&t=29041
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 10:52 am
by dreamer
The RC will receive updates over time through the repositories. The RC WILL update to Final via the normal update process.
So next release will be Final?
Is tumblerd monitor part of a package? My experience with tumblerd monitor in fully up to date beta 2.1 is that it doesn't work. Tumblerd won't quit until I close Thunar. So 50 % CPU activity until Thunar is closed.
It also seems that Xfce Task Manager reports wrong values for processes. Overall CPU activity is reported as 50 % (both in Task Manger and CPU Graph panel plugin), but top two processes in Task Manager are tumblerd with 2-3 % each.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 10:57 am
by WarhawkCZ
would it be possible to update RC to final later on?
(I am still stuck with beta 2, many things have happend since I left for a business trip :)
Great job everyone!
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 11:00 am
by dolphin_oracle
WarhawkCZ wrote: Wed Oct 16, 2019 10:57 am
would it be possible to update RC to final later on?
(I am still stuck with beta 2, many things have happend since I left for a business trip :)
Great job everyone!
yes, we support update from RC forward to final.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 11:18 am
by jackdanielsesq
dolphin_oracle wrote: Wed Oct 16, 2019 11:00 am
WarhawkCZ wrote: Wed Oct 16, 2019 10:57 am
would it be possible to update RC to final later on?
(I am still stuck with beta 2, many things have happend since I left for a business trip :)
Great job everyone!
yes, we support update from RC forward to final.
Beautiful ... thank you so much .. you Developers are all World Class ...
Highest Regards
Jack
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 11:44 am
by entropyfoe
dreamer,
Me to. This is NOT a RC issue, I had a lock-up (with new RAM sticks) where tumblerd was pegging one CPU to 100%, had to kill it in top.
Then I could down load the RC...so hopefully tonight will burn the RC and install for testing.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 11:54 am
by BV206
17" laptop with 1600x900 106 dpi display.
qpdfview Settings window is almost taller than the display and not resizeable.
I can only see the top part of the 3 buttons at the bottom of the window.
Additional info: I should have stated this happened with the panel on the bottom set to 30 pixels high and the Appearance custom DPI set to 106 to match the display.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 11:56 am
by Stuart_M
I just made a very quick check. I booted up to a Live instance of MX-19 RC1 from a Flash Drive and put the Panel horizontal on the bottom of the screen. I noticed there is a red line to the right of the unmount icon, but don't remember if that line was there when the panel was vertical before I made it horizontal.
Screenshot.png
This red line disappeared about a minute later, but don't remember if it disappeared before or after I clicked on the unmount icon, which just showed the Flash Drive I used to boot up.
I connected another Flash Drive that Thunar recognized, thinking that the line indicated something was mounted, but no red line appeared.
I booted up again with the same Flash Drive, but this time the red line never appeared.
What is that red line supposed to indicate?
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 12:00 pm
by richb
The red line signifies nothing. It is just an artifact that sometimes appears in the notification area. The reason is not really known as far as I know. Refreshing the panel wilt sometimes remove it.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 12:47 pm
by subluminal
Can I upgrade to RC1 from MX-19 beta 3?
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 12:49 pm
by dolphin_oracle
subluminal wrote: Wed Oct 16, 2019 12:47 pm
Can I upgrade to RC1 from MX-19 beta 3?
from the beta 3 release announcement:
The beta will receive updates over time through the repositories, but certain items, such as the live system and some user settings defaults, will not be obvious without some user intervention. Beta isos will always report themselves as beta versions in quick-system-info and inxi.
So you will get the updates but it will forever report itself as beta.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 12:57 pm
by subluminal
Thanks for the quick reply.
I don't mind inxi reporting as beta. But what do you mean by "some user settings defaults" ?? Can you elaborate please?
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 12:59 pm
by Jerry3904
Can you just wait until we get to that point, when we will explain to everybody in the Migration site on the website? Not all is known yet
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 1:08 pm
by subluminal
Ok. Understood.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 2:07 pm
by winemaker
sorry for sticking my oar in the water; but i believe one of the devs said to me when i asked it a while ago that there may be themes that may exist in beta but may not be in stable and various aspects like that so transferring that all over won;t be 100%. you may need to add and tweak or hope that certain things work. maybe i can find the thread.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 2:20 pm
by popjah
Thank you developers for this wonderful distribution! I've been with MX Linux for almost a year and love it.
About MX-19 RC1: is it possible to upload a torrent for the new iso? The link provided is too slow (15-20 kb/s).
Much appreciated, and thank you again!
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 2:30 pm
by vtvbreech
Only a few hours in but all seems well so far. I usually use the Adwaita-dark theme which is working fine but I can't seem to find the Adwaita-dark WM theme that was downloadable via MXPI previously. Has it been removed?
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 2:48 pm
by asqwerth
vtvbreech wrote: Wed Oct 16, 2019 2:30 pm
Only a few hours in but all seems well so far. I usually use the Adwaita-dark theme which is working fine but I can't seem to find the Adwaita-dark WM theme that was downloadable via MXPI previously. Has it been removed?
Add a package request in the appropriate sub-forum for MX19.
Adwaita dark never came with a proper WM theme. The latter was specially extracted and packaged for MX18 from a 3rd party gtk theme called adwaita-xfce-dark which is no longer maintained, but which WM theme still works for XFCE.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 2:56 pm
by rasat
Thank you, been waiting for this. This release is good. As a Gnome user everything looks fine and related packages are there. In beta "Gnome on Xorg" was missing. Good to know this RC will be updated to final.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 3:17 pm
by dolphin_oracle
winemaker wrote: Wed Oct 16, 2019 2:07 pm
sorry for sticking my oar in the water; but i believe one of the devs said to me when i asked it a while ago that there may be themes that may exist in beta but may not be in stable and various aspects like that so transferring that all over won;t be 100%. you may need to add and tweak or hope that certain things work. maybe i can find the thread.
the only differences are in default settings that live in the home folder (we never touch the home folder during upgrades), some default installed packages (gtk3-engines-xfce, bash-config, and fbreader were added), and if you are running live-usb, the live system is different from beta (the RC version has some new video selection options that most people won't need but if you do will appreciate).
This is why we say we support updates from RC forward rather than beta. And why beta isos will always report themselves as beta.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 3:23 pm
by gsm
Everything looks good.
I just managed the day before to make hplip work in MX Linux 18 for my P1102W.
But i have a problem again with the newer hplip version 3.19.6 in MX-19 RC1. It cannot detect my HP printer on the network.
I tried the MX Test repo, but same problem.
HPLIP cannot detect printers in your network.
This may be due to existing firewall settings blocking the required ports. When you are in a trusted network environment, you may open the ports for network services like mdns and slp in the firewall. For detailed steps follow the link.
http://hplipopensource.com/node/374
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 3:38 pm
by Gerson
I just installed both /root and /home zeros and when I want to access my saved files they appear with a padlock. I didn't change my username or my password and I'm the only user. How can I unlock them all?
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 4:02 pm
by Stevo
Gerson wrote: Wed Oct 16, 2019 3:38 pm
I just installed both /root and /home zeros and when I want to access my saved files they appear with a padlock. I didn't change my username or my password and I'm the only user. How can I unlock them all?
Did you chose to Reuse or to Save your /home?
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 4:04 pm
by Gerson
Stevo wrote: Wed Oct 16, 2019 4:02 pm
Gerson wrote: Wed Oct 16, 2019 3:38 pm
I just installed both /root and /home zeros and when I want to access my saved files they appear with a padlock. I didn't change my username or my password and I'm the only user. How can I unlock them all?
Did you chose to Reuse or to Save your /home?
No, the /home from zeros but I solved it with the command: chmod 770 -R /home/gerson
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 4:06 pm
by Stevo
Currently MX PI is installing the MX 17 version of the Liquorix kernels from Popular Apps--Kernels, which won't build the Nvidia drivers, even with the 435.21 driver from the test repo, due to the gcc mismatch.
A workaround until this is fixed is to install the header and image packages from the test repo tab instead; just search for Liquorix.
Va-api video hardware acceleration works out of the box with VLC using either the default kernel modesetting driver or the "intel" driver, which I switched to after still getting those annoying scrolling glitches in Firefox with the Skylake 520 Intel GPU with modesetting.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 4:50 pm
by winemaker
dolphin_oracle wrote: Wed Oct 16, 2019 3:17 pm
winemaker wrote: Wed Oct 16, 2019 2:07 pm
sorry for sticking my oar in the water; but i believe one of the devs said to me when i asked it a while ago that there may be themes that may exist in beta but may not be in stable and various aspects like that so transferring that all over won;t be 100%. you may need to add and tweak or hope that certain things work. maybe i can find the thread.
the only differences are in default settings that live in the home folder (we never touch the home folder during upgrades), some default installed packages (gtk3-engines-xfce, bash-config, and fbreader were added), and if you are running live-usb, the live system is different from beta (the RC version has some new video selection options that most people won't need but if you do will appreciate).
This is why we say we support updates from RC forward rather than beta. And why beta isos will always report themselves as beta.
sorry if i was far off - i did look for the thread and comment but did not have any luck. i was trying to recall what i read but either was so far off or else worded my response badly.
i apologize Dolphin_oracle. I tried.
:-)
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 6:32 pm
by vtvbreech
asqwerth wrote: Wed Oct 16, 2019 2:48 pm
vtvbreech wrote: Wed Oct 16, 2019 2:30 pm
Only a few hours in but all seems well so far. I usually use the Adwaita-dark theme which is working fine but I can't seem to find the Adwaita-dark WM theme that was downloadable via MXPI previously. Has it been removed?
Add a package request in the appropriate sub-forum for MX19.
Adwaita dark never came with a proper WM theme. The latter was specially extracted and packaged for MX18 from a 3rd party gtk theme called adwaita-xfce-dark which is no longer maintained, but which WM theme still works for XFCE.
No need for a package request, I'll simply move to a different theme. Thank you.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 7:38 pm
by Srdjan
Clock background in the panel a bit darker then the rest.
Code: Select all
System: Host: Lenovo Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=59b88264-eef6-44c1-882b-34bead552e10 ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: LENOVO product: 4384HE5 v: ThinkPad T510 serial: <filter>
Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 4384HE5 serial: <filter> BIOS: LENOVO v: 6MET92WW (1.52 )
date: 09/26/2012
Battery: ID-1: BAT0 charge: 27.0 Wh condition: 27.0/47.5 Wh (57%) volts: 12.1/10.8
model: LGC 42T4911 type: Li-ion serial: <filter> status: Full
CPU: Topology: Dual Core model: Intel Core i5 M 520 bits: 64 type: MT MCP arch: Nehalem
family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19151
Speed: 1600 MHz min/max: 1199/2400 MHz boost: enabled Core speeds (MHz): 1: 1762
2: 1795 3: 1834 4: 1787
Vulnerabilities: Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; 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
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo driver: i915
v: kernel bus ID: 00:02.0 chip ID: 8086:0046
Device-2: NVIDIA GT218M [NVS 3100M] driver: N/A bus ID: 01:00.0 chip ID: 10de:0a6c
Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k
port: 1820 bus ID: 00:19.0 chip ID: 8086:10ea
IF: eth0 state: down mac: <filter>
Device-2: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi v: kernel
port: 1880 bus ID: 03:00.0 chip ID: 8086:0084
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 111.80 GiB used: 6.10 GiB (5.5%)
ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 120 GB size: 111.80 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 00RL scheme: MBR
Partition: ID-1: / raw size: 109.77 GiB size: 107.54 GiB (97.97%) used: 6.10 GiB (5.7%) 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: System Temperatures: cpu: 63.0 C mobo: 0.0 C
Fan Speeds (RPM): cpu: 3070
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 217 Uptime: 58m Memory: 3.66 GiB used: 1011.8 MiB (27.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: quick-system-in inxi: 3.0.36
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 7:45 pm
by Srdjan
I really like you guys added that prompt selection profiles on terminal,
easy to apply, sure a lot of users will appreciate that! :)
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 7:55 pm
by Stevo
vtvbreech wrote: Wed Oct 16, 2019 6:32 pm
asqwerth wrote: Wed Oct 16, 2019 2:48 pm
vtvbreech wrote: Wed Oct 16, 2019 2:30 pm
Only a few hours in but all seems well so far. I usually use the Adwaita-dark theme which is working fine but I can't seem to find the Adwaita-dark WM theme that was downloadable via MXPI previously. Has it been removed?
Add a package request in the appropriate sub-forum for MX19.
Adwaita dark never came with a proper WM theme. The latter was specially extracted and packaged for MX18 from a 3rd party gtk theme called adwaita-xfce-dark which is no longer maintained, but which WM theme still works for XFCE.
No need for a package request, I'll simply move to a different theme. Thank you.
I just rebuilt it for MX 19, so it should be in main pretty soon as "adwaidta-xfce-wm-themes".
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 8:50 pm
by BV206
I think this is a MX 19 problem but I don't know how to troubleshoot this.
I downloaded the RC1 iso, made a usb stick, it booted with no problems.
I updated/upgraded it then I tried to make a persistent live USB.
Live USB Creator made the new USB with no errors.
I did everything the same as my 18.3 persistent live USB but it won't boot.
When I reboot the computer I get a quick flash of "Missing operating system" then the Grub on the HD boots the OS installed on the HD.
Gparted shows the same MX-Live-USB, MX-UEFI and encryted partitions as a good 18.3 USB.
I don't know how to tell what is going on.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 9:57 pm
by darknetmatrix
Everything just works 100% perfect over here, tnx to the dev.crew.
Re: MX-19 RC1 Feedback thread
Posted: Wed Oct 16, 2019 10:07 pm
by vtvbreech
Stevo wrote: Wed Oct 16, 2019 7:55 pm
I just rebuilt it for MX 19, so it should be in main pretty soon as "adwaidta-xfce-wm-themes".
Thank you Stevo, very much appreciate the effort
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 1:24 am
by JayM
BV206 wrote: Wed Oct 16, 2019 8:50 pm
I think this is a MX 19 problem but I don't know how to troubleshoot this.
I downloaded the RC1 iso, made a usb stick, it booted with no problems.
I updated/upgraded it then I tried to make a persistent live USB.
Live USB Creator made the new USB with no errors.
I did everything the same as my 18.3 persistent live USB but it won't boot.
When I reboot the computer I get a quick flash of
"Missing operating system" then the Grub on the HD boots the OS installed on the HD.
Gparted shows the same MX-Live-USB, MX-UEFI and encryted partitions as a good 18.3 USB.
I don't know how to tell what is going on.
Please run MX Tools/Quick System Info after booting your live USB, then right-click paste into a reply. (Quick System Info automatically copies the information to the clipboard and formats it properly for the forum so all you have to do is paste it.) Thanks.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 1:50 am
by penguin
Hi.
I have gone through this thread time by time.
Sorry if I repeat the same question.
Just a simple question. The update of MX 18.3 to MX 19 will be simply as .... Change Repos , upgrade system and reboot?
Or this will be not possible ?
I have managed to upgrade my Sparky Linux (month ago, simple by the described way and no problem at all. My Sparky Linux XFCE still runs on old XFCE (stable version predecessor of before 4.14).I am not sure how would be situation when the new XFCE will be included in Debian or Sparky repos.
Can we have the possibility to upgrade MX LInux in two steeps ?
1- Changing of Repos and upgrading of system without upgrading XFCE .
2- Adding a XFCE repo (if it is possible to have a different MX repo only for XFCE)
3- Upgrading of system with XFCE
Maybe what I am asking for is totally stupidity or wrong , but just a question.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 1:53 am
by JayM
I installed the 32-bit version on my Averatec 32-bit notebook this morning. It runs faster and smoother than MX-18. I love the screen that pops up when I connected my external monitor asking if I wanted to only use the netbook's display, mirror the two monitors, extend the desktop across both, or only use the external. Tha makes setting up multiple monitors easy. One little niggle though: after I made my selection my wallpaper got changed from the default one to an Xfce one with a mouse, and the wallpaper folder in Desktop Settings was changed from /usr/share/backgrounds/ to /usr/share/backgrounds/xfce/.
I went ahead and invested some time setting up the panels the way I like as I plan to just upgrade RC1 to the final release when the time comes.
Two problems with packages:
1. Lucky Backup as superuser doesn't run after I enter the root password. If I run it in a terminal it says
Code: Select all
jay@mx19:~
$ /usr/bin/luckybackup-pkexec
qt.qpa.screen: QXcbConnection: Could not connect to display
Could not connect to any X display.
2. When I use Zulucrypt GUI to decrypt my Veracrypt-encrypted external HDD where my backups live, I always get a message (after entering the passphrase) "Unrecognized ERROR with status number 255 encountered" and the decryption/mounting dialogue window doesn't close, yet it still decrypts and mounts the drive, mounting it under run/media/private/jay now instead of /run/media/private/root as it used to in MX-18.
My QSI:
Code: Select all
System: Host: mx19 Kernel: 4.19.0-6-686-pae i686 bits: 32 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/vmlinuz-4.19.0-6-686-pae
root=UUID=14a01254-11c5-4b33-83df-6a051e812e6f ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_386 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Other-vm? System: AVERATEC product: N1130 v: N/A serial: <filter>
Chassis: No Enclosure type: 1 serial: <filter>
Mobo: AVERATEC model: N1130 serial: <filter> BIOS: Phoenix
v: NAPA0001.86C.0056.D.0907311757 date: 07/31/09
Battery: ID-1: BAT0 charge: 65.3 Wh condition: 65.3/65.4 Wh (100%) volts: 65.5/N/A
model: AVERATEC N1130 type: Li-ion serial: N/A status: Full
CPU: Topology: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell
family: 6 model-id: 1C (28) stepping: 2 microcode: 218 L2 cache: 512 KiB
flags: nx pae sse sse2 sse3 ssse3 bogomips: 6384
Speed: 1059 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 1059 2: 1006
Vulnerabilities: Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1 status: Not affected
Type: spectre_v2 status: Not affected
Graphics: Device-1: Intel Mobile 945GSE Express Integrated Graphics driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:27ae
Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa
compositor: compton v: 0.1~beta2+20150922 resolution: 1280x1024~60Hz
OpenGL: renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
Sound Server: ALSA v: k4.19.0-6-686-pae
Network: Device-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0
port: 18e0 bus ID: 02:00.0 chip ID: 1814:3090
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169
v: kernel port: 2000 bus ID: 04:00.0 chip ID: 10ec:8136
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.93 TiB used: 1.22 TiB (63.1%)
ID-1: /dev/sda vendor: Gigabyte model: GP-GSTFS31120GNTD size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 61.3
scheme: MBR
ID-2: /dev/sdb type: USB vendor: Toshiba model: External USB 3.0 size: 1.82 TiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 5438
Partition: ID-1: / raw size: 109.24 GiB size: 107.03 GiB (97.97%) used: 6.33 GiB (5.9%) fs: ext4
dev: /dev/dm-0
ID-2: /boot raw size: 512.0 MiB size: 487.9 MiB (95.30%) used: 76.2 MiB (15.6%)
fs: ext4 dev: /dev/sda1
ID-3: swap-1 size: 1.98 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/dm-1
Sensors: System Temperatures: cpu: 39.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/antix.list
1: deb https://mirror.pregi.net/mx-linux-packages/antix//buster buster main
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
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 184 Uptime: 12m Memory: 1.90 GiB used: 388.4 MiB (20.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: quick-system-in inxi: 3.0.36
One final niggle: I changed my wallpaper to a darker one, and as I mentioned a while ago the default conky is almost impossible to see.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:01 am
by Eadwine Rose
penguin wrote: Thu Oct 17, 2019 1:50 am
Hi.
I have gone through this thread time by time.
Sorry if I repeat the same question.
Just a simple question. The update of MX 18.3 to MX 19 will be simply as .... Change Repos , upgrade system and reboot?
Or this will be not possible ?
I have managed to upgrade my Sparky Linux (month ago, simple by the described way and no problem at all. My Sparky Linux XFCE still runs on old XFCE (stable version predecessor of before 4.14).I am not sure how would be situation when the new XFCE will be included in Debian or Sparky repos.
Can we have the possibility to upgrade MX LInux in two steeps ?
1- Changing of Repos and upgrading of system without upgrading XFCE .
2- Adding a XFCE repo (if it is possible to have a different MX repo only for XFCE)
3- Upgrading of system with XFCE
Maybe what I am asking for is totally stupidity or wrong , but just a question.
No sorry, you will have to install fresh. You can keep /home for the config files and all.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:03 am
by asqwerth
MX conky was provided so you can change colours of the conky to suit your wallpaper. The conky can't conceivably be visually suitable for every wallpaper.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:25 am
by asqwerth
penguin wrote: Thu Oct 17, 2019 1:50 am
Hi.
I have gone through this thread time by time.
Sorry if I repeat the same question.
Just a simple question. The update of MX 18.3 to MX 19 will be simply as .... Change Repos , upgrade system and reboot?
Or this will be not possible ?
I have managed to upgrade my Sparky Linux (month ago, simple by the described way and no problem at all. My Sparky Linux XFCE still runs on old XFCE (stable version predecessor of before 4.14).I am not sure how would be situation when the new XFCE will be included in Debian or Sparky repos.
Can we have the possibility to upgrade MX LInux in two steeps ?
1- Changing of Repos and upgrading of system without upgrading XFCE .
2- Adding a XFCE repo (if it is possible to have a different MX repo only for XFCE)
3- Upgrading of system with XFCE
Maybe what I am asking for is totally stupidity or wrong , but just a question.
You can try but no promises if you break it. Or it may kind of work but not perfectly, and who's going to debug that? It's not recommended and won't be supported.
You're moving from a Debian base that had systemd-shim to one where it's deprecated in buster. MX had to get their own shim package done up for mx19 via a 3rd party developer.
Xfce 4.14 is gtk 3.
Settings and configs changes in mx19 affecting xfce and perhaps systemd-shim may not carry over using a change of repo, if changes were made inside the home partition.
So your mx18 settings may not go well with new xfce, etc in mx19.
I don't think you can realistically expect MX to just specially set up a separate mx19 repo for new xfce just so mx19 users can still use xfce 4.12 if they want
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:27 am
by JayM
asqwerth wrote: Thu Oct 17, 2019 2:03 am
MX conky was provided so you can change colours of the conky to suit your wallpaper. The conky can't conceivably be visually suitable for every wallpaper.
Yeah, I know, I was just kvetching.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 3:04 am
by Stufe
On MX19 RC1 x64 when selecting Grub install settings during the install process, choosing install to PBR doesn't automatically select the root partition. Eg installing MX to sda8, the automatically selected partition when selecting install grub to PBR was sda5 (existing MX18 installation). I would think it should automatically select the root partition.
Also Kodi for some reason doesn't include the Kodi repository!
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 3:18 am
by Eadwine Rose
As for your hardware info, please share MX Tools - quick system info
As for Kodi, please share the mxpi log
As per first post of this thread:
If posting hardware issues, please post the output of “quick-system-info” from the menu or terminal, at a minimum.
If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting installer issues, please include the contents of /var/log/minstall.log
If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 3:26 am
by Buck Fankers
Edit, sorry, scratch bellow, default button changed or is different than I usually use, my bad, everything is as it should be!
When I shut if off, it actually logged me out and waited there.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 3:30 am
by Stufe
The grub install doesn't look like a hardware issue, but I'm not an expert. - I was able to select sda8 for the grub install, just thought it should automatically choose the root install partition when clicking install to PBR. It's a minor thing in some regards, but due to my own haste, I initially didn't realise, so when I rebooted, the new MX19 install didn't boot, and I also had to reinstall grub on my mx18 partition.
Where is the mxpi log?
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 5:19 am
by penguin
asqwerth wrote: Thu Oct 17, 2019 2:25 am
penguin wrote: Thu Oct 17, 2019 1:50 am
Hi.
I have gone through this thread time by time.
Sorry if I repeat the same question.
Just a simple question. The update of MX 18.3 to MX 19 will be simply as .... Change Repos , upgrade system and reboot?
Or this will be not possible ?
I have managed to upgrade my Sparky Linux (month ago, simple by the described way and no problem at all. My Sparky Linux XFCE still runs on old XFCE (stable version predecessor of before 4.14).I am not sure how would be situation when the new XFCE will be included in Debian or Sparky repos.
Can we have the possibility to upgrade MX LInux in two steeps ?
1- Changing of Repos and upgrading of system without upgrading XFCE .
2- Adding a XFCE repo (if it is possible to have a different MX repo only for XFCE)
3- Upgrading of system with XFCE
Maybe what I am asking for is totally stupidity or wrong , but just a question.
You can try but no promises if you break it. Or it may kind of work but not perfectly, and who's going to debug that? It's not recommended and won't be supported.
You're moving from a Debian base that had systemd-shim to one where it's deprecated in buster. MX had to get their own shim package done up for mx19 via a 3rd party developer.
Xfce 4.14 is gtk 3.
Settings and configs changes in mx19 affecting xfce and perhaps systemd-shim may not carry over using a change of repo, if changes were made inside the home partition.
So your mx18 settings may not go well with new xfce, etc in mx19.
I don't think you can realistically expect MX to just specially set up a separate mx19 repo for new xfce just so mx19 users can still use xfce 4.12 if they want
Hmmmm. Ok thanks @asqwerth. At last the distro hoping, did serves me for something. Now I clearly realize for what a reason some Debian distros cannot upgraded smoothly to the next stage.
I have no any problem on my self. I can have a fresh install, backup partition and install to another computer or by personalized by my usb bootable snapshoot or just deploy as backup image and repair grub.
I have recommended MX Linux, but also installed to some of my friends and they are not expert, or simply they do not care to be expert or read about MX. They just use MX Linux. So... i a need to find the right way how to instruct them to upgrade to MX 19 (or they can still continue to use MX 18). Probably I need to have a physical touch of their machines to save my nerves and energies to upgrade their MX 18 to MX 19. How about the future ?
Seems that the critical point of MX Linux that does not allow to have a smooth upgrade remains system-shim.
Without having in mind to repeat discussions about system-shim in MX .... would be worthy to find a way ho to pass this glitch.
Sorry to bother again... but just to see possibilities or ideas for the future.
A MX Linux that starts with Systemd is fully functional ? No any problem at all ? If so, can some one starts MX Linux 18 in Systemd mode and upgrade MX to MX19 and remain with Systemd enabled ? Will be this a solution ?
In this case does not matter Systemd or not Systemd because is not To be or not To be....I do not care for this or for peoples opinion - at least Debian remains in Systemd and runs great ; OpenSuse runs Systemd and runs also great and .... authors of Systemd can improve it, let say in couple of months. This battle of being Systemd or not Systemd or system-Shim + Systemd for me seems like agony that needs a solution that will allow MX to have right approach for the future. The future of the distros as I see, aims rolling or at last having major upgrades more often.
With great respect for MX Linux team, devs and community. Sorry for bothering so much with my lines ,but I had not any bad intention in mind.
Last day I have experimented a lot with other distros . As I said. I want to recommend Linux to as much people I can, but first I should find the simplest way how to advice/help for upgrading of their system. As I said .... many people install Linux and they are not Linux enthusiast and have no intention to be.They just want to run a system in their laptop (free is possible, no viruses) and rest of the day .... to stick their fingers and mind on their smartphones
.
Best to all.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 5:36 am
by BitJam
penguin wrote: Thu Oct 17, 2019 5:19 am
A MX Linux that starts with Systemd is fully functional ? No any problem at all ? If so, can some one starts MX Linux 18 in Systemd mode and upgrade MX to MX19 and remain with Systemd enabled ? Will be this a solution ?
I don't know if this is relevant to your question but currently the MX live system only uses sysvinit, not systemd. It would be possible to make it work with systemd but the systemd devs seem to have made this unnecessarily difficult and painful for no good reason. They created new "standards" that were unnecessarily constricting that conflicted with what we had been doing for many years before systemd was started. It would have been just as easy for them to make their system easy to interface with rather than as difficult as possible.
The systemd devs did not get kicked out of kernel development because they were nice, considerate, and easy to work with. They've been a royal pain in the neck, making things difficult for everyone else, for no good reason.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 5:37 am
by asqwerth
Best to wait for mx19 to be officially released. Maybe at that time, some of the devs will be freer to assess any possible upgrade path. Maybe,maybe not.
I also think the xfce 4.14 change is also a significant factor against easy upgrade. Besides differences in settings, configs for gtk3 stuff, Packages and plug-ins may not be 100% equivalent with 4.12. Names may change. New packages may exist that don't get automatically pulled in on an upgrade. Old packages and plug-ins may be deprecated and not updated for 4.14.
Really, it's not doing your friends any favors to try to upgrade them from mx18 to mx19 with just a repo change. Mx18 is supported to 2022. If it works why change now?
Wait a while for assessment to happen first.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:05 am
by JayM
@penguin: As groovy as MX-19RC1 is, and MX-19's official released version is sure to be, I would recommend to your friends that they wait a while until the MX-19.1 point release is out, and just continue using 18.3 in the meantime. It's like a new version of Windows: wise people wait to upgrade until at least SP1 has been released for the new version, and meanwhile let the first adopters who can't wait identify and deal with the wee bugs and glitches.
Of course this is a matter of "do what I say, not as I do" because I just installed 19RC1 on my entire drive this morning,, but that was just my own decision which has a backstory (more hardware issues.) :(
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 7:30 am
by penguin
Thanks guys. I good point. Let's wait for MX 19.1, but also support till 2022, is a very good deal. At least, they are my friends and not my babies
. I can help them and show the path, but I can not continue
for them all the time.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 7:31 am
by Eadwine Rose
19.1? *giggle* MX19 isn't even final yet
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 7:35 am
by BitJam
BV206 wrote: Wed Oct 16, 2019 8:50 pm
I did everything the same as my 18.3 persistent live USB but it won't boot.
When I reboot the computer I get a quick flash of
"Missing operating system" then the Grub on the HD boots the OS installed on the HD.
Gparted shows the same MX-Live-USB, MX-UEFI and
encrypted partitions as a good 18.3 USB.
I don't know how to tell what is going on.
This is a bug in the latest live-usb-maker. Assume your live-usb is /dev/sdd and I'm assuming you're using the default msdos partitioning. You can verify the problem by running:
Code: Select all
sudo parted /dev/sdd print
[...]
Number Start End Size Type File system Flags
1 1049kB 157MB 156MB primary ext4
2 157MB 32.0GB 31.9GB primary boot
3 32.0GB 32.1GB 51.4MB primary fat32 esp
The first partition should be the boot partition but the 2nd is has the "boot" flag. You should be able to fix this in gparted or with this parted command:
Code: Select all
sudo parted /dev/sdd set 2 boot off set 1 boot on print
[...]
Number Start End Size Type File system Flags
1 1049kB 157MB 156MB primary ext4 boot
2 157MB 32.0GB 31.9GB primary
3 32.0GB 32.1GB 51.4MB primary fat32 esp
I replicated the problem you reported and I verified that the command above fixed it and got the live-usb to boot. I will next fix the LUM program. I believe this got broken when we added the data-first option. I think I tested data-first and data-first plus encryption but not encryption by itself.
I'm sorry for the inconvenience!
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 7:36 am
by JayM
Eadwine Rose wrote: Thu Oct 17, 2019 7:31 am
19.1? *giggle* MX19 isn't even final yet
I know. My advice to people, especially those who don't know Linux or MX that well and just want to use it, is to be patient and wait a while, maybe a few months, before upgrading to 19 and let a few more bugs get worked out if there are any..; At very least wait until MX-19 Official Release has been out for a month or so before having newbies tackle upgrading to it. This is a major release, MX-18 will still be supported for a couple-three years, so there's no hurry.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 8:14 am
by richb
JayM wrote: Thu Oct 17, 2019 7:36 am
Eadwine Rose wrote: Thu Oct 17, 2019 7:31 am
19.1? *giggle* MX19 isn't even final yet
I know. My advice to people, especially those who don't know Linux or MX that well and just want to use it, is to be patient and wait a while, maybe a few months, before upgrading to 19 and let a few more bugs get worked out if there are any..; At very least wait until MX-19 Official Release has been out for a month or so before having newbies tackle upgrading to it. This is a major release, MX-18 will still be supported for a couple-three years, so there's no hurry.
Or if you have the luxury of a large drive install MX 19 Final on another partiton(s) or on another drive. Keep 18.3 and "play" with 19. When you are comfortable with it and any bugs are quashed, I do not expect many, it can become your daily driver. That is what I have done. Although I have been running 19 since the first beta daily, I am keeping a copy of 18.3 on another drive for a while.
I intend to not fresh install final keeping RC1 up to date, depending on the final guidance from the Developers and it will be, actually currently is my daily driver.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 9:07 am
by BV206
JayM wrote: Thu Oct 17, 2019 1:24 am
BV206 wrote: Wed Oct 16, 2019 8:50 pm
I think this is a MX 19 problem but I don't know how to troubleshoot this.
I downloaded the RC1 iso, made a usb stick, it booted with no problems.
I updated/upgraded it then I tried to make a persistent live USB.
Live USB Creator made the new USB with no errors.
I did everything the same as my 18.3 persistent live USB but it won't boot.
When I reboot the computer I get a quick flash of
"Missing operating system" then the Grub on the HD boots the OS installed on the HD.
Gparted shows the same MX-Live-USB, MX-UEFI and encryted partitions as a good 18.3 USB.
I don't know how to tell what is going on.
Please run MX Tools/Quick System Info after booting your live USB, then right-click paste into a reply. (Quick System Info automatically copies the information to the clipboard and formats it properly for the forum so all you have to do is paste it.) Thanks.
OK but I think I can fix it now. I didn't know about the boot flag issue.
Code: Select all
System: Host: mx1 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: quiet splasht
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: Hewlett-Packard product: HP Pavilion g7 Notebook PC
v: 0690130000204610000620100 serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 3568 v: 21.46 serial: <filter> BIOS: Insyde v: F.6A
date: 05/13/2013
CPU: Topology: Dual Core model: AMD A4-3305M APU with Radeon HD Graphics bits: 64
type: MCP arch: Fusion family: 12 (18) model-id: 1 stepping: N/A microcode: 3000027
L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 7586
Speed: 801 MHz min/max: 800/1900 MHz boost: enabled Core speeds (MHz): 1: 800 2: 800
Vulnerabilities: Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: AMD Sumo [Radeon HD 6480G] vendor: Hewlett-Packard driver: radeon v: kernel
bus ID: 00:01.0 chip ID: 1002:9649
Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1600x900~60Hz
OpenGL: renderer: AMD SUMO2 (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1)
v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes
Audio: Device-1: AMD BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G series]
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:01.1
chip ID: 1002:1714
Device-2: AMD FCH Azalia vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter vendor: Hewlett-Packard
driver: rtl8192ce v: kernel port: 3000 bus ID: 01:00.0 chip ID: 10ec:8176
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet
vendor: Hewlett-Packard RTL810xE driver: r8169 v: kernel port: 2000 bus ID: 02:00.0
chip ID: 10ec:8136
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 310.69 GiB used: 5.90 GiB (1.9%)
ID-1: /dev/sda vendor: PNY model: CS900 240GB SSD size: 223.57 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 0208 scheme: MBR
ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 29.81 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR
ID-3: /dev/sdc type: USB vendor: SanDisk model: Ultra Fit size: 57.30 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
Partition: ID-1: / raw size: N/A size: 2.63 GiB used: 23.7 MiB (0.9%) fs: overlay
source: ERR-102
Sensors: System Temperatures: cpu: 42.9 C mobo: N/A gpu: radeon temp: 49 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 186 Uptime: 3m Memory: 3.34 GiB used: 559.7 MiB (16.4%) 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
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 9:13 am
by winemaker
JayM and RichB - that sounds like good sound advice. esp someone like me who needs a serious working system daily and also am too dumb to work out any glitches if there are a few gremlins left. i was seriously thinking of maybe installing rc1 today if i get the time but i may ponder that thought a bit more.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 9:27 am
by chrispop99
winemaker wrote: Thu Oct 17, 2019 9:13 am
JayM and RichB - that sounds like good sound advice. esp someone like me who needs a serious working system daily and also am too dumb to work out any glitches if there are a few gremlins left. i was seriously thinking of maybe installing rc1 today if i get the time but i may ponder that thought a bit more.
Alternatively if you have a USB pen drive, set it up live with persistence and see if MX-19 works well for you. All your files within your MX-18 install will be accessible to you should you want them.
Chris
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 9:29 am
by richb
chrispop99 wrote: Thu Oct 17, 2019 9:27 am
winemaker wrote: Thu Oct 17, 2019 9:13 am
JayM and RichB - that sounds like good sound advice. esp someone like me who needs a serious working system daily and also am too dumb to work out any glitches if there are a few gremlins left. i was seriously thinking of maybe installing rc1 today if i get the time but i may ponder that thought a bit more.
Alternatively if you have a USB pen drive, set it up live with persistence and see if MX-19 works well for you. All your files within your MX-18 install will be accessible to you should you want them.
Chris
+1
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 9:39 am
by Jerry3904
Even more alternatively, run 19 in a VM on 18 for a while--or vice versa (what I will do on my production machine)
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 9:41 am
by BV206
OK but I think I can fix it now. I didn't know about the boot flag issue.
This morning I noticed LUM was one of the packages that upgraded before I tried to make another USB.
I set the boot flags as what is shown a few posts back.
Now at least it can find the correct boot partition on the USB but then I get:
Fatal error
Encrypted device /dev/sdb2 is not a LUKS device.
I had encrypt checked in LUM so it looks like it made an encrypted partition but it can't use it for some reason.
If I don't check encrypt in LUM then it makes the USB with the correct boot flags and it boots normally.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 10:42 am
by gimbleguy
I'm using MXlinux 19-RC1 on Virtualbox. So far it's really good.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 11:25 am
by mklym
Installed MX-19RC1 on my CF-29 this morning. All went well, including setting up an SD card as swap. Will do testing tonight, as time allows. Thanks for all the hard work the Devs have put into MX-19 to get it to this point.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 11:43 am
by rasat
Everything works fine. I have one change I would like. How to change the /boot/grub/themes/linen/theme.txt not to show the few seconds of terminal image when launching the boot. The Debian background maybe from my previous grub setting, so how to skip this stage? See the screenshoot.
http://amurt.ro/download/mx/grub-screen-mx19rc1.jpg
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 11:46 am
by bpr323
dolphin_oracle wrote: Tue Oct 15, 2019 4:23 pm
Now open for business, although sourceforge doens't have many mirrors on it right now, it should be up.
https://sourceforge.net/projects/mx-lin ... ing/MX-19/
Remember:
If posting hardware issues, please post the output of “quick-system-info” from the menu or terminal, at a minimum.
If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting installer issues, please include the contents of /var/log/minstall.log
If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
I'm happy to confirm that after multiple updates to mx-installer coming through the updater, I could finally LUM and auto-install 19b3 snapshot ISO to bare metal X1 NVMe without a glitch - Woo-hoo!!
Spent about an hour with ArcoLinux, and they have some nasty issue with Thunar which spends like a whole minute before opening smb shares on my Libreelec media server.
5 minutes later, and I'm back on my MX desktop with a snapshot USB!
Hope my testing helped with nailing down the mx-installer issues.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 11:49 am
by dolphin_oracle
bpr323 wrote: Thu Oct 17, 2019 11:46 am
dolphin_oracle wrote: Tue Oct 15, 2019 4:23 pm
Now open for business, although sourceforge doens't have many mirrors on it right now, it should be up.
https://sourceforge.net/projects/mx-lin ... ing/MX-19/
Remember:
If posting hardware issues, please post the output of “quick-system-info” from the menu or terminal, at a minimum.
If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.
If posting remaster issues, please include the contents of /var/log/live/live-remaster.log
If posting installer issues, please include the contents of /var/log/minstall.log
If posting issues with MX-PackageInstaller “Popular Apps”, please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).
I'm happy to confirm that after multiple updates to mx-install coming through, I could finally auto-install 19b3 snapshot ISO to bare metal on my X1 without a glitch - Woo-hoo!!
Spent about an hour with ArcoLinux, and they have some issue with Thunar which spends like a whole minute before opening smb shares on my Libreelec media server.
5 minutes later, and I'm back on my MX desktop with a snapshot USB!
Hope my testing helped with nailing down the mx-installer issues.
nice! your reports were key. thank you.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 12:07 pm
by bpr323
Stuart_M wrote: Wed Oct 16, 2019 11:56 am
I just made a very quick check. I booted up to a Live instance of MX-19 RC1 from a Flash Drive and put the Panel horizontal on the bottom of the screen. I noticed there is a red line to the right of the unmount icon, but don't remember if that line was there when the panel was vertical before I made it horizontal.
Screenshot.png
This red line disappeared about a minute later, but don't remember if it disappeared before or after I clicked on the unmount icon, which just showed the Flash Drive I used to boot up.
I connected another Flash Drive that Thunar recognized, thinking that the line indicated something was mounted, but no red line appeared.
I booted up again with the same Flash Drive, but this time the red line never appeared.
What is that red line supposed to indicate?
Mate, you've got a bum steer answer on page 1 - it's not a "red line" - it's a duplicate of an icon to the right, which is tucked under your "infected" icon.
It happens to the mx-update panel icon most of the time.
mx panel icon shadowing.png
In my case if you point the tip of your cursor at the little white bit that protrudes on the right side of the mx-updater icon, it actually opens the USB Unmounter - the "full" icon of which is on the right and also functional. I've reported this issue in the 19b3 feedback thread, and ... crickets :) Doesn't happen with the XFCE panel on ArcoLinux though
A work-around "cure" is to move the Updater icon to the right so that it sits next to the Log Out (green) icon on its right - now it's "clean" :)
mx panel icon shadowing2.png
mx panel icon shadowing3.png
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 12:26 pm
by richb
Not a fix but a temporary solution for me. I have some hidden icons that I do not use. For example the removable device unmounter. That puts a right pointing arrow at the right of the notification ares. Clicking that to display the hidden icons and clicking it again to hide them eliminates any additional overlayed icons. This may be no help for you if you have all the icons displayed. But I throw it out there anyway.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 12:34 pm
by bpr323
richb wrote: Thu Oct 17, 2019 12:26 pm
Not a fix but a temporary solution for me. I have some hidden icons that I do not use. For example the removable device unmounter. That puts a right pointing arrow at the right of the notification ares. Clicking that to display the hidden icons and clicking it again to hide them eliminates any additional overlayed icons. This may be no help for you if you have all the icons displayed. But I throw it out there anyway.
I've just uninstalled clipit rather than hiding it - couldn't figure out how to use it ))
See how the VLC icon gets "infected" by the vlume icon on its right?
mx panel icon shadowing4.png
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 12:39 pm
by Eadwine Rose
It's a known problem, reported in the betas already. Nothing that we can fix, it's Xfce's issue.
At least.. that is what I understood.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 12:46 pm
by richb
And my suggested band aid requires hiding an icon, not deleting one. But as I said it is not a solution. It most likely is an XFCE issue.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 1:03 pm
by asqwerth
I just hide the volume icon in notification area because I prefer the pulse audio plug-in that goes onto the panel.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 1:19 pm
by Stuart_M
bpr323 wrote: Thu Oct 17, 2019 12:07 pm
Mate, you've got a bum steer answer on page 1 - it's not a "red line" - it's a duplicate of an icon to the right, which is tucked under your "infected" icon.
It happens to the mx-update panel icon most of the time.
Right you are! Looking closer to the image attachment I have on my post #9, I can see the "red line" duplicates the curved right side of the circular icon immediately to its right. The circular icon is white, but the "line" is red for some reason.
It made sense when you said that it happens to the mx-update icon most of the time because I remembered seeing a thin (a few pixels wide) "red line" to the right of this update icon, and in both cases the "line" suddenly disappears after a few minutes.
Thanks for the clarification!
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 1:52 pm
by bpr323
richb wrote: Thu Oct 17, 2019 12:46 pm
And my suggested band aid requires hiding an icon, not deleting one. But as I said it is not a solution. It most likely is an XFCE issue.
No it's not. I've just had temporarily on my X1 the ArcoLinux XFCE edition - and there's absolutely no artifacts in the panel.
It's how the notification area is integrated into the shell. Something is impacting on it in MX causing it to falter, maybe one of the aps in notification area... who knows
Definitely not clipit - I uninstalled it (not deleted the icon).
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:01 pm
by bpr323
asqwerth wrote: Thu Oct 17, 2019 1:03 pm
I just hide the volume icon in notification area because I prefer the pulse audio plug-in that goes onto the panel.
Yes, it doesn't integrate with pilse audio (pavucontrol) and doesn't change the volume at all, at least across BT interface
You can safely uninstall it - volumeicon-alsa in MPI rather than hiding, it won't affect alsa - I did it and the sound kept on working :)
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:12 pm
by Eadwine Rose
Huh.. then I must have a weird install because the thing works for me *scratches head*
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:39 pm
by Stevo
Stufe wrote: Thu Oct 17, 2019 3:04 am
On MX19 RC1 x64 when selecting Grub install settings during the install process, choosing install to PBR doesn't automatically select the root partition. Eg installing MX to sda8, the automatically selected partition when selecting install grub to PBR was sda5 (existing MX18 installation). I would think it should automatically select the root partition.
Also Kodi for some reason doesn't include the Kodi repository!
That's the Debian Buster build of Kodi 17.6. Are you referring to an official Kodi addon repository, or one of the many third-party ones which are nothing more than wretched hives of scum and villainy? I'm pretty sure Debian disables unofficial Kodi repos for security reasons.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:50 pm
by Stevo
penguin wrote: Thu Oct 17, 2019 7:30 am
Thanks guys. I good point. Let's wait for MX 19.1, but also support till 2022, is a very good deal. At least, they are my friends and not my babies
. I can help them and show the path, but I can not continue
for them all the time.
Those that have upgraded xfce 4.12 to 4.14 on MX 18 via my OBS repo, including my test installs, report that it went quite smoothly, so I don't think that will be an issue when saving /home when doing the MX 18 to MX 19 reinstall.
Maybe if you wait a bit after MX 19 is out, we'll have an MX migration app that duplicates many of the functions of aptik-gtk, which is no longer developed as freeware. For now, you can install aptik-gtk and use it to save a list of your installed packages, then reinstall it in MX 19 and use that list to reinstall those packages.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 2:58 pm
by winemaker
in chromium with the rc1 when i tried importing the bookmarks i had in my documents>MX linux folder usually you click on documents, then mxlinux folder which opens and choose the html bookmarks backup file. took me a few attempts but it appears that you have to choose a folder then click open at the bottom right and then click on the respective folder again to open etc. is this an mx thing now or chromium issue? was totally fine and so-called normal in 18.3. just letting you know. i happen to just come around to making it work in an unorthodox way.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 3:15 pm
by ChrisUK
Stevo wrote: Thu Oct 17, 2019 2:50 pm
[...]
Maybe if you wait a bit after MX 19 is out, we'll have an MX migration app that duplicates many of the functions of aptik-gtk, which is no longer developed as freeware. For now, you can install aptik-gtk and use it to save a list of your installed packages, then reinstall it in MX 19 and use that list to reinstall those packages.
The free version of
aptik still works fine... I just installed the MX-19 RC and then restored all of my Home/settings/apps*/mounts (swapfile fstab settings) etc from 18.3 without any problems. But I'll do the same when I get time on another Laptop just to check.
*(As usual, only missing or updated apps/libs are (re)installed)
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 3:18 pm
by richb
bpr323 wrote: Thu Oct 17, 2019 2:01 pm
asqwerth wrote: Thu Oct 17, 2019 1:03 pm
I just hide the volume icon in notification area because I prefer the pulse audio plug-in that goes onto the panel.
Yes, it doesn't integrate with pilse audio (pavucontrol) and doesn't change the volume at all, at least across BT interface
You can safely uninstall it - volumeicon-alsa in MPI rather than hiding, it won't affect alsa - I did it and the sound kept on working :)
Thanks for checking in another distro. All I can say is that I can get rid of it. If you discover a real solution let us all know.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 3:20 pm
by dolphin_oracle
the icon thing well could be due to the mix of gtk2 vs. gtk3 and qt icon settings. there is quite a mix in there at the moment.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 3:21 pm
by dreamer
It's easier to trigger tumblerd with root Thunar, because that image cache is probably almost empty. This time tumblerd monitor killed it so I guess it works the same as in MX-17/18. All in all MX-19 feels remarkably similar to MX 17/18 despite different base and new Xfce. This is a good accomplishment. I know there are a few new features too. And LightDM seems to be gone from restart/shut down.
Stevo wrote: Thu Oct 17, 2019 2:50 pm
penguin wrote: Thu Oct 17, 2019 7:30 am
Thanks guys. I good point. Let's wait for MX 19.1, but also support till 2022, is a very good deal. At least, they are my friends and not my babies
. I can help them and show the path, but I can not continue
for them all the time.
Those that have upgraded xfce 4.12 to 4.14 on MX 18 via my OBS repo, including my test installs, report that it went quite smoothly, so I don't think that will be an issue when saving /home when doing the MX 18 to MX 19 reinstall.
Maybe if you wait a bit after MX 19 is out, we'll have an MX migration app that duplicates many of the functions of aptik-gtk, which is no longer developed as freeware. For now, you can install aptik-gtk and use it to save a list of your installed packages, then reinstall it in MX 19 and use that list to reinstall those packages.
That's good and time-saving info. Is it possible to preserve /home in the installer if /home is located on the root partition?
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 4:02 pm
by Gordon Cooper
I downloaded MX-19RC1, transferred if to a USB drive, then wasted an hour trying to install it. I found that the installation
was much better when i plugged in the correct USB drive. MX19 was still lying on the desk. Now, it works like a dream. No problems!
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 4:08 pm
by winemaker
ok so on my x series 201 thinkpad this works great re: showing login screen after suspend. never did on 18.3 - blank black page that you had to start typing blind or else touch trackpad to get login to show that is great news! That was the only glitch i had with the 2 tp's and my wife's dell inspiron. will let you know about the x 220 series when i load it on that laster hopefully.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 4:39 pm
by Srdjan
The clock background in the panel has slightly different background color, here
is the image, can this be somehow fixed?
Screenshot-2.png
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 5:14 pm
by winemaker
winemaker wrote: Thu Oct 17, 2019 2:58 pm
in chromium with the rc1 when i tried importing the bookmarks i had in my documents>MX linux folder usually you click on documents, then mxlinux folder which opens and choose the html bookmarks backup file. took me a few attempts but it appears that you have to choose a folder then click open at the bottom right and then click on the respective folder again to open etc. is this an mx thing now or chromium issue? was totally fine and so-called normal in 18.3. just letting you know. i happen to just come around to making it work in an unorthodox way.
Ok maybe the reason was that i turned the double click off to1 MS instead of the 400 or 401 when i retweaked it. i remember that i had to shut the click after shutting down the trackpad while typing to zero so that i did not get a funky lag -so i tweaked the wrong one. all should work fine - and i apologize for anymore gray hairs to the devs.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 5:52 pm
by winemaker
ok installed and now tweaking on thinkpad220 x series. updates popeed up even though i updated upon install and i got this error
9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,202 kB of archives.
After this operation, 47.1 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1
http://mxrepo.com/mx/repo buster/main amd64 live-usb-maker all 0.4.1~2 [35.0 kB]
Ign:2
http://mxrepo.com/mx/repo buster/main amd64 apt-notifier all 19.10.17mx19+1
Get:3
http://mxrepo.com/mx/repo buster/main amd64 ddm-mx all 19.10.02 [54.8 kB]
Get:4
http://mxrepo.com/mx/repo buster/main amd64 libmypaint-common all 1.3.0-3mx19+1 [80.4 kB]
Get:5
http://mxrepo.com/mx/repo buster/main amd64 libmypaint-1.3-0 amd64 1.3.0-3mx19+1 [32.1 kB]
Get:6
http://mxrepo.com/mx/repo buster/main amd64 mx-installer amd64 19.10.04 [301 kB]
Get:7
http://mxrepo.com/mx/repo buster/main amd64 mx-live-usb-maker amd64 19.10 [121 kB]
Get:8
http://mxrepo.com/mx/repo buster/main amd64 mx-packageinstaller-pkglist all 19.10.03 [124 kB]
Get:9
http://mxrepo.com/mx/repo buster/main amd64 mx-packageinstaller amd64 19.10.01 [329 kB]
Err:2
http://mxrepo.com/mx/repo buster/main amd64 apt-notifier all 19.10.17mx19+1
404 Not Found [IP: 70.40.214.183 80]
Fetched 1,077 kB in 1s (1,385 kB/s)
E: Failed to fetch
http://mxrepo.com/mx/repo/pool/main/a/a ... +1_all.deb 404 Not Found [IP: 70.40.214.183 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
full upgrade complete (or was canceled)
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:01 pm
by Lupin
finished installing 19 RC1 on VM couple of hours ago, it's running like a charm, all is good. I appreciate MX's team for the hard work.
i'm not sure it's really gone now or not cause im running it from VM ,but in 18.3 when i play videos on vlc in fullscreen, clicking on seek bar causes the panel to popup on the video and also causes screen flickering, which i'm not seeing it happen anymore on 19 rc1. i hope this is true.
one last minor bug that i encountered is plank's old bug (panel setting window sticks there forever). i wish plank's devs finally do something about that.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:03 pm
by dolphin_oracle
Srdjan wrote: Thu Oct 17, 2019 4:39 pm
The clock background in the panel has slightly different background color, here
is the image, can this be somehow fixed?
Screenshot-2.png
yes.
you right click the clock and select a different color.
part of the issue is the default theme has a partially transparent panel and the clock plugin doesn't do transparency very well.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:06 pm
by Srdjan
Fixed, thanks a lot! :)
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:07 pm
by kmathern
I sent the 19.10.17mx19+1 update to Tim (timkb4cq) about an hour ago.
It looks like the package list (
http://mxrepo.com/mx/repo/dists/buster/ ... 4/Packages) got updated to point to the new version, but I don't see that .deb file in the pool folder yet (
http://mxrepo.com/mx/repo/pool/main/a/apt-notifier/).
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:10 pm
by Srdjan
yeah, just god that message too...
Code: Select all
full upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
apt-notifier (19.10.08mx19+1 => 19.10.17mx19+1)
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 125 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Ign:1 http://mxrepo.com/mx/repo buster/main amd64 apt-notifier all 19.10.17mx19+1
Err:1 http://mxrepo.com/mx/repo buster/main amd64 apt-notifier all 19.10.17mx19+1
404 Not Found [IP: 70.40.214.183 80]
E: Failed to fetch http://mxrepo.com/mx/repo/pool/main/a/apt-notifier/apt-notifier_19.10.17mx19+1_all.deb 404 Not Found [IP: 70.40.214.183 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
full upgrade complete (or was canceled)
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:28 pm
by winemaker
ahhh ok - I was thinkg that when i went out with the dog. thanks,
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:30 pm
by Laurentius
Just after booting from live usb, the mid part of the panel, from window buttons to launchers and workspace switcher does not seem to apply themes. it look light grey while the rest of the panel is dark (checked with different themes) (first image)
Code: Select all
[code]
System: Host: mx1 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: quiet splasht
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: Hewlett-Packard product: Compaq Presario CQ40 Notebook PC
v: F.31 serial: <filter> Chassis: Compal type: 10 serial: <filter>
Mobo: Compal model: 3607 v: 99.97 serial: <filter> BIOS: Hewlett-Packard v: F.31
date: 02/03/2009
Battery: ID-1: BAT0 charge: 65.3 Wh condition: 95.0/95.0 Wh (100%) volts: 11.1/10.8
model: Hewlett-Packard Primary type: Li-ion serial: N/A status: Discharging
CPU: Topology: Dual Core model: Pentium T4200 bits: 64 type: MCP arch: Penryn family: 6
model-id: 17 (23) stepping: A (10) microcode: A0B L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 7980
Speed: 1428 MHz min/max: 1200/2000 MHz Core speeds (MHz): 1: 1363 2: 1379
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42
Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1280x800~60Hz
OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:293e
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY vendor: Hewlett-Packard
driver: wl v: kernel port: 7000 bus ID: 03:00.0 chip ID: 14e4:4315
IF: wlan0 state: dormant mac: <filter>
Device-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet
vendor: Hewlett-Packard RTL810xE driver: r8169 v: kernel port: 3000 bus ID: 04:00.0
chip ID: 10ec:8136
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 150.92 GiB used: 101.68 GiB (67.4%)
ID-1: /dev/sda vendor: Samsung model: HM160HI size: 149.05 GiB block size:
physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: 0-15 scheme: MBR
ID-2: /dev/sdb type: USB vendor: Kingston model: DT 101 G2 size: 1.87 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
Partition: ID-1: / raw size: N/A size: 2.96 GiB used: 72.9 MiB (2.4%) fs: overlay
source: ERR-102
ID-2: swap-1 size: 1.96 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda2
Sensors: System Temperatures: cpu: 56.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/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 212 Uptime: 24m Memory: 3.76 GiB used: 1.05 GiB (28.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: quick-system-in inxi: 3.0.36
Video Tweaks:
pre-sandybridge UXA acceleration
[/code]
EDIT> Well, i went to mx tweak and resored default panel and now it is good. May be a little too much transparency in the background with greybird-mx (but that may be on purpose). (second image)
And the icons on window buttons are too small. (but that's an xfce thing isn't it?
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:39 pm
by Srdjan
Why there is no option for shutdown on Laptop lid closed (in power manager settings)?
Can that be added somehow?
Also, I have set power button to shut down, and nothing happens if I press power button on laptop.
Screenshot-3.png
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:41 pm
by BitJam
BV206 wrote: Thu Oct 17, 2019 9:41 am
Now at least it can find the correct boot partition on the USB but then I get:
Fatal error
Encrypted device /dev/sdb2 is not a LUKS device.
I had encrypt checked in LUM so it looks like it made an encrypted partition but it can't use it for some reason.
Unfortunately, I have not yet been able to replicate this problem here although others have.
If your live-usb is at /dev/sdd then what is the output of:
Code: Select all
sudo lsblk -o name,fstype,label /dev/sdd
Here the output looks like:
Code: Select all
NAME FSTYPE LABEL
sdd
├─sdd1 ext4 MX-Live-usb
├─sdd2 crypto_LUKS
└─sdd3 vfat MX-UEFI
I think I can fix the problem once I'm able to replicate it.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:46 pm
by asqwerth
dreamer wrote: Thu Oct 17, 2019 3:21 pm...
That's good and time-saving info. Is it possible to preserve /home in the installer if /home is located on the root partition?
It should from past experience. I haven't had time to install MX19 rc yet.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 6:49 pm
by richb
Yes, I just did so in RC1 install yesterday.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 7:30 pm
by anticapitalista
BitJam wrote: Thu Oct 17, 2019 6:41 pm
BV206 wrote: Thu Oct 17, 2019 9:41 am
Now at least it can find the correct boot partition on the USB but then I get:
Fatal error
Encrypted device /dev/sdb2 is not a LUKS device.
I had encrypt checked in LUM so it looks like it made an encrypted partition but it can't use it for some reason.
Unfortunately, I have not yet been able to replicate this problem here although others have.
If your live-usb is at /dev/sdd then what is the output of:
Code: Select all
sudo lsblk -o name,fstype,label /dev/sdd
Here the output looks like:
Code: Select all
NAME FSTYPE LABEL
sdd
├─sdd1 ext4 MX-Live-usb
├─sdd2 crypto_LUKS
└─sdd3 vfat MX-UEFI
I think I can fix the problem once I'm able to replicate it.
Just to jump in as I get the same error.
Code: Select all
sudo lsblk -o name,fstype,label /dev/sdb
[sudo] password for anticap:
NAME FSTYPE LABEL
sdb
├─sdb1 ext4 antiX-Live-usb
├─sdb2 crypto_LUKS
└─sdb3 vfat ANTIX-UEFI
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 8:41 pm
by BV206
I had to make another USB. I still get
Fatal error Encrypted device /dev/sdb2 is not a LUKS device.
Here is the lsblk output.
Code: Select all
$ sudo lsblk -o name,fstype,label /dev/sdc
NAME FSTYPE LABEL
sdc
├─sdc1 ext4 MX-Live-usb
├─sdc2 crypto_LUKS
└─sdc3 vfat MX-UEFI
I don't know if it makes any difference but this laptop is about 2010-2011 vintage and has the old style BIOS.
Re: MX-19 RC1 Feedback thread
Posted: Thu Oct 17, 2019 8:52 pm
by dolphin_oracle
BV206 wrote: Thu Oct 17, 2019 8:41 pm
I had to make another USB. I still get
Fatal error Encrypted device /dev/sdb2 is not a LUKS device.
Here is the lsblk output.
Code: Select all
$ sudo lsblk -o name,fstype,label /dev/sdc
NAME FSTYPE LABEL
sdc
├─sdc1 ext4 MX-Live-usb
├─sdc2 crypto_LUKS
└─sdc3 vfat MX-UEFI
I don't know if it makes any difference but this laptop is about 2010-2011 vintage and has the old style BIOS.
Let's put the encrypted live USB messages on hold for now. We think we are getting close. For now, encrypted live USB's aren't working.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 12:06 am
by BitJam
The encrypt problem stems from the new contradictory defaults in Debian. "cryptsetup luksFormat" defaults to the new luks2 format while "cryptsetup open --type luks" defaults to the old luks1 format. This seems designed to fail. My Gentoo system sanely leaves luksFormat defaulting luks1 so I was not seeing the problem here. Oh well. The usual suspects: anticapitalista, dolphin_oracle, and fehlix provided a tremendous amount of help in tracking this down.
I plan to push modified versions of the live initrd and LUM tonight. I plan to also add a --force=luks2 option in LUM for people who want to experiment with it.
I also plan to write a test checklist so we can catch problems like this earlier. Checklist have improved airplane safety. I hope they will help us too.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 3:53 am
by JayM
JayM wrote: Thu Oct 17, 2019 1:53 am
1. Lucky Backup as superuser doesn't run after I enter the root password. If I run it in a terminal it says
Code: Select all
jay@mx19:~
$ /usr/bin/luckybackup-pkexec
qt.qpa.screen: QXcbConnection: Could not connect to display
Could not connect to any X display.
If I edit /usr/bin/luckybackup-pkexec as root and change
Code: Select all
#!/bin/sh
pkexec "/usr/bin/luckybackup" "$@"
to
Code: Select all
#!/bin/sh
mx-pkexec "/usr/bin/luckybackup" "$@"
it launches the GUI app. Just FYI.
Is anyone else unable to run System/luckyBackup (super user) or is it just me?
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 6:30 am
by gsm
Same problem with Lucky Backup.
When i edit the Lucky Backup (super user) item properties, at the System category in the Menu and change the command
from
to the value, as used in MX-18,
Code: Select all
su-to-root -X -c /usr/bin/luckybackup
then it launches the GUI app.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 7:03 am
by JayM
gksu also works. However, if the luckybackup-pkexec shell script is modified on the back end as it were perhaps it can be pushed out as an update which will fix it for everybody, vs. everyone running 19RC1 having to edit their Whisker menus.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 8:03 am
by dolphin_oracle
JayM wrote: Fri Oct 18, 2019 7:03 am
gksu also works. However, if the luckybackup-pkexec shell script is modified on the back end as it were perhaps it can be pushed out as an update which will fix it for everybody, vs. everyone running 19RC1 having to edit their Whisker menus.
Good stuff JayM.
I've asked the package guys to look at modifying the luckybackup package to address this.
Oh, FWIW, on MX 19, su-to-root and gksu will both actually use mx-pkexec.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 8:08 am
by JayM
Thanks, d_o. FYI the Whisker menu command line for lucky as superuser in MX-18 is
Code: Select all
su-to-root -X -c /usr/bin/luckybackup
just to save anyone the trouble of booting into 18 to check.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 8:57 am
by winemaker
Ok - just tried in on the thinkpad x 220 - office laptop and the wacom works in krita, gimp, and mypaint. touch sensitive too. should work on the older 201 downstairs. probably no need to try it. worked out of the box as the saying goes!
thanks to everyone. so far everything is really nice and yes elegant in 19!
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 8:59 am
by Jerry3904
Nice to hear about the wacom--thanks for the feedback.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 9:06 am
by winemaker
ya i decided to jump in afterall yesterday and do the install on both. need to finish some tweaks and some other stuff - testing. maybe do my wife's soon or leave 18 on there since she has not even tried 18 yet - she doesn't use the dell very often.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 11:30 am
by SkOrPn
So far so good with RC1,
However, the first real annoying issue I have come across is that Thunar in MX19 RC1 is NOT letting me select my ftp user on the Server. It allows me to simply go into my servers shared folders etc, but I do not have write permissions. On MX18.3 I would get a popup asking me for my user name and password. The server is a windows 2016 server OS and the ftp program installed on it is FileZilla ftp server. On MX18.3 I got the full gigabit speeds both ways usinf ftp, but on MX19 I am getting 11.2 MB/s, lol that sucks and its only read permissions. So I assume I have to sign in somehow? How do I force Thunar on MX19 to give me the user/password popup in order to properly access my server? Help please!
EDIT: OK, MX 19 RC1 was set to 100 Mbps Full duplex in the Network configuration app. I changed it to 1 Gb/s and did a test and its still running at 11.2 MB/s. Not sure if I have to reboot or not to get the full network speed.
Obviously not a hardware issue, but here is the quick info anyway.
EDIT: LOL, It was a hardware issue, had to reboot the network router. Go figure...
Code: Select all
System: Host: SkOrPn-PC Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=70a61f9a-2aac-4b10-92ee-c29deae87a28 ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASRock model: AB350 Pro4 serial: <filter>
UEFI: American Megatrends v: P5.80 date: 06/14/2019
Battery: Device-1: hidpp_battery_0 model: Logitech K800 serial: <filter>
charge: 70% (should be ignored) rechargeable: yes status: Full
Device-2: hidpp_battery_1 model: Logitech Performance MX serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU: Topology: 6-Core model: AMD Ryzen 5 2600X bits: 64 type: MT MCP arch: Zen+
family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86226
Speed: 1885 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 1885
2: 2041 3: 2192 4: 2192 5: 2134 6: 1900 7: 2188 8: 2192 9: 2048 10: 2081 11: 2114
12: 1927
Vulnerabilities: 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: disabled, RSB filling
Graphics: Device-1: AMD Hawaii PRO [Radeon R9 290/390] vendor: PC Partner Limited
driver: radeon v: kernel bus ID: 0a:00.0 chip ID: 1002:67b1
Display: x11 server: X.Org 1.20.4 driver: radeon resolution: 2560x1440~60Hz
OpenGL: renderer: AMD HAWAII (DRM 2.50.0 4.19.0-6-amd64 LLVM 7.0.1)
v: 4.5 Mesa 18.3.6 direct render: Yes
Audio: Device-1: AMD Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X]
vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: 0a:00.1
chip ID: 1002:aac8
Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel
bus ID: 0c:00.3 chip ID: 1022:1457
Device-3: Logitech G35 Headset type: USB driver: hid-generic,snd-usb-audio,usbhid
bus ID: 1-10.7.3:7 chip ID: 046d:0a15
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock
driver: r8169 v: kernel port: d000 bus ID: 09:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 625.97 GiB used: 242.61 GiB (38.8%)
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPW256HEGL-000H1 size: 238.47 GiB
block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter>
rev: CXZ73H0Q scheme: GPT
ID-2: /dev/sda vendor: Western Digital model: WD1600HLFS-75G6U1 size: 149.01 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 10000 rpm
serial: <filter> rev: 4V03 scheme: MBR
ID-3: /dev/sdb vendor: Samsung model: SSD 840 PRO Series size: 119.24 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 6B0Q scheme: MBR
ID-4: /dev/sdc vendor: Samsung model: SSD 840 PRO Series size: 119.24 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 6B0Q scheme: MBR
Partition: ID-1: / raw size: 90.33 GiB size: 88.41 GiB (97.88%) used: 17.04 GiB (19.3%) fs: ext4
dev: /dev/nvme0n1p5
Sensors: System Temperatures: cpu: 40.0 C mobo: N/A gpu: radeon temp: 46 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release-.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ buster main
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/google-earth-pro.list
1: deb http://dl.google.com/linux/earth/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb https://mega.nz/linux/MEGAsync/Debian_10.0/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb stable main
Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
1: deb http://linux.teamviewer.com/deb stable main
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 316 Uptime: 13h 16m Memory: 15.66 GiB used: 2.69 GiB (17.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
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 11:54 am
by fehlix
SkOrPn wrote: Fri Oct 18, 2019 11:30 am
How do I force Thunar on MX19 to give me the user/password popup in order to properly access my server?
I do use within Thunar
ftp://ftpusername@ftpserver
ftp-ftpuser-ftpserver.png
and get an authentication pup-up:
ftp-thunar-authenticate.png
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 12:16 pm
by SkOrPn
OK, thank you fehlix, but that didn't work either. I still did not get the popup, it just instantly threw me into my server folders with read only permissions. So my guess backing up and restoring my /home from 18.3 to 19 RC1 has helped me to break something. I can't even get it to run at full gigabit speeds, it keeps changing back to 100 Mbps, instead of the 1000 Mbps I was getting.
Dang, I was hoping that RC1 was good enough for daily driver use but I was not expecting to have to fix stuff. My bad...
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 12:31 pm
by winemaker
i would sya - give them a chance t come up with a fix or get you goinf. i had an issue which was debian related and they fixed it within a few hrs. and that wasn't even their ( the devs - fault.) i have been running these 2 laptops for almost 20 and 24 hrs respectively and all is well. i was helped with info for a tweak too - other than that - it is sweet. you also knew it was rc so that was your call. i was interested and then a bit reluctant and finally jumped in based on what i see with MX and the team here. they are working hard tweaking the final little things.
p.s. I am glad I did 19rc1
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 12:59 pm
by davemx
I can't get libpng12-0 to install.
Console output:
------------------------
Reading package lists...
Building dependency tree...
Reading state information...
The following package was automatically installed and is no longer required:
zlib1g:i386
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
libpng12-0
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/173 kB of archives.
After this operation, 294 kB of additional disk space will be used.
(Reading database ... 290297 files and directories currently installed.)
Preparing to unpack .../libpng12-0_1.2.50-2+deb8u3.1_amd64.deb ...
Unpacking libpng12-0:amd64 (1.2.50-2+deb8u3.1) ...
dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.50-2+deb8u3.1_amd64.deb (--unpack):
unable to install new version of '/usr/lib/x86_64-linux-gnu/libpng12.so.0': No such file or directory
Errors were encountered while processing:
/var/cache/apt/archives/libpng12-0_1.2.50-2+deb8u3.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
------------------------
I need it for SP_Flash_Tool, a program used to root Mediatek-based phones.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 1:03 pm
by SkOrPn
Woohoo, got er fixed already. It wasn't a MX 19 bug, it was apparently my network. I updated the Server, rebooted it and then ran over to my Asus router and power cycled it just in case. A few days back we had a 2 second power outage, so that made me suspect a issue with the network or server. Waited for the network to come online and tried Thunar again, and sure enough it gave me the user popup, I filled in the password and the files are transferring at full Gigabit speeds. That kinda stressed me out there, but I'm good now. Love that I didn't have to go messing around with settings, eth0 drivers or kernels.
On a side note, I can't wait for Ubuntu Server 20.04 LTS with ZFS. I'm going to dump this windows server like a bad habit for sure. Just got to find a Linux replacement for the incredibly wonderful StableBit DrivePool software I use on Windows Server. If I can do that Windows is GONE forever. Lol
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 1:05 pm
by winemaker
glad you got it working. debian for server. go to the source. instead of ubuntu. my thoughts.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 1:14 pm
by Jerry3904
#davemx: maybe try switching repos? Does it show in you run
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 1:33 pm
by davemx
root@localhost:/home/davemx# apt policy libpng
libpng:
Installed: (none)
Candidate: (none)
Version table:
I changed the MX-Linux source from an American to a British one. No change.
Is it not from the Debian repo? Can I change that?
I tried deleting the downloaded libpng12-0 from the cache just in case the one there was broken, so it would have to download again. No change.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 1:37 pm
by dolphin_oracle
where did you get libpng12-0? that package is not in the debian repo.
libpng16-16 is in buster.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 1:59 pm
by davemx
dolphin_oracle wrote: Fri Oct 18, 2019 1:37 pm
where did you get libpng12-0? that package is not in the debian repo.
libpng16-16 is in buster.
libpng12-0: It comes up in both MX Linux Package installer AND Synaptic. If it's not in Debian or MX I have no idea why or how.
libpng16-16 is installed. SP_Flash_Tool insists on libpng12. Maybe I can add a symlink to see if it can be fooled to use 16-16.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 2:04 pm
by dolphin_oracle
davemx wrote: Fri Oct 18, 2019 1:59 pm
dolphin_oracle wrote: Fri Oct 18, 2019 1:37 pm
where did you get libpng12-0? that package is not in the debian repo.
libpng16-16 is in buster.
libpng12-0: It comes up in both MX Linux Package installer AND Synaptic. If it's not in Debian or MX I have no idea why or how.
libpng16-16 is installed. SP_Flash_Tool insists on libpng12. Maybe I can add a symlink to see if it can be fooled to use 16-16.
maybe I'm missing it.
quick-system-info?
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 2:06 pm
by fehlix
davemx wrote: Fri Oct 18, 2019 1:59 pm
dolphin_oracle wrote: Fri Oct 18, 2019 1:37 pm
where did you get libpng12-0? that package is not in the debian repo.
libpng16-16 is in buster.
libpng12-0: It comes up in both MX Linux Package installer AND Synaptic. If it's not in Debian or MX I have no idea why or how.
Perhaps show you're activated repo's. Someone might have added a stretch repo?
EDIT:
Check where you got it from with:
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 2:06 pm
by Jerry3904
libpng-dev is in buster
Code: Select all
[jb@mx]$ apt policy libpng-dev
libpng-dev:
Installed: (none)
Candidate: 1.6.36-6
Version table:
1.6.36-6 500
500 http://deb.debian.org/debian buster/main amd64 Packages
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 2:10 pm
by kmathern
The libpng12-0 package is from the antix/buster repo
Code: Select all
$ apt-cache policy libpng12-0
libpng12-0:
Installed: (none)
Candidate: 1.2.50-2+deb8u3.1
Version table:
1.2.50-2+deb8u3.1 500
500 http://iso.mxrepo.com/antix/buster buster/main amd64 Packages
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 3:06 pm
by Stevo
asqwerth wrote: Thu Oct 17, 2019 6:46 pm
dreamer wrote: Thu Oct 17, 2019 3:21 pm...
That's good and time-saving info. Is it possible to preserve /home in the installer if /home is located on the root partition?
It should from past experience. I haven't had time to install MX19 rc yet.
It has worked for me in the past no matter where it's located, including the last RC1 in VBox. It saves me having to make all the HDPI scaling adjustments needed with a HDPI screen, plus I have all the xfce4-hardware-monitor widgets still going in the panel, since we ship that now with MX 19.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 3:29 pm
by winemaker
ok tough typing with arthritis - but here is some info. installed the rc1 on a thinpad x series 201 first and then an x seires 220 for my office. so far all is superb. i installed the hplip in the mx package area and both print wireles 8600 hp multiprinter. i seem to have 2 - because i am used to having to add the printer but it prints no issues. maybe i will delete the 2nd and see what happens. there is pdf there too that was checked but the first 8600 is highlighted. not sure that the pdf thing is about. I never saw that beofre.
the wireless. both work. i do not recalle which one did what looking back to yesterday waking at 4 am as i do. but i ran them both live to check out wireless and a few others. the 220 the 2nd install not so much checking but they both were hooked up prior to install foir wireless. i noticed that on live mode both just needed paswword and all was good. i remember notcing - and this is the fuzzy one - whcih one did what. but when i installed rc1 on both of them and then tried to connect. one was easy and similar to live mode and the other was a bit of a bear - i ended up having to add a wifi network even though it found it and then had to go in and do the password stuff and the anomaly i found strange and inconsistent but hey - it worked. and they both have since yesterday. though the 201 is my daily downstairs and daily work laptop. the faster 220 with more ram and ssd thoug less gb's is my office laptop.
wacom tablets work using gimp, krita, and mypaint. and the scroll bar on the top left of the wacom tablet scrolled too too. no noy tutu - he he a little humor.
the suspend and lock works and when resuming the login does show up unlike in 18.3 where you get the black screen and need to either just type the password which brings up login screen or touch the trackpad or mouse cursor move to bring up login screen so that is a major fix in 19.
not sure what else i was going to comment on but damn nice distro and release.
thanks to evryone on the team
anyway... those are my observations. sorry for typos.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 3:41 pm
by Stevo
A patched Lucky Backup is done and should be seen as an upgrade in the main repos pretty soon.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 4:39 pm
by davemx
kmathern wrote: Fri Oct 18, 2019 2:10 pm
The libpng12-0 package is from the antix/buster repo
Code: Select all
$ apt-cache policy libpng12-0
libpng12-0:
Installed: (none)
Candidate: 1.2.50-2+deb8u3.1
Version table:
1.2.50-2+deb8u3.1 500
500 http://iso.mxrepo.com/antix/buster buster/main amd64 Packages
Sorry, been away from the computer — this is correct. Since I only installed the RC today, and haven't messed about with repositories at all, if it shouldn't be there, why is it?
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 8:01 pm
by BV206
MX Repo Manager
Individual sources tab
the bottom list is sources.list and it has a check box but no text next to the check box. The others have a deb http:// line.
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 8:13 pm
by anticapitalista
davemx wrote: Fri Oct 18, 2019 4:39 pm
kmathern wrote: Fri Oct 18, 2019 2:10 pm
The libpng12-0 package is from the antix/buster repo
Code: Select all
$ apt-cache policy libpng12-0
libpng12-0:
Installed: (none)
Candidate: 1.2.50-2+deb8u3.1
Version table:
1.2.50-2+deb8u3.1 500
500 http://iso.mxrepo.com/antix/buster buster/main amd64 Packages
Sorry, been away from the computer — this is correct. Since I only installed the RC today, and haven't messed about with repositories at all, if it shouldn't be there, why is it?
Does it cause you problems if it is there?
Does it help you that it is there?
Re: MX-19 RC1 Feedback thread
Posted: Fri Oct 18, 2019 10:00 pm
by Adrian
BV206 wrote: Fri Oct 18, 2019 8:01 pm
MX Repo Manager
Individual sources tab
the bottom list is sources.list and it has a check box but no text next to the check box. The others have a deb http:// line.
Thanks, I will take a look to see how I can fix this.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 1:32 am
by scatman98
congrats on the RC1
issue i have is the Monitor on desktop goes blank or freezes, needs a restart.
it is an AMD system with nvidia GPU. using 4.9.`93 kernel, mainly because 4.19.0.6 doesnt work with iridium browser.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 4:04 am
by asqwerth
dolphin_oracle wrote: Fri Oct 18, 2019 8:03 am
...I've asked the package guys to look at modifying the luckybackup package to address this.
Oh, FWIW, on MX 19, su-to-root and gksu will both actually use mx-pkexec.
Stevo wrote: Fri Oct 18, 2019 3:41 pm
A patched Lucky Backup is done and should be seen as an upgrade in the main repos pretty soon.
Dolphin, with the patched lucky backup, the icon (for both user and root lucky backup) has reverted back to the old xpm ones because of the hard coding of the icon filepath in the .desktop file.
Instead of:
Code: Select all
Icon=/usr/share/pixmaps/luckybackup.png
It should read:
so that it can apply the icon in Papirus.
Is this program still being maintained by a dev who can take bug reports?
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 4:09 am
by Eadwine Rose
scatman98 wrote: Sat Oct 19, 2019 1:32 am
congrats on the RC1
issue i have is the Monitor on desktop goes blank or freezes, needs a restart.
it is an AMD system with nvidia GPU. using 4.9.`93 kernel, mainly because 4.19.0.6 doesnt work with iridium browser.
Can you post the output of quick system info in MX Tools please? That way we will have more info to work with.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 4:50 am
by scatman98
Eadwine Rose wrote: Sat Oct 19, 2019 4:09 am
scatman98 wrote: Sat Oct 19, 2019 1:32 am
congrats on the RC1
issue i have is the Monitor on desktop goes blank or freezes, needs a restart.
it is an AMD system with nvidia GPU. using 4.9.`93 kernel, mainly because 4.19.0.6 doesnt work with iridium browser.
Can you post the output of quick system info in MX Tools please? That way we will have more info to work with.
sure this is the output.
Code: Select all
System: Host: mx Kernel: 4.20.12-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.20.12-antix.1-amd64-smp
root=UUID=7c8193ed-a2c8-4e5e-8e13-8c95f1c3d31a ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: Gigabyte product: B450 AORUS PRO WIFI v: N/A serial: <filter>
Mobo: Gigabyte model: B450 AORUS PRO WIFI-CF serial: <filter>
UEFI [Legacy]: American Megatrends v: F42c date: 09/12/2019
CPU: Topology: 6-Core model: AMD Ryzen 5 1600 bits: 64 type: MT MCP arch: Zen
family: 17 (23) model-id: 1 stepping: 1 microcode: 8001138 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 76648
Speed: 1374 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1375
2: 1373 3: 1374 4: 1375 5: 1375 6: 1375 7: 1375 8: 1375 9: 1381 10: 1375 11: 1375
12: 1371
Vulnerabilities: Type: l1tf 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: __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Graphics: Device-1: NVIDIA GF114 [GeForce GTX 560] vendor: ZOTAC driver: nvidia v: 390.116
bus ID: 07:00.0 chip ID: 10de:1201
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
resolution: 1680x1050~60Hz, 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 560/PCIe/SSE2 v: 4.6.0 NVIDIA 390.116
direct render: Yes
Audio: Device-1: NVIDIA GF114 HDMI Audio vendor: ZOTAC driver: snd_hda_intel v: kernel
bus ID: 07:00.1 chip ID: 10de:0e0c
Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 09:00.3 chip ID: 1022:1457
Sound Server: ALSA v: k4.20.12-antix.1-amd64-smp
Network: Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: 5.4.0-k
port: f000 bus ID: 04:00.0 chip ID: 8086:1539
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel
port: f000 bus ID: 05:00.0 chip ID: 8086:24fb
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 2.40 TiB used: 682.44 GiB (27.8%)
ID-1: /dev/nvme0n1 model: HS-SSD-C2000 size: 476.94 GiB block size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: ECFM12.1 scheme: MBR
ID-2: /dev/sda vendor: Seagate model: ST2000DM006-2DM164 size: 1.82 TiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: CC26 scheme: MBR
ID-3: /dev/sdb vendor: Samsung model: SSD 850 PRO 128GB size: 119.24 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 4B6Q scheme: MBR
Partition: ID-1: / raw size: 45.99 GiB size: 45.01 GiB (97.89%) used: 7.78 GiB (17.3%) fs: ext4
dev: /dev/nvme0n1p6
ID-2: swap-1 size: 2.73 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/nvme0n1p5
Sensors: System Temperatures: cpu: 48.2 C mobo: N/A gpu: nvidia temp: 47 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 29%
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb https://mirrors.evowise.com/mxlinux-packages/antix//buster buster main
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/iridium-browser.list
1: deb [arch=amd64] https://downloads.iridiumbrowser.de/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirrors.evowise.com/mxlinux-packages/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 320 Uptime: 18m Memory: 23.55 GiB used: 1.78 GiB (7.6%) 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
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 6:41 am
by dolphin_oracle
asqwerth wrote: Sat Oct 19, 2019 4:04 am
dolphin_oracle wrote: Fri Oct 18, 2019 8:03 am
...I've asked the package guys to look at modifying the luckybackup package to address this.
Oh, FWIW, on MX 19, su-to-root and gksu will both actually use mx-pkexec.
Stevo wrote: Fri Oct 18, 2019 3:41 pm
A patched Lucky Backup is done and should be seen as an upgrade in the main repos pretty soon.
Dolphin, with the patched lucky backup, the icon (for both user and root lucky backup) has reverted back to the old xpm ones because of the hard coding of the icon filepath in the .desktop file.
Instead of:
Code: Select all
Icon=/usr/share/pixmaps/luckybackup.png
It should read:
so that it can apply the icon in Papirus.
Is this program still being maintained by a dev who can take bug reports?
I don't know about maintaining, but we are hosting the package our selves. also, it should be luckybackup (all lowercase) as the papirus guys are different from all the other themes. the icon override we placed in the desktop file points to "luckybackup"
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 7:02 am
by JayM
scatman98 wrote: Sat Oct 19, 2019 1:32 am
congrats on the RC1
issue i have is the Monitor on desktop goes blank or freezes, needs a restart.
it is an AMD system with nvidia GPU. using 4.9.`93 kernel, mainly because 4.19.0.6 doesnt work with iridium browser.
Please run MX Tools / Quick System Info, then right-click and paste in a response. (Quick System Info automatically copies the information to your clipboard, already formatted correctly to be pasted in the forum, so just right click / paste and not copy / paste.) Thank you.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 8:10 am
by richb
Received an error creating a snapshot. I left all options default choosing a personal snapshot.
Code: Select all
File /.bind-root/home/richb/.config/xfce4/desktop/icons.screen0-1904x974.rc changed size while reading filesystem, attempting to re-readParallel mksquashfs: Using 4 processors
Creating 4.0 filesystem on iso-template/antiX/linuxfs, block size 131072.
[=========================================================/] 376202/376202 100%
Exportable Squashfs 4.0 filesystem, lz4 compressed, data block size 131072
compressed data, compressed metadata, compressed fragments, compressed xattrs
duplicates are removed
Filesystem size 5923802.20 Kbytes (5784.96 Mbytes)
53.61% of uncompressed filesystem size (11049685.40 Kbytes)
Inode table size 6462334 bytes (6310.87 Kbytes)
41.10% of uncompressed inode table size (15724253 bytes)
Directory table size 6723043 bytes (6565.47 Kbytes)
57.66% of uncompressed directory table size (11659719 bytes)
Xattr table size 72 bytes (0.07 Kbytes)
36.00% of uncompressed xattr table size (200 bytes)
Number of duplicate files found 26657
Number of inodes 438278
Number of files 318590
Number of fragments 21121
Number of symbolic links 95315
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 27
Number of directories 24346
Number of ids (unique uids + gids) 36
Number of uids 12
root (0)
lp (7)
mpd (120)
richb (1000)
_apt (100)
man (6)
mpdscribble (119)
colord (114)
lightdm (118)
statd (109)
ntp (105)
nm-openvpn (112)
Number of gids 29
root (0)
dip (30)
lp (7)
mpdscribble (129)
shadow (42)
nm-openvpn (120)
audio (29)
ssl-cert (110)
dialout (20)
richb (1000)
piavpn (1002)
tty (5)
crontab (108)
mail (8)
mlocate (115)
plugdev (46)
ssh (116)
games (60)
messagebus (113)
nogroup (65534)
utmp (43)
staff (50)
lpadmin (111)
man (12)
colord (121)
lightdm (128)
ntp (112)
sambashare (127)
adm (4)
xorriso 1.5.0 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:/home/snapshot/snapshot-20191019_0759.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 197g free
Added to ISO image: directory '/'='/tmp/mx-snapshot-y2hbE1Aw/iso-template'
xorriso : UPDATE : 935 files added in 1 seconds
Added to ISO image: directory '/'='/tmp/mx-snapshot-y2hbE1Aw/iso-2'
xorriso : FAILURE : Cannot find in ISO image: -boot_image ... bin_path='/boot/isolinux/isolinux.bin'
xorriso : UPDATE : 938 files added in 1 seconds
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
Code: Select all
System: Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=7a483f38-4278-4c7b-aba1-e43056401462 ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> Chassis: type: 3
serial: <filter>
Mobo: Gigabyte model: F2A68HM-H v: x.x serial: <filter> UEFI: American Megatrends
v: FB date: 04/22/2015
Battery: Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard serial: <filter>
charge: 10% (should be ignored) rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M325 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU: Topology: Quad Core model: AMD A8-7600 Radeon R7 10 Compute Cores 4C+6G bits: 64
type: MCP arch: Steamroller family: 15 (21) model-id: 30 (48) stepping: 1
microcode: 6003106 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 24755
Speed: 1415 MHz min/max: 1400/3100 MHz boost: enabled Core speeds (MHz): 1: 1645
2: 1838 3: 1409 4: 1399
Vulnerabilities: 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
Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: Gigabyte driver: radeon v: kernel
bus ID: 00:01.0 chip ID: 1002:1313
Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: AMD KAVERI (DRM 2.50.0 4.19.0-6-amd64 LLVM 7.0.1)
v: 4.5 Mesa 18.3.6 direct render: Yes
Audio: Device-1: AMD Kaveri HDMI/DP Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 00:01.1 chip ID: 1002:1308
Device-2: AMD FCH Azalia vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Device-3: Logitech Webcam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo
bus ID: 2-2:2 chip ID: 046d:0809 serial: <filter>
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
driver: r8169 v: kernel port: e000 bus ID: 01:00.0 chip ID: 10ec:8168
IF: eth0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k v: kernel
port: e000 bus ID: 02:00.0 chip ID: 168c:0030
IF: wlan0 state: up mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives: Local Storage: total: 755.94 GiB used: 104.77 GiB (13.9%)
ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT
ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT
ID-3: /dev/sdc vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: MBR
ID-4: /dev/sdd type: USB vendor: SanDisk model: Ultra size: 57.28 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 1.00 scheme: MBR
Partition: ID-1: / raw size: 230.60 GiB size: 225.99 GiB (98.00%) used: 11.84 GiB (5.2%)
fs: ext4 dev: /dev/sda2
ID-2: swap-1 size: 2.00 GiB used: 6.0 MiB (0.3%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda3
Sensors: System Temperatures: cpu: 8.4 C mobo: N/A gpu: radeon temp: 9 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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/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://mxrepo.com/mx/repo/ buster main non-free
Active apt repos in: /etc/apt/sources.list.d/slack.list
1: deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 257 Uptime: 2h 41m Memory: 14.63 GiB used: 2.61 GiB (17.8%) 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
Code: Select all
2019-10-19 07:59:36.499 DBG default: mx-snapshot version: 19.10.01
2019-10-19 07:59:36.562 DBG default: mountpoint -q /live/aufs
2019-10-19 07:59:36.571 DBG default: lslogins --noheadings -u -o user | grep -vw root
2019-10-19 07:59:36.579 DBG default: "richb"
2019-10-19 07:59:36.579 DBG default: uname -m
2019-10-19 07:59:36.584 DBG default: "x86_64"
2019-10-19 07:59:36.584 DBG default: cat /etc/debian_version | cut -f1 -d'.'
2019-10-19 07:59:36.590 DBG default: "10"
2019-10-19 07:59:36.591 DBG default: +++ void MainWindow::setup() +++
2019-10-19 07:59:36.788 DBG default: +++ void MainWindow::loadSettings() +++
2019-10-19 07:59:36.788 DBG default: +++ QString MainWindow::getFilename() +++
2019-10-19 07:59:36.788 DBG default: date +%Y%m%d_%H%M
2019-10-19 07:59:36.888 DBG default: "20191019_0759"
2019-10-19 07:59:36.909 DBG default: +++ void MainWindow::listFreeSpace() +++
2019-10-19 07:59:36.909 DBG default: df -h "/home" | awk 'NR==2 {print $4}'
2019-10-19 07:59:36.920 DBG default: "203G"
2019-10-19 07:59:36.920 DBG default: +++ QString MainWindow::getSnapshotSize() +++
2019-10-19 07:59:36.921 DBG default: +++ int MainWindow::getSnapshotCount() +++
2019-10-19 07:59:36.921 DBG default: df -h / | awk 'NR==2 {print $3}'
2019-10-19 07:59:36.954 DBG default: "12G"
2019-10-19 07:59:36.954 DBG default: mountpoint -q /home
2019-10-19 08:00:10.884 DBG default: uname -r
2019-10-19 08:00:10.915 DBG default: "4.19.0-6-amd64"
2019-10-19 08:00:15.103 DBG default: [ -f /boot/config-$(uname -r) ]
2019-10-19 08:00:15.113 DBG default: grep ^CONFIG_SQUASHFS_LZ4=y /boot/config-$(uname -r)
2019-10-19 08:00:15.122 DBG default: "CONFIG_SQUASHFS_LZ4=y"
2019-10-19 08:00:17.095 DBG default: +++ void MainWindow::checkDirectories() +++
2019-10-19 08:00:17.099 DBG default: +++ bool MainWindow::isOnSupportedPart(QDir) +++
2019-10-19 08:00:17.099 DBG default: stat --file-system --format=%T /home/snapshot
2019-10-19 08:00:17.113 DBG default: "ext2/ext3"
2019-10-19 08:00:17.113 DBG default: detected partition "ext2/ext3" supported part: true
2019-10-19 08:00:17.113 DBG default: +++ QString MainWindow::largerFreeSpace(QString, QString, QString) +++
2019-10-19 08:00:17.113 DBG default: +++ QString MainWindow::largerFreeSpace(QString, QString) +++
2019-10-19 08:00:17.113 DBG default: df -k --output=avail /tmp 2>/dev/null | tail -n1
2019-10-19 08:00:17.121 DBG default: "212451164"
2019-10-19 08:00:17.122 DBG default: df -k --output=avail /home 2>/dev/null | tail -n1
2019-10-19 08:00:17.129 DBG default: "212451164"
2019-10-19 08:00:17.130 DBG default: +++ QString MainWindow::largerFreeSpace(QString, QString) +++
2019-10-19 08:00:17.130 DBG default: df -k --output=avail /tmp 2>/dev/null | tail -n1
2019-10-19 08:00:17.137 DBG default: "212451164"
2019-10-19 08:00:17.137 DBG default: df -k --output=avail /home/snapshot 2>/dev/null | tail -n1
2019-10-19 08:00:17.145 DBG default: "212451164"
2019-10-19 08:00:17.146 DBG default: mktemp -d "/tmp/mx-snapshot-XXXXXXXX"
2019-10-19 08:00:17.152 DBG default: "/tmp/mx-snapshot-y2hbE1Aw"
2019-10-19 08:00:17.165 DBG default: +++ void MainWindow::copyNewIso() +++
2019-10-19 08:00:17.173 DBG default: tar xf /usr/lib/iso-template/iso-template.tar.gz
2019-10-19 08:00:17.458 DBG default: cp /usr/lib/iso-template/template-initrd.gz iso-template/antiX/initrd.gz
2019-10-19 08:00:17.468 DBG default: cp /boot/vmlinuz-4.19.0-6-amd64 iso-template/antiX/vmlinuz
2019-10-19 08:00:17.485 DBG default: +++ void MainWindow::replaceMenuStrings() +++
2019-10-19 08:00:17.485 DBG default: date +'%d %B %Y'
2019-10-19 08:00:17.492 DBG default: "19 October 2019"
2019-10-19 08:00:17.492 DBG default: cat /etc/antix-version | cut -f1 -d'_'
2019-10-19 08:00:17.500 DBG default: "MX-19RC1"
2019-10-19 08:00:17.500 DBG default: grep -oP '(?<=DISTRIB_ID=).*' /etc/lsb-release
2019-10-19 08:00:17.509 DBG default: "MX"
2019-10-19 08:00:17.509 DBG default: cat /etc/antix-version | cut -f-2 -d' '
2019-10-19 08:00:17.516 DBG default: "MX-19RC1_x64 patito"
2019-10-19 08:00:17.517 DBG default: grep -oP '(?<=DISTRIB_CODENAME=).*' /etc/lsb-release
2019-10-19 08:00:17.524 DBG default: "\"patito feo\""
2019-10-19 08:00:17.524 DBG default: sed -i 's/%DISTRO_NAME%/MX/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg"
2019-10-19 08:00:17.531 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg: No such file or directory"
2019-10-19 08:00:17.531 DBG default: sed -i 's/%OPTIONS%/quiet/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/syslinux.cfg"
2019-10-19 08:00:17.538 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/syslinux.cfg: No such file or directory"
2019-10-19 08:00:17.538 DBG default: sed -i 's/%OPTIONS%/quiet/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/isolinux.cfg"
2019-10-19 08:00:17.546 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/isolinux.cfg: No such file or directory"
2019-10-19 08:00:17.546 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg"
2019-10-19 08:00:17.553 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg: No such file or directory"
2019-10-19 08:00:17.554 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/syslinux.cfg"
2019-10-19 08:00:17.561 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/syslinux.cfg: No such file or directory"
2019-10-19 08:00:17.561 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/readme.msg"
2019-10-19 08:00:17.569 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/readme.msg: No such file or directory"
2019-10-19 08:00:17.570 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/isolinux.cfg"
2019-10-19 08:00:17.577 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/isolinux.cfg: No such file or directory"
2019-10-19 08:00:17.577 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/readme.msg"
2019-10-19 08:00:17.585 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/readme.msg: No such file or directory"
2019-10-19 08:00:17.585 DBG default: sed -i 's/%DISTRO%/MX-19RC1/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/theme/theme.txt"
2019-10-19 08:00:17.592 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/theme/theme.txt: No such file or directory"
2019-10-19 08:00:17.592 DBG default: sed -i 's/%DISTRO%/MX-19RC1/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg"
2019-10-19 08:00:17.600 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg: No such file or directory"
2019-10-19 08:00:17.600 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg"
2019-10-19 08:00:17.607 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg: No such file or directory"
2019-10-19 08:00:17.607 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/syslinux.cfg"
2019-10-19 08:00:17.616 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/syslinux.cfg: No such file or directory"
2019-10-19 08:00:17.617 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/readme.msg"
2019-10-19 08:00:17.624 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/readme.msg: No such file or directory"
2019-10-19 08:00:17.624 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/isolinux.cfg"
2019-10-19 08:00:17.631 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/isolinux.cfg: No such file or directory"
2019-10-19 08:00:17.631 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/readme.msg"
2019-10-19 08:00:17.640 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/readme.msg: No such file or directory"
2019-10-19 08:00:17.640 DBG default: sed -i 's/%CODE_NAME%/"patito feo"/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/syslinux.cfg"
2019-10-19 08:00:17.647 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/syslinux/syslinux.cfg: No such file or directory"
2019-10-19 08:00:17.647 DBG default: sed -i 's/%CODE_NAME%/"patito feo"/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/isolinux.cfg"
2019-10-19 08:00:17.655 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/isolinux/isolinux.cfg: No such file or directory"
2019-10-19 08:00:17.656 DBG default: sed -i 's/%ASCII_CODE_NAME%/"patito feo"/g' "/tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/theme/theme.txt"
2019-10-19 08:00:17.663 WRN default: "sed: can't read /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/theme/theme.txt: No such file or directory"
2019-10-19 08:00:17.663 DBG default: /usr/share/mx-packageinstaller/scripts/make-efi-img /tmp/mx-snapshot-y2hbE1Aw/iso-template/
2019-10-19 08:00:17.671 WRN default: "Missing file /tmp/mx-snapshot-y2hbE1Aw/iso-template/EFI/BOOT/BOOTx64.EFI\nMissing file /tmp/mx-snapshot-y2hbE1Aw/iso-template/EFI/BOOT/bootx64.efi"
2019-10-19 08:00:17.676 WRN default: "Missing file /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/grub/grub.cfg\nMissing file /tmp/mx-snapshot-y2hbE1Aw/iso-template/EFI/BOOT/fallback.efi"
2019-10-19 08:00:17.676 DBG default: "Kilobytes needed: 1120"
2019-10-19 08:00:17.676 WRN default: "Missing file /tmp/mx-snapshot-y2hbE1Aw/iso-template/EFI/BOOT/mt86.png\nMissing file /tmp/mx-snapshot-y2hbE1Aw/iso-template/boot/uefi-mt/mtest-64.efi"
2019-10-19 08:00:17.678 DBG default: "Try size: 1150 margin: 30"
2019-10-19 08:00:17.753 WRN default: "umount: /tmp/make-efi-img/mp: not mounted."
2019-10-19 08:00:17.822 DBG default: "Final size: 1160 margin: 40"
2019-10-19 08:00:17.831 WRN default: "umount: /tmp/make-efi-img/mp: not mounted."
2019-10-19 08:00:17.833 WRN default: "rmdir: failed to remove '/tmp/make-efi-img/mp': Directory not empty"
2019-10-19 08:00:17.834 WRN default: "rmdir: failed to remove '/tmp/make-efi-img': Directory not empty"
2019-10-19 08:00:17.835 DBG default: "make-efi-img created boot/grub/efi.img"
2019-10-19 08:00:17.835 DBG default: +++ void MainWindow::makeMd5sum(QString, QString) +++
2019-10-19 08:00:17.835 DBG default: sync
2019-10-19 08:00:17.854 DBG default: md5sum "vmlinuz">"/tmp/mx-snapshot-y2hbE1Aw/iso-template/antiX/vmlinuz.md5"
2019-10-19 08:00:17.877 DBG default: mktemp -d
2019-10-19 08:00:17.885 DBG default: "/tmp/tmp.2n9Y9cGehV"
2019-10-19 08:00:17.885 DBG default: +++ void MainWindow::openInitrd(QString, QString) +++
2019-10-19 08:00:17.885 DBG default: chmod a+rx "/tmp/tmp.2n9Y9cGehV"
2019-10-19 08:00:17.891 DBG default: gunzip -c "/tmp/mx-snapshot-y2hbE1Aw/iso-template/antiX/initrd.gz" | cpio -idum
2019-10-19 08:00:17.958 WRN default: "7177 blocks"
2019-10-19 08:00:17.959 DBG default: test -d "/tmp/tmp.2n9Y9cGehV/lib/modules" && rm -r "/tmp/tmp.2n9Y9cGehV/lib/modules"
2019-10-19 08:00:17.965 DBG default: test -r /usr/local/share/live-files/files/etc/initrd-release && cp /usr/local/share/live-files/files/etc/initrd-release "/tmp/tmp.2n9Y9cGehV/etc"
2019-10-19 08:00:17.973 DBG default: test -r /etc/initrd-release && cp /etc/initrd-release "/tmp/tmp.2n9Y9cGehV/etc"
2019-10-19 08:00:17.980 DBG default: /usr/share/mx-packageinstaller/scripts/copy-initrd-modules -t="/tmp/tmp.2n9Y9cGehV" -k="4.19.0-6-amd64"
2019-10-19 08:00:18.025 WRN default: "modprobe: WARNING: Module aufs not found in directory /lib/modules/4.19.0-6-amd64\nmodprobe: WARNING: Module block not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.026 WRN default: "modprobe: WARNING: Module fotg210-hcd not found in directory /lib/modules/4.19.0-6-amd64\nmodprobe: WARNING: Module fusbh200-hcd not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.026 WRN default: "modprobe: WARNING: Module hid-lenovo-tpkbd not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.026 WRN default: "modprobe: WARNING: Module hyperv not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.026 WRN default: "modprobe: WARNING: Module jbd not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.026 WRN default: "modprobe: WARNING: Module ntfs not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.027 WRN default: "modprobe: WARNING: Module pcie-aspm not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.027 WRN default: "modprobe: WARNING: Module printk not found in directory /lib/modules/4.19.0-6-amd64\nmodprobe: WARNING: Module rts5139 not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.027 WRN default: "modprobe: WARNING: Module shpchp not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 08:00:18.985 DBG default: /usr/share/mx-packageinstaller/scripts/copy-initrd-programs --to="/tmp/tmp.2n9Y9cGehV"
2019-10-19 08:00:19.001 DBG default: "add program: ntfs-3g"
2019-10-19 08:00:19.108 DBG default: "ld_linux: /lib64/ld-linux-x86-64.so.2"
2019-10-19 08:00:19.112 DBG default: "ld_dir: /tmp/tmp.2n9Y9cGehV/lib/x86_64-linux-gnu"
2019-10-19 08:00:19.137 DBG default: "add program: eject"
2019-10-19 08:00:19.181 DBG default: "ld_linux: /lib64/ld-linux-x86-64.so.2"
2019-10-19 08:00:19.184 DBG default: "ld_dir: /tmp/tmp.2n9Y9cGehV/lib/x86_64-linux-gnu"
2019-10-19 08:00:19.200 DBG default: +++ void MainWindow::closeInitrd(QString, QString) +++
2019-10-19 08:00:19.200 DBG default: (find . | cpio -o -H newc --owner root:root | gzip -9) >"/tmp/mx-snapshot-y2hbE1Aw/iso-template/antiX/initrd.gz"
2019-10-19 08:00:29.871 WRN default: "55706 blocks"
2019-10-19 08:00:29.896 DBG default: rm -r /tmp/tmp.2n9Y9cGehV
2019-10-19 08:00:29.943 DBG default: +++ void MainWindow::makeMd5sum(QString, QString) +++
2019-10-19 08:00:29.943 DBG default: sync
2019-10-19 08:00:29.949 WRN default: "shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory"
2019-10-19 08:00:29.958 DBG default: md5sum "initrd.gz">"/tmp/mx-snapshot-y2hbE1Aw/iso-template/antiX/initrd.gz.md5"
2019-10-19 08:00:29.987 DBG default: +++ void MainWindow::mkDir(QString) +++
2019-10-19 08:00:29.987 DBG default: +++ void MainWindow::savePackageList(QString) +++
2019-10-19 08:00:29.987 DBG default: dpkg -l | grep ^ii\ \ | awk '{print $2,$3}' | sed 's/:'$(dpkg --print-architecture)'//' | column -t >"/tmp/mx-snapshot-y2hbE1Aw/iso-template/snapshot-20191019_0759/package_list"
2019-10-19 08:00:30.088 DBG default: +++ void MainWindow::setupEnv() +++
2019-10-19 08:00:30.089 DBG default: mountpoint /boot
2019-10-19 08:00:30.097 DBG default: "/boot is not a mountpoint"
2019-10-19 08:00:30.098 DBG default: +++ bool MainWindow::checkInstalled(QString) +++
2019-10-19 08:00:30.098 DBG default: dpkg -s mx-installer | grep Status
2019-10-19 08:00:30.164 DBG default: "Status: install ok installed"
2019-10-19 08:00:30.165 DBG default: echo /home/*/Desktop | xargs -n1 cp /usr/share/applications/minstall.desktop 2>/dev/null
2019-10-19 08:00:30.176 DBG default: chmod +x /home/*/Desktop/minstall.desktop
2019-10-19 08:00:30.182 DBG default: installed-to-live -b /.bind-root start bind=/home live-files version-file adjtime read-only
2019-10-19 08:00:30.924 DBG default: +++ bool MainWindow::createIso(QString) +++
2019-10-19 08:00:30.924 DBG default: +++ void MainWindow::addRemoveExclusion(bool, QString) +++
2019-10-19 08:00:30.924 DBG default: +++ void MainWindow::addRemoveExclusion(bool, QString) +++
2019-10-19 08:00:30.924 DBG default: mksquashfs /.bind-root iso-template/antiX/linuxfs -comp lz4 -wildcards -ef /usr/local/share/excludes/mx-snapshot-exclude.list -e "home/snapshot" "tmp/mx-snapshot-y2hbE1Aw"
2019-10-19 08:00:46.607 WRN default: "File /.bind-root/home/richb/.config/xfce4/desktop/icons.screen0-1904x974.rc changed size while reading filesystem, attempting to re-read"
2019-10-19 08:00:51.192 DBG default: "Parallel mksquashfs: Using 4 processors\nCreating 4.0 filesystem on iso-template/antiX/linuxfs, block size 131072.\n\r[==========/ ] 66900/376202 17%"
2019-10-19 08:01:25.203 DBG default: "[====================================/ ] 238500/376202 63%"
2019-10-19 08:01:37.457 DBG default: "[===============================================- ] 311800/376202 82%"
2019-10-19 08:01:47.305 DBG default: "[=========================================================/] 376202/376202 100%"
2019-10-19 08:01:47.430 DBG default: "Exportable Squashfs 4.0 filesystem, lz4 compressed, data block size 131072\n\tcompressed data, compressed metadata, compressed fragments, compressed xattrs\n\tduplicates are removed\nFilesystem size 5923802.20 Kbytes (5784.96 Mbytes)\n\t53.61% of uncompressed filesystem size (11049685.40 Kbytes)\nInode table size 6462334 bytes (6310.87 Kbytes)\n\t41.10% of uncompressed inode table size (15724253 bytes)\nDirectory table size 6723043 bytes (6565.47 Kbytes)\n\t57.66% of uncompressed directory table size (11659719 bytes)\nXattr table size 72 bytes (0.07 Kbytes)\n\t36.00% of uncompressed xattr table size (200 bytes)\nNumber of duplicate files found 26657\nNumber of inodes 438278\nNumber of files 318590\nNumber of fragments 21121\nNumber of symbolic links 95315\nNumber of device nodes 0\nNumber of fifo nodes 0\nNumber of socket nodes 27\nNumber of directories 24346\nNumber of ids (unique uids + gids) 36\nNumber of uids 12\n\troot (0)\n\tlp (7)\n\tmpd (120)\n\trichb (1000)\n\t_apt (100)\n\tman (6)\n\tmpdscribble (119)\n\tcolord (114)\n\tlightdm (118)\n\tstatd (109)\n\tntp (105)\n\tnm-openvpn (112)\nNumber of gids 29\n\troot (0)\n\tdip (30)\n\tlp (7)\n\tmpdscribble (129)\n\tshadow (42)\n\tnm-openvpn (120)\n\taudio (29)\n\tssl-cert (110)\n\tdialout (20)\n\trichb (1000)\n\tpiavpn (1002)\n\ttty (5)\n\tcrontab (108)\n\tmail (8)\n\tmlocate (115)\n\tplugdev (46)\n\tssh (116)\n\tgames (60)\n\tmessagebus (113)\n\tnogroup (65534)\n\tutmp (43)\n\tstaff (50)\n\tlpadmin (111)\n\tman (12)\n\tcolord (121)\n\tlightdm (128)\n\tntp (112)\n\tsambashare (127)\n\tadm (4)"
2019-10-19 08:01:47.509 DBG default: +++ void MainWindow::makeMd5sum(QString, QString) +++
2019-10-19 08:01:47.509 DBG default: sync
2019-10-19 08:01:47.548 DBG default: md5sum "linuxfs">"/tmp/mx-snapshot-y2hbE1Aw/iso-template/antiX/linuxfs.md5"
2019-10-19 08:01:59.983 DBG default: mv iso-template/antiX/linuxfs* iso-2/antiX
2019-10-19 08:01:59.992 DBG default: installed-to-live cleanup
2019-10-19 08:02:01.177 DBG default: xorriso -as mkisofs -l -V MXLIVE -R -J -pad -iso-level 3 -no-emul-boot -boot-load-size 4 -boot-info-table -b boot/isolinux/isolinux.bin -eltorito-alt-boot -e boot/grub/efi.img -no-emul-boot -c boot/isolinux/isolinux.cat -o "/home/snapshot/snapshot-20191019_0759.iso" . "/tmp/mx-snapshot-y2hbE1Aw/iso-2"
2019-10-19 08:02:01.189 WRN default: "xorriso 1.5.0 : RockRidge filesystem manipulator, libburnia project."
2019-10-19 08:02:01.201 WRN default: "Drive current: -outdev 'stdio:/home/snapshot/snapshot-20191019_0759.iso'\nMedia current: stdio file, overwriteable\nMedia status : is blank\nMedia summary: 0 sessions, 0 data blocks, 0 data, 197g free"
2019-10-19 08:02:01.232 WRN default: "Added to ISO image: directory '/'='/tmp/mx-snapshot-y2hbE1Aw/iso-template'\nxorriso : UPDATE : 935 files added in 1 seconds"
2019-10-19 08:02:01.243 WRN default: "Added to ISO image: directory '/'='/tmp/mx-snapshot-y2hbE1Aw/iso-2'\nxorriso : FAILURE : Cannot find in ISO image: -boot_image ... bin_path='/boot/isolinux/isolinux.bin'\nxorriso : UPDATE : 938 files added in 1 seconds\nxorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'"
2019-10-19 08:02:07.244 DBG default: +++ void MainWindow::cleanUp() +++
2019-10-19 08:02:07.244 DBG default: sync
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 8:36 am
by Eadwine Rose
Here is my output when I do the exact same, leaving all default and personal snapshot.
Code: Select all
File /.bind-root/home/eadwine/.config/xfce4/desktop/icons.screen0-3824x1020.rc changed size while reading filesystem, attempting to re-readParallel mksquashfs: Using 16 processors
Creating 4.0 filesystem on iso-template/antiX/linuxfs, block size 131072.
[=========================================================\] 220969/220969 100%
Exportable Squashfs 4.0 filesystem, lz4 compressed, data block size 131072
compressed data, compressed metadata, compressed fragments, compressed xattrs
duplicates are removed
Filesystem size 2717775.19 Kbytes (2654.08 Mbytes)
50.11% of uncompressed filesystem size (5423597.54 Kbytes)
Inode table size 4227635 bytes (4128.55 Kbytes)
39.29% of uncompressed inode table size (10760956 bytes)
Directory table size 4345206 bytes (4243.37 Kbytes)
55.28% of uncompressed directory table size (7860065 bytes)
Xattr table size 58 bytes (0.06 Kbytes)
48.33% of uncompressed xattr table size (120 bytes)
Number of duplicate files found 20869
Number of inodes 297286
Number of files 196808
Number of fragments 11425
Number of symbolic links 83766
Number of device nodes 0
Number of fifo nodes 1
Number of socket nodes 40
Number of directories 16671
Number of ids (unique uids + gids) 32
Number of uids 10
root (0)
lp (7)
eadwine (1000)
_apt (100)
man (6)
colord (114)
lightdm (118)
statd (109)
ntp (105)
nm-openvpn (112)
Number of gids 26
root (0)
dip (30)
lp (7)
shadow (42)
ssl-cert (110)
dialout (20)
eadwine (1000)
tty (5)
crontab (108)
mail (8)
mlocate (115)
plugdev (46)
ssh (116)
games (60)
messagebus (113)
utmp (43)
staff (50)
lpadmin (111)
man (12)
colord (121)
lightdm (128)
nogroup (65534)
ntp (112)
nm-openvpn (120)
sambashare (127)
adm (4)
xorriso 1.5.0 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev 'stdio:/home/snapshot/snapshot-20191019_1422.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 151g free
Added to ISO image: directory '/'='/home/mx-snapshot-jgQz9oQb/iso-template'
xorriso : UPDATE : 926 files added in 1 seconds
Added to ISO image: directory '/'='/home/mx-snapshot-jgQz9oQb/iso-2'
xorriso : UPDATE : 929 files added in 1 seconds
xorriso : UPDATE : 1.72% done
xorriso : UPDATE : 18.32% done
xorriso : UPDATE : 36.76% done, estimate finish Sat Oct 19 14:24:01 2019
xorriso : UPDATE : 55.02% done, estimate finish Sat Oct 19 14:24:01 2019
xorriso : UPDATE : 72.44% done, estimate finish Sat Oct 19 14:24:01 2019
xorriso : UPDATE : 91.08% done
ISO image produced: 1375250 sectors
Written to medium : 1375250 sectors at LBA 0
Writing to 'stdio:/home/snapshot/snapshot-20191019_1422.iso' completed successfully.
isohybrid: Warning: more than 1024 cylinders: 2687
isohybrid: Not all BIOSes will be able to boot this device
MX Snapshot completed sucessfully!
Snapshot took 00:01:01 to finish.
Thanks for using MX Snapshot, run MX Live USB Maker next!
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 8:40 am
by richb
@Eadwine One difference I see in this line:
Mine
Added to ISO image: directory '/'='/tmp/mx-snapshot-y2hbE1Aw/iso-2'
Yours
Added to ISO image: directory '/'='/home/mx-snapshot-jgQz9oQb/iso-2
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 8:41 am
by Eadwine Rose
I wonder how that happens.. was using the latest iso, official SF downloaded RC1.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 8:45 am
by richb
Eadwine Rose wrote: Sat Oct 19, 2019 8:41 am
I wonder how that happens.. was using the latest iso, official SF downloaded RC1.
I also. I installed using whole disk, no pre-partitioning so my home is under root not a separate partition.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 8:46 am
by Eadwine Rose
Mine is not using the whole disk. I have partitions for root, home, and swap set up, and one of those tiny partitions one needs for the UEFI lalala.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 8:53 am
by richb
Eadwine Rose wrote: Sat Oct 19, 2019 8:46 am
Mine is not using the whole disk. I have partitions for root, home, and swap set up, and one of those tiny partitions one needs for the UEFI lalala.
May be a clue why it failed for me.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 1:02 pm
by scatman98
JayM wrote: Sat Oct 19, 2019 7:02 am
scatman98 wrote: Sat Oct 19, 2019 1:32 am
congrats on the RC1
issue i have is the Monitor on desktop goes blank or freezes, needs a restart.
it is an AMD system with nvidia GPU. using 4.9.`93 kernel, mainly because 4.19.0.6 doesnt work with iridium browser.
Please run MX Tools / Quick System Info, then right-click and paste in a response. (Quick System Info automatically copies the information to your clipboard, already formatted correctly to be pasted in the forum, so just right click / paste and not copy / paste.) Thank you.
hi jayM , i have attached it in post no 136
https://forum.mxlinux.org/viewtopic.php ... 54#p534254
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 2:19 pm
by winemaker
not sure if relevant - but i installed both of my thinkpads as whole disks - and let the installer do its thing. no issues - will try wife's dell probably monday when storms hit here.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 2:21 pm
by Lupin
i've been running rc1 on a live usb for about an hour now, i thought it will cool down but my laptop is running slightly hot even after an hour or so. no apps are running except the browser, im sure its not the browser cause it still runs hot (around 60 degrees) on idle(my idle temp on 18.3 is around 39-40 degrees). anybody had the same experience?
Code: Select all
System: Host: mx1 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: quiet splasht
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: ASUSTeK product: N56JRH v: 1.0 serial: <filter>
Mobo: ASUSTeK model: N56JRH v: 1.0 serial: <filter> BIOS: American Megatrends
v: N56JRH.204 date: 06/12/2019
CPU: Topology: Quad Core model: Intel Core i7-4700HQ bits: 64 type: MT MCP arch: Haswell
family: 6 model-id: 3C (60) stepping: 3 microcode: 17 L2 cache: 6144 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 38311
Speed: 1098 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 1098 2: 1098 3: 1097
4: 1098 5: 1098 6: 1098 7: 1098 8: 1098
Vulnerabilities: Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: ASUSTeK
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416
Device-2: NVIDIA GK106M [GeForce GTX 760M] vendor: ASUSTeK driver: N/A
bus ID: 01:00.0 chip ID: 10de:11e3
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.3.6 compat-v: 3.0
direct render: Yes
Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel
v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c
Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: AzureWave
driver: ath9k v: kernel port: e000 bus ID: 03:00.0 chip ID: 168c:0032
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
driver: r8169 v: kernel port: d000 bus ID: 04:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.14 TiB used: 59.8 MiB (0.0%)
ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB
block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm
serial: <filter> rev: 0001 scheme: MBR
ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: MBR
ID-3: /dev/sdc type: USB vendor: Generic model: USB Flash size: 7.62 GiB block size:
physical: 512 B logical: 512 B serial: <filter> rev: 0.00 scheme: MBR
Partition: ID-1: / raw size: N/A size: 6.08 GiB used: 59.8 MiB (1.0%) fs: overlay
source: ERR-102
ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda1
Sensors: System Temperatures: cpu: 55.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2600
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 229 Uptime: 14m Memory: 7.68 GiB used: 825.3 MiB (10.5%) 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
Video Tweaks:
Detected possible Hybrid Graphics
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 3:04 pm
by BitJam
@richb, I think the problem is here:
richb wrote: Sat Oct 19, 2019 8:10 amCode: Select all
xorriso : FAILURE : Cannot find in ISO image: -boot_image ... bin_path='/boot/isolinux/isolinux.bin'
xorriso : UPDATE : 938 files added in 1 seconds
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
That file is part of the legacy bootloader in the iso. I don't know why it would be missing. It should be inside of the iso-template.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 3:12 pm
by Paul..
@BitJam...Just replicated snapshot problem here, too...same error, FAILURE : Cannot find in ISO image: -boot_image ... bin_path='/boot/isolinux/isolinux.bin'
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 3:17 pm
by BV206
On Xubuntu and Debian the xfce panel preference window has a Profiles: section with a Backup and restore button at the top above the panel add/remove dropdown list. It allows you to select preset xfce panel configurations and save/export/import your customized panels.
I just notice that it is missing in MX19 but I don't remember if it was there on 18 and 17.
Is it supposed to be there or does MX-Tweak supply those functions?
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 3:32 pm
by Eadwine Rose
It's not missing.
MX tweak does that. I backup the .restore folder in /home/username/ and put it back in where I want it.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 4:10 pm
by dolphin_oracle
ok probably my fault. something went hey wire when I built the new mx-iso-template package. new one coming soon. sorry about that.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 4:44 pm
by Stevo
scatman98 wrote: Sat Oct 19, 2019 1:32 am
congrats on the RC1
issue i have is the Monitor on desktop goes blank or freezes, needs a restart.
it is an AMD system with nvidia GPU. using 4.9.`93 kernel, mainly because 4.19.0.6 doesnt work with iridium browser.
Iridium will work on the stock Kernel with the flag to disable the sandbox, or with Liquorix kernels (I think the problem with MXPI installing the MX 17 Liquorix kernels on MX 19 is fixed now, (Nvidia drivers won't build on mismatched kernels), but a workaround in the meantime was to install the Liquorix header and image packages from the MXPI's test repo tab. I know the test repo Nvidia-driver 435.21 is fine on the 5.2 Liquorix kernels, but am going to have to double check the legacy drivers.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 4:59 pm
by Stevo
asqwerth wrote: Sat Oct 19, 2019 4:04 am
dolphin_oracle wrote: Fri Oct 18, 2019 8:03 am
...I've asked the package guys to look at modifying the luckybackup package to address this.
Oh, FWIW, on MX 19, su-to-root and gksu will both actually use mx-pkexec.
Stevo wrote: Fri Oct 18, 2019 3:41 pm
A patched Lucky Backup is done and should be seen as an upgrade in the main repos pretty soon.
Dolphin, with the patched lucky backup, the icon (for both user and root lucky backup) has reverted back to the old xpm ones because of the hard coding of the icon filepath in the .desktop file.
Instead of:
Code: Select all
Icon=/usr/share/pixmaps/luckybackup.png
It should read:
so that it can apply the icon in Papirus.
Is this program still being maintained by a dev who can take bug reports?
OK, I'll roll another update. I didn't know we had a version that changed the desktop files for MX 17/18. Is "luckyBackup" the exact spelling and capitalization that we need to use?
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 5:08 pm
by dolphin_oracle
Paul.. wrote: Sat Oct 19, 2019 3:12 pm
@BitJam...Just replicated snapshot problem here, too...same error, FAILURE : Cannot find in ISO image: -boot_image ... bin_path='/boot/isolinux/isolinux.bin'
new mx-iso-template here:
https://github.com/MX-Linux/mx-iso-temp ... b?raw=true
I did test this one before uploading
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 5:10 pm
by dolphin_oracle
Stevo wrote: Sat Oct 19, 2019 4:59 pm
OK, I'll roll another update. I didn't know we had a version that changed the desktop files for MX 17/18. Is "luckyBackup" the exact spelling and capitalization that we need to use?
I pm'd stevo with some details...
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 5:48 pm
by Stevo
If we want it to always show the Papirus-type in the menu for us, can't I just just have our build install that icon into /usr/share/pixmaps during the build and overwrite the stock one? That's really easy to do. If so, can someone attach that icon to a message here?
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 6:00 pm
by dolphin_oracle
Stevo wrote: Sat Oct 19, 2019 5:48 pm
If we want it to always show the Papirus-type in the menu for us, can't I just just have our build install that icon into /usr/share/pixmaps during the build and overwrite the stock one? That's really easy to do. If so, can someone attach that icon to a message here?
that's not actually what we want. we want the theme's icon to be used, if present.
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 6:13 pm
by Stevo
OK, here's the builds with the fix-menu-icon.patch:
https://drive.google.com/open?id=1t4uDX ... NBDUWh9oQp
I have heavy stuff building on my MX 18 install that I can't interrupt, so can someone check these out?
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 8:50 pm
by nathan2423
@BitJam...Just replicated snapshot problem here, too...same error, FAILURE : Cannot find in ISO image: -boot_image ... bin_path='/boot/isolinux/isolinux.bin'
I can confirm the same issue, and can confirm that no matter how many times you try, it fails the same way! ;-) Am currently running it with the updated template file that just came over the updater, using a 15gb home+root partitions, and can report now ..... SUCCESS PAST THAT ERROR ANYWAY ....
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 9:14 pm
by richb
nathan2423 wrote: Sat Oct 19, 2019 8:50 pm
@BitJam...Just replicated snapshot problem here, too...same error, FAILURE : Cannot find in ISO image: -boot_image ... bin_path='/boot/isolinux/isolinux.bin'
I can confirm the same issue, and can confirm that no matter how many times you try, it fails the same way! ;-) Am currently running it with the updated template file that just came over the updater, using a 15gb home+root partitions, and can report now ..... SUCCESS PAST THAT ERROR ANYWAY ....
Yes. That has fixed it, the 19.10.03 version
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 9:24 pm
by Paul..
Re: MX-19 RC1 Feedback thread
Posted: Sat Oct 19, 2019 10:04 pm
by tascoast
I found a small improvement in my dual monitor setup, which was detected automatically, but required a couple of reboots and ARandR adjustments, whereby I think having defaults settings backed up finally locked in the monitors to correct arrangement (left-right as physically positioned, rather than hardware default that reversed arrangement on start-up.)
Screenshot also works better, no longer including an artifact of slightly different display proportions.
I did encounter an old issue common sometimes arising after installs of past versions of MX, that being Disk Manager not correctly recognising a NTFS, meaning that partition requires root access to write:
So I changed the Type to NTFS- 3g to resolve. I expect this will be a simple fix that is confirmed upon restarting the system
Trying to cheat a bit with Grub Customizer no longer works! I will need to reconsider how I approach editing Grub menus and study the fine print again. I have manually edited earlier Grub menus so should cope.
It doesn't bother me if I need to install MX-19 again when actually released
I quite like the font viewer inclusion and shall revisit some font collection to both explore and add. I can skip Waterfall, which I sometimes add for publishing needs.
Thank you to all contributing to this fine edition of MX and the hard work involved in getting translations and other detail polished up and included for eventual release, remarkably efficiently I should add.
Mick
Code: Select all
[code]
System: Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=d9ff2784-9c3e-4be2-9128-a6e5524c9aa4 ro quiet
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: LENOVO product: 7522RU3 v: ThinkCentre A58 serial: <filter>
Mobo: LENOVO model: N/A serial: <filter> BIOS: LENOVO v: 5HKT52AUS date: 07/15/2010
CPU: Topology: Dual Core model: Intel Core2 Duo E7300 bits: 64 type: MCP arch: Penryn
family: 6 model-id: 17 (23) stepping: 6 microcode: 60F L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 bogomips: 10638
Speed: 1596 MHz min/max: 1603/2670 MHz Core speeds (MHz): 1: 1596 2: 1596
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: AMD Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM] vendor: Dell
driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6778
Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1440x900~60Hz, 1680x1050~60Hz
OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 4.19.0-6-amd64 LLVM 7.0.1)
v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: Yes
Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Marvell 88E8057 PCI-E Gigabit Ethernet vendor: Lenovo driver: sky2 v: 1.30
port: e800 bus ID: 03:00.0 chip ID: 11ab:4380
IF: eth0 state: down mac: <filter>
IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac: <filter>
Drives: Local Storage: total: 931.51 GiB used: 174.34 GiB (18.7%)
ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-22MFCA0 size: 931.51 GiB
block size: physical: 4096 B logical: 512 B speed: <unknown> rotation: 7200 rpm
serial: <filter> rev: 1A01 scheme: MBR
Partition: ID-1: / raw size: 22.19 GiB size: 21.71 GiB (97.87%) used: 11.49 GiB (52.9%) fs: ext4
dev: /dev/sda12
ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda5
Sensors: System Temperatures: cpu: 38.0 C mobo: N/A gpu: radeon temp: 43 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 192 Uptime: 2m Memory: 3.85 GiB used: 548.7 MiB (13.9%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 al
Edit:
https://drive.google.com/open?id=1ET7fa ... fVfYrySU1y (desktop screenshot)
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 8:14 am
by Paul..
EDIT: Ignore below...booted USB snapshot drive successfully with boot option "xorg=nvidia" thanks to Eadwine Rose...
After recent Snapshot fix...ran some more tests
Spoke too soon, I guess. We may have a problem with the content of the Snapshot...maybe stuff missing...here's what happened
Ran Snapshot...used LUM to burn flashdrive....booted flashdrive (UEFI without persistence)....
- Terminal login prompt
- No X
- No nvidia driver
- No nouveau driver
- Tried installing nvidia as root "ddm-mx -i nvidia"...but ddm-mx indicated that nvidia driver was installed but not active...selected re-install...but no network available
- Then tried booting in 1024x768...vesa...no good
mx-snapshot.log
Code: Select all
2019-10-19 21:09:34.820 DBG default: mx-snapshot version: 19.10.01
2019-10-19 21:09:34.862 DBG default: mountpoint -q /live/aufs
2019-10-19 21:09:34.866 DBG default: lslogins --noheadings -u -o user | grep -vw root
2019-10-19 21:09:34.872 DBG default: "daddio"
2019-10-19 21:09:34.872 DBG default: uname -m
2019-10-19 21:09:34.876 DBG default: "x86_64"
2019-10-19 21:09:34.876 DBG default: cat /etc/debian_version | cut -f1 -d'.'
2019-10-19 21:09:34.880 DBG default: "10"
2019-10-19 21:09:34.880 DBG default: +++ void MainWindow::setup() +++
2019-10-19 21:09:34.920 DBG default: +++ void MainWindow::loadSettings() +++
2019-10-19 21:09:34.920 DBG default: +++ QString MainWindow::getFilename() +++
2019-10-19 21:09:34.920 DBG default: date +%Y%m%d_%H%M
2019-10-19 21:09:34.987 DBG default: "20191019_2109"
2019-10-19 21:09:34.994 DBG default: +++ void MainWindow::listFreeSpace() +++
2019-10-19 21:09:34.994 DBG default: df -h "/home" | awk 'NR==2 {print $4}'
2019-10-19 21:09:34.999 DBG default: "30G"
2019-10-19 21:09:35.000 DBG default: +++ QString MainWindow::getSnapshotSize() +++
2019-10-19 21:09:35.000 DBG default: find "/home/snapshot" -maxdepth 1 -type f -name '*.iso' -exec du -shc {} + | tail -1 | awk '{print $1}'
2019-10-19 21:09:35.007 DBG default: +++ int MainWindow::getSnapshotCount() +++
2019-10-19 21:09:35.007 DBG default: df -h / | awk 'NR==2 {print $3}'
2019-10-19 21:09:35.026 DBG default: "7.2G"
2019-10-19 21:09:35.026 DBG default: mountpoint -q /home
2019-10-19 21:09:37.608 DBG default: uname -r
2019-10-19 21:09:37.620 DBG default: "4.19.0-6-amd64"
2019-10-19 21:09:42.100 DBG default: [ -f /boot/config-$(uname -r) ]
2019-10-19 21:09:42.106 DBG default: grep ^CONFIG_SQUASHFS_LZ4=y /boot/config-$(uname -r)
2019-10-19 21:09:42.113 DBG default: "CONFIG_SQUASHFS_LZ4=y"
2019-10-19 21:09:44.424 DBG default: +++ void MainWindow::checkDirectories() +++
2019-10-19 21:09:44.424 DBG default: +++ bool MainWindow::isOnSupportedPart(QDir) +++
2019-10-19 21:09:44.424 DBG default: stat --file-system --format=%T /home/snapshot
2019-10-19 21:09:44.432 DBG default: "ext2/ext3"
2019-10-19 21:09:44.432 DBG default: detected partition "ext2/ext3" supported part: true
2019-10-19 21:09:44.432 DBG default: +++ QString MainWindow::largerFreeSpace(QString, QString, QString) +++
2019-10-19 21:09:44.432 DBG default: +++ QString MainWindow::largerFreeSpace(QString, QString) +++
2019-10-19 21:09:44.433 DBG default: df -k --output=avail /tmp 2>/dev/null | tail -n1
2019-10-19 21:09:44.437 DBG default: "30476404"
2019-10-19 21:09:44.437 DBG default: df -k --output=avail /home 2>/dev/null | tail -n1
2019-10-19 21:09:44.443 DBG default: "30476404"
2019-10-19 21:09:44.443 DBG default: +++ QString MainWindow::largerFreeSpace(QString, QString) +++
2019-10-19 21:09:44.443 DBG default: df -k --output=avail /tmp 2>/dev/null | tail -n1
2019-10-19 21:09:44.447 DBG default: "30476404"
2019-10-19 21:09:44.447 DBG default: df -k --output=avail /home/snapshot 2>/dev/null | tail -n1
2019-10-19 21:09:44.450 DBG default: "30476404"
2019-10-19 21:09:44.451 DBG default: mktemp -d "/tmp/mx-snapshot-XXXXXXXX"
2019-10-19 21:09:44.454 DBG default: "/tmp/mx-snapshot-zWPddX2P"
2019-10-19 21:09:44.462 DBG default: +++ void MainWindow::copyNewIso() +++
2019-10-19 21:09:44.468 DBG default: tar xf /usr/lib/iso-template/iso-template.tar.gz
2019-10-19 21:09:44.621 DBG default: cp /usr/lib/iso-template/template-initrd.gz iso-template/antiX/initrd.gz
2019-10-19 21:09:44.625 DBG default: cp /boot/vmlinuz-4.19.0-6-amd64 iso-template/antiX/vmlinuz
2019-10-19 21:09:44.632 DBG default: +++ void MainWindow::replaceMenuStrings() +++
2019-10-19 21:09:44.632 DBG default: date +'%d %B %Y'
2019-10-19 21:09:44.635 DBG default: "19 October 2019"
2019-10-19 21:09:44.635 DBG default: cat /etc/antix-version | cut -f1 -d'_'
2019-10-19 21:09:44.638 DBG default: "MX-19RC1"
2019-10-19 21:09:44.639 DBG default: grep -oP '(?<=DISTRIB_ID=).*' /etc/lsb-release
2019-10-19 21:09:44.644 DBG default: "MX"
2019-10-19 21:09:44.644 DBG default: cat /etc/antix-version | cut -f-2 -d' '
2019-10-19 21:09:44.648 DBG default: "MX-19RC1_x64 patito"
2019-10-19 21:09:44.648 DBG default: grep -oP '(?<=DISTRIB_CODENAME=).*' /etc/lsb-release
2019-10-19 21:09:44.653 DBG default: "\"patito feo\""
2019-10-19 21:09:44.653 DBG default: sed -i 's/%DISTRO_NAME%/MX/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/grub/grub.cfg"
2019-10-19 21:09:44.659 DBG default: sed -i 's/%OPTIONS%/quiet/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/syslinux/syslinux.cfg"
2019-10-19 21:09:44.664 DBG default: sed -i 's/%OPTIONS%/quiet/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/isolinux/isolinux.cfg"
2019-10-19 21:09:44.668 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/grub/grub.cfg"
2019-10-19 21:09:44.672 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/syslinux/syslinux.cfg"
2019-10-19 21:09:44.677 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/syslinux/readme.msg"
2019-10-19 21:09:44.682 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/isolinux/isolinux.cfg"
2019-10-19 21:09:44.688 DBG default: sed -i 's/%FULL_DISTRO_NAME%/MX-19RC1_x64 patito/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/isolinux/readme.msg"
2019-10-19 21:09:44.692 DBG default: sed -i 's/%DISTRO%/MX-19RC1/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/grub/theme/theme.txt"
2019-10-19 21:09:44.696 DBG default: sed -i 's/%DISTRO%/MX-19RC1/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/grub/grub.cfg"
2019-10-19 21:09:44.700 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/grub/grub.cfg"
2019-10-19 21:09:44.706 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/syslinux/syslinux.cfg"
2019-10-19 21:09:44.711 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/syslinux/readme.msg"
2019-10-19 21:09:44.717 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/isolinux/isolinux.cfg"
2019-10-19 21:09:44.722 DBG default: sed -i 's/%RELEASE_DATE%/19 October 2019/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/isolinux/readme.msg"
2019-10-19 21:09:44.728 DBG default: sed -i 's/%CODE_NAME%/"patito feo"/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/syslinux/syslinux.cfg"
2019-10-19 21:09:44.733 DBG default: sed -i 's/%CODE_NAME%/"patito feo"/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/isolinux/isolinux.cfg"
2019-10-19 21:09:44.737 DBG default: sed -i 's/%ASCII_CODE_NAME%/"patito feo"/g' "/tmp/mx-snapshot-zWPddX2P/iso-template/boot/grub/theme/theme.txt"
2019-10-19 21:09:44.743 DBG default: /usr/share/mx-packageinstaller/scripts/make-efi-img /tmp/mx-snapshot-zWPddX2P/iso-template/
2019-10-19 21:09:44.749 WRN default: "Missing file /tmp/mx-snapshot-zWPddX2P/iso-template/EFI/BOOT/BOOTx64.EFI"
2019-10-19 21:09:44.749 WRN default: "Missing file /tmp/mx-snapshot-zWPddX2P/iso-template/EFI/BOOT/bootx64.efi"
2019-10-19 21:09:44.755 WRN default: "Missing file /tmp/mx-snapshot-zWPddX2P/iso-template/EFI/BOOT/fallback.efi"
2019-10-19 21:09:44.755 WRN default: "Missing file /tmp/mx-snapshot-zWPddX2P/iso-template/EFI/BOOT/mt86.png"
2019-10-19 21:09:44.758 DBG default: "Kilobytes needed: 2112"
2019-10-19 21:09:44.758 DBG default: "Try size: 2142 margin: 30"
2019-10-19 21:09:45.031 DBG default: "Final size: 2152 margin: 40"
2019-10-19 21:09:45.096 WRN default: "rmdir: failed to remove '/tmp/make-efi-img/mp'"
2019-10-19 21:09:45.096 WRN default: ": Directory not empty"
2019-10-19 21:09:45.098 WRN default: "rmdir: failed to remove '/tmp/make-efi-img': Directory not empty"
2019-10-19 21:09:45.098 DBG default: "make-efi-img created boot/grub/efi.img"
2019-10-19 21:09:45.098 DBG default: +++ void MainWindow::makeMd5sum(QString, QString) +++
2019-10-19 21:09:45.098 DBG default: sync
2019-10-19 21:09:45.119 DBG default: md5sum "vmlinuz">"/tmp/mx-snapshot-zWPddX2P/iso-template/antiX/vmlinuz.md5"
2019-10-19 21:09:45.138 DBG default: mktemp -d
2019-10-19 21:09:45.142 DBG default: "/tmp/tmp.1Ev4kcueUC"
2019-10-19 21:09:45.142 DBG default: +++ void MainWindow::openInitrd(QString, QString) +++
2019-10-19 21:09:45.142 DBG default: chmod a+rx "/tmp/tmp.1Ev4kcueUC"
2019-10-19 21:09:45.146 DBG default: gunzip -c "/tmp/mx-snapshot-zWPddX2P/iso-template/antiX/initrd.gz" | cpio -idum
2019-10-19 21:09:45.194 WRN default: "7177 blocks"
2019-10-19 21:09:45.195 DBG default: test -d "/tmp/tmp.1Ev4kcueUC/lib/modules" && rm -r "/tmp/tmp.1Ev4kcueUC/lib/modules"
2019-10-19 21:09:45.198 DBG default: test -r /usr/local/share/live-files/files/etc/initrd-release && cp /usr/local/share/live-files/files/etc/initrd-release "/tmp/tmp.1Ev4kcueUC/etc"
2019-10-19 21:09:45.201 DBG default: test -r /etc/initrd-release && cp /etc/initrd-release "/tmp/tmp.1Ev4kcueUC/etc"
2019-10-19 21:09:45.206 DBG default: /usr/share/mx-packageinstaller/scripts/copy-initrd-modules -t="/tmp/tmp.1Ev4kcueUC" -k="4.19.0-6-amd64"
2019-10-19 21:09:45.232 WRN default: "modprobe: WARNING: Module aufs not found in directory /lib/modules/4.19.0-6-amd64\nmodprobe: WARNING: Module block not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.232 WRN default: "modprobe: WARNING: Module fotg210-hcd not found in directory /lib/modules/4.19.0-6-amd64\nmodprobe: WARNING: Module fusbh200-hcd not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.232 WRN default: "modprobe: WARNING: Module hid-lenovo-tpkbd not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.233 WRN default: "modprobe: WARNING: Module hyperv not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.233 WRN default: "modprobe: WARNING: Module jbd not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.233 WRN default: "modprobe: WARNING: Module ntfs not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.234 WRN default: "modprobe: WARNING: Module pcie-aspm not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.234 WRN default: "modprobe: WARNING: Module printk not found in directory /lib/modules/4.19.0-6-amd64\nmodprobe: WARNING: Module rts5139 not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.234 WRN default: "modprobe: WARNING: Module shpchp not found in directory /lib/modules/4.19.0-6-amd64"
2019-10-19 21:09:45.887 DBG default: /usr/share/mx-packageinstaller/scripts/copy-initrd-programs --to="/tmp/tmp.1Ev4kcueUC"
2019-10-19 21:09:45.897 DBG default: "add program: ntfs-3g"
2019-10-19 21:09:45.976 DBG default: "ld_linux: /lib64/ld-linux-x86-64.so.2"
2019-10-19 21:09:45.980 DBG default: "ld_dir: /tmp/tmp.1Ev4kcueUC/lib/x86_64-linux-gnu"
2019-10-19 21:09:45.998 DBG default: "add program: eject"
2019-10-19 21:09:46.027 DBG default: "ld_linux: /lib64/ld-linux-x86-64.so.2"
2019-10-19 21:09:46.028 DBG default: "ld_dir: /tmp/tmp.1Ev4kcueUC/lib/x86_64-linux-gnu"
2019-10-19 21:09:46.040 DBG default: +++ void MainWindow::closeInitrd(QString, QString) +++
2019-10-19 21:09:46.040 DBG default: (find . | cpio -o -H newc --owner root:root | gzip -9) >"/tmp/mx-snapshot-zWPddX2P/iso-template/antiX/initrd.gz"
2019-10-19 21:09:55.289 WRN default: "55706 blocks"
2019-10-19 21:09:55.303 DBG default: rm -r /tmp/tmp.1Ev4kcueUC
2019-10-19 21:09:55.331 DBG default: +++ void MainWindow::makeMd5sum(QString, QString) +++
2019-10-19 21:09:55.331 DBG default: sync
2019-10-19 21:09:55.335 WRN default: "shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory"
2019-10-19 21:09:55.343 DBG default: md5sum "initrd.gz">"/tmp/mx-snapshot-zWPddX2P/iso-template/antiX/initrd.gz.md5"
2019-10-19 21:09:55.368 DBG default: +++ void MainWindow::mkDir(QString) +++
2019-10-19 21:09:55.368 DBG default: +++ void MainWindow::savePackageList(QString) +++
2019-10-19 21:09:55.368 DBG default: dpkg -l | grep ^ii\ \ | awk '{print $2,$3}' | sed 's/:'$(dpkg --print-architecture)'//' | column -t >"/tmp/mx-snapshot-zWPddX2P/iso-template/snapshot-20191019_2109/package_list"
2019-10-19 21:09:55.417 DBG default: +++ void MainWindow::setupEnv() +++
2019-10-19 21:09:55.417 DBG default: mountpoint /boot
2019-10-19 21:09:55.420 DBG default: "/boot is not a mountpoint"
2019-10-19 21:09:55.420 DBG default: +++ bool MainWindow::checkInstalled(QString) +++
2019-10-19 21:09:55.421 DBG default: dpkg -s mx-installer | grep Status
2019-10-19 21:09:55.451 DBG default: "Status: install ok installed"
2019-10-19 21:09:55.452 DBG default: echo /home/*/Desktop | xargs -n1 cp /usr/share/applications/minstall.desktop 2>/dev/null
2019-10-19 21:09:55.459 DBG default: chmod +x /home/*/Desktop/minstall.desktop
2019-10-19 21:09:55.464 DBG default: installed-to-live -b /.bind-root start bind=/home live-files version-file adjtime read-only
2019-10-19 21:09:55.924 DBG default: +++ bool MainWindow::createIso(QString) +++
2019-10-19 21:09:55.924 DBG default: +++ void MainWindow::addRemoveExclusion(bool, QString) +++
2019-10-19 21:09:55.925 DBG default: +++ void MainWindow::addRemoveExclusion(bool, QString) +++
2019-10-19 21:09:55.925 DBG default: mksquashfs /.bind-root iso-template/antiX/linuxfs -comp lz4 -wildcards -ef /usr/local/share/excludes/mx-snapshot-exclude.list -e "home/snapshot" "tmp/mx-snapshot-zWPddX2P"
2019-10-19 21:09:58.432 DBG default: "Parallel mksquashfs: Using 8 processors\nCreating 4.0 filesystem on iso-template/antiX/linuxfs, block size 131072.\n\r[=========/ ] 40800/232720 17%"
2019-10-19 21:10:02.706 DBG default: "[=========================================================\\] 232720/232720 100%"
2019-10-19 21:10:02.733 DBG default: "Exportable Squashfs 4.0 filesystem, lz4 compressed, data block size 131072\n\tcompressed data, compressed metadata, compressed fragments, compressed xattrs\n\tduplicates are removed\nFilesystem size 3378038.72 Kbytes (3298.87 Mbytes)\n\t52.90% of uncompressed filesystem size (6385519.43 Kbytes)\nInode table size 4337666 bytes (4236.00 Kbytes)\n\t39.70% of uncompressed inode table size (10927335 bytes)\nDirectory table size 4484996 bytes (4379.88 Kbytes)\n\t56.17% of uncompressed directory table size (7984114 bytes)\nXattr table size 58 bytes (0.06 Kbytes)\n\t48.33% of uncompressed xattr table size (120 bytes)\nNumber of duplicate files found 19139\nNumber of inodes 301524\nNumber of files 201981\nNumber of fragments 12364\nNumber of symbolic links 83770\nNumber of device nodes 0\nNumber of fifo nodes 0\nNumber of socket nodes 24\nNumber of directories 15749\nNumber of ids (unique uids + gids) 32\nNumber of uids 10\n\troot (0)\n\tlp (7)\n\tdaddio (1000)\n\t_apt (100)\n\tman (6)\n\tcolord (114)\n\tlightdm (118)\n\tstatd (109)\n\tntp (105)\n\tnm-openvpn (112)\nNumber of gids 26\n\troot (0)\n\tdip (30)\n\tlp (7)\n\tshadow (42)\n\tssl-cert (110)\n\tdialout (20)\n\tdaddio (1000)\n\ttty (5)\n\tcrontab (108)\n\tmail (8)\n\tmlocate (115)\n\tplugdev (46)\n\tssh (116)\n\tgames (60)\n\tmessagebus (113)\n\tutmp (43)\n\tstaff (50)\n\tlpadmin (111)\n\tman (12)\n\tcolord (121)\n\tlightdm (128)\n\tnogroup (65534)\n\tntp (112)\n\tnm-openvpn (120)\n\tsambashare (127)\n\tadm (4)"
2019-10-19 21:10:02.801 DBG default: +++ void MainWindow::makeMd5sum(QString, QString) +++
2019-10-19 21:10:02.801 DBG default: sync
2019-10-19 21:10:02.816 DBG default: md5sum "linuxfs">"/tmp/mx-snapshot-zWPddX2P/iso-template/antiX/linuxfs.md5"
2019-10-19 21:10:08.448 DBG default: mv iso-template/antiX/linuxfs* iso-2/antiX
2019-10-19 21:10:08.452 DBG default: installed-to-live cleanup
2019-10-19 21:10:09.705 DBG default: xorriso -as mkisofs -l -V MXLIVE -R -J -pad -iso-level 3 -no-emul-boot -boot-load-size 4 -boot-info-table -b boot/isolinux/isolinux.bin -eltorito-alt-boot -e boot/grub/efi.img -no-emul-boot -c boot/isolinux/isolinux.cat -o "/home/snapshot/snapshot-20191019_2109.iso" . "/tmp/mx-snapshot-zWPddX2P/iso-2"
2019-10-19 21:10:09.711 WRN default: "xorriso 1.5.0 : RockRidge filesystem manipulator, libburnia project."
2019-10-19 21:10:09.716 WRN default: "Drive current: -outdev 'stdio:/home/snapshot/snapshot-20191019_2109.iso'\nMedia current: stdio file, overwriteable\nMedia status : is blank\nMedia summary: 0 sessions, 0 data blocks, 0 data, 25.8g free"
2019-10-19 21:10:09.735 WRN default: "Added to ISO image: directory '/'='/tmp/mx-snapshot-zWPddX2P/iso-template'\nxorriso : UPDATE : 926 files added in 1 seconds"
2019-10-19 21:10:09.738 WRN default: "Added to ISO image: directory '/'='/tmp/mx-snapshot-zWPddX2P/iso-2'\nxorriso : UPDATE : 929 files added in 1 seconds"
2019-10-19 21:10:09.842 WRN default: "xorriso : UPDATE : 2.57% done"
2019-10-19 21:10:10.343 WRN default: "xorriso : UPDATE : 14.96% done"
2019-10-19 21:10:11.344 WRN default: "xorriso : UPDATE : 37.40% done"
2019-10-19 21:10:12.345 WRN default: "xorriso : UPDATE : 59.99% done, estimate finish Sat Oct 19 21:10:14 2019"
2019-10-19 21:10:13.347 WRN default: "xorriso : UPDATE : 74.23% done, estimate finish Sat Oct 19 21:10:15 2019"
2019-10-19 21:10:14.348 WRN default: "xorriso : UPDATE : 84.08% done"
2019-10-19 21:10:15.349 WRN default: "xorriso : UPDATE : 93.96% done"
2019-10-19 21:10:16.350 WRN default: "xorriso : UPDATE : 99.72% done"
2019-10-19 21:10:17.351 WRN default: "ISO image produced: 1705381 sectors\nWritten to medium : 1705381 sectors at LBA 0"
2019-10-19 21:10:17.354 WRN default: "Writing to 'stdio:/home/snapshot/snapshot-20191019_2109.iso' completed successfully."
2019-10-19 21:10:17.358 DBG default: isohybrid --uefi "/home/snapshot/snapshot-20191019_2109.iso"
2019-10-19 21:10:17.366 WRN default: "isohybrid: Warning: more than 1024 cylinders: 3331\nisohybrid: Not all BIOSes will be able to boot this device"
2019-10-19 21:10:17.399 DBG default: +++ void MainWindow::makeMd5sum(QString, QString) +++
2019-10-19 21:10:17.399 DBG default: sync
2019-10-19 21:10:17.414 DBG default: md5sum "snapshot-20191019_2109.iso">"/home/snapshot/snapshot-20191019_2109.iso.md5"
2019-10-19 21:10:23.181 DBG default: +++ void MainWindow::makeSha512sum(QString, QString) +++
2019-10-19 21:10:23.181 DBG default: sync
2019-10-19 21:10:23.201 DBG default: sha512sum "snapshot-20191019_2109.iso">"/home/snapshot/snapshot-20191019_2109.iso.sha512"
2019-10-19 21:10:32.924 DBG default: "Snapshot took 00:00:48 to finish."
2019-10-19 21:10:32.924 DBG default: +++ void MainWindow::cleanUp() +++
2019-10-19 21:10:32.924 DBG default: sync
2019-10-19 21:10:36.470 WRN qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1730, resource id: 23074531, major code: 40 (TranslateCoords), minor code: 0
Code: Select all
2019-10-19 21:11:19.078 DBG default: mx-live-usb-maker version: 19.10
2019-10-19 21:11:19.114 DBG default: df -T / |tail -n1 |awk '{print $2}'
2019-10-19 21:11:19.120 DBG default: live-usb-maker --help | grep data-first
2019-10-19 21:11:19.173 DBG default: lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259
2019-10-19 21:11:19.213 DBG default: . /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev)
2019-10-19 21:11:43.569 DBG default: Options: "-N "
2019-10-19 21:11:43.589 DBG default: start io is 114848
2019-10-19 21:11:43.589 DBG default: max progress bar is 6936736
2019-10-19 21:11:43.590 DBG default: live-usb-maker gui -N -C off --from="/home/snapshot/snapshot-20191019_2109.iso" -t /dev/sdb
2019-10-19 21:14:11.333 WRN qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1469, resource id: 23083310, major code: 40 (TranslateCoords), minor code: 0
2019-10-19 21:14:12.105 DBG default: ""
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 8:24 am
by Eadwine Rose
Try booting the snapshot with an edited grub. Add this:
xorg=nvidia
see if that helps. It won't boot to a desktop for me otherwise (and that is snapshot made in 18.3).
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 8:36 am
by Paul..
Eadwine Rose wrote: Sun Oct 20, 2019 8:24 am
Try booting the snapshot with an edited grub. Add this:
xorg=nvidia
see if that helps. It won't boot to a desktop for me otherwise (and that is snapshot made in 18.3).
Hahaha...Perfect...Thanks, ER! (will edit post above...)
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 8:46 am
by Eadwine Rose
Great!! You can thank DO for that one, he helped me out with it back when and gave me that little boot option.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 9:27 am
by fehlix
Paul.. wrote: Sun Oct 20, 2019 8:36 am
Eadwine Rose wrote: Sun Oct 20, 2019 8:24 am
Try booting the snapshot with an edited grub. Add this:
xorg=nvidia
see if that helps. It won't boot to a desktop for me otherwise (and that is snapshot made in 18.3).
Hahaha...Perfect...Thanks, ER! (will edit post above...)
Would you mind trying the new vcard=menu boot option and select the found nvidia card.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 11:03 am
by asqwerth
I"m having a weird message when I try to upgrade:
Code: Select all
sudo apt update
[sudo] password for tuaztest:
Get:1 http://deb.debian.org/debian buster-updates InRelease [49.3 kB]
Hit:2 http://iso.mxrepo.com/antix/buster buster InRelease
Hit:3 http://mxrepo.com/mx/repo buster InRelease
Hit:4 http://deb.debian.org/debian buster InRelease
Hit:5 http://deb.debian.org/debian-security buster/updates InRelease
Fetched 49.3 kB in 2s (21.6 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
tuaztest@mx:~
$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
mx-apps
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
tuaztest@mx:~
The update was also held back if MX-updater was used.
Using Synaptic tells me the chroot-rescue will be removed and replaced by chroot-rescue-mx. Is that ok?
I'm puzzled because I used the "full-upgrade" command in terminal, which is supposed to accept removal of packages and installation of new ones, right?
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 11:09 am
by Jerry3904
I got that too. I figured that some prerequisite might not be available just yet.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 11:14 am
by winemaker
old dell inspiron - my wife's linux system. just installed and need to tweak stuff but so far it is working fine - thought i would let you guys know
Code: Select all
System: Host: pei Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=bb9848b2-d537-47b2-a7da-23df334466fa ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Portable System: Dell product: Inspiron N4010 v: A13 serial: <filter>
Mobo: Dell model: 021CN3 v: A13 serial: <filter> BIOS: Dell v: A13 date: 03/31/2011
Battery: ID-1: BAT0 charge: 6.3 Wh condition: 6.3/4.2 Wh (150%) volts: 12.5/11.1
model: SIMPLO Dell type: Li-ion serial: <filter> status: Full
CPU: Topology: Dual Core model: Intel Pentium P6100 bits: 64 type: MCP arch: Nehalem
family: 6 model-id: 25 (37) stepping: 5 microcode: 7 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 7980
Speed: 931 MHz min/max: 933/1999 MHz Core speeds (MHz): 1: 931 2: 931
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; 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
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Dell driver: i915
v: kernel bus ID: 00:02.0 chip ID: 8086:0046
Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 18.3.6
direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:3b56
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter
vendor: Dell Inspiron M5010 / XPS 8300 driver: wl v: kernel port: 1860
bus ID: 03:00.0 chip ID: 14e4:4727
IF: wlan0 state: up mac: <filter>
Device-2: Qualcomm Atheros AR8152 v1.1 Fast Ethernet vendor: Dell driver: atl1c
v: 1.0.1.1-NAPI port: 2000 bus ID: 04:00.0 chip ID: 1969:2060
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 465.76 GiB used: 6.19 GiB (1.3%)
ID-1: /dev/sda vendor: Seagate model: ST9500325AS size: 465.76 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter>
rev: DEM1 scheme: MBR
Partition: ID-1: / raw size: 463.73 GiB size: 455.45 GiB (98.21%) used: 6.19 GiB (1.4%) 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: System Temperatures: cpu: 45.0 C mobo: 0.0 C
Fan Speeds (RPM): cpu: 3147
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 171 Uptime: 59m Memory: 7.59 GiB used: 551.6 MiB (7.1%) 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
thanks everyone!!!!!!!
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 11:14 am
by Iguana77
Hello,
I installed it on my laptop HP Envy 17 the new one MX-19 Release Candidate 1 and i have a problem with brightness.
On Current release: MX-18.3 everything works.
Maybe someone should check and fix it.
Until fix i stay on the stable old one MX-18.3.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 11:16 am
by Eadwine Rose
You could start with MX Tools - quick system info :) That will help us know more about your computer.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 11:23 am
by richb
Also please define what problem you are having with brightness.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 11:58 am
by Jerry3904
Normally, one of these takes care of that problem:
--dedicated key on laptop (mine is Fn-F5)
--Color Profiles (select one that works)
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 12:14 pm
by danielson
Just installed Launchy and it can't seem to find any files even after "rebuild catalog".
Anyone else have this issue?
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 12:27 pm
by Jerry3904
I installed it, logged out and back in, clicked "Rescan catalog" on the Options tab--and it found 196 entries. It worked sometimes... It found GIMP but not galculator, for instance.
EDIT: no, I just mispelled galculator the first time.
Seems to work fine now.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 12:37 pm
by dolphin_oracle
asqwerth wrote: Sun Oct 20, 2019 11:03 am
I"m having a weird message when I try to upgrade:
Code: Select all
sudo apt update
[sudo] password for tuaztest:
Get:1 http://deb.debian.org/debian buster-updates InRelease [49.3 kB]
Hit:2 http://iso.mxrepo.com/antix/buster buster InRelease
Hit:3 http://mxrepo.com/mx/repo buster InRelease
Hit:4 http://deb.debian.org/debian buster InRelease
Hit:5 http://deb.debian.org/debian-security buster/updates InRelease
Fetched 49.3 kB in 2s (21.6 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
tuaztest@mx:~
$ sudo apt full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
mx-apps
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
tuaztest@mx:~
The update was also held back if MX-updater was used.
Using Synaptic tells me the chroot-rescue will be removed and replaced by chroot-rescue-mx. Is that ok?
I'm puzzled because I used the "full-upgrade" command in terminal, which is supposed to accept removal of packages and installation of new ones, right?
the removal of chroot-resuce in place of chroot-rescue-mx is OK.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 12:57 pm
by srq2625
- In VB 6.0 (and, also noticed in Beta 3 (I think))
- With the panel in "horizontal" mode at the top of the screen
- With or without the "Dont' reserve space on borders" item selected in the "Display" tab of the panel properties dialog
Any window that is expanded to full size will fill the screen with the window title bar hidden under the panel. To re-size the window, have to use the <Alt>-<Right_CLick> trick.
Further, the first default icon on the desktop (Manual) is partially obscured (covered) by the panel.
Is this intended behavior? Can this behavior be changed and I've yet to find the how-to to accomplish it?
Code: Select all
System: Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=18e6a9c0-faba-4e29-adaf-c90e6ab9a4e3 ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 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
CPU: Topology: Dual Core model: AMD Ryzen 7 2700 bits: 64 type: MCP arch: Zen+
family: 17 (23) model-id: 8 stepping: 2 microcode: 6000626 L2 cache: 1024 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 13574
Speed: 3394 MHz min/max: N/A Core speeds (MHz): 1: 3394 2: 3394
Vulnerabilities: 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 generic retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.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
resolution: 1600x1200~60Hz
OpenGL: renderer: SVGA3D; build v: 2.1 Mesa 18.3.6 direct render: Yes
Audio: Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel
bus ID: 00:05.0 chip ID: 8086:2415
Sound Server: ALSA v: k4.19.0-6-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: 20.00 GiB used: 5.21 GiB (26.1%)
ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.00 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR
Partition: ID-1: / raw size: 20.00 GiB size: 19.56 GiB (97.81%) used: 5.21 GiB (26.7%) fs: ext4
dev: /dev/sda1
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/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 182 Uptime: 16m Memory: 1.95 GiB used: 866.6 MiB (43.4%) 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
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 12:59 pm
by dolphin_oracle
srq2625 wrote: Sun Oct 20, 2019 12:57 pm
- In VB 6.0 (and, also noticed in Beta 3 (I think))
- With the panel in "horizontal" mode at the top of the screen
- With or without the "Dont' reserve space on borders" item selected in the "Display" tab of the panel properties dialog
Any window that is expanded to full size will fill the screen with the window title bar hidden under the panel. To re-size the window, have to use the <Alt>-<Right_CLick> trick.
Further, the first default icon on the desktop (Manual) is partially obscured (covered) by the panel.
Is this intended behavior? Can this behavior be changed and I've yet to find the how-to to accomplish it?
Code: Select all
System: Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=18e6a9c0-faba-4e29-adaf-c90e6ab9a4e3 ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 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
CPU: Topology: Dual Core model: AMD Ryzen 7 2700 bits: 64 type: MCP arch: Zen+
family: 17 (23) model-id: 8 stepping: 2 microcode: 6000626 L2 cache: 1024 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 bogomips: 13574
Speed: 3394 MHz min/max: N/A Core speeds (MHz): 1: 3394 2: 3394
Vulnerabilities: 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 generic retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.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
resolution: 1600x1200~60Hz
OpenGL: renderer: SVGA3D; build v: 2.1 Mesa 18.3.6 direct render: Yes
Audio: Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel
bus ID: 00:05.0 chip ID: 8086:2415
Sound Server: ALSA v: k4.19.0-6-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: 20.00 GiB used: 5.21 GiB (26.1%)
ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.00 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 1.0 scheme: MBR
Partition: ID-1: / raw size: 20.00 GiB size: 19.56 GiB (97.81%) used: 5.21 GiB (26.7%) fs: ext4
dev: /dev/sda1
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/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 182 Uptime: 16m Memory: 1.95 GiB used: 866.6 MiB (43.4%) 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
make sure you are using the VBox graphics drivers (configurable in VB 6 on the Display tab of teh VB settings manager
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 1:11 pm
by hunghung
I'm also using VBox 6. You have to change it Graphic Controller from VMSVGA to VBoxSVGA. I choose VBoxSVGA because it is said to have better performance but still compatible with the old VboxVGA:
https://superuser.com/questions/1403123 ... virtualbox
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 1:23 pm
by dreamer
asqwerth wrote: Thu Oct 17, 2019 6:46 pm
dreamer wrote: Thu Oct 17, 2019 3:21 pm...
That's good and time-saving info. Is it possible to preserve /home in the installer if /home is located on the root partition?
It should from past experience. I haven't had time to install MX19 rc yet.
That's a cool feature!
(I haven't tried it, but could come in handy)
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 1:32 pm
by 8bit
That is a cool feature! I've tried it and it comes in handy.
8bit
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 2:02 pm
by srq2625
dolphin_oracle wrote: Sun Oct 20, 2019 12:59 pm
make sure you are using the VBox graphics drivers (configurable in VB 6 on the Display tab of teh VB settings manager
It was set to VMSVGA, changed it to VBoxSVGA. No change in behavior.
IIRC I saw this with B3 when installed on bare metal. I'm going to try that and see what I get.... More later.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 2:05 pm
by danielson
Jerry3904 wrote: Sun Oct 20, 2019 12:27 pm
I installed it, logged out and back in, clicked "Rescan catalog" on the Options tab--and it found 196 entries. It worked sometimes... It found GIMP but not galculator, for instance.
EDIT: no, I just mispelled galculator the first time.
Seems to work fine now.
That'll do it!
Have logged out twice, rebooted once - still no go.
Me thinking it doesn't do Dropbox folders...
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 2:25 pm
by Paul..
fehlix wrote: Sun Oct 20, 2019 9:27 am
Would you mind trying the new vcard=menu boot option and select the found nvidia card.
Hey fehlix, I tried the vcard=menu boot option...both with persistence and no persistence
-Detected the card correctly...yes!
-Then, I selected that card...
-Then unfortunately, I was sent to terminal login prompt, no gui
I looked in /blah/blah/Live-usb/Live-usb-storage/ but could not identify a log that made any sense
...tell me where to look for a log and I will post
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 2:32 pm
by fmc
I have a Thinkpad X200 with 4gb ram and a Crucial MX500 250gb SSD. MX 18.3 and MX 19 RC-1 are both installed. This laptop doesn't have bluetooth so I ran "apt-get remove --autoremove bluez". That reduced memory usage by about 50mb on both installs and didn't cause any complications.
One issue I'm having is that, according to Conky, 19 RC-1 uses 100-150 mb more ram than 18.3 (it also did this before the bluez removal). This occurs whether I've just logged in (500mb vs 350mb) or I've got several programs running. Maybe the new version of XFCE is causing this, or maybe it's just more ram being held in reserve but not being used. I don't know what the cause is, but sincethe X200 has fairly low memory (although I can remember when 4gb was considered "a lot"), I might stick with MX 18.3 for now.
The other thing is with the Appearance setting, specifically in the Style section. Navigation, say from Blackbird to Greybird-MX, is done via an up/down arrow key. On MX 18.3 this happens more or less immediately. On 19.3 it's delayed by a second or two, such that it "feels" sticky. Again, no big deal, and you might not experience this on a more powerful system. I just thought it was worth mentioning.
Overall, nice system. It ticks all the boxes on my personal preference list for what a desktop OS should be and do.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 2:33 pm
by dolphin_oracle
gtk3, and the buster kernels, due take up a little more ram then stretch based systems. the same could be said for the jump between jessie and stretch.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 2:56 pm
by srq2625
OK - Install on bare metal with the same results:
Code: Select all
System: Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=d7bb0493-a34d-489a-a400-a00b87c605d7 ro quiet splash
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B450-PLUS v: Rev X.0x serial: <filter>
UEFI [Legacy]: American Megatrends v: 0809 date: 02/28/2019
Battery: Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: Discharging
CPU: Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
family: 17 (23) model-id: 8 stepping: 2 microcode: 800820B L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 108584
Speed: 1335 MHz min/max: 1550/3400 MHz boost: disabled Core speeds (MHz): 1: 1324
2: 1406 3: 1314 4: 1331 5: 1375 6: 1375 7: 1375 8: 1375 9: 1339 10: 1371 11: 1374
12: 1375 13: 1375 14: 1371 15: 1315 16: 2567
Vulnerabilities: 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: disabled, RSB filling
Graphics: Device-1: NVIDIA GF106 [GeForce GTS 450] driver: nouveau v: kernel bus ID: 08:00.0
chip ID: 10de:0dc4
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1600x1200~60Hz, 1600x1200~60Hz
OpenGL: renderer: NVC3 v: 4.3 Mesa 18.3.6 direct render: Yes
Audio: Device-1: NVIDIA GF106 High Definition Audio driver: snd_hda_intel v: kernel
bus ID: 08:00.1 chip ID: 10de:0be9
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 0a:00.3 chip ID: 1022:1457
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 465.76 GiB used: 5.30 GiB (1.1%)
ID-1: /dev/sda vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB block size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: KC48 scheme: MBR
Partition: ID-1: / raw size: 30.00 GiB size: 29.40 GiB (98.01%) used: 5.17 GiB (17.6%) fs: ext4
dev: /dev/sda2
ID-2: /home raw size: 419.76 GiB size: 412.17 GiB (98.19%) used: 132.2 MiB (0.0%)
fs: ext4 dev: /dev/sda3
ID-3: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda1
Sensors: System Temperatures: cpu: 27.0 C mobo: N/A gpu: nouveau temp: 37 C
Fan Speeds (RPM): cpu: 0 gpu: nouveau fan: 1680
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 319 Uptime: 4m Memory: 15.66 GiB used: 925.1 MiB (5.8%) 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
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 3:03 pm
by ChrisUK
So, I did a test install (System info not relevant for this post) to test out the "Preserve Home" option, but when Home is on root, not a separate partition... a couple of points:
- Installer asks if you want to preserve Home - selected this option.
- When install nearly complete, you get a rather confusing Dialog - something like (I forgot to screenshot) "Home dir already exists" [reuse] [delete] [save] [cancel]
- I figured "reuse" was the correct choice, but why am I being asked again? I selected "save", as I thought some might select that instead of "reuse" as some might fear "reuse" would delete existing contents.
- After booting new install, faced with a standard Desktop, my Home was now a nice new clean Home... none of my settings or data etc. However, browsing I find my old Home exists, but with the ".001" extension. So I needed to delete say "/home/chris" and delete the extension from the Home I expected to find.
So, thinking about it, I guess the installer did actually do what I asked, but maybe not what I expected. Anyway, easy enough for me, but not, I suspect, for any newish users.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 3:07 pm
by Adrian
I figured "reuse" was the correct choice, but why am I being asked again? I selected "save", as I thought some might select that instead of "reuse" as some might fear "reuse" would delete existing contents.
It might need clarification. You preserve /home but that doesn't mean that automatically you are going to us the same username, so when you enter the user information if the username is the same as the one one /home it asks what you want to do: reuse the old me, save it to a .001 folder or delete (probably it should not offer delete option since you wanted to preserve it, cancel also, what it does when you cancel? So yes, there's room for improvement.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 3:11 pm
by BitJam
Paul.. wrote: Sun Oct 20, 2019 2:25 pm
fehlix wrote: Sun Oct 20, 2019 9:27 am
Would you mind trying the new vcard=menu boot option and select the found nvidia card.
Hey fehlix, I tried the vcard=menu boot option...both with persistence and no persistence
-Detected the card correctly...yes!
-Then, I selected that card...
-Then unfortunately, I was sent to terminal login prompt, no gui
I looked in /blah/blah/Live-usb/Live-usb-storage/ but could not identify a log that made any sense
...tell me where to look for a log and I will post
Thanks for testing!
When it boots correctly, what is the output of "inxi -Gxx"?
The relevant log file is /var/log/Xorg.0.log but this is not saved under ~/Live-usb-storage/live-logs/. Maybe I should fix that. But I don't think that file would help ATM.
Ah, yes. I think I know what went wrong. The problem is that since you installed the nvidia driver there is a battle between the nvidia driver and the nouveau driver for control over the Nvidia hardware. The vcard=menu does not resolve this conflict and hence the blank screen. When you used "xorg=nvidia", this did resolve the conflict and allowed the nvidia driver to take precedence.
ISTM one way out of this mess is to detect this situation (Nvidia card selected and both nivdia and nouveau drivers available) then offer a 2nd menu. What do you think of this idea?
In fact, even if there is just one video card, if it's Nvidia then we could still offer this nvidia/nouveau menu when both drivers are available.
We could also try defaulting to "nvidia" if both nvidia and nouveau drivers are detected.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 3:20 pm
by fehlix
BitJam wrote: Sun Oct 20, 2019 3:11 pm
Paul.. wrote: Sun Oct 20, 2019 2:25 pm
fehlix wrote: Sun Oct 20, 2019 9:27 am
Would you mind trying the new vcard=menu boot option and select the found nvidia card.
Hey fehlix, I tried the vcard=menu boot option...both with persistence and no persistence
-Detected the card correctly...yes!
-Then, I selected that card...
-Then unfortunately, I was sent to terminal login prompt, no gui
I looked in /blah/blah/Live-usb/Live-usb-storage/ but could not identify a log that made any sense
...tell me where to look for a log and I will post
Thanks for testing!
When it boots correctly, what is the output of "inxi -Gxx"?
The relevant log file is /var/log/Xorg.0.log but this is not saved under ~/Live-usb-storage/live-logs/. Maybe I should fix that. But I don't think that file would help ATM.
Ah, yes. I think I know what went wrong. The problem is that since you installed the nvidia driver there is a battle between the nvidia driver and the nouveau driver for control over the Nvidia hardware. The vcard=menu does not resolve this conflict and hence the blank screen. When you used "xorg=nvidia", this did resolve the conflict and allowed the nvidia driver to take precedence.
ISTM one way out of this mess is to detect this situation (Nvidia card selected and both nivdia and nouveau drivers available) then offer a 2nd menu. What do you think of this idea?
In fact, even if there is just one video card, if it's Nvidia then we could still offer this nvidia/nouveau menu when both drivers are available.
We could also try defaulting to "nvidia" if both nvidia and nouveau drivers are detected.
Sounds good. ... perhaps also checking powerstate via vgaswitcheroo in case nvidia is in Off state to allow it to turn On, and if in DynOff state user need to reboot to have be able to turn it On .. (after we first turned if Off , I know.. sounds weird) EDIT: that's only for those dual-cards where nvidia stays on powerOff
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 4:01 pm
by Paul..
BitJam wrote: Sun Oct 20, 2019 3:11 pm
When it boots correctly, what is the output of "inxi -Gxx"?
Glad to help as always...Booting from MX19rc installed on metal...here it is
Code: Select all
inxi -Gxx
Graphics: Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: ASUSTeK driver: nvidia v: 435.21
bus ID: 09:00.0 chip ID: 10de:1380
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21
direct render: Yes
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 5:14 pm
by gimbleguy
When I check for update, it shows I have one update. But after that it shows none.
https://youtu.be/-VSp4T0qhsY
I'm using Virtualbox.
HostOS: Windows 10
GuestOS: MXlinux 19RC1
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 5:22 pm
by dolphin_oracle
do an apt-get dist-upgrade.
someone else reported that package being held back. it shouldn't be, but I think the updater is flagging it because the update removes a different package and installs a new one.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 5:30 pm
by gimbleguy
still the same issue. dist-upgrade doesn't do any thing :(
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 5:32 pm
by micronaut
Can't create pp2p vpn connection:
WARNING **: 22:28:03.161: Could not load editor VPN plugin for “org.freedesktop.NetworkManager.pptp” (missing plugin file "/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-vpn-plugin-pptp-editor.so").
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 5:37 pm
by Srdjan
I think network-manager-pptp-gnome package holds that plugin.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 5:51 pm
by dolphin_oracle
gimbleguy wrote: Sun Oct 20, 2019 5:30 pm
still the same issue. dist-upgrade doesn't do any thing :(
I would like to see the output of
Code: Select all
sudo apt update && sudo apt dist-upgrade
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 5:52 pm
by Stevo
Is it too late to add pulseaudio-equalizer to the standard ISO?
https://packages.debian.org/en/buster/p ... -equalizer
It seems like a quite useful tool.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 6:05 pm
by gimbleguy
dolphin_oracle wrote: Sun Oct 20, 2019 5:51 pm
gimbleguy wrote: Sun Oct 20, 2019 5:30 pm
still the same issue. dist-upgrade doesn't do any thing :(
I would like to see the output of
Code: Select all
sudo apt update && sudo apt dist-upgrade
https://youtu.be/prwRQ3UMPlo
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 6:27 pm
by BV206
I'm having some kind of network problem now. MX19RC1 live USB. IPv6 doesn't work.
Ethernet connection to cable modem works properly on Xubuntu on the same PC/modem.
I don't know what info to provide or how to trobleshoot it. I deleted the connection and let it autocreate a new one but that didn't fix it.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 6:57 pm
by BV206
BV206 wrote: Sun Oct 20, 2019 6:27 pm
I'm having some kind of network problem now. MX19RC1 live USB. IPv6 doesn't work.
Ethernet connection to cable modem works properly on Xubuntu on the same PC/modem.
I don't know what info to provide or how to trobleshoot it. I deleted the connection and let it autocreate a new one but that didn't fix it.
Well IPv6 is working again after I deleted the connection and rebooted, set it to DHCP addresses only, and added IPv4 and IPv6 DNS servers.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 7:04 pm
by dolphin_oracle
well that's weird.
how about
Code: Select all
sudo apt install mx-apps chroot-rescue-mx
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 7:24 pm
by fehlix
dolphin_oracle wrote: Sun Oct 20, 2019 7:04 pm
well that's weird.
how about
Code: Select all
sudo apt install mx-apps chroot-rescue-mx
A manuall "apt install" might suffice to sorted the issue. A full upgrade cannot solve the Conflicts/Replaces/Provides relation ship issue as both packages chroot-rescue and chroot-rescue-mx have the same version number. I guess a higher version number of chroot-rescue-mx might have allowed to have mx-apps upgraded and removed the lower version of chroot-rescue.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 7:26 pm
by dolphin_oracle
fehlix wrote: Sun Oct 20, 2019 7:24 pm
dolphin_oracle wrote: Sun Oct 20, 2019 7:04 pm
well that's weird.
how about
Code: Select all
sudo apt install mx-apps chroot-rescue-mx
A manuall "apt install" might suffice to sorted the issue. A full upgrade cannot solve the Conflicts/Replaces/Provides relation ship issue as both packages chroot-rescue and chroot-rescue-mx have the same version number. I guess a higher version number of chroot-rescue-mx might have allowed to have mx-apps upgraded and removed the lower version of chroot-rescue.
hmm...ok.
but mx-apps depends on chroot-rescue-mx and not on the other. but I'll bump the version. doing mx-apps now anyway.
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 7:28 pm
by richb
Another thread on this, unfortunately. It was solve this way .
https://forum.mxlinux.org/viewtopic.php ... 82#p534682
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 7:43 pm
by winemaker
as i just replied to dolphin oracle in the other thread - i was hesitant to post in this thread due to thinking it was my system or my error so i started the new thread.
:-)
Re: MX-19 RC1 Feedback thread
Posted: Sun Oct 20, 2019 9:19 pm
by winemaker
ok an observation: i believe someone may have mentioned this before and maybe on the beta threads. the icons in the panel - all are clean and you see the icons with the black background. the clock module on 3 different laptops have a gray backgroundsquare that sticks out from all of the rest. i can live with and not a glitch that i know since the clock works but it is not like all of the others in the panel - they are icons with a solid black panel and the clock has the block of gray behind/around the icon. again - not a complaint.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 1:22 am
by gimbleguy
dolphin_oracle wrote: Sun Oct 20, 2019 7:04 pm
well that's weird.
how about
Code: Select all
sudo apt install mx-apps chroot-rescue-mx
This fixed it. Thank you, much appreciated
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 1:31 am
by scatman98
https://forum.mxlinux.org/viewtopic.php ... 54#p534254
referring post number 136
i resolved this issue by 1. disabling xhci hand off in bios and 2. enabling 64h/60h setting in bios.
no more freezing.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 2:47 am
by chrispop99
winemaker wrote: Sun Oct 20, 2019 9:19 pm
ok an observation: i believe someone may have mentioned this before and maybe on the beta threads. the icons in the panel - all are clean and you see the icons with the black background. the clock module on 3 different laptops have a gray backgroundsquare that sticks out from all of the rest. i can live with and not a glitch that i know since the clock works but it is not like all of the others in the panel - they are icons with a solid black panel and the clock has the block of gray behind/around the icon. again - not a complaint.
This is configurable; right-click the clock, select 'Properties', tick 'Set background colour', click the colour swatch, then use the eye-dropper tool to select the panel (or elsewhere) to make the clock background to be what you want.
Chris
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 3:10 am
by chrispop99
I'm still seeing the updater message mentioned up-thread:
Code: Select all
The following packages have been kept back:
mx-apps (19.09.01 => 19.10.02)
with today's new updates.
Chris
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 3:44 am
by PLX
Hi all, in the live usb maker , there is an advanced options to update (only the existing live usb) ...
It's useful to update my live usb mx19 beta3 to rc1?
thanks in advance :)
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 3:56 am
by asqwerth
chrispop99 wrote: Mon Oct 21, 2019 3:10 am
I'm still seeing the updater message mentioned up-thread:
Code: Select all
The following packages have been kept back:
mx-apps (19.09.01 => 19.10.02)
with today's new updates.
Chris
Same. Of course I can use Synaptic to get the update going, as I'd explained in an earlier post. But the question is how come neither sudo apt-get dist-upgrade or apt full-upgrade in the terminal will proceed with the update?
I thought the point of those 2 commands (and why they are different from plain apt-get upgrade or apt upgrade) was that they would proceed with the update even where existing packages were removed and new packages installed in the course of applying the update.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 4:13 am
by Iguana77
Eadwine Rose wrote: Sun Oct 20, 2019 11:16 am
You could start with MX Tools - quick system info :) That will help us know more about your computer.
Code: Select all
System: Host: mx Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26 2019
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: Hewlett-Packard product: HP ENVY 17 Notebook PC
v: 0592210000201920000620000 serial: <filter>
Mobo: Hewlett-Packard model: 159B v: 91.36 serial: <filter> BIOS: Hewlett-Packard
v: F.18 date: 09/27/2011
Battery: ID-1: BAT0 charge: 13.5 Wh condition: 57.4/57.4 Wh (100%)
model: Hewlett-Packard Primary status: Discharging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M315/M235 charge: Normal
status: Discharging
CPU: Topology: Quad Core model: Intel Core i7-2670QM bits: 64 type: MT MCP
arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 35119
Speed: 2042 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 798 2: 1135 3: 1862
4: 798 5: 1117 6: 800 7: 842 8: 798
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard
driver: radeon v: kernel bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: ati,modesetting,radeon unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A direct render: N/A
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Device-2: AMD Juniper HDMI Audio [Radeon HD 5700 Series] vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 3000
bus ID: 02:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 2000 bus ID: 03:00.0
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 931.52 GiB used: 10.45 GiB (1.1%)
ID-1: /dev/sda vendor: Seagate model: ST9500423AS size: 465.76 GiB
ID-2: /dev/sdb vendor: Seagate model: ST9500423AS size: 465.76 GiB
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
bus ID: 00:1f.2
Partition: ID-1: / size: 455.45 GiB used: 10.45 GiB (2.3%) fs: ext4 dev: /dev/sda1
Sensors: System Temperatures: cpu: 47.0 C mobo: N/A gpu: radeon temp: 46 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/bitmask.list
1: deb http://deb.leap.se/client release stretch
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.hu.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.hu.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb https://mega.nz/linux/MEGAsync/Debian_9.0/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/repo/ stretch main non-free
Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
Active apt repos in: /etc/apt/sources.list.d/stretch-backports.list
1: deb http://deb.debian.org/debian stretch-backports main
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 245 Uptime: 1h 05m Memory: 5.77 GiB used: 2.71 GiB (47.0%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.36
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 4:13 am
by darknetmatrix
PLX wrote: Mon Oct 21, 2019 3:44 am
Hi all, in the live usb maker , there is an advanced options to update (only the existing live usb) ...
It's useful to update my live usb mx19 beta3 to rc1?
thanks in advance :)
I don't think that you can update the beta3 to RC1, to the devs. correct me if i am wrong
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 4:16 am
by Iguana77
richb wrote: Sun Oct 20, 2019 11:23 am
Also please define what problem you are having with brightness.
It just doesn't work.
The keys on the keyboard do not respond, so brightess not working.
It's always the same level of lighting.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 4:25 am
by Eadwine Rose
darknetmatrix wrote: Mon Oct 21, 2019 4:13 am
PLX wrote: Mon Oct 21, 2019 3:44 am
Hi all, in the live usb maker , there is an advanced options to update (only the existing live usb) ...
It's useful to update my live usb mx19 beta3 to rc1?
thanks in advance :)
I don't think that you can update the beta3 to RC1, to the devs. correct me if i am wrong
You might be able to, but it won't be supported. There are quite a few changes between them, so it is not recommended to do that.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 4:57 am
by BitJam
PLX wrote: Mon Oct 21, 2019 3:44 am
Hi all, in the live usb maker , there is an advanced options to update (only the existing live usb) ...
It's useful to update my live usb mx19 beta3 to rc1?
You could. Pesistence and state information won't carry over. Most of the time to make a live-usb is in copying over the large linuxfs file so you won't save much time doing this.
My guess is it won't quite do exactly what you want since it has not been tested (at least not recently). But I say
"go for it!" See what happens and let us know. If it doesn't work then you can just run the program again without update enabled so it makes then entire live-usb from scratch. Let's see what happens. If that feature is not really useful then maybe we should remove it in future versions. I think I added it when I was doing development and testing. I did not expect it to end up in the gui.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 5:00 am
by asqwerth
Iguana77 wrote: Mon Oct 21, 2019 4:13 am
Eadwine Rose wrote: Sun Oct 20, 2019 11:16 am
You could start with MX Tools - quick system info :) That will help us know more about your computer.
Code: Select all
System: Host: mx Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26 2019
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: Hewlett-Packard product: HP ENVY 17 Notebook PC
v: 0592210000201920000620000 serial: <filter>
Mobo: Hewlett-Packard model: 159B v: 91.36 serial: <filter> BIOS: Hewlett-Packard
v: F.18 date: 09/27/2011
Battery: ID-1: BAT0 charge: 13.5 Wh condition: 57.4/57.4 Wh (100%)
model: Hewlett-Packard Primary status: Discharging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M315/M235 charge: Normal
status: Discharging
CPU: Topology: Quad Core model: Intel Core i7-2670QM bits: 64 type: MT MCP
arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 35119
Speed: 2042 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 798 2: 1135 3: 1862
4: 798 5: 1117 6: 800 7: 842 8: 798
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard
driver: radeon v: kernel bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: ati,modesetting,radeon unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A direct render: N/A
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Device-2: AMD Juniper HDMI Audio [Radeon HD 5700 Series] vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 3000
bus ID: 02:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 2000 bus ID: 03:00.0
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 931.52 GiB used: 10.45 GiB (1.1%)
ID-1: /dev/sda vendor: Seagate model: ST9500423AS size: 465.76 GiB
ID-2: /dev/sdb vendor: Seagate model: ST9500423AS size: 465.76 GiB
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
bus ID: 00:1f.2
Partition: ID-1: / size: 455.45 GiB used: 10.45 GiB (2.3%) fs: ext4 dev: /dev/sda1
Sensors: System Temperatures: cpu: 47.0 C mobo: N/A gpu: radeon temp: 46 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/bitmask.list
1: deb http://deb.leap.se/client release stretch
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.hu.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.hu.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb https://mega.nz/linux/MEGAsync/Debian_9.0/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/repo/ stretch main non-free
Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
Active apt repos in: /etc/apt/sources.list.d/stretch-backports.list
1: deb http://deb.debian.org/debian stretch-backports main
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 245 Uptime: 1h 05m Memory: 5.77 GiB used: 2.71 GiB (47.0%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.36
When you tried to use RC1, did you enable any non-default repo? I notice that in MX18, you enabled the stretch backports repo. If you still have your live USB stick for RC1, could you run it live and give us the Quick SYstem Info output from within MX19RC1?
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 5:11 am
by BitJam
Eadwine Rose wrote: Mon Oct 21, 2019 4:25 amYou might be able to, but it won't be supported. There are quite a few changes between them, so it is not recommended to do that.
Well the update feature in live-usb-maker updates almost everything so if it works as intended then PLX should be okay. The kernel, the live initrd, the linuxfs file, and even the bootloaders should get updated. This is very different from trying to update an installed systems.
Too Many Notes
At it's heart, the live system is very simple. There are bootloaders and then just three important files all in the /antiX/ directory (for antiX and MX):
Code: Select all
linuxfs the main file system
vmlinuz the kernel
initrd.gz programs to set up the main file system then switch to it
Since these will all get updated and even the bootloaders will get updated (thanks to fehlix), PLX should be fine. But on second thought there might be a problem with the legacy boot-loader. That may need to get re-installed.
With the three files listed above the live system is a single unit. If you replace those 3 files then you've done a complete upgrade except for the live bootloaders. But those should/might get updated too. It's possible there will be complaints but it will work anyway.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:04 am
by srq2625
OK - just wondering .... is
this going to be addressed or should I just drop it and live with it? Or, is this something that needs to be addressed up-stream (by the Xfce folks, for example)?
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:09 am
by JayM
srq2625 wrote: Mon Oct 21, 2019 6:04 am
OK - just wondering .... is
this going to be addressed or should I just drop it and live with it? Or, is this something that needs to be addressed up-stream (by the Xfce folks, for example)?
What are the "same results" mentioned in the post you linked to? I can't see what the problem is in those small images.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:16 am
by winemaker
chrispop thanks. never knew that. regarding clock backgrouns color.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:57 am
by Iguana77
asqwerth wrote: Mon Oct 21, 2019 5:00 am
Iguana77 wrote: Mon Oct 21, 2019 4:13 am
Eadwine Rose wrote: Sun Oct 20, 2019 11:16 am
You could start with MX Tools - quick system info :) That will help us know more about your computer.
Code: Select all
System: Host: mx Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26 2019
base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: Hewlett-Packard product: HP ENVY 17 Notebook PC
v: 0592210000201920000620000 serial: <filter>
Mobo: Hewlett-Packard model: 159B v: 91.36 serial: <filter> BIOS: Hewlett-Packard
v: F.18 date: 09/27/2011
Battery: ID-1: BAT0 charge: 13.5 Wh condition: 57.4/57.4 Wh (100%)
model: Hewlett-Packard Primary status: Discharging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M315/M235 charge: Normal
status: Discharging
CPU: Topology: Quad Core model: Intel Core i7-2670QM bits: 64 type: MT MCP
arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 35119
Speed: 2042 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 798 2: 1135 3: 1862
4: 798 5: 1117 6: 800 7: 842 8: 798
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard
driver: radeon v: kernel bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: ati,modesetting,radeon unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A direct render: N/A
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Device-2: AMD Juniper HDMI Audio [Radeon HD 5700 Series] vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 01:00.1
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 3000
bus ID: 02:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 2000 bus ID: 03:00.0
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 931.52 GiB used: 10.45 GiB (1.1%)
ID-1: /dev/sda vendor: Seagate model: ST9500423AS size: 465.76 GiB
ID-2: /dev/sdb vendor: Seagate model: ST9500423AS size: 465.76 GiB
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
bus ID: 00:1f.2
Partition: ID-1: / size: 455.45 GiB used: 10.45 GiB (2.3%) fs: ext4 dev: /dev/sda1
Sensors: System Temperatures: cpu: 47.0 C mobo: N/A gpu: radeon temp: 46 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/bitmask.list
1: deb http://deb.leap.se/client release stretch
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.hu.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.hu.debian.org/debian/ stretch main contrib non-free
2: deb http://security.debian.org/ stretch/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb https://mega.nz/linux/MEGAsync/Debian_9.0/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/repo/ stretch main non-free
Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
Active apt repos in: /etc/apt/sources.list.d/stretch-backports.list
1: deb http://deb.debian.org/debian stretch-backports main
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 245 Uptime: 1h 05m Memory: 5.77 GiB used: 2.71 GiB (47.0%) Init: SysVinit
runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.36
When you tried to use RC1, did you enable any non-default repo? I notice that in MX18, you enabled the stretch backports repo. If you still have your live USB stick for RC1, could you run it live and give us the Quick SYstem Info output from within MX19RC1?
Hi this is from live usb>
Code: Select all
System: Host: mx1 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: quiet splasht
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: Hewlett-Packard product: HP ENVY 17 Notebook PC
v: 0592210000201920000620000 serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 159B v: 91.36 serial: <filter> BIOS: Hewlett-Packard
v: F.18 date: 09/27/2011
Battery: ID-1: BAT0 charge: 57.4 Wh condition: 57.4/57.4 Wh (100%) volts: 12.5/10.8
model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Full
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M315/M235 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU: Topology: Quad Core model: Intel Core i7-2670QM bits: 64 type: MT MCP
arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F
L2 cache: 6144 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 35119
Speed: 798 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798
5: 798 6: 798 7: 798 8: 798
Vulnerabilities: Type: l1tf mitigation: PTE Inversion
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard driver: N/A
bus ID: 01:00.0 chip ID: 1002:68a8
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.6 compat-v: 3.0
direct render: Yes
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:1c20
Device-2: AMD Juniper HDMI Audio [Radeon HD 5700 Series] vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aa58
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel port: 3000
bus ID: 02:00.0 chip ID: 8086:4239
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 2000 bus ID: 03:00.0
chip ID: 10ec:8168
IF: eth0 state: down mac: <filter>
Drives: Local Storage: total: 1.36 TiB used: 1.52 GiB (0.1%)
ID-1: /dev/sda vendor: Seagate model: ST9500423AS size: 465.76 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: HPM1 scheme: MBR
ID-2: /dev/sdb vendor: Seagate model: ST9500423AS size: 465.76 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter>
rev: HPM1
ID-3: /dev/sdc type: USB vendor: Toshiba model: MQ01UBF050 size: 465.76 GiB
block size: physical: 512 B logical: 512 B rotation: 5400 rpm serial: <filter>
scheme: MBR
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
port: 4060 bus ID: 00:1f.2 chip ID: 8086.282a rev: 05
Partition: ID-1: / raw size: N/A size: 4.56 GiB used: 66.2 MiB (1.4%) fs: overlay
source: ERR-102
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: System Temperatures: cpu: 62.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/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 244 Uptime: 11m Memory: 5.77 GiB used: 904.4 MiB (15.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
Video Tweaks:
Detected possible Hybrid Graphics
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:26 am
by Jerry3904
JayM wrote: Mon Oct 21, 2019 6:09 am
srq2625 wrote: Mon Oct 21, 2019 6:04 am
OK - just wondering .... is
this going to be addressed or should I just drop it and live with it? Or, is this something that needs to be addressed up-stream (by the Xfce folks, for example)?
What are the "same results" mentioned in the post you linked to? I can't see what the problem is in those small images.
I think the question is the horizontal panel overlapping the icons. We tried to replicate that without much success in another thread, I seem to recall, but I will take a look again later today.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:34 am
by asqwerth
Iguana77 wrote: Mon Oct 21, 2019 6:57 am
Code: Select all
[MX18]
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard
driver: radeon v: kernel bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: ati,modesetting,radeon unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A direct render: N/A
Hi this is from live usb>
Code: Select all
[MX19]
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard driver: N/A
bus ID: 01:00.0 chip ID: 1002:68a8
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.6 compat-v: 3.0
direct render: Yes
Video Tweaks:
Detected possible Hybrid Graphics
I don't know enough about video graphics, but it looks like your machine selected and ran with the radeon driver in MX18, but it's using another driver by default in MX19.
You'll have to wait for the experts to give you advice on how to deal with your hybrid graphics.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 10:19 am
by Moishe
Great job! Installed quickly and runs beautifully.
I have noticed one issue; I can not change the default app used to open MP3 files. Clementine is the default but I can not change it to Audacious or any other app. After trying the "Open with" option in the file manager I tried changing the default using the Mime Type Editor but MP3 is not in the list of mime types!
Perhaps this is a bug or an error. It could also be that I don't know how to manually edit and change the settings! :)
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 10:24 am
by Jerry3904
Welcome to the Forum!
It is not as easy as it should be, and we have submitted an enhancement request to Xfce. For now:
--right-click any mp3 file > Open with
--highlight the app (e.g., Audacious) in the list that you want to use
--scroll down and check the box to make it the default for that type of file, then OK
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 10:28 am
by srq2625
JayM wrote: Mon Oct 21, 2019 6:09 am
srq2625 wrote: Mon Oct 21, 2019 6:04 am
OK - just wondering .... is
this going to be addressed or should I just drop it and live with it? Or, is this something that needs to be addressed up-stream (by the Xfce folks, for example)?
What are the "same results" mentioned in the post you linked to? I can't see what the problem is in those small images.
Sorry for the confusion - please see this (initial) post describing the issues I've seen -->
https://forum.mxlinux.org/viewtopic.php ... 70#p534586
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 10:31 am
by srq2625
Jerry3904 wrote: Mon Oct 21, 2019 7:26 am
JayM wrote: Mon Oct 21, 2019 6:09 am
srq2625 wrote: Mon Oct 21, 2019 6:04 am
OK - just wondering .... is
this going to be addressed or should I just drop it and live with it? Or, is this something that needs to be addressed up-stream (by the Xfce folks, for example)?
What are the "same results" mentioned in the post you linked to? I can't see what the problem is in those small images.
I think the question is the horizontal panel overlapping the icons. We tried to replicate that without much success in another thread, I seem to recall, but I will take a look again later today.
And over-lapping the title bar of windows expanded to full-size. See -->
https://forum.mxlinux.org/viewtopic.php ... 70#p534586
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 1:15 pm
by Friedrich
Not a problem; just not perfect:
During startup the lightdm-wallpaper appears for a moment, before bringing up the desktop
(This does not occur with 18.3)
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 1:25 pm
by Jerry3904
@srq2625: as I said, so far I have not been able to replicate this behavior, even with the Panel set to 75 width. If that only happens in a VM but is correct in an installation, it is not much of a problem for us.
We can return to your individual situation after we get MX-19 out the door. When that happens, start a separate thread showing us the steps to take from a clean install of MX-19 to reproduce the problem. Or file that as a bug report (click "Bugs" on the top right menu).
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 2:32 pm
by rs55
Friedrich wrote: Mon Oct 21, 2019 1:15 pm
Not a problem; just not perfect:
During startup the lightdm-wallpaper appears for a moment, before bringing up the desktop
(This does not occur with 18.3)
In the lightdm settings - if you uncheck the "user wallpaper" box - then it wont do that.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 5:08 pm
by komer
I'm using mx19-rc1 as "static persistent" usb stick. I set keyboard layout with Mx tools -> system_keyboard to Croatian and rebooted. It works in XFCE. But if I open console (ctrl+alt+F1), us keyboard is active. Is that normal?
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 5:52 pm
by fehlix
komer wrote: Mon Oct 21, 2019 5:08 pm
But if I open console (ctrl+alt+F1), us keyboard is active.
Can you try to adjust the console keyboard layout with
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 5:57 pm
by komer
fehlix wrote: Mon Oct 21, 2019 5:52 pm
Can you try to adjust the console keyboard layout with
that worked ... I will reboot and see if it is sticky :-)
EDIT: NOPE, it's not. Back to US keyboard after reboot.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:28 pm
by fehlix
komer wrote: Mon Oct 21, 2019 5:57 pm
fehlix wrote: Mon Oct 21, 2019 5:52 pm
Can you try to adjust the console keyboard layout with
that worked ... I will reboot and see if it is sticky :-)
EDIT: NOPE, it's not. Back to US keyboard after reboot.
can you show /etc/default/keyboard :
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:46 pm
by komer
fehlix wrote: Mon Oct 21, 2019 6:28 pm
can you show /etc/default/keyboard :
Code: Select all
┌─[demo@mx1]─[00:32:47]──────────────────────────────────────────[/etc/default]
└─> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="hr"
XKBVARIANT=""
XKBOPTIONS="terminate:ctrl_alt_bksp"
BACKSPACE="guess"
┌─[demo@mx1]─[00:45:31]──────────────────────────────────────────[/etc/default]
└─>
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:50 pm
by BitJam
komer wrote: Mon Oct 21, 2019 5:57 pmEDIT: NOPE, it's not. Back to US keyboard after reboot.
What is in the file /proc/cmdline? These are the boot parameters and one of them may be over-riding your "manual"
keyboard layout selection. For example, if lang= is used then we automatically set the language, timezone, keyboard layout, and maybe other things. If you have lang= and you don't like the keyboard layout then use the following cheats
kbd= kbopt= kbvar= to specify your keyboard layout, options, and variant.
I believe this works by us writing the file /etc/default/keyboard. This is used by X and the setupcon program magically uses this information to set the console keyboard layouts as well.
So I think there are two approaches. One is to specify the language and the keyboard information in live boot parameters that you save to the live bootloader. The other is to rely on persistence and not use any of these parameters because by so doing you will end up over-writing your persistent settings.
This has been tripping a lot of people up. Maybe there could be a better way. For example we could have a
lang_only= cheat that only sets the language. Or only sets the language for the early boot process. And if we see that persistence is enabled then we can automatically convert lang= to lang_only=.
I'm sorry this has been difficult for you. You're not the only one. We try very hard to make the live system as easy to configure as possible but it looks like the way we are handling the keyboard is not optimal.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 6:59 pm
by fehlix
komer wrote: Mon Oct 21, 2019 6:46 pm
fehlix wrote: Mon Oct 21, 2019 6:28 pm
can you show /etc/default/keyboard :
Code: Select all
┌─[demo@mx1]─[00:32:47]──────────────────────────────────────────[/etc/default]
└─> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="hr"
XKBVARIANT=""
XKBOPTIONS="terminate:ctrl_alt_bksp"
BACKSPACE="guess"
┌─[demo@mx1]─[00:45:31]──────────────────────────────────────────[/etc/default]
└─>
Right, so it show exact just one (and not two or more) keyboard layout, and this one shall default to the console keyboard.
Hmme not sure what's wrong ..
And when you run with Xfce Terminal
dooes it show somwthing like :
Code: Select all
model: pc105
layout: hr
variant:
options: terminate:ctrl_alt_bksp
Perhaps open console again Ctrl-Alt-F1
and
Code: Select all
sudo service keyboard-setup restart
The last line is actually what is done when you reboot, so it should set the console keyboard to the default defined within /etc/default/keyboard.
Actually I changed just now, the system-default console and run "service keyboard-setup restart"
a couple of times, and it always changed the console keyboard.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:04 pm
by fehlix
BitJam wrote: Mon Oct 21, 2019 6:50 pm
What is in the file /proc/cmdline? These are the boot parameters and one of them may be over-riding your "manual"
keyboard layout selection.
yes, of course, I forgot the boot parameter ...
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:07 pm
by komer
BitJam wrote: Mon Oct 21, 2019 6:50 pm
komer wrote: Mon Oct 21, 2019 5:57 pmEDIT: NOPE, it's not. Back to US keyboard after reboot.
What is in the file /proc/cmdline? These are the boot parameters and one of them may be over-riding your "manual"
keyboard layout selection.
Code: Select all
┌─[demo@mx1]─[00:54:57]─────────────────────────────────────────────────────[~]
└─> cat /proc/cmdline
persist_static tz=Europe/Berlin quiet splasht
┌─[demo@mx1]─[00:55:04]─────────────────────────────────────────────────────[~]
└─>
I don't think time zone should conflict with anything. Should I remove that option in live persistence settings?
So I think there are two approaches. One is to specify the language and the keyboard information in live boot parameters that you save to the live bootloader.
How would one do that? I didn't mess up a lot with those options. I just like to set basic stuff.
The other is to rely on persistence and not use any of these parameters because by so doing you will end up over-writing your persistent settings.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:38 pm
by fehlix
komer wrote: Mon Oct 21, 2019 7:07 pm
How would one do that?
With the BIOS-boot menu you add kbd=hr to the boot option line and select F8 "save", so the the next boot shall be have the kbd-boot option already.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:40 pm
by BitJam
komer wrote: Mon Oct 21, 2019 7:07 pm
Code: Select all
$ cat /proc/cmdline
persist_static tz=Europe/Berlin quiet splasht
Thanks!
Quick tip: If you want to copy and paste with fancy-prompts enabled, first run "prompt-tiny". This will create a tiny prompt. When you are done go back to your usual prompt with "prompt-fancy" or whatever variant you're using. This is a very useful and powerful feature of fancy-prompts.
I don't think time zone should conflict with anything.
I agree. It only controls the timezone and the automatic repo selection based on the timezone.
Should I remove that option in live persistence settings?
I don't think that will help.
Let me think about this. ISTM your settings are either not getting saved or they are getting clobbered during the live boot. H'mm. It's also possible that we are not running /etc/init.d/console-setup on your live boots. Yes, this may be the problem.
Even though I may be covering old ground, after you boot try runnig:
and see if that fixes things.
The problem is that I'm only running that during the live boot if one of the variables like lang= or kbd= are set. This is because setupcon can take a lot of time to run and if someone has a default system we waste a second or so of boot time for no good reason. But this doesn't work for people like you who have used persistence to change these settings and have not used a boot parameter.
Perhaps the mistake we made was ASSuming the results of setupcon were saved in files that were saved with persistence. But if it is only running programs like loadkeys then it needs to be run on every boot in order to work.
One quick fix would be to add a "setupcon" boot parameter that will cause setupcon to always run. We could also always run setupcon but that seems like a bad solution for all the people who don't need it.
PS: I think the "kbd=hr" fix fehlix proposed will also work.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 7:56 pm
by BitJam
komer wrote: Mon Oct 21, 2019 7:07 pmI just like to set basic stuff.
If running "sudo /bin/setupcon -k" fixes things then I have a solution that does not require you to change your boot parameters. If you are comfortable with the command line, I can give you simple instructions on how to implement it. but first we must see if the command above fixes the problem.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 8:43 pm
by komer
BitJam wrote: Mon Oct 21, 2019 7:56 pm
komer wrote: Mon Oct 21, 2019 7:07 pmI just like to set basic stuff.
If running "sudo /bin/setupcon -k" fixes things then I have a solution that does not require you to change your boot parameters. If you are comfortable with the command line, I can give you simple instructions on how to implement it. but first we must see if the command above fixes the problem.
Tnx for the tip.
"sudo /bin/setupcon -k" worked.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 9:20 pm
by BitJam
komer wrote: Mon Oct 21, 2019 8:43 pm"sudo /bin/setupcon -k" worked.
Excellent! I will try to get a fixed version to you. Are you okay with the command line?
Thank you for your help! I have a new policy that when people help out like this I send them an antiX sticker. If you would like a free sticker then please PM me your address.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 9:55 pm
by komer
BitJam wrote: Mon Oct 21, 2019 9:20 pm
komer wrote: Mon Oct 21, 2019 8:43 pm"sudo /bin/setupcon -k" worked.
Excellent! I will try to get a fixed version to you. Are you okay with the command line?
Thank you for your help! I have a new policy that when people help out like this I send them an antiX sticker. If you would like a free sticker then please PM me your address.
Command line is okay. Why not. I know how to type :D
Well, there are a lot of people that help around here. I didn't do much. I wish I could do more.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 10:27 pm
by Stevo
FWIW, I just updated a MX 19 Beta i386 install in virtualbox that had not been run in maybe a month. All 200+ updates went well--mx-apps updated to 19.10.3 without any hangups. The problems earlier in this thread seem to relate to the previous release, not the current one, so perhaps they aren't making sure they are up to date, or their mirrors are lagging.
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 10:30 pm
by BitJam
komer wrote: Mon Oct 21, 2019 9:55 pmCommand line is okay. Why not. I know how to type :D
Well, there are a lot of people that help around here. I didn't do much. I wish I could do more.
This may have to wait until tomorrow. I'm exhausted and the Debian sysvint circus confuses me. The sticker thing is because you reported a problem and then had the patience to help us track it down and (hopefully) fix it. I don't like having bugs. If it costs me a little money and a little time when there is a bug then that might help me create fewer of them. When I was teaching at University a million years ago I would give out gold stars to students who did really well. It's kind of silly but I think it works anyway. For you, it would be a reminder that your help is appreciated, perhaps turning a negative into a positive. A token of our appreciation. It might be silly but I think it works anyway.
Ah yes. It's very simple. I treat humans like I treat my dog. I reward behavior I want more of. I don't reward behavior I want less of. This seems simple and easy and obvious but it does not seem to be applied nearly enough. If I want more of something then I give a thumbs-up, a tip, a recommendation, a donation, or a sticker. I vote with my attention, my energy, and my wallet. This is how we make the world a better place.
/rant from exhaustion
Re: MX-19 RC1 Feedback thread
Posted: Mon Oct 21, 2019 11:41 pm
by komer
BitJam wrote: Mon Oct 21, 2019 10:30 pm
Ah yes. It's very simple. I treat humans like I treat my dog.
woof
.... okay. I surrender... :rollover:
when you implement the fix, I will test it. I gotta sleep now. It's 5:30am here. I'm way off my curfew. Have a good night BjtJam :-)
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 1:51 am
by JayM
I finally got around to installing MX-19RC1 on my primary computer (HP Pavilion DV6 laptop) today. The entire process took around 3 1/2 hours including installing a couple of apps from the test repo plus one flatpak app, adding a second panel, then setting up both panels the way they were in 18.3. That's not too bad: less than four hours every few years to reinstall after a new version of Debian Stable comes out. I can live with that. (BTW I was also doing other things, so if I'd dedicated the entire time to setting up 19RC1 it would have been faster.)
The only glitch was that the weather panel app was showing nighttime icons for some reason. I checked all of my time settings and the date and time in BIOS: all correct. The clock and conky were showing the correct time of 1PM too. I made a screen capture and wanted to circle the icon in red, so I had to install pinta which I had forgotten to do. By the time I'd added the red circle and saved the image prior to posting about the problem I happened to look at the panel again and the problem had come clear. Weird. I've never encountered that in any of the betas or the 32-bit version of RC1.
Anyway, all done. Most of my settings got saved except my latitude and longitude in fluxgui, and my location in the weather applet. Everything else is there: browser bookmarks and default home pages, my mailbox in Thunderbird, etc. So far, so good.
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 3:50 am
by Lupin
i just checked mx website. is MX19 officially released?
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 4:01 am
by monsieurzik
Just seen it too. It seems to be The day ^^
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 4:02 am
by cigam
My system is a Dell D630 (Intel T7250 CPU, Intel GMA965 chipset (ICH8) with integrated VGA (GMA X3100)). The new 19RC1 display very dark. I think the brightness on minimum. When I push the "brightness up/down" keys, I get a popup animation to brightens changed, but the display stay dark. The stable version (18) no such problem.
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 4:06 am
by JayM
cigam wrote: Tue Oct 22, 2019 4:02 am
My system is a Dell D630 (Intel T7250 CPU, Intel GMA965 chipset (ICH8) with integrated VGA (GMA X3100)). The new 19RC1 display very dark. I think the brightness on minimum. When I push the "brightness up/down" keys, I get a popup animation to brightens changed, but the display stay dark. The stable version (18) no such problem.
Please run MX Tools/Quick System Info, then right-click paste into a reply. (Quick System Info automatically copies the information to your clipboard, already formatted properly for pasting into the forum so all you have to do is a right-click/ paste, not a copy/paste.) Thanks.
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 4:08 am
by BitJam
komer wrote: Mon Oct 21, 2019 11:41 pm
when you implement the fix, I will test it. I gotta sleep now. It's 5:30am here. I'm way off my curfew. Have a good night BjtJam :-)
Wow. This Debian sysvinit code hurts my brain.
I've attached a small tarball called xtra.tgz. If you *copy* this tarball to the /antiX/ directory it will add my fix on every live boot. Don't unpack the tarball just copy it.
The plan is simple. If the file /etc/default/keyboard differs from the default version we ship on the iso file then we will call "setupcon -k". When it does this, it will say "Setting up live keyboard layout" on tty1. Sometimes messages fill the screen and scroll off the top. The cheat "tty1off" will disable login on tty1 which saves some lines.
You can also run the script manually after you've booted:
Code: Select all
sudo service setup-keyboard.sh start
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 4:23 am
by cigam
Code: Select all
System: Host: mx1 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: lang=hu_HU quiet splasht video=SVIDEO-1:d
Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19RC1_x64 patito feo October 15 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Portable System: Dell product: Latitude D630 v: N/A serial: <filter> Chassis:
type: 8 serial: <filter>
Mobo: Dell model: 0KU184 serial: <filter> BIOS: Dell v: A19 date: 06/04/2013
CPU: Topology: Dual Core model: Intel Core2 Duo T7250 bits: 64 type: MCP arch: Core Merom
family: 6 model-id: F (15) stepping: D (13) microcode: A4 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 7979
Speed: 798 MHz min/max: 800/2001 MHz boost: enabled Core speeds (MHz): 1: 798 2: 798
Vulnerabilities: Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Graphics: Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Dell Latitude D630
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a02
Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1440x900~60Hz
OpenGL: renderer: Mesa DRI Intel 965GM v: 2.1 Mesa 18.3.6 direct render: Yes
Audio: Device-1: Intel 82801H HD Audio vendor: Dell Latitude D630 driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:284b
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Broadcom Limited NetXtreme BCM5755M Gigabit Ethernet PCI Express
vendor: Dell driver: tg3 v: 3.137 port: 10c0 bus ID: 09:00.0 chip ID: 14e4:1673
IF: eth0 state: down mac: <filter>
Device-2: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945 v: in-tree:s
port: 10c0 bus ID: 0c:00.0 chip ID: 8086:4222
IF: wlan0 state: down mac: <filter>
Device-3: Dell Wireless 360 Bluetooth type: USB driver: btusb bus ID: 1-2:2
chip ID: 413c:8140
Drives: Local Storage: total: 584.81 GiB used: 25.6 MiB (0.0%)
ID-1: /dev/sda vendor: Kingston model: SV300S37A120G size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: BBF0 scheme: MBR
ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 410 size: 7.26 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: PMAP scheme: MBR
ID-3: /dev/sdc type: USB vendor: Samsung model: HM502JX size: 465.76 GiB block size:
physical: 512 B logical: 512 B serial: <filter> scheme: MBR
Partition: ID-1: / raw size: N/A size: 1.51 GiB used: 25.6 MiB (1.7%) fs: overlay
source: ERR-102
Sensors: System Temperatures: cpu: 58.0 C mobo: N/A sodimm: 51.0 C
Fan Speeds (RPM): cpu: 3391
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/buster buster main
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://mxrepo.com/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 187 Uptime: 1m Memory: 1.94 GiB used: 510.6 MiB (25.7%) 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
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 6:05 am
by srq2625
Jerry3904 wrote: Mon Oct 21, 2019 1:25 pm
@srq2625: as I said, so far I have not been able to replicate this behavior, even with the Panel set to 75 width. If that only happens in a VM but is correct in an installation, it is not much of a problem for us.
We can return to your individual situation after we get MX-19 out the door. When that happens, start a separate thread showing us the steps to take from a clean install of MX-19 to reproduce the problem. Or file that as a bug report (click "Bugs" on the top right menu).
@Jerry3904 : Understood. This does not happen just in a VM. Same exact behavior when installed on bare metal (as the only install on the computer). But, will re-address this after MX-19 is released.
Thanks
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 6:05 am
by Iguana77
asqwerth wrote: Mon Oct 21, 2019 7:34 am
Iguana77 wrote: Mon Oct 21, 2019 6:57 am
Code: Select all
[MX18]
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard
driver: radeon v: kernel bus ID: 01:00.0
Display: x11 server: X.Org 1.19.2 driver: ati,modesetting,radeon unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: N/A v: N/A direct render: N/A
Hi this is from live usb>
Code: Select all
[MX19]
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Hewlett-Packard driver: N/A
bus ID: 01:00.0 chip ID: 1002:68a8
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.3.6 compat-v: 3.0
direct render: Yes
Video Tweaks:
Detected possible Hybrid Graphics
I don't know enough about video graphics, but it looks like your machine selected and ran with the radeon driver in MX18, but it's using another driver by default in MX19.
You'll have to wait for the experts to give you advice on how to deal with your hybrid graphics.
Thank you for your reply. Whom can I ask for help?
Re: MX-19 RC1 Feedback thread
Posted: Tue Oct 22, 2019 6:19 am
by Jerry3904
With the release of MX-19, this thread is now closed. Please upgrade to Final before posting further feedback.
Release announcement:
https://forum.mxlinux.org/viewtopic.php?f=131&p=535116
Feedback thread:
https://forum.mxlinux.org/viewtopic.php?f=77&p=535117
