Puppy Linux Discussion Forum

[pemasu]

Composite (comp) module there was. I tested it and my e17 didnt even start. I had to boot jwm and I fixed the situation somehow. I tested it using e17 setting wizard several times. Alwayd non-bootable situation.
I removed comp module. If I have left scale module, I will remove it also.
I think that best thing for you is to compile those modules yourself if you have use for them. I believe I uploaded development pet also. if i didnt, I will upload it.

After that I read that there has been problems before with composite. My pet wont include modules which can cause non startable X.

[Hasimir]

Hi, I'm new to the forum, to Puppy and to Linux overall
I'm wrestling to learn how to make this "thing" do my bidding but with veeery little success so far

I'm running a eeePC with:
CPU = atom n450@1.66gHz
RAM = 1Gb RAM

I've Frugally installed LuPu 589 on a 16Gb usb drive.

Now, when I first tried installing E17 I got the same problem as Jim1911:

[pemasu]

Hasimir. I know now the reason to this fbpanel existing problem. The /root/.xinitrc script needs one change so that fbpanel is not activated. I looked the problem from wrong route, before I understood to check that script also. I have working version now.

Anyway. When you have e17 up, you can kill fbpanel in console by typing: killall fbpanel.

I will post the fixed xinitrc later today, when I have the fixed puppy working. I dont have many Puppies with openbox installed, so it goes to the evening before I can grap the fixed script. But the problem is now targeted.

If you want, you could post your .xinitrc script, I check it and make the fix and post it back, so that others can use the fix also.

[Hasimir]

Awesome!
Let's see in the meantime if I manage to do what you requested

EDIT incoming... ...is this what you needed?

[pemasu]

Thanks. I check it now....

[pemasu]

Hasimir and all the others interested of this package. I fixed the fbpanel not shutting down when launching e17. But...I also noticed that when I repackaged the pet that I had copied the working wmreboot, wmexit etc... scripts to /bin and they belong to the /usr/bin. It means that the previous ones where called with Pupshutdown. So...My newly packaged pet from first page now have both fixes. I will make a fixing pet also for those who have already customized their e17 and dont want to uninstall it.

Hasimir and all the others. I recommend to uninstall existing e17 pet and redownload the repackaged pet from same first page download link.

[Hasimir]

thanks!

[pemasu]

Well...it didnt take long. I made the pet which fixes fbpanel existing problem, fbpanel will now be proberly shut down when launching e17 and now the scripts which Pupshutdown uses to exit, shutdown, restartwm and reboot works properly from Shutdown icon in the menu.

Install the pet and all above are fixed. And the scripts in the wrong place are removed.

[Hasimir]

the new package works fine BUT:

- there are still problems with the reboot/shutdown panel ... it doesn't work and when I rebooted the system from the console it crashed X

- for some reason the AudioMixer gadget did not work ... I had to manually start AlsaMixer and use it to regulate my volume settings

[pemasu]

Hasimir. I will check the package again when I have time. I am now a little busy with dpup exprimo.
What closing app are you referring to. I use PupShutdown for closing.
I have it in Polarpup as default app.
If you use e17 own shutdown app, it does not work with puppies.

[aragon]

Pemasu,

Maybe ask iguleder, i think he talked about a patch for e16 to get the long-standing shutdown-issue solved. Maybe he could also patch e17.

Aragon

[Iguleder]

The best solution we have at the moment is building Enlightenment (the window manager itself) with "--disable-syscon" and use a tool like Pupshutdown. Enlightenment's default shutdown/poweroff/etc are handled through PAM, which isn't there on Puppy.

Regarding getting Pupshutdown and similar tools to work, there is a problem. E is started with "enligtenment-start" and wmreboot, wmexit, restartwm, etc' try to kill a process named like that to exit E17. However, "enlightenment-start" launches "enlightenment", which is the window manager itself. It's similar to the problem with Xfce, which starts the panels and they don't die so you can't quit Xfce.

The solution is simple: add "killall enlightenment" to wmreboot, restartwm, wmexit and wmpoweroff.

[pemasu]

Thanks Iguleder. I will check the specs of those files tomorrow. I repackage the pet if needed.
Thank you.

[Béèm]

I just log out of E17 and type reboot or poweroff at the X prompt.

[Hasimir]

I didn't know about the E17 poweroff problem >_<'