You might not see any difference from previous Wary versions. Lots of packages upgraded though, so it is mostly changes "under the bonnet".
There is one known bug. I have not yet determined the cause of this or exactly what circumstances cause it. After the first shutdown and creating a save-file, on next bootup the BootManager runs -- clicking any button in the BootManager hangs it, in fact hangs all applications, although the mouse and keyboard still work.
The workaround, if this happens, is to press CTRL-ALT-BACKSPACE, then "xwin" to restart X, then when the BootManager starts don't try to use it -- instead, right click on the BootManager item in the taskbar and choose "Kill".
The weird thing is, if you start the BootManager via the "System" menu, it works ok.
It's a weird bug, and I am letting it rest in my brain for awhile. Will feel inspired to solve it soon.
Comments:Posted on 17 Sep 2011, 23:36 by Terryphi
Warysave upgrade fails
I am seeing the same problem with Wary as I reported with Racy. Trying to use warysave.2fs from 18.104.22.168 produces same result: black screen and taskbar only.
Posted on 17 Sep 2011, 23:50 by Terryphi
Warysave upgrade error
Further to comment above, using warysave.sfs from 22.214.171.124, it is impossible to set xorg to work and xwin always produces:
FATAL: Module usbhid not found
Posted on 18 Sep 2011, 14:07 by Sage
You are correct - stark is terrible. However, a simple inversion to white on black will make it as stunning as Slacko.
Posted on 18 Sep 2011, 16:52 by scsijon
everything went well including the probe for intel setup (hooray and well done to fix this problem at last); until I tried to install with PUI.
It said it did a partition sanity check before continuing and gave an error "cannot be unmounted,currently mounted rerad-write, does not have warysave.3fs file"; however at this point I haven't even chosen which partition I want to install it into.
I'm using a box with a sata drive and want to install into /sda2 a ext2 partition (as are all my puppy partitions as they share). Not sure where to go from here except hand the problem back to you.
Posted on 21 Sep 2011, 2:56 by rodin.s
Bootmanager bug doesn't happen on my computer. It works normal.
Posted on 25 Sep 2011, 11:47 by broomdodger
the right click (ROX) version of copy has changed because of an update to coreutils
corutils 6.9 -- cp -p "bug"
when copying a file in/to an ntfs partition
+ the copy (ROX right click) would not warn
+ cp -p <file1> <file2> also would not warn
+ cp -p <file1> <file2> warns:
cp: can't preserve permissions of '<file2>': Operation not supported
Successfully copies the file, although it can not preserve the permissions.
coreutils 6.12 -- this looks like a fix to cp
+ the copy (ROX right click) now warns:
Copying <file1> as <file2>
cp: preserving permissions for `<file2>': Operation not supported
Failed to copy '<file1>'
BUT it does successfully copy the file, although not necessarily the permissions.
Maybe the message "Failed to copy..." needs changing to reflect the fact that the file has been copied but not preserving the permissions.
+ cp -p <file1> <file2> also now warns:
cp: preserving permissions for <file>: Operation not supported