Page 1 of 1
MX-14 beta 2
Posted: Thu Jan 30, 2014 12:55 pm
by Jerry3904
This is the feedback thread for the awesome second beta of MX-14.
Some things to particularly look at:
--booting on any machine that would not boot with B1
--wireless that failed with B1
--any hardware issues that came up in B1
--new default browser
--new Nvidia_install (System) -- no icon, we know
--new grub-customizer and disk-manager (System)
--Synaptic preferences holding, repos, etc.
--lean and clean panel
--new default layout of menu favorites
--new "Find files here" in Thunar context menu
--revised QuickStart doc (we want to start getting this translated)
anti probably has more
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 1:05 pm
by anticapitalista
Just to point out that users should do a fresh install. Do not save /home.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 1:36 pm
by kmathern
I'm in Beta2 now and using Qupzilla.
It looks like Qupzilla has Jerry's username and password to this forum stored in it's configs or saved cookies, I think I could have logged in as 'Jerry3904'.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 1:46 pm
by Adrian
kmathern wrote:I'm in Beta2 now and using Qupzilla.
It looks like Qupzilla has Jerry's username and password to this forum stored in it's configs or saved cookies, I think I could have logged in as 'Jerry3904'.
Oh, crap that's not good, Jerry, you might need to change your password for this forum.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 1:47 pm
by KBD
Will test on two computers. Had trouble burning the iso with Brasero to a cd, will try with K3b. Had no trouble installing it to usb with Unetbootin.
Here is the page to get the download:
http://www.mepiscommunity.org/mx14
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 1:47 pm
by chrispop99
Very quick first test:
In Thunar, clicking Browse Network raises an error message 'Failed to open "/ on". The specified location is not supported' (This worked in B1, allowing browsing of network shares.)
Flash is not working in QupZilla. It worked in Midori in B1.
EDIT: Flash works in Firefox. (I can't remember if Flash worked in QupZilla with B1.)
Chris
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 1:51 pm
by megatotoro
Downloading the full iso now. 35 minutes to go...
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 2:14 pm
by muskt
My first post on this topic vaporized, oh well.
DL'd & burned to USB stick via Win7.
installed (fresh) with no problems.
Rearranged panel to my preferences.
Checked Synaptic--NO CHANGE from B1--still reverts back to "highest version". I can live with it--still irritating, though.
I like QupZilla much better than that thing in B1.
I noticed during the install that the check box for Samba was greyed out & inop. Same on B1. I attempted on B1 to install Samba from the repos and got a "broken package error". Haven't tried on B2 yet.
Boots & runs quite nicely on my I7-930 System on this desktop--Haven't installed on laptop, yet.
Good Work, guys.
Thank You
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 2:21 pm
by KBD
Good job guys! Using K3b was able to burn the iso to a CD and boot up my ancient desktop computer (it would not boot with the first beta). Also pleasantly surprised that the wireless dongle was picked up and worked (I have to dig up firmware for it on Debian).
I did a full install to my Acer D250/Kav60 netbook and it was quick and no issues using Unetbootin with a USB stick. Will further test it later, but very pleased with the second beta, definitely improved.
Thanks!
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 2:22 pm
by chrispop99
Still no thumbnail icons in Thunar; tumbler needs to be installed.
If its omission is deliberate for reasons of space, I think that will not be good for a new user, it's something that is expected nowadays.
Chris
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 2:32 pm
by dolphin_oracle
chrispop99 wrote:Very quick first test:
In Thunar, clicking Browse Network raises an error message 'Failed to open "/ on". The specified location is not supported' (This worked in B1, allowing browsing of network shares.)
Chris
gvfs-backends has been removed, thus limiting Thunar's network browsing.
The connectshares scripts work without it, but they don't really "browse".
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 2:48 pm
by dolphin_oracle
chrispop99 wrote:Very quick first test:
Flash is not working in QupZilla. It worked in Midori in B1.
Chris
Flash is working for me, but it looks like a flash-blocker is installed. So you get an "play" button in the middle of the window.
I should also point out that on my first loading of youtube.com, upon pressing this "play" button, nothing happens. Refreshing the page brought up the "play" button again, which worked the second time around.
Restarting qupzilla and going back to youtube yielded the same result.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 2:49 pm
by Jerry3904
chrispop99 wrote:Very quick first test:
In Thunar, clicking Browse Network raises an error message 'Failed to open "/ on". The specified location is not supported' (This worked in B1, allowing browsing of network shares.)
Flash is not working in QupZilla. It worked in Midori in B1.
EDIT: Flash works in Firefox. (I can't remember if Flash worked in QupZilla with B1.)
Chris
Flash works fine in Qpz, it is just set by default to be click-driven (that arrow in the middle of the screen), can change in Preferences > Extensions > WebKit Plugins tab.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 3:29 pm
by dolphin_oracle
A couple of quick comments:
1. smplayer youtube works once you start vlc once.
2. the cups configure in browser link in settings looks for midori and fails.
3. gvfs-backends is not installed, which disables thunar network browsing/mounting in browser. You can still you connectshares to do your mounting.
4. flash problems (mentioned earlier) - click-to-flash prevents the flash windows on youtube from working correctly.
5. new default side bar much improved. its a wonder what little changes can make. consider mapping the "super_L" key to the whisker-menu. It makes using the search bar a 1-button-press affair (personal preference, I know...)
6. consider changing the left-click action on the volume icon to "slider" rather than "mute". The default is great if you have a mouse-wheel... again, personal preference, I know.
7. ceni window is looking good.
8. disk manager scares me.
9. mxuser appears to work as intended for adding uses, although deleted users remain in /etc/group
10. while obviously I didn't try every package in the meta-installer, I did try guayadeque, and it worked well.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 3:32 pm
by Jerry3904
2. the cups configure in browser link in settings looks for midori and fails.
man, I thought I got all of those...
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 3:44 pm
by muskt
Beta 2 up & running on Dell laptop.
No big surprises.
Still getting the reversion in Synaptic----Liveable.
Wireless did not connect up automatically. Located the link and DLd the Broadcom driver. Was told it was already installed??? Anyway after doing a re-install of the driver, the wireless connected right up.
Pretty much an un-thorough test run, but looks promising.
Wondering about an Nvidia driver install next--It has always been problematic on this laptop. Usually good for one or two OS reinstalls.
Thanks again developers.
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:05 pm
by KBD
xfce4-volumed is installed but volume up and down control from fn up/down arrow not working. Usually that works for me in xfce4.
Scratch that, after clicking around on the volume icon a few times it started working :-)
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:17 pm
by richb
First pre-release I have had issues with networking.
1. Wireless will not connect with Network Manager, all previous versions were not an issue. Edimax N300, Realtech, but I cannot get the series number from inxi (see below). Is either EW-7317UG or EW-7317UHG
2. Ceni hangs when trying to switch from network manager to ceni control.
3. INXI -F hangs at the point reporting the network information if ceni has been tried.
4. System restart hangs at shutting down network
4. Reboot gives ceni control of networking, but ceni hangs trying to configure.
I will have to try a reinstall as I cannot get a network connection.
PS. Before trying ceni a direct ethernet connection did work.
Correction: the card is RTL8192CU and lsmod shows that driver is loaded.
EDIT: Reinstalled and all OK.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:21 pm
by anticapitalista
iso has been pulled.
Those that have it, ok and keep it for a patch.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:22 pm
by chrispop99
Jerry3904 wrote:Flash works fine in Qpz, it is just set by default to be click-driven (that arrow in the middle of the screen), can change in Preferences > Extensions > WebKit Plugins tab.
Thanks; perhaps the default should be changed for release?
Chris
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:31 pm
by Jerry3904
Perhaps. I did not touch it, that is the Qpz default.
EDIT: no, we have to change it, YouTube doesn't like it, clicking on the arrow just brings an error.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:31 pm
by chrispop99
dolphin_oracle wrote:
gvfs-backends has been removed, thus limiting Thunar's network browsing.
Thanks; if this is going to be the default, perhaps the Network bookmark should be removed?
Chris
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:34 pm
by rokytnji
anticapitalista wrote:iso has been pulled.
Those that have it, ok and keep it for a patch.
I downloaded the delta patch before this post. I was gonna xdelta the Beta 1. I will wait for a reply before deleting
Code: Select all
harry@biker ~/isos/MX14 $ ls
b1-b2_delta b1-b2_delta.md5
10051fa8dc269e722604f0c56cf37652 b1-b2_delta
In case my delta was pulled for fixing also. Edit. P.S. I have not ran xdelta on the Beta 1 iso yet so everything is original and static still.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:35 pm
by dolphin_oracle
richb wrote:First pre-release I have had issues with networking.
1. Wireless will not connect with Network Manager, all previous versions were not an issue. Edimax N300, Realtech, but I cannot get the series number from inxi (see below). Is either EW-7317UG or EW-7317UHG
2. Ceni hangs when trying to switch from network manager to ceni control.
3. INXI -F hangs at the point reporting the network information if ceni has been tried.
4. System restart hangs at shutting down network
4. Reboot gives ceni control of networking, but ceni hangs trying to configure.
I will have to try a reinstall as I cannot get a network connection.
PS. Before trying ceni a direct ethernet connection did work.
It looks like all the previous realtek firmware is still installed, so hopefully you just got a weird install for some reason.
network-manager working fine here, with intel wireless. (iwlwifi)
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:37 pm
by anticapitalista
beta2 has a lot more wireless firmware than beta1. Maybe there is a conflict somewhere?
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:43 pm
by dolphin_oracle
Mousepad tapping and two-finger scroll working fine OOTB!
yay!
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:44 pm
by Jon_J
I just booted MX-14 beta 2 and installed it.
No problem for me, but the internal hard drive in my Dell mini 10 netbook is listed as sdc
(I think this is a USB thing because several of the hardware cards in this netbook are on USB internally).
The SD card that I have the MX-14 beta 2 ISO on, connected with a USB reader, is listed as sda.
I almost forgot and installed the bootloader/grub on sda (SD card).
Broadcom BCM4312 WiFi uses wl driver in "Live" mode, and all I had to do to get connected was to input my password for my WiFi wpa setting.
After installing MX-14 beta 2 to my hard drive, I booted to the desktop with working wifi. !! yeah! thank you! :)
I know this is an old netbook from 2009, but having GMA500 poulsbo graphics, and Broadcom WiFi working in Live and installed setups, makes me very happy.
I'll post my results over at the Dell Mini forum, even though that site is pretty slow these days.
I haven't done much else with this yet. I'm just happy my netbook works in this version.
Jon
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 4:56 pm
by KBD
Jon, your netbook is the same age as mine. Who would have thought these things could work so well for so long.
MX-14 is absolutely perfect on a netbook.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 5:17 pm
by richb
anticapitalista wrote:beta2 has a lot more wireless firmware than beta1. Maybe there is a conflict somewhere?
Reinstalled and was able to get a wireless connection with network manager. Maybe a flaky first install.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 5:19 pm
by Jerry3904
good
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 6:27 pm
by Jerry3904
MX-14 is absolutely perfect on a netbook.
I totally agree, +1. My netbook rocks with this!
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 6:51 pm
by Jon_J
Thunar locked up completely. I have the file tree shown in the left pane. I clicked on "File System" and it locked everything. My mouse cursor disappeared. The hardware power button no longer lets me log out.
Ctrl-Alt-Backspace doesn't respond either. Only thing I can think to do is to hold the power button for 8-10 seconds to shut the netbook down. I restarted to see if this happens again. I'm trying to access the / etc/default/ folder so I can edit grub, but it won't let me click the folder, nothing happens when I click it. Actually, I cannot click on anything. I just clicked to close thunar, and got popup to terminate application.
I worked around this by opening a terminal and as root, opened mousepad to edit the "grub" file.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 6:54 pm
by megatotoro
I haven't installed it on my netbook yet (Toshiba NB-100), but will do so soon to replace beta1.
This new beta, on my desktop, seemed a bit slower to install. Can't be certain, though.
The issue sound I reported for beta1 persists. I need to disable auto-mute to get sound working. Not a big deal.
I did get an unusual behavior when running Gparted on the live session before installing. I tried to mount a partition and then I got lots of Thunar windows popping up (one for each partition on my system). Of course, after that, all my partitions were mounted and locked in Gparted. I had to unmount them one by one.
However, I haven't been able to replicate that behavior.
BTW, is there a way to polish the Spanish version of the information messages in the installer? I can take care of that, if you want.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 6:56 pm
by Jerry3904
Jon_J wrote:Thunar locked up completely. I have the file tree shown in the left pane. I clicked on "File System" and it locked everything. My mouse cursor disappeared. The hardware power button no longer lets me log out.
Ctrl-Alt-Backspace doesn't respond either. Only thing I can think to do is to hold the power button for 8-10 seconds to shut the netbook down. I restarted to see if this happens again. I'm trying to access the / etc/default/ folder so I can edit grub, but it won't let me click the folder, nothing happens when I click it. Actually, I cannot click on anything. I just clicked to close thunar, and got popup to terminate application.
I worked around this by opening a terminal and as root, opened mousepad to edit the "grub" file.
Never seen anything like that, weird.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 7:33 pm
by Jon_J
Jon_J wrote:Thunar locked up completely. I have the file tree shown in the left pane. I clicked on "File System" and it locked everything. My mouse cursor disappeared. The hardware power button no longer lets me log out.
Ctrl-Alt-Backspace doesn't respond either. Only thing I can think to do is to hold the power button for 8-10 seconds to shut the netbook down. I restarted to see if this happens again. I'm trying to access the / etc/default/ folder so I can edit grub, but it won't let me click the folder, nothing happens when I click it. Actually, I cannot click on anything. I just clicked to close thunar, and got popup to terminate application.
I worked around this by opening a terminal and as root, opened mousepad to edit the "grub" file.
I did this a third time and watched the clock when I did it, so I could see if I could find the problem in a log file.
I booted into my slitaz partition and opened my MX-14-b2 /var/log directory and found 3 log files with the timestamp that was the same as above action.
Below is a segfault line in each of these 3 log files. They look the same to me. I hope I'm not cluttering up this thread with this.
kern.log, messages, syslog
Code: Select all
kern.log
Jan 30 18:01:59 mx14-b2 kernel: [ 32.482814] apt-notifier.py[2860]: segfault at 24 ip b5c7f527 sp bfa9e32c error 4 in libQtCore.so.4.8.2[b5aed000+2dd000]
messages
Jan 30 18:01:59 mx14-b2 kernel: [ 32.482814] apt-notifier.py[2860]: segfault at 24 ip b5c7f527 sp bfa9e32c error 4 in libQtCore.so.4.8.2[b5aed000+2dd000]
syslog
Jan 30 18:01:59 mx14-b2 kernel: [ 32.482814] apt-notifier.py[2860]: segfault at 24 ip b5c7f527 sp bfa9e32c error 4 in libQtCore.so.4.8.2[b5aed000+2dd000]
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 7:44 pm
by kmathern
Jon_J wrote:They look the same to me. I hope I'm not cluttering up this thread with this.
kern.log, messages, syslog
Code: Select all
kern.log
Jan 30 18:01:59 mx14-b2 kernel: [ 32.482814] apt-notifier.py[2860]: segfault at 24 ip b5c7f527 sp bfa9e32c error 4 in libQtCore.so.4.8.2[b5aed000+2dd000]
messages
Jan 30 18:01:59 mx14-b2 kernel: [ 32.482814] apt-notifier.py[2860]: segfault at 24 ip b5c7f527 sp bfa9e32c error 4 in libQtCore.so.4.8.2[b5aed000+2dd000]
syslog
Jan 30 18:01:59 mx14-b2 kernel: [ 32.482814] apt-notifier.py[2860]: segfault at 24 ip b5c7f527 sp bfa9e32c error 4 in libQtCore.so.4.8.2[b5aed000+2dd000]
They're all the same segfault, reported/stored in multiple logfiles. I've see that every now and then in Mepis as well. I think it's harmless. The apt-notifier does a check every 5 minutes to see if updates are available. As long as it's not segfaulting every time (and filling up the logs), I don't get too concerned.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 8:40 pm
by Jerry3904
BTW, is there a way to polish the Spanish version of the information messages in the installer? I can take care of that, if you want.
I am sure there is, PM anti about it.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 8:57 pm
by Jerry3904
OK, full ISO is now available via anti's site or a torrent from the MX-14 home website:
http://www.mepiscommunity.org/mx14
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 9:00 pm
by Jon_J
I patched my ISO. I first checked the md5 of the patch and md5 of the new ISO.
I installed it and opened Thunar.
Thunar still locks up as in my previous post.
In Thunar I have the file tree showing in the left pane, and in the right pane I have all details shown.
When I installed this, I disabled 3 things in the startup settings page.
Bluetooth
Spamassassion
Printing (cups)
I did the same settings in beta 1
I installed this on a different partition, so I can go back to beta 1 if I need to.
Jon
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 9:02 pm
by Jerry3904
Can you please open a terminal and launch thunar from there? Then report back any messages you get.
Also: did this happen when running live as well?
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 9:32 pm
by Jon_J
Jerry3904 wrote:Can you please open a terminal and launch thunar from there? Then report back any messages you get.
Also: did this happen when running live as well?
Here's the output I got after I clicked a folder, then tried to close Thunar
Code: Select all
jon@mx14-b2:~
$ thunar
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560009] CPU: 1 PID: 3384 Comm: thunar Tainted: P O 3.12-0.bpo.1-686-pae #1 Debian 3.12.6-2~bpo70+1
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560009] Hardware name: Dell Inc. Inspiron 1010 /0P374N, BIOS A09 09/10/2009
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560009] task: ec96b240 ti: f18e6000 task.ti: f18e6000
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560009] Stack:
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560009] Call Trace:
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560009] Code: 00 48 75 fd 48 c3 8d 74 26 00 8d bc 27 00 00 00 00 ff 15 d4 05 5a c1 f3 c3 90 8d b4 26 00 00 00 00 c1 e0 02 64 8b
15 9c 7e 64 c1 <6b> d2 3e f7 e2 8d 42 01 ff 15 d4 05 5a c1 f3 c3 8d b6 00 00 00
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560023] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P O 3.12-0.bpo.1-686-pae #1 Debian 3.12.6-2~bpo70+1
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560023] Hardware name: Dell Inc. Inspiron 1010 /0P374N, BIOS A09 09/10/2009
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560023] task: c1576980 ti: c156a000 task.ti: c156a000
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560023] Stack:
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560023] Call Trace:
Message from syslogd@mx14-b2 at Jan 30 20:21:23 ...
kernel:[ 166.560023] Code: 52 08 83 e2 08 75 24 31 d2 83 c0 08 89 d1 0f 01 c8 0f ae f0 89 f6 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 07 b1 01
89 f8 0f 01 c9 <85> 1d f4 21 5a c1 75 0c 89 e2 b8 05 00 00 00 e8 0e f9 e1 ff 89
^C
Message from syslogd@mx14-b2 at Jan 30 20:21:49 ...
kernel:[ 192.064009] BUG: soft lockup - CPU#1 stuck for 22s! [thunar:3384]
Message from syslogd@mx14-b2 at Jan 30 20:21:49 ...
kernel:[ 192.064009] CPU: 1 PID: 3384 Comm: thunar Tainted: P O 3.12-0.bpo.1-686-pae #1 Debian 3.12.6-2~bpo70+1
Message from syslogd@mx14-b2 at Jan 30 20:21:49 ...
kernel:[ 192.064009] Hardware name: Dell Inc. Inspiron 1010 /0P374N, BIOS A09 09/10/2009
Message from syslogd@mx14-b2 at Jan 30 20:21:49 ...
kernel:[ 192.064009] task: ec96b240 ti: f18e6000 task.ti: f18e6000
Message from syslogd@mx14-b2 at Jan 30 20:21:49 ...
kernel:[ 192.064009] Stack:
Message from syslogd@mx14-b2 at Jan 30 20:21:49 ...
kernel:[ 192.064009] Call Trace:
Message from syslogd@mx14-b2 at Jan 30 20:21:49 ...
kernel:[ 192.064009] Code: 75 dd b8 01 00 00 00 5b c3 8d b4 26 00 00 00 00 53 89 c3 e8 d8 0b c3 ff ba 00 01 00 00 f0 66 0f c1 13 0f b6 c6 38
d0 75 04 5b c3 <f3> 90 0f b6 13 38 c2 75 f7 5b c3 8d 76 00 8d bc 27 00 00 00 00
I'll try this in live next.
I opened Thunar in a terminal in Live mode. Thunar locked up when I clicked the > (arrow) beside "File System"
I waited almost a minute and tried to close Thunar. A popup came up and I was able to close Thunar.
There were no messages in the terminal this time.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 10:37 pm
by Adrian
In Help:
- Customization tab has two Note RC=right-click
- smxi tab, the same message appears in parentheses while in the other tabs there are no parentheses.
MInstaller:
- There's some text at GRUB install time in the left panel that talks about reinstalling it afterwards with MEPIS Tools, I don't think we have those available, right?
It works really nice at first look I cannot find anything wrong with it, I will come back with other reports.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 10:41 pm
by DBeckett
I used b1-b2_delta and then burned a verified CD. It boots fine on four machines I have here.
Interestingly, one of those machines is a recent build, an AMD A4-3400 APU with Radeon graphics. It's been rather a problem child. Of many distros I have here, MX-14 is the first that has successfully booted to the Desktop without intervention. Everything worked except the wireless, a Linksys WUSB54Gv2 usb adapter, which needs Intersil ISL3887 firmware to work. Having that firmware handy, I dropped it into /lib/firmware and was able to set it up and be online in two minutes.
I must say that I didn't expect to really like MX-14 — I was just participating in testing to help out. I've looked at Xfce before, and it wasn't my cup of tea. Having said that, this is really impressive. It has some nice features and is wickedly fast. Kudos to Jerry, anti, and all involved!
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 10:54 pm
by Adrian
Jon_J wrote:Opened Thunar in a terminal in Live mode. Thunar locked up when I clicked the > (arrow) beside "File System"
I waited almost a minute and tried to close Thunar. A popup came up and I was able to close Thunar.
There were no messages in the terminal this time.
Thanks for the report, the arrow that you speak is that looks like this ^ (upward) is to unmount the particular mount point, I don't think it's a good idea to try to unmount the file system. If that's not what you meant then it's probably something related to how slow the CD is, I haven't seen locks up on HDD installation.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 11:02 pm
by Jon_J
Adrian wrote:Jon_J wrote:Opened Thunar in a terminal in Live mode. Thunar locked up when I clicked the > (arrow) beside "File System"
I waited almost a minute and tried to close Thunar. A popup came up and I was able to close Thunar.
There were no messages in the terminal this time.
Thanks for the report, the arrow that you speak is that looks like this ^ (upward) is to unmount the particular mount point, I don't think it's a good idea to try to unmount the file system. If that's not what you meant then it's probably something related to how slow the CD is, I haven't seen locks up on HDD installation.
The arrow I'm talking about is the one that expands the file tree.
I have no CD on this machine. I use an SD card in a USB adapter.
Can I merge my last 2 posts, since they belong together?
I made 2 posts because it took me awhile to troubleshoot my installed setup in the first post.
Jon
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 11:20 pm
by Adrian
You can edit the first post and add the content from the second and a mod can probably delete the duplicated post.
Re: MX-14 beta 2
Posted: Thu Jan 30, 2014 11:52 pm
by BitJam
@Jon_J,
that looks like a serious problem. You are getting segfaults and kernel crashes/freezes. This could be caused either by a hardware problem or a software problem or a combination. There are two easy things you can test with the Live media. First, use F4 -> Check MD5 from the bootloader. When you boot, this will verify that the kernel, the initrd, and the compressed file system are all intact. If any of these tests fail then corrupted media is the likely source of your problem. The second test you can try is the "Memory Test" selection in the bootloader. I'd let it run for a half hour while you are doing something else. If this reports errors then you know you have a hardware problem. If it passes there might still be a hardware problem but with another part of the system.
On the live system (and the installed system) you can see the kernel log with the command "dmesg". This is usually thousands of lines. You can look at the last 100 lines with "dmesg | tail -n 100". Either in the dmesg output or one of the system log files (which may not appear in the default live system) you should find the complete information of the kernel crashes/freezes that were appearing in the terminal. Posting this information might be useful. If a log file or the dmesg output contains something juicy perhaps you could post the entire file or the entire dmesg output at
http://pastebin.com Then post the link here. You can capture the output of dmesg with "dmesg > dmesg.out". Pastebin is a great help in providing lots of information without cluttering the thread. If you are unable to get to the internet then just save the files and outputs on the sdcard and post them from another machine. You won't be able to do this if you used "dd" to create the bootable sdcard, so use something like Unetbootin instead. There are versions available for both Linux and Windows.
Another approach would be to try to boot a different version of Linux or an earlier version of Mepis or antiX-full. If these are problem-free with Thunar and if the md5 check above passed then the problem is likely something in the MX-14 software/kernel, perhaps triggered by your particular hardware. The output of "inxi -F" and "lspci -k" could potentially be useful to help us track down the problem further.
PS: I'm an antiX dev and I've helped other people with similar problems on the antiX forums. The last time this happened we traced the problem to a failing sdcard.
Oh yes. One big clue to differentiate hardware problems from software problems: hardware problems usually occur somewhat randomly and are rarely identical twice in a row. Software problems are usually very repeatable; you keep getting almost exactly the same error or errors. A failing sdcard can give you repeatable errors but I still count that as a hardware problem.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 12:29 am
by Jon_J
BitJam wrote:@Jon_J,
that looks like a serious problem. You are getting segfaults and kernel crashes/freezes. This could be caused either by a hardware problem or a software problem or a combination. There are two easy things you can test with the Live media. First, use F4 -> Check MD5 from the bootloader. When you boot, this will verify that the kernel, the initrd, and the compressed file system are all intact. If any of these tests fail then corrupted media is the likely source of your problem. The second test you can try is the "Memory Test" selection in the bootloader. I'd let it run for a half hour while you are doing something else. If this reports errors then you know you have a hardware problem. If it passes there might still be a hardware problem but with another part of the system.
On the live system (and the installed system) you can see the kernel log with the command "dmesg". This is usually thousands of lines. You can look at the last 100 lines with "dmesg | tail -n 100". Either in the dmesg output or one of the system log files (which may not appear in the default live system) you should find the complete information of the kernel crashes/freezes that were appearing in the terminal. Posting this information might be useful. If a log file or the dmesg output contains something juicy perhaps you could post the entire file or the entire dmesg output at
http://pastebin.com Then post the link here. You can capture the output of dmesg with "dmesg > dmesg.out". Pastebin is a great help in providing lots of information without cluttering the thread. If you are unable to get to the internet then just save the files and outputs on the sdcard and post them from another machine. You won't be able to do this if you used "dd" to create the bootable sdcard, so use something like Unetbootin instead. There are versions available for both Linux and Windows.
Another approach would be to try to boot a different version of Linux or an earlier version of Mepis or antiX-full. If these are problem-free with Thunar and if the md5 check above passed then the problem is likely something in the MX-14 software/kernel, perhaps triggered by your particular hardware. The output of "inxi -F" and "lspci -k" could potentially be useful to help us track down the problem further.
PS: I'm an antiX dev and I've helped other people with similar problems on the antiX forums. The last time this happened we traced the problem to a failing sdcard.
Oh yes. One big clue to differentiate hardware problems from software problems: hardware problems usually occur somewhat randomly and are rarely identical twice in a row. Software problems are usually very repeatable; you keep getting almost exactly the same error or errors. A failing sdcard can give you repeatable errors but I still count that as a hardware problem.
I found out it is a failing SD card. I used 2 tools in windows that showed it has bad sectors. "h2testw-flash-card" and "SD-Card Formatter" from SDcard.org
I'll use LinuxLive USB creator and put it on my "Lexar" compact flash card. That is the card I used for beta1 with no problems.
Thank you for your help, and I bookmarked this post for later reference.
Jon
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 12:53 am
by BitJam
For me, the MX-14_13.98_386-xfce.iso (beta-2, 2nd edition) LiveCD always starts up X even if I give it the boot parameter "3". I did not have this problem with the first beta release. Can anyone else replicate this?
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:56 am
by m_pav
--booting on any machine that would not boot with B1
Intel 945 system with IDE CDROM booted fine, failed in B1
--wireless that failed with B1
Lenovo E330 wireless worked for the first time ever using Linux, no other distro does this, however, had to use ceni, NM would not connect
--any hardware issues that came up in B1
N/A
--new default browser
Works just fine, played Youtube videos
--new Nvidia_install (System) -- no icon, we know
N/A
--new grub-customizer and disk-manager (System)
not tested
--Synaptic preferences holding, repos, etc.
Never been a problem
--lean and clean panel
Da Bom!
--new default layout of menu favorites
Perfection in a box
--new "Find files here" in Thunar context menu
Magic. Love the option to use find or locate. Mounted a windows profile folder, searched for a file about 6 folders down using find and it came up in the blink of an eye - Awesome !!
--revised QuickStart doc (we want to start getting this translated)
The first 3 pages look just fine to me for the regular user looking for first time assistance. Deep enough to get most users up and running in no time at all, not too deep to bog them down.
MetaInstaller
gscantopdf should be in the graphics section, not the Office section
Please add cups-driver-gutenprint to the Printers section
Laptop Power Management
As good as it gets using suspend on lid close, and that was using a Live-USB !.
Wake up login screen is a bit unrefined and could potentially be improved. Will upload photo soon to this post.
EDIT - photo added
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:59 am
by Eadwine Rose
On the install, right click - open root Thunar here is not opening a root Thunar. It doesn't seem to do anything.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 5:19 am
by chrispop99
Their were reported issues pre-B2 with booting on older machines with IDE drives. To test this, I had thrown together a single-core Athlon box with an IDE HDD. This failed to boot B1, giving the 'Fatal error - No block devices found!' report.
I have just tried B2 on the IDE box, and it boots fine.
inxi -F for machine:
Code: Select all
demo@mx1:~
$ su
Password:
root@mx1:/home/demo# inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: System: American Megatrends product: K7S41GX version: 1.0 serial: 00000000
Mobo: N/A model: K7S41GX version: 1.0 serial: 00000000 Bios: American Megatrends version: P2.80 date: 10/18/2006
CPU: Single core AMD Athlon XP 3000+ (-UP-) cache: 512 KB flags: (pae sse) clocked at 2180.710 MHz
Graphics: Card: NVIDIA NV34 [GeForce FX 5200]
X.org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) tty size: 80x25 Advanced Data: N/A for root
Audio: Card: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller driver: snd_intel8x0
Sound: Advanced Linux Sound Architecture ver: k3.12-0.bpo.1-686-pae
Network: Card: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet driver: sis900
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:19:66:48:a2:e2
Drives: HDD Total Size: 80.0GB (-) 1: id: /dev/sda model: ST380012A size: 80.0GB
Partition: ID: / size: 794M used: 1.7M (1%) fs: rootfs
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 102 Uptime: 3 min Memory: 117.6/1008.2MB Client: Shell (bash) inxi: 1.9.16
root@mx1:/home/demo#
Chris
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 5:22 am
by chrispop99
Eadwine Rose wrote:On the install, right click - open root Thunar here is not opening a root Thunar. It doesn't seem to do anything.
It's working fine here, on both an install and running live.
If you are running installed, can you try live?
Chris
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 5:36 am
by Eadwine Rose
Interesting, it works on the livecd.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 5:45 am
by anticapitalista
BitJam wrote:For me, the MX-14_13.98_386-xfce.iso (beta-2, 2nd edition) LiveCD always starts up X even if I give it the boot parameter "3". I did not have this problem with the first beta release. Can anyone else replicate this?
Yes, bug found. Will fix. (lightdm still has symlink in /etc/rc.3.d)
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 6:11 am
by chrispop99
Eadwine Rose wrote:Interesting, it works on the livecd.
Perhaps it might be worth reinstalling, in case something screwed up?
Chris
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 6:49 am
by chrispop99
I tried an install on a DELL D430 netbook. This machine has no built-in optical drive, and uses a proprietary USB connection for its dedicated external optical drive. (I installed with a CD.) It has been difficult to install some Linux distros to this machine in the past, and some hardware is not recognised.
MX-14 installed perfectly, with no issues. Graphics, sound, networking, special function keys, and all touchpad functions work 100%. It runs really well on a machine that only has modest performance.
inxi -F details:
Code: Select all
chris@mx3:~
$ su
Password:
root@mx3:/home/chris# inxi -F
System: Host: mx3 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: System: Dell product: Latitude D430 serial: 8YS224J
Mobo: Dell model: 0F331C serial: .8YS224J.CN129618B66907. Bios: Dell version: A08 date: 07/28/2008
CPU: Dual core Intel Core2 Duo CPU U7700 (-MCP-) cache: 2048 KB flags: (lm nx pae sse sse2 sse3 ssse3 vmx)
Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz
Graphics: Card: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics Controller
X.org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) tty size: 80x25 Advanced Data: N/A for root
Audio: Card: Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture ver: k3.12-0.bpo.1-686-pae
Network: Card-1: Broadcom NetXtreme BCM5752 Gigabit Ethernet PCI Express driver: tg3
IF: eth0 state: down mac: 00:21:70:c5:a5:b6
Card-2: Intel PRO/Wireless 3945ABG [Golan] Network Connection driver: iwl3945
IF: wlan0 state: up mac: 00:1f:3c:c8:fa:db
Drives: HDD Total Size: 80.0GB (-) 1: id: /dev/sda model: SAMSUNG_HS082HB size: 80.0GB
Partition: ID: / size: 72G used: 2.4G (4%) fs: ext4 ID: swap-1 size: 2.17GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 56.5C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 132 Uptime: 1 min Memory: 122.8/2014.6MB Client: Shell (bash) inxi: 1.9.16
root@mx3:/home/chris#
Chris
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:07 am
by afab4
Needs smbclient if you want to set up printers via samba.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:22 am
by anticapitalista
To install samba stuff, use the metapackage installer application
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:33 am
by Paul..
anticapitalista wrote:To install samba stuff, use the metapackage installer application
Unfortunately, 'smbclient' is not part of that Samba install option in 'metapackage-installer'...To afab4's point, it should be added to solve the problem he notes.
EDIT: I've added this as a suggestion in the metapackage-installer section.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:36 am
by richb
Choosing configure printers via cups from the menu throws an error as it looks for midori.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:39 am
by Gaer Boy
Quickstart - GRUB - Live Screen - CLI
Odd display in text - I've changed no defaults.
root password (“rootâ€, without the quotation marks) to continue
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:45 am
by Jerry3904
Some error in the html codes for single quote, will fix.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:46 am
by Paul..
chrispop99 wrote:
In Thunar, clicking Browse Network raises an error message 'Failed to open "/ on". The specified location is not supported' (This worked in B1, allowing browsing of network shares.)
Installing Samba via metapackage-installer...solves the problem...but still needs to be fixed in the default install, obviously.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 8:19 am
by Pierre
it's looking good

Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 8:49 am
by Gaer Boy
I've shifted to the desktop for faster typing.
Only tried on netbook so far. One quirk on live boot (as with previous versions) - first attempt gives blank screen with cursor. Second attempt boots fine. I've had no hardware problems with any version on the netbook.
Wireless - will test later (I'll have to take it to the pub). No NVIDIA on the netbook.
Browser - QupZilla is fast and clean, but YouTube videos don't play. SMplayer doesn't work either. I will investigate more.
Grub-customizer - looks good, but some changes have unexpectedly large effects. I won't use it on the netbook, but will test later on desktop.
Disk-manager - Not sure what I would use this for. Interesting quirk - when opened, the bottom left buttons say 'Edit' 'Demonter'. When a partition is selected, the 'Demonter' changes to 'Unmount'.
Synaptic - installed 3 upgrades. Set Preferences to 'Prefer Mepis' - holds and survives reboot.
Panel - I like this clean version, and the Menu structure. I needed to increase the default height of the first menu window to show the whole menu.
Thunar - 'Find files here' is stunningly fast on the netbook, including files 2 levels down. Unlike beta 1, I can browse shared network NTFS files with no problem.
I've set Claws Mail up with my travelling address and it is much snappier than my previous solutions. This applies to almost everything in this beta - I'm thinking I have no need to upgrade the RAM.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 8:51 am
by dolphin_oracle
pcallahan80 wrote:chrispop99 wrote:
In Thunar, clicking Browse Network raises an error message 'Failed to open "/ on". The specified location is not supported' (This worked in B1, allowing browsing of network shares.)
Installing Samba via metapackage-installer...solves the problem...but still needs to be fixed in the default install, obviously.
Installing Samba from the meta-installer did not solve this problem on my network. smbtree can see the shares just fine. I can connect with direct addressing no problem, but browsing is broke.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 8:55 am
by Jerry3904
Gaer Boy. YouTube videos don't play. SMplayer doesn't work either.
YouTube videos play fine IF you uncheck to make Flash require a click in Preferences; and SMplayer (which I
really don't like!) needs you to go into settings, where VLC is already selected, then say OK.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 9:09 am
by Paul..
dolphin_oracle wrote:pcallahan80 wrote:chrispop99 wrote:
In Thunar, clicking Browse Network raises an error message 'Failed to open "/ on". The specified location is not supported' (This worked in B1, allowing browsing of network shares.)
Installing Samba via metapackage-installer...solves the problem...but still needs to be fixed in the default install, obviously.
Installing Samba from the meta-installer did not solve this problem on my network. smbtree can see the shares just fine. I can connect with direct addressing no problem, but browsing is broke.
'direct addressing' meaning you need to type 'smb://[ip address]' or 'smb://[share name]' in Thunar path window (or whatever it's called)?
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 9:15 am
by Gaer Boy
Jerry3904 wrote:Gaer Boy. YouTube videos don't play. SMplayer doesn't work either.
YouTube videos play fine IF you uncheck to make Flash require a click in Preferences; ans SMplayer (which I
really don't like!) needs you to go into settings, where VLC is already selected, then say OK.
Thanks. I don't like SMplayer either, but I was trying alternatives. After making your adjustments, I can play YouTube videos either way, but I need to double-click in the video to start it in both cases. Clicking anything else has no effect.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 9:33 am
by dolphin_oracle
Installing Samba via metapackage-installer...solves the problem...but still needs to be fixed in the default install, obviously.
Installing Samba from the meta-installer did not solve this problem on my network. smbtree can see the shares just fine. I can connect with direct addressing no problem, but browsing is broke.
'direct addressing' meaning you need to type 'smb://[ip address]' or 'smb://[share name]' in Thunar path window (or whatever it's called)?
yes, except I forgot I installed gvfs-backends while doing that. connectshares scripts work fine by default install.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 9:41 am
by Jerry3904
you bad
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 9:46 am
by anticapitalista
gvfs-backends is installed in beta2 (the second one, not the first) as is tumbler.
Could those still using the first beta2 install tumbler and gvfs-backends. Then it will be 99.9% the same. Or apply the patch and reinstall.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 9:49 am
by dolphin_oracle
oh, OK. the second beta 2 :)
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:11 am
by chris_debian
Beta-2 recognizes my CDROM on /dev/sr0, so boots without any cheats/ tweaks. :-)
On the downside, when the installer has almost finished, and asked where I would like GRUB placing, I click Next and nothing happens. The Close button doesn't work either, so hard reboot required.
Cheers,
Chris.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:16 am
by richb
richb wrote:Choosing configure printers via cups from the menu throws an error as it looks for midori.
Can someone confirm this so it can be added to known issues.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:20 am
by Jerry3904
That was fixed with the recent b2 patch (which you perhaps have not applied?)
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:22 am
by dolphin_oracle
richb wrote:richb wrote:Choosing configure printers via cups from the menu throws an error as it looks for midori.
Can someone confirm this so it can be added to known issues.
you actually confirmed my post :)
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:24 am
by chrispop99
richb wrote:richb wrote:Choosing configure printers via cups from the menu throws an error as it looks for midori.
Can someone confirm this so it can be added to known issues.
Nope, it opens QupZilla here on two different installs.
It fails if I uninstall QupZilla and install Firefox however.
Chris
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:27 am
by anticapitalista
chrispop99 wrote:richb wrote:richb wrote:Choosing configure printers via cups from the menu throws an error as it looks for midori.
Can someone confirm this so it can be added to known issues.
Nope, it opens QupZilla here on two different installs.
It fails if I uninstall QupZilla and install Firefox however.
Chris
That's because it was hard coded to open qupzilla. It will be fixed for next version.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:36 am
by Adrian
chrispop99 wrote:richb wrote:richb wrote:Choosing configure printers via cups from the menu throws an error as it looks for midori.
Can someone confirm this so it can be added to known issues.
Nope, it opens QupZilla here on two different installs.
It fails if I uninstall QupZilla and install Firefox however.
Chris
Can we make sure it opens the default browser?
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:37 am
by richb
Jerry3904 wrote:That was fixed with the recent b2 patch (which you perhaps have not applied?)
Thanks. No I somehow missed there was a patch.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:41 am
by Jerry3904
You have to patch the ISO and reinstall to get all the changes, I think.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:45 am
by kmathern
richb wrote:Jerry3904 wrote:That was fixed with the recent b2 patch (which you perhaps have not applied?)
Thanks. No I
somehow missed there was a patch.
http://forum.mepiscommunity.org/viewtop ... 91&t=35470
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 12:55 pm
by Gaer Boy
pcallahan80 wrote:chrispop99 wrote:
In Thunar, clicking Browse Network raises an error message 'Failed to open "/ on". The specified location is not supported' (This worked in B1, allowing browsing of network shares.)
Installing Samba via metapackage-installer...solves the problem...but still needs to be fixed in the default install, obviously.
I'm a bit mystified by this. I can browse network shares (NTFS) from Thunar with no problem. I have just checked it running live and then immediately after a fresh install. Navigating from 'Browse Network' to the shared folder (partition in this case) adds a Network entry 'smb://Annesroom/Winfiles' which I can then use directly. I have to repeat the navigation on subsequent boots.
Am I the only one for whom this is working?
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:09 pm
by Utopia
Catfish still shows the search alternative "locate". Locate isn't installed and even if you install it and all the recommended and suggested packages, catfish is crashing when you use it.
It's better if catfish is set to show "find" only.
Henry
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:14 pm
by Jerry3904
Was that behavior using the RC menu in Thunar, or starting up catfish independently?
Inside Thunar it is set to find by default, and maybe we need to take catfish out of the menu (visible=no).
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:22 pm
by dolphin_oracle
Its in the catfish window that opens after selecting "find files here" from the thunar menu, AND the regular catfish launch. Its a "feature" of the program.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:23 pm
by Utopia
Was that behavior using the RC menu in Thunar, or starting up catfish independently?
It was after starting catfish indenpendently. To be able to do fulltext search, you have to change "find" to "locate". Haven't tested the RC menu in Thunar.
Henry
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:33 pm
by Utopia
Some simple configuration can probably hide "fulltext search" and "locate". A search app is needed for daily use, at least if you keep on mislaying stuff all the time.
Henry
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:39 pm
by richb
Strange in a VM and a HD install both locate and Find work in catfish, no crashing. Locate not installed.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:39 pm
by Jerry3904
dolphin_oracle wrote:Its in the catfish window that opens after selecting "find files here" from the thunar menu, AND the regular catfish launch. Its a "feature" of the program.
Let's get some other feedback here, please. On two HDD installs catfish opens up for me inside Thunar with "find" being selected by default.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:44 pm
by richb
Jerry3904 wrote:dolphin_oracle wrote:Its in the catfish window that opens after selecting "find files here" from the thunar menu, AND the regular catfish launch. Its a "feature" of the program.
Let's get some other feedback here, please. On two HDD installs catfish opens up for me inside Thunar with "find" being selected by default.
Same here, on VM and a HDD install. I forgot to mention that there was no malfunction opening catfish directly from the menu or via Find in Thunar.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:46 pm
by Utopia
catfish opens up for me inside Thunar with "find" being selected by default
It does for me too. But to be able to use Fulltext search, you have to switch to locate. Then it crashes.
Henry
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:48 pm
by Utopia
And it's only a small crash, says something unexpected happened (or something similar).
Henry
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:50 pm
by richb
Utopia wrote:catfish opens up for me inside Thunar with "find" being selected by default
It does for me too. But to be able to use Fulltext search, you have to switch to locate. Then it crashes.
Henry
Tried that but did not crash.
EDIT: No crash but without locate installed it does not find text in a file. IMO, crash or not, either locate should be added to the iso (158 Kb) or removed from catfish (if possible). It is a non-functional feature without locate.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 1:55 pm
by Utopia
Tried that but did not crash.
Strange, didn't you get a red sign? And no search results?
Henry
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:01 pm
by richb
Utopia wrote:Tried that but did not crash.
Strange, didn't you get a red sign? And no search results?
Henry
A red sign flashed momentarily (just a flash of red, not long enough to read) then cleared by itself, and no search results.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:06 pm
by Utopia
mlocate is supposed to do the same and is installed. Found this in the Arch wiki:
When mlocate is installed, a script is automatically placed in /etc/cron.daily (so that cron runs it daily) that will update the database. You can also manually run updatedb at any time.
It could be as simple as the databases not being updated in a fresh installation.
Henry
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:11 pm
by Jerry3904
Interesting. I think that is what happens with Thunar tree view as well.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:17 pm
by chrispop99
Jerry3904 wrote:Let's get some other feedback here, please. On two HDD installs catfish opens up for me inside Thunar with "find" being selected by default.
(Also on two HDD installs.)
I tried opening Catfish from Whisker, from Thunar context menu, and from Thunar menu 'Find files here'. In each case, 'find' was set as default, and worked as expected.
When starting Catfish from within Thunar by either method, changing 'find' to 'locate' resulted in the error message "Fatal error, search was aborted." The window could be closed normally however, so there was no crash.
Chris
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:20 pm
by Utopia
Yes, the locate and fulltext search is working after doing an "updatedb".
Henry
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:45 pm
by anticapitalista
locate is installed as mlocate.
No issues on my box either catfish/locate from menu or within Thunar. This is a straight after logging in.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:49 pm
by dolphin_oracle
I just tried searching with catfish/locate for something I know would show up in the default system (the word "installed" ) and I got several hits, and no crash. So this seems better.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:51 pm
by Jerry3904
It begins to look to me like in both this and the Thunar tree view case, the issue might be one of initial system scanning and db populating--if that makes sense.
Will take a look at the Xfce forum on this topic.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 2:54 pm
by anticapitalista
The build script runs updatedb in a chroot before building the squashfs file system (linuxfs0 and the iso.
It should not be necessary to do it before running catfish/locate.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:01 pm
by dolphin_oracle
Just got the fatal error by searching for "fred" which I'm pretty sure isn't in the installed system anywhere. Doesn't crash, just give the nasty looking error "fatal error: search aborted".
A simply file not found would have be sufficient.

Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:02 pm
by Jerry3904
When the 1.6 series was released last year, most of the commentary was about crashing:
https://forum.xfce.org/viewtopic.php?id=7645&p=1
The version we are using (1.6.3) is nine months old, so maybe an update is in the works.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:11 pm
by golinuxgo
I don't like catfish because it's never worked properly for me. I installed gnome-search-tool as a custom action on my wheezy xfce instead.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:13 pm
by Jerry3904
We would use that if we had the room, but we don't.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:16 pm
by richb
golinuxgo wrote:I don't like catfish because it's never worked properly for me. I installed gnome-search-tool as a custom action on my wheezy xfce instead.
I tend to agree with you concerning function but as Jerry indicate, room.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:21 pm
by dolphin_oracle
Odd point...is anyone else's whisker menu gradually shrinking... Mines gets a little smaller everytime I hit the "menu" button. I thought I was nuts at first, but now a scroll bar has shown up and the free space on the scrollbar gets bigger everytime I access the menu.
I can resize the menu of course, its just weird.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:22 pm
by golinuxgo
Jerry3904 wrote:We would use that if we had the room, but we don't.
Well, I only have the LO writer installed so saves me a huge hunk of disk space.

(Sorry . . . couldn't resist.)
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:24 pm
by Jerry3904
Irrelevant...
EDIT: every distro sets out with some core decisions that cascade through the whole process. Here decisions were made at the beginning of development to feature a full LO, Debian Stable, a single CD size and a unique look. If those start being changed this late in the game, everything suddenly comes into flux and all hell breaks loose.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:45 pm
by Eadwine Rose
I can barely keep up with it all, but I got the root thunar (right click open root) working on the newest downloaded iso and on the install. Likely a glitch then
Also got mic sound to work on Skype although it is VERY soft, which is where the prob was. All is set to max, cannot change anything there.
Then has someone tried to get the screenshot plugin in the panel? I cannot get it to work since it apparently launches itself more than once in the last 60 seconds. Pressing execute produces the same screen again.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:49 pm
by Jerry3904
I just tried, and it seems to crash with an error message like you report.
This is a good time maybe to remind people that Alt-F5 is mapped to the screenshooter (see QuickStart).
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:55 pm
by Eadwine Rose
Thank you! Do you happen to know where to remap the keycombo?
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 3:59 pm
by Jerry3904
--> QuickStart

Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:05 pm
by Eadwine Rose
Color me stupid.. where??
FOUND IT!
Menu - settings - keyboard -application shortcuts

Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:06 pm
by Gaer Boy
dolphin_oracle wrote:Odd point...is anyone else's whisker menu gradually shrinking... Mines gets a little smaller everytime I hit the "menu" button. I thought I was nuts at first, but now a scroll bar has shown up and the free space on the scrollbar gets bigger everytime I access the menu.
I can resize the menu of course, its just weird.
Mine was too small to start with, so I resized it. It has remained at that size since.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:34 pm
by Jerry3904
ditto
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:35 pm
by chrispop99
A couple of fairly trivial things I have found:
You can right-click the Whisker menu and select Properties in order to configure it. One of the options on the Behaviour tab is to have an icon for 'All Settings; this launches Settings Manager. (This is off by default, but might be worth having on and removing the panel link for Settings Manager?).
Checking the tick-box to enable this results in the icon launching 'App-finder'. It should point to xfce4-settings-manager. (It's easy to change it in the properties dialogue.)
I'm sure this worked correctly in B1.
Also, if Firefox is installed, when clicking an image file in Thunar Firefox launches instead of Mirage. Again, it's easy to change, but confusing for a beginner.
Chris
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:39 pm
by richb
Gaer Boy wrote:
Installing Samba via metapackage-installer...solves the problem...but still needs to be fixed in the default install, obviously.
I'm a bit mystified by this. I can browse network shares (NTFS) from Thunar with no problem. I have just checked it running live and then immediately after a fresh install. Navigating from 'Browse Network' to the shared folder (partition in this case) adds a Network entry 'smb://Annesroom/Winfiles' which I can then use directly. I have to repeat the navigation on subsequent boots.
Am I the only one for whom this is working?[/quote]
I do not know the secret sauce to get samba shares working on the MX side. Installed samba, and get an errror in Thunar when accessing the network, How does one share a folder. Do you have to mess with the samba.cfg file?
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:41 pm
by arjaybe
I don't know if this is the intended behavior, but . . .
Using "Printers (CUPS)" from the menu on a live USB stick and in virtualbox, I get "Server refused the connection."
In a VM install adding my printer was easy. (Samsung ML-1640)
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:42 pm
by Jerry3904
Also, if Firefox is installed, when clicking an image file in Thunar Firefox launches instead of Mirage.
That's what a FF install does on any OS, I think, and it's very annoying.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:47 pm
by Gaer Boy
richb wrote:Gaer Boy wrote:
Installing Samba via metapackage-installer...solves the problem...but still needs to be fixed in the default install, obviously.
I'm a bit mystified by this. I can browse network shares (NTFS) from Thunar with no problem. I have just checked it running live and then immediately after a fresh install. Navigating from 'Browse Network' to the shared folder (partition in this case) adds a Network entry 'smb://Annesroom/Winfiles' which I can then use directly. I have to repeat the navigation on subsequent boots.
Am I the only one for whom this is working?
I do not know the secret sauce to get samba shares working on the MX side. Installed samba, and get an errror in Thunar when accessing the network, How does one share a folder. Do you have to mess with the samba.cfg file?[/quote]
The quote is a bit garbled, Rich - only the last bit is mine. I've not managed to succesfully share a folder from Mepis or MX yet - I don't know the sambas secret either. This is not a priority for me, although I want to get it working one day. My main requirement is to be able to pull files from the real WinXP machine to my main desktop, and that works fine - I simply browse the shared partition over the network.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 4:54 pm
by richb
Thanks Gaer Boy. I am trying to share between a KDE install on a laptop and MX-14 on a desktop. It is fairly automatic KDE to KDE, but I suspect that one has to modify configuration files in MX-14. Beyond me at this point, so I will put it aside for the more important MX-14 evaluations. I do not want to muddy the waters.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 5:16 pm
by tascoast
Jerry3904 wrote:Also, if Firefox is installed, when clicking an image file in Thunar Firefox launches instead of Mirage.
That's what a FF install does on any OS, I think, and it's very annoying.
Browsers are a fast loading image viewer (*jpg, *.bmp *.png, *gif of course, or just *.txt, not sure what else). I sometimes drag pics to a FF icon for this, but I digress....still using the previous *.iso and still just reading and trying to comprehend some of the discussion, although it often feels like I'm overhearing a group of wizards discussing magic.
Kindly
Mick
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 5:31 pm
by chrispop99
Jerry3904 wrote:Also, if Firefox is installed, when clicking an image file in Thunar Firefox launches instead of Mirage.
That's what a FF install does on any OS, I think, and it's very annoying.
I just tried this on a fresh install of Zorin-OS-8, chosen because it doesn't have Firefox installed as standard, and the disc happened to be at the top of the pile. I had been playing with it before B2 was up, and couldn't remember this happening.
I checked jpg and png files opened in the default viewer. (EOG). I then installed Firefox, rebooted, and the image files still opened in EOG, so it's possible to achieve the desired behaviour somehow.
Of course, it's the 'somehow' that's the problem
Chris
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 6:11 pm
by loco
wow, brilliant!
burned to a dvd -r for an ancient p4 laptop which then took almost the entire 20 minutes for setup (i forgot) worked well though. i thought the clock was off but needed to run ceni again. also forgot about the
ESS Maestro thing but all is well now

.
used custom install to include a swap partition :) enjoyed the meta-installer right away to swoop on opera. beautiful, fast and seems to run noticeably cooler than the antiX kde that it replaced.

easy... and thanks

inxi.txt
kinda knew it was going to be great by looking at the sources

definitely on the right track.
meme?
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 6:14 pm
by Jerry3904
Hey, loco! Don't you think you need to start a thread about a theme song for MX-14?
Everybody is definitely working too hard on this...
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:23 pm
by malspa
Jerry3904 wrote:That was fixed with the recent b2 patch (which you perhaps have not applied?)
After downloading MX-14_13.98_386-xfce.iso (from the antiX server), do I still need to apply the patch?
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:33 pm
by Jerry3904
Not if you did it today
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:55 pm
by malspa
Jerry3904 wrote:Not if you did it today
OK, thanks. I haven't even had a chance to download the second beta yet.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 7:58 pm
by uncle mark
Posting from the live beta2. Booted straight up, no issues. Fed it my wireless passcode and bingo. Pretty spunky for a live disk on this old P4 1024 laptop.
Question -- I have an antique Dell PIII-700MHz/512MB with a load of M8. I've tried straight antiX and just don't care for it. (No offense intended at all, I'm too much of a GUI weenie.) Any chance this woul perform equally well? Be nice to have a current OS on that old beater.
Here's the inxi on this P4-1024MB Vaio:
Code: Select all
demo@mx1:~
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: System: Sony product: PCG-K13(UC) version: C1006989
Mobo: Sony model: Q-Project version: 01 Bios: Phoenix version: R0107X1 date: 03/26/2004
CPU: Single core Intel Pentium 4 CPU (-UP-) cache: 512 KB flags: (pae sse sse2) clocked at 2791.356 MHz
Graphics: Card: Advanced Micro Devices [AMD] nee ATI RS200 [Radeon IGP330M/340M/350M]
X.Org: 1.12.4 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1024x768@60.0hz
GLX Renderer: Mesa DRI R100 (RS200 4337) x86/MMX/SSE2 NO-TCL DRI2 GLX Version: 1.3 Mesa 8.0.5
Audio: Card: ULi M5451 PCI AC-Link Controller Audio Device driver: snd_ali5451 Sound: ALSA ver: k3.12-0.bpo.1-686-pae
Network: Card-1: Atheros AR5212/AR5213 Wireless Network Adapter driver: ath5k
IF: wlan0 state: up mac: 00:0e:9b:01:40:77
Card-2: Realtek RTL-8139/8139C/8139C+ driver: 8139too
IF: eth0 state: down mac: 08:00:46:ce:c9:50
Drives: HDD Total Size: 47.9GB (14.4% used) 1: id: /dev/sda model: FUJITSU_MHT2040A size: 40.0GB
2: USB id: /dev/sdb model: USB_Flash_Drive size: 7.9GB
Partition: ID: / size: 743M used: 5.5M (1%) fs: rootfs ID: swap-1 size: 1.83GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 52.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 113 Uptime: 12 min Memory: 191.1/944.2MB Client: Shell (bash) inxi: 1.9.16
demo@mx1:~
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 8:10 pm
by uncle mark
uncle mark wrote:Posting from the live beta2. Booted straight up, no issues. Fed it my wireless passcode and bingo. Pretty spunky for a live disk on this old P4 1024 laptop.
LOL... and it's already tellin' me I've got three updates to do.
You guys need to slow down, sheesh.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 9:28 pm
by uncle mark
Wow! I mean freaking
Wow!
Post now live from my antique Dell lappy with a smokin' 700MHz PIII and 512MB RAM. And it's actually (subjectively) as quick if not quicker than the P4/1024MB Vaio I was playing with earlier. The RealTek PCMCIA wireless card was picked up automagically (normally have to use ndiswrapper), fed it my wireless code, and here I am.
During boot, there were some antiX messages about disabling or removing services, something like lean, leaner, leanest. Anybody wanna tell me what that's about?
At any rate, it looks like the load of M8 on this thing is probably not long for this world.
Code: Select all
demo@mx1:~
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: Mobo: Dell model: Latitude C600 Bios: Dell version: A21 date: 04/12/2001
CPU: Single core Pentium III (Coppermine) (-UP-) cache: 256 KB flags: (pae sse) clocked at 751.690 MHz
Graphics: Card: Advanced Micro Devices [AMD] nee ATI Rage Mobility M3 AGP 2x
X.Org: 1.12.4 drivers: ati (unloaded: fbdev,vesa) Resolution: 1024x768@60.0hz
GLX Renderer: Gallium 0.4 on softpipe GLX Version: 2.1 Mesa 8.0.5
Audio: Card: ESS ES1983S Maestro-3i PCI Audio Accelerator Sound: ALSA ver: k3.12-0.bpo.1-686-pae
Network: Card-1: Realtek RTL8180L 802.11b MAC driver: rtl8180
IF: wlan0 state: up mac: 00:90:47:07:48:a1
Card-2: 3Com 3c556 Hurricane CardBus [Cyclone] driver: 3c59x
IF: eth0 state: down mac: 00:04:76:46:d4:2e
Drives: HDD Total Size: 27.9GB (24.8% used) 1: id: /dev/sda model: HITACHI_DK23CA size: 20.0GB
2: USB id: /dev/sdb model: USB_Flash_Drive size: 7.9GB
Partition: ID: / size: 388M used: 5.4M (2%) fs: rootfs ID: swap-1 size: 1.15GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 53.5C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 108 Uptime: 14 min Memory: 178.3/500.5MB Client: Shell (bash) inxi: 1.9.16
demo@mx1:~
$ ^C
demo@mx1:~
$
Good job guys. Very impressed.
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 10:06 pm
by BitJam
uncle mark wrote:During boot, there were some antiX messages about disabling or removing services, something like lean, leaner, leanest. Anybody wanna tell me what that's about?
That is entirely to make the Live system boot faster and use less memory.
It is controlled by the antiX= boot parameter which is explained briefly
here:
These are options that are only available in antiX
lean -- disable some services including wicd for a fast boot
mean -- disable dhclient (Internet connection)
Xtralean -- disable more services for a faster boot
nodbus -- disable dbus service
[...]
NOTE: Four of these options are combined into the single antiX= option. For example antiX=LMX.
L stands for lean
M stands for mean
X stands for Xtralean
D stands for nodbus
That is just an HTML version of the bootloader help that is available via "F1 Help" in the bootloader. I believe anticapitalista is adapting the help screens for MX.
You can look at the file /etc/init.d/antiX-disable-services to see which services are disabled by each parameter (or letter). Some (many?) of the services on those lists don't exist or are not installed. To see which services actually get disabled use the super secret "db++" boot option. the info is saved in /var/log/live/antiX-init.log which can be useful if some of it scrolls off the screen. If the colored text bothers you use the "noco" (nocolor) boot option to turn it off or use "loco" (lowcolor) to get a slightly different color scheme.
Just remove the "antiX=MLX" boot parameter if you don't want any services disabled. Actually, you only need to remove the "MLX".
Re: MX-14 beta 2
Posted: Fri Jan 31, 2014 11:53 pm
by james c
Fresh install of latest MX-14 Beta. CD burned with default Windows 7 app.
Other than needing to unmute the sound all the basics appear to be working ootb.I had my concerns but Youtube videos play with no problem (yet) in Qupzilla. No crashing or burning so looking pretty solid so far.
Code: Select all
james@mx1:~
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: Mobo: ECS model: GeForce7050M-M version: 1.0 Bios: American Megatrends version: 080014 date: 05/30/2008
CPU: Dual core AMD Athlon 64 X2 3800+ (-MCP-) cache: 1024 KB flags: (lm nx pae sse sse2 sse3 svm)
Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz
Graphics: Card: NVIDIA C68 [GeForce 7050 PV / nForce 630a]
X.Org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1440x900@59.9hz
GLX Renderer: Gallium 0.4 on NV67 GLX Version: 2.1 Mesa 8.0.5
Audio: Card: NVIDIA MCP67 High Definition Audio driver: snd_hda_intel Sound: ALSA ver: k3.12-0.bpo.1-686-pae
Network: Card: NVIDIA MCP67 Ethernet driver: forcedeth
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:1e:90:fe:92:50
Drives: HDD Total Size: 250.1GB (-) 1: id: /dev/sda model: ST3250318AS size: 250.1GB
Partition: ID: / size: 16G used: 2.4G (17%) fs: ext4 ID: swap-1 size: 6.40GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 30.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 127 Uptime: 14 min Memory: 203.4/3793.7MB Client: Shell (bash) inxi: 1.9.16
james@mx1:~
$ free
total used free shared buffers cached
Mem: 3884740 641760 3242980 0 68020 366140
-/+ buffers/cache: 207600 3677140
Swap: 6246396 0 6246396
james@mx1:~
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 1:04 am
by masinick
Finally made it in and I'm running Beta 2 (a build within the past 24 hours or so). Got it to boot live on both of my systems, a Gateway 2000 Series 17" portable and a Lenovo 3000 Series laptop.
The Gateway uses a Broadcom 4311 wireless firmware driver, which is half and half as far as distributions including it; MEPIS and antiX usually do, this release doesn't detect it if it's there. (Anti may recall from past discussions that there are two Broadcom firmware drivers that should be included from Debian: b43 and b43legacy, but NOT the STL or whatever that other one is; it causes conflicts and doesn't work as well as b43 does.
On the Lenovo, I have Intel Pro Wireless 3945 firmware; that is included with nearly all distros, and that is working fine. That probably means I'll try installing here first.
I believe I have a binary drop of the b43 package; I'll try to bring it in manually to see if that's what is missing on the Gateway and I'll try to install tomorrow if I can get the time.
Both systems boot just fine; so far the wireless firmware (just the Broadcom b43 driver) is the only thing I notice that's missing so far.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 9:25 am
by dolphin_oracle
richb wrote:Gaer Boy wrote:
Installing Samba via metapackage-installer...solves the problem...but still needs to be fixed in the default install, obviously.
I'm a bit mystified by this. I can browse network shares (NTFS) from Thunar with no problem. I have just checked it running live and then immediately after a fresh install. Navigating from 'Browse Network' to the shared folder (partition in this case) adds a Network entry 'smb://Annesroom/Winfiles' which I can then use directly. I have to repeat the navigation on subsequent boots.
Am I the only one for whom this is working?
I do not know the secret sauce to get samba shares working on the MX side. Installed samba, and get an errror in Thunar when accessing the network, How does one share a folder. Do you have to mess with the samba.cfg file?[/quote]
well...I am running live with persistence. everything seems to be working, but I'm at home today and guess what works...network share browsing! For whatever reason, share browsing at work doesn't work, but browsing at home does. There must be something in the two network configs that's different, because I haven't changed anything on the install. And I have NOT installed the samba package. This is totally with whatever is on the beta2 (second) iso by default.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 9:33 am
by Jerry3904
That's great to hear, thanks for staying with it.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 9:41 am
by richb
You mean the Network icon in Thunar? When I click on that I get the cryptic error message "Failed to open "/" On"
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 10:06 am
by dolphin_oracle
richb wrote:You mean the Network icon in Thunar? When I click on that I get the cryptic error message "Failed to open "/" On"
yep. this is with the second beta 2, that has gvfs-backends installed.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:03 pm
by muskt
I have been attempting to install Samba on the B2. Synaptic always tells me that the package is broken, and that I need to fix it/them.
I cannot locate any instructions for doing so.
Although it usually took me numerous attempts, I was usually successful at setting Samba up on previous versions of Mepis.
What is different here?
Which of the distributions is the recommended one for Synaptic to be accessing?
Which of the many Samba entries should I select for installation--I tried Samba (plain) and received the "Fix broken package" error?
Thanks,
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:09 pm
by richb
dolphin_oracle wrote:richb wrote:You mean the Network icon in Thunar? When I click on that I get the cryptic error message "Failed to open "/" On"
yep. this is with the second beta 2, that has gvfs-backends installed.
some progress. Installed gvfs-backends. That eliminated the error message. I Then had to edit the ~.config/connectshares/connectshares.conf file and add the IP of my other machine on the network. I then can get a Workgroup icon from Network. But it errors being unable to find shares.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:10 pm
by anticapitalista
This has come up several times.
Install samba by using the metapackage-installer.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:17 pm
by muskt
Anti--
If your post was for me (Jerry in Anchorage), I can locate no information on "metapackage-installer" that seems to apply to MX-14.
What is it, & where is it? Please?
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:21 pm
by anticapitalista
muskt wrote:Anti--
If your post was for me (Jerry in Anchorage), I can locate no information on "metapackage-installer" that seems to apply to MX-14.
What is it, & where is it? Please?
Jerry in Anchorage
Menu - Accessories-metapackage-installer (Or in recently used)
Give password, go to Network -> click on the > to open the menu ->click Samba
Press install
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:25 pm
by Adrian
Since the MX site is temporarily broken, if you need to get the Beta2 at this moment you can use this direct link:
http://sourceforge.net/projects/antix-l ... X-14/beta/
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:35 pm
by muskt
Thanks, Anti---
Found it and ran it. It finally asked for a code. Is that a password, or what? Anyway, I exited via the instruction and nothing seems different. No Samba.
Damn, I feel stupid.
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:43 pm
by kmathern
muskt wrote:Thanks, Anti---
Found it and ran it. It finally asked for a code. Is that a password, or what? Anyway, I exited via the instruction and nothing seems different. No Samba.
Damn, I feel stupid.
Jerry in Anchorage
Is this what you're talking about?
Code: Select all
Setting up samba-common-bin (2:4.1.3+dfsg-2~bpo70+1) ...
Setting up samba-dsdb-modules (2:4.1.3+dfsg-2~bpo70+1) ...
Setting up tdb-tools (1.2.12-1~bpo70+1) ...
update-alternatives: using /usr/bin/tdbbackup.tdbtools to provide /usr/bin/tdbbackup (tdbbackup) in auto mode
Setting up libkdc2-heimdal:i386 (1.6~git20120403+dfsg1-2) ...
Setting up samba (2:4.1.3+dfsg-2~bpo70+1) ...
Adding group `sambashare' (GID 116) ...
Done.
[ ok ] Starting SMB/CIFS daemon: smbd.
[ ok ] Starting NetBIOS name server: nmbd.
Setting up smbclient (2:4.1.3+dfsg-2~bpo70+1) ...
---- preprocessing done----
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
search all installed packages who need locale packages, please wait ...
grep-dctrl: /var/lib/apt/lists/antix.daveserver.info_stable_dists_stable_main_binary-i386_Packages:511: expected a colon
.
==================================
enter your code or close the window <ALT> + <F4>
#
I'm not sure how to proceed as well.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:49 pm
by anticapitalista
Just ignore that message and press Enter
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 12:55 pm
by kmathern
anticapitalista wrote:Just ignore that message
Is it just an error when exiting the metainstaller?
Running dpkg -C, and dpkg -l in another terminal, it looks like samba installed okay:
Code: Select all
demo@mx1:~
$ dpkg -C
demo@mx1:~
$ dpkg -l | grep -e samba -e smb
ii libsmbclient:i386 2:4.1.3+dfsg-2~bpo70+1 i386 shared library for communication with SMB/CIFS servers
ii python-samba 2:4.1.3+dfsg-2~bpo70+1 i386 Python bindings for Samba
ii samba 2:4.1.3+dfsg-2~bpo70+1 i386 SMB/CIFS file, print, and login server for Unix
ii samba-common 2:4.1.3+dfsg-2~bpo70+1 all common files used by both the Samba server and client
ii samba-common-bin 2:4.1.3+dfsg-2~bpo70+1 i386 Samba common files used by both the server and the client
ii samba-dsdb-modules 2:4.1.3+dfsg-2~bpo70+1 i386 Samba Directory Services Database
ii samba-libs:i386 2:4.1.3+dfsg-2~bpo70+1 i386 Samba core libraries
ii smbclient 2:4.1.3+dfsg-2~bpo70+1 i386 command-line SMB/CIFS clients for Unix
demo@mx1:~
$
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 1:05 pm
by uncle mark
muskt wrote:If your post was for me (Jerry in Anchorage), I can locate no information on "metapackage-installer" that seems to apply to MX-14.
I couldn't find it either. But stumbled on it using the search bar at the top of the menu.
In my mind, it would be more intuitive for it to be found under System. In fact, on the web site's screenshots, it looks like that's where it ought to be.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 1:08 pm
by Jerry3904
That location is driven by the desktop application file from the developer. It can be changed by the user, but will get overwritten by the next upgrade.
That's why I find that top search box so useful...don't have to know where things are.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 1:09 pm
by lonesomepoint
I just learned of this new distro. Can you tell me what it's (going to be) like or give me an information link?
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 1:10 pm
by muskt
If I continue at this (trying to learn Linux), in 8 or 10 years (if I live that long), I may just get to join the club, & learn the secret handshake (as well as the secret language/terminology used).
Jerry
(with tongue firmly embedded in cheek)
In Anchorage
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 1:12 pm
by muskt
"I just learned of this new distro. Can you tell me what it's (going to be) like or give me an information link?"
It occurred a couple of days age. No new numbering (except for the 2nd or 3rd decimal place on the download server)--nothing confusing about that(embedded sarcasm)--Beta 2a might have helped.
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 1:16 pm
by uncle mark
Jerry3904 wrote:That location is driven by the desktop application file from the developer. It can be changed by the user, but will get overwritten by the next upgrade.
That's why I find that top search box so useful...don't have to know where things are.
Screenshot #3 on the web page
implies that it's under System. At least that's how I read it. Not bitching, just pointing out what could be a souce of confusion. It got me.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 1:19 pm
by anticapitalista
kmathern wrote:Is it just an error when exiting the metainstaller?
Yes.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 3:09 pm
by Stevo
lonesomepoint wrote:I just learned of this new distro. Can you tell me what it's (going to be) like or give me an information link?
http://mepiscommunity.org/mx
What are people getting for memory usage? Is htop a good tool to get this? It seems like minimum recommended memory should be 256 MB, and it would run well with 512--barring those big memory-eaters like Google Earth. It'll probably boot to a desktop with 128 MB, but start swapping as soon as you do anything.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 3:13 pm
by uncle mark
Stevo wrote:What are people getting for memory usage? Is htop a good tool to get this? It seems like minimum recommended memory should be 256 MB, and it would run well with 512--barring those big memory-eaters like Google Earth. It'll probably boot to a desktop with 128 MB, but start swapping as soon as you do anything.
I posted earlier that it runs great (live) on a PIII-700MHz with 512MB.
Just a data point.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 3:25 pm
by richb
It is using 130MiB in a VB install when no apps open.
184MiB with Thunar and Qupzilla open
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 4:40 pm
by chrispop99
Stevo wrote:It seems like minimum recommended memory should be 256 MB, and it would run well with 512--barring those big memory-eaters like Google Earth. It'll probably boot to a desktop with 128 MB, but start swapping as soon as you do anything.
I did a test today with an Athlon XP 1700 system with 256 MB RAM. It ran live, and installed, but was pretty much unusable. I tried four different browsers; two of them crashed when a 'busy' page tried to load, and the other two wouldn't run Flash.
I then tried with the graphics card removed, taking another 64 MB of RAM away. It booted live, but was too slow to be useful. When I tried to install from live, it failed at the 'creating' partition' stage with an error message.
I then tried using the CLI installer from the boot menu, but early on I was left with a black screen and no control.
My conclusion is that 512 MB is the realistic minimum.
Chris
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 4:48 pm
by KBD
I've wondered how much linux swap might make a difference on that small amount of ram (256mb)? I've seen machine running OK on 1 gig of ram but add 2-3 gigs of Swap to the hard drive and it acts like a new machine it runs so fast. Don't know if it would make as much difference starting with such a small amount of ram or not.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 4:59 pm
by anticapitalista
Although MX-14 is pretty light compared to KDE and some other implementations of Xfce, it still is 'heavy' as it uses quite a lot of stuff to make it a featured 'desktop' ie all the gvfs stuff that adds around 40MB to running live RAM use.
I would say that 256MB with pre-configured swap to be the bare minimum. 512 should be ok, but users should not expect miracles.
ie running firefox with 100 tabs open whilst watching a video in vlc and ripping a dvd.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:08 pm
by chrispop99
anticapitalista wrote: running firefox with 100 tabs open whilst watching a video in vlc and ripping a dvd.
Ah, you've seen me at work...
Chris
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:10 pm
by uncle mark
anticapitalista wrote:...but users should not expect miracles.
ie running firefox with 100 tabs open whilst watching a video in vlc and ripping a dvd.
Well sh!t, that makes it pretty much worthless then.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:14 pm
by anticapitalista
Joking aside, you will be surprised what some people think they can do with an old box/laptop.
If I got a euro (or dollar/yen/pound) for every unrealistic expectation of what (name distro here) can do, I'd be a millionaire.
You know how it goes.
"I have an old computer that worked fantastically with windows 98 until it got slowed down by virus. I read that linux can save old computers like mine, but what a load of baloney! I can't surf the net, video doesn't work, I tried to rip a dvd. Nothing but crashes.
BTW It is a PII with 128MB RAM. Why won't firefox work? Netscape did!"
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:24 pm
by KBD
I'm actually amazed at how many old machines will work at all after 7-10 years, much less work well with Linux. Most of the time they work as well or better than they did with Windows, but there is a limit with processors, and video cards, even when the ram is bumped up to the maximum amount.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:33 pm
by richb
My 14 year old 1.7 GHz P4 was a no go with Debian 6.0, and KDE at 312 Mb ram and an old nVidia graphics card. Bumping it up to 1 Gb ram and a nVidia 6200 made it usable but no speed demon, and at times frustrating to use. Now with MX-14 on, it runs, while not super fast, at a very responsive clip. Videos and Youtube are smooth. Netflix desktop, however, is choppy and really not usable as such. So limitations remain with older machines.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:38 pm
by Jerry3904
I'd actually like to see people start describing the performance on new(er) machines, b/c the whole field of old machines and Linux has been done...by antiX!
What's happening on the upper end?
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:42 pm
by richb
Do not have an upper end machine to put it on but in VB on my new laptop it flies.
CPU Intel i5 Dual core 1.8 GHz, Intel onboard graphics, 12 Gb ram.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:49 pm
by Stevo
Very fast on my year-old AMD-based laptop, which is considered a "basic" laptop.
CPU: Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-)
As most distros do, it sets the HDMI as the default sound output, but that can be fixed in .asoundrc.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:52 pm
by KBD
Not really high end hardware but my Acer C7 Chromebook is running Ubuntu crouton Xfce and looks and runs awesome. That is low end new hardware, I can only imagine how good Linux would be on high end new hardware with tons of ram.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:54 pm
by Jerry3904
I'd rather hear about MX-14, thanks
;-D
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 5:55 pm
by anticapitalista
KBD wrote:Not really high end hardware but my Acer C7 Chromebook is running Ubuntu crouton Xfce and looks and runs awesome. That is low end new hardware, I can only imagine how good Linux would be on high end new hardware with tons of ram.
Have you tried MX-14 on that Chromebook? If so, how is it running compared to Ubuntu crouton Xfce.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 6:00 pm
by KBD
anticapitalista wrote:KBD wrote:Not really high end hardware but my Acer C7 Chromebook is running Ubuntu crouton Xfce and looks and runs awesome. That is low end new hardware, I can only imagine how good Linux would be on high end new hardware with tons of ram.
Have you tried MX-14 on that Chromebook? If so, how is it running compared to Ubuntu crouton Xfce.
I would like to try it, but I don't know of any chroot for it besides Debian and Ubuntu. Not sure what would be involved in someone creating a MX chroot. It might be worth considering in the near future as Chromebook sales are taking off. I have to think MX would fly on my Chromebook, as would AntiX.
Here is some info about Crouton:
https://github.com/dnschneid/crouton
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 7:26 pm
by uncle mark
anticapitalista wrote:Joking aside, you will be surprised what some people think they can do with an old box/laptop.
If I got a euro (or dollar/yen/pound) for every unrealistic expectation of what (name distro here) can do, I'd be a millionaire.
You know how it goes.
"I have an old computer that worked fantastically with windows 98 until it got slowed down by virus. I read that linux can save old computers like mine, but what a load of baloney! I can't surf the net, video doesn't work, I tried to rip a dvd. Nothing but crashes.
BTW It is a PII with 128MB RAM. Why won't firefox work? Netscape did!"
No, I wouldn't. Some people think Linux will run on a toaster, and it should run like a quad core with 4G RAM.
Once upon a time I thought I'd be all do-goody and fix up old computers and donate them to deserving folks (my wife is a professional do-gooder and she had plenty of potential recipients).
I got tired of people turning their noses up at what I offered. Wasn't good enough, fast enough, fancy enough. Plus they expected to be supported for free, too. Gave up the charity work quickly. Now I deal with cash customers only. I may adjust my pricing to their situations (within reason), but it's amazing how much less people will settle for when they're paying for it.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 7:32 pm
by uncle mark
KBD wrote:anticapitalista wrote:Have you tried MX-14 on that Chromebook? If so, how is it running compared to Ubuntu crouton Xfce.
I would like to try it, but I don't know of any chroot for it besides Debian and Ubuntu. Not sure what would be involved in someone creating a MX chroot. It might be worth considering in the near future as Chromebook sales are taking off. I have to think MX would fly on my Chromebook, as would AntiX.
Here is some info about Crouton:
https://github.com/dnschneid/crouton
I've been looking for an excuse to buy a Chromebook. If you guys could come up with an MX that worked like Crouton, that would put me over the edge.
Re: MX-14 beta 2
Posted: Sat Feb 01, 2014 8:47 pm
by golden45
Wow xfce beta 2 which installed without any problems -- great system.I have used meta package installer to install
Icewm
mate
kde ststem
lxde
gnome
All of these systems which are available after installing them using xfce beta 2 - you can logout and choosing which system to run from the login menu which one you want to use .you can run different systems at your will.
Thanks anticapitalista for the meta package installer this allows anybody to try different systems and try them as they want by log out and login choosing what they want to run.
Re: MX-14 beta 2-booting now
Posted: Sun Feb 02, 2014 12:54 am
by entropyfoe
I was not able to boot the first beta on the test system.
(A7n8X MB, Athlon XP 2500 (1.8GHz single core), 3G RAM.
The machine is of early windows XP vintage, a good target population for such a medium weight operating system.
For me that is a key divider, modern systems are dual core or more.
Older single core systems need more efficient software, and hopefull enough RAM.
I did not try patching beta1.
The second beta waas (13.98) downloaded, verified md5, verified burn, and booted.
Seemed to hang, black screen with the white bar where the panel would go.
CNTL ALT backspace, (? what else) and up popped a log in
logged in as demo, started browsing the file system with Thunar, a Win XP hard drive,
and the system locked, for minutes not reacting to any mouse click anywhere on the screen, couldnt open a terminal, nothing
ctl-alt-sysrq REISUB
Rebooted
(seems to load slowly, but it is older hardware)
Everything fine, logged in as demo.
I will do further testing as I recall my earlier xfce usages.
So far looks good, not sure about that first boot, maybe I was impatient and should have waited longer?
I browsed the same drive again, and did not lock up.
Re: MX-14 beta 2
Posted: Sun Feb 02, 2014 1:21 am
by muskt
My desktop is relatively speedy.
I7-930
6G Ram
Nvidia GTX550TI
WD Velociraptor 320G 10000RPM Drive (for this distro).
I have a multi-boot system, and starting from scratch probably wouldn't be fair.
So, I started timing from the GRUB prompt when I selected MX-14.
I entered the password as quickly as possible.
I also have a 5 second delay in my Conky.
From the beginning to the time Conky was on was 53 seconds.
I do not know if that is fast or not--seems pretty speedy to me.
Edit: Hmmmmmmm! I just logged out and rebooted into a "mature" install of Win 7 and it took 13 seconds.
Edit #2--Big dummy--Win7 is on an SSD. Sorry 'bout that.
Jerry in Anchorage
Re: MX-14 beta 2-booting now
Posted: Sun Feb 02, 2014 1:34 am
by BitJam
entropyfoe wrote:So far looks good, not sure about that first boot, maybe I was impatient and should have waited longer?.
For me it seems to take forever for the XFCE desktop to appear. I'm hoping this is something we can improve before the final release. From my experience I think you just needed to wait more. OTOH I don't think it is good for users to have to wait so long to get to the desktop. Running in VirtualBox, it takes 15 seconds between when it switches from vt1 until I get a desktop background. The whole process takes about 30 seconds.
Maybe I'm spoiled. My development system (with an ssd but only a scsi-2 bus) boots in 15 seconds.
BTW: you can get the seconds between when the machine booted and when a process started with this command:
where XXX is the process ID. If you use "self" then you will get the time the cut command started. If you use "$$" then you will get the time the shell you are in started. The times are displayed in hundredths of a second so something that started 30 seconds after the machine booted would show "3000".
I poked around a little and most of the XFCE processes started within 15 seconds of boot but for some reason it takes another 15 seconds before I see the desktop bg image.
Re: MX-14 beta 2
Posted: Sun Feb 02, 2014 4:37 am
by m_pav
Jerry3904 wrote:This is a good time maybe to remind people that Alt-F5 is mapped to the screenshooter (see QuickStart).
Why are we mapping the screenshooter to this key combo when almost every system I have ever encountered has its screenshot tool mapped to the purpose built PrtSc key I have seen on every keyboard since I started with computers in 1995.
In such a move, I fear we doing the equivalent of trying to reinvent the wheel. Laptops have started coming out with a dedicated PrtSc button, my 2 laptops both have one as does our reception PC at work and our public internet terminal, my wifes Logitech Wireless Desktop 520 has a dedicated PrtSc key and I use mine almost every day. I'd be loathe to have to replace it with anything else.
Re: MX-14 beta 2
Posted: Sun Feb 02, 2014 4:45 am
by Gaer Boy
+1. Even my old netbook has a PrtSc key.
Re: MX-14 beta 2
Posted: Sun Feb 02, 2014 5:13 am
by malspa
Workaround to get a Screenshot button on the panel:
I went to Panel Preferences > Items tab and added a launcher (from the top of the "Add New Items" window). From the Items tab, selected the launcher and clicked the "Edit the currently selected item" button. In the next window, clicked the "Add one or more existing items to the launcher" button, selected "Screenshot," clicked the "Add" button.
Not the quickest way to go about it, but this Screenshooter launcher works.
Re: MX-14 beta 2
Posted: Sun Feb 02, 2014 5:35 am
by Jerry3904
m_pav wrote:Jerry3904 wrote:This is a good time maybe to remind people that Alt-F5 is mapped to the screenshooter (see QuickStart).
Why are we mapping the screenshooter to this key combo when almost every system I have ever encountered has its screenshot tool mapped to the purpose built PrtSc key I have seen on every keyboard since I started with computers in 1995.
In such a move, I fear we doing the equivalent of trying to reinvent the wheel. Laptops have started coming out with a dedicated PrtSc button, my 2 laptops both have one as does our reception PC at work and our public internet terminal, my wifes Logitech Wireless Desktop 520 has a dedicated PrtSc key and I use mine almost every day. I'd be loathe to have to replace it with anything else.
I use screenshooter with a keystroke because I am often doing captures with something open that will close if I click somewhere else, and b/c screenshooter allows for a rectangle to be drawn, saving me a crop step, and--in the case of my AAO722 laptop, the PrtSc doesn't seem to work.
Re: MX-14 beta 2
Posted: Sun Feb 02, 2014 5:56 am
by Gaer Boy
I haven't noticed much feedback about grub-customizer. I used it early on to change the default menu item, which was fine. Now I tried to change the appearance slightly - the default text is a bit cramped.
Careful - the Appearance settings make a great sledgehammer! Taking heed of the warnings, I cautiously tried increasing the point size by 1. This completely corrupted the grub screen - double-spaced text, character-drawn borders and a distorted graphic background. A number of attempts failed to revert to original settings, so I will have to repair grub. It's sort of usable at the moment, so no priority.
Re: MX-14 beta 2
Posted: Sun Feb 02, 2014 6:18 am
by Jerry3904
Most people seem to find its best use is to assign an alias (MX-14 working) or change order of listing
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 7:28 am
by dolphin_oracle
dolphin_oracle wrote:A couple of quick comments:
4. flash problems (mentioned earlier) - click-to-flash prevents the flash windows on youtube from working correctly.
Well, I don't know what's different, but now a fresh install of beta 2 and click-to-flash is working fine.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 7:34 am
by Jerry3904
dolphin_oracle wrote:dolphin_oracle wrote:A couple of quick comments:
4. flash problems (mentioned earlier) - click-to-flash prevents the flash windows on youtube from working correctly.
Well, I don't know what's different, but now a fresh install of beta 2 and click-to-flash is working fine.
Same here, I wonder what the diff is?
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 8:12 am
by jdmeaux1952
I downloaded the Beta 2 and varified the md5. Could not get it to burn onto my Maxell cd's. Had to utilize a Ridata dvd to burn it onto. Live worked okay, except for the time being off 1 hour. I rechecked my BIOS clock to make sure my time was correct, and then began an install on my JUNKBOX. After install the time was off exactly 1 hour.
After a reboot, I rechecked my BIOS time (it was off 1 hour) and tried out MX-14 Beta 2 that I installed. Again the time was off 1 hour. I have been unable to correct this from within the desktop applications.

The system was shut down, coin battery was replaced, BIOS was rechecked (time was rechecked), and then rebooted to go into the beta. Time AGAIN was off 1 hour (Eastern time instead of Central time).
After rebooting I checked my BIOS. I'm not sure if 1)- my motherboard / BIOS chip is going flakey and changing the time on its own, OR 2)- the os is screwing with the time in BIOS somehow (?). I suspect the BIOS is getting flakey. I HATE unsoldering chips and replacing them on a motherboard. :lipsrsealed: :lipsrsealed: But at least this is only a single layer board.
I have had the same complaints of centi working then not working, flash headaches. But all in all this beta works good to excellent. Now to get rid of the bugs.

Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 9:30 am
by uncle mark
[quote="jdmeaux1952"]After a reboot, I rechecked my BIOS time (it was off 1 hour) and tried out MX-14 Beta 2 that I installed. Again the time was off 1 hour. I have been unable to correct this from within the desktop applications.

The system was shut down, coin battery was replaced, BIOS was rechecked (time was rechecked), and then rebooted to go into the beta. Time AGAIN was off 1 hour (Eastern time instead of Central time).
dpkg-reconfigure tzdata
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 10:26 am
by Eadwine Rose
Maybe I missed something but you DID set up the timezone and such in the settings?
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 12:55 pm
by lucky9
Make sure BIOS time is correct. On the installation, setup the time to not use UTC. After installation use kdesu systemsettings on a Command Line to set the time zone. Or do what um said.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 1:02 pm
by Jerry3904
Kdesu in MX-14?
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 1:06 pm
by richb
for that matter systemsettings in MX-14?
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 1:08 pm
by anticapitalista
Jerry3904 wrote:Kdesu in MX-14?
Why? We don't have any KDE.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 1:11 pm
by richb
gksudo is the equivalent for me in mX-14. Not sure if it came in by installing something else as I no longer have a clean install.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 1:22 pm
by golinuxgo
richb wrote:gksudo is the equivalent for me in mX-14. Not sure if it came in by installing something else as I no longer have a clean install.
Question . . . is sudo set up as default in MX-14? Or can one set a root pwd during installation and avoid the sudo thing altogether? I've only run MX-14 from live cd. Seems at some point I opened a root terminal, entered 'root' as pwd and it worked but I may be imagining that I did that . . .
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 1:24 pm
by richb
golinuxgo wrote:richb wrote:gksudo is the equivalent for me in mX-14. Not sure if it came in by installing something else as I no longer have a clean install.
Question . . . is sudo set up as default in MX-14? Or can one set a root pwd during installation and avoid the sudo thing altogether? I've only run MX-14 from live cd. Seems at some point I opened a root terminal, entered 'root' as pwd and it worked but I may be imagining that I did that . . .
I should have said or gksu. Yes su is setup. You do not have to use sudo.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 1:32 pm
by lucky9
You can always tell when I haven't gotten my nap in. I'm particularly unconscious about where I am on the Forum. Apologies to those that do know where they are....
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 2:04 pm
by chrispop99
I've found some odd behaviour when installing from the meta-installer.
I used it to install Firefox. It ran properly. I then right-clicked on its entry in the menu, and selected 'Add to Panel'. It added a launcher, but the launcher was devoid of any information. It was exactly as if I had placed a blank launcher on the panel from the Panel>Add New Items dialogue.
I deleted the launcher, logged out, then back in, and was then able to successfully add a functioning launcher.
I then installed something else from Synaptic. Once installed, I was able to create a working launcher as would be the expected behaviour.
It's not a huge problem, but would be confusing for a novice.
Chris
EDIT:
I've just tried this whilst running live, and was unable to replicate the behaviour, so it must be something I've changed.
I will try this on the next Beta.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 2:19 pm
by Jerry3904
richb wrote:golinuxgo wrote:richb wrote:gksudo is the equivalent for me in mX-14. Not sure if it came in by installing something else as I no longer have a clean install.
Question . . . is sudo set up as default in MX-14? Or can one set a root pwd during installation and avoid the sudo thing altogether? I've only run MX-14 from live cd. Seems at some point I opened a root terminal, entered 'root' as pwd and it worked but I may be imagining that I did that . . .
I should have said or gksu. Yes su is setup. You do not have to use sudo.
And sudo is set up by default, so it can be used. Root is the password for, ummm, root in Live mode.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 2:44 pm
by rokytnji
Re-install over previous Beta1. No change needed for grub4dos menu entry since I installed grub to root on /dev/sda2.
/home sits on /dev/sdb2 as a test of the installer.
Pretty freshly done so nothing new to report.
For the blinking cursor boot posts. I burned a cd on one computer that threw that up. My md5sum is correct because I have the same iso on a another computer. Anyhows. I tried the blinking cursor cd on a few computers. Then stopped because of no changes. I booted a 01-04-2014 Parted Magic cd I have to make sure my old dvdrom was OK.
Then burned another cd on another computer. Same cd -r Memorex cheapo walmart brand.
Booted up fine with copied iso on another computer.
Code: Select all
biker@biker:~
$ inxi -Fxz
System: Host: biker Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit, gcc: 4.6.3)
Desktop: Xfce 4.10.2 (Gtk 2.24.10) Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: System: IBM product: 679421U
Mobo: IBM model: IBM Bios: IBM version: 20KT46AUS date: 06/04/2004
CPU: Single core Intel Pentium 4 CPU (-UP-) cache: 256 KB flags: (pae sse sse2) bmips: 3588.19 clocked at 1794.099 MHz
Graphics: Card: NVIDIA NV6 [Vanta/Vanta LT] bus-ID: 01:00.0
X.Org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1024x768@85.0hz
GLX Renderer: Mesa DRI nv05 x86/MMX/SSE2 GLX Version: 1.2 Mesa 8.0.5 Direct Rendering: Yes
Audio: Card: Intel 82801BA/BAM AC'97 Audio Controller driver: snd_intel8x0 ports: 1c00 1840 bus-ID: 00:1f.5
Sound: Advanced Linux Sound Architecture ver: k3.12-0.bpo.1-686-pae
Network: Card-1: Intel 82801BA/BAM/CA/CAM Ethernet Controller driver: e100 ver: 3.5.24-k2-NAPI port: 2000 bus-ID: 02:08.0
IF: eth0 state: down mac: <filter>
Card-2: Realtek RTL8187B Wireless 802.11g 54Mbps Network Adapter usb-ID: 001-002
IF: N/A state: N/A mac: N/A
Drives: HDD Total Size: 200.1GB (13.4% used) 1: id: /dev/sda model: ST3160215ACE size: 160.0GB
2: id: /dev/sdb model: IC35L040AVVA07 size: 40.0GB
Partition: ID: / size: 11G used: 2.7G (28%) fs: ext4 ID: /home size: 27G used: 109M (1%) fs: ext4
ID: swap-1 size: 1.17GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 25.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 127 Uptime: 1:42 Memory: 465.4/1134.5MB Runlevel: 5 Gcc sys: 4.7.2
Client: Shell (bash 4.2.37) inxi: 1.9.16
biker@biker:~
$ sudo blkid
/dev/sda2: UUID="d42d2a5e-cefc-411e-b295-e0dc4c962740" TYPE="ext4"
/dev/sda1: LABEL="/data" UUID="ee7bdb53-cea8-4e61-ba99-2a4e6e1adf7a" TYPE="ext4"
/dev/sdb1: UUID="5e6d4bb9-198e-4a6d-a39e-0d6451e8a949" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: UUID="4b98406c-63db-4b9c-875f-34c68c3ea365" TYPE="ext4"
/dev/sdb3: UUID="48072200-9a78-49a3-a8f2-2446cb94e45c" TYPE="swap"
biker@biker:~
$ sudo fdisk -l
[sudo] password for biker:
Disk /dev/sda: 160 GB, 160039272960 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 18096 145356088 83 Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sda2 18096 19458 10940265 83 Linux
Warning: Partition 2 does not end on cylinder boundary.
Disk /dev/sdb: 40 GB, 40015987200 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 1167 9373896 83 Linux
/dev/sdb2 1168 4723 28555537 83 Linux
/dev/sdb3 4724 4865 1132582 82 Linux swap
I don't deal with shares on this rig as it is a playtoy for customers and I don't want them accessing my other gear.
Thats it from me.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 2:54 pm
by golinuxgo
Jerry3904 wrote:And sudo is set up by default, so it can be used.
UGH! Is there an option to NOT have sudo set up at all on install?
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 3:02 pm
by dolphin_oracle
some of the antix stuff requires sudo to be set up.
but you could remove it...or delete the contents of the sudoers file.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 3:55 pm
by golinuxgo
dolphin_oracle wrote:some of the antix stuff requires sudo to be set up.
Is there a list of that 'stuff' somewhere? Thanks!
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 4:28 pm
by BitJam
golinuxgo wrote:Is there a list of that 'stuff' somewhere? Thanks!
You can get a list with the commands "sudo cat /etc/sudoers.d/antixers". It is possible that some of these are not required by MX.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 5:15 pm
by anticapitalista
Or simply don't use sudo.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 5:18 pm
by jdmeaux1952
Referring back to my earlier post from today (Post # 329212 Re: MX-14 beta 2), I had to change out the motherboard on my JUNKBOX. Same model, but it has a bad timer so my P III is now running at 334 Mhz. It's so slow I could cook a turkey by the time it refreshes a page. (I told you it was a JUNKBOX made from old computer parts.
But Beta 2 is up and running with the TIME set okay. Now to seriously play around with it.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 5:22 pm
by BitJam
anticapitalista wrote:Or simply don't use sudo.
I think golinuxgo wanted to know what might get broken if he removes sudo entirely.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 5:53 pm
by golinuxgo
BitJam wrote:anticapitalista wrote:Or simply don't use sudo.
I think golinuxgo wanted to know what might get broken if he removes sudo entirely.
Precisely. She, BTW (an an old one at that).

Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 6:06 pm
by anticapitalista
Why do you want to remove sudo?
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 6:07 pm
by BitJam
golinuxgo wrote:Precisely. She, BTW (an an old one at that).

Oops. Sorry about that. Please excuse me.
May I ask why you don't like sudo? From the developer's perspective it can be very handy to give normal users the ability to use certain commands without having to enter a password. Other routes have problems. For example, altering commands to be SUID will get nuked whenever a package containing the command gets upgraded.
BTW, other ways to see where sudo is used by MX is with these commands:
Code: Select all
grep sudo $(find / -name "*.desktop" 2> /dev/null) 2>/dev/null
grep sudo /usr/local/bin/*
Ninja'ed by anti.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 6:39 pm
by golinuxgo
anticapitalista wrote:Why do you want to remove sudo?
Irrational prejudice because of my introduction to it with Ubuntu many years ago @2004-5. The thought of having anything reminiscent of 'buntu on my box makes my skin crawl and blood pressure go up (not really but it feels like that).

Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 6:46 pm
by uncle mark
golinuxgo wrote:anticapitalista wrote:Why do you want to remove sudo?
Irrational prejudice because of my introduction to it with Ubuntu many years ago @2004-5. The thought of having anything reminiscent of 'buntu on my box makes my skin crawl and blood pressure go up (not really but it feels like that).

I react the same way to Windows.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 6:50 pm
by golinuxgo
BitJam wrote:golinuxgo wrote:Precisely. She, BTW (an an old one at that).

Oops. Sorry about that. Please excuse me.
Not a problem at all so no need to apologize.
BitJam wrote:May I ask why you don't like sudo?
See above response to anti. But then there's the hard-core Debian disdain for sudo. Many mountains to climb. Maybe MX can reverse my well-ingrained aversion to sudo.
BitJam wrote:From the developer's perspective it can be very handy to give normal users the ability to use certain commands without having to enter a password. Other routes have problems. For example, altering commands to be SUID will get nuked whenever a package containing the command gets upgraded.
Probably hasn't been an issue for me because I'm used to doing it the old-fashioned, user-unfriendly way.
BitJam wrote:BTW, other ways to see where sudo is used by MX is with these commands:
Code: Select all
grep sudo $(find / -name "*.desktop" 2> /dev/null) 2>/dev/null
grep sudo /usr/local/bin/*
I'll check out the list when I get on that computer later tonight. Thanks.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 6:51 pm
by golinuxgo
uncle mark wrote:golinuxgo wrote:anticapitalista wrote:Why do you want to remove sudo?
Irrational prejudice because of my introduction to it with Ubuntu many years ago @2004-5. The thought of having anything reminiscent of 'buntu on my box makes my skin crawl and blood pressure go up (not really but it feels like that).

I react the same way to Windows.
Tell me about it! There be no Winders here for many years.
Re: MX-14 beta 2
Posted: Mon Feb 03, 2014 6:59 pm
by uncle mark
golinuxgo wrote:uncle mark wrote:I react the same way to Windows.
Tell me about it! There be no Winders here for many years.
I keep one around for reference, since I make my pocket money fixin' 'em.
But for
my use??? Not for about seven or eight years for me.
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 2:07 am
by james c
Regret to report that the Nvidia Installer grabbed and installed the incorrect driver(319.xx instead of the correct 304.xx) and someone was too oblivious too notice in time to stop it. Will try to reinstall tomorrow.
http://packages.debian.org/sid/nvidia-l ... 4xx-driver
Code: Select all
Chip description:
VGA compatible controller: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] (rev a2)
Posting from Puppy Raring running 304.88......
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 3:10 am
by james c
Was able to get back into Nouveau and purge 319.xx....... really didn't have time to reinstall.
I despise booting to a blinking cursor........
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 5:10 am
by m_pav
james c wrote:Was able to get back into Nouveau and purge 319.xx....... really didn't have time to reinstall.
I despise booting to a blinking cursor........
Were you using smxi or sgfxi to get the nvidia drivers?
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 7:43 am
by kmathern
james c wrote:Regret to report that the Nvidia Installer grabbed and installed the incorrect driver(319.xx instead of the correct 304.xx) and someone was too oblivious too notice in time to stop it. Will try to reinstall tomorrow.
http://packages.debian.org/sid/nvidia-l ... 4xx-driver
Code: Select all
Chip description:
VGA compatible controller: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] (rev a2)
Posting from Puppy Raring running 304.88......
Yeah, I already posted that the Nvidia Installer that beta2 comes with will install the incorrect driver for GeForce 6xxx/7xxx cards, the post is here:
http://forum.mepiscommunity.org/viewtop ... 38#p328938.
There's a command in that post that will download an updated version of the installer.
The updated version should now detect and install the 304xx driver for 6xxx/7xxx cards.
The update also worked for Eadwine Rose with her GT 640 card which had previously been reported as unsupported.
Anticapitalista tried it, and it worked (or I should say still works) with his GeForce 8400 GS card.
I would appreciate it if you would try the updated installer, because no 6xxx/7xxx user has tried it yet. It can be tested in a Live session.
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 8:40 am
by richb
kmathern wrote:james c wrote:Regret to report that the Nvidia Installer grabbed and installed the incorrect driver(319.xx instead of the correct 304.xx) and someone was too oblivious too notice in time to stop it. Will try to reinstall tomorrow.
http://packages.debian.org/sid/nvidia-l ... 4xx-driver
Code: Select all
Chip description:
VGA compatible controller: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] (rev a2)
Posting from Puppy Raring running 304.88......
Yeah, I already posted that the Nvidia Installer that beta2 comes with will install the incorrect driver for GeForce 6xxx/7xxx cards, the post is here:
http://forum.mepiscommunity.org/viewtop ... 38#p328938.
There's a command in that post that will download an updated version of the installer.
The updated version should now detect and install the 304xx driver for 6xxx/7xxx cards.
The update also worked for Eadwine Rose with her GT 640 card which had previously been reported as unsupported.
Anticapitalista tried it, and it worked (or I should say still works) with his GeForce 8400 GS card.
I would appreciate it if you would try the updated installer, because no 6xxx/7xxx user has tried it yet. It can be tested in a Live session.
Worked.
Code: Select all
Graphics: Card: NVIDIA NV44A [GeForce 6200] X.Org: 1.12.4 driver: nvidia Resolution: 1280x1024@60.0hz
GLX Renderer: GeForce 6200/AGP/SSE2 GLX Version: 2.1.2 NVIDIA 304.117
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 11:05 am
by Stevo
I've just finished building Deadbeef 0.6.1 for the M12 CR, and noticed it comes in at a smaller installed size than 0.6.0 (7.2 MB vs 8.4), but everything still is working. That should free up several hundred K on the CD.
Packages are here for quick testing:
http://ubuntuone.com/1OAYuNHmAeO2EE89FWleR9
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 11:10 am
by Jerry3904
Looks like we will be moving to your Clementine instead at this point--but I will love DeaDBeeF and wonder if it might make a candidate for antiX at some point.
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 12:28 pm
by rokytnji
@Stevo
Does the new deadbeef play streaming .pls files?
What is weird for me is that deadbeef streams .pls OK live. But after install. of MX14 to hard drive. It no longer streams internet radio.
I get my stations from
http://loudcity.com/
Anyhows. After a hard drive install. I uninstall Deadbeef becuase of this issue and go with xmms and xmms with antiX goodies.
So I am just wondering if I am the only one seeing this in deadbeef? I download the winamp link which is a .pls because cmus or moc can handle this also.
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 3:17 pm
by james c
kmathern wrote:james c wrote:Regret to report that the Nvidia Installer grabbed and installed the incorrect driver(319.xx instead of the correct 304.xx) and someone was too oblivious too notice in time to stop it. Will try to reinstall tomorrow.
http://packages.debian.org/sid/nvidia-l ... 4xx-driver
Code: Select all
Chip description:
VGA compatible controller: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] (rev a2)
Posting from Puppy Raring running 304.88......
Yeah, I already posted that the Nvidia Installer that beta2 comes with will install the incorrect driver for GeForce 6xxx/7xxx cards, the post is here:
http://forum.mepiscommunity.org/viewtop ... 38#p328938.
There's a command in that post that will download an updated version of the installer.
The updated version should now detect and install the 304xx driver for 6xxx/7xxx cards.
The update also worked for Eadwine Rose with her GT 640 card which had previously been reported as unsupported.
Anticapitalista tried it, and it worked (or I should say still works) with his GeForce 8400 GS card.
I would appreciate it if you would try the updated installer, because no 6xxx/7xxx user has tried it yet. It can be tested in a Live session.
Did a fresh reinstall to clear out any junk........installed the updated installer from the linked post and success.
Code: Select all
james@mx1:~
$ inxi -G
Graphics: Card: NVIDIA C68 [GeForce 7050 PV / nForce 630a] X.Org: 1.12.4 driver: nvidia Resolution: 1440x900@59.9hz
GLX Renderer: GeForce 7050 PV / nForce 630a/integrated/SSE2/3DNOW! GLX Version: 2.1.2 NVIDIA 304.117
Thanks.....
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 5:41 pm
by KrispyKritter
I have tried the liveCD. I was able to get in and post from it. This is more than I can do with M12b2.
Steve
Re: MX-14 beta 2
Posted: Tue Feb 04, 2014 11:16 pm
by namida12
Dell Vostro 220 on Work Bench with junk power supply booted Live :
demo@mx1:~/Desktop
$ inxi -Fxz
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit, gcc: 4.6.3)
Desktop: Xfce 4.10.2 (Gtk 2.24.10) Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: System: Dell product: Vostro 220 Series
Mobo: Dell model: 0P301D version: A00 Bios: Dell version: 1.0.4 date: 02/10/2009
CPU: Dual core Intel Pentium Dual CPU E2200 (-MCP-) cache: 1024 KB flags: (lm nx pae sse sse2 sse3 ssse3) bmips: 8778.02
Clock Speeds: 1: 1595.00 MHz 2: 2195.00 MHz
Graphics: Card: Intel 4 Series Integrated Graphics Controller bus-ID: 00:02.0
X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz
GLX Renderer: Mesa DRI Intel G45/G43 x86/MMX/SSE2 GLX Version: 2.1 Mesa 8.0.5 Direct Rendering: Yes
Audio: Card: Intel 82801JI (ICH10 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture ver: k3.12-0.bpo.1-686-pae
Network: Card: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller
driver: r8169 ver: 2.3LK-NAPI port: e800 bus-ID: 02:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 80.0GB (-) 1: id: /dev/sda model: WDC_WD800JD size: 80.0GB
Partition: ID: / size: 765M used: 154M (21%) fs: rootfs
Sensors: System Temperatures: cpu: 39.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 105 Uptime: 1:12 Memory: 527.1/973.7MB Runlevel: 5 Gcc sys: 4.7.2
Client: Shell (bash 4.2.37) inxi: 1.9.16
demo@mx1:~/Desktop
$
Default QupZilla is a bit iffy, freezing any time there is a flash problem.
Plays Jpop well on Sky.FM however!
Am going to add larger hard drive and see how well it performs with a faster drive. I know I need another gig stick of memory in this system , to make it run a bit quicker but could not find a stick in my memory bin.
JR
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 12:06 am
by namida12
Could not boot this older Compaq, only got a blinking cursor on black screen:
Was able to boot beta 1 using Via cheat code: <--can not find that posting, but nothing loads from media. Same media works in 4 other systems before and tested one afterwards with same DVD Rom.
Here is inxi info
Sue01@antiX1:~
$ inxi -F
System: Host: antiX1 Kernel: 3.7.10-antix.5-486-smp i686 (32 bit)
Desktop: IceWM 1.3.7 Distro: antiX-13.2_386-full Luddite 4 November 2013
Machine: System: Compaq Presario 061 product: PJ506AA-ABA SR1215CL NA440 version: 0n41411CO101KELUT00
Mobo: ASUSTek model: Kelut version: 2.02 Bios: Phoenix version: 3.11 date: 09/02/2004
CPU: Single core AMD Sempron 3000+ (-UP-) cache: 512 KB flags: (pae sse) clocked at 1999.722 MHz
Graphics: Card: VIA KM400/KN400/P4M800 [S3 UniChrome]
X.Org: 1.12.4 drivers: openchrome (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz
GLX Renderer: Gallium 0.4 on softpipe GLX Version: 2.1 Mesa 8.0.5
Audio: Card: VIA VT8233/A/8235/8237 AC97 Audio Controller driver: snd_via82xx Sound: ALSA ver: k3.7.10-antix.5-486-smp
Network: Card: VIA VT6102 [Rhine-II] driver: via-rhine
IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: 00:11:2f:9f:fa:b2
Drives: HDD Total Size: 82.3GB (4.2% used) 1: id: /dev/sda model: HDS728080PLAT20 size: 82.3GB
Partition: ID: / size: 14G used: 3.3G (26%) fs: ext4 ID: swap-1 size: 1.61GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 43.5C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 87 Uptime: 15 min Memory: 158.6/944.8MB Client: Shell (bash) inxi: 1.9.16
Sue01@antiX1:~
$
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 1:27 am
by james c
Have a bit of free time since I'm in the middle of yet another winter storm so ...... Beta 2 test on an old box with 512 Mb ram and no hdd,so no swap.In other words,some old parts thrown into a case. Booted fine from the old IDE cd-rom drive...internet,sound and display all working on initial boot.
Code: Select all
demo@mx1:~
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: System: Compaq Presario 06 product: DD307A-ABA 6412us NA910 version: 0n41411RE101SALSA
Mobo: N/A model: KM266-8235 Bios: Phoenix version: AM37308 date: 12/16/2002
CPU: Single core AMD Athlon XP 2000+ (-UP-) cache: 256 KB flags: (pae sse) clocked at 1665.257 MHz
Graphics: Card: S3 VT8375 [ProSavage8 KM266/KL266]
X.Org: 1.12.4 drivers: savage (unloaded: fbdev,vesa) Resolution: 1024x768@87.0hz
GLX Renderer: Gallium 0.4 on softpipe GLX Version: 2.1 Mesa 8.0.5
Audio: Card: VIA VT8233/A/8235/8237 AC97 Audio Controller driver: snd_via82xx Sound: ALSA ver: k3.12-0.bpo.1-686-pae
Network: Card: Realtek RTL-8139/8139C/8139C+ driver: 8139too
IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: 00:40:ca:46:5b:e6
Partition: ID: / size: 363M used: 5.3M (2%) fs: rootfs
Sensors: System Temperatures: cpu: 40.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 98 Uptime: 8 min Memory: 178.5/468.9MB Client: Shell (bash) inxi: 1.9.16
demo@mx1:~
$ free
total used free shared buffers cached
Mem: 480112 466408 13704 0 90332 195084
-/+ buffers/cache: 180992 299120
Swap: 0 0 0
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 1:44 am
by BitJam
namida12 wrote:Could not boot this older Compaq, only got a blinking cursor on black screen
At what stage in the boot process did this happen?
Since antiX is booting okay, maybe there is a mismatch between the machine that burned the dvd and this machine trying to read. A relatively easy way to check the dvd on the older Compaq is to mount the dvd and then check the md5sum of the files linuxfs, vmlinuz, and initrd.gz in the /antiX directory. For example:
Code: Select all
$ md5sum /media/dvd/antiX/linuxfs
f046ac305aab5c9d14a9ca395b5108c4 /media/dvd/antiX/linuxfs
$ cat /media/dvd/linuxfs.md5
f046ac305aab5c9d14a9ca395b5108c4 iso/antiX/linuxfs
If you want to run these tests from a antiX LiveCD session then just select "F4 Options" --> "to ram" in the bootloader. This will allow you to eject the antiX LiveCD and insert the MX LiveDVD.
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 1:48 am
by james c
One more quick test run....all IDE drives on this old box.All good on initial boot.
Code: Select all
demo@mx1:~
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: Mobo: MICRO-STAR INTL model: MS-7037 version: Ver 0A Bios: Phoenix version: 6.00 PG date: 06/08/2004
CPU: Single core Intel Pentium 4 CPU (-HT-) cache: 512 KB flags: (pae sse sse2)
Clock Speeds: 1: 3000.721 MHz 2: 3000.721 MHz
Graphics: Card: Intel 82865G Integrated Graphics Controller
X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x768@85.0hz
GLX Renderer: Mesa DRI Intel 865G x86/MMX/SSE2 GLX Version: 1.3 Mesa 8.0.5
Audio: Card: Intel 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller driver: snd_intel8x0
Sound: Advanced Linux Sound Architecture ver: k3.12-0.bpo.1-686-pae
Network: Card: Realtek RTL-8139/8139C/8139C+ driver: 8139too
IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: 00:11:09:27:3b:5a
Drives: HDD Total Size: 200.0GB (-) 1: id: /dev/sda model: WDC_WD2000JB size: 200.0GB
Partition: ID: / size: 1.6G used: 5.3M (1%) fs: rootfs ID: swap-1 size: 2.20GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 37.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 108 Uptime: 7 min Memory: 171.6/2016.2MB Client: Shell (bash) inxi: 1.9.16
demo@mx1:~
$ free
total used free shared buffers cached
Mem: 2064588 658840 1405748 0 88920 395740
-/+ buffers/cache: 174180 1890408
Swap: 2150396 0 2150396
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:02 am
by whell
namida12 wrote:
Default QupZilla is a bit iffy, freezing any time there is a flash problem.
Plays Jpop well on Sky.FM however!
JR
Similar results here. QupZilla doesn't seem to like my Yahoo mail. I get taken to a page in Yahoo that asks me to use IE or Firefox instead. If I click on a link that allows me to proceed to Yahoo mail with QupZilla, Yahoo sends me back to the IE/Firefox page. The good news is that Firefox installs fast and easy with the meta-installer.

Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:19 am
by kmathern
whell wrote:namida12 wrote:
Default QupZilla is a bit iffy, freezing any time there is a flash problem.
Plays Jpop well on Sky.FM however!
JR
Similar results here. QupZilla doesn't seem to like my Yahoo mail. I get taken to a page in Yahoo that asks me to use IE or Firefox instead. If I click on a link that allows me to proceed to Yahoo mail with QupZilla, Yahoo sends me back to the IE/Firefox page. The good news is that Firefox installs fast and easy with the meta-installer. ;)
Qupzilla works a lot better for me, midori would crash on a lot of sites (gmail, yahoo, random sites returned in search results that I would try to go to).
As far as yahoo requiring IE/Firefox, is there a way to change Qupzilla's user agent?
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:28 am
by Silent Observer
Wow, this looks like it could be a good candidate to replace antiX on my second desktop machine, maybe even in place of MEPIS on my quad-core -- but I have a question: the mention of a PAE kernel seems to imply MX is 32-bit (if 64-bit, it wouldn't need PAE to access large RAM installation). Is there a 64-bit version, or some advantage to running a 32-bit kernel on 64-bit capable systems?
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:30 am
by Gaer Boy
kmathern wrote:As far as yahoo requiring IE/Firefox, is there a way to change Qupzilla's user agent?
Yes - under 'Other' in Edit>Preferences.
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:32 am
by dolphin_oracle
There is a user agent manager in Preferences>Other.
yahoomail works, but you do get that screen warning you to "upgrade"
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:36 am
by Jerry3904
As far as yahoo requiring IE/Firefox, is there a way to change Qupzilla's user agent?
Edit > Preferences > Other
EDIT: wow, 3 responses in 1 minute, gotta be some kind of record
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:41 am
by Jerry3904
Silent Observer wrote:Wow, this looks like it could be a good candidate to replace antiX on my second desktop machine, maybe even in place of MEPIS on my quad-core -- but I have a question: the mention of a PAE kernel seems to imply MX is 32-bit (if 64-bit, it wouldn't need PAE to access large RAM installation). Is there a 64-bit version, or some advantage to running a 32-bit kernel on 64-bit capable systems?
Yup, 32 bit, no plans for a 64-bit version
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:48 am
by Gaer Boy
Jerry3904 wrote:As far as yahoo requiring IE/Firefox, is there a way to change Qupzilla's user agent?
Edit > Preferences > Other
EDIT: wow, 3 responses in 1 minute, gotta be some kind of record
The record is that they all say the same!
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 10:42 am
by golinuxgo
whell wrote:Similar results here. QupZilla doesn't seem to like my Yahoo mail. I get taken to a page in Yahoo that asks me to use IE or Firefox instead. If I click on a link that allows me to proceed to Yahoo mail with QupZilla, Yahoo sends me back to the IE/Firefox page. The good news is that Firefox installs fast and easy with the meta-installer.

I think it's more than a QupZilla problem. I access one of my Yahoo emails on Squeeze with Galeon and observed this same behavior begin yesterday. It's stuck on a loop back to a Firefox/Safari update announcement. Very annoying. But then the Yahoo redesign is a disaster in so many ways . . .
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 11:03 am
by KrispyKritter
System is now installed and ready for testing.
First observations:
Startup fast
Found Wireless Network without any problems
Recognized and set up mature Wacom Tablet
Desktop will take a little getting time to embrace. Been with KDE, Gnome, or Unity for too long.
Shutdow fast
It looks like something I can put to good use.
Steve
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 11:07 am
by Jerry3904
Desktop will take a little getting time to embrace.
Suggest you read the QuickStart document (question mark on Panel) to get going.
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 12:26 pm
by KrispyKritter
Jerry,
It just takes some "old" folks a little longer to get used to something different.

Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 12:28 pm
by lucky9
Silent Observer wrote:Wow, this looks like it could be a good candidate to replace antiX on my second desktop machine, maybe even in place of MEPIS on my quad-core -- but I have a question: the mention of a PAE kernel seems to imply MX is 32-bit (if 64-bit, it wouldn't need PAE to access large RAM installation). Is there a 64-bit version, or some advantage to running a 32-bit kernel on 64-bit capable systems?
There's a few more computers out there that can use a 32-bit OS. Most of those will run a PAE kernel. (For instance my Atom NetBook is 32-bit only, but will use a PAE kernel.) Super old hardware will need antiX. It's i486 version will run on almost anything. Including the latest and greatest.
If you need 64-bit then Mepis is ready and waiting.
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 1:00 pm
by dolphin_oracle
there is one advantage to running a 32 bit kernel on a 64bit system, at least if you have more than 4gb of ram and support the PAE .
Debian multi-arch is an evolving beast, and a lot of popular apps (brother printer drivers, netflix-desktop, steam, I'm looking at you) are 32 bit only. You can install them on a 64bit system, but you run into having to have multiple libraries installed. and with MX's extensive use of wheezy-backports, I'm not so sure that a 64 bit system will not have problems, particularly with ia32-libs (a perennial source of pain for me).
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 3:25 pm
by namida12
Trying beta2 on another system with a Biostar Motherboard :
demo@mx1:~/Desktop
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: Mobo: N/A model: nForce Bios: Phoenix version: 6.00 PG date: 08/26/2005
CPU: Single core AMD Athlon 64 3400+ (-UP-) cache: 512 KB flags: (lm nx pae sse sse2 sse3) clocked at 2411.705 MHz
Graphics: Card: NVIDIA G73 [GeForce 7300 GT]
X.Org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz
GLX Renderer: Gallium 0.4 on NV4B GLX Version: 2.1 Mesa 8.0.5
Audio: Card: NVIDIA nForce3 250Gb AC'97 Audio Controller driver: snd_intel8x0 Sound: ALSA ver: k3.12-0.bpo.1-686-pae
Network: Card: NVIDIA CK8S Ethernet Controller driver: forcedeth
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:16:ec:77:4f:22
Drives: HDD Total Size: 163.9GB (-) 1: id: /dev/sda model: Maxtor_6Y160P0 size: 163.9GB
Partition: ID: / size: 793M used: 4.3M (1%) fs: rootfs
Sensors: System Temperatures: cpu: 40.0C mobo: N/A gpu: 58.0
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 106 Uptime: 4 min Memory: 174.2/1008.2MB Client: Shell (bash) inxi: 1.9.16
demo@mx1:~/Desktop
$
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 3:47 pm
by Silent Observer
lucky9 wrote:Silent Observer wrote:Wow, this looks like it could be a good candidate to replace antiX on my second desktop machine, maybe even in place of MEPIS on my quad-core -- but I have a question: the mention of a PAE kernel seems to imply MX is 32-bit (if 64-bit, it wouldn't need PAE to access large RAM installation). Is there a 64-bit version, or some advantage to running a 32-bit kernel on 64-bit capable systems?
There's a few more computers out there that can use a 32-bit OS. Most of those will run a PAE kernel. (For instance my Atom NetBook is 32-bit only, but will use a PAE kernel.) Super old hardware will need antiX. It's i486 version will run on almost anything. Including the latest and greatest.
If you need 64-bit then Mepis is ready and waiting.
Yep, I've got two machines in the house that can only run 32-bit (both currently on antiX 13.2). I was checking whether MX might replace MEPIS for me (having a more current kernel and other parts might, for instance, allow installing Pepper Flash, which won't go on MEPIS 11).
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 3:57 pm
by kmathern
Silent Observer wrote:Yep, I've got two machines in the house that can only run 32-bit (both currently on antiX 13.2). I was checking whether MX might replace MEPIS for me (having a more current kernel and other parts might, for instance, allow installing Pepper Flash, which won't go on MEPIS 11).
There's a pepperflashplugin-nonfree in wheezy-backports. so yes you'll be able to install it.
The pepperflashplugin has the same sse2 requirement that the other flashplugin has, so you still might not be able to use it with old 32bit machines.
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 6:59 pm
by tascoast
No problems downloading via the Sourceforge source nor installing under VirtualBox (PAE already checked/anticipated by VB this time around), and I now have both betas running this way with no drama.
I'm going to explore the USB approach next I think and making ISOs after that, two things that perhaps make MX-14 (antiX etc too I think) particularly interesting if I understand the implications ie. a 'portable' OS (within reason, hardware being similar to initial setup) and burning a current MX-14 setup to disc as an ISO for easy reinstall (unlike others, with updates and personal settings, updates and modifications included). These features will make me learn a bit more but seem to fly under the radar as far as beginners go and might deserve a bit of emphasis.
I can't comment on wireless support as such, using VB (it passes to the machine fine as expected), although this would be a nice bit of icing and make me figure out how to go from XP/M 11 dual boot to adding MX-14 as a third boot option, although it is something I'd probably want to set up anyway over time after working of a USB.
kindly
Mick
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 8:19 pm
by BitJam
tascoast wrote:
I'm going to explore the USB approach next I think and making ISOs after that, two things that perhaps make MX-14 (antiX etc too I think) particularly interesting if I understand the implications ie. a 'portable' OS (within reason, hardware being similar to initial setup) ...
If you develop on a LiveUSB (or a frugal install) then the situation is actually a little better than this because you drop the requirement for similar hardware. The whole Live hardware detection system stays intact. If you have plenty of RAM on your development system then add and remove packages to suit your taste and when you are done (before you reboot) run remaster-live via the RemasterCC (CC= Control Centre). If you want to save system changes across reboots without having to remaster each time then enable root persistence via the same RemasterCC. If you don't have much RAM on your development system then you need to either remaster-live frequently (to move fs changes from RAM to squashfs on disk) or enable Root Persistence and choose Static Root Persistence in the bootloader menu (which always saves fs changes on disk). You are free to switch between Static and Dynamic Persistence (or to go back to no persistence) every time you boot (unless all your file system changes are too big to fit into RAM in which case you can't use Dynamic Persistence).
If you want to create a family of respins and make both 64-bit and 32-bit versions then the build-antiX-iso system might be a better fit. IIRC, it is currently being used to make all six versions of antiX as well as MX and an antiX music respin. Until the final MX-14 gets out the door there might not be a lot of help available to get your started using the system.
NOTE: the one step that is not yet automated in the LiveUSB is the creation of a .iso file from the LiveUSB. It involves just two commands: genisoimage and isohybrid.
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 9:00 pm
by namida12
Using live Media to run MX-14:
Machine: Mobo: Biostar Motherboard: nForce Bios: Phoenix version: 6.00 PG date: 08/26/2005
CPU: Single core AMD Athlon 64 3400+ (-UP-) cache: 512 KB flags: (lm nx pae sse sse2 sse3) clocked at 2411.705 MHz
Graphics: Card: NVIDIA G73 [GeForce 7300 GT]
I am trying to move files from sda1 to /media/backup-2013 (a USB 2.0 external drive), and it has continued to lock up/freeze with 400 Gigs free on the external drive. This is the first problem I have had with the live media. Earlier today I moved 50 gigs without any problems occurring. But have tried several times without success to move more files, and just ended up with a (.fuse hidden 000000x00) file that could not be deleted. Confused not understanding this slowdown. I only have about 1 gig more to save to external drive, and then i can format the drive...
Edit: have managed to move the remaining files, and now tumbler is active keeping the volume busy, and it tells me I should not disconnect the drive. This is the bug, that tumbler has? since i am on a demo, believe this should not create a problem, but not certain...
Funny, I recently realized when you drag a file from one drive to another drive it does not give you the choice to "copy" or "move", is there a setting i need to change to have this choice again, seem to remember Mepis 11.9.92 giving me that option.
Re: MX-14 beta 2
Posted: Wed Feb 05, 2014 10:42 pm
by BitJam
@namida12, the hidden .fuse file is a copy of a file you deleted/moved while another process still had it open. This will happen with file systems mounted via fuse (filesystem in userspace), most likely NTFS. I imagine the other process that had the file open was tumbler. For more about this problem with tumber see
this thread.
I am trying to move files from sda1 to /media/backup-2013 (a USB 2.0 external drive), and it has continued to lock up/freeze with 400 Gigs free on the external drive.
This symptom would occur if you were mistakenly moving a lot of data to the LiveCD/USB root file system. All changes to that file system are stored in RAM so when you copy too much information into it, you run out of RAM and the system freezes up. When you reboot then all signs of this are gone. I'm not sure that is what happened but it is a simple explanation. This could also happen if you copied a bunch of files to a file system that is mounted as tmpfs (which stores the entire filesystem in RAM).
In the future you can run the following in a terminal window:
where $DIRECTORY is where you plan to copy files. This will tell you what the underlying file system is for that directory. If it tells you the underlying filesystem is "/live/aufs" then you don't want to fill it with files.
Also, you can monitor how much RAM is being used for the root file system with either one of these commands:
Code: Select all
$ df -h /live/aufs-ram
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.2G 1.7M 1.2G 1% /live/aufs-ram
This shows you how much RAM is being used by the file system and how much is theoretically available although you may run out of RAM before that limit is reached.
The other command is simply
Code: Select all
$ free -m
total used free shared buffers cached
Mem: 1516 144 1371 0 0 47
-/+ buffers/cache: 96 1419
Swap: 0 0 0
With the -m flag all sizes are in megabytes. The number you are interested is in the "cached" column. Among other things, this number includes all of the RAM used by the LiveCD/USB root file system and all tmpfs file systems. Most programs that monitor memory usages *ignore* the RAM that is used as cache assuming the system can reclaim that memory when it is needed. On a LiveCD/USB (or any system that stores a significant amount of data on tmpfs) this is a very bad assumption. So if you copy a bunch of files to the root file system of a LiveCD/USB you may end up running out of memory with little warning. The 47 meg in the "free" command output is larger than the 1.7M in the "df" output because the "free" output includes all other forms of cached data.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 7:34 am
by Silent Observer
kmathern wrote:Silent Observer wrote:Yep, I've got two machines in the house that can only run 32-bit (both currently on antiX 13.2). I was checking whether MX might replace MEPIS for me (having a more current kernel and other parts might, for instance, allow installing Pepper Flash, which won't go on MEPIS 11).
There's a pepperflashplugin-nonfree in wheezy-backports. so yes you'll be able to install it.
The pepperflashplugin has the same sse2 requirement that the other flashplugin has, so you still might not be able to use it with old 32bit machines.
I've got one system currently running 32-bit MEPIS on which I had to add an antiX install to allow a user to play Flash based games that require a Pepper generation Flash plugin -- converting that system entirely to MX would resolve that (though users would still have to use Chrome/Chromium to have Pepper). The 32-bit CPU systems won't be helped on that front; one is the last processor AMD made that didn't support SSE2, the other is a Pentium II 300 MHz.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 7:51 pm
by golinuxgo
I just pulled out an old HP Celeron computer that hadn't been booted in over 500 days. It had an old squeeze install that I was using to play with window managers etc. MX-14 live loaded but there were problems. QupZilla crashed every time it tried to pull up a web page. The page would appear for a few seconds and then . . . poof. Then I thought I would try installing. It failed with this message and I had to push the button:
minstall
Sorry, failed to create a user directory.
In all fairness I was not very focused - cooking and working on another 'puter at the same time. I'll try again later maybe with AntiX. At least I was able to get the system specs onto a flash drive. Maybe you gurus will see something in there that could be a problem:
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: No /sys/class/dmi, using dmidecode: you must be root to run dmidecode
CPU: Single core Celeron (Coppermine) (-UP-) cache: 128 KB flags: (pae sse) clocked at 664.621 MHz
Graphics: Card: Intel 82810 (CGC) Graphics Controller
X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1280x1024@60.0hz
GLX Renderer: Gallium 0.4 on softpipe GLX Version: 2.1 Mesa 8.0.5
Audio: Card: Intel 82801AA AC'97 Audio Controller driver: snd_intel8x0 Sound: ALSA ver: k3.12-0.bpo.1-686-pae
Network: Card: Broadcom NetXtreme BCM5705 Gigabit Ethernet driver: tg3
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:10:18:0c:5f:7c
Drives: HDD Total Size: 30.0GB (-) 1: id: /dev/sda model: QUANTUM_FIREBALL size: 30.0GB
Partition: ID: / size: 388M used: 3.8M (1%) fs: rootfs ID: swap-1 size: 1.03GB used: 0.00GB (0%) fs: swap
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 100 Uptime: 5 min Memory: 140.0/499.6MB Client: Shell (bash) inxi: 1.9.16
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 8:27 pm
by BitJam
@golinuxgo, my first thought was not enough memory but
james c says
his 512 Meg machine worked fine.
I suggest you try launching "qupzilla" from the command line in a terminal window. Perhaps there will be some more useful output when it crashes. If the kernel is having problems then there might be useful information in the output of "dmesg".
It is also possible that you need to do a command-line install on this machine. Unfortunately, this bootloader option is broken on beta-2. You can kill off the GUI with the command (as root):
You can use <ctrl><alt><Fn> to get to a virtual console where "n" is in 1 -- 6. Once there you can move between virtual consoles with <alt><left-arrow> and <alt><right-arrow>. Use <shift><pgup> and <shift><pgdn> for limited scrolling.
You might want to mount your flash drive in XFCE before you kill it although I'm not certain it will stay mounted.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 8:41 pm
by Jerry3904
And, again, just a reminder that MX-14 is not designed for low-end machines--where antiX rules.
This is a "midweight" distro.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 8:50 pm
by uncle mark
Jerry3904 wrote:And, again, just a reminder that MX-14 is not designed for low-end machines--where antiX rules.
This is a "midweight" distro.
While not disagreeing, I will tell you it works well on my 750MHz PIII with 512MB. Surprisingly so. I was quite taken aback at how well, actually.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 8:52 pm
by golinuxgo
Jerry3904 wrote:And, again, just a reminder that MX-14 is not designed for low-end machines--where antiX rules.
This is a "midweight" distro.
I previously had squeeze with gnome2 and xfce desktops installed on this machine so I thought MX-14 might work OK. Unfortunately I don't have free space on my other testing machine to install MX-14 right now.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 9:05 pm
by Jerry3904
uncle mark wrote:Jerry3904 wrote:And, again, just a reminder that MX-14 is not designed for low-end machines--where antiX rules.
This is a "midweight" distro.
While not disagreeing, I will tell you it works well on my 750MHz PIII with 512MB. Surprisingly so. I was quite taken aback at how well, actually.
Good to know. I only keep mentioning this b/c I want to avoid the use of the word "lightweight": everybody uses it, and some (like antiX) actually make it work extremely well. Just from a marketing perspective (--> my job), the "lightweight" field is saturated.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 9:10 pm
by uncle mark
Jerry3904 wrote:uncle mark wrote:Jerry3904 wrote:And, again, just a reminder that MX-14 is not designed for low-end machines--where antiX rules.
This is a "midweight" distro.
While not disagreeing, I will tell you it works well on my 750MHz PIII with 512MB. Surprisingly so. I was quite taken aback at how well, actually.
Good to know. I only keep mentioning this b/c I want to avoid the use of the word "lightweight": everybody uses it, and some (like antiX) actually make it work extremely well. Just from a marketing perspective (--> my job), the "lightweight" field is saturated.
I gotchya. Me and anti had a brief bit of fun with this earlier. Some people think Linux is supposed to run on a toaster, and if you call something "lightweight", they'll try and install it on one.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 9:12 pm
by megatotoro
Jerry3904 wrote:uncle mark wrote:Jerry3904 wrote:And, again, just a reminder that MX-14 is not designed for low-end machines--where antiX rules.
This is a "midweight" distro.
While not disagreeing, I will tell you it works well on my 750MHz PIII with 512MB. Surprisingly so. I was quite taken aback at how well, actually.
Good to know. I only keep mentioning this b/c I want to avoid the use of the word "lightweight": everybody uses it, and some (like antiX) actually make it work extremely well. Just from a marketing perspective (--> my job), the "lightweight" field is saturated.
I'd add "ideal for netbooks" to it. My Toshiba NB-100 agrees!
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 9:21 pm
by Jerry3904
Totally agree! I have two, both running extremely well with MX-14.
Re: MX-14 beta 2
Posted: Thu Feb 06, 2014 11:36 pm
by namida12
BitJam wrote:@namida12, the hidden .fuse file is a copy of a file you deleted/moved while another process still had it open. This will happen with file systems mounted via fuse (filesystem in userspace), most likely NTFS. I imagine the other process that had the file open was tumbler. For more about this problem with tumber see
this thread.
I am trying to move files from sda1 to /media/backup-2013 (a USB 2.0 external drive), and it has continued to lock up/freeze with 400 Gigs free on the external drive.
This symptom would occur if you were mistakenly moving a lot of data to the LiveCD/USB root file system. All changes to that file system are stored in RAM so when you copy too much information into it, you run out of RAM and the system freezes up. When you reboot then all signs of this are gone. I'm not sure that is what happened but it is a simple explanation. This could also happen if you copied a bunch of files to a file system that is mounted as tmpfs (which stores the entire filesystem in RAM).
In the future you can run the following in a terminal window:
where $DIRECTORY is where you plan to copy files. This will tell you what the underlying file system is for that directory. If it tells you the underlying filesystem is "/live/aufs" then you don't want to fill it with files.
Also, you can monitor how much RAM is being used for the root file system with either one of these commands:
Code: Select all
$ df -h /live/aufs-ram
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.2G 1.7M 1.2G 1% /live/aufs-ram
This shows you how much RAM is being used by the file system and how much is theoretically available although you may run out of RAM before that limit is reached.
The other command is simply
Code: Select all
$ free -m
total used free shared buffers cached
Mem: 1516 144 1371 0 0 47
-/+ buffers/cache: 96 1419
Swap: 0 0 0
With the -m flag all sizes are in megabytes. The number you are interested is in the "cached" column. Among other things, this number includes all of the RAM used by the LiveCD/USB root file system and all tmpfs file systems. Most programs that monitor memory usages *ignore* the RAM that is used as cache assuming the system can reclaim that memory when it is needed. On a LiveCD/USB (or any system that stores a significant amount of data on tmpfs) this is a very bad assumption. So if you copy a bunch of files to the root file system of a LiveCD/USB you may end up running out of memory with little warning. The 47 meg in the "free" command output is larger than the 1.7M in the "df" output because the "free" output includes all other forms of cached data.
Quote: "This symptom would occur if you were mistakenly moving a lot of data to the LiveCD/USB root file system."
Would this be correct?
I was trying to copy files from a hard drive 130 gig sda1 formatted as ext3, and only holding data to a 1 Gig external hard drive " /media/backup-2013 formatted as ect4" not to a usb flash drive. Not a NTFS formatted hard drive.
All the problems started when the .fuse file appeared. I could not delete, copy or move the .fuse hidden file, but after renaming the file, I then copied it to the external drive and once there I was able to delete it easily in both drives. But could not shut down the system, I ended up shutting down the computer holding the power button for 5 seconds, walked away for a few minutes with system powered down. Later restarted the live media, and then was able to continue copying the files, to the external hard drive, once the hidden fuse file was deleted on both hard drives.
Maybe this was another instance of the tumber bug. But i do not have a record of what happened, and do not want to try and recreate the problem. The 120 Gig hard drive was recycled using dban to make certain it was not easily read, and that drive is powering another AntiX operating system as a replacement for a malware infected WinXP owner, that has been converted to Linux. She is delighted, and she was playing a Facebook game when i left her on her own.
One machine at a time, as WinXP get closer to its end of life... I was hesitant to use MX-14, and decided on AntiX, but really think MX-14 is going to be a good O/S for winXP users.
JR
Re: MX-14 beta 2
Posted: Fri Feb 07, 2014 12:15 am
by james c
Another old machine.....MX latest live. 512 mb of ram again w/swap but a much slower P3 compared to the 1.7 Ghz Athlon XP box.
Qupzilla seems ok for basic browsing but sites like Youtube lead to an immediate and sudden crash.Problem didn't seem to appear with the faster cpu.
Code: Select all
-demo@mx1:~
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: System: Micro-Star product: MS-6215 version: 0000000
Mobo: Micro-Star model: MS-6351 version: 1.0 Bios: American Megatrends version: 62710 date: 03/30/01
CPU: Single core Pentium III (Coppermine) (-UP-) cache: 256 KB flags: (pae sse) clocked at 863.754 MHz
Graphics: Card: Intel 82815 Graphics Controller (CGC)
X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x768@85.0hz
GLX Renderer: Gallium 0.4 on softpipe GLX Version: 2.1 Mesa 8.0.5
Audio: Card: Intel 82801BA/BAM AC'97 Audio Controller driver: snd_intel8x0 Sound: ALSA ver: k3.12-0.bpo.1-686-pae
Network: Card: Intel 82801BA/BAM/CA/CAM Ethernet Controller driver: e100
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:10:dc:a8:50:d9
Drives: HDD Total Size: 40.0GB (-) 1: id: /dev/sda model: WDC_WD400EB size: 40.0GB
Partition: ID: / size: 388M used: 13M (4%) fs: rootfs ID: swap-1 size: 1.15GB used: 0.00GB (0%) fs: swap
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 99 Uptime: 9 min Memory: 179.6/499.5MB Client: Shell (bash) inxi: 1.9.16
demo@mx1:~
Code: Select all
$ free
total used free shared buffers cached
Mem: 511536 490988 20548 0 96924 211732
-/+ buffers/cache: 182332 329204
Swap: 1126396 240 1126156
Re: MX-14 beta 2
Posted: Fri Feb 07, 2014 12:20 am
by BitJam
namida12 wrote:Would this be correct?
Drop the dollar-sign:
I was trying to copy files from a hard drive 130 gig sda1 formatted as ext3, and only holding data to a 1 Gig external hard drive " /media/backup-2013 formatted as ect4" not to a usb flash drive. Not a NTFS formatted hard drive.
If you are interested or curious, I suggest you Google(fuse hidden file). There are many complaints about not being able to delete these files. I got the impression they only showed up on fuse mediated filesystems but maybe I was wrong.
All the problems started when the .fuse file appeared. [...] Maybe this was another instance of the tumber bug.
I suggest you turn tumbler off. It was off by default in beta-1 and will likely be off by default in beta-3 and beyond. Something strange happened on your system. Hopefully you will not encounter it again which would mean we probably will never find out what actually happened.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 12:00 am
by golinuxgo
golinuxgo wrote:Jerry3904 wrote:And, again, just a reminder that MX-14 is not designed for low-end machines--where antiX rules.
This is a "midweight" distro.
I previously had squeeze with gnome2 and xfce desktops installed on this machine so I thought MX-14 might work OK. Unfortunately I don't have free space on my other testing machine to install MX-14 right now.
Here's a followup on my attempt to install MX-14 posted
here. This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:
/boot/grub is not readable by GRUB on boot. Installation is impossible . . .
I have no idea where the install went sideways. But I do know that refracta (with xfce) installed and booted successfully shortly thereafter. Sure it lumbers along and the internet is not really usable. But it BOOTS and WORKS! I have retired that old 'toaster' for now but may try to install AntiX on it when I have some spare time maybe this summer.
Final comment . . . this has been the crankiest distro, I've ever played with. I really, REALLY wanted to like it but it seems it was not meant to be. Bummer. Maybe the final release will have the kinks worked out . . .
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 2:59 am
by lucky9
golinuxgo wrote:
This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:
There isn't one? No MBR? What do you have?
If you don't install GRUB to the MBR you won't get to the /boot/grub/menu.list which is where the OS will boot from. You didn't use another distro to chainload either. How could you think you could boot the OS?
There has to be a way for /boot/grub/menu.list to be called so it can boot the OS.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 3:15 am
by golinuxgo
lucky9 wrote:golinuxgo wrote:
This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:
There isn't one? No MBR? What do you have?
If you don't install GRUB to the MBR you won't get to the /boot/grub/menu.list which is where the OS will boot from. You didn't use another distro to chainload either. How could you think you could boot the OS?
There has to be a way for /boot/grub/menu.list to be called so it can boot the OS.
Good heavens! I've been using distros with grub2 for the last 3 years at least, probably longer. This distro doesn't??? I can barely remember /boot/grub/menu.list . . .
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 5:52 am
by richb
golinuxgo wrote:[
Good heavens! I've been using distros with grub2 for the last 3 years at least, probably longer. This distro doesn't??? I can barely remember /boot/grub/menu.list . . .
It does use grub2 and there is no /boot/menu.list in grub2 as you said.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 9:04 am
by ko
lucky9 wrote:golinuxgo wrote:
This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:
There isn't one? No MBR? What do you have?
If you don't install GRUB to the MBR you won't get to the /boot/grub/menu.list which is where the OS will boot from. You didn't use another distro to chainload either. How could you think you could boot the OS?
There has to be a way for /boot/grub/menu.list to be called so it can boot the OS.
You're (nearly) absolutely right, but it's /boot/grub/grub.cfg, NOT /boot/grub/menu.list
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 9:09 am
by uncle mark
richb wrote:golinuxgo wrote:Good heavens! I've been using distros with grub2 for the last 3 years at least, probably longer. This distro doesn't??? I can barely remember /boot/grub/menu.list . . .
It does use grub2 and there is no /boot/menu.list in grub2 as you said.
Yeah, lucky got his terms mixed up a bit, but...
The OP still needs to explain how he expects to boot MX-14. If he put grub on root, then he has to invoke it from some other method.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 9:28 am
by GuiGuy
golinuxgo wrote:........
Final comment . . . this has been the crankiest distro, I've ever played with. I really, REALLY wanted to like it but it seems it was not meant to be. Bummer. Maybe the final release will have the kinks worked out . . .
Your opinion appears to be based on trying MX on an unsuitable machine.
My opinion is very different: this is the most promising beta I have ever played with.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 10:29 am
by whell
GuiGuy wrote:golinuxgo wrote:........
Final comment . . . this has been the crankiest distro, I've ever played with. I really, REALLY wanted to like it but it seems it was not meant to be. Bummer. Maybe the final release will have the kinks worked out . . .
Your opinion appears to be based on trying MX on an unsuitable machine.
My opinion is very different: this is the most promising beta I have ever played with.
Ditto. My beta 2 has been running steady for a week, and nary a hick-up. I've streamed audio and video, served music and video files, traded files with my wife's Windows box, and all has worked great.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 10:40 am
by kmathern
golinuxgo wrote:I just pulled out an old HP Celeron computer that hadn't been booted in over 500 days. It had an old squeeze install that I was using to play with window managers etc. MX-14 live loaded but there were problems. QupZilla crashed every time it tried to pull up a web page. The page would appear for a few seconds and then . . . poof....
... Maybe you gurus will see something in there that could be a problem:
Code: Select all
$ inxi -F
System: Host: mx1 Kernel: 3.12-0.bpo.1-686-pae i686 (32 bit)
Desktop: Xfce 4.10.2 Distro: MX-14_13.98_386-xfce beta2 30 January 2014
Machine: No /sys/class/dmi, using dmidecode: you must be root to run dmidecode
CPU: Single core Celeron (Coppermine) (-UP-) cache: 128 KB flags: (pae sse) clocked at 664.621 MHz
You have the SSE2 problem noted in these two threads:
http://forum.mepiscommunity.org/viewtop ... 91&t=35543 &
http://forum.mepiscommunity.org/viewtop ... 91&t=35541. Your Celeron/Coppermine cpu lacks sse2 support, so any web page you go to with flash content will crash Qupzilla.
GParted locks up? MX-14 beta 2
Posted: Sun Feb 09, 2014 10:51 am
by entropyfoe
The beta2 booted into a live session (beta 1 did not) on my old A7N8X mother board.
OK, so I found an old PATA drive in the parts bin and installed it so I could install MX-14.
This old machine has a working XP installation on a SATA drive that I have disconnected the power on so it is undisturbed.
From the live session, I can see the new PATA drive and access the files. But I cannot launch GParted to repartition the drive.
I supply root credentials an d everything locks up, no mouse cursor nothing works until I Ctrl Shift SysRq REISUB.
So, then I tried to install, thinking I could partition as part of the install, but when I get to the part to modify partitions, same lock up.
Any ideas what to try?
Has anyone used GParted from the beta2 live session?
-Jay
Re: GParted locks up? MX-14 beta 2
Posted: Sun Feb 09, 2014 10:54 am
by malspa
entropyfoe wrote:
Has anyone used GParted from the beta2 live session?
I have the live session booted up right now, but here GParted starts up just fine.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 2:19 pm
by muskt
I am still not able to get Samba to work on MX-14 B2.
I have it installed on 2 machines and can't figure it out.
I used the meta-installer-more than once-and it tells me it completed successfully.
I went into Synaptic, and downloaded the Help for Samba--There is absolutely no way for me to know where it went--I cannot locate it.
I searched the web, & found numerous "instructions" for installing & configuring Samba--None of these appeared close to MX-14.
I have, in the past, been successful with getting Mepis to talk to Windows; however, not with MX.
Anyone feel like providing me a "walkthrough" to get this going?
Thanks,
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 2:40 pm
by mariel77
Hi, it's great to see all of you working on a new distro. Congrats!
I'm trying it because I need something newer on my desktop.
(I can't get M12 beta to boot; just black screen. I tried all my usual boot codes, but nothing, so here I am.)
I can't login once I install; the login screen just refreshes over and over.
I downloaded the iso (13.98) , the md5sum matched. I first burned a DVD (4x speed). MX-14 booted fine with the default, found my wifi, looked great, so I installed. The first install I didn't check Auto login. Got the screen that just refreshed on Login.
Burned a CD (same iso). This time on install I checked Auto login, but the same thing happens.
Any suggestions? Thank you!!
Here is my $ inxi -F -f (on my Mepis11 install; do you need it for the live MX-14?)
System: Host: MarielAcer Kernel: 2.6.36-1-mepis-smp i686 (32 bit) Desktop: KDE 4.5.3 Distro: unknown
Machine: System: Acer product: Aspire T180 version: R01-A2
Mobo: Acer model: EM61SM/EM61PM Bios: Phoenix version: R01-A2 date: 09/14/2006
CPU: Dual core AMD Athlon 64 X2 3800+ (-MCP-) cache: 1024 KB
Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz
CPU Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx
fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm
extapic cr8_legacy
Graphics: Card: nVidia C61 [GeForce 6100 nForce 405] X.Org: 1.7.7 driver: nvidia Resolution: 1600x900@50.0hz
GLX Renderer: GeForce 6100 nForce 405/PCI/SSE2/3DNOW! GLX Version: 2.1.2 NVIDIA 260.19.21
Audio: Card: nVidia MCP61 High Definition Audio driver: HDA Intel Sound: ALSA ver: 1.0.23
Network: Card-1: Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver: sky2
IF: eth0 state: down mac: 00:19:21:55:b5:84
Card-2: 3Com 3c905C-TX/TX-M [Tornado] driver: 3c59x
IF: eth1 state: down mac: 00:01:02:6a:65:17
Card-3: Ralink RT2501/RT2573 Wireless Adapter driver: rt73usb
IF: wlan0 state: up mac: 00:0e:2e:e6:08:77
Drives: HDD Total Size: 750.2GB (15.0% used) 1: id: /dev/sda model: Hitachi_HDT72502 size: 250.1GB
2: id: /dev/sdb model: Hitachi_HDS72105 size: 500.1GB
Partition: ID: / size: 15G used: 6.4G (45%) fs: ext3 ID: /home size: 49G used: 8.3G (19%) fs: ext3
ID: swap-1 size: 2.10GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 40.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 189 Uptime: 12 min Memory: 690.6/3294.7MB Client: Shell (bash) inxi: 1.8.26
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 2:46 pm
by afab4
muskt wrote:I am still not able to get Samba to work on MX-14 B2.
I have it installed on 2 machines and can't figure it out.
I used the meta-installer-more than once-and it tells me it completed successfully.
I went into Synaptic, and downloaded the Help for Samba--There is absolutely no way for me to know where it went--I cannot locate it.
I searched the web, & found numerous "instructions" for installing & configuring Samba--None of these appeared close to MX-14.
I have, in the past, been successful with getting Mepis to talk to Windows; however, not with MX.
Anyone feel like providing me a "walkthrough" to get this going?
Thanks,
Jerry in Anchorage
Jerry,
Are you trying to set up a server or simply trying to connect to a Windows shared printer?
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 2:47 pm
by Jerry3904
muskt wrote:I am still not able to get Samba to work on MX-14 B2.
I have it installed on 2 machines and can't figure it out.
I used the meta-installer-more than once-and it tells me it completed successfully.
I went into Synaptic, and downloaded the Help for Samba--There is absolutely no way for me to know where it went--I cannot locate it.
I searched the web, & found numerous "instructions" for installing & configuring Samba--None of these appeared close to MX-14.
I have, in the past, been successful with getting Mepis to talk to Windows; however, not with MX.
Anyone feel like providing me a "walkthrough" to get this going?
Thanks,
Jerry in Anchorage
A full document has been worked out by the Development Team and is coming in the next couple of days. Here are the general guidelines.
Connecting to Samba Shares
If Samba is installed on other computers, MX can connect to shared folders (Samba Shares) on Windows, Mac, Linux computers and NAS (Network Attached Storage) devices. The easiest method is to use the file manager (Thunar) to connect.
- Open the Thunar file manager
- Selecting Browse Network in the left pane will show various networks including Windows Network (address bar shows: network:///)
- Selecting Windows Network will show available Windows Workgroups (often called WORKGROUP by default)
- Selecting a Workgroup will show the available Samba Servers
- Selecting a Server will show the available Samba Shares
- Selecting a Samba Share will show all the available folders and create a shortcut in the Network sidebar section for the Share
Re: GParted locks up? MX-14 beta 2
Posted: Sun Feb 09, 2014 3:04 pm
by BitJam
entropyfoe wrote:Has anyone used GParted from the beta2 live session?
GParted works fine here in VirtualBox.
How much memory does your system have?
You could try killing X-windows and then doing a CLI install from one of the virtual consoles. Kill X-windows (as root) with:
First, I suggest you disable tumblerd but I don't know of a good or easy way to do that. The only two methods I've seen are:
- apt-get remove tumbler, and
- add a cron entry to periodically run "pkill tumblerd"
ISTM there is an outstanding issue of MX-14-beta-2 crashing or locking up on *some* older systems with 512 Meg of memory even though other people have no problem on similar systems. Maybe tumbler is responsible. IOW maybe tumbler is causing OOM errors on some older systems but not all, depending on usage patterns and/or on what files are on the hard drive for tumbler work on.
Even if tumbler is not the culprit, I am very concerned that there is not an easy and well-advertised way to disable it, especially given the history of problems it has caused in past. IMO tumbler should be disabled by default (at least on systems with limited RAM) and we need to have an easier way to turning it off. It is ridiculous that people feel they need to run a cron job that periodically kills off tumblerd.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 3:56 pm
by muskt
All I want to do is be able to share files between computers on my home network.
I have played with Thunar.
If I select the network option. a new window opens that says something like "Network Shares"--I do not remember, cuz I'm in Windows right now. If I click on the "window" option, the whole mess disappears and goes back to the desktop.
I'll reboot into MX & get right back in a couple.
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 4:10 pm
by muskt
I'm in MX now.
OK, Thunar open.
Click "Browse Network"
New Window -- shows what you said Jerry.
Click "Windows Network" -- Boom, back to desktop--even Thunar in Panel or Taskbar is gone.
As I said earlier, I located the Samba .conf file and inserted my Workgroup name there. Spelling was correct.
Although this isn't a really important thing for me, it could be a significant roadblock to others who may desire to adopt MX for their use.
Thanks,
Jerry in Anchoarge
PS--Where should I look to find the Samba Help that I "supposedly" installed from Synaptic?
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 4:12 pm
by richb
Just spent the better part of a week with some other users working on this. Different solutions exist depending on the mix of computers on your network. If Windows in the mix, samba can be used. If all Linux machines NFS can be used. (NFS can also be used with Windows). I am not the expert, but with help got both methods working on a purely Linux network. Since I am not the expert, and still not too confident with the Samba solution, I will leave it to someone else to respond with details. By the way NFS, in my opinion, is the more reliable with Linux networks, and quite easy to set up.
The docs for MX will be updated also with details, eventually.
(If you search for samba and NFS in the MX section you will see the thread on this. But it is easy to get lost in the posts.
EDIT: OK I will try.
You need to setup the shares on the server. As root they are added to the samba.conf file something like this for a folder called Documents.
Code: Select all
[Documents]
path = /home/username/Documents
force user = username
force group = users
read only = No
guest ok = Yes
case sensitive = No
strict locking = No
msdfs proxy = no
Then on the client I was able to access the shares by typing
smb:/ip address of server/home/username/Documents) in the location bar of Thunar. Others were able to access Documents from Network in the Thunar Panel. For some reason I was not.
EDIT 2: It would be better to add to an existing samba thread or create a new one for your samba issues.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 4:30 pm
by loco
mariel77 wrote:Hi, it's great to see all of you working on a new distro. Congrats!
I'm trying it because I need something newer on my desktop.
(I can't get M12 beta to boot; just black screen. I tried all my usual boot codes, but nothing, so here I am.)
I can't login once I install; the login screen just refreshes over and over... ...
hi,
one suggestion that comes to mind would be to ctrl alt f1 or f2 then do your apt-get update and upgrade to find out what is available

. first i've heard of this one, but it sounds like x is crashing. noticed your nvidia and it's probably using nouveau which works pretty well when i use it.
sure. inxi from the live session might give our guys a little added information.

good to see you
Code: Select all
$ inxi -G
Graphics: Card: NVIDIA G84 [Quadro FX 1700]
X.Org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz
GLX Renderer: Gallium 0.4 on NV84 GLX Version: 2.1 Mesa 8.0.5
:blurb: gp works from here, live usb with persistence

also, checked an installed version of xfce4 and tumbl... not installed.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 4:34 pm
by anticapitalista
loco is on the right track - mariel77.
You probably need to install the nvidia driver for your card. When you get dumped out of X, run sgfxi -f as root.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 4:41 pm
by Jon_J
muskt wrote:
PS--Where should I look to find the Samba Help that I "supposedly" installed from Synaptic?
This is an unusual method to find stuff that is installed in most linux's.
Look in /var/cache/apt/archives folder. Here you will find most installed *.deb files. Open the one in question, "samba-help?" or whatever the name of the pkg is. Don't install it, just poke around inside the archive and you'll see the paths to all the files it installed. I would look for something like "samba-help.htm" or "samba-help.pdf"
Once you locate the file you're looking for, then you can locate it in your file system.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 4:49 pm
by richb
Jon_J wrote:muskt wrote:
PS--Where should I look to find the Samba Help that I "supposedly" installed from Synaptic?
This is an unusual method to find stuff that is installed in most linux's.
Look in /var/cache/apt/archives folder. Here you will find most installed *.deb files. Open the one in question, "samba-help?" or whatever the name of the pkg is. Don't install it, just poke around inside the archive and you'll see the paths to all the files it installed. I would look for something like "samba-help.htm" or "samba-help.pdf"
Once you locate the file you're looking for, then you can locate it in your file system.
In konsole
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 5:19 pm
by kmathern
anticapitalista wrote:loco is on the right track - mariel77.
You probably need to install the nvidia driver for your card. When you get dumped out of X, run sgfxi -f as root.
mariel77 can also run the 'Nvidia_Install' installer from the Whiskermenu.
Before she doing that though she'll need to update it following the instructions here:
http://forum.mepiscommunity.org/viewtop ... 38#p328938 because the installer that came with Beta2 doesn't install the correct driver for GeForce 6xxx & 7xxx cards, that's fixed in the updated version.
If you follow the instructions in that link & install the nvidia driver in a MX14 Live session, it will carryover to a harddrive install.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 5:21 pm
by anticapitalista
But mariel77 cannot get into X after installation.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 5:32 pm
by kmathern
anticapitalista wrote:But mariel77 cannot get into X after installation.
Well, what I'm suggesting is installing the nvidia driver in the live session, and then reinstalling beta2 to harddrive.
If she's never managed to get into X, she's not really losing anything (other than some time) reinstalling it to harddrive.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 5:56 pm
by whell
muskt wrote:All I want to do is be able to share files between computers on my home network.
I have played with Thunar.
If I select the network option. a new window opens that says something like "Network Shares"--I do not remember, cuz I'm in Windows right now. If I click on the "window" option, the whole mess disappears and goes back to the desktop.
I'll reboot into MX & get right back in a couple.
Jerry in Anchorage
Can you post your smb.conf file? Its in etc/samba.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 6:00 pm
by richb
whell wrote:muskt wrote:All I want to do is be able to share files between computers on my home network.
I have played with Thunar.
If I select the network option. a new window opens that says something like "Network Shares"--I do not remember, cuz I'm in Windows right now. If I click on the "window" option, the whole mess disappears and goes back to the desktop.
I'll reboot into MX & get right back in a couple.
Jerry in Anchorage
Can you post your smb.conf file? Its in etc/samba.
Muskt post it in another thread please.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 6:04 pm
by mariel77
Well, I posted a reply, but don't see it, so I have no idea where it went.
Thank you loco, anticapitalista, and kmathern! :)
Before I saw kmathern's post, I did sgfxi -f as root and it failed to remove nouveau, and I didn't have a 1600x900 display, so I installed it again, and it seems to be OK.
Code: Select all
inxi -G
Graphics: Card: NVIDIA C61 [GeForce 6100 nForce 405] X.Org: 1.12.4 driver: nvidia Resolution: 1600x900@60.0hz
GLX Renderer: GeForce 6100 nForce 405/integrated/SSE2/3DNOW! GLX Version: 2.1.2 NVIDIA 304.119
Is this the correct driver, or should I reinstall using kmathern's instructions? At this point, I don't mind.
NEW Issue:
Regarding the login. After fixing nvidia, I could only login as root. When I looked in the MX User Assistant, I did not find myself, so I created a new user. I was able to login the next time with the new user. I can't see the user that I created on install, but I couldn't create the same one. Is there some way I can remove that user.
Also when synaptic says I have updates, is it safe to install those? It wants to install the Linux 3.12 kernel and headers from
http://ftp.us.debian.org/pool/main/l/li ... o70+1_i386
Do I turn off the wheezy main repo? And just use antix, wheezy security, and wheezy backports?
Thanks!
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 6:12 pm
by kmathern
mariel77 wrote:Code: Select all
inxi -G
Graphics: Card: NVIDIA C61 [GeForce 6100 nForce 405] X.Org: 1.12.4 driver: nvidia Resolution: 1600x900@60.0hz
GLX Renderer: GeForce 6100 nForce 405/integrated/SSE2/3DNOW! GLX Version: 2.1.2 NVIDIA 304.119
Is this the correct driver, or should I reinstall using kmathern's instructions? At this point, I don't mind.
The 304.xxx driver is correct for your GeForce 6100. It does look like sgfxi installs a slightly newer version, 304.119 vs 304.117 that my script will install from wheezy-backports. Either of them should work.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 6:19 pm
by richb
mariel77 wrote:
Also when synaptic says I have updates, is it safe to install those? It wants to install the Linux 3.12 kernel and headers from
http://ftp.us.debian.org/pool/main/l/li ... o70+1_i386
Do I turn off the wheezy main repo? And just use antix, wheezy security, and wheezy backports?
Thanks!
I went ahead and installed the updates including the kernel update. Rebooted and have no issues. In fact have done a few updates from wheezy main.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 6:21 pm
by mariel77
Thank you, kmathern. Then I'll just keep using this install.
OK, thank you, richb. Then MX-14 is using a Debian kernel?
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 6:22 pm
by kmathern
Wheezy had a point release update yesterday (7.3 -> 7.4) which accounts for most of the updates. I think 3 or 4 updates are MX related updates.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 6:26 pm
by richb
Yes it is based on debian and uses its repositories along with antix repos.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 6:30 pm
by Jerry3904
mariel77 wrote: Then MX-14 is using a Debian kernel?
Kernel is 3.12. Nice to see you again!
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 7:10 pm
by afab4
posting deleted.
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 7:31 pm
by richb
I will answer in the appropriate thread,
Re: MX-14 beta 2
Posted: Sun Feb 09, 2014 7:39 pm
by mariel77
Thank you, Rich and Jerry.
It's nice to see you too, Jerry. :)
Re: GParted locks up? MX-14 beta 2
Posted: Mon Feb 10, 2014 5:11 am
by mangku
BitJam wrote:
IMO tumbler should be disabled by default (at least on systems with limited RAM) and we need to have an easier way to turning it off. It is ridiculous that people feel they need to run a cron job that periodically kills off tumblerd.
What about adding ''killall tumblerd'' to Thunars Custom actions, or as a launcher on the panel.
Re: GParted locks up? MX-14 beta 2
Posted: Mon Feb 10, 2014 5:42 am
by BitJam
mangku wrote:What about adding ''killall tumblerd'' to Thunars Custom actions, or as a launcher on the panel.
IIUC, the problem is that tumblerd keeps respawning so killing all instances just once doesn't do much because it will just respawn. That's why people added a cron job that periodically wakes up and kills all tumblerd processes. IMO, the lack of an easy "off" switch indicates a poor or immature design. Having to make a cron job that keeps running killall tumblerd over and over is a really ugly solution. It is a significant waste of resources and it doesn't fully solve the problem unless killall runs every second or so. Even if tumblerd wasn't so broken, I would still want it to have an easy off switch. Hopefully, such a switch exists but was just not well advertised.
I'm not certain tumbler is responsible for the crashes on systems with 512 Meg of RAM but it is the only hypothesis I've come up with that explains why some 512M systems crash consistently while others work fine. If you do a fresh install with no existing data on a hard drive then tumbler should not be a problem. Likewise if you have plenty of RAM and CPU then even if you have a hard drive with lots of stuff for tumbler to work on, you should be fine. It is just the combination of a small system and a lot of data for tumbler to work on when you get a problem.
Re: MX-14 beta 2
Posted: Mon Feb 10, 2014 6:31 am
by anticapitalista
We have a solution to tumbler in the next version. It won't be included.
What would be an alternative? Anyone know?
Re: MX-14 beta 2
Posted: Mon Feb 10, 2014 6:41 am
by Jerry3904
I seem to remember some discussions on this in the Xfce forum, if someone wants to go over and do a search.
Re: MX-14 beta 2
Posted: Mon Feb 10, 2014 7:41 pm
by lucky9
golinuxgo wrote:lucky9 wrote:golinuxgo wrote:
This time I tried the command line install. I told the installer to put grub on /dev/sda1 (root) not the mbr (there isn't one). It reported completion but when I rebooted there was no grub, just a blank screen with a cursor. Couldn't bring up the console. No keyboard. No nothing. It was just dead. So I popped in the refracta live disk and tried to chroot into mx1 to reinstall grub. I had never tried this before but have read quite a bit. Anyway, this is the resulting message:
There isn't one? No MBR? What do you have?
If you don't install GRUB to the MBR you won't get to the /boot/grub/menu.list which is where the OS will boot from. You didn't use another distro to chainload either. How could you think you could boot the OS?
There has to be a way for /boot/grub/menu.list to be called so it can boot the OS.
Good heavens! I've been using distros with grub2 for the last 3 years at least, probably longer. This distro doesn't??? I can barely remember /boot/grub/menu.list . . .
Sorry for the confusion. I intended to say the boot portion of the root filesystem. My most direct experience is with Legacy GRUB which uses a menu.list. So insert 'boot portion of the root filesystem' to make it easier for you to understand, anywhere there's a menu.list. They all mean the portion of the root file system that actually boots the OS.....instead of the portion of (Legacy or GRUB2) that's resident on the MBR.....or whatever bootloader you choose that rests on the MBR.
In other words, there's little difference in duties performed by either version of GRUB (or any other bootloader). All MS-DOS-based hard disk partitioning schemes will have a part of GRUB (or other) bootloader on the MBR.
If using a GPT partitioned HDD, then there will be a partition set aside as a Boot Partition which will have the (former) MBR code for finding the OS that you want to boot.
Re: MX-14 beta 2
Posted: Mon Feb 10, 2014 10:08 pm
by golinuxgo
lucky9 wrote:Sorry for the confusion.
No problem. I also suffered from confusion all my own. Maybe a senior moment? In either the GUI or CLI install there was mention of Windows in reference to the MBR and my knee-jerk reaction was "there's no stinkin' Winders here!" so I don't need an MBR. On my testing box where I have several versions of Debian installed, I think I have even installed without installing a bootloader and of course the one on sda finds it anyway. Thanks for the excellent explanation, which is now (hopefully) permanently seared into my pea brain. (My approach to computers tends to be more Zen than RTFM.)
Re: MX-14 beta 2
Posted: Mon Feb 10, 2014 11:48 pm
by KBD
Did a fresh install on another netbook tonight of MX. It went well and I ran the updates. Just one odd thing, the icon is messed up for the shutdown/logout action button. I changed the icons then changed it back to tango but it still shows a red X for some reason:
http://imgur.com/SIQSkFV
Not a big issue just an odd one on this new install.
Re: MX-14 beta 2
Posted: Mon Feb 10, 2014 11:55 pm
by muskt
I got that too today on a fresh install. Fresh download, too.
Was not like that this morning prior to the download/install--same machine, same drive, same USB stick--different download.
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Tue Feb 11, 2014 12:05 am
by Stevo
So I see a lot of questions on forums about updating the Flash plugin, since it does not inform the user when there's a new version, and I heard about yet another critical 0-day exploit in Flash, with exploits already in the wild.
I found a post on the Siduction forums about adding a script to /etc/cron.daily to do so:
Code: Select all
#!/bin/sh
test -x /usr/sbin/update-flashplugin-nonfree && /usr/sbin/update-flashplugin-nonfree --install --quiet
which seems like it would do the trick. Laptop users should install anacron if they are going to be off the Net at times.
Would this be a good idea to have as default in MX? I know some old machines without SSE2 will not be able to use the new plugin, but they'll have to be a special case.
There's a Debian bug report about it, but the reason for refusal to add the cron job now does not apply, IMO.
There's also a slightly different version of the cron script:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700092
Re: MX-14 beta 2
Posted: Tue Feb 11, 2014 1:31 am
by BitJam
You could prevent the script from upgrading flash on non-sse2 systems by adding one line:
Code: Select all
#!/bin/sh
grep -q "^flags.*\<sse2\>" /proc/cpuinfo || exit 0
test -x /usr/sbin/update-flashplugin-nonfree && /usr/sbin/update-flashplugin-nonfree --install --quiet
Re: MX-14 beta 2
Posted: Tue Feb 11, 2014 3:25 pm
by lucky9
golinuxgo wrote: (My approach to computers tends to be more Zen than RTFM.)
An excellent way of putting it.
I used to say I used the Gestalt way. Lots of different information and I try and connect the pieces. Occasionally I actually do.
Re: MX-14 beta 2
Posted: Tue Feb 11, 2014 4:03 pm
by uncle mark
lucky9 wrote:golinuxgo wrote: (My approach to computers tends to be more Zen than RTFM.)
An excellent way of putting it.
I used to say I used the Gestalt way. Lots of different information and I try and connect the pieces. Occasionally I actually do.
Mine is "Total Immersion". Immersed in
what is best left to the imagination.
Re: MX-14 beta 2
Posted: Tue Feb 11, 2014 4:22 pm
by arjaybe
uncle mark wrote:lucky9 wrote:golinuxgo wrote: (My approach to computers tends to be more Zen than RTFM.)
An excellent way of putting it.
I used to say I used the Gestalt way. Lots of different information and I try and connect the pieces. Occasionally I actually do.
Mine is "Total Immersion". Immersed in
what is best left to the imagination.
I call my method "blundering." I just keep blundering until something works.-)
Re: MX-14 beta 2
Posted: Tue Feb 11, 2014 5:07 pm
by golinuxgo
arjaybe wrote:I call my method "blundering." I just keep blundering until something works.-)
Yup. Know that one well. Maybe there should be a 'blundering moments' thread just for giggles!
Re: MX-14 beta 2
Posted: Tue Feb 11, 2014 5:14 pm
by Eadwine Rose
golinuxgo wrote:arjaybe wrote:I call my method "blundering." I just keep blundering until something works.-)
Yup. Know that one well. Maybe there should be a 'blundering moments' thread just for giggles!
*cough* 
Re: MX-14 beta 2
Posted: Tue Feb 11, 2014 9:21 pm
by golden45
Where did screensaver go in mx14?
all other xfce systems have it installed when system is installed.john
Re: MX-14 beta 2
Posted: Wed Feb 12, 2014 12:18 am
by Stevo
(presses index fingers against forehead, shuts eyes, affects distant, hollow voice:)
I foresee xscreensavers in the next beta release.
Thank you, next show in 15 minutes, thank you, yes, all donations welcome, thank you, ma'am.
Re: MX-14 beta 2
Posted: Wed Feb 12, 2014 11:07 pm
by golden45
I've tried a lot of xfce systems but this mx14 is the only one that has acer 23" monitor that keeps the 1920x1080 setting.all others after updates change.john
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 3:25 am
by Eadwine Rose
Just wanted to share that I have been running the system now pretty much all the time, and it runs like a charm! Even scanning works, which is normally on my system one of the harder things. The learning curve was more like a speedbump in the road than a curve. Googling helps with a LOT of things.
The only thing I miss is virtualbox (doesn't seem to be fully there?) and a few other minor things, like launch feedback (for those new I'd put this in, noobs like me like to see something happen when they start an application), putting a web hosted image on the desktop that refreshes after a few minutes (picture frame in kde can do that), and have a moonphase screenlet (like kmoon). Tried for a day on the two latter ones to find something that worked but nope.
Just booted the system and there is something in the syslog that appears very time, minor, but I figured I'd put it here:
Code: Select all
Feb 13 08:48:55 eadwinemx14beta2 kernel: [ 72.958310] apt-notifier.py[3380]: segfault at 4 ip b5b5a660 sp bf84aad0 error 4 in libQtCore.so.4.8.2[b5af2000+2dd000]
Also when I print something this happens (the print looks fine though):
Code: Select all
Feb 13 09:18:59 eadwinemx14beta2 hpcups[13171]: prnt/hpcups/Lidil.cpp 586: CupeInteger1 = [1]
Feb 13 09:18:59 eadwinemx14beta2 hpcups[13171]: prnt/hpcups/Lidil.cpp 587: CupeInteger2 = [0]
Feb 13 09:18:59 eadwinemx14beta2 hpcups[13171]: prnt/hpcups/Lidil.cpp 588: PrintMode Index = [4]
Feb 13 09:18:59 eadwinemx14beta2 hpcups[13171]: prnt/hpcups/Lidil.cpp 600: Print Mode = [PlainNormalColor]
Feb 13 09:18:59 eadwinemx14beta2 kernel: [ 1879.487458] usblp0: removed
Feb 13 09:18:59 eadwinemx14beta2 kernel: [ 1879.489319] Did not find alt setting 1 for intf 0, config 1
Feb 13 09:19:29 eadwinemx14beta2 kernel: [ 1909.082914] Did not find alt setting 1 for intf 0, config 1
Feb 13 09:19:31 eadwinemx14beta2 kernel: [ 1911.087498] Did not find alt setting 1 for intf 0, config 1
Feb 13 09:19:33 eadwinemx14beta2 kernel: [ 1913.091198] Did not find alt setting 1 for intf 0, config 1
Feb 13 09:19:35 eadwinemx14beta2 kernel: [ 1915.094855] Did not find alt setting 1 for intf 0, config 1
Feb 13 09:19:37 eadwinemx14beta2 kernel: [ 1917.098494] Did not find alt setting 1 for intf 0, config 1
Should I open a separate thread for the printing and apt notifier?
Anyway, just wanted to share my satisfaction on this new MX14, it is well on its way to becoming my new main system!

Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 4:21 am
by chrispop99
Eadwine Rose wrote:The only thing I miss is virtualbox (doesn't seem to be fully there?)
Did you install from Synaptic? If so, it advises that you must also install virtualbox-dkms or virtualbox-source. In order to have a GUI, you must also install virtualbox-qt.
After that, it appears to run OK, although I haven't tested much.
Perhaps this would be a good candidate for an addition to the meta-package installer?
Chris
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 4:37 am
by Eadwine Rose
I did not install at all. I cannot find the virtualbox-4.2 package (I would like to put my vdi or whatever that thing is called again back) and I have no clue what I need to install
One more issue, which is a little annoying: I use Chrome (not Chromium!) and in M12b2 I could set in window behavior focus stealing prevention on high, so when I click a link in my email program or RSS feed (to read later when done in Akregator) the Chrome browser would not steal focus.
I have set it up in the settings od MX14b2 to turn the stealing focus prevention on, but that is not enough for Chrome to steal focus still.
Any ideas?
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 4:46 am
by chrispop99
Eadwine Rose wrote:I did not install at all. I cannot find the virtualbox-4.2 package (I would like to put my vdi or whatever that thing is called again back) and I have no clue what I need to install

If you search Synaptic for virtualbox, it finds version 4.2.16. The information on the lower part of the screen tells you what else is needed.
Since my last post, I have installed a virtual XP, and all works as expected.
Chris
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 4:56 am
by chrispop99
Eadwine Rose wrote:minor things, like launch feedback (for those new I'd put this in, noobs like me like to see something happen when they start an application), putting a web hosted image on the desktop that refreshes after a few minutes (picture frame in kde can do that), and have a moonphase screenlet (like kmoon). Tried for a day on the two latter ones to find something that worked but nope.
As far as I know, launch feedback is not available with Xfce. It's one of the omissions that keeps it lean.
A picture frame, and a moon phase display would both be possible using Conky; it's not a point-and-click type of application however! I'm sure in time someone here would be able to help with this - I don't have an intimate knowledge of the program sadly.
Eadwine Rose wrote:Anyway, just wanted to share my satisfaction on this new MX14, it is well on its way to becoming my new main system!

Remember MX-14 is in its very early stages - second Beta of something completely new to Mepis/antiX - so I'm sure there will be a lot more good things coming!
Chris
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 5:29 am
by BitJam
Eadwine Rose wrote:[...] and have a moonphase screenlet (like kmoon). Tried for a day on the two latter ones to find something that worked but nope.
I am not familiar with kmoon but I use the gkrellm moon clock. You can installed it via the gkrellmoon package.
GKrellM is a system monitor like Conky. Perhaps it is showing its age but it is usually one of the very first apps I install because without it it feels like I'm flying blind. If you don't want all of the monitors, you can disable everything and just enable the moon clock. I use a transparent theme (Pseudo transparency) which makes it look like the moon is just floating on your desktop (if everything else is disabled).
It has plenty of other tricks. I've attached a small tarball that contains 3 slightly different invisible themes. I have almost 200 themes installed but I much prefer the invisible themes because they work well with almost any bg image.
Here is a screen shot of it next to the default panel with everything turned off except the moon clock. AFAIK, the size of the moon clock is not adjustable.
moonclock2.jpg
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:05 am
by Eadwine Rose
GKrellM: looking good that moon! Thanks for the screenshot. Definitely need to look into that one. Can it run next to conky without issues? I have just finished configuring that, so.. heh. Hate to lose it.
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:12 am
by kmathern
Eadwine Rose wrote:Just booted the system and there is something in the syslog that appears very time, minor, but I figured I'd put it here:
Code: Select all
Feb 13 08:48:55 eadwinemx14beta2 kernel: [ 72.958310] apt-notifier.py[3380]: segfault at 4 ip b5b5a660 sp bf84aad0 error 4 in libQtCore.so.4.8.2[b5af2000+2dd000]
Should I open a separate thread for the printing and apt notifier?
I've also seen the apt-notifier segfaults listed in syslog with Mepis 11 & 12. I'm not sure what causes it, the notifier seems to work okay in spite of the segfault.
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:14 am
by Eadwine Rose
Yep me too. Ah well. It is not flooding the system or anything *shrug*

Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:23 am
by BitJam
Eadwine Rose wrote:GKrellM: looking good that moon! Thanks for the screenshot. Definitely need to look into that one. Can it run next to conky without issues? I have just finished configuring that, so.. heh. Hate to lose it.
Yes. I use both. No problem. The nice thing about GKrellM is that there is no config file to edit; it is all done via a GUI. OTOH, it is not nearly as flexible as Conky. OTOOH, I think GKrellM looks better OOTB.
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:50 am
by Eadwine Rose
Where did you get the moonthingie? Still need to install it, just wondering how to go about this
Edit: never mind.. moon clock, it is in synaptic.
me <---- READ already

Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 8:08 am
by Eadwine Rose
It works, thanks! One thing I would like to know is how to increase the size, not just the width, but the size of the moon basically, do you know how to do that?
edit: asked via PM, avoids clutter
*continues fiddling, happy with the new system*

Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 11:04 am
by golinuxgo
BitJam wrote:GKrellM is a system monitor like Conky. Perhaps it is showing its age but it is usually one of the very first apps I install because without it it feels like I'm flying blind.
It has plenty of other tricks. I've attached a small tarball that contains 3 slightly different invisible themes. I have almost 200 themes installed but I much prefer the invisible themes because they work well with almost any bg image.
I also find gkrellm useful. Not for the moonphase but for the reminder plugin. Events can be set for every x number of days (not just weekly, monthly etc), plays music as a reminder (in addition to a popup) and you can reset the reminder for x hours later on the fly to keep reminding you until it gets done. It's a very pleasant nag. Thanks for the transparent themes.
*edit* The transparent themes you posted are not transparent here (on refracta xfce). Are they transparent only for the moonclock?
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 11:10 am
by Eadwine Rose
Just discovered.. Menu-multimedia-codecs.

Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 11:42 am
by arjaybe
golinuxgo wrote:BitJam wrote:GKrellM is a system monitor like Conky. Perhaps it is showing its age but it is usually one of the very first apps I install because without it it feels like I'm flying blind.
It has plenty of other tricks. I've attached a small tarball that contains 3 slightly different invisible themes. I have almost 200 themes installed but I much prefer the invisible themes because they work well with almost any bg image.
I also find gkrellm useful. Not for the moonphase but for the reminder plugin. Events can be set for every x number of days (not just weekly, monthly etc), plays music as a reminder (in addition to a popup) and you can reset the reminder for x hours later on the fly to keep reminding you until it gets done. It's a very pleasant nag. Thanks for the transparent themes.
*edit* The transparent themes you posted are not transparent here. Are they transparent only for the moonclock?
The transparent themes don't work in KDE. I wish they did. GkrellM is one of the first things I install in a new system, so I'm glad to hear that the transparency works in MX-14.
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 11:59 am
by richb
arjaybe wrote:
The transparent themes don't work in KDE. I wish they did. GkrellM is one of the first things I install in a new system, so I'm glad to hear that the transparency works in MX-14.
Because of that it looks out of place in KDE. The native widgets look much better. I will have to try it in MX.
EDIT: Yes looks much better in MX with transparency.
Re:GParted in MX-14 beta 2 wouldn't load
Posted: Thu Feb 13, 2014 1:06 pm
by entropyfoe
OK, a bit more research on partitioning my old PATA drive.
I booted Puppy Live CD (old 5.4.3 I think) and I was able to run GParted. I made a traditional ext3, swap, ext3 partition scheme for /, swap and /home.
Not sure why GParted locked with MX-14. But now I have a correctly partitioned disk, and I will try an install or MX-14 on that drive. Will report later.
-Jay
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Earlier post
The beta2 booted into a live session (beta 1 did not) on my old A7N8X mother board.
OK, so I found an old PATA drive in the parts bin and installed it so I could install MX-14.
This old machine has a working XP installation on a SATA drive that I have disconnected the power on so it is undisturbed.
From the live session, I can see the new PATA drive and access the files. But I cannot launch GParted to repartition the drive.
I supply root credentials an d everything locks up, no mouse cursor nothing works until I Ctrl Shift SysRq REISUB.
So, then I tried to install, thinking I could partition as part of the install, but when I get to the part to modify partitions, same lock up.
Any ideas what to try?
Has anyone used GParted from the beta2 live session?
-Jay
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 4:36 pm
by BitJam
golinuxgo wrote:*edit* The transparent themes you posted are not transparent here (on refracta xfce). Are they transparent only for the moonclock?
The transparency is for the entire gkrellm, but only if you don't use a compositor.
IIUC there is a general conflict between psuedo transparency and compositing. Some years ago there was also a conflict between tearing video and compositing (at least with Nvidia drivers) so I choose to go with an non-compositing desktop since non-tearing video playback was high on my priority list while wobbly windows, not so much.
If you are using a compositor then true transparency should be available, where you can see other windows behind a transparent window. TBH, I think I like visual effect of pseudo-transparency better, otherwise the bg in the transparent window gets too noisy. For example, I tend to use only dark bg images but many windows have light backgrounds.
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:01 pm
by golinuxgo
BitJam wrote:golinuxgo wrote:*edit* The transparent themes you posted are not transparent here (on refracta xfce). Are they transparent only for the moonclock?
The transparency is for the entire gkrellm, but only if you don't use a compositor.
IIUC there is a general conflict between psuedo transparency and compositing. Some years ago there was also a conflict between tearing video and compositing (at least with Nvidia drivers) so I choose to go with an non-compositing desktop since non-tearing video playback was high on my priority list while wobbly windows, not so much.
If you are using a compositor then true transparency should be available, where you can see other windows behind a transparent window. TBH, I think I like visual effect of pseudo-transparency better, otherwise the bg in the transparent window gets too noisy. For example, I tend to use only dark bg images but many windows have light backgrounds.
Ah! That explains it. Once I got the nvidia driver working, I enabled XFCE's simple compositor because I like transparency when I move windows. I'll look at your themes and try to tweak them a bit - I'm usually pretty good at that kind of thing. (Unless you take it on first!) :D
*Edit* OK I just disabled XFCE compositing and the transparency still didn't display. :( It would have been a nice option . . .
(That's the way life is.)
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:31 pm
by BitJam
golinuxgo wrote:Ah! That explains it. Once I got the nvidia driver working, I enabled XFCE's simple compositor because I like transparency when I move windows. I'll look at your themes and try to tweak them a bit - I'm usually pretty good at that kind of thing. (Unless you take it on first!) :D
I don't think tweaking the themes will help with transparency when a compositor is being used.
This page:
http://www.muhri.net/gkrellm/ has a link to a tarball with almost 200 themes in it. If you want to go non-transparent then their tarball contains a bunch of good starting points.
AFAIK, you need to give up pseudo-transparency when you use a compositor. You can't just tweak the pseudo-transparent apps. I'd love for you to prove me wrong.
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:42 pm
by Eadwine Rose
Just a big thankyou to the person who got Lbreakout2 to be in the games. Just discovered it was there

Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 6:56 pm
by Jerry3904
me, me, me
Did you try Chromium BSU?
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 7:10 pm
by anticapitalista
But you nicked it from antiX :) We have had it for several releases.
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 7:21 pm
by Jerry3904
did not, did not, had it forever...
Re: MX-14 beta 2
Posted: Thu Feb 13, 2014 7:41 pm
by golinuxgo
BitJam wrote:This page:
http://www.muhri.net/gkrellm/ has a link to a tarball with almost 200 themes in it. If you want to go non-transparent then their tarball contains a bunch of good starting points.
I am familiar with that site. Have downloaded a few themes that suited me but not the whole tarball.
BitJam wrote:AFAIK, you need to give up pseudo-transparency when you use a compositor. You can't just tweak the pseudo-transparent apps. I'd love for you to prove me wrong.
I'm just about caught up on a never-ending video project so may have some time to explore gkrellm themes soon.
Re: MX-14 beta 2
Posted: Fri Feb 14, 2014 3:55 am
by Eadwine Rose
Jerry3904 wrote:me, me, me
Did you try Chromium BSU?
WOOT!
Did just now!

Re: MX-14 beta 2
Posted: Fri Feb 14, 2014 5:57 am
by malspa
Eadwine Rose wrote:Just a big thankyou to the person who got Lbreakout2 to be in the games. Just discovered it was there

Jerry3904 wrote:me, me, me
Did you try Chromium BSU?
I haven't touched any kind of computer game in years, and I don't mind at all if a distro doesn't include any games by default. That being said, LBreakout2 was one I did play! And, I probably would have liked Chromium BSU, too, even though the only reason I've known of its existence was because of having confused it with the Chromium web browser.

Re: MX-14 beta 2
Posted: Fri Feb 14, 2014 12:09 pm
by golinuxgo
Just discovered that the transparent skins work on my squeeze/gnome/compiz setup but not on wheezy/xfce. I'm guessing GeForce 8400 GS vs GEForce MX 4000 might be the difference? Here it is working on squeeze - Desktop and with browser open:
Hope I'll eventually be able to getting it working on xfce (using a different wallpaper though).
Re: MX-14 beta 2
Posted: Sat Feb 15, 2014 4:22 pm
by BitJam
Sometimes XFCE is very slow to start on LiveCD in VirtualBox
Normally with beta-2, XFCE takes about 15 seconds to start but sometimes it can take minutes. During the longer delay I get a black bg and a white bar where the panel will be. There is a flickering rectangle of about 10 x 10 or 20 x 20 pixels near the bottom of the white bar at the border with the black bg, perhaps near where the volumeicon is supposed to appear.
This time when it happened, I thought to switch to a vt and run htop. I saw there was 100% cpu utilization. The nm-applet (network manager) program was using most of it, followed by volumeicon. It broke out of whatever loop it was stuck in when I switched back to vt-7. Then XFCE completed its startup and cpu usage went down to near zero.
I'd guess this happens on about 10% of my boots, maybe less. It has happened at least 3 or 4 times.
Re: MX-14 beta 2
Posted: Sat Feb 15, 2014 7:41 pm
by muskt
What is the latest rumor concerning B3?
Anyone care to start one??
I still cannot get Samba to function--even partially.
Jerry in Anchorage
Re: MX-14 beta 2
Posted: Sat Feb 15, 2014 7:45 pm
by uncle mark
muskt wrote:What is the latest rumor concerning B3?
I heard it has been specifically coded to mess with Alaskan pilots.
Re: MX-14 beta 2
Posted: Sat Feb 15, 2014 11:36 pm
by Stevo
It is not only virus-resistant, it actually seeks them out and kills them!
http://www.rumormillnews.com/cgi-bin/ar ... ead=189740
Re: MX-14 beta 2
Posted: Sun Feb 16, 2014 2:14 am
by Eadwine Rose
I am ready for b3, all done and set up with b2 now where my demands are concerned, just some minor issues.

Just one big thing to sort out for me, but hopefully b3 will fix that.
Mind.. how do I find out the xfce version on this system? I have googled but xfce4-about won't work and the package cannot be found in synaptic.
Re: MX-14 beta 2
Posted: Sun Feb 16, 2014 5:08 am
by chrispop99
Eadwine Rose wrote:
Mind.. how do I find out the xfce version on this system? I have googled but xfce4-about won't work and the package cannot be found in synaptic.
The package you need to install is:
It's a bit of an over-kill; it shows a pane with lots of other information on it.
Chris
Re: MX-14 beta 2
Posted: Sun Feb 16, 2014 5:40 am
by BitJam
Eadwine Rose wrote:Mind.. how do I find out the xfce version on this system? I have googled but xfce4-about won't work and the package cannot be found in synaptic.
From a terminal, run:
Re: MX-14 beta 2
Posted: Sun Feb 16, 2014 5:57 am
by Eadwine Rose
That works! Thanks :D
Love how it gives me two version numbers for them hehe
Code: Select all
$ xfwm4 -V
This is xfwm4 version 4.10.1 (revision 3918e6b) for Xfce 4.10
Released under the terms of the GNU General Public License.
Compiled against GTK+-2.24.10, using GTK+-2.24.10.
Build configuration and supported features:
- Startup notification support: Yes
- XSync support: Yes
- Render support: Yes
- Xrandr support: Yes
- Embedded compositor: Yes
- KDE systray proxy (deprecated): No
$ xfdesktop -V
This is xfdesktop version 4.10.2, running on Xfce 4.10.
Built with GTK+ 2.24.10, linked with GTK+ 2.24.10.
Build options:
Desktop Menu: enabled
Desktop Icons: enabled
Desktop File Icons: enabled
Is 4.10.1 the base and the desktop version what runs on it?
Just trying to graps what is what
Also.. we are not running Xfce on this thing then?
Honestly, I am suddenly thoroughly confused about the namings

Oh wait we are.. Xfce 4.10 is the Xfce version
xfwm4...
Oh man can someone just give me the explanation for all these namings so even the stupid (read: me) can grasp it?
Re: MX-14 beta 2
Posted: Sun Feb 16, 2014 7:09 am
by BitJam
xfwm4
The Xfce 4 Window Manager is part of the Xfce Desktop Environment. The actual command to run is xfwm4. To run it in the background use xfwm4 –daemon. The window manager is responsible for the placement of windows on the screen, provides the window decorations and allows you for instance to move, resize or close them.
xfdesktop
The xfdesktop application manages the desktop backdrop. It sets a backdrop image and/or color and it can pop up an applications menu and a list of all running applications when you click on the desktop with the right or middle mouse button respectively. As of Xfce 4.4, xfdesktop also draws icons on the desktop.
So they are both components of the XFCE Desktop Environment. Here is a
List of the Core Components.
Re: MX-14 beta 2
Posted: Wed Feb 26, 2014 11:58 pm
by golden45
Just enabled testing repos and upgraded mx14.I then installed kde 4.8 using meta package installer and upgraded to kde 4.11 .Then installed lxde using meta package installer .I'm switching between the three systems with no problems
I'm seeing all systems running together with each system.Seems like they all are all compitable using testing repos.I logout and login selecting which system I want to run logout- login with no problems.Adding upgraded packages using synaptic with each system .
Re: MX-14 beta 2
Posted: Fri Feb 28, 2014 3:59 pm
by golden45
Used synaptic to upgrade kde 4.11-5 while using mx-14.You can also use it to install updates.Apt notification is on the bar of mx-14 and reads updates of packages of the three systems.Still running the three of them.Lcde with kde games installed you have to use other in menu to get them all to work-some of them work by just using menu,Its mind blowing what you can do.
Re: MX-14 beta 2
Posted: Fri Feb 28, 2014 7:01 pm
by jsalpha2
I made a live USB from within Win 7 using Rufus. Everything is working, including Flash on YouTube.
My question is in the boot options I have three choices for persistence; root, static, and home.
I read this thread, but I'm still confused.
http://forum.mepiscommunity.org/viewtop ... 1&start=30
I'm using a 16GB Sandisk flash drive. I think I should start at step 6.
6. At usb boot menu screen choose root persistence
7. You will be prompted for a new root and user password
8. In desktop, use the meta-installer(Synaptic?) to install a couple of apps eg Clementine, minitube (nothing too big)
9. DO NOT REBOT FROM THE MENU. For changes to save on next boot, you MUST run the Remastercc application -> Save root persistence.
10. Once that has finished, reboot as usual and again choose root persistence in the menu.
11. You should now have the apps you installed in 8 in the menu.
I plan to use the live USB for a while and then try an install on an old Thinkpad. Wish me lck.
Re: MX-14 beta 2
Posted: Sat Mar 01, 2014 8:34 am
by dolphin_oracle
have you made a persistence file. they are not set up by default. use remastercc in the menu to set up a persistence file on your liveusb. Then you can select one of the persistence options at boot and install any app you like.
I generally set up root persistence. this will keep all the apps you install and information in your home folder.
static is good if you don't have a lot of ram...it wills save all changes as you make them.
the other pesistence option will save all changes into ram and then save to the persistence file either on demand or at logout.
with either option, you can use remastercc to incorporate any changes into the usb filesystem, lessening the demands on you ram.
check out the help (the big question mark on the toolbar). there is a persistence section.
Re: MX-14 beta 2
Posted: Sat Mar 01, 2014 8:56 am
by Jerry3904
check out the help (the big question mark on the toolbar). there is a persistence section.
+1
Re: MX-14 beta 2
Posted: Sat Mar 01, 2014 1:17 pm
by jsalpha2
I've read the persistence section in the help (big question mark on the toolbar). I've read the thread I already mentioned. I've googled until I'm blue in the face.
The original problem was Rufus marking the USB as read only. I've reformatted and used Unetbootin about 6 times. After using remastercc to create a persistence file
and then trying to re-start the computer, it asks me to log back in, won't accept any password, then crashes, when the computer restarts the USB is no longer recognized. Re-format and repeat,
same outcome.
Re: MX-14 beta 2
Posted: Sat Mar 01, 2014 1:41 pm
by KBD
On a 16 gig stick I would do a full install of MX. I've done it many times. Just format a couple gigs of swap, the rest ext4 partition. Point the installer at it, be careful with grub so you don't overwrite whatever is on your hard drive. With Debian I make it easy on myself and uplug the hard drive of the computer I'm using and it treats the usb stick like the hard drive. With the Buntus the installer is easier and I don't unplug the hard drives. 16 gigs is about the smallest usb stick I'd try it with, but I know it works well, at least it does with Sandisk usb sticks of that size.
Re: MX-14 beta 2
Posted: Sat Mar 01, 2014 1:49 pm
by KBD
Just noticed MX is refusing to save my preferred browser. Every time I try to open an email it asks again for preferred application. Strange because I have LXDE installed on top of MX and it doesn't do that with LXDE.
Re: MX-14 beta 2
Posted: Sat Mar 01, 2014 2:49 pm
by BitJam
jsalpha2 wrote:I've read the persistence section in the help (big question mark on the toolbar). I've read the thread I already mentioned. I've googled until I'm blue in the face. The original problem was Rufus marking the USB as read only.
This makes sense. The same problem exists if you create a LiveUSB with the Linux (Unix) "dd" command. We can't write to read-only devices.
I've reformatted and used Unetbootin about 6 times.
Ouch!
After using remastercc to create a persistence file and then trying to re-start the computer, it asks me to log back in, won't accept any password, then crashes, when the computer restarts the USB is no longer recognized.
This sounds very strange.
Can you reboot the LiveUSB when you don't create persistences files?
Can you reboot the LiveUSB after you create persistence files but continue to boot with persistence *disabled*?
The first time you boot with root persistence enabled, you will be asked, during the boot process, to *change* the root password and the password for the demo user. It won't let you keep the current passwords. This is for a modicum of security. It is very hard to infect a LiveCD or a LiveUSB on read-only media. That's why we allow the convenience of well publicized passwords on the LiveCD. But once root persistence is enabled, the live system becomes as vulnerable to infection as an installed system. It would have been unconscionable for us to allow live systems with persistent root to boot with the default passwords.
Re: MX-14 beta 2
Posted: Sat Mar 01, 2014 2:58 pm
by Jerry3904
Just noticed MX is refusing to save my preferred browser. Every time I try to open an email it asks again for preferred application.
Do I understand that you are setting the preferred browser and then wondering why MX-14 asks you about email? If yes, why don't you try seting the preferred
email client and see what happens?
Re: MX-14 beta 2
Posted: Sat Mar 01, 2014 3:08 pm
by KBD
Jerry3904 wrote:Just noticed MX is refusing to save my preferred browser. Every time I try to open an email it asks again for preferred application.
Do I understand that you are setting the preferred browser and then wondering why MX-14 asks you about email? If yes, why don't you try seting the preferred
email client and see what happens?
I thought I had Thunderbird set as preferred email, but evidently didn't. Now Chrome is launching when I click on the links.
Thanks!
Re: MX-14 beta 2
Posted: Mon Mar 03, 2014 5:49 am
by jdmeaux1952
After a couple of days of busy, I came back to MX-14 to be told there were 1139 UPDATES.
Problem: I Right-click anywhere on the desktop, and I get (what used to be the menu) a series of blocks -- no characters or unprintable characters. I rebooted to see if that would correct it, but no dice. Any right-click on the desktop results with "block characters".
Re: MX-14 beta 2
Posted: Mon Mar 03, 2014 5:56 am
by chrispop99
jdmeaux1952 wrote:After a couple of days of busy, I came back to MX-14 to be told there were 1139 UPDATES.
Problem: I Right-click anywhere on the desktop, and I get (what used to be the menu) a series of blocks -- no characters or unprintable characters. I rebooted to see if that would correct it, but no dice. Any right-click on the desktop results with "block characters".
Have you by any chance changed the default repositories?
Chris
Re: MX-14 beta 2
Posted: Mon Mar 03, 2014 9:19 am
by jsalpha2
BitJam, Thanks
Can you reboot the LiveUSB when you don't create persistence files? Yes, Of course nothing is saved.
Can you reboot the LiveUSB after you create persistence files but continue to boot with persistence *disabled*?
I tried one more time and created a 2GB persistence file. Then I tried to reboot. When it asked me to log back in I just did not touch anything,but waited about 5 minutes. It may not actually try to create the persistence file until this time and may need to take some time. I believe the persistence file was created,but not set up. It finally re-booted, but I could only log back in without persistence. Tried remastercc again, this time tryingOption 2 Save root persistence. Error, the file/live/config/.conf was not found. Tried Option3 AntiX Live Remaster Do you want to save files under /home in the new remaster - yes Ready to create a new linuxfs file. Shall we begin -, yes Remaster Type Personal, OK Enter an optional title, Test
"Error Remastering Terminated Early" Do you want to save the incomplete file?
I've decided I don't really need to have persistence on my pendrive. It would be much easier just to do a real install.
KBD Thanks, I have heard of trying it your way, either by burning a CD or using two pendrives.
Jerry3904 Your post was not helpful at all. I read the help section, searched the forum and google searched before making my first post here. You did not make me feel welcome.
Re: MX-14 beta 2
Posted: Mon Mar 03, 2014 9:27 am
by Jerry3904
Jerry3904 Your post was not helpful at all. I read the help section, searched the forum and google searched before making my first post here. You did not make me feel welcome.
Sorry--did not know you knew that document existed.
Re: MX-14 beta 2
Posted: Mon Mar 03, 2014 1:42 pm
by BitJam
jsalpha2 wrote:[...] Then I tried to reboot. When it asked me to log back in I just did not touch anything,but waited about 5 minutes.
Ah. Maybe the problem is that your system is not rebooting when you tell it to and instead is just logging you out of X-windows. This will happen if you have any invalid characters in your hostname.
This post contains a link to instructions on how to change your hostname. I think those instructions are not very good because they tell you to edit the /etc/hostname file directly. It is much better to use the "hostname" command because it will check for invalid characters. The only valid characters are letters, digits, the hyphen "-", and the period "." but the hostname cannot start or end with a hyphen or period and (I think) cannot start with a digit.
You can tell if the computer is rebooting because it will switch you to a text screen with scrolling text as the system shuts down and then the screen will go blank, then you will see the Power-On-Self-Test as the machine restarts and then you will get to the bootloader menu that has F1 through F7 menus at the bottom and includes the choices for "Root Persistence", "Static Root Persistence", and so on in the main menu. I've attached a screenshot of what the bootloader menu looks like.
Re: MX-14 beta 2
Posted: Tue Mar 04, 2014 5:52 pm
by jdmeaux1952
chrispop99 wrote:jdmeaux1952 wrote:After a couple of days of busy, I came back to MX-14 to be told there were 1139 UPDATES.
Problem: I Right-click anywhere on the desktop, and I get (what used to be the menu) a series of blocks -- no characters or unprintable characters. I rebooted to see if that would correct it, but no dice. Any right-click on the desktop results with "block characters".
Have you by any chance changed the default repositories?
Chris
Today I turn on MX-14, and find 15 updates. After the updates finish, the problem with the Right-click menu having "block characters" as disappeared. It seems to be back to normal. But after a reboot, my auto login doesn't work. ?? I'm puzzled.
And NO, I have not changed any settings. Just a boot in, updates, a reboot, and then forced to manually login.
Re: MX-14 beta 2
Posted: Tue Mar 04, 2014 6:35 pm
by KBD
Just curious, what is:
connectshares-antix ?
saw that in today's updates.
Thanks.
Re: MX-14 beta 2
Posted: Tue Mar 04, 2014 6:39 pm
by dolphin_oracle
its a samba and nfs mount automation script. I don't think it will be in the release candidate by default, but it will be available in the repos. I've got some vids up on my channel (they are a little out of date, but you get the idea). I find it very handy in antix.
Re: MX-14 beta 2
Posted: Tue Mar 04, 2014 6:44 pm
by KBD
Thanks Dolphin!
Re: MX-14 beta 2
Posted: Tue Mar 04, 2014 8:29 pm
by BitJam
D.O. rocks!
Re: MX-14 beta 2
Posted: Thu Dec 04, 2014 11:18 pm
by golden45
mx system -just changed all repositories to jessle did a complete update and still running after update posting this.Everything seems to still run that i have installed.I did this in terminal and had to run dpkg --configure -a several times and apt-get -f install but everything seems to still run. I would not suggest trying this but I like experimenting and trying different things.
Re: MX-14 beta 2
Posted: Fri Dec 05, 2014 5:37 am
by Jerry3904
It would be much better if you would repost this in its own thread, maybe with a generic title such as "Upgrading to Jesse." This thread has been dead for 6 months, and your post starts a new idea.
TIA