MX-14 beta 2

[Jon_J]

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.

[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.

[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!

[Adrian]

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.

[Jon_J]

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

[Adrian]

You can edit the first post and add the content from the second and a mod can probably delete the duplicated post.

[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.

[Jon_J]

@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

[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?

[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