白い熊 | # 21 | 2010-03-22, 08:51 | Report

You said you already reflashed right? If so, you have a clean system, since kumatux.org doesn't install anything into the system and doesn't touch the underlying rootfs, so unless you did something weird on the side, it shouldn't make a difference.

Don't understand why it would segfault.

Are you running it as user, i.e. not as root?

Where did you extract the apps to, which directory?

Just to see, try kumatux.org-unlink xbindkeys and all the apps, as root:
then as user extract all there and kumatux.org-link them. Then export the ~/.profile via as user. No need to reboot. And see if xbindkeys runs now.

bpe | # 22 | 2010-03-22, 09:44 | Report

Running it as "user"

I first had them installed at /home/user/

moved them to /media/0/kumatux.org-apps and it now works but when I press shift + enter, it does not make the application full screen, the prompt turns white when pressed though and in some apps the key area of the window does light up but does not go full screen. let me test some more.

When I type vi ~/.xbindkeysrc

This in the contents.

"wmctrl -r :ACTIVE: -b toggle,fullscreen"
shift + KP_Enter

I also have your wmctrl from applications installed !

---

Last edited by bpe; 2010-03-22 at 10:11.

白い熊 | # 23 | 2010-03-22, 21:04 | Report

Did you run xbindkeys from the terminal, before attempting to Shift+Enter maximize an app?

What happens when you execute the following in the terminal?

ToJa92 | # 24 | 2010-03-22, 21:12 | Report

Thank you, just one question, should I remove everything and do it again? What would happen if I right now removed all files and reboot, would something break? I was thinking of reflashing anyway, but I want to try it out first.

ivnvir | # 25 | 2010-03-22, 21:32 | Report

why not pack all this stuff in deb (imagemagick and everything)?

why everyone has to suffer instead of just one suffering making a deb?

or am I missing something?

It s*cks to use the terminal and copy 1000 files...

白い熊 | # 26 | 2010-03-22, 22:14 | Report

Don't do this. That's why I designed kumatux.org so that if something is wrong, you didn't mess with the underlying system, you didn't change any files, so you don't have to reinstall anything and reflash etc.

If you installed it as user, then run kumatux.org-link as user. If you want to use it as root, use as root.

If you want to completely remove it for any user, if you ran kumatux.org setup as a regular user it created /home/user/kumatux.org-root and /home/user/kumatux.org-links which are just directories of symlinks which get exported on login from the /home/user/.profile file. So to completely remove it, just delete these two directories and delete these lines from the end of your /home/user/.profile
Now when you relogin/reboot you have a clean system, just like you started with.

白い熊 | # 27 | 2010-03-22, 22:19 | Report

Yeah, you're missing something man: that's exactly what kumatux.org was designed for, so that you wouldn't install stuff from debs pulling all the dependencies in, potentially messing up your system, removing system parts etc. That's what happens actually in the N900 if you install some sdk, devel stuff etc.

This way, you just extract the compiled package anywhere on your system, you can put it in /media/trash or whatever, and just run kumatux.org-link and can use it.

Sure, you need to take care of the dependencies, like this xbindkeys stuff, but if something goes wrong you don't have a bricked system, you don't need no reflashes, you are guaranteed all system files are untouched and can easily go back via just kumatux.org-unlink

And most stuff I compiled has no dependency hell, this xbindkeys stuff is by far the worst...

Guess, it depends on what you consider suffering. I'm not a beginner in GNU/Linux I'd think, but I had to reflash this damn Nokia more than a hundred times, when I was compiling stuff, installing it into the system, or pulling in SDK dependencies etc. So came up with this super-clean solution, even enabling users without root access to use any app anywhere.

Think it's quite potent, just requires so CLI work, but I think it's well worth it.

bpe | # 28 | 2010-03-23, 00:16 | Report

When I run wmctrl -r :ACTIVE: -b toggle,fullscreen into terminal nothing happens.

I was meant to use wmctrl from your applications right?

zoner | # 29 | 2010-03-23, 03:29 | Report

well, I've read this thread 30 times, before I screw something up, someone please tell me what I'm doing wrong.

1-copied kumatux.org to /home/user/
2-copied 3 files from n900 tools directory to /home/user/kuma..org/bin
3-in /home/user/ directory, run

~ $ kumatux.org/bin/bash kumatux.org/kumatux.org-setup.sh

I get
-sh: kumatux.org/bin/bash: Permission denied

I know I can run as user, but it sure looks like it wants root.

I moved kumatux all over the place, tried running the bash from the bin directory, no go for me. I've tried with & without the tilde's like the source instructions. help? chmod? chown?

白い熊 | # 30 | 2010-03-23, 03:32 | Report

I find that hard to believe, you should be getting some response, either it should fullscreen the window, or you should get some feedback.

What is the response to: and