MX Linux Forum

Posted: **Sat Feb 21, 2015 4:46 pm**

The beta version of the MX Linux Users Manual is now available off the Manuals tab at the top of the page. This thread is opened to collect feedback, corrections, suggestions, etc.

TIA

Posted: **Sat Feb 21, 2015 5:08 pm**

Impressive!

I think I found a typo.

On page 14, table 1, Home Persistence, line 3: "...but does not save system-wide settings are packages that have been installed."

It should read "system-wide settings and packages..."

Posted: **Sat Feb 21, 2015 5:18 pm**

Typo noted. Thanks Hawkeye!

Posted: **Sat Feb 21, 2015 5:18 pm**

Jerry3904 wrote: :bongodrums: :bongodrums: :bongodrums:
... As far as we know, all existing links to documentation have been corrected to point to it instead of the older MX Docs (which no longer exist except as transmogrified in the Manual) ...

These two need to be fixed:
http://www.mepiscommunity.org/user_manu ... html#check {needs to point to section 3.2.3}
http://www.mepiscommunity.org/user_manu ... tml#notify {needs to point to section 3.2.1}

Posted: **Sat Feb 21, 2015 5:26 pm**

2.1 Introduction

Last bullet
custom configuration may not work in a LiveDVD session...should be Live CD

Posted: **Sat Feb 21, 2015 5:43 pm**

kmathern wrote:
Jerry3904 wrote:
... As far as we know, all existing links to documentation have been corrected to point to it instead of the older MX Docs (which no longer exist except as transmogrified in the Manual) ...
These two need to be fixed:
http://www.mepiscommunity.org/user_manu ... html#check {needs to point to section 3.2.3}
http://www.mepiscommunity.org/user_manu ... tml#notify {needs to point to section 3.2.1}

They both do. Did you refresh the page?

Posted: **Sat Feb 21, 2015 5:44 pm**

2.1.1 PAE or non-PAE?

Make pae all-caps PAE

2nd paragraph + bullet
The method you use to determine whether you need the pae or non-pae version depends on the OS you currently run.
Linux. Open a terminal and enter this command (install inxi first if necessary): inxi -f. If the CPU Flags entry does not include pae in the list, then you’ll need the non-pae version.

Windows 2nd bullet
Windows®XP and Vista. Right click My Computer ≻ Properties, General tab. If it says Physical Address Extension (=PAE) at the bottom, then pae is the correct version to install.

2.2.1 Obtain the ISO

Last bullet before Fig 3
Transmission will then show the torrent in its list...should be Your torrent client

Posted: **Sat Feb 21, 2015 5:46 pm**

Jerry3904 wrote:They both do. Did you refresh the page?

Okay, they do now after doing a "Ctrl R".

Posted: **Sat Feb 21, 2015 9:44 pm**

2.2.3 Create the LiveMedium

1st Bullet
An ISO is a formatted image of an entire DVD. Should probably be formatted and bootable image of an OS.

2.3.1 Coming from Windows®

Accounts and passwords
I think maybe each of these bullets was meant to start with formatting like this?

ISP login information. You will need at least your...

To be consistent, use same formatting for the bullets in previous section? Backing up email, calendar, and contact data and the next section? Browser favorites

General comment on the use of Windows® or other trademarks. You only need to use the trademark symbol ® once in a document, the first time it is used is sufficient. No need to repeat it throughout the whole document.

2.4.2 The opening screen

Last line with link before section 2.4.3
MORE: Liinux startup process...should be Linux startup process

Posted: **Sat Feb 21, 2015 11:53 pm**

2.5.1 Detailed installation steps
Somewhere there it should be mentioned that it's a good idea to update mx-installer from before installing MX, for example the feature to "save live desktop changes" that is referenced in the manual is not available in the installer that comes on the CD, but it's available in the repos (actually, Tim will update the package in the repo and it will become available very soon).

Also, not sure if it's worth taking another screenshot, but the Installer Screen 2 now has two checkboxes for setting disk labels (if people don't want to go with the default).

Posted: **Sun Feb 22, 2015 4:26 am**

There are many more DVD's in the text:
In 2.2.3 they appear 5 times. The whole sentence "Use a good quality writable DVD-R with a 4.7 GB capacity" ought to be rewritten to get rid of the DVD's.
2.4.1 liveDVD
2.5.2 or a bad DVD. If you have determined that the DVD
7.7 MX Linux LiveDVD
9 LiveUSB... See LiveDVD, but the entry is LiveCD/DVD
Henry

Posted: **Sun Feb 22, 2015 5:56 am**

Another Linux typo:
2.6
Installing MX LInux
Henry

Posted: **Sun Feb 22, 2015 6:02 am**

Also, not sure if it's worth taking another screenshot, but the Installer Screen 2 now has two checkboxes for setting disk labels (if people don't want to go with the default).

Definitely worth it--damn moving targets.

Posted: **Sun Feb 22, 2015 6:06 am**

custom configuration may not work in a LiveDVD session...should be Live CD

This Manual is pointed forward to MX-15, where it looks like we might well be needing a DVD. But it should read LiveMedium, the term I thought I had used consistently to cover DVD and thumb drive.

Posted: **Sun Feb 22, 2015 7:42 am**

2 Installation
2.1 Introduction
A MX LiveMedium...should be An MX

2.5.2 Troubleshooting
Locking up see 2nd bullet
create a MX Linux...should be create an MX Linux

2.4.4 Exiting
Temporary Format bullet lead-in as bold to match other sections. Delete long dash at end of last bullet.

3.1.2 Printer <-- should be Printers
Network If bolding all actions (e.g.,right-click Properties ≻ Print Test Page), need to go through section to make consistent

5.3.2 Upgrading and downgrading
Upgraging See 1st bullet
This the faster method...should be This is the faster method

5.4 Troubleshooting
Next to last bullet...from a MX repository...should be from an MX repository

6.4 Command Line
2nd paragraph
in a MX desktop...should be in an MX desktop

Posted: **Sun Feb 22, 2015 11:02 am**

2.3.1 running VirutalBox (at the end)
2.5.1 the boatloader (fig. 14)
for a Bluetooth (fig. 17), what's "a" doing there?
2.6 the CUPS adminstration (Figure 20)
3.6.2 LIkewise
3.8.8 particuar instance
4.2.1 library organiser
6.3 destop environment
6.4.2 ouput of a command
8.2.4 peristence device (at the end)
8.3.2 snapshot-exlude.list (isn't it exclude?)
Henry

Posted: **Mon Feb 23, 2015 4:11 pm**

I was looking over the PDF version. This may be specific to my setup. The videos play when I access them from the html version. From the PDF version I get this popup

Screenshot - manual-pdf.jpg

Posted: **Mon Feb 23, 2015 4:17 pm**

peregrine wrote:I was looking over the PDF version. This may be specific to my setup. The videos play when I access them from the html version. From the PDF version I get this popup
Screenshot - manual-pdf.jpg

Working OK here.

Posted: **Mon Feb 23, 2015 5:37 pm**

peregrine wrote:I was looking over the PDF version. This may be specific to my setup.

I checked them with qpdfview and Okular, are you using Adobe?

Posted: **Mon Feb 23, 2015 5:44 pm**

yes using adobe. They do open for me with gpdf.

Posted: **Mon Feb 23, 2015 7:19 pm**

Fired up my old XP machine. MX Manual.pdf opens OK and videos work on Adobe Acrobat 7 and Nuance PDF Converter 6.
Adobe Reader 8.1 went through the motions and asked if I wished to connect to the appropriate web page, but would not connect.

Posted: **Tue Feb 24, 2015 9:00 am**

MX Linux comes with Iceweasel installed, which is a fork of Mozilla’s Firefox® that adds some additional security and omits trademarked artwork. Beyond these two changes, it is identical to Firefox®, and supports all the same add-ons.

What additional security ?, because backporting of security fixes from a more current version of firefox is not adding additional security.
It should read

MX Linux comes with Iceweasel installed, which is a fork of Mozilla’s Firefox® that adds backported security fixes to the declared Debian stable version and omits trademarked artwork. Beyond these two changes, it is identical to Firefox®, and supports all the same add-ons.

Posted: **Wed Feb 25, 2015 1:12 pm**

Subsection 3.6.3, the .pulse-volicon-cheat.sh script.

#!/bin/bash
pulse audio — start
sleep 2
volumeicon &
exit 0

Remove the space between "pulse" and "audio".

Posted: **Thu Feb 26, 2015 1:39 pm**

From a thread on sound: add turn off HDMI in Bios as another option in 3.6

Posted: **Thu Feb 26, 2015 2:13 pm**

kmathern wrote:Subsection 3.6.3, the .pulse-volicon-cheat.sh script.
#!/bin/bash
pulse audio — start
sleep 2
volumeicon &
exit 0
Remove the space between "pulse" and "audio".

also, the - should be -- in front of "start" with no space..

Code: Select all

pulseaudio --start

Posted: **Thu Feb 26, 2015 4:51 pm**

dolphin_oracle wrote: also, the - should be -- in front of "start" with no space..
Code: Select all
pulseaudio --start

This occurs in a number of places through the Manual. It's probably because of Lyx auto-substituting. I spotted the following in the HTML version:
4.8.3
6.4.2 Accessing documentation
6.5.2
7.3 CLI commands

Also the <> characters in code boxes:
6.4.1 last code
6.6.3 at end.

These will only matter if the code is copied.

Relating to pulseaudio - 3.6.3 says "best installed via synaptic", but MX Package Manager does a more thorough job.

Posted: **Thu Feb 26, 2015 5:30 pm**

Yeah, they were originally all correct. But then some goofball editor decided to replace the two en-dashes in the Manual with one em-dash to make it look more professional, forgetting that they appear correctly in some of the code...

Posted: **Thu Feb 26, 2015 5:34 pm**

Jerry3904 wrote:Yeah, they were originally all correct. But then some goofball editor decided to replace the two en-dashes in the Manual with one em-dash to make it look more professional, forgetting that they appear correctly in some of the code...

I'd fire the bast...

Posted: **Thu Feb 26, 2015 6:43 pm**

I plead "Not Guilty" Judge.

Posted: **Thu Feb 26, 2015 7:00 pm**

Gaer Boy wrote:
Also the <> characters in code boxes:
6.4.1 last code
6.6.3 at end.

These will only matter if the code is copied.

Phil - I guess that you are referring to the shape of the > symbols in the pdf? We have a problem with them. < and > are not
available in the fonts.
Gordon.

Posted: **Thu Feb 26, 2015 9:44 pm**

Why not switch to a font that does have < and > ?

Posted: **Thu Feb 26, 2015 10:20 pm**

I wish it was so easy, all of the serif and san-serif fonts available for the pdf conversion give a couple of inverted symbols
(! and ? upside-down) for <>. Hope to solve if before the final release. There are similar issues with the pipe symbol,
and as has been reported today, with --. Have found a workaround for the pdf version, still working on it for html.

Posted: **Sun Mar 01, 2015 7:52 am**

8.3 KDE on MX Linux

You may be very disappointed with the graphics rendering OOTB for gtk applications. This may need some work. If you use the oxygen theme, be sure that both gtk2-engines-oxygen and gtk3-engines-oxygen are installed and be sure to select oxygen-gtk in System Settings ≻ Application Appearance ≻ GTK ≻ GTK Themes. Not all the gtk packages that are required are installed with the KDE-standard meta package, so you’ll have to follow up with installing them yourself.

From Debian. https://wiki.debian.org/KDE

The appearance of GTK-applications in Plasma

To get gtk-applications look native in Plasma you need install these packages and configure appearance of them through System Settings > Application appearance.

kde-config-gtk-style
KDE configuration module for GTK+ 2/3.x style selection
gtk2-engines-oxygen
Oxygen widget theme for GTK2+-based applications
gtk3-engines-oxygen
Oxygen widget theme for GTK3+-based applications (Debian Wheezy)

Consider removing kdesudo if installed. Removing kdesudo will force applications doing root actions to ask for the root password, instead of allowing root actions to occur with the user password.

Removing kdesudo will not do anything, as it is a kde gui for sudo, which should not be removed
[/quote]

Posted: **Sun Mar 01, 2015 1:40 pm**

Small typo on paragraph 6.6: (HTML version)

'SSH (Secure SHell)is a protocol used...'

Missing space between ')' and 'is'.

Good idea adding links to the man pages. Kudos for the good work to all the team.

Posted: **Sun Mar 01, 2015 7:20 pm**

Re SSH typo error. Was in the pdf too, Para 6.7. Fixed.
Edit.
More thanks eselma for noting that. It's a formatting error rather than a typo. Just found several more, caused by the html and pdf converters ignoring spaces that followed Hyperlinks in the typed draft.

Posted: **Mon Mar 02, 2015 8:21 am**

8.3.1 Installation

8. Network Manager is present, but not visible in the KDE System Tray. This is resolved by installing plasma-widget-networkmanager.

Should be networkmanagment.

Ran into this just last night on a new install.

Posted: **Wed Mar 04, 2015 2:19 pm**

Wow...what an impressive manual! I have only had time to browse it briefly, but I did wonder, in Section 1.3 System Requirements, if a soundcard really is a requirement. Will the install fail if there is no sound card?

Posted: **Wed Mar 04, 2015 2:24 pm**

Section 4.10.5

"GE for Linux is available from the repos." I think it would look more professional if "Google Earth" was spelled out rather than abbreviated "GE".

Posted: **Wed Mar 04, 2015 2:45 pm**

Section 4.10.2 in the body paragraph "Google's" is misspelled "Goggle's"

Posted: **Wed Mar 04, 2015 6:57 pm**

In the KDE section, 8.3.2 you might want to consider adding something to the effect of:

The KDE Menu Editor is not included with the installation of KDE-Standard. You can add it by installing the 'kmenuedit' package via Synaptic. It can then be run from krunner. A full reload of KDE or reboot may be necessary before it will be available as a right click option on the menu launcher.

Posted: **Thu Mar 05, 2015 12:35 am**

Since you're bringing up a vanilla MX 14.x that's a good find.

I didn't have to specifically install kmenuedit. I did pretty much follow the protocol that joany put out. I also followed Danum's recent KDE post. I've found that I have to Unlock Widgets to have it available. Not sure that was always so.

But I've also added this and that along the way so it could have been connected as a dependency to something. Sometimes dependencies don't make a lot of sense. I know that having the Backports repository enabled has some problems for me at least. I've been told that I have broken packages. None appear if I ask Synaptic to show them. I resorted to aptitude -f install. It took several iterations to clear the 'broken packages'. But they did clear up.

Posted: **Thu Mar 05, 2015 10:04 am**

I had just done a new, fresh install of MX-14.3, updated, installed KDE-Standard, and then did some basic tweaking and configuring based on Joany's tips and a few things that had been posted in the MX-KDE forum. The absence of the menu editor didn't seem to be addressed anywhere (that I saw, anyway).

I normally don't install MX for any of my "converts" -- for my users, a KDE desktop with all the tweaks and additions I was used to seeing in MEPIS has been best. That's what I'm hoping to achieve with this latest install.

Posted: **Thu Mar 05, 2015 10:24 am**

kmenuedit could probably be added to the FLL_PACKAGES section of the /usr/share/mx-packageinstaller/bm/WindowManager-kde4_standard.bm file

Code: Select all

$ FLL_PACKAGES=(
          kde-standard
          #kdm
          virtuoso-minimal
          kmenuedit
)

Are there any other KDE4 packages that should be installed?

Posted: **Thu Mar 05, 2015 12:40 pm**

K3b has to be added, at least for me.

Posted: **Thu Mar 05, 2015 12:47 pm**

Probably a good addition for anybody wanting to run KDE on MX.

Posted: **Thu Mar 05, 2015 12:49 pm**

What about kdm? Not necessary, but from a cosmetic standpoint...

Posted: **Thu Mar 05, 2015 12:53 pm**

uncle mark wrote:What about kdm? Not necessary, but from a cosmetic standpoint...

kdm is in the WindowManager-kde4_standard.bm file, but is commented out. I'm not exactly sure why.

Posted: **Thu Mar 05, 2015 1:11 pm**

kmathern wrote:
uncle mark wrote:What about kdm? Not necessary, but from a cosmetic standpoint...
kdm is in the WindowManager-kde4_standard.bm file, but is commented out. I'm not exactly sure why.

Because user input is needed to select the default login manager, but it isn't (wasn't) showing up in the mx-packageinstaller 'screen'

Posted: **Thu Mar 05, 2015 1:17 pm**

Before we get scolded, this is moving away from feedback on the Manual.

Perhaps a new topic for KDE-Standard "enhancements" or some such for MX-15?

Posted: **Sat Mar 07, 2015 11:51 am**

Development note: all feedback up to this point has been taken into account in a new version (20150307) being uploaded now. Make sure to refresh the page and check to see the new version number.

I will close this thread and open a new one in a short while--thanks to every one for the terrific help!

MX Linux Forum

Beta Manual feedback

Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback

Re: Beta Manual feedback