BarryK wrote:I have just gone through the exercise of doing a frugal install on my "workhorse" laptop, and discovered a couple of bugs.
I was talking about the first boot up window while the system will create the second (ext) partition.BarryK wrote:I am not sure where this is. Do you mean the little popup message that appears briefly, just before the QuickSetup window?rufwoof wrote:I had the same in a earlier version. Subsequent boots were fine.FeodorF wrote:At very first boot you'll see the message *Easy $[DISTR_VERSION] instead of "0.9.9".
.. that one disappears so fast, I never read it.
Ah, that's why I never knew what you guys were complaining about!FeodorF wrote:I was talking about the first boot up window while the system will create the second (ext) partition.BarryK wrote:I am not sure where this is. Do you mean the little popup message that appears briefly, just before the QuickSetup window?rufwoof wrote: I had the same in a earlier version. Subsequent boots were fine.
.. that one disappears so fast, I never read it.
Boy, I had some fun with this problem - but it is solved!FeodorF wrote:Ups problem!
After taking the photo I realized that the communication with the pop up window went dead. Had to hard boot the PC.
How about a little ugly tray icon?rufwoof wrote:Perhaps the Alt-F6 message needs to be something other than a popup message ???
Xephyr is a server that outputs to a window on a pre-existing host X display. Somewhat like Xnest but unlike Xnest which is a X proxy, i.e. limited to the capabilities of the host X server, Xephyr is a real X server which uses the host X server window as a "framebuffer".
Code: Select all
#rm -f ${DIRSESSION}/root/Choices/ROX-Filer/* 2>/dev/nullCode: Select all
rox -p /root/Choices/ROX-Filer/PuppyPin
jwmCode: Select all
<JWM>
<!-- IMPORTANT, ONLY EDIT /etc/xdg/templates/_root_.jwmrc -->
<!-- jwm menu for puppy Linux -->
<StartupCommand>killall ROX-Filer</StartupCommand> <!-- ensure rox is clean -->
<StartupCommand>rox -p /root/Choices/ROX-Filer/PuppyPin</StartupCommand> <!-- show pinboard -->
<StartupCommand>/root/Startup/pmcputemp_tray</StartupCommand>
<StartupCommand>/root/Startup/freememapplet_tray</StartupCommand>
<RootMenu label="Menu" labeled="false" height="24" onroot="3">Yes, that looks like a good way to do it. Will add that to the to-investigate list.rufwoof wrote:Having reverted back to the default rox pinboard, if I simply comment out /usr/local/easy-containers/start-container line 216then for me the easy container works much better when I move icons, change background wallpaper/icon themes/jwm theme ...etc.Code: Select all
#rm -f ${DIRSESSION}/root/Choices/ROX-Filer/* 2>/dev/null
If additionally I change ..../containers/easy/.session/.control/easy (created by /usr/local/sfsget/dir2sfs) and comment out all of the code from "# start rox" comment onwards and replace that with justand modify /etc/xdg/templates/_root_.jwmrc to add in some StartupCommands so it looks something like ....Code: Select all
rox -p /root/Choices/ROX-Filer/PuppyPin jwmthen as jwm isn't backgrounded as per current, then you can run jwm -exit and the container closes and drops you back to the main session. As-is if you run jwm -exit it leaves just rox running (no jwm panel).Code: Select all
<JWM> <!-- IMPORTANT, ONLY EDIT /etc/xdg/templates/_root_.jwmrc --> <!-- jwm menu for puppy Linux --> <StartupCommand>killall ROX-Filer</StartupCommand> <!-- ensure rox is clean --> <StartupCommand>rox -p /root/Choices/ROX-Filer/PuppyPin</StartupCommand> <!-- show pinboard --> <StartupCommand>/root/Startup/pmcputemp_tray</StartupCommand> <StartupCommand>/root/Startup/freememapplet_tray</StartupCommand> <RootMenu label="Menu" labeled="false" height="24" onroot="3">
Code: Select all
HOSTNAME=EASYPC10092
XDG_DATA_HOME=/root/.local/share
TERM=xterm
SHELL=/bin/bash
HISTSIZE=1000
QT_XFT=true
GTK2_RC_FILES=/root/.gtkrc-2.0
DEFAULTDRAW=inkscape
QT5DIR=/usr
MOZILLA_FIVE_HOME=/usr/lib/seamonkey
XLIB_SKIP_ARGB_VISUALS=1
USER=root
HISTFILESIZE=2000
LS_COLORS=bd=33:cd=33
GDK_USE_XFT=1
LANGORG=en_GB.UTF-8
RGBDEF=/usr/share/X11/rgb.txt
OOO_FORCE_DESKTOP=gnome
DEFAULTIMAGEVIEWER=gpicview
MOZ_DISABLE_PANGO=1
DEFAULTPAINT=mtpaint
MOZ_PLUGIN_PATH=/usr/lib/mozilla/plugins:/usr/lib/seamonkey/plugins
XDG_CONFIG_DIRS=/etc/xdg
PATH=/usr/local/bin:/.control:/usr/sbin:/usr/bin:/sbin:/bin
DEFAULTBROWSER=mozstart
DEFAULTMEDIAPLAYER=xinewrapper
_=/usr/bin/env
QT_QPA_PLATFORMTHEME=gtk2
EC_CAP_DROP=
PWD=/
INPUTRC=/etc/inputrc
DEFAULTIMAGEEDITOR=mtpaint
EDITOR=mp
LANG=en_GB.UTF-8
XFINANSDIR=/root/.xfinans
DEFAULTHTMLEDITOR=mozedit
DEFAULTSPREADSHEET=exec
HISTCONTROL=ignoredups
HOME=/root
SHLVL=8
XDG_CONFIG_HOME=/root/.config
MAKE=make
XDG_CACHE_HOME=/root/.cache
LOGNAME=root
G_FILENAME_ENCODING=@locale
PREFIX=/usr
XDG_DATA_DIRS=/usr/share:/usr/local/share
PKG_CONFIG_PATH=/usr/share/pkgconfig:/usr/lib/pkgconfig
TEXTDOMAIN=xwin
WINDOWPATH=4
DISPLAY=:1
MM_RUNASROOT=1
container=pflask
DEFAULTTEXTEDITOR=geany
DEFAULTWORDPROCESSOR=swriter
NO_AT_BRIDGE=1
OUTPUT_CHARSET=UTF-8Code: Select all
Current: = cap_fsetid,cap_setgid,cap_setuid,cap_linux_immutable,
cap_net_bind_service,cap_net_broadcast,cap_net_raw,cap_ipc_lock,
cap_ipc_owner,cap_sys_rawio,cap_sys_pacct,cap_lease,cap_audit_write,
cap_audit_control,cap_mac_override,cap_mac_admin,cap_syslog,
cap_wake_alarm,cap_block_suspend,cap_audit_read+ep
Bounding set =cap_fsetid,cap_setgid,cap_setuid,cap_linux_immutable,
cap_net_bind_service,cap_net_broadcast,cap_net_raw,cap_ipc_lock,
cap_ipc_owner,cap_sys_rawio,cap_sys_pacct,cap_lease,cap_audit_write,
cap_audit_control,cap_mac_override,cap_mac_admin,
cap_syslog,cap_wake_alarm,cap_block_suspend,cap_audit_read
Ambient set =
Securebits: 00/0x0/1'b0
secure-noroot: no (unlocked)
secure-no-suid-fixup: no (unlocked)
secure-keep-caps: no (unlocked)
secure-no-ambient-raise: no (unlocked)
uid=0(root)
gid=0(root)
groups=Problem returned - it wasn't the Dell screen!FeodorF wrote:My Dell screen comes with a built-in USB hub. As soon as there is no more data running through the USB for over 30 minutes this thing goes dead. Dead as dead can be even with the 5 Volts still being present.
Finally fixed that one!BarryK wrote:Ah, that's why I never knew what you guys were complaining about!FeodorF wrote:I was talking about the first boot up window while the system will create the second (ext) partition.BarryK wrote: I am not sure where this is. Do you mean the little popup message that appears briefly, just before the QuickSetup window?
.. that one disappears so fast, I never read it.
I usually test on my UEFI-BIOS machines, which have a different boot menu (using refind).
When boot on a traditional BIOS machine, Syslinux handles the bootup and you get the Syslinux menu.
My circa-2011 Acer laptop, that I am using right now, running the frugal install, mostly sits neglected these days.
OK, will get onto it.