Minisys-Linux Muppy008 (dec, 20, 2007) / SP3 (jan, 13, 2008)
no, this is not normal.
I can connect to the internet without delay.
But maybe it is another issue.
We had cases, where msy_save.2fs (also pup_save.2fs) was loaded extremely slow.
This happened if it was saved on a ext3 or Reiserfs partition.
On a vfat, it loads very fast.
Maybe a filesystem-check is needed?
fsck.ext3 for example. The partion to check should not be mounted.
I just finished Version 008.1.
Unfortunately upload to sourceforge is very slow.
The files will be there tomorrow.
I have made so many changes meanwhile, maybe this works better for you.
I start to upload the Minis, then the addons_081.sfs (Openoffice and such).
Then maybe in 2 days the 2 full size isos.
With the minis, just around 240 MB of Ram is used.
I'll announce them in a new thread, when they are available (after some sleep).
Mark
I can connect to the internet without delay.
But maybe it is another issue.
We had cases, where msy_save.2fs (also pup_save.2fs) was loaded extremely slow.
This happened if it was saved on a ext3 or Reiserfs partition.
On a vfat, it loads very fast.
Maybe a filesystem-check is needed?
fsck.ext3 for example. The partion to check should not be mounted.
I just finished Version 008.1.
Unfortunately upload to sourceforge is very slow.
The files will be there tomorrow.
I have made so many changes meanwhile, maybe this works better for you.
I start to upload the Minis, then the addons_081.sfs (Openoffice and such).
Then maybe in 2 days the 2 full size isos.
With the minis, just around 240 MB of Ram is used.
I'll announce them in a new thread, when they are available (after some sleep).
Mark
-
- Posts: 405
- Joined: Mon 01 Jan 2007, 20:24
- Location: Hayslope, near Middlemarch, Midlands, England
Hey; you beat me to it! I logged back on so I could update my posting, but you have already replied - wow.
Anyway, it looks as if the wireless connection delay was " one of those things" as it is fine on re-boot, and was also fine setting up afresh with another Puppy version.
Disk Free is still a problem, however. Sorry.
Nick
Anyway, it looks as if the wireless connection delay was " one of those things" as it is fine on re-boot, and was also fine setting up afresh with another Puppy version.
Disk Free is still a problem, however. Sorry.
Nick
Please examine the errorlog.alcoheca wrote:Hi,
Hi my frugal Muppy008 has an issue..
I tried to change my locale to en_GB using the Puppy wizards and now icewm does not show up on startup, even after changing locale back to en_US.
If you need more information, would be glad to provide it.
mp /tmp/xerrs.txt
Maybe that gives a hint.
I'll also have a look at that when I test the isos later today.
There was a similar error reported for french in the Muppy-build thread, but I was not able to reproduce it yet.
As an own build has many changes, it is good to see your report now.
This will be easier to reproduce I hope.
Also try to run by typing
xwin jwm
You then might be able to select icewm from the "windowmanager" menu.
Mark
hi Mark,MU wrote: Please examine the errorlog.
mp /tmp/xerrs.txt
Maybe that gives a hint.
I'll also have a look at that when I test the isos later today.
There was a similar error reported for french in the Muppy-build thread, but I was not able to reproduce it yet.
As an own build has many changes, it is good to see your report now.
This will be easier to reproduce I hope.
Also try to run by typing
xwin jwm
You then might be able to select icewm from the "windowmanager" menu.
Mark
You're right, changing the window manager to jwm, restarting X then changing back to icewm has fixed that problem.
However I have another issue to do with the personal session file.
When I first installed Muppy, I had the option to save to a partition rather than a 2fs file, so I chose that as I would prefer it over a set size of storage file.
Muppy doesn't pick up the saved settings and each time I start, I need to set everything up again.
So I changed to saving to a 512MB 2fs file and now the settings are being saved, however my partition is also being mounted at /mnt/initrd/dev_save
Where are my settings being saved then?
also, I createda folder in /root, copied all my files there, and now when I restart the files can't be found there, only in /mnt/home. How should somebody go about storing their files with this kind of setup?
More info for last post,
# mount
rootfs on / type rootfs (rw)
/dev/hda2 on /initrd/mnt/dev_save type ext2 (rw,noatime)
/dev/loop1 on /initrd/pup_rw type ext2 (rw,noatime)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
/dev/loop3 on /initrd/pup_ro3 type squashfs (ro,noatime)
unionfs on / type unionfs (rw,dirs=/initrd/pup_rw=rw:/initrd/pup_ro2=ro:/initrd/pup_ro3=ro)
tmpfs on /tmp type tmpfs (rw)
none on /proc type proc (rw)
shmfs on /dev/shm type tmpfs (rw)
none on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /proc/bus/usb type usbfs (rw)
###################################
Also, when I run 'DiskFree' from the desktop, nothing appears and I see this in the x error log. Seems to be related to my save file issue.
# cat /tmp/xerrs.log
Error in startup script: child process exited abnormally
while executing
"exec /bin/losetup-FULL /dev/loop1 | grep "/pup_save" | cut -f 2 -d "(" | cut -f 1 -d ")" | cut -f 4 -d "/" "
(procedure "df_check" line 11)
invoked from within
"df_check "
(file "/usr/sbin/partview" line 94)
# mount
rootfs on / type rootfs (rw)
/dev/hda2 on /initrd/mnt/dev_save type ext2 (rw,noatime)
/dev/loop1 on /initrd/pup_rw type ext2 (rw,noatime)
tmpfs on /initrd/mnt/tmpfs type tmpfs (rw)
/dev/loop0 on /initrd/pup_ro2 type squashfs (ro,noatime)
/dev/loop3 on /initrd/pup_ro3 type squashfs (ro,noatime)
unionfs on / type unionfs (rw,dirs=/initrd/pup_rw=rw:/initrd/pup_ro2=ro:/initrd/pup_ro3=ro)
tmpfs on /tmp type tmpfs (rw)
none on /proc type proc (rw)
shmfs on /dev/shm type tmpfs (rw)
none on /dev/pts type devpts (rw)
none on /sys type sysfs (rw)
none on /proc/bus/usb type usbfs (rw)
###################################
Also, when I run 'DiskFree' from the desktop, nothing appears and I see this in the x error log. Seems to be related to my save file issue.
# cat /tmp/xerrs.log
Error in startup script: child process exited abnormally
while executing
"exec /bin/losetup-FULL /dev/loop1 | grep "/pup_save" | cut -f 2 -d "(" | cut -f 1 -d ")" | cut -f 4 -d "/" "
(procedure "df_check" line 11)
invoked from within
"df_check "
(file "/usr/sbin/partview" line 94)
alcoheca :
I must test that on my own in the next days.
Until now I always used save-files, as they are easier to handle.
The partition must be mounted, so that the save-file on it can be accessed.
/mnt/home is just a symbolic link to /initrd/mnt/dev_save, it is a nicer name.
So now your settings should be stored in the save-file (msy_save.2fs)
I will upload Muppy008.1 today, where this is fixed besides several other glitches.
Mark
I cannot tell you, why "save to partition" did not work.When I first installed Muppy, I had the option to save to a partition rather than a 2fs file, so I chose that as I would prefer it over a set size of storage file.
Muppy doesn't pick up the saved settings and each time I start, I need to set everything up again.
I must test that on my own in the next days.
Until now I always used save-files, as they are easier to handle.
Yes, shure.So I changed to saving to a 512MB 2fs file and now the settings are being saved, however my partition is also being mounted at /mnt/initrd/dev_save
The partition must be mounted, so that the save-file on it can be accessed.
/mnt/home is just a symbolic link to /initrd/mnt/dev_save, it is a nicer name.
So now your settings should be stored in the save-file (msy_save.2fs)
Please see the reply above for nic2109, that fixes it.Also, when I run 'DiskFree' from the desktop, nothing appears and I see this in the x error log. Seems to be related to my save file issue.
I will upload Muppy008.1 today, where this is fixed besides several other glitches.
Mark
-
- Posts: 405
- Joined: Mon 01 Jan 2007, 20:24
- Location: Hayslope, near Middlemarch, Midlands, England
This fix worked perfectly. Could it be put into the base system, or is there a reason for leaving it out?willhunt wrote:just run sylpheed and open the configuration>Common Preferences>Details>External commandsnic2109 wrote:One teeny-weeny problemette however: http://etc.etc links in emails have no effect
and edit the Web Rowser statement to readCode: Select all
/usr/local/bin/defaultbrowser -remote 'openURL(%s,new-window)'
Nick
-
- Posts: 405
- Joined: Mon 01 Jan 2007, 20:24
- Location: Hayslope, near Middlemarch, Midlands, England
Making URLs in emails open a browser
The news on making URLs in emails work in sylpheed has moved on a bit.
The fix I quoted earlier does work, but only if you already have a browser session open. If not then you get the little green box saying 'a moment - starting web browser' but no browser appears.
Nick
The fix I quoted earlier does work, but only if you already have a browser session open. If not then you get the little green box saying 'a moment - starting web browser' but no browser appears.
Nick
I have d/led the latest version Minisys Myppy008.1-EN.iso and
all seems to go well. I would like to change the fonts
in the sub menus of the start menu as they look quit thick in
style. I have noted this with other versions of puppy. I like something
crisper. How can it be changed?
I have included a screenshot of a few other things found.
I would like to change the background colour where the wifi antenna
is at bottom right handside as it does not show up clearley
Also the MUT utility has text extending outside the rect box. Is this
a bug?
all seems to go well. I would like to change the fonts
in the sub menus of the start menu as they look quit thick in
style. I have noted this with other versions of puppy. I like something
crisper. How can it be changed?
I have included a screenshot of a few other things found.
I would like to change the background colour where the wifi antenna
is at bottom right handside as it does not show up clearley
Also the MUT utility has text extending outside the rect box. Is this
a bug?
fonts in menu:
edit
/root/.icewm/prefsoverride
MUT:
yes, this happened since a font I installed, that seems to look a bit clearer.
/usr/X11R7/lib/X11/fonts/TTF/
There the Vera-fonts.
I think before, the text was smaller.
I will try to search where to set it in mut.tcl.
-------------------------
The Wifi-antenna:
Is it still dark after you restart X?
It is a problem with the tray, that the backgroundcolor does not change, if you use a different icewm-theme.
Just after restarting X it is set.
Which application is this?
Mark
edit
/root/.icewm/prefsoverride
MUT:
yes, this happened since a font I installed, that seems to look a bit clearer.
/usr/X11R7/lib/X11/fonts/TTF/
There the Vera-fonts.
I think before, the text was smaller.
I will try to search where to set it in mut.tcl.
-------------------------
The Wifi-antenna:
Is it still dark after you restart X?
It is a problem with the tray, that the backgroundcolor does not change, if you use a different icewm-theme.
Just after restarting X it is set.
Which application is this?
Mark
MUT:
edit /usr/lib/mut/mut.tcl
change:
Line 1219
to:
I'll add this in the next version.
Mark
edit /usr/lib/mut/mut.tcl
change:
Line 1219
Code: Select all
.boxc create text [expr "$x1 + 4"] $y1 -anchor nw -text $tex -fill $colour -font {Helvetica -10 bold}
Code: Select all
.boxc create text [expr "$x1 + 4"] $y1 -anchor nw -text $tex -fill $colour -font {Helvetica -9 bold}
Mark
Re: Muppy 080 final
Hi Mark
Have you had time to look at this bug (from Dec 20th)
Have you had time to look at this bug (from Dec 20th)
I use wide screen monitors and the clock is always reset to the initial positionBarburo wrote: 2. The analog clock always resets to the same initial position - it doesn't remember where I move it.
Barburo,
please exit the clock with a right-click.
That will save the position.
I soon will relese an updated version, that remembers the position after every move.
If that does not work, you might have found a bug.
Then try to set the position with an editor (while the clock is not running) in
/root/.GtkBasic-Analogclock/windowposition.txt
Mark
please exit the clock with a right-click.
That will save the position.
I soon will relese an updated version, that remembers the position after every move.
If that does not work, you might have found a bug.
Then try to set the position with an editor (while the clock is not running) in
/root/.GtkBasic-Analogclock/windowposition.txt
Mark
Thanks Mark,
Yes that does it. (I should have experimented a bit more!)
A question: I use muppy008 on an HP Pavilion laptop tx1000 model that I tweaked the xorg.confile to get the correct 1280x800 resolution working by adding an extra "screen" section. The laptop uses an nvidia card. Muppy's nvidia install worked flawlessly. I also use a 22" wide screen external monitor, and I can plug-in the monitor to an already-running Muppy session and it displays the full screen resolution (something like 1800x1600) perfectly. No restarts, no extra specification for the new screen size and resolution. I didn't need to do anything. How does this work?
Yes that does it. (I should have experimented a bit more!)
A question: I use muppy008 on an HP Pavilion laptop tx1000 model that I tweaked the xorg.confile to get the correct 1280x800 resolution working by adding an extra "screen" section. The laptop uses an nvidia card. Muppy's nvidia install worked flawlessly. I also use a 22" wide screen external monitor, and I can plug-in the monitor to an already-running Muppy session and it displays the full screen resolution (something like 1800x1600) perfectly. No restarts, no extra specification for the new screen size and resolution. I didn't need to do anything. How does this work?
I can't tell you, how it works.
The Nvidia-installer uses an own utility to build xorg.conf.
So the xorg.conf from Puppys xorgwizard is overwritten by the Nvidia-installer (I had to tweak Puppy, so that it does not destroy again the new xorg.conf by Nvidia).
I commented some lines in /usr/X11R7/bin/xwin to remove Puppys Hardware-profiling, that would remove the new xorg.conf.
I added a comment to that part around line 181.
Mark
The Nvidia-installer uses an own utility to build xorg.conf.
So the xorg.conf from Puppys xorgwizard is overwritten by the Nvidia-installer (I had to tweak Puppy, so that it does not destroy again the new xorg.conf by Nvidia).
I commented some lines in /usr/X11R7/bin/xwin to remove Puppys Hardware-profiling, that would remove the new xorg.conf.
I added a comment to that part around line 181.
Mark