Re: Running Debian in a chroot
 

It's me again,

I've got some other problems, so if you chroot debian pros could help me it would be a very nice. :)

my first problem concerns hal and apt-get. I installed a lot of packages and now each time I use apt-get it is written: (sorry it's in french)

paramétrage de hal (0.5.11-2) ...
dpkg : erreur de traitement de hal (--configure) :
le sous processus post-installation script a retourné une erreur de sortie d'état 1
I think that with all the installs I made some minor manipulation went wrong with hal but I don't know what.

my second problem is about launching properly xfce 4. I can launch xfce from the chroot debian terminal with:
startxfce4
But it isn't fullscreen and it doesn't look like a clean launch at all compared to qole's icewm icon. I looked in the icon of qole and found out that it was this command:
debwm icewm xpice
I tried:
debwm xfce xpice
and
debwm startxfce4 xpice
in an OS2008 terminal but it is not fullscreen and completely buggy (I only see the wallpaper)

But xfce works, when I type startxfce4 in the chroot terminal, the menu, the bar ... they work. So I'm sure there isn't much to do for it to go as flawless as qole's icewm, just that a stupid guy like me don't know what to do to make it work. :)

Re: Running Debian in a chroot
 

the xpice is a command qole wront on the debian side that statically launches IceWM.. if you want to launch XFCE you need to copy the xpice command in the debian root shell (so launch Debian Chroot):
Then edit the /usr/bin/wmxfce .. there is a line that specifically says icewm-session.. change that to xfce-session (i think - it might be xfce4-session or similar.. type xfce in a debian chroot and hit tab twice).

To something like:
As far as full screen.. read back a page or two - i think there is some python dependencies you need..

Re: Running Debian in a chroot
 

Here's the post from qole regarding the python dependencies... it was in the other thread as well:

Also: I get that hal reconfigure error all the time as well now.. but it doesn't actually hinder the installation of my apps.

Re: Running Debian in a chroot
 

I think offensivebias isn't getting fullscreen because he isn't using my Debian script that starts the Xephyr nested X-Server and then sets the display to :1. I think he's actually starting xfce4 directly in OS2008... That produces some seriously weird (but somehow really cool :D ) stuff.

Make sure you use fatalsaint's method for copying and modifying the xpice script.

As for hal, just "apt-get remove hal" ... you don't need it and it won't install right on the tablet. If you can't get it to uninstall, tell me and I'll tell you how to hack dpkg to get it to work. But I hope you can just get it to uninstall. dbus is the other package that doesn't install right.

Re: Running Debian in a chroot
 

I was able to uninstall with no problem hal, thanks.

For xfce, qole was right, I was launching "debwm xfce xpice" in an 0S2008 terminal because I thought that the icewm icon qole created was launching from 0S2008. I did what you said about xpice, but how do I launch "debwm xfce wmxfce" on an icon like icewm ? Or if too complicated to explain in which terminal should I launch it ?
(because when I input "debwm xfce wmxfce" in a debian chroot terminal, it tells me command not found and when I launch it from a 0S2008 terminal the host window appears, sadly, debian and xfce do not follow :confused: ).
Maybe I should put something else too in the wmxfce ? I tried to replace "icewm-session" with "xfce-session" and "startxfce4" (the command to start xfce on a normal computer).

thank you all for the very quick reply to my previous post

note: with "startxfce4" in wmxfce, when I launch "debwm xfce wmxfce" in an OS2008 terminal, I get for a brief period a time a minimized black screen with the mouse in x form (like the first moments when x starts, I can move it) and it disapears to leave only the host window, I get the following in the 0S2008 terminal:
oups sorry forgot to paste the output
note: with xfce4-session it gives

Re: Running Debian in a chroot
 

First, I realized that fatalsaint's instructions need one little bit more to make things work smoothly. Find this line in your Debian script:
This line starts the Xephyr nested X-Server. It looks for a host window titled "icewm" and then uses that window. So if you want to call your host window something else (like xfce4), you have to change the "icewm" in that line to "xfce4". Basically, you change "icewm" to whatever your first parameter of "debwm" is.

Now, the "debwm" command is in OS2008, so you have to run that from an OS2008 terminal, not a Debian chroot terminal. You can troubleshoot your Debian wmxfce script by opening two terminal windows, the standard osso-xterm window and Debian chroot terminal. In the osso-xterm window, enter:
This will open the host window for xfce4.

Now, in the Debian chroot, you run wmxfce (make sure you've made the change above). If it doesn't work, or if it starts up in something other than the xfce4 host window, post the errors, and I'll help out.

When it all works, you can run this from a non-Debian OS2008 terminal or make a menu item to do this automagically:

EDIT: Just in case you didn't notice, I have a special affection for xfce4; I pestered JohnX about making it the default window manager for bootable Debian, and it was the first WM I got running using this method, see this post back on the first page.


http://farm3.static.flickr.com/2059/...4603f6b4d1.jpg

Re: Running Debian in a chroot
 

I also forgot to add that you may need to chmod +x /usr/bin/wmxfce - shouldn't if it was copied from an executable; but it might be necessary as I haven't tried it in practical application on this yet...

To add an icon the panel you can do one of two things.. Install Personal Menu; go into the Control Panel; and edit "Personal Menu"..

The other thing is to copy the /usr/share/applications/hildon/debwm.desktop to something like /usr/share/applications/hildon/wmxfce.desktop .. Edit it; and change the Title and Commands to their respective ones.

ETA: I did some googling and I think the command is actually xfce4-session .. not xfce-session... so try that one inside of wmxfce..

Re: Running Debian in a chroot
 

Qole - quick thought;
in your next edition/release.. any chance you could make debwm take 4 arguments, and change xpice to something more generic (startwm) and have it take 2 arguments..

debwm IceWM startwm IceWM icewm-session

this makes it dynamic.. your shortcuts and stuff will still launch iceWM by default.. but this makes it so users can simply add their own menu icon by running:

debwm xfce4 startwm xfce4 xfce4-session

The code would look something like this:

There might be a way to clean that up a bit .. obviously the first and third arguments need to be the same as they both represent the window managers title.. if there was some way to pass that title using just the first argument would be nice but I haven't tried any of this on my table.. i might do it while I'm bored here at work though..

Re: Running Debian in a chroot
 

Ok.. it was a little harder than I originally thought...I added this to the beginning of xpice:

Then there is 2 wmctrl lines that reference IceWM.. must replace both those lines with $title.. the Xepyr line becomes:
The launcher line becomes:

And then in the debwm file..


I don't know if you'd be even remotely interested in doing this.. but that's what I had to do to get it working. Then of course the changes to the launcher in the menu system in the post above. Makes it dynamic for the end user to launch their own WM.. however it obviously requires the end user to know things like the wm launcher command.. and to keep $1 and $3 of the debwm the same... so not sure if it's much better or not lol.

Re: Running Debian in a chroot
 

Xfce is the first you got working, that's right (forgot it). I couldn't get openwindow.py working, is it one of your other script ? (I quickly reread the thread but couldn't find it, I'm really not good at coming in the middle of a thread), I wasn't able to find it either with a <sudo find / -iname 'openwindow.py'> so it isn't in my system.