sigbart (?) error

[back2future]

Greeting
kde desktop so there is a sub menu appears with a warning SIGABRT (?) error, when I choose" backtrack"
no explanation.
is this a bug of kde or porteus?
This problem porteus version 1.2 rc2
sorry for google translate english
(I extract with winrar to a usb from my friend's computer)

[wread]

SIGABRT is a short for "signal abort". This is a crash, probably. You should check your installation. That's all.

Regards!

[brokenman]

Traceback was disabled in TDE. Can you please let me know the menu item?

There was one item in the control panel that aborted due to module buginess upstream, but i wrote a workaround for Porteus using a kcmshell call in the desktop file.

[back2future]

Thank you both

@brokenman sorry it's been years have use remix/porteus forgot most of the technical jargon.
i hope this help

here it pastebin of dmesg
http://pastebin.com/jd2K55Tm

Ps info
http://pastebin.com/Eyaawjxz

strangely only 1 of 2 usb readable, but the snapshot does have 2 usb attached to the computer.

what site i can upload image ?
iam download rc2 again just incase classic fat32 error ( but fsck say ok )
thanks again

[Hamza]

Hello

First, Slax Remix is different than Porteus.

Please upload a screenshot to mediafire

Did you checked the md5sum ?

[back2future]

@hamza
you are right ....

I've tried chkbase.sh
the result ....
porteus root @: ~ # / mnt/sdb1/XRemix/XI/base
bash: / mnt/sdb1/XRemix/XI/base: is a directory
porteus root @: ~ #

Have I made ​​a typo?

[brokenman]

kde desktop so there is a sub menu appears with a warning SIGABRT

Can you please let me know the menu item?

[back2future]

@ brokenman

i hope this is what you ask for

http://img801.imageshack.us/img801/5331/config12.png
ie
kmenu
under all Apps
setting/configure the panel

If i mislead you (on my first post ) this is how i got the error

setting......
initial system service.....
peripherals.....
As soon as "loading desktop...." thats where the error appear at the background.

This error appears when booting sda1 even boot a few times ( sda1 is fat 32 )

When booting sdb1 the error doesn't shows up ( sdb1 ext2 )

sorry if i confuse you

[brokenman]

Yes this is what i need. I will test on FAT partition today. I can't reproduce this on ext partition either. A little strange but is looking like a potential bug.