MX Linux Forum

Posted: **Wed Nov 29, 2017 1:34 pm**

Feedback for beta 3 here please.

Please post conky comments here: The MX-17 conkies

If posting hardware issues, please post the output of the terminal command "inxi -F" at a minimum.

If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.

If posting remaster issues, please include the contents of /var/log/live/live-remaster.log

If posting issues with MX-PackeageInstaller "Popular Apps", please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).

We expect a somewhat shorter test cycle for this release, as we move toward release-canditate (RC) status.

Posted: **Wed Nov 29, 2017 3:03 pm**

First quick look: very nice!

Some minor items that caught my eye:
1) Live boot screen: "Press F1 for Help" is not localized, and the use of that font (which I like very much) looks very muddy. Maybe instead: "F1 = Help" (understood by almost everybody?)
2) the login box looks much better with the face enabled, as we have noted during earlier testing: line 11 in /etc/lightdm/mx17/lightdm-gtk-greeter.conf has to read

Code: Select all

hide-user-image=false

3) the default for png images is feh, though nomacs is installed. Don't have jpg to test but suspect it is the same.

Posted: **Wed Nov 29, 2017 3:07 pm**

The "Press F1 for Help" can't be localized because its part of the graphic. That's the same text as antiX uses, but we can do whatever.

as for the font...I'm got someone looking at the bootloader graphic but I really wanted to get this b3 out of the way. FWIW, thats a 1024x768 graphic and its stretches to whatever you have.

So open to suggestions on font and such.

3. I probably forgot to update the mimelist. We have that stuff hardcoded, and it probably still points to gthumb, so feh gets used as a default. same thing happened with leafpad_to_featherpad.

Posted: **Wed Nov 29, 2017 3:37 pm**

Installed fine to BIOS/HDD machine in sig. Looks great. No issues so far.

email me when you're ready for torrents.

Posted: **Wed Nov 29, 2017 3:49 pm**

WOW!!! What a difference from Beta1 - Truly awesome work - well done to all concerned.

Posted: **Wed Nov 29, 2017 3:58 pm**

Torrents up and seeding.

Links

32-bit
http://linuxtracker.org/download.php?id ... rent&key=0

64-bit
http://linuxtracker.org/download.php?id ... rent&key=0

Posted: **Wed Nov 29, 2017 4:02 pm**

zebedeeboss wrote:WOW!!! What a difference from Beta1 - Truly awesome work - well done to all concerned.

thanks zeb!

everyone has been working real hard on it. Not to mention all the work gone into populating our repos with stretch packages! I think I saw kdenlive 17 in the test repo.

and translations keep coming in!

Posted: **Wed Nov 29, 2017 4:05 pm**

iPhone Mounter works again, though the dialog box stays on top of Thunar instead of disappearing (we know this already, just logging it).

Posted: **Wed Nov 29, 2017 4:11 pm**

Jerry3904 wrote:iPhone Mounter works again, though the dialog box stays on top of Thunar instead of disappearing (we know this already, just logging it).

Out of curiosity, did you start with thunar already running, or did you allow the iDevice-mounter tool to launch it?

Posted: **Wed Nov 29, 2017 4:18 pm**

iDevice called it

Posted: **Wed Nov 29, 2017 4:37 pm**

Want a really small annoyance? The items in the Favorites menu are not in alphabetical order--or any other order AFAIK.

Posted: **Wed Nov 29, 2017 4:54 pm**

Note:
If anyone has a problem with a HUGE mouse cursor due to 4k resolution

add a file called .gtkrc-2.0 to your home folder and the contents need to be

Code: Select all

gtk-cursor-theme-name="Adwaita"
gtk-cursor-theme-size=22

You pick the theme-name and you pick the cursor-theme-size

Apologies if this is not the correct way or there is a better way - but it works for me here.

Posted: **Wed Nov 29, 2017 4:57 pm**

The Debian backports repo is hanging for me when called from MXPI. When enabled in Synaptic it does refresh. Anyone else seeing this. It did the same in b2.

Posted: **Wed Nov 29, 2017 5:08 pm**

richb wrote:The Debian backports repo is hanging for me when called from MXPI. When enabled in Synaptic it does refresh. Anyone else seeing this. It did the same in b2.

I had problems with that, I think it might be because it downloads packages in quick succession maybe there's a timeout for this kind of downloads, not sure, somebody who knows more about websites should tell me what's best to use to download the packages I use something like this:

Code: Select all

wget ftp://ftp.us.debian.org/debian/dists/" + ver_name + "-backports/main/binary-" + arch + "/Packages.gz -O mainPackages.gz"

And then I download contribPackages.gz and nonfreePackages.gz, I put a 3 second delay between the downloads but it doesn't seem to help.

Posted: **Wed Nov 29, 2017 6:36 pm**

All Users not checked in Network Manager, I thought this was required to auto-connect to wlan upon booting. Currently it does not connect.

Posted: **Wed Nov 29, 2017 6:38 pm**

richb wrote:All Users not checked in Network Manager, I thought this was required to auto-connect to wlan upon booting. Currently it does not connect.

it does here.

however, you have to set it up after each user is created. or check the box. there is no way to ship with the box checked.

incidentally, this configuration has not changed since early alpha.

Posted: **Wed Nov 29, 2017 6:47 pm**

dolphin_oracle wrote:
richb wrote:All Users not checked in Network Manager, I thought this was required to auto-connect to wlan upon booting. Currently it does not connect.
it does here.

however, you have to set it up after each user is created. or check the box. there is no way to ship with the box checked.

incidentally, this configuration has not changed since early alpha.

It does for me too, when the box is checked. Hard to remember all the default settings through 4 per-releases.

Posted: **Wed Nov 29, 2017 6:51 pm**

richb wrote:
dolphin_oracle wrote:
richb wrote:All Users not checked in Network Manager, I thought this was required to auto-connect to wlan upon booting. Currently it does not connect.
it does here.

however, you have to set it up after each user is created. or check the box. there is no way to ship with the box checked.

incidentally, this configuration has not changed since early alpha.
It does for me too, when the box is checked. Hard to remember all the default settings through 4 per-releases.

generally you set up a connection twice.

1. on the live media, (if you bother to do so, I usually don't unless I'm using a live stick).
2. again after initial reboot.

If its not working as above (which has been the same for every release except alpha 1, which I messed up with some interfaces stuff), then we need more info.

Install methodolgy
type of network
vpns?
inxi -n
is this after a hibernate or a cold restart?

and so forth.

Posted: **Wed Nov 29, 2017 6:59 pm**

generally you set up a connection twice.

1. on the live media, (if you bother to do so, I usually don't unless I'm using a live stick).
2. again after initial reboot.

If its not working as above (which has been the same for every release except alpha 1, which I messed up with

some interfaces stuff), then we need more info.

Install methodolgy
type of network
vpns?
inxi -n
is this after a hibernate or a cold restart?

and so forth.

I did not set it up in live,

And did not check the box until after several boots, some cold some restarts. Once checked it auto-connects. Si it is working as expected.

Posted: **Wed Nov 29, 2017 7:01 pm**

Jerry3904 wrote:Want a really small annoyance? The items in the Favorites menu are not in alphabetical order--or any other order AFAIK.

I always put my most frequent favorites at the top or bottom of the list anyway--easy to drag and drop them there. We have to give those that suffer from OCD something to do, eh?

Posted: **Wed Nov 29, 2017 7:13 pm**

Stevo wrote:
Jerry3904 wrote:Want a really small annoyance? The items in the Favorites menu are not in alphabetical order--or any other order AFAIK.
I always put my most frequent favorites at the top or bottom of the list anyway--easy to drag and drop them there. We have to give those that suffer from OCD something to do, eh?

I don't think the list has changed, except for adding the conky toggle and task manager since mx15 and that was only the manual link.

What order do you want?

Posted: **Wed Nov 29, 2017 7:27 pm**

dolphin_oracle wrote:
Stevo wrote:
Jerry3904 wrote:Want a really small annoyance? The items in the Favorites menu are not in alphabetical order--or any other order AFAIK.
I always put my most frequent favorites at the top or bottom of the list anyway--easy to drag and drop them there. We have to give those that suffer from OCD something to do, eh?
I don't think the list has changed, except for adding the conky toggle and task manager since mx15 and that was only the manual link.

What order do you want?

One that will please everyone.

Posted: **Wed Nov 29, 2017 7:31 pm**

Posted: **Wed Nov 29, 2017 7:37 pm**

I said it was really small...alphabetical would be what I would think would work best myself.

Posted: **Wed Nov 29, 2017 8:46 pm**

Jerry3904 wrote:I said it was really small...alphabetical would be what I would think would work best myself.

Tell the suckers that whatever order random order they are in was determined by careful studies of feng shui to make them harmonize...wait, is this a public thread? DELETE DELETE DELETE

Posted: **Wed Nov 29, 2017 9:34 pm**

Just installed tonight on my Lenovo SL510. Generally running great, but I have started running into the problem I have seen mentioned earlier that on reboot, the display brightness is being set very low by default, and it's necessary to turn it up every time I start the computer.

Code: Select all

$ inxi -F
System:    Host: lenovosl510 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b3_x64 Horizon November 29, 2017
Machine:   Device: laptop System: LENOVO product: 2847CZU v: ThinkPad SL510 serial: N/A
           Mobo: LENOVO model: 2847CZU serial: N/A
           BIOS: LENOVO v: 6JET85WW (1.43 ) date: 12/24/2010
Battery    BAT1: charge: 32.6 Wh 96.4% condition: 33.8/47.5 Wh (71%)
CPU:       Dual core Intel Core2 Duo T6670 (-MCP-) cache: 2048 KB
           clock speeds: max: 2201 MHz 1: 1200 MHz 2: 1200 MHz
Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@59.64hz
           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-1-amd64
Network:   Card-1: Intel Centrino Wireless-N 1000 [Condor Peak] driver: iwlwifi
           IF: wlan0 state: up mac: 8c:a9:82:3d:d1:2a
           Card-2: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: down mac: 60:eb:69:d9:a0:71
Drives:    HDD Total Size: 250.1GB (7.2% used)
           ID-1: /dev/sda model: WDC_WD2500BEVT size: 250.1GB
Partition: ID-1: / size: 20G used: 6.6G (35%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 20G used: 6.8G (37%) fs: ext4 dev: /dev/sda2
           ID-3: swap-1 size: 3.83GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
Sensors:   System Temperatures: cpu: 47.0C mobo: 0.0C
           Fan Speeds (in rpm): cpu: N/A fan-1: 0
Info:      Processes: 188 Uptime: 4 min Memory: 631.3/3794.7MB Client: Shell (bash) inxi: 2.3.43

Posted: **Wed Nov 29, 2017 9:44 pm**

nathan2423 wrote:Just installed tonight on my Lenovo SL510. Generally running great, but I have started running into the problem I have seen mentioned earlier that on reboot, the display brightness is being set very low by default, and it's necessary to turn it up every time I start the computer.
...
[/code]

Does the brightness-controller program do anything to help?

This: http://www.webupd8.org/2014/10/fix-brig ... -very.html may also help.

Posted: **Wed Nov 29, 2017 10:08 pm**

I am sorry - the "brightness controller program"? What I have done each time so far is simply rightclick on the power icon and then slide the brightness to the right, which works fine but is a pain. I will test the settings on the ubuntu page that you referenced, but I don't recall this same unit having any such problems on MX16 (recently it had been running Manjaro without this issue either, but I am switching it back to MX) ;-)

Posted: **Wed Nov 29, 2017 10:09 pm**

mx 17 beta 3 on 32 bit still stops at cli-installer

Posted: **Wed Nov 29, 2017 10:28 pm**

Although not specifically MX-Linux 17 b3 issue - thought i'd share that i managed to install Vivaldi 1.14.1030.3 (Official Build) snapshot (64-bit) which now has (as of today) sync option (bookmarks, p.w.,notes, extensions) and was just thrilled to try a first sync here and to see that everything seems to be syncing just fine with the version i had previously setup on Windows!

Vivaldi has made history in a big way today!

Posted: **Wed Nov 29, 2017 10:53 pm**

Feedback

... Wow, looks great. Down loaded and checked md5, all good. Burn to USB, and did a fast install. From pressing install, to rebooting after nvidia driver, it was all of 14 minutes, and the install was only 4 minutes.
From the first boot screen with the dark blue and stars to the demo wall paper, it is the best I have ever seen on a demo, looks very professional. Praise to the artists and designers, good colors on my monitor.
Did the default install.
Used the MX tool to install nvidia, chose the backport version of 375,82
Rebooted fine.
auto eth0 works
sound- had to use the sound card selector, go with the generic, works well.
Synaptic updates plus 100 packages installed.
enable data drive sda1 with the disk manager
enable compositor
Reboot for good measure.
Changed conky to mx-ko0/mx-full- easy, maybe something to play around with
updated the wallpaper anyway, did theme tweaks, widened panel, changed clock a bit, added panel shortcuts
usb thumb drive mounts, plays video, and unmounts all as normal
samba works, it looked better, but worked as usual, enabling me to supply credentials and log onto my wife's win7 machine.
suspend works, with a resume in 6-8 seconds (sound first)

All in all, fast, clean, everything works so far. A great beta so far I would say. Now to check stability.

Code: Select all

System:    Host: Ryzen Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b3_x64 Horizon November 29, 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: 2200 MHz 2: 2200 MHz 3: 2200 MHz 4: 2200 MHz
           5: 2200 MHz 6: 2200 MHz 7: 2200 MHz 8: 2200 MHz 9: 2200 MHz 10: 2200 MHz 11: 2200 MHz
           12: 2200 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-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.8% 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.1G (14%) fs: ext4 dev: /dev/nvme0n1p1
           ID-2: /home size: 73G used: 101M (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: 36C
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 254 Uptime: 9 min Memory: 496.6/16047.5MB Client: Shell (bash) inxi: 2.3.43

Posted: **Wed Nov 29, 2017 11:44 pm**

nathan2423 wrote:I am sorry - the "brightness controller program"? What I have done each time so far is simply rightclick on the power icon and then slide the brightness to the right, which works fine but is a pain. I will test the settings on the ubuntu page that you referenced, but I don't recall this same unit having any such problems on MX16 (recently it had been running Manjaro without this issue either, but I am switching it back to MX) ;-)

Brightness-controller is not on the default install, but it's in the repository. It's a tiny python application that also allows you to set the brightness and color temperature. Perhaps when you save a setting, it will remember the brightness.

Posted: **Thu Nov 30, 2017 1:49 am**

(as previously reported to dev during b2, not yet fixed)

BootScreen F1 ---} dialog titled "F4: Miscellaneious Options"
Clicking the hyperlink displayed here, titled "See Options Details Two for LiveUSB-only options", kicks user back to F1 MainMenu.

Posted: **Thu Nov 30, 2017 1:55 am**

MX Welcome ---} Contribute
Clicking opens an MX Viewer instance displaying a wiki page.
Because no address bar is visible, it seems inappropriate to present a "Click Here" (leading to a PayPal form)
in a context where the user is unable to see https:// plus secure lock icon.

Also, the PayPal form indicates "purpose: antiX" (which, given the context, seems incorrect)

Posted: **Thu Nov 30, 2017 2:00 am**

Related to the above, MX Welcome ---} Forums
same observation applies to ---} Wiki
clicking really should launch a traditional browser instance (IMO) rather than dumping the user into a context lacking urlbar (and ability to create bookmarks while traversing the forum and/or wiki)

Posted: **Thu Nov 30, 2017 2:09 am**

Noticed in MX Tweaks:
The as-shipped default is enabled for "Single-click in Thunar File Manager"

This default is dangerous, is noob-unfriendly; y'all can expect that reviewers will notice, and berate, this detail.

Posted: **Thu Nov 30, 2017 2:15 am**

MX Package Installer:
click "full app catalog"
click "stable repo"

I experienced an intolerable (in excess of 4 minutes) delay, progressbar dialog waiting for the list to populate.
After successfully testing, by installing "ncdu" package (86kb)... another damned 4+ minute wait until the list was refreshed.
-=-
This excessive delay was absent when choosing "testing" or "debian backports".
Whatever the cause (intermittent server lag?), 250+ seconds is way too long to leave the user hanging, wondering whether the app has become unresponsive.

Posted: **Thu Nov 30, 2017 2:20 am**

MX Codecs Installer:
The dialog text mentions legalese... responsibility... and user wonders "What codecs? Which ones, exactly?!?"

The exact details are presented in the linked wiki page.
Toward precluding worry/confusion and toward accomplishing informed consent, I'm just suggesting revision of the dialog text, coaching the user to click the Help button to read the details.

Posted: **Thu Nov 30, 2017 2:27 am**

MX Menu Editor:

Point of confusion ~~ the editor presents "categories" which are absent from the menu (and cannot be added to the menu)
screensavers, personal, hardware, education, development

I clicked "Help" to look for an explanation.
D'oh! user finds sparse text stating "it's basically, mostly self-explanatory" (thanks for makin' me feel stoopid, eh)

If the linked wiki page is to remain sparse, should at least provide hyperlinked "SeeAlso" citations.

[x] Notify Startup
^------- that's self-explanatory? (not even an onhover hint is provided)

Posted: **Thu Nov 30, 2017 2:31 am**

MX Tools ---} Live USB Maker

The popup dialog begs inclusion of a Help button, leading to wikiwiki page or section of the UserManual.

verbiage: "Select ISO"
???
"Select an ISO" or "Select a source (ISO)"

Posted: **Thu Nov 30, 2017 2:40 am**

(although the status quo "default" startup/shutdown are tooooo lennnnnnghty IMO)
consider:
Setting all sounds enabled, by default, including event sounds...
would provide immediate first-run feedback to the user, indicating "Hey, sound is working, right outa the box!"

ya only gits one chance to make a first impression

Posted: **Thu Nov 30, 2017 2:41 am**

skidoo wrote:Noticed in MX Tweaks:
The as-shipped default is enabled for "Single-click in Thunar File Manager"

This default is dangerous, is noob-unfriendly; y'all can expect that reviewers will notice, and berate, this detail.

Its not that dangerous, and has been the default for 3 years. Plus antiX single-clicks as well.

But I don't like the default, hence the inclusion of the checkbox to change it.

Posted: **Thu Nov 30, 2017 2:44 am**

skidoo wrote:MX Tools ---} Live USB Maker

The popup dialog begs inclusion of a Help button, leading to wikiwiki page or section of the UserManual.

verbiage: "Select ISO"
???
"Select an ISO" or "Select a source (ISO)"

there is a help button. Or is it a different pop up you are referring to.

Posted: **Thu Nov 30, 2017 2:45 am**

skidoo wrote:Noticed in MX Tweaks:
The as-shipped default is enabled for "Single-click in Thunar File Manager"

This default is dangerous, is noob-unfriendly; y'all can expect that reviewers will notice, and berate, this detail.

Isn't single-click the usual Linux default, with double-click a nod to Windows refugees?

Chris

Posted: **Thu Nov 30, 2017 2:47 am**

good stuff skiddoo. thanks!

Posted: **Thu Nov 30, 2017 2:56 am**

MX Tools ---} Live-usb Kernel

Because it requires explanation (and prerequisite remastering), seems wrong to present it first in the list of "Live" tools.
Click, and the MX Tools window disappears, replaced by a scary terminal window... and (oops) by clicking I've made it create some bargledonf.conf file???
Help, please.
^----- At the very least, the first line output by the script could direct the user to read file:///uber/share/doc/suchandsuch.html (or to consult manpage, or???)

Posted: **Thu Nov 30, 2017 2:58 am**

.
Upon clicking "Live-usb Maker" within MX Tools, here's what I see:

Similarly, clicking the MX Tools button labeled "Snapshot" dumps the user into a window stating "Calculating...."
The help button therein is enabled, and if the user clicks before waiting 2minutes for Calculating to finish,
window disappears, replaced by "MX Snapshot help" (and, we notice in conky, background process races(?) for another 3-4 minutes, consuming 100% CPU).
That "calculating" operation should not autostart; it would be better as a user-initiated Step1, with user able to read help before deciding whether to proceed.

A reordering of the entries within "Live" section seems advisable.
remasterCC /// Live-usb Maker /// LiveTools Help
Snapshot /// spacer (or another help link) /// Live-usb kernel updater

Posted: **Thu Nov 30, 2017 3:02 am**

skidoo wrote:MX Tools ---} Live-usb Kernel

Because it requires explanation (and prerequisite remastering), seems wrong to present it first in the list of "Live" tools.
Click, and the MX Tools window disappears, replaced by a scary terminal window... and (oops) by clicking I've made it create some bargledonf.conf file???
Help, please.
^----- At the very least, the first line output by the script could direct the user to read file:///uber/share/doc/suchandsuch.html (or to consult manpage, or???)

just to note, the output of the terminal file does indicate to press 'h' from help, which gives a man page.

Posted: **Thu Nov 30, 2017 3:03 am**

skidoo wrote:.
Upon clicking "Live-usb Maker" within MX Tools, here's what I see:

Gotcha, thanks. That is what you'll see first when running live.

Posted: **Thu Nov 30, 2017 3:15 am**

Put on naive user hat, visit MX Tools and click "Snapshot", mutter "Oops, durn, wrong thang" and close the window.
For me, the result is: background process racing several minutes 100% CPU load

Posted: **Thu Nov 30, 2017 3:24 am**

kodi works on 17b3.

it failed on 17b1 n 17b2, unknown fault(s) which only works after upgrade to kodi 17.5 n 'install -f'.

Code: Select all

$ apt policy kodi ffmpeg
kodi:
  Installed: 2:17.3+dfsg1-1mx17+1
  Candidate: 2:17.3+dfsg1-1mx17+1
  Version table:
 *** 2:17.3+dfsg1-1mx17+1 500
        500 http://iso.mxrepo.com/mx/repo stretch/main amd64 Packages
        100 /var/lib/dpkg/status
     2:17.1+dfsg1-3 500
        500 http://ftp.hk.debian.org/debian stretch/main amd64 Packages
ffmpeg:
  Installed: (none)
  Candidate: 7:3.3.4-1mx17+1
  Version table:
     7:3.3.4-1mx17+1 500
        500 http://iso.mxrepo.com/mx/repo stretch/main amd64 Packages
     7:3.2.9-1~deb9u1 500
        500 http://security.debian.org stretch/updates/main amd64 Packages
     7:3.2.7-1~deb9u1 500
        500 http://ftp.hk.debian.org/debian stretch/main amd64 Packages

Posted: **Thu Nov 30, 2017 3:44 am**

MX Tools ---} Snapshot

Snapshot "calcutatimates" free space on /home...
and, using a 2GB RAM testing machine, I've learned to expect that a user is "screwed, snapshot is doomed to fail, right from the starting gate".

Even if I _know_ to choose another device for the working directory, even if I attempt to workaround by uninstalling buncha stuffs + remaster prior to attempting snapshot... snapshot will still often (race the CPU 20+ minutes, and then ultimately) puke due to insufficient memory.

This is not a newly-introduced problem, and I cannot understand why it hasn't been mentioned by other testers.
A year back, during MX16 betatesting, I even added RAM (to 3GB) and retested. Same (failed) result, unless a considerable amount of pre-installed content was uninstalled prior to attempting a snapshot operation.

I'm testing on real hardware, but what I'm describing here should be reproduceable on a VM apportioned with 2GB RAM (or 3).
Fresh iso, perform apt update & apt upgrade then immediately (optionally, live-remaster and) attempt to perform a snapshot operation.

Posted: **Thu Nov 30, 2017 3:54 am**

MX Tools ---} MX Boot Repair

Click "Help" and (as with the other tools + associated help) the "MX Boot Repair" dialog window disappears, replaced by the MX Viewer instance.
Read that help page, now close it and return to "MX Boot Repair" dialog window. Do you recall whatall you just read in the Help?
Wait, there's FOUR options here? Dint muh helptext only mention 3? Better recheck...

The status quo expects (demands) the user to memorize, or have a clear takeaway upon first reading of the help content.
Isn't it reasonable to expect the user will want/need to have the helptext window remain open throughout the workflow?

Posted: **Thu Nov 30, 2017 4:00 am**

Across the MX Tools, users face an inbuilt "gotcha":
The tools close blissfully, ignoring the eventuality where I've changed a setting but have forgotten to click the APPLY button
( the prospect of forgetting to do so is especially likely in a multi-tabbed tool, e.g. MX Tools ---} User Manager )

Posted: **Thu Nov 30, 2017 4:10 am**

.
MX Tools ---} NVidia Driver Installer

No help for the wicked, eh. I (seriously) don't know whether this tool works in Livesession.
Let's clicky and

So, like, i still dunno whether it works in live session, not gonna go check the wiki right this moment
and so I Press <Enter>
and da joke's on me, eh?
(instead of exiting, it tells me my password failed)

edit:
before chalking it up to user error (screenshot shows "user pressed ^C)
I retried.
Didn't see a helplink, unsure whether to proceed, yes, it TELLS me to press control C, then to press enter
then (still) barks about incorrect password and invites another go'round

Posted: **Thu Nov 30, 2017 4:22 am**

This default is dangerous, is noob-unfriendly; y'all can expect that reviewers will notice, and berate, this detail.
Isn't single-click the usual Linux default, with double-click a nod to Windows refugees?

and double-chins might be the Mac default, and but all the other kids were playing with matches so...

Posted: **Thu Nov 30, 2017 4:34 am**

Hibernation tests

Eight machines with different hardware were tested, with fresh installs of b3. Details of machines are in attached files.

Each machine had the following code run:

Code: Select all

sudo update-initramfs -u -k all

They were then rebooted. MX Tweak was used to enable the Hibernate button. A random Featherpad file was created, and left open on the desktop. The machine was hibernated, and then resume was attempted.

Machine A
After hibernation, when attempting to resume, machine would sometimes lock up or spontaneously reboot. When it did reboot to the desktop, the open file was missing.

Machine B
After hibernation, when attempting to resume, machine would sometimes lock up or spontaneously reboot. When it did reboot to the desktop, the open file was missing.

Machine C
Sometimes resumed successfully, other times after a long delay would boot to desktop, but the open file was missing.

Machine D
Resumed successfully several times.

Machine E
Resumed successfully several times.

Machine F
Resumed successfully several times.

Machine G
Resumed successfully several times.

Machine H
Resumed successfully several times.

My conclusion would be that if we go with the option to include Hibernation enabling, it should be with the caveat that it may not work on lower end machines.

Chris

Posted: **Thu Nov 30, 2017 4:37 am**

MX Tools ---} MX Conky

Yay! The help window remains open
but... oops

.
.
(same glitch)
MX Tools ---} MX System Sounds

.
MX Tools ---} iDevice Mounter

Posted: **Thu Nov 30, 2017 4:51 am**

I clicked "Hide...tools"
and now (because I decline "don't ever display this root without password warning again") it's stuck in a loop

Dude!
Still stuck in a loop after xkilling the MX Tools window AND attempting to xkill the "Granted Permissions" dialog afterward.

Finally, after visiting terminal and "sudo killall mx-tools", I was able to RedX to close and dismiss the permissions dialog.

Posted: **Thu Nov 30, 2017 5:10 am**

skidoo wrote:MX Welcome ---} Contribute
Also, the PayPal form indicates "purpose: antiX" (which, given the context, seems incorrect)

The page has two links,one for antiX above another for MX, and the Purpose entry changes. I'm not sure whether most users see the difference, but from actual donations I have the impression that they are navigating that for the most part. On security: not sure, PayPal is pretty clear about its security. The trade-off on all these is that if the new user clicks on a Welcome icon that leads to a web page, there is a very long wait while Firefox sets everything up for the first time.

Posted: **Thu Nov 30, 2017 5:13 am**

Thanks for the careful look at the Tools.

skidoo wrote:MX Package Installer:
click "full app catalog"
click "stable repo"

I experienced an intolerable (in excess of 4 minutes) delay, progressbar dialog waiting for the list to populate.
After successfully testing, by installing "ncdu" package (86kb)... another damned 4+ minute wait until the list was refreshed.
-=-
This excessive delay was absent when choosing "testing" or "debian backports".
Whatever the cause (intermittent server lag?), 250+ seconds is way too long to leave the user hanging, wondering whether the app has become unresponsive.

Agreed--which is why I never use it.

skidoo wrote:MX Codecs Installer:
I'm just suggesting revision of the dialog text, coaching the user to click the Help button to read the details.

Maybe, but we do that with every single MX Tool to keep the screen uncluttered and to reduce the load on the translators.

Point of confusion ~~ the editor presents "categories" which are absent from the menu (and cannot be added to the menu)
screensavers, personal, hardware, education, development

I clicked "Help" to look for an explanation.
D'oh! user finds sparse text stating "it's basically, mostly self-explanatory" (thanks for makin' me feel stoopid, eh)

Yup, needs improvement. We have an entry in Tracker for updating the Help files, and I will give a stern warning to the fool who is supposed to be doing that, a Jerry somebody...

Posted: **Thu Nov 30, 2017 6:25 am**

skidoo wrote:MX Tools ---} Snapshot

Snapshot "calcutatimates" free space on /home...
and, using a 2GB RAM testing machine, I've learned to expect that a user is "screwed, snapshot is doomed to fail, right from the starting gate".

Even if I _know_ to choose another device for the working directory, even if I attempt to workaround by uninstalling buncha stuffs + remaster prior to attempting snapshot... snapshot will still often (race the CPU 20+ minutes, and then ultimately) puke due to insufficient memory.

This is not a newly-introduced problem, and I cannot understand why it hasn't been mentioned by other testers.
A year back, during MX16 betatesting, I even added RAM (to 3GB) and retested. Same (failed) result, unless a considerable amount of pre-installed content was uninstalled prior to attempting a snapshot operation.

I'm testing on real hardware, but what I'm describing here should be reproduceable on a VM apportioned with 2GB RAM (or 3).
Fresh iso, perform apt update & apt upgrade then immediately (optionally, live-remaster and) attempt to perform a snapshot operation.

Maybe we need a ram check while running live.

Likely the whole snapshot process is taking place in ram when running live.

Note snapshot routinely works in small amounts of ram when running from installed base, so the above makes some sense.

Posted: **Thu Nov 30, 2017 6:51 am**

skidoo wrote:.
MX Tools ---} NVidia Driver Installer

No help for the wicked, eh. I (seriously) don't know whether this tool works in Livesession.
Let's clicky and

So, like, i still dunno whether it works in live session, not gonna go check the wiki right this moment
and so I Press <Enter>
and da joke's on me, eh?
(instead of exiting, it tells me my password failed)

I'll check out that message, thanks.

I actually don't know if it works on live or not. If someone could try I would be obliged (I don't have any nvidia cards).

Posted: **Thu Nov 30, 2017 6:57 am**

I actually don't know if it works on live or not. If someone could try I would be obliged (I don't have any nvidia cards).

I don't think it can; a re-boot is suggested:

Screenshot.png

Chris

Posted: **Thu Nov 30, 2017 6:59 am**

Not germane feedback, but I have to say that background is stunning. I modified it to a teal and it is gorgeous. It also works very well desaturated for lightdm and boot menu.

Posted: **Thu Nov 30, 2017 7:04 am**

Just a reminder - we still have the situation where preventing Conky from starting using Conky Manager leaves a non-functional Whisker menu item.

Chris

Posted: **Thu Nov 30, 2017 7:16 am**

Do you mean: if no conky is selected to run the Toggle doesn't work? If yes, don't see a problem with that. I do see a good change where when a conky has been selected and neither CM nor MXC is open, it is not a true toggle (both directions).

Posted: **Thu Nov 30, 2017 7:31 am**

chrispop99 wrote:Just a reminder - we still have the situation where preventing Conky from starting using Conky Manager leaves a non-functional Whisker menu item.

Chris

Have you checked on b3? I thought I updated the script but maybe I left it off the iso.

***dangnubit*** I left it off the iso. Will update for RC.

Posted: **Thu Nov 30, 2017 7:51 am**

golden45 wrote:mx 17 beta 3 on 32 bit still stops at cli-installer

can you elaborate? Do you mean you don't get an XFCE desktop?

can you post inxi -F for your machine?

Posted: **Thu Nov 30, 2017 7:53 am**

richb wrote:generally you set up a connection twice.

1. on the live media, (if you bother to do so, I usually don't unless I'm using a live stick).
2. again after initial reboot.

If its not working as above (which has been the same for every release except alpha 1, which I messed up with
some interfaces stuff), then we need more info.

Install methodolgy
type of network
vpns?
inxi -n
is this after a hibernate or a cold restart?

and so forth.
I did not set it up in live,

And did not check the box until after several boots, some cold some restarts. Once checked it auto-connects. Si it is working as expected.

no I don't think it is working as expected. I don't have to check the box.

Does anyone else?

Posted: **Thu Nov 30, 2017 7:54 am**

In MX17 how is the user to add a logo or photo for his user image, especially in the Whisker menu? I don't see that mugshot is included - is there another way?

Posted: **Thu Nov 30, 2017 8:01 am**

@D_O re Network Manager: Yes I should have said it is working as I expected, not imply as it should be working.

Posted: **Thu Nov 30, 2017 8:05 am**

skiddoo, do those graphical problems all result after running mx-viewer? and are they running in a virtual machine or on actual hardware (I think hardware is what you said but confirming)?

Posted: **Thu Nov 30, 2017 8:33 am**

nathan2423 wrote:In MX17 how is the user to add a logo or photo for his user image, especially in the Whisker menu? I don't see that mugshot is included - is there another way?

Check Users Manual, Section 3.8.7. IIRC Whisker then picks that up .face image, would have to check if not

Posted: **Thu Nov 30, 2017 8:54 am**

In post 31 of this thread last night I posted my b3 results.

Stability testing...not so good.
I went down this morning to the machine and faced a log in.
Last night after the post, I left the desk top open (not hibernated), and came down to see a log in prompt.

So, I logged in, and checked the uptime, it was 7 hours something.

So, the machine had auto logged out, or crashed and rebooted at midnight last night.

Anything I can check?

Posted: **Thu Nov 30, 2017 8:55 am**

entropyfoe wrote:In post 31 of this thread last night I posted my b3 results.

Stability testing...not so good.
I went down this morning to the machine and faced a log in.
Last night after the post, I left the desk top open (not hibernated), and came down to see a log in prompt.

So, I logged in, and checked the uptime, it was 7 hours something.

So, the machine had auto logged out, or crashed and rebooted at midnight last night.

Anything I can check?

might be something in the /var/log/syslog* files.

Posted: **Thu Nov 30, 2017 9:10 am**

Jerry3904 wrote:
nathan2423 wrote:In MX17 how is the user to add a logo or photo for his user image, especially in the Whisker menu? I don't see that mugshot is included - is there another way?
Check Users Manual, Section 3.8.7. IIRC Whisker then picks that up .face image, would have to check if not

You also need to upload the image in lightdm greeter. Just putting it in .face does not work. Also it does not show in the whisker menu.

Posted: **Thu Nov 30, 2017 9:17 am**

Is that a correction or an addition to what we have in the Manual Section i referred to:

You can have the login greeter show an image as follows:
• Create or select an image, and use gthumb or another photo editor to resize it to about 96x96 pixels
• Save that image in your home folder as .face (make sure to include the dot and do not add any extension such as jpg or png).
• Click All Settings > LightDM GTK+ Greeter Settings, Appearance tab: turn on the User image switch.
• Log out, and you will see the image next to the login box; it will also show up in Whisker menu.

Posted: **Thu Nov 30, 2017 9:26 am**

Hold on I screwed up and created a .face folder not a .face image

Posted: **Thu Nov 30, 2017 9:26 am**

Jerry3904 wrote:
nathan2423 wrote:In MX17 how is the user to add a logo or photo for his user image, especially in the Whisker menu? I don't see that mugshot is included - is there another way?
Check Users Manual, Section 3.8.7. IIRC Whisker then picks that up .face image, would have to check if not

The procedure in the manual is correct.

Chris

Posted: **Thu Nov 30, 2017 9:33 am**

chrispop99 wrote:
Jerry3904 wrote:
nathan2423 wrote:In MX17 how is the user to add a logo or photo for his user image, especially in the Whisker menu? I don't see that mugshot is included - is there another way?
Check Users Manual, Section 3.8.7. IIRC Whisker then picks that up .face image, would have to check if not
The procedure in the manual is correct.

Chris

Confirmed.

Posted: **Thu Nov 30, 2017 10:00 am**

Thanks for the responses on this. If mugshot also creates an image that gets into the lightdm greeting, might it not be a good idea to include mugshot?

https://smdavis.us/2013/07/27/mugshot-q ... er-config/

(but I don't see on first glance that the greeter would pick it up)
Supported Applications
Currently, LibreOffice and Pidgin are the only supported external applications. Other applications that retrieve user information from /etc/passwd will also be updated (including Abiword and Gnumeric). This ultimately provides a wide coverage of desktop and terminal Linux applications.

Posted: **Thu Nov 30, 2017 10:04 am**

nathan2423 wrote:Thanks for the responses on this. If mugshot also creates an image that gets into the lightdm greeting, might it not be a good idea to include mugshot?

https://smdavis.us/2013/07/27/mugshot-q ... er-config/

(but I don't see on first glance that the greeter would pick it up)
Supported Applications
Currently, LibreOffice and Pidgin are the only supported external applications. Other applications that retrieve user information from /etc/passwd will also be updated (including Abiword and Gnumeric). This ultimately provides a wide coverage of desktop and terminal Linux applications.

But i see mugshot is referenced in Whisker documentation - http://www.webupd8.org/2015/02/whisker- ... it-in.html
Most important changes in the latest Whisker Menu 1.5.0:
added option to set background opacity;
added profile picture and a command which allows editing the profile picture (via Mugshot);
added customizable limit for recently used;
added support for non-square panel button icon;
added items of Xfce settings manager to allow searching;

Posted: **Thu Nov 30, 2017 10:20 am**

Mugshot has never worked during testing, so we don't include it. Not totally sure it still doesn't work, however, so we should test it now on B3. Thanks.

Posted: **Thu Nov 30, 2017 10:22 am**

Installed it and got an error when I ran it

Code: Select all

$ mugshot
Traceback (most recent call last):
  File "/usr/bin/mugshot", line 36, in <module>
    mugshot.main()
  File "/usr/lib/python3/dist-packages/mugshot/__init__.py", line 47, in main
    window = MugshotWindow.MugshotWindow()
  File "/usr/lib/python3/dist-packages/mugshot_lib/Window.py", line 52, in __new__
    new_object.finish_initializing(builder)
  File "/usr/lib/python3/dist-packages/mugshot/MugshotWindow.py", line 228, in finish_initializing
    self.init_user_details()
  File "/usr/lib/python3/dist-packages/mugshot/MugshotWindow.py", line 271, in init_user_details
    user_details = self.get_user_details()
  File "/usr/lib/python3/dist-packages/mugshot/MugshotWindow.py", line 654, in get_user_details
    as_data = self.get_accounts_service_data()
  File "/usr/lib/python3/dist-packages/mugshot/MugshotWindow.py", line 706, in get_accounts_service_data
    name = self.split_name(name)
  File "/usr/lib/python3/dist-packages/mugshot/MugshotWindow.py", line 686, in split_name
    parts = name.split()
AttributeError: 'bool' object has no attribute 'split'

Also no menu entry. Tried rebooting, no change. Lots of complaints in a web search on "mugshot fails," and there is recent detail in the Arch Wiki.

That is why we came up with an alternative method in the first place.

Posted: **Thu Nov 30, 2017 10:51 am**

Do we normally ship with PCManFM installed? I was surprised to see it!

Chris

Posted: **Thu Nov 30, 2017 10:57 am**

chrispop99 wrote:Do we normally ship with PCManFM installed? I was surprised to see it!

Chris

It isn't on the 32 bit beta3.

Posted: **Thu Nov 30, 2017 10:57 am**

anticapitalista wrote:
chrispop99 wrote:Do we normally ship with PCManFM installed? I was surprised to see it!

Chris
It isn't on the 32 bit beta3.

not on 64 bit either, at least I don't think so. (just realized the live-USB in my pocket is still b2).

anybody else got it?

Posted: **Thu Nov 30, 2017 11:01 am**

dolphin_oracle wrote:
anticapitalista wrote:
chrispop99 wrote:Do we normally ship with PCManFM installed? I was surprised to see it!

Chris
It isn't on the 32 bit beta3.9/quote]

not on 64 bit either, at least I don't think so. (just realized the live-USB in my pocket is still b2).
anybody else got it?

I do not.

apt-cache policy pcmanfm

Code: Select all

pcmanfm:
  Installed: (none)
  Candidate: 1.2.5-3
  Version table:
     1.2.5-3 500
        500 http://debian.mirror.frontiernet.net/debian stretch/main amd64 Packages

Posted: **Thu Nov 30, 2017 11:39 am**

Posted: **Thu Nov 30, 2017 11:45 am**

It was brought in when I test-installed LXDE to help someone else - sorry!

I blame the cold meds I'm taking, and the cough that forced me out of bed at 5am today.

Chris

Posted: **Thu Nov 30, 2017 12:42 pm**

Jerry3904 wrote:Mugshot has never worked during testing, so we don't include it. Not totally sure it still doesn't work, however, so we should test it now on B3. Thanks.

I installed it, and per feedback in the Arch community discussion, installed accountsservice as well
It shows up in the Settings Menu with the title About Me and it works fine.
In order for it to be picked up by WhiskerMenu you need to right-click on WhiskerMenu -> Properties -> Commands (tab) and check the Edit Profile box.

Posted: **Thu Nov 30, 2017 1:29 pm**

Just downloaded Beta 3 and during live usb boot I noticed the intel microcode msg still appears as I reported in beta2 (viewtopic.php?f=94&t=43278&start=160#p427207)

Some suggestions:
1 Add pcmanfm in order to Baobab (disk usage analyzer) be able open directories (it does not work with thunar, at least I can't make it work...)
2 Enable sound events by default (as suggest in a previous post)
3 Consider replacing Clementine by Guayadeque (it has a great online radio support and many other functionalities, also GTK based)
4 Mugshot would be a great addition...
5 Add templates to "Templates" folder; as MX comes with libreoffice installed I think it is good to improve user experince (see attached image)

Posted: **Thu Nov 30, 2017 1:33 pm**

I actually don't know if it works on live or not. If someone could try I would be obliged (I don't have any nvidia cards).
I don't think it can; a re-boot is suggested:

Screenshot.png

Yes, failure due to reboot (and the script isn't aware of the need to repack live-initramfs).
My most recent attempt (probably sgfxi, back around antiX15-b3) failed, and ingrained a "gun shy" outlook.
At the time, IIRC someone posted to insist "is possible" but I don't recall the details/workaround.
Now am wondering: install driver, immediately followed by live-remaster during the same session, would workaround?

Posted: **Thu Nov 30, 2017 1:35 pm**

skidoo wrote:
I actually don't know if it works on live or not. If someone could try I would be obliged (I don't have any nvidia cards).
I don't think it can; a re-boot is suggested:

Screenshot.png
Yes, failure due to reboot (and the script isn't aware of the need to repack live-initramfs).
My most recent attempt (probably sgfxi, back around antiX15-b3) failed, and ingrained a "gun shy" outlook.
At the time, IIRC someone posted to insist "is possible" but I don't recall the details/workaround.
Now am wondering: install driver, immediately followed by live-remaster during the same session, would workaround?

possibly. the nvidia driver loads as a kms driver module. In most cases, you don't even need the xorg.conf.

maybe we should have some sort of limit, to install only if persistence file is found. If that works. If it doesn't, we can set it to only work in an installed case. Its relatively easy to detect the live system.

Posted: **Thu Nov 30, 2017 1:49 pm**

do those graphical problems all result after running mx-viewer? and are they running in a virtual machine or on actual hardware
(I think hardware is what you said but confirming)?

Yes, my testing is always performed on actual hardware.

Yes, launching mx-viewer was the common ingredient across that batch of tests ~~ during that batch of tests, I was assessing the availability of per-item help.
Isn't it easily reproduceable? Both the tool window and the mx-viewer window are positioned, auto-centered. The artifacting appears in parent window as soon as you drag the mx-viewer window (intending to place it side-by-side with its overlapped parent window).

Posted: **Thu Nov 30, 2017 1:50 pm**

skidoo wrote:
do those graphical problems all result after running mx-viewer? and are they running in a virtual machine or on actual hardware
(I think hardware is what you said but confirming)?
Yes, my testing is always performed on actual hardware.

Yes, launching mx-viewer was the common ingredient across that batch of tests ~~ during that batch of tests, I was assessing the availability of per-item help.
Isn't it easily reproduceable? Both the tool window and the mx-viewer window are positioned, auto-centered. The artifacting appears in parent window as soon as you drag the mx-viewer window (intending to place it side-by-side with its overlapped parent window).

Yeah, I can reproduce it here. At the time, I didn't have a mx machine in front of me. I just checked it at lunch.

Posted: **Thu Nov 30, 2017 1:51 pm**

timkb4cq wrote:
Jerry3904 wrote:Mugshot has never worked during testing, so we don't include it. Not totally sure it still doesn't work, however, so we should test it now on B3. Thanks.
I installed it, and per feedback in the Arch community discussion, installed accountsservice as well
It shows up in the Settings Menu with the title About Me and it works fine.
In order for it to be picked up by WhiskerMenu you need to right-click on WhiskerMenu -> Properties -> Commands (tab) and check the Edit Profile box.

Good. I meant to follow up on the Arch discussion, but have been diverted. That works great, and I'm good with putting it in the RC as long as we can bring accountsservice in with it during installation.

Posted: **Thu Nov 30, 2017 2:00 pm**

timkb4cq wrote:
Jerry3904 wrote:Mugshot has never worked during testing, so we don't include it. Not totally sure it still doesn't work, however, so we should test it now on B3. Thanks.
I installed it, and per feedback in the Arch community discussion, installed accountsservice as well
It shows up in the Settings Menu with the title About Me and it works fine.
In order for it to be picked up by WhiskerMenu you need to right-click on WhiskerMenu -> Properties -> Commands (tab) and check the Edit Profile box.

Confirmed that procedure worked for me.

Chris

Posted: **Thu Nov 30, 2017 2:04 pm**

Great--I put a request into Tracker so DO could follow it

Posted: **Thu Nov 30, 2017 4:10 pm**

Realtek Wifi usb dongle not working
I have this setup:

inxi -n
Network: Card-1: Intel Ethernet Connection I217-V driver: e1000e
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 94

80:ba:3f:7e
Card-2: Realtek RTL8188SU 802.11n WLAN Adapter driver: r8712u
IF: wlan0 state: N/A mac: N/A

After booting WIFI won' t work out of the box I had to edit
/etc/NetworkManager/NetworkManager.conf and add the following lines:

[device]
wifi.scan-rand-mac-address=no

After reboot/restart service it works as expected.

Posted: **Thu Nov 30, 2017 4:30 pm**

Thanks for the feedback.

Posted: **Thu Nov 30, 2017 4:47 pm**

Jerry3904 wrote:Thanks for the feedback.

is that something that can be by default?

Posted: **Thu Nov 30, 2017 4:56 pm**

I took a note about it b/c I had the same question. Kent hasn't been on the Forum for quite a while, but probably knows best.

Posted: **Thu Nov 30, 2017 5:05 pm**

https://xfce.space/en/2017/11/mx-linux- ... hgeklickt/
a review/walkthrough, titled "MX Linux 17: the third beta version clicked through"
(like, a paragraph, plus 5 screenshots)

Posted: **Thu Nov 30, 2017 5:14 pm**

I read that and thanked him für den schnellen Durchblick when he tweeted a link to @MX_Linux.

Pretty weak complaint IMO, since there is the Help button...

Posted: **Thu Nov 30, 2017 7:37 pm**

Impressive. Very good first impression. Running live on an old beater hand-me-down I just got. Vista would barely pull itself; MX is spunky, and thats running from a DVD. Maybe I'll finally update from my old M11...

Code: Select all

demo@mx1:~
$ inxi -F
System:    Host: mx1 Kernel: 4.13.0-1-686-pae i686 bits: 32 Desktop: Xfce 4.12.3
           Distro: MX-17.b3_386 Horizon November 28, 2017
Machine:   Device: portable System: Gateway product: MT6705 v: 3408385R serial: N/A
           Mobo: Gateway model: N/A v: 77.09 serial: N/A BIOS: Phoenix v: 77.09 date: 11/27/2006
Battery    BAT1: charge: 39.4 Wh 99.7% condition: 39.5/51.8 Wh (76%)
CPU:       Dual core Intel T2060 (-MCP-) cache: 1024 KB
           clock speeds: max: 1600 MHz 1: 1600 MHz 2: 1600 MHz
Graphics:  Card: Intel Mobile 945GM/GMS 943/940GML Express Integrated 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 945GM x86/MMX/SSE2 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-1-686-pae
Network:   Card-1: Marvell 88E8038 PCI-E Fast Ethernet Controller driver: sky2
           IF: eth0 state: down mac: 00:e0:b8:c4:bc:fe
           Card-2: Realtek RTL8187 Wireless Adapter
           IF: N/A state: N/A mac: N/A
Drives:    HDD Total Size: NA (-)
           ID-1: /dev/sda model: WDC_WD1200BEVS size: 120.0GB
Partition: ID-1: / size: 1.6G used: 49M (4%) fs: overlay dev: N/A
Sensors:   System Temperatures: cpu: 48.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 11 min Memory: 458.5/2009.5MB Client: Shell (bash) inxi: 2.3.43 
demo@mx1:~

Posted: **Thu Nov 30, 2017 7:48 pm**

Maybe I'll finally update from my old M11...

We'd be glad to have you back in the thick of things.

Posted: **Thu Nov 30, 2017 7:59 pm**

Jerry3904 wrote:
Maybe I'll finally update from my old M11...
We'd be glad to have you back in the thick of things.

Be careful what you ask for... my reputation precedes me.

Posted: **Thu Nov 30, 2017 8:02 pm**

@UM...checkin' out your age there...2016...that's very old

Posted: **Thu Nov 30, 2017 8:20 pm**

Paul.. wrote:@UM...checkin' out your age there...2016...that's very old

Hmmm....

Posted: **Thu Nov 30, 2017 8:44 pm**

And down we go...

Posted: **Thu Nov 30, 2017 8:55 pm**

dolphin_oracle wrote:
golden45 wrote:mx 17 beta 3 on 32 bit still stops at cli-installer

can you elaborate? Do you mean you don't get an XFCE desktop?

can you post inxi -F for your machine?

I'm running an older intel p4 with 3 g of ram - computer with sis drivers.On boot from dvd Everything works well until it tries to boot the display.Then it stops asking for root login and root password to use the cli-installer and follow instructions.No I can't get to the XFCE desktop.thanks john

Posted: **Thu Nov 30, 2017 9:00 pm**

golden45 wrote:
dolphin_oracle wrote:
golden45 wrote:mx 17 beta 3 on 32 bit still stops at cli-installer

can you elaborate? Do you mean you don't get an XFCE desktop?

can you post inxi -F for your machine?
I'm running an older intel p4 with 3 g of ram - computer with sis drivers.On boot from dvd Everything works well until it tries to boot the display.Then it stops asking for root login and root password to use the cli-installer and follow instructions.No I can't get to the XFCE desktop.thanks john

Ok.

Please.try the safe or.failsafe options please.

Posted: **Thu Nov 30, 2017 9:02 pm**

I've had no trouble with MX 16.1 november update It booted to the desktop I then installed the os using the installer and it runs great.Very nice os thanks to all.John

Posted: **Thu Nov 30, 2017 9:06 pm**

golden45 wrote:I've had no trouble with MX 16.1 november update It booted to the desktop I then installed the os using the installer and it runs great.Very nice os thanks to all.John

There is no safe menu on boot of dvd I will try and download again with a check of the download.Thanks John

Posted: **Thu Nov 30, 2017 9:19 pm**

golden45 wrote:There is no safe menu on boot of dvd I will try and download again with a check of the download.Thanks John

This is a bug! Downloading again won't help.

edit: You can type in these boot parameters "nomodeset vga=safe" instead of using the missing F6 menu.

Posted: **Thu Nov 30, 2017 9:29 pm**

I just tried to boot dvd again--It booted fine until it displayed en
en
Localizing thunar custom actions
Welcome To MX 17.b3(Horizon)32 bit pae
For command line install login as root (password root) enter the command cli-installer Follow the instructions.
MX1 Login: It then stops and waits
Thanks John

Posted: **Fri Dec 01, 2017 5:23 am**

dolphin_oracle wrote:
Jerry3904 wrote:Thanks for the feedback.
is that something that can be by default?

I have been looking at this. The firmware-realtek package we have installed does not list this. According to a post on the Ubuntu forum there is firmware missing that can be gotten here:

Code: Select all

wget http://launchpadlibrarian.net/37387612/rtl8192sfw.bin.gz

I was able to download it, so it still exists, but I have no way to test if that would take care of the problem.

Posted: **Fri Dec 01, 2017 6:09 am**

Jerry3904 wrote:
dolphin_oracle wrote:
Jerry3904 wrote:Thanks for the feedback.
is that something that can be by default?
I have been looking at this. The firmware-realtek package we have installed does not list this. According to a post on the Ubuntu forum there is firmware missing that can be gotten here:
Code: Select all
wget http://launchpadlibrarian.net/37387612/rtl8192sfw.bin.gz
I was able to download it, so it still exists, but I have no way to test if that would take care of the problem.

The only reference I found about this was in archlinux wiki:
https://wiki.archlinux.org/index.php/Ne ... domization
I think its not only related to realtek, not sure though...
This is also referenced in wiki page:
https://blogs.gnome.org/thaller/2016/08 ... ger-1-4-0/

Posted: **Fri Dec 01, 2017 6:16 am**

Thanks again. Not sure atm what we should do about this exactly, but will do some testing.

Posted: **Fri Dec 01, 2017 1:35 pm**

Is it working without problems to update from beta 2 to 3 or final after beta 2 has been installed?

I updated from MX-16 to MX-17 (live distro with persistent home) and got some grafical problems (e.g fonts and no transparent background in terminal). I'm not completely happy with the visual options, e.g. in FF the current tab isn't looking well (see Attachment) with MediterranianTributeDark Theme, because it is not in one color. [EDIT: Resolved by reboot] These problem might be related because I was keeping my home dir, which is why I'd like to know if I could install MX-17B2 or B3 now, and then update later.

Thanks for the whole work, of course, I wouldn't use it if I wouldn't like. Had some Windows for some days on my new PC, not generally bad but I'll stick with MX which seems even to start much faster.

Posted: **Fri Dec 01, 2017 1:51 pm**

darth.severus wrote:Is it working without problems to update from beta 2 to 3 or final after beta 2 has been installed?

I updated from MX-16 to MX-17 (live distro with persistent home) and got some grafical problems (e.g fonts and no transparent background in terminal). I'm not completely happy with the visual options, e.g. in FF the current tab isn't looking well (see Attachment) with MediterranianTributeDark Theme, because it is not in one color. These problem might be related because I was keeping my home dir, which is why I'd like to know if I could install MX-17B2 or B3 now, and then update later.

Thanks for the whole work, of course, I wouldn't use it if I wouldn't like. Had some Windows for some days on my new PC, not generally bad but I'll stick with MX which seems even to start much faster.

Updating from beta releases is never good practice, and most Linux distributions won't support it.

It is often the case that you can upgrade from a release candidate to final, but as there is usually only a short time between those releases, there seems little point.

Chris

Posted: **Fri Dec 01, 2017 1:51 pm**

I tried to view a heap of pics saved as png files on a test machine and when I went to view them, feh was the default - YUK!. I ended up with over 20 instances of feh in the taskbar that had to be closed individually, a task not made easy on a laptop when no external mouse is available. Having the default set to feh needs to be a users choice, not a default, especially when it's 1000 times easier to open one image with nomacs and then arrow through all other images in the directory.

Posted: **Fri Dec 01, 2017 1:53 pm**

m_pav wrote:I tried to view a heap of pics saved as png files on a test machine and when I went to view them, feh was the default - YUK!. I ended up with over 20 instances of feh in the taskbar that had to be closed individually, a task not made easy on a laptop when no external mouse is available. Having the default set to feh needs to be a users choice, not a default, especially when it's 1000 times easier to open one image with nomacs and then arrow through all other images in the directory.

It's already been reported as an oversight. The default will be Nomacs, and the next release will have that pre-set as the default.

Chris

Posted: **Fri Dec 01, 2017 3:47 pm**

Cool.

I saw a post on the MX facebook page from a user who complained about our GRUB and whether the user is right or wrong, I have to say I have experienced an issue with GRUB on not a few occasions when using my ageing Lenovo E330 laptop. This model is known for having some issues with the bios, however, the repeated failures of GRUB to "work" after installation under a certain process validate the facebook users complaint.

Here's the condition:
boot from LiveUSB, use the partitioner in the installer to blank the disk, create a new MS-DOS partition table and create 3 new partitions, 20G /, 80G /home and 3G swap. Install to existing partitions and install GRUB to MBR. On reboot without the LiveUSB, nothing, BIOS is looking for a bootable device. re-insert liveUSB, boot live and set about repairing GRUB, result = status quo, it reports nothing to repair and testing via reboot confirms nothing has changed.

This I repeated 2x last night with the same result, however, on the 3rd attempt, I let the installer use the whole drive and auto-partition it, GRUB to MBR, rebooted to GRUB and onto the fresh installation without a problem.

I repeated this procedure on 2 other machines with no issues, custom partitioning et al, boots to grub without an issue, but on my little Lenovo, nothing whatsoever.

In my opinion, this is a hardware combination issue where a number of factors determine the outcome. Lenovos shonky BIOS doesn't help, but as an aside, I'm using a M.2 128GB SSD hosted in an adapter to fit into a standard SATA port within the machine. At the time, it was the cheapest way for me to get this thing sped up and we pay more than double what other larger countries pay for their hardware while our incomes are much the same or less in dollar value.

I've had this laptop for about 4 years since new and I did not have this type of problem when I had a 2.5" 250GB SSD installed in the machine, firstly running Linux only, and secondly with with a dual boot installation with Windows7 and Linux.

In my experience, the issue reported by the facebook user is directly related to hardware and BIOS combinations and how our installer operates, NOT installed operating systems. It's no secret that in an effort to keep prices down, OEM's try to cut corners and in doing so, cater only for Microsofts products with no regard whatsoever for users choice, thereby distancing themselves from "industry standards". Claiming Ubuntu as the benchline for operations is a misnomer because they have gotten into bed with Microsoft and are therefore partially aided by the same, so it comes as no surpirse the ewwbuntu works in the fringe areas whereas ours fails.

I write all of this because we need to 1, try to find a way to make it work in the fringe area, or 2, be fully aware of it and deal with it appropriately.

Posted: **Fri Dec 01, 2017 3:53 pm**

that is a rather exhaustive write up.

out of curiosity, when you did the manual partitioning, did you set a boot flag? I think the auto-partitioner does this.

Posted: **Fri Dec 01, 2017 4:01 pm**

Boot flag should not be necessary with GRUB to MBR as evidenced by my other install tests to different hardware.

Posted: **Fri Dec 01, 2017 4:06 pm**

m_pav wrote:Boot flag should not be necessary with GRUB to MBR as evidenced by my other install tests to different hardware.

maybe not, but its a difference between the auto-install and possibly manual install.

we use this:

parted -s $dev set 1 boot on

Posted: **Fri Dec 01, 2017 6:35 pm**

OK, I've checked the other laptop I test installed onto and there are no partitions marked with the boot flag, yet it still boots. I checked the current installation and sure enough, the / partition had been marked as bootable, so I reset my E330, installed as before to manual partitions and achieved the same no-boot result. I set the boot flag and it booted to t fresh manual partition install, so it seems to me, the way forward with this on MBR drives with manual or existing partitions to set have the installer set the boot flag on the partition used for the / install, however, with efi installations, it may be a totally different matter as I have experienced the same non-boot issue there.

I'll have to spend some time on my E330 to check it further with an EFI installation, but i have family stuff to do for the rest of the day, so will try to have a go tonight.

Posted: **Fri Dec 01, 2017 7:29 pm**

chrispop99 wrote:
darth.severus wrote:Is it working without problems to update from beta 2 to 3 or final after beta 2 has been installed?

I updated from MX-16 to MX-17 (live distro with persistent home) and got some grafical problems (e.g fonts and no transparent background in terminal). I'm not completely happy with the visual options, e.g. in FF the current tab isn't looking well (see Attachment) with MediterranianTributeDark Theme, because it is not in one color. These problem might be related because I was keeping my home dir, which is why I'd like to know if I could install MX-17B2 or B3 now, and then update later.

Thanks for the whole work, of course, I wouldn't use it if I wouldn't like. Had some Windows for some days on my new PC, not generally bad but I'll stick with MX which seems even to start much faster.
Updating from beta releases is never good practice, and most Linux distributions won't support it.

It is often the case that you can upgrade from a release candidate to final, but as there is usually only a short time between those releases, there seems little point.

Chris

The Mediterranean themes have been removed from beta 3 along with many others that don't work right on the new platform.

Posted: **Fri Dec 01, 2017 7:33 pm**

dolphin_oracle wrote:
golden45 wrote:
dolphin_oracle wrote:

can you elaborate? Do you mean you don't get an XFCE desktop?

can you post inxi -F for your machine?
I'm running an older intel p4 with 3 g of ram - computer with sis drivers.On boot from dvd Everything works well until it tries to boot the display.Then it stops asking for root login and root password to use the cli-installer and follow instructions.No I can't get to the XFCE desktop.thanks john
Ok.

Please.try the safe or.failsafe options please.

I'm sure the culprit is that SIS graphics. I have to wonder if that antiX sis driver is going to work with the newer xorg stack in MX 17.

Posted: **Fri Dec 01, 2017 7:36 pm**

Is it correct that not even the generic CUPS pdf printer is set up in a default install?

Posted: **Fri Dec 01, 2017 7:52 pm**

nathan2423 wrote:Is it correct that not even the generic CUPS pdf printer is set up in a default install?

It's there in my install to HDD.

Cups.png

Posted: **Fri Dec 01, 2017 8:09 pm**

Hmm - I went to Print .. Settings.. using the Whisker menu and it was not there on mine (I installed beta 3 to hard disk about two days ago)

Posted: **Fri Dec 01, 2017 8:35 pm**

nathan2423 wrote:Hmm - I went to Print .. Settings.. using the Whisker menu and it was not there on mine (I installed beta 3 to hard disk about two days ago)

It's installed by default...Just right-click on a web page and select Print...then you will see the preview page with "save as PDF" as the default on left.

Posted: **Fri Dec 01, 2017 9:02 pm**

All installed well here. I note that https://mxlinux.org/wiki/system/wine may need revision to note that winetricks is included in MX-17 when installed via Package Manager and need not be obtained separately, as the wiki advises in previous versions of MX.

Used MX-17 Grub for MBR amd customised with MX GC without any issues. Conky default looks fine on 1680x1050 display.
Bluetooth functionality checks out good, along with wifi dongle (this can be slow to initialise but networking is activated late in startup services anyway these days I believe).
Google Chrome doesn't import FF settings. Used saved 'bookmark.html ' to import favorites.
Checked/unchecked Power Manager Panel icon in settings to remove.

Code: Select all

System:    Host: mx1 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b3_x64 Horizon November 29, 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: 2136 MHz 2: 2136 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-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 (44.0% used)
           ID-1: /dev/sda model: WDC_WD10EZEX size: 1000.2GB
Partition: ID-1: / size: 49G used: 7.1G (16%) 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: 170 Uptime: 8 min Memory: 1077.2/3920.8MB Client: Shell (bash) inxi: 2.3.43

Posted: **Fri Dec 01, 2017 9:05 pm**

tascoast, Thanks for the feedback.

Posted: **Sat Dec 02, 2017 7:07 am**

I can only say one thing MX is improving from version to version the conkys are good and all the features are awesome
1) However i couldn't find anything like themes in MX package installer i think some one in the dev team told me that we will include them

Removed themes in the appearance tab this is actually very good got rid of ugly themes

(Thanks for considering my suggestion)
2) My suggestion regarding MX package installer that change the interface as that of settings manager in XFCE as attached in the screenshot so that it will be much easier to access

Thanks when we can expect the Final Version approximately ..

Posted: **Sat Dec 02, 2017 7:13 am**

However i couldn't find anything like themes in MX package installer i think some one in the dev team told me that we will include them

Just hasn't happened yet...a lot is going on.

Posted: **Sat Dec 02, 2017 7:26 am**

Jerry3904 wrote:
However i couldn't find anything like themes in MX package installer i think some one in the dev team told me that we will include them
Just hasn't happened yet...a lot is going on.

Thanks Jerry

Posted: **Sat Dec 02, 2017 11:29 am**

Working on the Manual, saw this for the umpteenth time: the dialog box for pkexec is extremely wide (it overwhelms my testing machine). I can't find a config file for it, but it would be preferable to shrink the length in half, or so.

Posted: **Sat Dec 02, 2017 2:03 pm**

Arista Multimedia Transcoder does not install from MXPI.

Chris

Posted: **Sat Dec 02, 2017 2:13 pm**

Jerry3904 wrote:Working on the Manual, saw this for the umpteenth time: the dialog box for pkexec is extremely wide...

As far as I can determine, the basic layout is determined by polkit-gnome-authentication-agent-1. It is hard-coded in src/polkitgnomeauthenticationdialog.c
It's probably not a package I should try to modify and rebuild, and we are a bit late in the process to switch to another authentication agent.

Posted: **Sat Dec 02, 2017 2:31 pm**

ok, thanks

Posted: **Sat Dec 02, 2017 3:15 pm**

vamsi wrote:i couldn't find anything like themes in MX package installer i think some one in the dev team told me that we will include them

opendesktop.org 800+ XFCE themes

Would be helpful to split this from the beta-testing topic, into a topic dedicated to reporting:

themes folks have test-installed (to confirm working) and that they recommend for inculsion within a future curated collection.
(and, for each recommended candidate, the url of its screenshots+download page)

Posted: **Sat Dec 02, 2017 4:02 pm**

skidoo wrote:
vamsi wrote:i couldn't find anything like themes in MX package installer i think some one in the dev team told me that we will include them
opendesktop.org 800+ XFCE themes

Would be helpful to split this from the beta-testing topic, into a topic dedicated to reporting:

themes folks have test-installed (to confirm working) and that they recommend for inculsion within a future curated collection.
(and, for each recommended candidate, the url of its screenshots+download page)

We also seemed to have dropped the greybird themes ported over from Debian that provided greybird-accessability and -compact window decorations.

Scratch that---I was looking in the wrong settings, they are there.

Posted: **Sat Dec 02, 2017 4:06 pm**

hard-coded in src/polkitgnomeauthenticationdialog.c
It's probably not a package I should try to modify and rebuild

Please do (and post to xfce.org to announce its availability)
It's a several-years-long outstanding bug, and affects all of debian downstream XFCE, Cinnamon, and Unity (as acknowledged by debian here)

The package is (has been) seldom updated, so shouldn't need frequent followup attention.
I'm suggesting (but haven't tested) the following quick modifications:

gtk_window_set_resizable (GTK_WINDOW (dialog), TRUE);
. . .
gtk_widget_show_all (dialog->priv->table_alignment);
gtk_window_resize (dialog, 600, 480); /** TBD (blind to length of translation strings, I can't guess the ideal dimensions) **/
response = gtk_dialog_run (GTK_DIALOG (dialog));

Posted: **Sat Dec 02, 2017 4:08 pm**

Interesting, skidoo.

Posted: **Sat Dec 02, 2017 4:11 pm**

chrispop99 wrote:Arista Multimedia Transcoder does not install from MXPI.

Chris

No doubt that is because it's not in any of the repos. I'll see if we can add it. But Ubuntu also dropped it after 14.04, so there may be something wrong with it.

Posted: **Sat Dec 02, 2017 4:18 pm**

Stevo wrote:
chrispop99 wrote:Arista Multimedia Transcoder does not install from MXPI.

Chris
No doubt that is because it's not in any of the repos. I'll see if we can add it. But Ubuntu also dropped it after 14.04, so there may be something wrong with it.

It also seems to have not been updated for some years, so maybe remove it?

Chris

Posted: **Sat Dec 02, 2017 4:22 pm**

mentioning because audacity seems to me like a high-profile {didn't check popcon stats} application

Installed via MX PackageInstaller, no audacity entry appears in the XFCE menu. (tested: same result if installed via synaptic)
a .desktop file is installed, an associated imagefile icon is installed, and MenuEditor recognizes the category assignments
...so, it's a headscratcher

Posted: **Sat Dec 02, 2017 4:41 pm**

chrispop99 wrote:
Stevo wrote:
chrispop99 wrote:Arista Multimedia Transcoder does not install from MXPI.

Chris
No doubt that is because it's not in any of the repos. I'll see if we can add it. But Ubuntu also dropped it after 14.04, so there may be something wrong with it.
It also seems to have not been updated for some years, so maybe remove it?

Chris

Yes, it requires gstreamer-0.10, which isn't in Debian Stretch, so it needs to be removed. Perhaps to be replaced with qwinff, if I can port that up to MX 17.

Posted: **Sat Dec 02, 2017 4:44 pm**

another very good alternative is Selene, but it is not in the repositories or in MX PackageInstaller

Posted: **Sat Dec 02, 2017 4:48 pm**

skidoo wrote:mentioning because audacity seems to me like a high-profile {didn't check popcon stats} application

Installed via MX PackageInstaller, no audacity entry appears in the XFCE menu. (tested: same result if installed via synaptic)
a .desktop file is installed, an associated imagefile icon is installed, and MenuEditor recognizes the category assignments
...so, it's a headscratcher

It appears in the menu on my installed 64-bit b3.

Posted: **Sat Dec 02, 2017 5:18 pm**

skidoo, I installed audacity with synaptic.

I have an entry for audacity under the multimedia sub menu.
You were looking in the multimedia tab?

Posted: **Sat Dec 02, 2017 6:36 pm**

Repo manager. When I "Select fastest Debian repo for me" it doesn't change security and backports repos. Right? and Why? Thanks.

Posted: **Sat Dec 02, 2017 8:47 pm**

Stevo wrote:
chrispop99 wrote:
Stevo wrote:
No doubt that is because it's not in any of the repos. I'll see if we can add it. But Ubuntu also dropped it after 14.04, so there may be something wrong with it.
It also seems to have not been updated for some years, so maybe remove it?

Chris
Yes, it requires gstreamer-0.10, which isn't in Debian Stretch, so it needs to be removed. Perhaps to be replaced with qwinff, if I can port that up to MX 17.

I will remove Arista from MXPI.

Posted: **Sat Dec 02, 2017 9:54 pm**

skidoo wrote:
Timkb4cq wrote:hard-coded in src/polkitgnomeauthenticationdialog.c
It's probably not a package I should try to modify and rebuild
Please do (and post to xfce.org to announce its availability)
It's a several-years-long outstanding bug, and affects all of debian downstream XFCE, Cinnamon, and Unity...

OK, you talked me into it. policykit-1-gnome_0.105-6mx17 is now available in the Testing repository. The suggested patch wasn't quite correct but was very helpful (I really don't know gtk and am not very good at C). In any case it was only 2 lines changed in the dialog window settings so it shouldn't affect anything else.

It looks better here, but I'd like some people to test it (maybe with different locales) before announcing it to XFCE.
It takes a logout/login to take effect.

Posted: **Sun Dec 03, 2017 4:49 am**

It does look much better.

Posted: **Sun Dec 03, 2017 7:05 am**

timkb4cq wrote:
skidoo wrote:
Timkb4cq wrote:hard-coded in src/polkitgnomeauthenticationdialog.c
It's probably not a package I should try to modify and rebuild
Please do (and post to xfce.org to announce its availability)
It's a several-years-long outstanding bug, and affects all of debian downstream XFCE, Cinnamon, and Unity...
OK, you talked me into it. policykit-1-gnome_0.105-6mx17 is now available in the Testing repository. The suggested patch wasn't quite correct but was very helpful (I really don't know gtk and am not very good at C). In any case it was only 2 lines changed in the dialog window settings so it shouldn't affect anything else.

It looks better here, but I'd like some people to test it (maybe with different locales) before announcing it to XFCE.
It takes a logout/login to take effect.

Excellent work!

This has irritated me for a long time; I think I mentioned it during one of the Alpha rounds.

Tested on 2x64 machines, and 1x32. It's a great improvement on the lo-res 32-bit machine as the original dialogue went off-screen at each end.

Chris

Posted: **Sun Dec 03, 2017 7:34 am**

That's much better, thanks a lot!

On my testing machine, I can shrink the length fine, but there is a gap below the password field that limits shrinking the height

Posted: **Sun Dec 03, 2017 7:37 am**

A bug and a whine on the Settings screen:

bug: the ADSL/PPPOE entry lacks an icon and does not work, though works fine off the menu << put this in Tracker

whine: the iDevice Mounter is located under System, but really belongs under Hardware where Removable Drives and Media is

Posted: **Sun Dec 03, 2017 9:05 am**

Jerry3904 wrote:...I can shrink the length fine, but there is a gap below the password field that limits shrinking the height

I tried making it shorter but that's as skinny as it would go. I'm pretty sure that space is reserved for those authentication actions where you have to choose between specific users. It's where their icons go. Don't really want to mess with that in case some programs in the repos use that documented functionality.

When there are translations for MX-iDevice Mounter in github, I'll update the .desktop file to use Hardware instead of System.

Posted: **Sun Dec 03, 2017 12:01 pm**

I finally installed B3 on VB as well as on actual hardware, and for the first time in forever, I'm having trouble with the sound in MX Linux. Sound was also non-existent in live mode in VB before installation. I'd installed in the hope the sound would sort itself out but nope.

In both live and installed systems, I tried using MX-select-sound to switch between the HDMI and PCH cards. Neither appear to work - usually PCH is what works on this computer.

I'm wondering if it's a kernel issue because all the earlier versions of MX17 were fine even in VB.

Installation are all old-school MBR/Grub.

inxi below for the real metal install:

Code: Select all

System:    Host: mx17b3 Kernel: 4.13.0-1-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.3
           Distro: MX-17.b3_x64 Horizon November 29, 2017
Machine:   Device: desktop Mobo: MSI model: H97M-G43(MS-7924) v: 1.0 serial: N/A
           BIOS: American Megatrends v: V2.4 date: 07/22/2014
CPU:       Quad core Intel Core i5-4460 (-MCP-) cache: 6144 KB
           clock speeds: max: 3400 MHz 1: 3199 MHz 2: 3199 MHz 3: 3199 MHz 4: 3199 MHz
Graphics:  Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
           Display Server: x11 (X.Org 1.19.2 ) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Mesa DRI Intel Haswell Desktop version: 3.3 Mesa 13.0.6
Audio:     Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
           driver: snd_hda_intel
           Card-2 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-1-amd64
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: d8:cb:8a:12:38:3e
Drives:    HDD Total Size: 6129.2GB (0.3% used)
           ID-1: /dev/sda model: ADATA_SP900 size: 128.0GB
           ID-2: /dev/sdb model: WDC_WD30EZRX size: 3000.6GB
           ID-3: /dev/sdc model: WDC_WD30EZRX size: 3000.6GB
Partition: ID-1: / size: 21G used: 4.5G (24%) fs: ext4 dev: /dev/sdb1
           ID-2: swap-1 size: 16.00GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 187 Uptime: 9 min Memory: 721.9/15921.5MB Client: Shell (bash) inxi: 2.3.43

Posted: **Sun Dec 03, 2017 12:05 pm**

Occasionally sound in virtualbox routes thru the surround sound channel instead of the regular master.

There is a link to alsamixer in the xfce settings manager
Make sure the volumes are turned up. I have to do this with antix.

Posted: **Sun Dec 03, 2017 12:11 pm**

dolphin_oracle wrote:Occasionally sound in virtualbox routes thru the surround sound channel instead of the regular master.

There is a link to alsamixer in the xfce settings manager
Make sure the volumes are turned up. I have to do this with antix.

Real metal install also has no sound. But I'll go check on the alsamixer thingy.

After I sort out why the latest Manjaro updates has led to a grub menu with half of my distros missing from the list.

[UPDATED POST]
OK, tried "surround" and PCM (latter of which worked in the past with other distros), no success.

Ran alsamixer and turned vol to 100%. No change.

Screenshot.png

Argh.

Posted: **Sun Dec 03, 2017 12:50 pm**

Still going through Section 4 of the Manual, slow checking validity. Just discovered that indicator-keylock is not in our repos--Stevo needs to move it over from his build that is successful on Debian 9

https://software.opensuse.org//download ... or-keylock

Posted: **Sun Dec 03, 2017 12:54 pm**

The following MX Conkys:
1. geeky tower logo
2. Asq-clock
3. Asq-clock-new

all need to change the line referring to /etc/antix-version file, because in beta 3 the OS details are now in the /etc/mx-version file.

Posted: **Sun Dec 03, 2017 1:05 pm**

asqwerth wrote: Real metal install also has no sound. But I'll go check on the alsamixer thingy.

Use F6 in AlsaMixer to select your real soundcard and look for the AutoMut setting.
It ends up being enabled on about half my installs & I need to disable it for my sound to work. Once disabled it stays disabled.

Posted: **Sun Dec 03, 2017 1:07 pm**

asqwerth wrote:The following MX Conkys:
1. geeky tower logo
2. Asq-clock
3. Asq-clock-new

all need to change the line referring to /etc/antix-version file, because in beta 3 the OS details are now in the /etc/mx-version file.

Thanks. In spite of my declaration that I was done, I will put together one more revision for Final.

Posted: **Sun Dec 03, 2017 1:41 pm**

Is there anything else.looking for antix-version? We can put it back, or have both.

Posted: **Sun Dec 03, 2017 1:55 pm**

timkb4cq wrote:
asqwerth wrote: Real metal install also has no sound. But I'll go check on the alsamixer thingy.
Use F6 in AlsaMixer to select your real soundcard and look for the AutoMut setting.
It ends up being enabled on about half my installs & I need to disable it for my sound to work. Once disabled it stays disabled.

AutoMut was indeed enabled. However, after disabling, I still can't get any sound.

Time to sleep now, so I'll reboot and try again tomorrow.

Posted: **Sun Dec 03, 2017 2:24 pm**

How about replacing Orage calander with date and time gadgets on xfce and Orage calander when we click on it is poping on the middle of the screen which is not that effective whereas date and time gadget when we click on it it shows small area with the month and date which is cool. Ofcourse this is my suggestion

Thanks..

Posted: **Sun Dec 03, 2017 2:27 pm**

I prefer orage. It is more configurable. Of course one realizes this is a personal preference.

Posted: **Sun Dec 03, 2017 2:47 pm**

entropyfoe wrote:skidoo, I installed audacity with synaptic.

I have an entry for audacity under the multimedia sub menu.
You were looking in the multimedia tab?

oops? idunno. {blush} It was a late, late night testing session.

Yeah... what he said -----v

Posted: **Sun Dec 03, 2017 4:06 pm**

Jerry3904 wrote:Still going through Section 4 of the Manual, slow checking validity. Just discovered that indicator-keylock is not in our repos--Stevo needs to move it over from his build that is successful on Debian 9

https://software.opensuse.org//download ... or-keylock

OK, will see if I can fix up what I can now recognize as a now outdated build system while I'm at it, too. Oh, wait, that's already done in the OBS 3.0.2 version, so I'll just rebuild for MX 15 & 17.

Posted: **Sun Dec 03, 2017 4:09 pm**

Thanks.

Posted: **Sun Dec 03, 2017 4:16 pm**

richb wrote:I prefer orage. It is more configurable. Of course one realizes this is a personal preference.

Me too.

Chris

Posted: **Sun Dec 03, 2017 9:07 pm**

golden45 wrote:I've had no trouble with MX 16.1 november update It booted to the desktop I then installed the os using the installer and it runs great.Very nice os thanks to all.John

I did a fresh install of 16.1 and did a full dist-upgrade after changing to stretch repos.All went well.How do I change the background grub menu to the horizon background.Thanks john
It is running very well.

Posted: **Sun Dec 03, 2017 11:15 pm**

A quick intro to the MX-17 beta3 desktop and Thunar settings, highlighting some of the tools and versatility of xfce for the newer user
http://mxlinuxguide.blogspot.com.au/p/blog-page_64.html

Posted: **Mon Dec 04, 2017 2:07 am**

Hi

I Never noticed this before but why is there a right click menu in Thunar that says "Ownership to Root". Surely this is incredibly dangerous to new users. Especially if they use it on their Home Folder ? I won't try it as I am pretty sure I won't be able to login in again as I will no longer own my own Home Folder.

If someone wants to use such a powerful command then they should have to learn how to do it via terminal and all the learning that goes along with that.

Apologies if this is in the wrong thread. Please move as needed.

ps please don't say - no one would be that stupid - lol - we are talking new users here and never underestimate the power of stupidity.

Posted: **Mon Dec 04, 2017 5:19 am**

If someone wants to use such a powerful command then they should have to learn how to do it via terminal and all the learning that goes along with that.

That is not the position that MX Linux takes on the issue, and in 4 years of existence we have never had a user complain that s/he has run into trouble because of this shortcut.

Posted: **Mon Dec 04, 2017 5:29 am**

Jerry3904 wrote:
If someone wants to use such a powerful command then they should have to learn how to do it via terminal and all the learning that goes along with that.
That is not the position that MX Linux takes on the issue, and in 4 years of existence we have never had a user complain that s/he has run into trouble because of this shortcut.

That's cool, but I felt I had to mention it :) I am not someone who generally says rtfm, I am all for giving new users a helping hand. It's just such a powerful command.

Posted: **Mon Dec 04, 2017 7:56 am**

zebedeeboss wrote:That's cool, but I felt I had to mention it :) I am not someone who generally says rtfm, I am all for giving new users a helping hand. It's just such a powerful command.

No worries, zebedeeboss. Mention to your heart's content.

Posted: **Mon Dec 04, 2017 8:05 am**

tascoast wrote:A quick intro to the MX-17 beta3 desktop and Thunar settings, highlighting some of the tools and versatility of xfce for the newer user
http://mxlinuxguide.blogspot.com.au/p/blog-page_64.html

Nice job tascoast.

Posted: **Mon Dec 04, 2017 8:33 am**

zebedeeboss wrote:That's cool, but I felt I had to mention it :) I am not someone who generally says rtfm, I am all for giving new users a helping hand. It's just such a powerful command.

You have a point.

Posted: **Mon Dec 04, 2017 8:39 am**

The manual is one of the premier features of MX. It is not unwarranted to ask users to consult the manual, especially for more complex procedures, and phrasing it in friendly terms.

Posted: **Mon Dec 04, 2017 8:47 am**

Don't know how the Manual got into this...

Posted: **Mon Dec 04, 2017 9:02 am**

Microsoft's official release of Skype for Linux has been added to the b3 MX Package-Installer. Please test!!

EDIT: Skype is located in Package-Installer under Messaging

Posted: **Mon Dec 04, 2017 9:13 am**

Thanks--installed and launched fine, mic and cam recognized.. Hope users know to not enter a password in the Gnome Keyring dialog box.

I put in the wrong password first, and somehow ended up with Skype hung. Logged out and back in, then everything went correctly.

Posted: **Mon Dec 04, 2017 9:17 am**

Jerry3904 wrote:.. Hope users know to not enter a password in the Gnome Keyring dialog box.

I put in the wrong password first, and somehow ended up with Skype hung. Logged out and back in, then everything went correctly.

For that reason, I'd like to know how to keep Skype from calling Gnome Keyring. Don't know if it's possible, though.

Posted: **Mon Dec 04, 2017 9:21 am**

Maybe this helps:

https://askubuntu.com/questions/412793/ ... -ssh-agent

Posted: **Mon Dec 04, 2017 9:48 am**

Jerry3904 wrote:Don't know how the Manual got into this...

Lots of dedication and hard work. ;-)

Posted: **Mon Dec 04, 2017 9:53 am**

Don't know how the Manual got into this...

It was mentioned in a post regarding "Ownership to Root" I should have quoted it.

Posted: **Mon Dec 04, 2017 2:59 pm**

live-usb-maker-gui
1.is not able to see usb stick plugged. Whether it's formatted or not.
2.can be found in whisker twice with different titles though. 'mx tools' and 'system' sections.

# dd-live-usb works fine in terminal.

And let me ask 2nd time about mx repo manager --> debian repos tab --> select fastest mx repo for me button. Why it won't affect security and backports repos location. It's security.debian.org and deb.debian.org correspondingly always.

Posted: **Mon Dec 04, 2017 3:13 pm**

dr-kart wrote:
And let me ask 2nd time about mx repo manager --> debian repos tab --> select fastest mx repo for me button. Why it won't affect security and backports repos location. It's security.debian.org and deb.debian.org correspondingly always.

deb.debian.org is a redirector type site, so they do the choosing on their end.

not sure about security.debian.org. It may be similar.

Posted: **Mon Dec 04, 2017 3:44 pm**

dr-kart wrote:live-usb-maker-gui
1.is not able to see usb stick plugged. Whether it's formatted or not.
2.can be found in whisker twice with different titles though. 'mx tools' and 'system' sections.

# dd-live-usb works fine in terminal.

That's strange. I thought they used the same algorithm to determine if a drive is usb/removable or not. Anyway, that test is not perfect. I suggest you try using live-usb-maker in a terminal and if it doesn't see your usb stick then use the "--force=usb" option. This is a little dangerous because it will let you over-write internal hard drives.

Posted: **Mon Dec 04, 2017 3:52 pm**

How about replacing qpdfview with evince or Okular in MX Linux

Posted: **Mon Dec 04, 2017 3:59 pm**

vamsi wrote:How about replacing qpdfview with evince or Okular in MX Linux

Okular was seriously considered for a while, and its still many of the dev team members' favorite pdf reader. However, given our non-kde-ness, we stuck with qpdfview for now.

MX Linux Forum

MX-17 Beta 3 Feedback

MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback

Re: MX-17 Beta 3 Feedback