E17 windowmanager all in one pet, wmswitcher, usual modules
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.
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.
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:
I then tried installing LuPu 528, then E17 ... because reading this thread it seemed the problem could be only affecting 529 and subsequent distros.
No effect, I encountered the same problem.
The problem presents itself asap... even if I just install E17 without actually switching it on.
As soon as X restarts, the problem shows up.
Is there a way to uninstall/remove the Openbox WM or the Fbpanel toolbar?
Maybe this will get around the crossover problem :\
But I can't seem able to find a document that explains how.
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:
I tried the solution posted HERE but I only messed up things worse, so I had to re-install Puppy clean from scratchI get a mixed desktop which can probably be cleaned up, however to switch WM it required Ctrl>Alt>Backspace and then xwin since restart X would not work.
I then tried installing LuPu 528, then E17 ... because reading this thread it seemed the problem could be only affecting 529 and subsequent distros.
No effect, I encountered the same problem.
The problem presents itself asap... even if I just install E17 without actually switching it on.
As soon as X restarts, the problem shows up.
Is there a way to uninstall/remove the Openbox WM or the Fbpanel toolbar?
Maybe this will get around the crossover problem :\
But I can't seem able to find a document that explains how.
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.
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.
Awesome!
Let's see in the meantime if I manage to do what you requested
EDIT incoming... ...is this what you needed?
Let's see in the meantime if I manage to do what you requested
EDIT incoming... ...is this what you needed?
Code: Select all
#!/bin/sh
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $
. /etc/rc.d/PUPSTATE
. /etc/rc.d/BOOTCONFIG
if [ -f /root/.jwm/jwm_colors ];then #v3.96
. /root/.jwm/jwm_colors
fi
[ -x /usr/sbin/fixicons ] && fixicons #icon fix for lupu by 01micko
if [ "$LASTUNIONRECORD" != "$PREVUNIONRECORD" ];then #sfs fix?
echo "ICONWIPE" >/tmp/pup_event_icon_change_flag
fi
#v4.01 BK daemon to handle kernel uevents...
/sbin/clean_desk_icons #v4.02 tidy up drive icons first.
/sbin/pup_event_frontend_d & #v403
#w482 reshape background image if widescreen...
[ $PUPMODE -eq 5 ] && /usr/sbin/background_reshape
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/usr/lib/X11/xinit/Xresources
sysmodmap=/usr/lib/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge -nocpp $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f $userresources ]; then
xrdb -merge -nocpp $userresources
fi
if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi
CURRENTWM="`cat /etc/windowmanager`"
#start compiz
if [[ "$CURRENTWM" != "jwm" && "$CURRENTWM" != "icewm" && "$CURRENTWM" != "openbox" && "$CURRENTWM" != "startfluxbox" ]];then
if [[ `which compiz` != "" ]];then LIBGL_ALWAYS_INDIRECT=1 compiz --replace --indirect-rendering --sm-disable ccp emerald --replace &
sleep 3
fi
fi
if [ "$CURRENTWM" = "startkde" ];then
exec startkde
fi
#100501 if full nvidia pkg installed, it has a gui config app...
[ -f /root/.nvidia-settings-rc ] && nvidia-settings --load-config-only
[ -f $HOME/.xgamma-gamma ] && /bin/sh $HOME/.xgamma-gamma #100215 see /usr/sbin/xgamma-gui.
#0.9.8 sync selection-buffer and clipboard. only useful for older apps
#such as rxvt that use the selection-buffer...
[ -f /usr/bin/autocutsel ] && /usr/bin/autocutsel &
#...disadvantage of this is it creates a little square bottom-right of screen.
if [ -e /tmp/videomode ];then #xvesa only: testing a video mode
video-wizard &
fi
[ -f /usr/local/bin/agenda_chk ] && agenda_chk &
#v1.0.7 set by xrandrshell, part of xorg wizard... v3.99...
if [ -f /etc/xrandrindex ];then
#v3.99 workround for dual monitors, 'head -n 1'....
XYDEFAULT="`xrandr | grep '\*' | tr -s " " | grep '^ [0-9]' | cut -f 2 -d " " | head -n 1`"
XRANDRINDEX="`cat /etc/xrandrindex`" #v3.99 XRANDRINDEX now is XxY resolution.
#but do not switch if default is already this resolution....
if [ "$XRANDRINDEX" = "$XYDEFAULT" ];then
rm -f /etc/xrandrindex
else
xrandr -s $XRANDRINDEX
fi
fi
if [ -f /root/.xset.sh ];then
#this is created by /usr/bin/pupx...
eval "/root/.xset.sh"
else
##Xorg has it's own fontpath settings in /etc/X11/xorg.conf...
#if [ "`readlink /usr/bin/X`" != "Xorg" ];then
# #xset fp+ /usr/lib/X11/fonts/Type1/
# #xset fp+ /usr/lib/X11/fonts/TTF/
# xset fp+ /usr/share/fonts/default/Type1/
# xset fp+ /usr/share/fonts/default/TTF/
#fi
xset s 600 600 s blank
fi
#v1.0.7 also see /etc/rc.d/rc.local0
if [ -f /root/.fonts/fonts.dir ];then
xset fp+ /root/.fonts/
fi
[ -f /usr/bin/xsetroot ] && xsetroot -cursor_name top_left_arrow
#v555 w003
#[ -f /usr/bin/xfce-mcs-manager ] && xfce-mcs-manager
#[ "$CURRENTWM" = "xfwm4" ] && xfce-mcs-manager
#...no need to start it here, fvwm4 below will start it automatically.
#if jwm, icewm, openbox or fluxbox then we run rox-desktop #micko 311010 v luci-234
if [[ "$CURRENTWM" != "startxfce4" && "$CURRENTWM" != "startkde" ]];then
#relocates right-side icons to actual right-side of screen...
/usr/sbin/fixPuppyPin /root/Choices/ROX-Filer/PuppyPin #v1.0.7
#w468 on old PCs this sometimes does not start, see further down...
if [ -f /root/Choices/ROX-Filer/PuppyPan1 ];then
rox -p /root/Choices/ROX-Filer/PuppyPin -r /root/Choices/ROX-Filer/PuppyPan1
else
rox -p /root/Choices/ROX-Filer/PuppyPin
fi
fi
#v2.0.0
/usr/sbin/delayedrun &
#v2.01 hide cursor when not moving... (setup in /usr/sbin/input-wizard)
if [ -f /etc/mousehide ];then
IDLETIME="`cat /etc/mousehide | cut -f 1 -d ','`"
[ ! "$IDLETIME" = "0" ] && unclutter -idle $IDLETIME &
fi
##v2.14 rarsa: update xdg menu for w.m. that do not allow includes...
#which ${CURRENTWM}_menu_refresh && ${CURRENTWM}_menu_refresh
#...no, now doing it differently, see /usr/sbin/fixmenus
#v2.17 removed, interferes with clipboard in Composer....
##v2.15 disovered by GuestToo...
#[ "`which glipper`" != "" ] && glipper &
#v2.17 made it optional...
[ -f /root/.glipper_on ] && glipper &
if [ "$CURRENTWM" = "xfwm4" ];then
if [ "`which xfce4-panel`" != "" ];then
xfwm4 --daemon #note, starts xfce-mcs-manager daemon also.
exec xfce4-panel
fi
fi
#v3.91 volume tray applet, thanks to hairywill... v3.96 MENU_BG variable...
if [ -f /usr/bin/absvolume ];then
if [ "$MENU_BG" = "" ];then
absvolume &
else
absvolume -bg $MENU_BG &
fi
fi
#v3.95 support fbpanel tray/taskbar...
#only launch tray for w.m. without inbuilt tray...
if [[ "$CURRENTWM" != "jwm" && "$CURRENTWM" != "icewm" && "$CURRENTWM" != "startxfce4" && "$CURRENTWM" != "startfluxbox" ]];then
if [ -f /usr/bin/fbpanel ];then
#a bit of a hack: when 3builddistro runs fixmenus, which calls variconlinks,
#which populates /var/local/icons with symlinks, /usr/local/lib/X11/pixmaps
#is not yet populated (happens at first boot, from default icon theme)...
[ ! -e /var/local/icons/home48.png ] && ln -fs /usr/local/lib/X11/pixmaps/* /var/local/icons/
fbpanel &
fi
[ -f /usr/bin/lxpanel ] && lxpanel &
fi
##w468 rox may not start old hardware, try again...
#PS="`ps`"
#if [ "`echo "$PS" | grep 'ROX\-Filer'`" = "" ];then
# touch /tmp/roxfilerstartupproblem #see /sbin/pup_event_frontend_d
# sleep 0.2
# rox -p /root/Choices/ROX-Filer/PuppyPin
#fi
#exec $CURRENTWM
#v2.11 GuestToo suggested this improvement...
which $CURRENTWM && exec $CURRENTWM
[ -x $CURRENTWM ] && exec $CURRENTWM
exec jwm
###END###
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 and all the others. I recommend to uninstall existing e17 pet and redownload the repackaged pet from same first page download link.
Last edited by pemasu on Fri 16 Sep 2011, 17:21, edited 1 time in total.
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.
Install the pet and all above are fixed. And the scripts in the wrong place are removed.
- Attachments
-
- e17-fix-0.0.1.pet
- (3.39 KiB) Downloaded 663 times
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
- 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,
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
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
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
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.
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.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
I haven't looked at the .pet But if you have /ect/enlightenment ,see if the sysactions.conf file is in there. If it is, open it as text and edit lines 46 and 47 to use your shutdown/reboot scripts. The scripts still need to be fixed like Iguleder said . This will make the e exit menu shutdown /reboot options work.
This is a older fix , I don't use the e exit menu .
This is a older fix , I don't use the e exit menu .
an alternative approach would be toIguleder wrote: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.
Code: Select all
echo 'enlightenment' > /etc/windowmanager
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
Thanks for all the information and suggestions. The first page enlightenment pet has been repackaged. It went through considerable reorganization. I tested and checked shutdown and reboot options.
Sysconf module has been disabled. Ppoweroff added to the Ibar, Mixer module removed and Alsamixer added to the Ibar, Forecasts gadget added to the Ibar, scripts checked and fixed etc....
I downloaded Lucid 529 aka three headed dog. Couldnt get wlan working whatever I tried. First time in Puppy history since kernel 2.6.33.2 puppies.
Eth0 connection worked, I uploaded and downloaded the e17 pet and checked that it works.
Now the pet has Xmessage which informs that after installing the pet, reboot is needed.
The pet changes the needed scripts.
It might cause that first shutdown needs to be done using console:
wmreboot
Download link: http://www.smokey01.com/pemasu/Pets/e17-62731.pet
Sysconf module has been disabled. Ppoweroff added to the Ibar, Mixer module removed and Alsamixer added to the Ibar, Forecasts gadget added to the Ibar, scripts checked and fixed etc....
I downloaded Lucid 529 aka three headed dog. Couldnt get wlan working whatever I tried. First time in Puppy history since kernel 2.6.33.2 puppies.
Eth0 connection worked, I uploaded and downloaded the e17 pet and checked that it works.
Now the pet has Xmessage which informs that after installing the pet, reboot is needed.
The pet changes the needed scripts.
It might cause that first shutdown needs to be done using console:
wmreboot
Download link: http://www.smokey01.com/pemasu/Pets/e17-62731.pet
Last edited by pemasu on Tue 20 Sep 2011, 18:25, edited 1 time in total.
E17 themes pack which I created after hunting themes from the net. You get 6 extra themes with installing this pet.
http://www.smokey01.com/pemasu/pet_pack ... -0.0.1.pet
http://www.smokey01.com/pemasu/pet_pack ... -0.0.1.pet
Hey pemasu !
Funtastico !
Cool thing you did with E17 . You make me happy .
Using it happily on Puppy Precise 5.5.9 . (tried on Dpup Wheezy but does not work )
This what i really was (waiting ) looking for.
(just need some fine-tuning) Up till now only found mixer module does not find my alsamixer .
Want to thank you for all you have done for us all .(and also all the other developers too ).
Thanks !
Funtastico !
Cool thing you did with E17 . You make me happy .
Using it happily on Puppy Precise 5.5.9 . (tried on Dpup Wheezy but does not work )
This what i really was (waiting ) looking for.
(just need some fine-tuning) Up till now only found mixer module does not find my alsamixer .
Want to thank you for all you have done for us all .(and also all the other developers too ).
Thanks !