MX-17 Release Candidate 1 - Feedback

[kmathern]

I never thought I'd feel this way, but I'm hoping a MX-17 final release is not too soon. It'll take me 10+ hours to download RC1 on dial-up & I was having video related crashes with beta 3. So now I'm hoping I'll have enough time to post data on the crashes if they continue in RC1 --- and somebody will have time to resolve them before final. :snail:

Since you already have beta3 you can considerably reduce the amount you need to download if you download the b3_RC1 xdelta file or the zsync file. (or maybe that is what you were planning to do -- back when I had dialup it took a couple days to download 600 to 700 MB size isos)

[Adrian]

Running Live on my production system in sig, Power Manager is that yellow icon.

I see the same icon when I run the ISO in KVM, but on my laptop it doesn't show up (I created the USB with live-usb-maker if that makes a difference). So there's some variation somewhere.

Just tested, I don't see the icon in VirtualBox either.

[asqwerth]

Does it only appear on a non-laptop?

To be honest, I don't have much objection to it and don't really feel as if it's jarringly incongruous.

[Adrian]

Does it only appear on a non-laptop?

I guess so, I see it in KVN/Qemu and on a test desktop, not on the laptop or VirtualBox.

To be honest, I don't have much objection to it and don't really feel as if it's jarringly incongruous.

It's a bit out of place next to the other gray icons in system tray, it's also good to have some consistency between laptops/desktops.

[felicity]

Welcome to the Forum! Can you post the output of this from your current beta 3

Code: Select all

inxi -G

Thanks Jerry3904.

Code: Select all

$ inxi -G
Graphics:  Card: Intel 82915G/GV/910GL Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Mesa DRI Intel 915G x86/MMX/SSE2 version: 2.1 Mesa 13.0.6

Let me add that I fiddled with the graphics-related boot parameters. Here's the relevant part of the Grub Customizer Entry Editor window:

Code: Select all

echo  'Loading Linux 4.13.0-1-686-pae ...'
linux /boot/vmlinuz-4.13.0-1-686-pae root=UUID=087920e3-6bb0-4eab-bb4a-345e13e0d895 ro  vga=795 gfxsave video=1280x1024 failsafe

I did that because the MX-17 & antiX-17 standard kernels tend to boot into 1024x768 display resolution. And what's worse, they end up in some state that prevents me from changing the display resolution at all from this most unacceptable 1024x768. (I have no idea if these boot params are rational.)

But wait, there's more... Even though I can get the kernel into 1280x1024 resolution, I then change its default version of this resolution (for reasons explained later). The kernel likes to boot into video mode "1280x1024 (0x45) 108.879MHz" as below. But I force it into mode " 1280x1024 (0x9e) 108.000MHz" with a start-up script.

Code: Select all

$ sudo xrandr -q --verbose
Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
VGA1 connected 1280x1024+0+0 (0x9d) normal (normal left inverted right x axis y axis) 0mm x 0mm
...
  1280x1024 (0x9e) 108.000MHz +HSync +VSync +preferred
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1280x1024 (0x45) 108.879MHz -HSync +VSync
        h: width  1280 start 1360 end 1496 total 1712 skew    0 clock  63.60KHz
        v: height 1024 start 1025 end 1028 total 1060           clock  60.00Hz

I do this because I dual boot with XP (whose security vulnerabilities forced me into Linux) and XP chooses (I believe) this mode. Also, this mode (" 1280x1024 (0x9e) 108.000MHz") is the only one that my monitor's manual says it will accept (it's the standard VESA mode) at this resolution. This Acer AL1715 LCD monitor has a cranky module (the DAC?) and often refuses to do it's self-adjust thing successfully (especially when cold), so I want to stick with this one resolution.

[chrispop99]

Does it only appear on a non-laptop?

To be honest, I don't have much objection to it and don't really feel as if it's jarringly incongruous.

Yes, only on desktop machines.

It was reported during beta.

Chris

[felicity]

I never thought I'd feel this way, but I'm hoping a MX-17 final release is not too soon. It'll take me 10+ hours to download RC1 on dial-up & I was having video related crashes with beta 3. So now I'm hoping I'll have enough time to post data on the crashes if they continue in RC1 --- and somebody will have time to resolve them before final.

Since you already have beta3 you can considerably reduce the amount you need to download if you download the b3_RC1 xdelta file or the zsync file. (or maybe that is what you were planning to do -- back when I had dialup it took a couple days to download 600 to 700 MB size isos)

Yup, I sure did have to figure out that xdelta trick! (412 MiB/24 hrs @ 40 Kbps. But the darn (few remaining) ISP that support dial-up have taken to limiting us to only 10 hrs/day.

[Adrian]

Try zsync it can use the older file as base and download only the changes, for example to download the 64bit one:

Code: Select all

zsync -i INPUTFILE http://iso.mxrepo.com/Testing/MX-17/MX-17.RC1_x64.iso.zsync

where INPUTFILE can be the last Beta you have, if you have beta3 you can do:

Code: Select all

zsync -i MX-17.b3_x64.iso http://iso.mxrepo.com/Testing/MX-17/MX-17.RC1_x64.iso.zsync

You need to run this command in the folder where you have that ISO (or use the full path of the ISO).

[dolphin_oracle]

Does it only appear on a non-laptop?

To be honest, I don't have much objection to it and don't really feel as if it's jarringly incongruous.

Yes, only on desktop machines.

It was reported during beta.

Chris

its the default icon for power-manager (also appears inside the settings) via the chosen theme. it only appears if there is no battery.

[Jerry3904]

I remember that it was reported, didn't remember if it had been fixed.

I can turn off the switch that has it appear in NA from the settings, General tab: Appearance. Maybe we could consider doing that with a small script when not a laptop...?