Page 1 of 1

MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 4:27 am
by Jerry3904
Beta testing is all about the Community's involvement, so we hope to see lots of people posting in this thread.

The Announcement is here:

viewtopic.php?f=131&p=426693#p426693

If reporting a hardware issue, please include the output of

Code: Select all

inxi -F
.

Thanks--should be fun!

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 4:37 am
by Jerry3904
I'd like to keep these two topics separate, please:

1) The Users Manual has been revised for Sections 1-3 only. I will post a thread for its review.

2) The conkies in the default collection still need basic revision, and it would be much easier as we head toward Final if we use the existing thread for feedback.

Thanks.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 4:38 am
by chrispop99
When live or installed on a desktop machine, an ugly yellow Power Manager icon is shown in the Notification Area. This doesn't happen live or installed on a laptop. This seems counter-intuitive. Do we need the Power Manage to show in the NA at all? If so, can we replace the garish icon?

I understood we were going to default the User Image setting in LightDM GTK+ Greeter settings to 'On'?

(The default wallpaper/backgrounds for this release are great; nothing to offend the eye!)

Chris

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 4:42 am
by Jerry3904
an ugly yellow Power Manager icon is shown in the Notification Area
Not here installed on my testing laptop in sig; I just see the usual battery. Maybe on a desktop only?

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 5:06 am
by chrispop99
Jerry3904 wrote:
an ugly yellow Power Manager icon is shown in the Notification Area
Not here installed on my testing laptop in sig; I just see the usual battery. Maybe on a desktop only?
'This doesn't happen live or installed on a laptop.'
Screenshot.png
Chris

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 5:11 am
by Jerry3904
Why didn't you say so in the first place??!!

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 5:40 am
by CaputAlista
Thanks, you. it would be so kind in beta 3 or end to configure in the initr the write permissions for any user (guest) to the live folder as it was in the mx-15 version. :frown:
I boot the iso in live hd with an antix folder in a partition with grub4dos
First of all, Thanks.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 6:06 am
by azrielle
I have not had a chance to try this on something yet, but the included browser wasn't mentioned in the announcement...what version of FF? 56 or 57?
Thank You.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 6:15 am
by richb
azrielle wrote:I have not had a chance to try this on something yet, but the included browser wasn't mentioned in the announcement...what version of FF? 56 or 57?
Thank You.
It is 56. But likely next release will be 57. 57 is available in the test repo.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 6:51 am
by Kestrel
Jerry3904 wrote:Why didn't you say so in the first place??!!
He did. Hence the quotation marks in his second post.

But afaik any panel icon can be removed by the user if it offends their eyes. Thats why xfce is great.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 6:54 am
by Kestrel
richb wrote:
azrielle wrote:I have not had a chance to try this on something yet, but the included browser wasn't mentioned in the announcement...what version of FF? 56 or 57?
Thank You.
It is 56. But likely next release will be 57. 57 is available in the test repo.
And hopefully by that time a Firefox addon will be available to hide the titlebar. Not being able to hide the title bar is a fly in the ointment on FF57 for me.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:00 am
by richb
The diagonal line with two arrows at either end in the toolbar puts it full screen hiding titlebar, address bar. everything at the top. Moving your mouse to the screen top brings them back, back down hides them again.

EDIT: Or F11 toggle.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:02 am
by dolphin_oracle
chrispop99 wrote:
Jerry3904 wrote:
an ugly yellow Power Manager icon is shown in the Notification Area
Not here installed on my testing laptop in sig; I just see the usual battery. Maybe on a desktop only?
'This doesn't happen live or installed on a laptop.'

Screenshot.png

Chris
That is actually the default icon from Xfce4-power-manager in the icon set. if you have a battery, you get the charging or discharging icons, which are white.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:23 am
by Paul..
Jerry3904 wrote:
an ugly yellow Power Manager icon is shown in the Notification Area
Not here installed on my testing laptop in sig; I just see the usual battery. Maybe on a desktop only?
Confirm that the ugly yellow Power Manager is here on my HDD-installed desktop system (see sig).

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:28 am
by Jerry3904
Put it in Tracker, something we all have to remember to keep doing

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:42 am
by Paul..
Jerry3904 wrote:Put it in Tracker, something we all have to remember to keep doing
Done

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:48 am
by Jerry3904
Sorry, I meant I put it in Tracker. Wasn't giving an order... (Deleted the one I had put in earlier.)

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 8:29 am
by richb
Reminded I forgot last Friday's review. Probably best with the work to get b2 out. We will do a review this Friday.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 8:53 am
by stsoh
17b2 is awesome........ :number1:

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 9:47 am
by miker107
I have been using MX17 beta over the last couple days and love it. I have 2 machines running MX now, one Dell desktop running MX16 and now on this HP laptop MX17 has replaced my Solus system, and that says a lot because I was loving Solus. MX17 has been running flawless so for with no problems to report. I love all the subtle changes you guys have made from 16 to 17. I especially like the addition of the dd live usb creator, and MX-Tweak is a nice touch as well. Great job guys!
HP Pavilion G7
6 GB Memory
Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 10:44 am
by Be OK
Running it in VB so far it works and do look great.
I wonder do where you set the time on the desktop,its 12 hour time now and in whisper 24 hour.
Ok i admit not reading the new manual yet.It do look smooth and handy.
Any thing that need try out by a semi noob = old grumpy user with a memory brrr :bagoverhead:

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 12:27 pm
by mardi
Hi!
I have been using MX-16 for some time now, but never bothered to join this forum until now. I have one question of MX-17 beta 2. Will there be an upgrade path from MX-17 beta 2 to MX-17 final? I just tested this beta from usb-stick and it appeared to be very nice and functional already.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 12:53 pm
by asqwerth
I'm having a memory leakage problem (I think) with the MX-Conky app (or featherpad??).

Nothing but MX-conky and file manager are opened. When I click on the "edit" button within MX-conky, Featherpad opens the conky script and straight away, the main MX-conky app in the background doesn't get rendered/redrawn well. If I move featherpad away so it's not blocking or overlapping MX-conky, the latter doesn't get redrawn and will still show the bit of featherpad that was overlapping it. Same if I open whisker menu or Thunar and it covers MX-conky. If I close the other app, the "afterimage" of that app remains superimposed on MX-conky.

Once I close featherpad, all is well again.

I didn't turn compositing on so it's a fairly default setup of MX.

System: VB install, and as usual, I gave it 3.5GB RAM (this is my normal testing memory for MX, and should be enough for normal stuff) and 25GB virtual space.

Here's a screenshot of MX-conky with bits of various other windows left behind on it.
Screenshot.png

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:03 pm
by Max17
I was having an issue with MX b1 wireless connection with my Panda dongle. I am please to announce that this issue has been solved. My dongle now is connecting. Awesome and thank you all so much. MX is the best. Am very happy. :happy: Now I can install MX and never take it off my machine.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:05 pm
by timkb4cq
There will be no upgrade path from MX-16. The debian base has changed from Jessie to Stretch and following the debian upgrade directions will leave you with a badly mangled system given that debian uses systemd as its init system and MX uses sysvinit.
Whether there is even an upgrade path from MX-17 beta2 to Final depends on how many, and what kind of, changes we have to make during beta testing. I certainly wouldn't rely on it.

A clean install is recommended. You can use a utility like Aptik to make tweaking your new install easier. Aptik will back up the list of packages you installed on MX-16 so you can install them automatically on MX-17 (if they're available in the repos).

Which reminds me that I need to build Aptik for MX-17 before release...

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:09 pm
by BitJam
asqwerth wrote:When I click on the "edit" button within MX-conky, Featherpad opens the conky script and straight away, the main MX-conky app in the background doesn't get rendered/redrawn well. If I move featherpad away so it's not blocking or overlapping MX-conky, the latter doesn't get redrawn and will still show the bit of featherpad that was overlapping it.
This is not a memory leak problem. This is due to blocking the event loop in the app. I've complained about this privately in the past. It makes our programs look amateurish.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:12 pm
by mardi
Thanks. I have used Aptik before and it's a nice tool. So doing a clean install is not a problem for me... :)

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:27 pm
by vamsi
Add Antivirus to This release i think no distro is using antivirus in linux if we add one which will be useful to scan pendrives and other small stuff
and is it possible to add our image on whisker menu icon where a person pic is already in default on the whisker menu ?
Is it possible to add Startup screen for mx 17 like lubuntu branding instead of the default text appearing when we boot on the system?
Thanks.. :p :p

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:36 pm
by chrispop99
Fails to boot to X after Nvidia install.

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: desktop System: Gigabyte product: N/A serial: N/A
           Mobo: Gigabyte model: Z77P-D3 v: x.x serial: N/A
           BIOS: American Megatrends v: F8e date: 11/21/2012
CPU:       Dual core Intel Core i3-3220 (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 3300 MHz 1: 3303 MHz 2: 3303 MHz 3: 3303 MHz 4: 3303 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210]
           Display Server: x11 (X.Org 1.19.2 )
           drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Gallium 0.4 on NVA8 version: 3.3 Mesa 13.0.6
Audio:     Card-1 NVIDIA High Def. Audio Controller driver: snd_hda_intel
           Card-2 Intel 7 Series/C216 Family High Def. Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 90:2b:34:50:9c:79
Drives:    HDD Total Size: 254.1GB (2.7% used)
           ID-1: /dev/sda model: WDC_WD2500AAKX size: 250.1GB
           ID-2: USB /dev/sdb model: Flash_Disk size: 4.0GB
Partition: ID-1: / size: 6.2G used: 15M (1%) fs: overlay dev: N/A
           ID-2: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 47.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 186 Uptime: 5 min Memory: 442.2/7947.0MB Client: Shell (bash) inxi: 2.3.43 
Note: ddm-mx worked OK on this hardware in b1. Kernel problem perhaps?

Chris

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:37 pm
by Jerry3904
is it possible to add our image on whisker menu icon where a person pic is already in default on the whisker menu ?
I don't really understand what you mean. You can add any image to the icon that appears in the Panel, if that's what you mean: right-click > Properties, click on the image and navigate to your heart's content. The image will have to be pretty small to look right, I think, so just fool around until it is good for you.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:41 pm
by Adrian
I've complained about this privately in the past. It makes our programs look amateurish.
There's a very simple explanation to that, it's because they are written by amateurs. But if professional people or better coders would bother to contribute we'd gladly accept the contributions.

I forgot the add this->hide() and this->show() to hide the GUI while the foreground app is running. I forgot that because at some point we were trying to use xdg-open and that is not blocking so those commands would be irrelevant because this->show() would run immediately after issuing xdg-open command.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:47 pm
by chrispop99
vamsi wrote:Add Antivirus to This release i think no distro is using antivirus in linux if we add one which will be useful to scan pendrives and other small stuff
and is it possible to add our image on whisker menu icon where a person pic is already in default on the whisker menu ?
Is it possible to add Startup screen for mx 17 like lubuntu branding instead of the default text appearing when we boot on the system?
Thanks.. :p :p
You are asking three things at once; it's generally better to post each item separately.

To answer your first question - it's unlikely that an antivirus program will be added as it's not seen as needed. If you wish to add one for your specialised needs, clamav is available via Synaptic.

To answer your third question, on balance it was decided that the text displayed on boot is useful for bug tracing, so the decision was made to keep that, rather than a splash screen.

Chris

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 1:58 pm
by vamsi
chrispop99 wrote:
vamsi wrote:Add Antivirus to This release i think no distro is using antivirus in linux if we add one which will be useful to scan pendrives and other small stuff
and is it possible to add our image on whisker menu icon where a person pic is already in default on the whisker menu ?
Is it possible to add Startup screen for mx 17 like lubuntu branding instead of the default text appearing when we boot on the system?
Thanks.. :p :p
You are asking three things at once; it's generally better to post each item separately.

To answer your first question - it's unlikely that an antivirus program will be added as it's not seen as needed. If you wish to add one for your specialised needs, clamav is available via Synaptic.

To answer your third question, on balance it was decided that the text displayed on boot is useful for bug tracing, so the decision was made to keep that, rather than a splash screen.

Chris
Well i was Lazy to ask the questions individually ;) ;)
Okay you answered 2 questions and left 1 question that is it possible to change the default icon as in the image below to whatever pic i like

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:04 pm
by richb
asqwerth wrote:I'm having a memory leakage problem (I think) with the MX-Conky app (or featherpad??). etc .....

Here's a screenshot of MX-conky with bits of various other windows left behind on it.

Screenshot.png
Just a point of interest I do not see this when using compiz or the xfce compositor.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:09 pm
by chrispop99
vamsi wrote:Well i was Lazy to ask the questions individually ;) ;)
Okay you answered 2 questions and left 1 question that is it possible to change the default icon as in the image below to whatever pic i like
I'm currently testing three different things, on three different machines, other than this one, so I'm certainly not lazy!

Search the Forum; from memory there were too many problems caused when a user icon was added to Whisker, but I can't be sure.

Chris

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:12 pm
by dolphin_oracle
chrispop99 wrote:Fails to boot to X after Nvidia install.

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: desktop System: Gigabyte product: N/A serial: N/A
           Mobo: Gigabyte model: Z77P-D3 v: x.x serial: N/A
           BIOS: American Megatrends v: F8e date: 11/21/2012
CPU:       Dual core Intel Core i3-3220 (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 3300 MHz 1: 3303 MHz 2: 3303 MHz 3: 3303 MHz 4: 3303 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210]
           Display Server: x11 (X.Org 1.19.2 )
           drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Gallium 0.4 on NVA8 version: 3.3 Mesa 13.0.6
Audio:     Card-1 NVIDIA High Def. Audio Controller driver: snd_hda_intel
           Card-2 Intel 7 Series/C216 Family High Def. Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 90:2b:34:50:9c:79
Drives:    HDD Total Size: 254.1GB (2.7% used)
           ID-1: /dev/sda model: WDC_WD2500AAKX size: 250.1GB
           ID-2: USB /dev/sdb model: Flash_Disk size: 4.0GB
Partition: ID-1: / size: 6.2G used: 15M (1%) fs: overlay dev: N/A
           ID-2: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 47.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 186 Uptime: 5 min Memory: 442.2/7947.0MB Client: Shell (bash) inxi: 2.3.43 
Note: ddm-mx worked OK on this hardware in b1. Kernel problem perhaps?

Chris
Thanks for posting the log

Code: Select all

Building for 4.13.0-0.bpo.1-amd64
Building initial module for 4.13.0-0.bpo.1-amd64
Error! Bad return status for module build on kernel: 4.13.0-0.bpo.1-amd64 (x86_64)
yep, nvidia-driver failed to build. ( I need to trap those kinds of errors and report them.)

You could try the debian-backports option.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:14 pm
by vamsi
Jerry3904 wrote:
is it possible to add our image on whisker menu icon where a person pic is already in default on the whisker menu ?
I don't really understand what you mean. You can add any image to the icon that appears in the Panel, if that's what you mean: right-click > Properties, click on the image and navigate to your heart's content. The image will have to be pretty small to look right, I think, so just fool around until it is good for you.
Hello Jerry

is it possible to change the default icon as in the image below to whatever pic i like that is what i am asking

Thanks..

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:16 pm
by vamsi
Please remove some of old xfce themes which are ugly and add some more themes like adapta theme by the way new arc theme is awesome :number1:

Thanks..

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:17 pm
by chrispop99
dolphin_oracle wrote:
chrispop99 wrote:Fails to boot to X after Nvidia install.

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: desktop System: Gigabyte product: N/A serial: N/A
           Mobo: Gigabyte model: Z77P-D3 v: x.x serial: N/A
           BIOS: American Megatrends v: F8e date: 11/21/2012
CPU:       Dual core Intel Core i3-3220 (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 3300 MHz 1: 3303 MHz 2: 3303 MHz 3: 3303 MHz 4: 3303 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210]
           Display Server: x11 (X.Org 1.19.2 )
           drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x1024@60.02hz
           OpenGL: renderer: Gallium 0.4 on NVA8 version: 3.3 Mesa 13.0.6
Audio:     Card-1 NVIDIA High Def. Audio Controller driver: snd_hda_intel
           Card-2 Intel 7 Series/C216 Family High Def. Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 90:2b:34:50:9c:79
Drives:    HDD Total Size: 254.1GB (2.7% used)
           ID-1: /dev/sda model: WDC_WD2500AAKX size: 250.1GB
           ID-2: USB /dev/sdb model: Flash_Disk size: 4.0GB
Partition: ID-1: / size: 6.2G used: 15M (1%) fs: overlay dev: N/A
           ID-2: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 47.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 186 Uptime: 5 min Memory: 442.2/7947.0MB Client: Shell (bash) inxi: 2.3.43 
Note: ddm-mx worked OK on this hardware in b1. Kernel problem perhaps?

Chris
Thanks for posting the log

Code: Select all

Building for 4.13.0-0.bpo.1-amd64
Building initial module for 4.13.0-0.bpo.1-amd64
Error! Bad return status for module build on kernel: 4.13.0-0.bpo.1-amd64 (x86_64)
yep, nvidia-driver failed to build. ( I need to trap those kinds of errors and report them.)

You could try the debian-backports option.
debian-backports version failed also.

Chris

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:26 pm
by chrispop99
chrispop99 wrote:Fails to boot to X after Nvidia install.

Chris
I did a fresh install, used the PI to drop the kernel to 4.9, and then used ddm-mx to install the Nvidia driver.

It booted successfully, so I'm guessing it is a problem related to the 4.13 kernel.

Chris

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:44 pm
by dolphin_oracle
chrispop99 wrote:
chrispop99 wrote:Fails to boot to X after Nvidia install.

Chris
I did a fresh install, used the PI to drop the kernel to 4.9, and then used ddm-mx to install the Nvidia driver.

It booted successfully, so I'm guessing it is a problem related to the 4.13 kernel.

Chris
Probably...the classic problem with new kernels...dkms module building.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 2:48 pm
by BitJam
FWIW, there are patches to let the legacy nvidia 340.102 driver work with kernels up to 4.12: Fully Working Patch for Nvidia Driver 340.102and Linux Kernel 4.12. It might work for 4.13.

For more recent nvidia hardware: NVIDIA 384.59 Driver Is Playing Fine With Linux 4.13.

edit: 420.102 --> 320.102 --> 340.102

edit: Patches for linux 4.13: Patches (2 of them) for NVIDIA Driver 340.104 with Linux Kernel 4.13 and 4.14

It is obviously well past my naptime. Apologies to Adrian.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:08 pm
by Jerry3904
Please remove some of old xfce themes which are ugly
Or don't work...

That is a good reminder for us, we have intended to some theme-cleaning in the past but somehow keep forgetting.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:13 pm
by Stevo
We'll have to see if those legacy drivers are already patched in stretch-backports for the 4.13 kernel there.


I did an install in Virtual Box and upgraded to the 4.13.0-1 (4.13.13) kernel in our test repo from the stock bpo 4.13.0-0, and it's running fine. This is seen as a new package, not an upgrade, so the stock kernel is still installed, but I just installed the newer one via the linux-image and headers metapackages.The guest-dkms modules built automatically. One rather big difference is that the stock bpo kernel throws a TSC error at the start of boot and recommends a firmware upgrade when starting in VBox, but the newer kernel doesn't show this. This might be enough to make this the standard kernel, as well as its extended support for amdgpu and the higher kernel frequency...so let's test the new kernel.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:16 pm
by dolphin_oracle
Stevo wrote:We'll have to see if those legacy drivers are already patched in stretch-backports for the 4.13 kernel there.


I did an install in Virtual Box and upgraded to the 4.13.0-1 (4.13.13) kernel in our test repo from the stock bpo 4.13.0-0, and it's running fine. This is seen as a new package, not an upgrade, so the stock kernel is still installed, but I just installed the newer one via the linux-image and headers metapackages.The guest-dkms modules built automatically. One rather big difference is that the stock bpo kernel throws a TSC error at the start of boot and recommends a firmware upgrade when starting in VBox, but the newer kernel doesn't show this. This might be enough to make this the standard kernel, as well as its extended support for amdgpu and the higher kernel frequency...so let's test the new kernel.

chris tried the debian-backports hosted nvidia installation and they also failed.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:21 pm
by Stevo
vamsi wrote:Add Antivirus to This release i think no distro is using antivirus in linux if we add one which will be useful to scan pendrives and other small stuff
and is it possible to add our image on whisker menu icon where a person pic is already in default on the whisker menu ?
Is it possible to add Startup screen for mx 17 like lubuntu branding instead of the default text appearing when we boot on the system?
Thanks.. :p :p
I doubt we'll add any antivirus. Probably not any bootup screen, either--many devs like the text. Maybe we can add plymouth with debian-plymouth-manager to the package installer to make it easy to add and configure, but we don't presently don't have any custom MX plymouth theme, and we have to remember that Ubuntu plymouth themes won't work in MX/Debian, and plymouth just zips by in a second or two if you are booting from an SSD.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:29 pm
by anticapitalista
Does virtualbox build ok with the latest kernel used on beta2?

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:30 pm
by Stevo
dolphin_oracle wrote:
Stevo wrote:We'll have to see if those legacy drivers are already patched in stretch-backports for the 4.13 kernel there.


I did an install in Virtual Box and upgraded to the 4.13.0-1 (4.13.13) kernel in our test repo from the stock bpo 4.13.0-0, and it's running fine. This is seen as a new package, not an upgrade, so the stock kernel is still installed, but I just installed the newer one via the linux-image and headers metapackages.The guest-dkms modules built automatically. One rather big difference is that the stock bpo kernel throws a TSC error at the start of boot and recommends a firmware upgrade when starting in VBox, but the newer kernel doesn't show this. This might be enough to make this the standard kernel, as well as its extended support for amdgpu and the higher kernel frequency...so let's test the new kernel.

chris tried the debian-backports hosted nvidia installation and they also failed.
Ahh, OK. I know the main 375.82 Nvidia driver has no problem with the 4.13 kernel.

I just watched this Youtube review, I know you saw it: https://www.youtube.com/watch?v=rQWnFTIMDQo&t=1020s

where he adds the freaking upstream Debian repos to get one tiny upgrade that we already have in our test repo. Obviously this guy doesn't like to read the Fine Manual; horse-water-can't make drink problem...

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:31 pm
by Stevo
Virtualbox 5.1.30 and the 5.2 from Oracle are good with the 4.13 kernel.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:41 pm
by Stevo
The changelog for the 340xx Nivida drivers in Buster says they are patched for 4.14, so a backport should work. There's also a newer 304xx in Buster that should work, too.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:47 pm
by entropyfoe
With the nvidia driver not building on 4.13, I am wondering what my next step should be.

I have the nvidia card listed in the signature. I have the nvidia working on antix17 and MX17 b1. (375.82-1-deb90)

Is my card new enough that I would get a working nvidia driver built during an upgrade with the MX tool?

Or should I wait to try an MX 17 b2 install until some fix is in place.
I can't run the noveau driver, as X locks the mouse and keyboard every half day or so.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 3:58 pm
by dolphin_oracle
entropyfoe wrote:With the nvidia driver not building on 4.13, I am wondering what my next step should be.

I have the nvidia card listed in the signature. I have the nvidia working on antix17 and MX17 b1. (375.82-1-deb90)

Is my card new enough that I would get a working nvidia driver built during an upgrade with the MX tool?

Or should I wait to try an MX 17 b2 install until some fix is in place.
I can't run the noveau driver, as X locks the mouse and keyboard every half day or so.
stevo says that driver builds, so give it a try.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 4:18 pm
by Stevo
I am backporting the 304 and 340 legacy drivers from upstream Debian, which are advertised to build on the newer kernels, including even 4.14. I'll have them in a couple minutes, thanks to pbuilder...

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 4:42 pm
by entropyfoe
Thanks Dolphin_Oracle and stevo...

I will try it tonight and report the results.

As a side note...I have never seen in all my Mepis and MX history such a recent kernel as the basis of the distro.
Now, I am excited, because I need newer to support the Ryzen CPU and motherboard chip sets, so no problem for me.

But I wonder, are we in greater danger of instability with such a new kernel? Does this warrant extra testing in the beta and RC stage than say MX-16 did?

For me MX (and Mepis before) have always been known for stability and robustness. This along with this great community are the strong points of MX and antix.
I hope we do not lose the stability.

My antix 17 is very stable on the 4.10 kernel, now approaching 17 days uptime without crash or lock-up in two trials (8 days with rc1, and now 9 days with the final). I am hoping the 4.13 will be even better, though 4.14 will be a LTS kernel, and Phoronix says 4.15 will be the big increase in capability for Ryzen chips, with working temperature monitoring (finally !) and other goodies. The whole Ryzen thing is still in flux, with a new BIOS (1204) just out a week ago , promising "increase system stability". Since antix seems stable, I will hold off on the newer BIOS for now since Asus offers no change log.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 5:27 pm
by BitJam
entropyfoe wrote:As a side note...I have never seen in all my Mepis and MX history such a recent kernel as the basis of the distro.
Now, I am excited, because I need newer to support the Ryzen CPU and motherboard chip sets, so no problem for me.

But I wonder, are we in greater danger of instability with such a new kernel? Does this warrant extra testing in the beta and RC stage than say MX-16 did?
MX-15 used a 4.2.6 kernel which was released in mid-November. The 4.13 kernel was released in early September. There was a lot of last-minute Christmas-eve-eve coding to get that 4.2.6 kernel to work live. So compared to MX-15 we are being more conservative this time. The reason we pushed that recent kernel into MX-15 was the same reason we are pushing a recent kernel into MX-17: support for recently released hardware.

The biggest problems are the ones you are seeing in this thread: support for older (often close-sourced) drivers. I don't speak for the dev team but IMO it is almost always worthwhile to use a recent kernel if it supports the next generation of hardware that is already in the field. I'm not saying recent kernels are problem-free it's that not supporting recent hardware can be a big black-eye.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 5:30 pm
by dolphin_oracle
Also assuing we stick with 4.13, we will offer fallback kernels in mx-pi.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 5:48 pm
by richb
It's a balancing act isn't it. Indeed we must support newer machines with the newer kernels but not create problems for older machines which are still in the wild and I would guess are in higher numbers than the brand new ones. I would not want to hear that my five year old laptop or two year old desktop is not going to work anymore with a new MX release. One would say stay with the older version of MX. I do not roll that way.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 5:51 pm
by dr-kart
Stevo wrote:...main 375.82 Nvidia driver has no problem with the 4.13 kernel

Yes. Got no problem with it on 4.13 kernel.
Since backported nvidia driver appears to me bit newer I choose the one with 375.82-8~bpo9+1 name. Not from main repo. And what's the difference between those main's and bpo's versions?

Code: Select all

Graphics:  Card: NVIDIA GK106 [GeForce GTX 650 Ti] bus-ID: 01:00.0 chip-ID: 10de:11c6
           Display Server: x11 (X.Org 1.19.2 ) driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GTX 650 Ti/PCIe/SSE2
           version: 4.5.0 NVIDIA 375.82 Direct Render: Yes

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 6:08 pm
by huffy
The sound worked perfect with MX16 but doesn't work on MX17beta2 64 bit. Dell Latitude E5400. This is an issue with several new distros I've tried so not your problem exclusively. I tried the fallback 4.10 kernel and same. This beta works very well otherwise. I guess my puter is growing old. Thanks for a great system, I'll just keep using 16.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 6:16 pm
by dolphin_oracle
huffy wrote:The sound worked perfect with MX16 but doesn't work on MX17beta2 64 bit. Dell Latitude E5400. This is an issue with several new distros I've tried so not your problem exclusively. I tried the fallback 4.10 kernel and same. This beta works very well otherwise. I guess my puter is growing old. Thanks for a great system, I'll just keep using 16.
could you post "inxi -F" for this hardware? I'm surprised you have no sound.

Perhaps check alsamxier (now in Xfce Settings Manager) and see if the channels are muted or if its defaulting to an hdmi or some other port.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 6:24 pm
by caprea
Can confirm the 375.82-8~bpo9+1 nvidia builds perfectly against the 4.13.0-0.bpo.1-amd64 -kernel.

What didn't work at all is the grub-customizer. Did anyone else try?
It mixed all up and many lines were double in the bootscreen.
I had to reboot into antix and did an "sudo grub-install /dev/sda" to resolve.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:07 pm
by Jerry3904
I tried it, renaming the name of the default, rebooted, all good. Are you sure you waited until it was saved (takes a while)?

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:13 pm
by caprea
I didn't try to rename the default, I used the up-arrow,which worked in MX 16
O.K.,there are three systems with some different kernels, so I have many lines.
Sure waited until it was saved.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:19 pm
by tascoast
I've just installed MX-17 b2, Grub to MBR, and then customised Grub without issues being noted above.
(Wifi dongle was detected quickly during live boot, although was quite slow to activate upon booting from HDD. b1 seemed to require some re-plugging in, by comparison)

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:25 pm
by Stevo
The backported 304xx and 340xx Nvidia legacy drivers are now in the main MX 17 repo for testing with the 4.13 kernels. They are also in the testing repo for MX 15, since we don't have kernels in main that needs those ones.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 7:28 pm
by Stevo
dr-kart wrote:
Stevo wrote:...main 375.82 Nvidia driver has no problem with the 4.13 kernel

Yes. Got no problem with it on 4.13 kernel.
Since backported nvidia driver appears to me bit newer I choose the one with 375.82-8~bpo9+1 name. Not from main repo. And what's the difference between those main's and bpo's versions?

Code: Select all

Graphics:  Card: NVIDIA GK106 [GeForce GTX 650 Ti] bus-ID: 01:00.0 chip-ID: 10de:11c6
           Display Server: x11 (X.Org 1.19.2 ) driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GTX 650 Ti/PCIe/SSE2
           version: 4.5.0 NVIDIA 375.82 Direct Render: Yes
You can look at the package's changelogs at packages.debian.org to see what the differences are. They share the same original source version, so any changes will be Debian patches or packaging changes. Looks like most of it is stuff that won't affect us with Mesa 13, concerning many troubles with the Vulkan variant packages for Mesa 17 upstream--they messed up with a -4 in stretch-backports and had to fix it with yet another version.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 8:23 pm
by Jerry3904
Tried it on my Dell 700m, on which everything through the MX-16x series worked.

1) had to try the cheat "forcepae" to even start
2) once it entered runlevel 5, screen went completely black; waited a few minutes, then pressed the power button once, and it finished booting to the desktop.
3) wifi enabled and light on, but "device is not ready"
4) installed without problem
6) hung on exiting, had to power down manually << this usually happens
7) on rebooting without USB, saw that forcepae had been retained as a cheat -- very nice!
8) hung again part way through runlevel 5, pushing power button, Ctrl-C or Ctrl-Alt-F1 did not help.
9) finally used the power button to end
Too bad, this is the first MX Linux release I could not use on this machine. (BTW: same thing with B1)
Here is an inxi report from an earlier time:

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 3.16.0-4-586 i686 (32 bit) Desktop: Xfce 4.12.2
           Distro: MX-15-a3_386-mx Fusion 10 October 2015
Machine:   System: Dell product: Inspiron 700m v: -1
           Mobo: DELL SYSTEM model: Inspiron 700m v: Rev.A
           Bios: Phoenix v: A02 date: 02/01/05
CPU:       Single core Intel Pentium M (-UP-) cache: 2048 KB
           speed: 1600 MHz (max)
Graphics:  Card: Intel 82852/855GM Integrated Graphics Device
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1280x800@65.28hz
           GLX Renderer: Mesa DRI Intel 852GM/855GM x86/MMX/SSE2
           GLX Version: 1.3 Mesa 10.3.2
Audio:     Card Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller
           driver: snd_intel8x0
           Sound: Advanced Linux Sound Architecture v: k3.16.0-4-586
Network:   Card-1: Broadcom BCM4306 802.11b/g Wireless LAN Controller
           driver: b43-pci-bridge
           IF: wlan0 state: up mac: 00:0b:7d:18:92:4b
           Card-2: Broadcom BCM4401-B0 100Base-TX driver: b44
           IF: eth0 state: down mac: 00:0f:1f:b1:d6:13
Drives:    HDD Total Size: 48.0GB (4.7% used)
           ID-1: /dev/sda model: HTS548040M9AT00 size: 40.0GB
           ID-2: USB /dev/sdb model: Cruzer_Glide size: 8.0GB
Partition: ID-1: swap-1 size: 1.21GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 58.0C mobo: 43.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 121 Uptime: 10 min Memory: 229.7/1245.3MB
           Client: Shell (bash) inxi: 2.2.25
 

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 8:43 pm
by ldsemerchen
Beta2 MX Select Sound: When I choose another sound divice, it always sound from PC's speaker when I applied it and "Test current sound card". Beta1 is OK.

Image

Audio: Card-1 Intel 7 Series/C216 Family High Def. Audio Controller driver: snd_hda_intel
Card-2 C-Media Audio Adapter (Planet UP-100 Genius G-Talk) driver: USB Audio
Card-3 Microsoft LifeCam VX-3000 driver: USB Audio
Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.3-amd64-smp

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 9:06 pm
by dolphin_oracle
Just so folks are aware, at some point a lightdm upgrade is going to come down. during the upgrade, you may be asked what to do with a script in /etc/init.d/ (/etc/init.d/lightdm) . Please accept the change and let us know any ill effects.

this update should allow the run level 3 (boot code 3) to work to get to a console without starting X.

thanks, and remember...beta beta beta!

**edit***

This should work be default on the next iso build, but testers on the current b2 build will need to run

Code: Select all

sudo update-rc.d lightdm remove
sudo update-rc.d lightdm defaults
to be able to use the "3" boot code.

<MOD: corrected the typo (-rcd.) in the second command>

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 10:21 pm
by danielson
stsoh wrote:17b2 is awesome........ :number1:
Isn't it funny how words get twisted around over time?
Awe-some = Some awe ;
Awful = Full of awe.

Having jumped around for a long time from distro to distro, and most recently, to be greatly impressed with the outcome of Solus 3 and then Ubuntu Budgie (which i find fuller) but now... this MX-17 b2!
The latter has really put me in crisis!
Here's one more hand to lift that cup higher to cheer the devs on! :)

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 10:22 pm
by dolphin_oracle
danielson wrote:
stsoh wrote:17b2 is awesome........ :number1:
Isn't it funny how words get twisted around over time?
Awe-some = Some awe ;
Awful = Full of awe.

Having jumped around for a long time from distro to distro, and most recently, to be greatly impressed with the outcome of Solus 3 and then Ubuntu Budgie (which i find fuller) but now... this MX-17 b2!
The latter has really put me in crisis!
Here's one more hand to lift that cup higher to cheer the devs on! :)
that's pretty good company, thanks!

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 10:48 pm
by asqwerth
I'm totally not an Apple/iDevice person, but I'm sure the programmers in the Dev Team who came up with the new MX-iDevice-mounter app would like to hear users' feedback on the new app.

Does it work? Fully or partially?

Please let them know!

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 20, 2017 11:39 pm
by entropyfoe
:happy:
A very solid beta2. Looks good, and thanks to all the developers who made the last minute changes to the 4.13 kernel. I downloaded, md5 was good, so I burned it to a USB flash drive with the antix tool. Successful was reported.

I booted the beta2, and everything seemed to work in the live session. Conky looked weird with the time digits skewed.
So I installed over the beta1. All very fast. Rebooted, immediately used the nvidia driver installer to install the 375.82-8-bpo+1.

Another reboot, all went well.

As I mentioned the big clock conky is not my taste, but by just clicking around, I could change the conky to mx-asq-geekyTower which looks better to me. The point is , don't sweat the conky stuff, there are many options, easy to figure out, and you can always turn it off in the manager if you don't like it.

So far:
eth0 auto connects
sound works with no selection, just a mixe rvolume increase, youtube plays with sound, as well as wav and mp3 from disk in clementine.
data drive mounted with the disk manager.
Turned on xfce compositor.
suspend/resume works correctly, resumes in about 10 sec.
USB thumb drive mounts and unmounts correctly.
samba works OTB, with credentials I can see directories and files on my wife's win 7 machine. (This always amazes me how easily this works...in contrast I can't get connectshares working in antix)
Lots of desktop tweaks, and finally 2 synaptic updates, and 104 new packages added !

So far all looks like it is working. And now for stability testing. Can I equal 9 days recently on antix 17?

Code: Select all

 inxi -F
System:    Host: Ryzen Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: desktop Mobo: ASUSTeK model: PRIME X370-PRO v: Rev X.0x serial: N/A
           UEFI [Legacy]: American Megatrends v: 0902 date: 09/08/2017
CPU:       Hexa core AMD Ryzen 5 1600X Six-Core (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 3600 MHz 1: 3593 MHz 2: 3593 MHz 3: 3593 MHz 4: 3593 MHz
           5: 3593 MHz 6: 3593 MHz 7: 3593 MHz 8: 3593 MHz 9: 3593 MHz 10: 3593 MHz 11: 3593 MHz
           12: 3593 MHz
Graphics:  Card: NVIDIA GK208 [GeForce GT 710B]
           Display Server: x11 (X.Org 1.19.2 ) driver: nvidia Resolution: 1920x1080@60.00hz
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 version: 4.5.0 NVIDIA 375.82
Audio:     Card-1 Advanced Micro Devices [AMD] Device 1457 driver: snd_hda_intel
           Card-2 NVIDIA GK208 HDMI/DP Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card: Intel I211 Gigabit Network Connection driver: igb
           IF: eth0 state: up speed: 100 Mbps duplex:
Drives:    HDD Total Size: 2250.5GB (29.6% used)
           ID-1: /dev/nvme0n1 model: Samsung_SSD_960_EVO_250GB size: 250.1GB
           ID-2: /dev/sda model: WDC_WD2002FAEX size: 2000.4GB
Partition: ID-1: / size: 39G used: 5.4G (15%) fs: ext4 dev: /dev/nvme0n1p1
           ID-2: /home size: 73G used: 94M (1%) fs: ext4 dev: /dev/nvme0n1p3
           ID-3: swap-1 size: 17.83GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p2
Sensors:   System Temperatures: cpu: N/A mobo: N/A gpu: 38C
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 273 Uptime: 31 min Memory: 874.2/16047.5MB Client: Shell (bash) inxi: 2.3.43 

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 12:45 am
by vamsi
Jerry3904 wrote:
Please remove some of old xfce themes which are ugly
Or don't work...

That is a good reminder for us, we have intended to some theme-cleaning in the past but somehow keep forgetting.
Thanks !

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 2:37 am
by asinoro
zsync shows ok but still I have the 17.b1.
downloading from http://netcologne.dl.sourceforge.net/pr ... b2_x64.iso:
#################### 100.0% 1.8 kBps DONE

verifying download...checksum matches OK
used 1238364160 local, fetched 4396

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 4:58 am
by Jerry3904
MX Tweak, Theme tab.

Didn't know what "Nichi (horizontal)" was, and there is nothing in the Help file about it (which we have to update anyway). So I tried it, and got a vertical panel broken up into squares.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 5:00 am
by dolphin_oracle
Jerry3904 wrote:MX Tweak, Theme tab.

Didn't know what "Nichi (horizontal)" was, and there is nothing in the Help file about it (which we have to update anyway). So I tried it, and got a vertical panel broken up into squares.
yes, its for a horizontal panel...and the vertical one is for a vertical panel. its why there are 2.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 5:05 am
by Jerry3904
Selecting the "horizontal" one produces the vertical panel in the image

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 5:11 am
by dolphin_oracle
I'll tweak the names.

get it, tweak? (its too early, but the dog is needy).

horizonatl theme on vertical panel
horizontal.jpg
horizontal on a horizontal panel
horizontal_used_on_a_horizontal_panel.jpg
vertical on a vertical panel
vertical.jpg

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 5:18 am
by richb
Just got up, one sip of coffee, but your last post (horizontal on horizontal, horizontal on vertical) confused me totally.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 5:19 am
by dolphin_oracle
see if this clears things up.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 5:21 am
by richb
I don;t know if it was the second sip of coffee, but yes it does.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 5:28 am
by Jerry3904
Ahhhhh...yes it does.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 7:11 am
by richb
Another success data point.

I made a snapshot of my AMD graphics b2 desktop install, editing exclusion to allow the Inlel graphics driver. Put the ISO on a USB drive using antiX Live USB Maker. Plugged it in to a USB 2.0 port on my Acer laptop. Booted and made adjustments to dpi and font sizes for the smaller screen. It is vert fast and no glitches. Kudos to the dev team and Bitjam for the excellent antiX Live USB Maker and snapshot tool.

PS no inxi data as I am now off the laptop, but it is an Acer i5 Optimus, 15 inch screen 1366 x 768 with 8 GB ram and a 20 GB SSD.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 7:14 am
by huffy
dolphin_oracle wrote:
huffy wrote:The sound worked perfect with MX16 but doesn't work on MX17beta2 64 bit. Dell Latitude E5400. This is an issue with several new distros I've tried so not your problem exclusively. I tried the fallback 4.10 kernel and same. This beta works very well otherwise. I guess my puter is growing old. Thanks for a great system, I'll just keep using 16.
could you post "inxi -F" for this hardware? I'm surprised you have no sound.

Perhaps check alsamxier (now in Xfce Settings Manager) and see if the channels are muted

or if its defaulting to an hdmi or some other port.
Here it is, sorry I'm late

System: Host: mx1 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine: Device: portable System: Dell product: Latitude E5400 serial: N/A
Mobo: Dell model: 0D695C serial: N/A BIOS: Dell v: A19 date: 06/13/2013
Battery BAT0: charge: 86.6 Wh 213.8% condition: 40.5/86.6 Wh (47%)
CPU: Dual core Intel Core2 Duo P8700 (-MCP-) cache: 3072 KB
clock speeds: max: 2527 MHz 1: 2527 MHz 2: 2527 MHz
Graphics: Card: Intel Mobile 4 Series Integrated Graphics Controller
Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1280x800@60.05hz
OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express version: 2.1 Mesa 13.0.6
Audio: Card Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network: Card-1: Broadcom Limited NetXtreme BCM5761e Gigabit Ethernet PCIe driver: tg3
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: a4:ba:db:a2:3b:f0
Card-2: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter driver: wl
IF: wlan0 state: dormant mac: 42:be:34:45:5b:79
Drives: HDD Total Size: 250.1GB (2.8% used)
ID-1: /dev/sda model: WDC_WD2500BEVS size: 250.1GB
Partition: ID-1: / size: 112G used: 4.8G (5%) fs: ext4 dev: /dev/sda3
ID-2: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors: System Temperatures: cpu: 32.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 165 Uptime: 7 min Memory: 556.0/3911.0MB Client: Shell (bash) inxi: 2.3.43
manager@mx1:~

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 7:18 am
by huffy
Thanks for your help, would sure like to keep MX17 on.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 8:47 am
by twodogs
I'm running MX17 beta 2 in virtualbox and I love it. Really nice job and a fantastic distro.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 8:53 am
by dolphin_oracle
huffy wrote:Thanks for your help, would sure like to keep MX17 on.

check the default audio sink in pulse audio control. IIRC, that chipset sometimes defaults to HDMI if you have one.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 10:14 am
by peregrine
Beta 2 is very nice on this laptop - no problems. I have an iphone 8 and can test the iphone connect.
I connected with my android tablet first. Connects and folders are available. I can move items to it and download.
I can connect the iphone but see no folders. I can see that it mounts.

Code: Select all

$ inxi -F
System:    Host: asusmx17b2 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: laptop System: ASUSTeK product: X550LA v: 1.0 serial: N/A
           Mobo: ASUSTeK model: X550LA v: 1.0 serial: N/A
           UEFI: American Megatrends v: X550LA.403 date: 11/26/2013
Battery    BAT0: charge: 33.4 Wh 98.1% condition: 34.1/37.8 Wh (90%)
CPU:       Dual core Intel Core i5-4200U (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 2600 MHz 1: 2294 MHz 2: 2294 MHz 3: 2294 MHz 4: 2294 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.06hz
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 3.3 Mesa 13.0.6
Audio:     Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel
           Card-2 Intel Haswell-ULT HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: down mac: e0:3f:49:d6:e7:7d
           Card-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
           IF: wlan0 state: up mac: 54:35:30:21:fa:95
           Card-3: Atmel
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 500.1GB (3.4% used)
           ID-1: /dev/sda model: HGST_HTS545050A7 size: 500.1GB
Partition: ID-1: / size: 39G used: 4.3G (12%) fs: ext4 dev: /dev/sda13
           ID-2: /home size: 18G used: 217M (2%) fs: ext4 dev: /dev/sda14
           ID-3: swap-1 size: 12.58GB used: 0.00GB (0%) fs: swap dev: /dev/sda8
Sensors:   System Temperatures: cpu: 40.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 190 Uptime: 44 min Memory: 964.3/5855.3MB Client: Shell (bash) inxi: 2.3.43 

Screenshot-1.jpg

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 11:01 am
by Jerry3904
Did you ever see a "trust this..." dialog box on your phone?

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 11:19 am
by peregrine
yes, Trusted device came up and I selected to trust.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 11:35 am
by Jerry3904
Well that's a start. Did you try rebooting the phone after that?

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 12:31 pm
by peregrine
rebooted phone.
thunar closed and iphone connect open - rescan on iphone connect no trust dialog came up. clicked mount and got.
Error when getting information for file '/media/mx-idevice/80a967637f72a8bb21a14c9d521d6a1b28eea0ec/iPhone': No such file or directory.
Now the iphone connect window content is gone and a portion of firefox shows on it.
The icon in the panel for mount/unmount showed it unmounted.

I removed the usb for the phone, opened thunar and attached the phone again.

I now have an icon for the iphone in thunar and it shows to be mounted but no files. Iphone connect has only mount available and nothing happens when I click it. No option to unmount using it.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 1:27 pm
by Jerry3904
Thanks.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 1:56 pm
by huffy
huffy wrote:
dolphin_oracle wrote:
huffy wrote:The sound worked perfect with MX16 but doesn't work on MX17beta2 64 bit. Dell Latitude E5400. This is an issue with several new distros I've tried so not your problem exclusively. I tried the fallback 4.10 kernel and same. This beta works very well otherwise. I guess my puter is growing old. Thanks for a great system, I'll just keep using 16.
could you post "inxi -F" for this hardware? I'm surprised you have no sound.

Perhaps check alsamxier (now in Xfce Settings Manager) and see if the channels are muted

or if its defaulting to an hdmi or some other port.
SOLVED! The alsa settings were off. Thanks again, this beta is absolutely terrific!

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 2:23 pm
by Stevo
asinoro wrote:zsync shows ok but still I have the 17.b1.
downloading from http://netcologne.dl.sourceforge.net/pr ... b2_x64.iso:
#################### 100.0% 1.8 kBps DONE

verifying download...checksum matches OK
used 1238364160 local, fetched 4396
Of course, if we saw the complete command you used, the problem would be pretty obvious. :frown:

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 3:07 pm
by asinoro
Stevo wrote:
asinoro wrote:zsync shows ok but still I have the 17.b1.
downloading from http://netcologne.dl.sourceforge.net/pr ... b2_x64.iso:
#################### 100.0% 1.8 kBps DONE

verifying download...checksum matches OK
used 1238364160 local, fetched 4396
Of course, if we saw the complete command you used, the problem would be pretty obvious. :frown:
Both they had the same result.
zsync -i /media/Programs/MX-17.b1_x64.iso $(wget -nv --spider https://sourceforge.net/projects/mx-lin ... c/download 2>&1 | grep -Eo https.*iso.zsync | sed 's/https/http/')

zsync -i /media/Programs/MX-17.b1_x64.iso http://iso.mxrepo.com/Testing/MX-17/MX- ... .iso.zsync

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 3:39 pm
by Adrian
I'm using the last zsync command you posted to download the ISO, here's what it should look like:

Code: Select all

zsync -i MX-17.b1_x64.iso http://iso.mxrepo.com/Testing/MX-17/MX-17.b2_x64.iso.zsync
#################### 100.0% 775.4 kBps DONE      

reading seed file MX-17.b1_x64.iso: *********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************Read MX-17.b1_x64.iso. Target 81.2% complete.      
downloading from http://iso.mxrepo.com/Testing/MX-17/MX-17.b2_x64.iso:
##################-- 93.2% 636.2 kBps 2:16 ETA
and when is done you'll see:

Code: Select all

verifying download...checksum matches OK
used 1005977600 local, fetched 233401481
And the file should be in the folder you ran the command from.

If zsync doesn't work for you it might be a network problem, maybe a proxy or router between your computer and server... but I'm not sure.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 3:53 pm
by asinoro
Solved, there was no problem in the first place just I didn't use zsync for a lot time, the iso was made in my home folder.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 4:34 pm
by asinoro
Vbox responds fast, but after time when I open an app like boot repair or synaptic it stucks but this time there in not a lot cpu usage as it was with beta 1.

Edit. The cpu of the laptop do not stuck but it stuck again the vbox cpu.

Edit. Only if I use both processors of my system with the same memory settings it goes better but again with difficulties with MX 16.1 I don't have any problem.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 5:45 pm
by vortex
How is the general "wifi problem not connecting" going along ?

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 6:31 pm
by dolphin_oracle
vortex wrote:How is the general "wifi problem not connecting" going along ?
What general problem? If you are talking about stuff from alpha that's been addressed long ago.

The new kernel in b2 also addresses some usb wifi dongle issues.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 7:11 pm
by topcat
It has been requested for others to test the new iMountDevice app so I gave it a go with my MX-17b1 install to usb flash drive using my iphone 7.

It worked perfectly. I plugged in my usb cable with iMointDevice app open and selected rescan. It showed my phone and uuid. It brought up a trust window and I said yes, then my phone asked for my phone password which I provided. Then I chose to Mount in the iMointDevice app and thunar opened with a view of the files on the iphone 7. I opened the DCIM folder and copied my pictures from the iphone 7 and pasted to a new folder on mx-17b1. Worked like a charm - screenshot below:
Mount iDevice3.jpg
Great job devs...

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 7:36 pm
by peregrine
@topcat - since I had not been able to get my iphone to mount (iphone 8 MX beta 2), I followed your instructions. I still had a beta1 install and it worked there as it did for you. However it does not in beta2 for me.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 7:37 pm
by topcat
@peregrine : Wonder if the devs changed anything from beta 1 to beta 2?

If it helps I could download beta 2 tomorrow and try it out?

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 7:52 pm
by nathan2423
Minor icon issue:

Just installed beta two; switched panel to horizontal bottom. When left-clicking on Firefox or other icons on panel, select properties, buttons on right side of Launcher dialog are all grey - no content. Using Papirus Dark icons. Switching to Papirus light shows the content. So does Papirus itself. Switching back to Papirus dark turns them back to no content. Changing compositor does not seem to make a difference.

That's my only non-expected observation. No troubles whatsoever otherwise.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 8:43 pm
by dolphin_oracle
nathan2423 wrote:Minor icon issue:

Just installed beta two; switched panel to horizontal bottom. When left-clicking on Firefox or other icons on panel, select properties, buttons on right side of Launcher dialog are all grey - no content. Using Papirus Dark icons. Switching to Papirus light shows the content. So does Papirus itself. Switching back to Papirus dark turns them back to no content. Changing compositor does not seem to make a difference.

That's my only non-expected observation. No troubles whatsoever otherwise.
By any chance, did you use the "restore default panel" option at any point?

I think you have discovered a important bug! Should be easy to fix, thank you very much!

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 8:55 pm
by Stevo
dolphin_oracle wrote:
nathan2423 wrote:Minor icon issue:

Just installed beta two; switched panel to horizontal bottom. When left-clicking on Firefox or other icons on panel, select properties, buttons on right side of Launcher dialog are all grey - no content. Using Papirus Dark icons. Switching to Papirus light shows the content. So does Papirus itself. Switching back to Papirus dark turns them back to no content. Changing compositor does not seem to make a difference.

That's my only non-expected observation. No troubles whatsoever otherwise.
By any chance, did you use the "restore default panel" option at any point?

I think you have discovered a important bug! Should be easy to fix, thank you very much!
Are you using a dark or light theme? Papirus Dark has light-colored icons meant for use on a dark theme, the standard Papirus has darker icons.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 9:19 pm
by Jerry3904
topcat wrote:@peregrine : Wonder if the devs changed anything from beta 1 to beta 2?

If it helps I could download beta 2 tomorrow and try it out?
That would be very helpful.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 9:24 pm
by topcat
OK Jerry3904, I'll give it a shot tomorrow on b2.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 21, 2017 9:35 pm
by dolphin_oracle
Stevo wrote:
dolphin_oracle wrote:
nathan2423 wrote:Minor icon issue:

Just installed beta two; switched panel to horizontal bottom. When left-clicking on Firefox or other icons on panel, select properties, buttons on right side of Launcher dialog are all grey - no content. Using Papirus Dark icons. Switching to Papirus light shows the content. So does Papirus itself. Switching back to Papirus dark turns them back to no content. Changing compositor does not seem to make a difference.

That's my only non-expected observation. No troubles whatsoever otherwise.
By any chance, did you use the "restore default panel" option at any point?

I think you have discovered a important bug! Should be easy to fix, thank you very much!
Are you using a dark or light theme? Papirus Dark has light-colored icons meant for use on a dark theme, the standard Papirus has darker icons.
I do believe the restore/backup/default feature of MX-Tweak is broke. working on a fix now.

**and fix sent to Tim, at least I hope its fixed**

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 12:31 am
by handydan918
After a long absence here, I was unable to get Debian to install on a Mac I was given, so I immediately thought of MX.

17 is up and running on an early 2011 13" Macbook Pro, even the damnable BCM wireless.

Great work, guys.
I haven't really shaken this thing down, yet, but time will tell.

Code: Select all

inxi -F
System:    Host: mx1 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: laptop System: Apple product: MacBookPro8 1 v: 1.0 serial: N/A
           Mobo: Apple model: Mac-94245B3640C91C81 v: MacBookPro8 1 serial: N/A
           UEFI: Apple v: MBP81.88Z.0047.B2C.1510261540 date: 10/26/15
Battery    BAT0: charge: 33.4 Wh 70.5% condition: 47.4/62.9 Wh (75%)
CPU:       Dual core Intel Core i5-2415M (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 2900 MHz 1: 2294 MHz 2: 2294 MHz 3: 2294 MHz 4: 2294 MHz
Graphics:  Card: Intel 2nd Generation Core Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1280x800@60.22hz
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile version: 3.3 Mesa 13.0.6
Audio:     Card Intel 6 Series/C200 Series Family High Def. Audio Controller
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card-1: Broadcom Limited NetXtreme BCM57765 Gigabit Ethernet PCIe driver: tg3
           IF: eth0 state: down mac: c8:2a:14:02:01:65
           Card-2: Broadcom Limited BCM4331 802.11a/b/g/n driver: wl
           IF: wlan0 state: up mac: e0:f8:47:0e:99:6c
Drives:    HDD Total Size: 320.1GB (2.8% used)
           ID-1: /dev/sda model: Hitachi_HTS54503 size: 320.1GB
Partition: ID-1: / size: 20G used: 4.3G (24%) fs: ext4 dev: /dev/sda4
           ID-2: /home size: 123G used: 105M (1%) fs: ext4 dev: /dev/sda6
           ID-3: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 54.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 5:19 am
by vamsi
Please add some popular themes to package manager like adapta and macos theme and like that add some popular themes in MX package installer so that it will be easy for us to install them. I think no other distro has this type of feature which will be very useful
Thanks..

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 5:46 am
by tascoast
I have tested Bluetooth connectivity using a hearing aid bluetooth connector, a relatively high end (expensive anyway!) device.
The test involved pairing EasyTek* with Bluetooth Manager and testing persistence after restarting system
------------(*a Siemens thingy that enables bluetooth audio streaming to hearing devices)
Setting VLC to use EasyTek to stream movie audio to ears
------------(a nice feature for me, as with phone calls using Android smart phone)
Confirming if Easytek would reconnect after leaving and returning to broadcast range
Confirming if VLC would remember device and default to it in Audio/Audio Device after restarting system.
Passed :happy:

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 7:02 am
by Jerry3904
Good to *hear,* thanks. We had a problem there in earlier testing, so it's nice to know it's working now.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 7:03 am
by Jerry3904
add some popular themes in MX package installer so that it will be easy for us to install them
That's a good suggestion, and we will look into it.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 7:11 am
by vamsi
Jerry3904 wrote:
add some popular themes in MX package installer so that it will be easy for us to install them
That's a good suggestion, and we will look into it.
Thank you ..

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 12:37 pm
by asqwerth
Brother network printer MFC-9320CW - the correct colour printer driver is found in the Printer Config program. Works fine.
Scanner function - again does not work OOTB as detailed in the MX Wiki here: https://mxlinux.org/wiki/hardware/scanners#Brother

/usr/lib/sane folder not created by default in the iso.

I followed the instructions in wiki to create said folder and the 6 symlinks, and confirm that the solution works for MX17 as well.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 1:19 pm
by JLS727
I ran into a problem when trying to test Beta 2 on my Dell Latitude 3160. MX-17 Beta 2 will not boot from a usb drive.
It gives the following info:

Loading hardware specific modules ...
Scan usb,cd devices. Look for boot file(s) antiX/linuxfs
Retry for 15 seconds ...
Filter devices /dev/sdb1 /dev/sdb
Mounted boot device. Mounted device /dev/sdb1 at live/boot-dev
Initializing random number generator ...
Saving random seed
live-usb-save: Restore state information
Reset file /etc/adjtime
live-init: Localizing/configuring X-Windows
Creating issue file for MX 17.b2 (Horizon) 64 it
Possibly adding swap partitions to fstab

After the above the it hangs with a blinking cursor and just sits there.

I have MX-16.1 installed on this Dell laptop and it runs fine except that it will not recognize my sd card reader.
This laptop has 8 gb memory and a 128 gb ssd drive and I'm dual booting with Windows 10 pro. I hope this helps.
Thanks for all the work on MX 17.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 1:29 pm
by chrispop99
Using the Nvidia driver installer in an earlier test resulted in a failure to boot to a graphical environment.

Following Stevo's updating of the drivers, I can confirm they now work as expected.

Chris

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 2:08 pm
by topcat
In Post # 103 in this thread I posted how I could access files on my iphone7 using the new MX-iMountDevice app on MX-17b1 64bit running installed to a usb flash drive.

Peregrine, in Post # 89, tried this on MX-17b2 64 bit without success. She then tried it on MX-17b1 and it worked.

As per Jerry3904's request, I created a Live USB of MX-17b2 64 bit and booted it up and tried the MX-iMountDevice app and it worked the same as in b1 for me on my iphone7.

So in summary, MX17b1 and b2 work fine for me accessing my iphone7 using the new app MX-iMountDevice.
For peregrine, her iphone8 works in b1 but not in b2.

If I can provide any other info that would be helpful, let me know...

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 2:25 pm
by Jerry3904
Great, thanks. I have access to a 6 and 6S here in Minneapolis, and will test them later.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 2:52 pm
by Stevo
vamsi wrote:Please add some popular themes to package manager like adapta and macos theme and like that add some popular themes in MX package installer so that it will be easy for us to install them. I think no other distro has this type of feature which will be very useful
Thanks..
We have heard that some of the included themes no longer work well in MX 17, so we may replace them on the ISO with popular themes such as adapta anyway. Any more suggestions?

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 3:00 pm
by Stevo
chrispop99 wrote:Using the Nvidia driver installer in an earlier test resulted in a failure to boot to a graphical environment.

Following Stevo's updating of the drivers, I can confirm they now work as expected.

Chris
Thanks, we still need testing of the newer 4.13.13 (4.13.0-1) kernel in testing--it has a couple advantages over the bpo one and would be better as the default.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 3:33 pm
by richb
Installed the 4.13.13 (4.13.0-1) kernel. I do not see nay issues. I installed VB from MXPI without a problem. Let me know if there is something specific that I should test.

Code: Select all

System:    Host: mx1 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: desktop System: Gigabyte product: N/A serial: N/A
           Mobo: Gigabyte model: F2A68HM-H v: x.x serial: N/A UEFI: American Megatrends v: FB date: 04/22/2015
Battery    hidpp__0: charge: N/A condition: NA/NA Wh
CPU:       Quad core AMD A8-7600 Radeon R7 10 Compute Cores 4C+6G (-MCP-) cache: 8192 KB
           clock speeds: max: 3100 MHz 1: 1400 MHz 2: 1400 MHz 3: 1400 MHz 4: 1400 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
           Display Server: x11 (X.Org 1.19.2 ) drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Gallium 0.4 on AMD KAVERI (DRM 2.50.0 / 4.13.0-1-amd64, LLVM 3.9.1)
           version: 4.3 Mesa 13.0.6
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio Controller driver: snd_hda_intel
           Card-3 Logitech Webcam Pro 9000 driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.13.0-1-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: down mac: 40:8d:5c:0d:62:1b
           Card-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k
           IF: wlan0 state: up mac: 60:e3:27:08:b6:6c
Drives:    HDD Total Size: 820.2GB (9.8% used)
           ID-1: /dev/sda model: ST3320820SCE size: 320.1GB

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 3:39 pm
by Stevo
The only differences I could really spot with the newer kernel is that I don't see that TSC and firmware error message when booting in Virtual Box. I don't have the hardware to test the extended amdgpu support, and all the driver builds should be the same as for the 4.13 bpo kernel. Just keep using it and make sure everything keeps working, I guess.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 3:42 pm
by entropyfoe
Another successful beta 2 install. This one on my family room system used for streaming youtube, music, pictures etc.
The install from USB was fast.Everything working so far. This box has an on chip ati graphs, using whatever open-source selected automatically.
The install, all updated, fixed two nagging application problems I had.
1. pandora was not working, now it is under firefox 57, though noscript is not available yet, and that may have caused the problem (though I allowed all scripts, still did not play).
2. I have some family VHS I had transferred to DVD, and ripped with handbrake. On this machine only, the video was skewed, torn diagonally. Now the same file play perfectly in vlc.

Code: Select all

 inxi -F
System:    Host: X2 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: desktop Mobo: ASUSTeK model: A88XM-A/USB 3.1 v: Rev X.0x serial: N/A
           UEFI [Legacy]: American Megatrends v: 0309 date: 03/04/2016
CPU:       Quad core AMD A10-7860K Radeon R7 12 Compute Cores 4C+8G (-MCP-) cache: 8192 KB
           clock speeds: max: 3600 MHz 1: 3590 MHz 2: 3590 MHz 3: 3590 MHz 4: 3590 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
           Display Server: x11 (X.Org 1.19.2 )
           drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           Resolution: 1024x768@60.00hz
           OpenGL: renderer: Gallium 0.4 on AMD KAVERI (DRM 2.50.0 / 4.13.0-0.bpo.1-amd64, LLVM 3.9.1)
           version: 4.3 Mesa 13.0.6
Audio:     Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel
           Card-2 Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio Controller
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: up speed: 100 Mbps duplex: 
Drives:    HDD Total Size: 1560.3GB (26.9% used)
           ID-1: /dev/sdb model: SAMSUNG_HD501LJ size: 500.1GB
           ID-2: /dev/sdc model: WDC_WD1002FAEX size: 1000.2GB
           ID-3: /dev/sda model: OCZ size: 60.0GB
Partition: ID-1: / size: 15G used: 4.4G (32%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 15G used: 116M (1%) fs: ext4 dev: /dev/sda3
           ID-3: swap-1 size: 8.83GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 0.0C mobo: N/A gpu: -1.0
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 195 Uptime: 24 min Memory: 1745.6/6916.5MB Client: Shell (bash) inxi: 2.3.43 

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 4:06 pm
by Jerry3904
Tested iDevice Mounter on B1 and B2--twice. Results identical for iPhone 6 and 6S

B1: both mounted successfully, folders available
B2: neither mounted, error message attached

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 4:11 pm
by BitJam
asqwerth wrote:Brother network printer MFC-9320CW - the correct colour printer driver is found in the Printer Config program. Works fine.
Scanner function - again does not work OOTB as detailed in the MX Wiki here: https://mxlinux.org/wiki/hardware/scanners#Brother

/usr/lib/sane folder not created by default in the iso.

I followed the instructions in wiki to create said folder and the 6 symlinks, and confirm that the solution works for MX17 as well.
Is this something we can or should automate with the package installer?

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 4:16 pm
by dolphin_oracle
BitJam wrote:
asqwerth wrote:Brother network printer MFC-9320CW - the correct colour printer driver is found in the Printer Config program. Works fine.
Scanner function - again does not work OOTB as detailed in the MX Wiki here: https://mxlinux.org/wiki/hardware/scanners#Brother

/usr/lib/sane folder not created by default in the iso.

I followed the instructions in wiki to create said folder and the 6 symlinks, and confirm that the solution works for MX17 as well.
Is this something we can or should automate with the package installer?

Its a little different what you do depending on which brother driver, IIRC. Here is the info that asqwerth linked to, for reference. (its on the scanner side as she said).

Code: Select all

sudo mkdir /usr/lib/sane
sudo ln -s /usr/lib64/sane/libsane-brother3.so /usr/lib/sane/libsane-brother3.so
sudo ln -s /usr/lib64/sane/libsane-brother3.so.1 /usr/lib/sane/libsane-brother3.so.1
sudo ln -s /usr/lib64/sane/libsane-brother3.so.1.0.7 /usr/lib/sane/libsane-brother3.so.1.0.7
sudo ln -s /usr/lib64/libbrscandec3.so /usr/lib/libbrscandec3.so
sudo ln -s /usr/lib64/libbrscandec3.so.1 /usr/lib/libbrscandec3.so.1
sudo ln -s /usr/lib64/libbrscandec3.so.1.0.0 /usr/lib/libbrscandec3.so.1.0.0

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 4:33 pm
by chrispop99
Stevo wrote:
chrispop99 wrote:Using the Nvidia driver installer in an earlier test resulted in a failure to boot to a graphical environment.

Following Stevo's updating of the drivers, I can confirm they now work as expected.

Chris
Thanks, we still need testing of the newer 4.13.13 (4.13.0-1) kernel in testing--it has a couple advantages over the bpo one and would be better as the default.
Would that be the Liquorix one from the PI?

Chris

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 4:41 pm
by richb
chrispop99 wrote:
Stevo wrote:
chrispop99 wrote:Using the Nvidia driver installer in an earlier test resulted in a failure to boot to a graphical environment.

Following Stevo's updating of the drivers, I can confirm they now work as expected.

Chris
Thanks, we still need testing of the newer 4.13.13 (4.13.0-1) kernel in testing--it has a couple advantages over the bpo one and would be better as the default.
Would that be the Liquorix one from the PI?

Chris
I installed the one NOT labelled Liquorix from the PI. I think that is what he meant.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 4:45 pm
by stsoh
i have update kernel from experiment repo to 4.14.1.

Code: Select all

$ inxi -S
System:    Host: mx1 Kernel: 4.14.1-antix.1-amd64-smp x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 5:01 pm
by Jerry3904
Tested the iPad that worked with B1, it also fails with B2

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 22, 2017 7:08 pm
by Kestrel
richb wrote:The diagonal line with two arrows at either end in the toolbar puts it full screen hiding titlebar, address bar. everything at the top. Moving your mouse to the screen top brings them back, back down hides them again.

EDIT: Or F11 toggle.
Thanks but this also hides the panel at the bottom of my screen which is not ideal. And moving my mouse to the bottom does not make the panel reappear like it does with the toolbars etc at the top.

Its a minor annoyance which I can live with. MX is the best distro I have used so far.

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 7:05 am
by chrispop99
Testing of 4.13.0-1 kernel from 'Testing'

Machine 1 - 64-bit desktop
This machine has Nvidia graphics, with the PI driver installed. After the kernel upgrade, graphics continued to work as normal.

Machine 2 - 64 bit laptop
After the kernel upgrade, Virtual Box was installed from the PI. A virtual machine was created,and Windows 7 installed into it. The Guest Additions were installed. No problems were encountered.

Machine 3 - 32 bit laptop
After the kernel upgrade, no problems were encountered.

Basic functionality works as expected on all machines. Common graphic, multimedia and document files opened and their applications functioned as expected. Internet and network connectivity continued to work. The network printer they are connected to continues to function.

If anything specific needs testing, please ask before the machines have a fresh install ready for more testing.

Chris

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 8:31 am
by richb
Testing of 4.13.0-1 kernel from 'Testing'

Installed to nVidia Optimus laptop. nVidia driver install successful. I do not observe any problems

Code: Select all

System:    Host: mx1 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: laptop System: Acer product: Aspire V5-572G v: V2.06 serial: N/A
           Mobo: Acer model: Dazzle_CX v: Type2 - A01 Board Version serial: N/A
           UEFI [Legacy]: Insyde v: V2.06 date: 05/22/2013
Battery    BAT1: charge: 43.8 Wh 100.0% condition: 43.8/53.4 Wh (82%)
           hidpp__0: charge: N/A condition: NA/NA Wh
CPU:       Dual core Intel Core i5-3337U (-HT-MCP-) cache: 3072 KB
           clock speeds: max: 2700 MHz 1: 1795 MHz 2: 1795 MHz 3: 1795 MHz 4: 1795 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M]
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@59.99hz


Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 8:55 am
by entropyfoe
Stability testing is going well so far.
Happy Thanksgiving to all US forum members, and to the world as well...
I have much to be thankful for, including this wonderfully maturing MX-17.
As I wrote earlier, for me,mx-17 is at the level of a Woodford beta, which many have run for years !


With beta1, and its 4.9 kernel, my Ryzen chip and board would spontaneously reboot. These sorts of reports are found widely on the net , on reddit(amd), phoronix etc. All saying new kernels are better.
On this hardware (signature machine), antix with its 4.10 was stable >17 days.
But the MX beta1 would reboot usually once a day, often at idle, not much happening.

But the beta2, fully updated, at idle, under heavy load, sleeping, waking, apps crash, MX 17 remains solid.

It feels solid like the antix, I had one application lock, scid, a chess database, but scid was killed, and all other programs and OS went on as normal. Not an OS problem, or the hardware, I think it is a new version..Can I revert to an earlier version, none earlier are in synaptic????)

So far so good, and I read in the earlier post even a 4.14 kernel. That is a long tern support kernel.
For Ryzen, 4.15 is the holy grail, lots of new improvements, temperature monitoring I read !

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 10:49 am
by JLS727
As a follow-up to post 119 following is some data on the Dell latitude 3160 system:

Code: Select all

jlschwartz@mx16:~
$ inxi -F
System:    Host: mx16 Kernel: 4.7.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.2
           Distro: MX-16.1_x64 Metamorphosis 12 December 2016
Machine:   Device: laptop System: Dell product: Latitude 3160 serial: N/A
           Mobo: Dell model: N/A serial: N/A UEFI: Dell v: A09 date: 06/29/2017
Battery    BAT0: charge: 31.7 Wh 83.1% condition: 38.2/39.3 Wh (97%)
CPU:       Quad core Intel Pentium N3710 (-MCP-) cache: 1024 KB
           clock speeds: max: 2560 MHz 1: 871 MHz 2: 479 MHz 3: 479 MHz 4: 539 MHz
Graphics:  Card: Intel Device 22b1
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@60.04hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 405 (Braswell) version: 4.3 Mesa 12.0.3
Audio:     Card Intel Device 2284 driver: snd_hda_intel Sound: ALSA v: k4.7.0-0.bpo.1-amd64
Network:   Card-1: Intel Wireless 7265 driver: iwlwifi
           IF: wlan1 state: up mac: a4:02:b9:0a:69:14
           Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth1 state: down mac: 14:18:77:b4:f4:18
Drives:    HDD Total Size: 128.0GB (26.0% used)
           ID-1: /dev/sda model: LITEON_CV3 size: 128.0GB
Partition: ID-1: / size: 38G used: 28G (76%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
Sensors:   System Temperatures: cpu: 27.0C mobo: 25.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 208 Uptime: 2 min Memory: 487.8/7844.2MB Client: Shell (bash) inxi: 2.3.43 
In addition this system will not boot Antix 17 either. It stops and hangs as well. I hope this helps. Thanks.

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 11:02 am
by dolphin_oracle
JLS727 wrote:As a follow-up to post 119 following is some data on the Dell latitude 3160 system:

Code: Select all

jlschwartz@mx16:~
$ inxi -F
System:    Host: mx16 Kernel: 4.7.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.2
           Distro: MX-16.1_x64 Metamorphosis 12 December 2016
Machine:   Device: laptop System: Dell product: Latitude 3160 serial: N/A
           Mobo: Dell model: N/A serial: N/A UEFI: Dell v: A09 date: 06/29/2017
Battery    BAT0: charge: 31.7 Wh 83.1% condition: 38.2/39.3 Wh (97%)
CPU:       Quad core Intel Pentium N3710 (-MCP-) cache: 1024 KB
           clock speeds: max: 2560 MHz 1: 871 MHz 2: 479 MHz 3: 479 MHz 4: 539 MHz
Graphics:  Card: Intel Device 22b1
           Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@60.04hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 405 (Braswell) version: 4.3 Mesa 12.0.3
Audio:     Card Intel Device 2284 driver: snd_hda_intel Sound: ALSA v: k4.7.0-0.bpo.1-amd64
Network:   Card-1: Intel Wireless 7265 driver: iwlwifi
           IF: wlan1 state: up mac: a4:02:b9:0a:69:14
           Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth1 state: down mac: 14:18:77:b4:f4:18
Drives:    HDD Total Size: 128.0GB (26.0% used)
           ID-1: /dev/sda model: LITEON_CV3 size: 128.0GB
Partition: ID-1: / size: 38G used: 28G (76%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
Sensors:   System Temperatures: cpu: 27.0C mobo: 25.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 208 Uptime: 2 min Memory: 487.8/7844.2MB Client: Shell (bash) inxi: 2.3.43 
In addition this system will not boot Antix 17 either. It stops and hangs as well. I hope this helps. Thanks.
Thanks. We (mx and antiX) are taking a look! thanksgiving in the states might slow things down a little this weekend.

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 1:46 pm
by tradonal
hello all
I am french post translated with google
just for information:
This concerns synaptic

-) On my main system MX-16.1 on sda1 primary partition I have no problems with synaptic.

-) With MX-17.b2_386 Horizon November 20, 2017 on sda6 logical partition, synaptic is very very very long before finishing ( rebuilding the index) (reconstruction de l'index) and uses 100% cpu

If It can help....

Image

Code: Select all

carlus@mx1:~
$ apt-cache show synaptic 
Package: synaptic
Version: 0.84.2
Installed-Size: 7824
Maintainer: Michael Vogt <mvo@debian.org>
Architecture: i386
Depends: libapt-inst2.0 (>= 0.8.16~exp12), libapt-pkg5.0 (>= 1.1~exp9), libatk1.0-0 (>= 1.12.4), libc6 (>= 2.3.6-6~), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.2.4), libept1.5.0, libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.16.0), libgnutls30 (>= 3.5.0), libgtk-3-0 (>= 3.3.16), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libpcre2-8-0, libstdc++6 (>= 5.2), libvte-2.91-0, libx11-6, libxapian30, zlib1g (>= 1:1.1.4), hicolor-icon-theme, policykit-1
Recommends: libgtk2-perl (>= 1:1.130), rarian-compat, xdg-utils
Suggests: dwww, menu, deborphan, apt-xapian-index, tasksel, software-properties-gtk
Conflicts: menu (<< 2.1.11)
Description-fr: Gestionnaire graphique de paquets
 Synaptic est un outil graphique de gestion de paquets basé sur GTK+ et APT.
 Il permet l'installation, la mise à jour et la suppression de paquets
 logiciels de manière conviviale.
 .
 En plus des fonctionnalités de base, les fonctions suivantes sont aussi
 fournies :
  - recherche et filtrage dans la liste des paquets disponibles ;
  - mise à jour intelligente du système ;
  - correction des dépendances cassées ;
  - modification de la liste des dépôts (sources.list) utilisés ;
  - téléchargement du dernier journal des modifications d'un paquet
     (« changelog ») ;
  - configuration des paquets avec « debconf » ;
  - parcours de l'ensemble de la documentation d'un paquet
     (« dwww » est nécessaire).
Description-md5: d4fb8e90c9684f1113e56123c017d85f
Homepage: http://www.nongnu.org/synaptic/
Tag: admin::package-management, implemented-in::c++, interface::graphical,
 interface::x11, role::program, scope::application, suite::debian,
 uitoolkit::gtk, works-with::software:package, x11::application
Section: admin
Priority: optional
Filename: pool/main/s/synaptic/synaptic_0.84.2_i386.deb
Size: 2106592
MD5sum: a76c37d0f560634a116b418407c0ef05
SHA256: c995d774d0a298a77b855296db6266f55fb7c99b0a1ff62751cfd2f893913a63

carlus@mx1:~
$ 

Code: Select all

carlus@mx1:~
$ inxi -S
System:    Host: mx1 Kernel: 4.13.0-0.bpo.1-686-pae i686 bits: 32 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_386 Horizon November 20, 2017
carlus@mx1:~
$ 

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 1:56 pm
by Jerry3904
Please post the output of

Code: Select all

inxi -r
as regular user.

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 2:18 pm
by tradonal
Jerry3904 wrote:Please post the output of

Code: Select all

inxi -r
as regular user.
here is

Code: Select all

carlus@mx1:~
$ inxi -r
Repos:     Active apt sources in file: /etc/apt/sources.list.d/antix.list
           deb http://nl.mxrepo.com/antix/stretch stretch main
           Active apt sources in file: /etc/apt/sources.list.d/debian-stable-updates.list
           deb http://ftp.fr.debian.org/debian/ stretch-updates main contrib non-free
           Active apt sources in file: /etc/apt/sources.list.d/debian.list
           deb http://ftp.fr.debian.org/debian/ stretch main contrib non-free
           deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt sources in file: /etc/apt/sources.list.d/mx.list
           deb http://nl.mxrepo.com/mx/repo/ stretch main non-free
carlus@mx1:~
$ 
EDIT:
synaptic is start htop watch line with *** apt-xapian **** for 100% cpu
command to use to monitor synaptic output?
ps -aux *** or ???
thank you

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 8:41 pm
by dolphin_oracle
the first update of the index takes a while because there isn't an exisiting index. later updates should be faster. Have you let the index finish building?

Re: MX-17 Beta 2 Feedback

Posted: Thu Nov 23, 2017 8:44 pm
by dolphin_oracle
running bluetooth audio for the first time ever on my laptop.

tip: some audio devices, like mine, have more than out output logically, although only one actual output in fact. I used pavucontrol's sink settings to select the right one for my device.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 3:05 am
by skidoo
1) launch MX Welcome
2) click "Users Manual"
3) exit the pdf viewer
4) note the (overpainted?) state of the MX Welcome window
Image

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 3:11 am
by skidoo
1) right-click desktop and choose "Create Launcher"
2) fill name + comment + command fields... and click the button labeled "No Icon" to choose an icon image assignment
3) note the "application is not responding" popup dialog if you attempt to RedX close the "Create Launcher" window
4) note the 25(?) second delay, with no busy icon to indicate activity...

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 3:32 am
by skidoo
suggested tiny tweaks:

consider jogging the default x/y offset for the "torn red paper" conky (as is, it partially obscures the MX logo of the default wallpaper)

noticed: at the foot of one of the tall conkies, a line displays ${some_var} an unknown/unreplaced placeholder

noticed: paperclip icon in panel lacks an onhover hint text

consider changing the icon assigned for "Root Terminal" (in panel taskbar, it is currently indistinguishable from "regular" terminal instances)

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 5:38 am
by Jerry3904
good ones

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 7:11 am
by greyowl
I need a newer version of qt for an app that I use.

I notice that MX 17b2 has qt 4.8.7 and MX 16.1 has qt 4.8.6 and the new antiX 17 has qt 5.7.1. The current version of qt is 5.9.3.

Is the final MX 17 going to have the newest version of qt 5.9.3?
If not, what is the reason why MX 17 has the older version of qt?

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 8:28 am
by vamsi
I doubt we'll add any antivirus
I think the antivirus is useful i copied some videos from my freinds windows pc Fortunate or Unfortunate i scanned the pendrive and i found 2 threats then i deleted the threats . From internet we will download many software that we want and at that time there is probability for antivirus. So i request you to add antivirus for scanning the downloaded files from internet it is very essential. If not possible then add that to MX package installer

Another Doubt are there any feature plans to upgrade MX package installer like Ubuntu software center or Mint software center

Thanks,
Vamsi.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 8:33 am
by richb
vamsi wrote:
I doubt we'll add any antivirus
I think the antivirus is useful i copied some videos from my freinds windows pc Fortunate or Unfortunate i scanned the pendrive and i found 2 threats then i deleted the threats . From internet we will download many software that we want and at that time there is probability for antivirus. So i request you to add antivirus for scanning the downloaded files from internet it is very essential. If not possible then add that to MX package installer

Another Doubt are there any feature plans to upgrade MX package installer like Ubuntu software center or Mint software center

Thanks,
Vamsi.
I understand your concern. One should not download software from the internet in my opinion. The devs may consider adding it to MXPI, although its availability in the repos makes it an easy install for those who want it.

No plans for emulating other software centers that I am aware of.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 8:39 am
by tascoast
Is MX Tweak-Other/Show systray (notification area) frame checkbox working for everyone else?

Unless I need to log out or something to refresh... I can only show/hide the frame via the traditional Notification Area-Properties/Show Frame checkbox. I am using currently the MX-16 Dark theme.

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: desktop System: LENOVO product: 7522RU3 v: ThinkCentre A58 serial: N/A
           Mobo: LENOVO model: N/A serial: N/A BIOS: LENOVO v: 5HKT52AUS date: 07/15/2010
CPU:       Dual core Intel Core2 Duo E7300 (-MCP-) cache: 3072 KB
           clock speeds: max: 2670 MHz 1: 2659 MHz 2: 2659 MHz
Graphics:  Card: Intel 4 Series Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.88hz
           OpenGL: renderer: Mesa DRI Intel G41 version: 2.1 Mesa 13.0.6
Audio:     Card Intel NM10/ICH7 Family High Def. Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card-1: Marvell 88E8057 PCI-E Gigabit Ethernet Controller driver: sky2
           IF: eth0 state: down mac: 00:01:6c:48:1a:77
           Card-2: Realtek RTL8191SU 802.11n WLAN Adapter driver: r8712u
           IF: wlan0 state: N/A mac: N/A
Drives:    HDD Total Size: 1000.2GB (43.8% used)
           ID-1: /dev/sda model: WDC_WD10EZEX size: 1000.2GB
Partition: ID-1: / size: 49G used: 4.8G (11%) fs: ext4 dev: /dev/sda13
           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 38.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 189 Uptime: 1:30 Memory: 985.5/3920.8MB Client: Shell (bash) inxi: 2.3.43 

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 8:42 am
by vamsi
richb wrote:
vamsi wrote:
I doubt we'll add any antivirus
I think the antivirus is useful i copied some videos from my freinds windows pc Fortunate or Unfortunate i scanned the pendrive and i found 2 threats then i deleted the threats . From internet we will download many software that we want and at that time there is probability for antivirus. So i request you to add antivirus for scanning the downloaded files from internet it is very essential. If not possible then add that to MX package installer

Another Doubt are there any feature plans to upgrade MX package installer like Ubuntu software center or Mint software center

I understand your concern. One should not download software from the internet in my opinion. The devs may consider adding it to MXPI, although its availability in the repos makes it an easy install for those who want it.

No plans for emulating other software centers that I am aware of.

Thanks,
Vamsi.
Thanks :happy:
About MX package installer will the Look of the Package installer will be changed to modern look like that of other software center in other distros in future. :happy:

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 8:56 am
by Jerry3904
Probably not, we generally avoid heavy GUIs.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 9:05 am
by vamsi
Jerry3904 wrote:Probably not, we generally avoid heavy GUIs.
Thanks.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 9:21 am
by dolphin_oracle
tascoast wrote:Is MX Tweak-Other/Show systray (notification area) frame checkbox working for everyone else?

Unless I need to log out or something to refresh... I can only show/hide the frame via the traditional Notification Area-Properties/Show Frame checkbox. I am using currently the MX-16 Dark theme.

Code: Select all

$ inxi -F
System:    Host: mx1 Kernel: 4.13.0-0.bpo.1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_x64 Horizon November 20, 2017
Machine:   Device: desktop System: LENOVO product: 7522RU3 v: ThinkCentre A58 serial: N/A
           Mobo: LENOVO model: N/A serial: N/A BIOS: LENOVO v: 5HKT52AUS date: 07/15/2010
CPU:       Dual core Intel Core2 Duo E7300 (-MCP-) cache: 3072 KB
           clock speeds: max: 2670 MHz 1: 2659 MHz 2: 2659 MHz
Graphics:  Card: Intel 4 Series Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.88hz
           OpenGL: renderer: Mesa DRI Intel G41 version: 2.1 Mesa 13.0.6
Audio:     Card Intel NM10/ICH7 Family High Def. Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-amd64
Network:   Card-1: Marvell 88E8057 PCI-E Gigabit Ethernet Controller driver: sky2
           IF: eth0 state: down mac: 00:01:6c:48:1a:77
           Card-2: Realtek RTL8191SU 802.11n WLAN Adapter driver: r8712u
           IF: wlan0 state: N/A mac: N/A
Drives:    HDD Total Size: 1000.2GB (43.8% used)
           ID-1: /dev/sda model: WDC_WD10EZEX size: 1000.2GB
Partition: ID-1: / size: 49G used: 4.8G (11%) fs: ext4 dev: /dev/sda13
           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 38.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 189 Uptime: 1:30 Memory: 985.5/3920.8MB Client: Shell (bash) inxi: 2.3.43 

its working here...just check the box (or uncheck depending on your preference) and hit "apply"

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 9:35 am
by tascoast
its working here...just check the box (or uncheck depending on your preference) and hit "apply"
Apply you say, ahem, I embarrass myself missing that now (pleas habitual familiarity with the instant Notification area settings) :cool: :snail:

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 9:40 am
by tascoast
tascoast wrote:
its working here...just check the box (or uncheck depending on your preference) and hit "apply"
Apply you say, ahem, I embarrass myself missing that now (pleas habitual familiarity with the instant Notification area settings) :cool: :snail:
* And I was happy to see this and the single-double click choices in MX Tweak, well done thank you.

****Apologies for double post, please delete...

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 10:02 am
by chrispop99
vamsi wrote:
I doubt we'll add any antivirus
I think the antivirus is useful i copied some videos from my freinds windows pc Fortunate or Unfortunate i scanned the pendrive and i found 2 threats then i deleted the threats . From internet we will download many software that we want and at that time there is probability for antivirus. So i request you to add antivirus for scanning the downloaded files from internet it is very essential. If not possible then add that to MX package installer
Anti-virus is not very essential for Linux. If sharing files with Windows machines, those machines are the ones that need to have up-to-date scanning on them.
vamsi wrote:Another Doubt are there any feature plans to upgrade MX package installer like Ubuntu software center or Mint software center

Thanks,
Vamsi.
One of the goals of MX Linux is to be fast and light, whilst still having acceptable usability. If more things are added, it will just become another Mint or Ubuntu, so no, it's very unlikely that the already adequate package installer will be changed.

Chris

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 10:31 am
by vamsi
Anti-virus is not very essential for Linux. If sharing files with Windows machines, those machines are the ones that need to have up-to-date scanning on them.
:happy: :happy:

One of the goals of MX Linux is to be fast and light, whilst still having acceptable usability. If more things are added, it will just become another Mint or Ubuntu, so no, it's very unlikely that the already adequate package installer will be changed.
Yes agree :p

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 10:37 am
by dolphin_oracle
clamAV and clamtk (a gui) are available in the standard repos if anyone wants them.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 10:44 am
by greyowl
greyowl wrote:I need a newer version of qt for an app that I use.

I notice that MX 17b2 has qt 4.8.7 and MX 16.1 has qt 4.8.6 and the new antiX 17 has qt 5.7.1. The current version of qt is 5.9.3.

Is the final MX 17 going to have the newest version of qt 5.9.3?
If not, what is the reason why MX 17 has the older version of qt?
Does anyone know the answer to these questions?
Thanks

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 10:47 am
by dolphin_oracle
we ship with qt 5.7.1

15 and 16 shipped with qt 5.3


These are the versions in the respective debian stable branch.

when looking at qt versions, be sure to check not only qt4 packages, but also qt5 packages.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 11:06 am
by Paul..
greyowl wrote:I need a newer version of qt for an app that I use.

I notice that MX 17b2 has qt 4.8.7 and MX 16.1 has qt 4.8.6 and the new antiX 17 has qt 5.7.1. The current version of qt is 5.9.3.

Is the final MX 17 going to have the newest version of qt 5.9.3?
If not, what is the reason why MX 17 has the older version of qt?
You can install qt5-default from the repo...which will get you qt 5.7.1...that is the proper version for debian stretch which MX-17 is based on. As root: apt install qt5-default. That should be sufficient unless you need something special in 5.9.3...

Or...you can use MX-Tools->Package Installer->Development->Qt5 Dev Environment
which will install the full development environment:
qtcreator
qt5-default
qttools5-dev-tools

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 11:19 am
by greyowl
Thanks for the clarification on qt.
I was using wrong info which I got from DistroWatch.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 11:21 am
by dolphin_oracle
greyowl wrote:Thanks for the clarification on qt.
I was using wrong info which I got from DistroWatch.

:happy: Ah, I see....they have several things wrong on that list. Enough that I suspect other distros' lists have inaccuracies as well.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 11:29 am
by spsf64
Not sure if this has been already posted;
During boot in live USB mode I see this msg:

[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)

I already tried to reinstall intel microcode, remaster and update kernel but the message persists...
Note: After Installation to HD there is no such message
This is part of the log from /var/log/dmesg
========================================================
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
[ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
========================================================

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 11:55 am
by BitJam
spsf64 wrote:[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
Googling that error message led me to this rather ominous report: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 12:20 pm
by Stevo
That error goes away if you install the 4.13.0-1 kernel in the test repo. We may make it the default.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 12:48 pm
by timkb4cq
According to the debian changelog, the Intel-microcode package that we include is supposed to have the fixes for both Skylake & Kaby Lake processors.
Reading the whole thread, it appears the original test to determine which processors are susceptible included some newer processors without the problem. I suspect the warning is due to an over-broad test in the kernel, which would explain why a later kernel gets rid of the message.

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 1:30 pm
by spsf64
Stevo wrote:That error goes away if you install the 4.13.0-1 kernel in the test repo. We may make it the default.
I tried; updated the kernel, remastered, " live usb kernel updater" and no go :frown:

demo@mx1:~/Desktop
$ uname -a
Linux mx1 4.13.0-1-amd64 #1 SMP Debian 4.13.13-1mx17 (2017-11-18) x86_64 GNU/Linux
demo@mx1:~/Desktop
$ dmesg | grep microcode
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
[ 0.451446] microcode: sig=0x306c3, pf=0x2, revision=0x19
[ 0.451761] microcode: Microcode Update Driver: v2.2.

Did I miss something?

Re: MX-17 Beta 2 Feedback

Posted: Fri Nov 24, 2017 5:07 pm
by timkb4cq
I have backported the newer intel-microcode from Buster (64bit only so far)
http://teharris.net/misc/intel-microcod ... _amd64.deb
Please install it and see if the message is still there at reboot.

edit: the backported intel-microcode for both arches is now available in the MX-17 testing repository, so you can get it with the MX-Tools Package Installer.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 4:55 am
by spsf64
timkb4cq wrote:I have backported the newer intel-microcode from Buster (64bit only so far)
http://teharris.net/misc/intel-microcod ... _amd64.deb
Please install it and see if the message is still there at reboot.

edit: the backported intel-microcode for both arches is now available in the MX-17 testing repository, so you can get it with the MX-Tools Package Installer.
Still the same message, not working in live USB...
Once again I did the same procedure; updated the package / remaster / update kernel (is this the right sequence?)
I think this problem is related to remaster, as I said before it is working fine in the in this same machine with system installed to HDD (It was already working with the original beta2 kernel).

edit: by "working" I mean loading microcode is ok, no message displayed during boot.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 8:28 am
by entropyfoe
Stability testing....OK, I got the first crash with beta2. It had been up 4 days as of last night.

I came down this morning to a blank screen. The fans are spinning, but no keyboard or mouse would make the system come back.
As before, a crash at idle, nothing much was going on, a browser with 2 windows, maybe 20 tabs, a few other applications, but basically sitting idle.
So I had to hit the reset button...clearing some orphaned inodes....and now back.
So, not as stable as the antix 17 with the 4.10 kernel where I got 8 and 9 days uptime in two stretches with NO crashes.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 9:52 am
by BitJam
spsf64 wrote:During boot in live USB mode I see this msg:

[Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)

I already tried to reinstall intel microcode, remaster and update kernel but the message persists...
Note: After Installation to HD there is no such message
This is part of the log from /var/log/dmesg
========================================================
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
========================================================
The timestamp on that message shows that it is occurring very early in the boot process while the live initrd is running. In order to get rid of that message the new microcode will need to be added to the live initrd since we are many seconds away from having the main file system available where the microcode was installed.

The basic procedure for this is straightforward:

Code: Select all

sudo su -
/live/bin/unpack-initrd
[ copy microcode, modules, whatever to newly created initrd/ directory]
/live/bin/unpack-initrd -r
exit
The first line changes to the root user. Then we unpack the live initrd into the initrd/ directory. Add the microcode and perhaps modules or whatever (if needed) under this new directory and then when you are done, the -r (--reverse) flag cause unpack-initrd to repackage the live initrd so it will be used on the next boot.

If the microcode is getting loaded when the "real" system starts a few seconds later, it might be okay to live with the error message on the live system. This depends on what the new microcode fixes.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 11:24 am
by tradonal
dolphin_oracle wrote:the first update of the index takes a while because there isn't an exisiting index. later updates should be faster.
re,
votre note est correcte, le problème est parti
your rating is correct, the problem is gone
dolphin_oracle wrote: Have you let the index finish building?
yes

thx

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 12:55 pm
by Stevo
spsf64 wrote:
Stevo wrote:That error goes away if you install the 4.13.0-1 kernel in the test repo. We may make it the default.
I tried; updated the kernel, remastered, " live usb kernel updater" and no go :frown:

demo@mx1:~/Desktop
$ uname -a
Linux mx1 4.13.0-1-amd64 #1 SMP Debian 4.13.13-1mx17 (2017-11-18) x86_64 GNU/Linux
demo@mx1:~/Desktop
$ dmesg | grep microcode
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
[ 0.451446] microcode: sig=0x306c3, pf=0x2, revision=0x19
[ 0.451761] microcode: Microcode Update Driver: v2.2.

Did I miss something?
Oh, I was just seeing the same error at first startup in Virtual Box with the bpo kernel, and the kernel update made that go away from the boot screen. I didn't check to see if it was still in dmesg.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 12:58 pm
by Stevo
Icons in the system tray are still limited to 22 pixels max as the default, and that is too small for higher DPI screens. Is there any downside to raising the maximum size on the ISO?

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 1:34 pm
by dolphin_oracle
Stevo wrote:Icons in the system tray are still limited to 22 pixels max as the default, and that is too small for higher DPI screens. Is there any downside to raising the maximum size on the ISO?

they can get pretty "cartoony" on high-dpi monitors. at 64 (the max), the default panel takes up almost the whole left side of the screen of a 1600x900 monitor.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 1:51 pm
by richb
I do not have much of an issue with the way they are on a 1920 X 1080. The app icons scale up reasonably with panel width and the notification icons can be scaled with the notification properties.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 3:31 pm
by Stevo
richb wrote:I do not have much of an issue with the way they are on a 1920 X 1080. The app icons scale up reasonably with panel width and the notification icons can be scaled with the notification properties.
I'm just assuming that the notification properties are not instantly discoverable, based on some of the video reviews we've seen on Youtube lately. It would be better if we would have them scaling bigger with the panel as default, rather than have to change the max value manually.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 3:36 pm
by richb
Stevo wrote:
richb wrote:I do not have much of an issue with the way they are on a 1920 X 1080. The app icons scale up reasonably with panel width and the notification icons can be scaled with the notification properties.
I'm just assuming that the notification properties are not instantly discoverable, based on some of the video reviews we've seen on Youtube lately. It would be better if we would have them scaling bigger with the panel as default, rather than have to change the max value manually.
I see your point. The first thing I do on a new install is raise the font size for the NA, A size of 44 is comfortable for me. However for a new user that "fix" is not obvious.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 3:39 pm
by Stevo
dolphin_oracle wrote:
Stevo wrote:Icons in the system tray are still limited to 22 pixels max as the default, and that is too small for higher DPI screens. Is there any downside to raising the maximum size on the ISO?

they can get pretty "cartoony" on high-dpi monitors. at 64 (the max), the default panel takes up almost the whole left side of the screen of a 1600x900 monitor.
I'm sorry, but I can't see how raising the maximum allowed size of the icons forces the panel to get bigger. On my 1920 x 1080 15.6 laptop screen, which is not uncommon, let alone even higher dpi counts, 22 pixels is just too small. They stay the same size if I raise the minimum size until I scale up the panel pixel size. If I don't raise the maximum size from 22, they stay dinky even if I make the panel bigger for my screen. But maybe this only applies to horizontal vs vertical panels?

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 3:59 pm
by BitJam
As I've said before, I really think we should be scaling these sizes automatically on the live system based on the screen resolution. This way the system should be very usable right out of the box on a very wide range of hardware. The default of making everything teeny-tiny on high resolution displays makes no sense.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 4:03 pm
by Stevo
BitJam wrote:As I've said before, I really think we should be scaling these sizes automatically on the live system based on the screen resolution. This way the system should be very usable right out of the box on a very wide range of hardware. The default of making everything teeny-tiny on high resolution displays makes no sense.
I was reading on the xfce forum that they recommend xrandr/arandr for that sort of scaling, but haven't messed around with that. I'm not sure if those keep the resolution at the display's native one, which font dpi and icon scaling does. If we had automatic display scaling for xfce, that would be a distinct advance. Do any other xfce distros have that?

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 9:39 pm
by danielson
Having a Conky conflict with Cairo (maybe).

Ever since i installed a few themes in Cairo, i can no longer access Conky clocks.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 10:00 pm
by danielson
Vivaldi is set as default browser and it is also set that way in applications but Firefox still loads.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 10:20 pm
by tascoast
Display=1680x1050, Panel Row Size=38, Notification Area=28

In a horizontal Panel I typically bump up the default Notification Area. The Panel icons still appear larger as they 'fill' the Panel space but it works for me.
Also using two rows on Workplace Switcher, a more compact arrangement.

viewtopic.php?f=97&t=42447&p=416413&hil ... er#p416408

...mentions an 'allow drag and drop' setting I'd been looking for. My Windows button Panel objects are currently opaque, but if panel reordering is set as I've done in MX-16, only the active window is, with the others being clear save for the text labels. This suits a Panel using a transparent background image. Is the setting hidden now in MX-17b2?

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 10:41 pm
by dolphin_oracle
tascoast wrote:Display=1680x1050, Panel Row Size=38, Notification Area=28

In a horizontal Panel I typically bump up the default Notification Area. The Panel icons still appear larger as they 'fill' the Panel space but it works for me.
Also using two rows on Workplace Switcher, a more compact arrangement.

viewtopic.php?f=97&t=42447&p=416413&hil ... er#p416408

...mentions an 'allow drag and drop' setting I'd been looking for. My Windows button Panel objects are currently opaque, but if panel reordering is set as I've done in MX-16, only the active window is, with the others being clear save for the text labels. This suits a Panel using a transparent background image. Is the setting hidden now in MX-17b2?

right click on panel>panel preferences>Items Tab>"Window Buttons" and the 'drag and drop" option is in the pull down box.

This dialog used to be available but the preference dialog is no longer exposed to external commands.

Re: MX-17 Beta 2 Feedback

Posted: Sat Nov 25, 2017 11:16 pm
by tascoast
Thanks dolphin. I got it at last by going to 'Edit the currently selected item' :happy:

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 4:26 am
by ldsemerchen
My Bluetooth headset can't connect. I can find it but last step failed.
Image

Code: Select all

System:    Host: mxfuji Kernel: 4.10.5-antix.3-amd64-smp x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine:   Device: laptop System: FUJITSU product: LifeBook T4220 serial: N/A
           Mobo: FUJITSU model: FJNB1D4 serial: N/A
           BIOS: FUJITSU // Phoenix v: Version 1.18 date: 02/23/2009
Battery    CMB1: charge: 32.1 Wh 99.2% condition: 32.3/56.2 Wh (58%)
CPU:       Dual core Intel Core2 Duo T8300 (-MCP-) cache: 3072 KB
           clock speeds: max: 2401 MHz 1: 1200 MHz 2: 2400 MHz
Graphics:  Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1024x768@60.00hz
           OpenGL: renderer: Mesa DRI Intel 965GM version: 2.1 Mesa 13.0.6
Audio:     Card Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.3-amd64-smp
Network:   Card-1: Marvell 88E8055 PCI-E Gigabit Ethernet Controller driver: sky2
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 00:17:42:c1:c5:19
           Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection driver: iwl4965
           IF: wlp12s0 state: up mac: 00:1f:3b:be:ce:3f
Drives:    HDD Total Size: 1120.2GB (2.0% used)
           ID-1: /dev/sda model: FUJITSU_MHY2120B size: 120.0GB
           ID-2: USB /dev/sdb model: My_Passport_0730 size: 1000.2GB
Partition: ID-1: / size: 106G used: 18G (17%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
Sensors:   System Temperatures: cpu: 61.0C mobo: 26.8C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 222 Uptime: 16 min Memory: 592.6/1993.7MB Client: Shell (bash) inxi: 2.3.43

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 9:23 am
by chrispop99
If Conky is prevented from starting using the Conky Manager, the Conky Toggle menu item remains, but is non-functional.

I can see the potential for confusion amongst some users, but am not sure if we can/should find a way to deal with this.

(As an aside, I've spent a couple of hours configuring Beta 2 on a spare machine as if I was using it for myself. I've added lots of software, and made many configuration changes. Nothing's broken!)

Chris

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 9:38 am
by richb
chrispop99 wrote:If Conky is prevented from starting using the Conky Manager, the Conky Toggle menu item remains, but is non-functional.

I can see the potential for confusion amongst some users, but am not sure if we can/should find a way to deal with this.

(As an aside, I've spent a couple of hours configuring Beta 2 on a spare machine as if I was using it for myself. I've added lots of software, and made many configuration changes. Nothing's broken!)

Chris
Maybe it should be removed from the menu and added to MX Tweak and show only if conky is running. I do not know if that is possible or even desirable.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 10:28 am
by Jerry3904
ldsemerchen wrote:My Bluetooth headset can't connect. I can find it but last step failed.

Code: Select all

System:    Host: mxfuji Kernel: 4.10.5-antix.3-amd64-smp x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_x64 Horizon November 6, 2017
Does the same error show up in Beta 2 with the new kernel...and the new package mentioned below?

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 10:35 am
by dolphin_oracle
ldsemerchen wrote:My Bluetooth headset can't connect. I can find it but last step failed.
Image

Code: Select all

System:    Host: mxfuji Kernel: 4.10.5-antix.3-amd64-smp x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b1_x64 Horizon November 6, 2017
Machine:   Device: laptop System: FUJITSU product: LifeBook T4220 serial: N/A
           Mobo: FUJITSU model: FJNB1D4 serial: N/A
           BIOS: FUJITSU // Phoenix v: Version 1.18 date: 02/23/2009
Battery    CMB1: charge: 32.1 Wh 99.2% condition: 32.3/56.2 Wh (58%)
CPU:       Dual core Intel Core2 Duo T8300 (-MCP-) cache: 3072 KB
           clock speeds: max: 2401 MHz 1: 1200 MHz 2: 2400 MHz
Graphics:  Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1024x768@60.00hz
           OpenGL: renderer: Mesa DRI Intel 965GM version: 2.1 Mesa 13.0.6
Audio:     Card Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.3-amd64-smp
Network:   Card-1: Marvell 88E8055 PCI-E Gigabit Ethernet Controller driver: sky2
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 00:17:42:c1:c5:19
           Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection driver: iwl4965
           IF: wlp12s0 state: up mac: 00:1f:3b:be:ce:3f
Drives:    HDD Total Size: 1120.2GB (2.0% used)
           ID-1: /dev/sda model: FUJITSU_MHY2120B size: 120.0GB
           ID-2: USB /dev/sdb model: My_Passport_0730 size: 1000.2GB
Partition: ID-1: / size: 106G used: 18G (17%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
Sensors:   System Temperatures: cpu: 61.0C mobo: 26.8C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 222 Uptime: 16 min Memory: 592.6/1993.7MB Client: Shell (bash) inxi: 2.3.43

pulseaudio-module-bluetooth wasn't installed until beta 2, so try installing that first.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 10:37 am
by Jerry3904
chrispop99 wrote:If Conky is prevented from starting using the Conky Manager, the Conky Toggle menu item remains, but is non-functional.

I can see the potential for confusion amongst some users, but am not sure if we can/should find a way to deal with this.

(As an aside, I've spent a couple of hours configuring Beta 2 on a spare machine as if I was using it for myself. I've added lots of software, and made many configuration changes. Nothing's broken!)

Chris
I noticed this too just last night. Wondered if changing the desktop file would help by adding the word "running" like this:

Code: Select all

[Desktop Entry]
Encoding=UTF-8
Type=Application
Name=Conky Toggle
Comment=Toggle running conky on/off
Icon=mx-conky
Categories=Utility;System;
Exec=conkytoggle.sh
Terminal=false
NoDisplay=False

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 11:18 am
by dolphin_oracle
how about we just start the "default" conky.

see attached script.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 11:21 am
by richb
dolphin_oracle wrote:how about we just start the "default" conky.

see attached script.
Sounds like a good solution.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 11:41 am
by Jerry3904
Maybe--it looks like it would work OK with Conky Manager but we would need to test it: does it open the right conky, does CM *know* about the open conky, etc.

Would just like to be sure.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 11:43 am
by dolphin_oracle
Jerry3904 wrote:Maybe--it looks like it would work OK with Conky Manager but we would need to test it: does it open the right conky, does CM *know* about the open conky, etc.

Would just like to be sure.
yes and yes.

and testing is why I attached the script.

what happens when you uncheck all the conky files in conky-manager is that conky-manager removes the startup script. all the files are still in place (even the ones copied to the fonts folder).

the revised toggle just puts back the default one as shipped if an existing one isn't found. no other changes.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 11:57 am
by Jerry3904
Sure, will test--was responding to Rich, sorry.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 12:11 pm
by richb
With default conky loaded ti toggles it off. Running again to toggle on which it does then produces an error:

Code: Select all

conky: no process found
conky: Syntax error (/home/richb/.conky/MX-antiX17:2: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: desktop window (1c00003) is subwindow of root window (4a7)
conky: window type - normal
conky: drawing to created window (0x4a00001)
conky: drawing to double buffer
conky: Unknown setting 'mail_spool'
conky: forked to background, pid is 12634
If a different conky is loaded and script run it disables it, toggling on works but gives an error:

Code: Select all

sed: can't read /home/richb/.Xresources: No such file or directory

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 1:06 pm
by dolphin_oracle
richb wrote:With default conky loaded ti toggles it off. Running again to toggle on which it does then produces an error:

Code: Select all

conky: no process found
conky: Syntax error (/home/richb/.conky/MX-antiX17:2: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: desktop window (1c00003) is subwindow of root window (4a7)
conky: window type - normal
conky: drawing to created window (0x4a00001)
conky: drawing to double buffer
conky: Unknown setting 'mail_spool'
conky: forked to background, pid is 12634
If a different conky is loaded and script run it disables it, toggling on works but gives an error:

Code: Select all

sed: can't read /home/richb/.Xresources: No such file or directory
those are conky errors. they happen no matter how the conky is launched. you just don't see them outside the terminal, but the messages do show up in ~/.xsession-errors

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 1:30 pm
by richb
Good. Then the script performed properly.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 1:36 pm
by kb5050
Is there a GUI tool that can safely automount my hard drives on startup?
I have Linux on my sdb drive and windows on my sda drive. Just want the drives fully mounted at startup so that applications can use them.
All the gurus say oh just edit your fstab file. Thats fine but how? Attempts to do that in the past, result in failure to boot.
I therefore would like to for now get a GUI or method of how to do that, by simply checking a checkbox.
In fact if you would only include it or automount all local sdx drives, that would surely be a blessing to many.
No the disks (GNOME) utility does not work by unchecking them.
Not even in a GNOME version of linux.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 1:39 pm
by Jerry3904
Try MX Tweak, Other tab: "Enable mounting of internal drives by non-root users."

Not sure offhand if that covers Windows partitions...

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 1:50 pm
by dolphin_oracle
kb5050 wrote:Is there a GUI tool that can safely automount my hard drives on startup?
I have Linux on my sdb drive and windows on my sda drive. Just want the drives fully mounted at startup so that applications can use them.
All the gurus say oh just edit your fstab file. Thats fine but how? Attempts to do that in the past, result in failure to boot.
I therefore would like to for now get a GUI or method of how to do that, by simply checking a checkbox.
In fact if you would only include it or automount all local sdx drives, that would surely be a blessing to many.
No the disks (GNOME) utility does not work by unchecking them.
Not even in a GNOME version of linux.
Checkout "disk manager " in out menu. I think it will do what you want.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 1:58 pm
by uncle mark
kb5050 wrote:Is there a GUI tool that can safely automount my hard drives on startup?
I have Linux on my sdb drive and windows on my sda drive. Just want the drives fully mounted at startup so that applications can use them.
All the gurus say oh just edit your fstab file. Thats fine but how? Attempts to do that in the past, result in failure to boot.
You've been pointed at the GUI tools. That said, I have always used fstab, but I'm running an ancient system and those tools weren't readily available at the time. You may have failed to create a mount point prior to editing.

If for some reason you want to try fstab again, start a new topic, post the file here, and I'll try and walk you through it.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 6:22 pm
by Stevo
Any thoughts about going to the newer papirus-icon-theme in testing? Visibly changes the Firefox icon to more to of a reddish instead of orangeish color, and needs a few more MB on the ISO for the new papirus-adapta and papirus-adapta-nokto variants. Lots of other icon additions/changes, too.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 6:29 pm
by dolphin_oracle
Stevo wrote:Any thoughts about going to the newer papirus-icon-theme in testing? Visibly changes the Firefox icon to more to of a reddish instead of orangeish color, and needs a few more MB on the ISO for the new papirus-adapta and papirus-adapta-nokto variants. Lots of other icon additions/changes, too.
I like the changes for the most part. The only thing we don't like is the life preserver icon for help-about. It stands out like a sore thumb. The mx16 version had a little info "i" icon.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 7:55 pm
by Stevo
What about using help-info or help-browser icons from the new theme?

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 8:11 pm
by dolphin_oracle
Stevo wrote:What about using help-info or help-browser icons from the new theme?
might be an option, but help-about is in every theme I've checked, but help-info is not.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 8:48 pm
by Stevo
Help-browser looks universal, and seem to be standardized with a question mark as the symbol...except for Adwaita, where it's that life-preserver again.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 8:48 pm
by Paul..
help-browser is also in a lot of themes, is it not? That's way better than the dopey life ring.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 8:50 pm
by dolphin_oracle
what bugs me is that "small" ones, like in the thunar "about" are an info "i". its the 48x48 and up that are life preservers. why in an svg icon theme would you care?

we can take help-browser up with adrian, but it still won't match other apps "help-about".

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 9:02 pm
by dolphin_oracle
on asqwerth's advice, I posted the help-about icon thing as an "issue" on the papirus team's github.

Re: MX-17 Beta 2 Feedback

Posted: Sun Nov 26, 2017 9:09 pm
by Paul..
dolphin_oracle wrote:what bugs me is that "small" ones, like in the thunar "about" are an info "i". its the 48x48 and up that are life preservers. why in an svg icon theme would you care?

we can take help-browser up with adrian, but it still won't match other apps "help-about".

It's only the 48x48 and up that are the life ring...weird! Yeah, let's talk with Adrian about the alternatives. I'm willing to do the work of changing from "help-about" to "help-browser" on each Qt app if we can agree on using it.

...Also see what your github post yields from Papirus dev...

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 1:06 am
by vamsi
Hello Devteam i have some suggestions with regard to MX linux

1) In Mx- Package installer now we had to click on + symbol and then the softwares expand instead of that add a thumbnail of the category i.e, Like Games as one big thumbnail and softwares as one big thumbnail like that when we click on that we will see the normal softwares what we see when we click on + icon to expand softwares . Because some time it is little bit uncomfortable to expand each and each category

2) Also remove some of the Extra softwares like Lucky Backup, Gnome PPP instead add them to Package installer and also update compiz in package installer

3) Add About Me in the MX -Linux which displays little hardware information about the system and MX- Logo brand with GUI interface which is quite useful to see the basic specifications

These are my suggestions only if possible implement them.
Thanks for making the Distro Unique :happy: :happy:

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 4:35 am
by stsoh
kernel 4.14.2 is out.

Code: Select all

$ uname -a
Linux mx1 4.14.2-antix.1-amd64-smp #1 SMP PREEMPT Sat Nov 25 20:09:07 EET 2017 x86_64 GNU/Linux

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 6:52 am
by danielson
With Manjaro, updating to newest kernel always erases boot entry to Windows.
Can grub-customizer help to avoid this in MX-Linux?

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 6:54 am
by dolphin_oracle
danielson wrote:With Manjaro, updating to newest kernel always erases boot entry to Windows.
Can grub-customizer help to avoid this in MX-Linux?
I've got 4 kernels installed right now (currently using antix 4.14.2 kernel) and my windows entry has remained thru them all.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 7:11 am
by jerry525
Has anyone tried to install the Private Internet Access Open VPN Application?
MX 16 worked a treat with the Version 68. (https://www.privateinternetaccess.com/)
I tried installing the latest version but did not work.
I tried installing earlier versions but no luck also, just got messages that I had the latest version.
I've now done a full reinstall of MX17 beta so am ready to try something.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 7:18 am
by asqwerth
danielson wrote:With Manjaro, updating to newest kernel always erases boot entry to Windows.
Can grub-customizer help to avoid this in MX-Linux?
A caution: if your main grub is something other than Manjaro, the boot entry generated for Manjaro by your other distro will have a missing portion in the initrd line. That's because Manjaro boots up the intel microcode differently from other distros, which is reflected in their correct/complete grub entry.

You'll need to manually edit the Manjaro boot entry in your other distro to have a proper grub menu entry that boots into Manjaro, or create a custom separate boot entry (manually or using grub-customiser) which has the complete initrd line.

Another caution: using grub-customiser over a long period, especially with a distro that has constant kernel updates (e.g. Manjaro), will lead eventually to lots of repeat entries in grub menu.

For that reason, I made Manjaro my main grub. But then, I don't have Windows on my PC.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 8:43 am
by asqwerth
Stevo wrote:Any thoughts about going to the newer papirus-icon-theme in testing? Visibly changes the Firefox icon to more to of a reddish instead of orangeish color, and needs a few more MB on the ISO for the new papirus-adapta and papirus-adapta-nokto variants. Lots of other icon additions/changes, too.
I like the adapta variants. FF icon is much more clearly defined now, which I like.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 8:50 am
by dolphin_oracle
I've asked the papirus guys to modify the help-about icon. conversing with them now, although I'm not sure we are going to get the answer we want.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 8:57 am
by asqwerth
Actually, what's wrong with the life preserver icon? I'm curious. Or is it just that it refuses to show up at all in the mx-apps when help-about is used as the icon?

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 9:03 am
by dolphin_oracle
asqwerth wrote:Actually, what's wrong with the life preserver icon? I'm curious. Or is it just that it refuses to show up at all in the mx-apps when help-about is used as the icon?

there is not wrong with it per se, it just doesn't match the other default icons on the mx-app button bars. Its also not consistent in papirus, depending on size for instance.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 12:20 pm
by jerry525
jerry525 wrote:Has anyone tried to install the Private Internet Access Open VPN Application?
MX 16 worked a treat with the Version 68. (https://www.privateinternetaccess.com/)
I tried installing the latest version but did not work.
I tried installing earlier versions but no luck also, just got messages that I had the latest version.
I've now done a full reinstall of MX17 beta so am ready to try something.
I’ve moved to Linux Mint (ironically it's where I started), really sorry, I loved MX. But PIA worked straight away with the latest Mint Cinnamon edition.
I wish you all well.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 1:01 pm
by Jerry3904
Thanks for letting us know--now we'll look into it!

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 2:23 pm
by brokera

Code: Select all

$ inxi -F
System:    Host: andy2 Kernel: 4.13.0-0.bpo.1-686-pae i686 bits: 32 Desktop: Xfce 4.12.3
           Distro: MX-17.b2_386 Horizon November 20, 2017
Machine:   Device: portable System: Dell product: ME051 serial: N/A
           Mobo: Dell model: 0RJ272 serial: N/A BIOS: Dell v: A10 date: 11/07/2006
Battery    BAT0: charge: 31.0 Wh 366.3% condition: 8.5/31.0 Wh (27%)
CPU:       Single core Intel Celeron M (-UP-) cache: 1024 KB speed: 1596 MHz (max)
Graphics:  Card: Intel Mobile 915GM/GMS/910GML Express Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1280x800@60.00hz
           OpenGL: renderer: Mesa DRI Intel 915GM x86/MMX/SSE2 version: 2.1 Mesa 13.0.6
Audio:     Card Intel 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Def. Audio Controller
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-0.bpo.1-686-pae
Network:   Card: Broadcom Limited BCM4401-B0 100Base-TX driver: b44
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:15:c5:61:3a:0c
Drives:    HDD Total Size: 250.1GB (10.3% used)
           ID-1: /dev/sda model: WDC_WD2500BEVE size: 250.1GB
Partition: ID-1: / size: 37G used: 5.3G (16%) fs: ext4 dev: /dev/sda3
           ID-2: /home size: 78G used: 17G (23%) fs: ext4 dev: /dev/sda1
           ID-3: swap-1 size: 2.14GB used: 0.02GB (1%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 48.5C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 154 Uptime: 1:32 Memory: 572.2/2011.4MB Client: Shell (bash) inxi: 2.3.43 
Hello. I have the following problems: I can not configure the wifi, and I periodically lose normal display of the laptop monitor. Vertical color bars appear on the monitor and I have to turn it off forcibly.
I will be very grateful for any help.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 5:16 pm
by mmontz
jerry525 wrote:
Has anyone tried to install the Private Internet Access Open VPN Application?
MX 16 worked a treat with the Version 68. (https://www.privateinternetaccess.com/)
I tried installing the latest version but did not work.
I tried installing earlier versions but no luck also, just got messages that I had the latest version.
I've now done a full reinstall of MX17 beta so am ready to try something.
I can confirm this.

Even following the manual instructions here: https://www.privateinternetaccess.com/f ... -debian/p1

Connecting with Network Manager errors with 'The VPN connection failed because the VPN service failed to start'

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 5:35 pm
by Jerry3904
I'm not an expert but could you try something to see if it helps? Install these 3 packages:

Code: Select all

pptpd 
ppp 
pptp-linux
and reboot to try again.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 5:36 pm
by Jerry3904
BTW: did you also follow the directions in the section
(optional manual OpenVPN config)
Now Configure Network Manager (Manual config)
I ask b/c openvpn is installed in MX by default.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 5:46 pm
by mmontz
Jerry3904 wrote:BTW: did you also follow the directions in the section
(optional manual OpenVPN config)
Now Configure Network Manager (Manual config)
I ask b/c openvpn is installed in MX by default.
I see nothing in the manual about OpenVPN.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 6:14 pm
by Jerry3904
It's down the page you linked to:
(optional manual OpenVPN config)
Now Configure Network Manager (Manual config)
=============================================
- Right click the Network Manager on the menu bar
- and click "Edit Connections..."
- then click "Add" (...or if you see and "VPN" tab click it then click "Add")
- choose "OpenVPN" for the connection type from the drop down menu
- then click "Create..."
- for the "Connection name:" type in "Private Internet Access VPN"
- for the "Gateway:" type in "us-west.privateinternetaccess.com" or...
- whatever Hostname you would like to use from...
https://www.privateinternetaccess.com/pages/network/
- Ex. "brazil.privateinternetaccess.com"
- Ex. "mexico.privateinternetaccess.com"
- for the "Type:" select "Password" from the dropdown menu
- for the "User name:" type in your "p1234567" username
- for the "Password:" type in the password that goes with your "p-xxxxx" username
- for the "CA Certificate:" browse and select the CA Certificate from ~/OpenVPN-setup-PIA folder
- now click on "Advanced..."
- Check "Use custom gateway port:" and set it to "1198"
- Put a check in "Use LZO compression"
- Click on the "Security" tab
- Set the "Cipher:" to "AES-128-CBC"
- Set the "HMAC Authentication:" to "SHA-1"
- Click "OK"
- Click "Save"
- You may get asked to save a keyring password (you can leave this blank)

Reboot the computer now! (optional but recommended )

Now connect to the VPN
=============================================
- Now Left click the Network Manager on the menu bar
- click "VPN Connections"
- click "Private Internet Access"
- wait for it to connect

- Test by opening your Internet browser and going to...
https://ipleak.net/

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 7:03 pm
by mmontz
Following those instructions for VPN worked.

Thanks!

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 7:09 pm
by Jerry3904
Excellent--you're welcome.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 7:14 pm
by danielson
Btw, don't know who to thank for the desktop backgrounds (especially the wavy curtain kind) but they are just superb!
Hope to see more colors of same pattern.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 7:15 pm
by richb
I have been messing with this as well How does one obtain a username and password.

for the "User name:" type in your "p1234567" username
- for the "Password:" type in the password that goes with your "p-xxxxx" username

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 7:36 pm
by mmontz
You have to sign with a VPN provider. In this case it is Private Internet Access. Cost is about $40.00/yr.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 7:45 pm
by Jerry3904
danielson wrote:Btw, don't know who to thank for the desktop backgrounds (especially the wavy curtain kind) but they are just superb!
Hope to see more colors of same pattern.
Thanks for the kind words. We actually have a blog post on the topic:

https://mxlinux.org/mx17-artwork-prettifying-our-distro

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 9:06 pm
by danielson
Logitech headset issues again...

No matter how many times select the headset as default via MX-Select Sound or Alsa, the choice is not "sticking".
Have updated system and rebooted twice already (just in case).

@Jerry3904 - thank you for the link! Must write a word of appreciation to antechdesigns!

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 9:08 pm
by dolphin_oracle
danielson wrote:Logitech headset issues again...

No matter how many times select the headset as default via MX-Select Sound or Alsa, the choice is not "sticking".
Have updated system and rebooted twice already (just in case).

@Jerry3904 - thank you for the link! Must write a word of appreciation to antechdesigns!
do you unplug the headset?

I would set it as the default sound sink in pavucontrol rather than trying to set it via alsa. (which is what set-sound-card will try to do).

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 9:26 pm
by richb
mmontz wrote:You have to sign with a VPN provider. In this case it is Private Internet Access. Cost is about $40.00/yr.
Thanks. Up and running. Download speed is about 60% of a normal connection, upload about 90%. But very usable.

Re: MX-17 Beta 2 Feedback

Posted: Mon Nov 27, 2017 9:36 pm
by danielson
@dolphin_oracle,

Logitech is usually always plugged in.
Have removed it a few times to see, still no go.
Usually managed to get volume controls going with the Logitech device itself but no config options in pulseaudio controls are not doing it.

Update: got it! via alsa icon on panel (not alsa mixer).

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 28, 2017 5:55 am
by dr-kart
I tried to install oracle java 9. http://www.webupd8.org/2015/02/install- ... linux.html
(I did this way with mx 16.1 with no issues)
Now installation went without any warnings. And I do have

Code: Select all

java -version
java version "9.0.1"
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
But neither Firefox ESR nor Palemoon locate java plug-in. Which was the case with mx16.1.
Still not sure if this relates to current mx17b2. Did anyone have an experience installing java9 ?

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 28, 2017 9:01 am
by stsoh
hi,
btrfs auto resume lengthen boot time by 27sec, is this necessary? can it be not resume?
i like the fast boot time of mx-linux but fall short when i saw during bootup started to resume btrfs scripts/local-block 27 times.
anyway, i googled n found a solution to stop btrfs resume function.

Code: Select all

adding a new line containing "RESUME=none" to the end of /etc/initramfs-tools/initramfs.conf.
followed up, open terminal > su > password and run "update-initramfs -u".
See "man initramfs.conf" for details.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 28, 2017 8:34 pm
by MX-16_fan
I have a very cool super small no-name USB Nano stick here. Tested the MX-17 Beta 2 Live, and it managed to work with it on approx. every second boot (couldn't find any logic in it). Sometimes I had to unplug and replug it, and only after that it was being discovered.

However, when I used a fully installed MX-17 Beta 2, the stick wasn't being discovered at all.

On a different machine, lsusb identifies this WiFi stick as

Code: Select all

Bus 001 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
.

Doing a full dist-upgrade, taking everything that's in the MX Test Repo, didn't bring any change.

I had sometimes-but-sometimes-not kind of trouble using this stick with MX-16.1 also.

Ethernet isn't always present either.


Greetings, Joe

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 28, 2017 8:46 pm
by BitJam
MX-16_fan wrote:I have a very cool super small no-name USB Nano stick here. Tested the MX-17 Beta 2 Live, and it managed to work with it on approx. every second boot (couldn't find any logic in it). Sometimes I had to unplug and replug it, and only after that it was being discovered.
I've had that problem with SanDisk Ultra-Fit usb 3 sticks. They would always boot if I unplugged and replugged them while it was looking for the linuxfs file. I could not find a way to fix it. I think it is a problem with the hardware and/or the kernel. I've stopped using them as live-usbs. I now use Samsung Flash drive Fit usb-3 sticks. I don't have this problem with them or with any of the other usb sticks I've tried.

Re: MX-17 Beta 2 Feedback

Posted: Tue Nov 28, 2017 10:27 pm
by Stevo
dr-kart wrote:I tried to install oracle java 9. http://www.webupd8.org/2015/02/install- ... linux.html
(I did this way with mx 16.1 with no issues)
Now installation went without any warnings. And I do have

Code: Select all

java -version
java version "9.0.1"
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
But neither Firefox ESR nor Palemoon locate java plug-in. Which was the case with mx16.1.
Still not sure if this relates to current mx17b2. Did anyone have an experience installing java9 ?
It maybe a different setup for Oracle Java...our browser plugin is usually supplied by icedtea-plugin. We also have the openJDK 9 in our test repo for Java 9.

We are removing the browser plugin from the ISO since Firefox 57 no longer supports it.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 6:40 am
by dr-kart
Qupzilla 2.1.2 from test repo.
Won't connect any url. Since by default it has Proxy Configuration from Preferences|Browsing set to Manual configuration. Instead of System proxy configuration.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 7:01 am
by MX-16_fan
@BitJam:
BitJam wrote:I've had that problem with SanDisk Ultra-Fit usb 3 sticks. They would always boot if I unplugged and replugged them while it was looking for the linuxfs file. I could not find a way to fix it. I think it is a problem with the hardware and/or the kernel. I've stopped using them as live-usbs. I now use Samsung Flash drive Fit usb-3 sticks. I don't have this problem with them or with any of the other usb sticks I've tried.
Since yours is a USB flash drive and the one I have here is a USB WiFi adapter, sounds like the system is having problems with USB in general?


Greetings, Joe

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 9:09 am
by nathan2423
dr-kart wrote:Qupzilla 2.1.2 from test repo.
Won't connect any url. Since by default it has Proxy Configuration from Preferences|Browsing set to Manual configuration. Instead of System proxy configuration.
I wish there were a like button. Not in relation to the beta testing, but I've run into that issue with Qupzilla regularly.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 9:31 am
by BitJam
MX-16_fan wrote:Since yours is a USB flash drive and the one I have here is a USB WiFi adapter, sounds like the system is having problems with USB in general?
I doubt the two problems are related. When you said "nano stick" I thought you meant a flash drive, not a wifi dongle. For your problem, looking at the kernel messages may be useful. I suggest:

Code: Select all

dmesg --color=always | less -R

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 11:26 am
by jerry525
I'm not sure where my post went, here's a re-post:

I get this message on my desktop after logging in; Configured directory for incoming files does not exist. Please make sure that directory "/home/demo/Downloads" exists or configure it with blueman-services

No idea what to do with this.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 11:48 am
by BitJam
jerry525 wrote:I get this message on my desktop after logging in; Configured directory for incoming files does not exist. Please make sure that directory "/home/demo/Downloads" exists or configure it with blueman-services

No idea what to do with this.
I remember seeing this problem reported before. If it was your report I saw then IIRC, you get this message on an installed system with a username other than "demo". Had you done a snapshot before installing? I also remember that you had never used bluetooth. I think I asked you to run a command to search everything under your home directory for "demo" but we came up blank.

Someone else reported this same message on MX-14.4 but they were having other problems as well. With a Google(make sure that directory exists or configure it with blueman-services) I've found similar reports where the old home directory had to be recreated in order to get rid of this message. There was also a bug report in the blueman-project github repo.

There may be something funky in the file ~/.config/user-dirs.dirs or something strange in the XDG stuff, perhaps the $XDG_CONFIG_HOME variable or $XDG_DOWNLOAD_DIR. Perhaps /home/demo/Downloads gets baked in somewhere along the way and then it sticks even though it is not the same user anymore.

If the file ~/config/user-dirs.dirs exists (or something like that), please post the contents. Perhaps with:

Code: Select all

head -n30 ~/.config/user-dirs*

Also please post the output of the command:

Code: Select all

printenv | grep XDG
Maybe one of the other devs with more free time can help try to track this down.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 1:05 pm
by jerry525
You are right, I made some changes in live mode which saved on exit (language, keyboard & locale mainly), then I used this snapshot when I used it again & installed.
Here are the outputs:

Code: Select all

jerry@mx1:~
$ head -n30 ~/.config/user-dirs*
==> /home/jerry/.config/user-dirs.dirs <==
# This file is written by xdg-user-dirs-update
# If you want to change or add directories, just edit the line you're
# interested in. All local changes will be retained on the next run
# Format is XDG_xxx_DIR="$HOME/yyy", where yyy is a shell-escaped
# homedir-relative path, or XDG_xxx_DIR="/yyy", where /yyy is an
# absolute path. No other format is supported.
# 
XDG_DESKTOP_DIR="$HOME/Desktop"
XDG_DOWNLOAD_DIR="$HOME/Downloads"
XDG_TEMPLATES_DIR="$HOME/Templates"
XDG_PUBLICSHARE_DIR="$HOME/Public"
XDG_DOCUMENTS_DIR="$HOME/Documents"
XDG_MUSIC_DIR="$HOME/Music"
XDG_PICTURES_DIR="$HOME/Pictures"
XDG_VIDEOS_DIR="$HOME/Videos"

==> /home/jerry/.config/user-dirs.locale <==

Code: Select all

en_GBjerry@mx1:~
$ printenv | grep XDG
XDG_MENU_PREFIX=xfce-
XDG_VTNR=7
XDG_SESSION_ID=1
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/jerry
XDG_SESSION_TYPE=x11
XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share
XDG_SESSION_DESKTOP=lightdm-xsession
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_CURRENT_DESKTOP=XFCE
XDG_SEAT=seat0
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_CONFIG_DIRS=/etc/xdg

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 2:04 pm
by MX-16_fan
Just had the chance to test a friend's Technoethical N150 Mini Wireless USB Adapter for GNU/Linux-libre (https://tehnoetic.com/tehnoetic-wireles ... e-tet-n150). This is one of only two smaller USB WiFi sticks on the market that currently are officially being endorsed by the Free Software Foundation (see http://www.fsf.org/resources/hw/endorse ... ur-freedom).

What can I say? Plugged it in while MX-17 Beta 2 (fully dist-upgraded, including this version's "MX Test Repo") was running. Auto-detected in lightning speed, approx. one second, even though on slow hardware. System showed available networks approx. two seconds later.

I can definitely recommend this wonderful piece of hardware for testing. Thanks so much, MX-17 developers.

And thanks, Technoethical and Richard Stallman. Really great job!


Greetings, Joe

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 2:22 pm
by Adrian
Beta 3 is out viewtopic.php?f=94&t=43349
It's probably time to close the feedback for Beta 2.

Re: MX-17 Beta 2 Feedback

Posted: Wed Nov 29, 2017 2:40 pm
by richb
Thanks for the reminder. Done.

Testing of Beta 2 is complete. Beta 3 is available, announcement soon. issues unresolved in this thread should be posted in the beta 3 thread with a beta 3 installed.