Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

A few notes after installing MX17.1

Help for Current Versions of MX
Message
Author
User avatar
thomasl
Forum Novice
Forum  Novice
Posts: 14
Joined: Sun Feb 04, 2018 10:26 am

A few notes after installing MX17.1

#1 Post by thomasl » Sun May 13, 2018 8:59 am

Here are a few things I noticed during and after installing the MX17.1/64 bit/April2018 ISO. No particular order.
1. No option at all to encrypt part or all of the system.
2. MX USB Unmounter does nothing. No matter how many USB sticks and HDs I have mounted its window remains empty.
3. When calling persist-save or saving to rootfs during shutdown, I often get nonsensical values for the "Approx. transfer size", often a "w" or a "b" or even a "?".
4. The Close button in MX RemasterCC closes the window upon pressing the left mouse button while all other window buttons are only triggered upon releasing the mouse button.
5. Synaptic doesn't store the sizes of manually resized windows. This is pet-peeve of mine... apps which do not save window states or list column options.
6. MX Snapshot has an option to disable md5 generation. This seems to do nothing.
7. In Disk Manager, the second button from the left (at the bottom) reads "Demonter" which sounds like a French "unmount".
8. The resize margins of windows are way too small. I have found a solution but this should work better out of the box.

And finally a question about the sizes of the ttys (those I get with Alt-Ctrl-F[1-6]). 80x25 on my monitor is too small as a resolution so I tried to change that with a vga= parameter during boot. Does work for the the first part of the boot but then the screen is switched back to 80x25 and that is that. How can I do that?

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 21614
Joined: Wed Jul 19, 2006 6:13 am

Re: A few notes after installing MX17.1

#2 Post by Jerry3904 » Sun May 13, 2018 9:22 am

Thanks for the feedback. A few comments:

1. You get a checkbox to encrypt Home on Screen 7.
2. I have never seen that behavior, can you could post the output of this command so we can see your system values?

Code: Select all

inxi -F
3.
4.
5. It always does for me, so not sure what is happening on your system.
6.
7. That is a 10-year-old app that was first produced in French; has not been touched since 2011 but is still very useful. Don't know whether we could change that missing translation or not...
8. In Xfce, Alt-F8 jumps the cursor to the lower-right corner of the window that has focus. There are other threads on this topic, see especially this recent one: viewtopic.php?f=97&t=45145&p=446803.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, Kingston SSD 120 GB and WesternDigital 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB

User avatar
thomasl
Forum Novice
Forum  Novice
Posts: 14
Joined: Sun Feb 04, 2018 10:26 am

Re: A few notes after installing MX17.1

#3 Post by thomasl » Sun May 13, 2018 10:41 am

1. Hm... I must get new glasses:-/
2.

Code: Select all

System:    Host: montana Kernel: 4.15.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.1_x64 Horizon March 14, 2018
Machine:   Type: Laptop System: TOSHIBA product: TECRA R950 v: PT535E-09S04YUK serial: N/A
           Mobo: TOSHIBA model: TECRA R950 v: Version A0 serial: N/A BIOS: TOSHIBA v: Version 6.70
           date: 04/04/2013
CPU:       Topology: Dual Core model: Intel Core i5-3340M bits: 64 type: MT MCP L2 cache: 3072 KiB
           Speed: 1198 MHz min/max: 1200/3400 MHz Core speeds (MHz): 1: 1198 2: 1198 3: 1199 4: 1197
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
           Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz
           OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 3.3 Mesa 13.0.6
Audio:     Card-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel
           Sound Server: ALSA v: k4.15.0-1-amd64
Network:   Card-1: Intel Centrino Advanced-N 6235 driver: iwlwifi
           IF: wlan0 state: up mac: d8:f1:33:d1:59:93
Drives:    HDD Total Size: 281.48 GiB used: 38.51 GiB (13.7%)
           ID-1: /dev/mmcblk0 model: SU16G size: 14.84 GiB
           ID-2: /dev/sda model: KINGSTON_SA400S3 size: 223.57 GiB
           ID-3: /dev/sdb type: USB model: Ultra size: 57.91 GiB
Partition: ID-1: / size: 4.51 GiB used: 288.3 MiB (6.2%) fs: overlay dev: ERR-102
Sensors:   System Temperatures: cpu: 40.0 C mobo: N/A
           Fan Speeds (RPM): N/A
Info:      Processes: 208 Uptime: 2m Memory: 5.71 GiB used: 374.3 MiB (6.4%) Shell: zsh inxi: 3.0.06
5. It does store the size of the main window but not eg the size of the Repositories window, even not during the same run.
7. NBD, just thought I mention it.

EDIT re point 2: If USB sticks or USB HDs are already inserted into the USB slots upon boot I definitely get the empty Unmounter box (although those sticks have been automounted). However, when I unmount them via Thunar and then re-insert them they do show up in the Unmounter window. HTH.

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 21614
Joined: Wed Jul 19, 2006 6:13 am

Re: A few notes after installing MX17.1

#4 Post by Jerry3904 » Sun May 13, 2018 11:10 am

EDIT re point 2: If USB sticks or USB HDs are already inserted into the USB slots upon boot I definitely get the empty Unmounter box (although those sticks have been automounted). However, when I unmount them via Thunar and then re-insert them they do show up in the Unmounter window. HTH.
Thanks for that detail.
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, Kingston SSD 120 GB and WesternDigital 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB

User avatar
fehlix
Forum Regular
Forum Regular
Posts: 250
Joined: Wed Apr 11, 2018 5:09 pm

Re: A few notes after installing MX17.1

#5 Post by fehlix » Sun May 13, 2018 3:42 pm

thomasl wrote:
Sun May 13, 2018 10:41 am
.... although those sticks have been automounted...
Have those sticks been automated at boot via Thunar's automount or via Disk-Manager automount?
If the later, they got automounted via fstab-entries at boot time and would not be available
for MX-unmounter!
If they are get mounted or auto-mounted via Thunar the shall show up within MX-unmounter.
I do personally prefer to avoid Disk-Manager as I rather handle fstab-entries manually. :snail:

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15376
Joined: Fri Dec 15, 2006 8:07 pm

Re: A few notes after installing MX17.1

#6 Post by Stevo » Sun May 13, 2018 4:15 pm

As for the one-pixel wide window borders, some of the others available in the settings for "Window Manager" have fatter borders. Maybe we can rebuild the standard Arc theme to have those as well, since we already did that for the Arc-hdpi and Arc-xdpi custom MX themes. Is there anyone that really likes the one-pixel border?

User avatar
Richard
Posts: 1684
Joined: Fri Dec 12, 2008 10:31 am

Re: A few notes after installing MX17.1

#7 Post by Richard » Sun May 13, 2018 5:01 pm

If they do they must have sharper eyes and steadier hands than I do.
Greybird-MX17 is the best IMHO and it's sometimes rather squirrely and hard to catch.
6 or 8 pixels would be better, especially on the corners.
I need to dig out the GTK config file, again.
MX17.1: T430-2017, 8 GB RAM, 4.15.0-1-amd64, 119 SSD
antiX-/MX-171: AA1/Eee, 1 GB RAM, 4.15.0-1-686-pae, 149 HDD
DoubleCmd, LO604, Dropbox, Slimjet, mPDFed, Py3, CherryT, Vbox

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15376
Joined: Fri Dec 15, 2006 8:07 pm

Re: A few notes after installing MX17.1

#8 Post by Stevo » Sun May 13, 2018 6:04 pm

Some themes, like Arc, render all the theme elements from a vector svg file during the build, so configuring gtk won't change anything. You have to edit the svg file before the build to make the border elements fatter, and then that passes on to the final rendered bitmaps. Since svg files are text, the change in a newer MX version could be applied as a patch to the svg file.

User avatar
Richard
Posts: 1684
Joined: Fri Dec 12, 2008 10:31 am

Re: A few notes after installing MX17.1

#9 Post by Richard » Sun May 13, 2018 6:27 pm

Thanks for the tip. Now I know.
I'd already looked around and didn't find anything helpful.

Greybird-MX17 is much better than some of the others.
MX17.1: T430-2017, 8 GB RAM, 4.15.0-1-amd64, 119 SSD
antiX-/MX-171: AA1/Eee, 1 GB RAM, 4.15.0-1-686-pae, 149 HDD
DoubleCmd, LO604, Dropbox, Slimjet, mPDFed, Py3, CherryT, Vbox

skidoo
Forum Regular
Forum Regular
Posts: 780
Joined: Tue Sep 22, 2015 6:56 pm

Re: A few notes after installing MX17.1

#10 Post by skidoo » Sun May 13, 2018 6:34 pm

3. When calling persist-save or saving to rootfs during shutdown, I often get nonsensical values for the "Approx. transfer size", often a "w" or a "b" or even a "?"
confirming your observation ~~ I too occasionally see the mangled characters display for size values.
Not just at shutdown. It can also occur (semi-automatic persistence mode) when performing a manual persist-save operation.
FWIW, the persistence saving has been flawless, even when the garbled characters were displayed.
6. MX Snapshot has an option to disable md5 generation. This seems to do nothing.
idunno. When ticked, a myisoname-blablah.md5 file is created in addition to a myisoname-blablah.iso file in the output directory. I don't recall ever setting it to NOT create the md5 file. Really, I don't understand why the NOT option even exists.

Post Reply

Return to “MX Help”