Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 21 Jun 2018, 06:43
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
tahrpup 6.0, 6.0.2 & 6.0.5 CE
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 35 of 56 [830 Posts]   Goto page: Previous 1, 2, 3, ..., 33, 34, 35, 36, 37, ..., 54, 55, 56 Next
Author Message
rerwin


Joined: 24 Aug 2005
Posts: 1889
Location: Maine, USA

PostPosted: Sat 28 Mar 2015, 21:07    Post subject:  

OK, got more info. I see that the debug code above does not appear to have any bad consequences. It just wasted my time checking the suspicious-looking code.

I dug deeper into the "not saved" issue and found that I am wrong about the free-space explanation for failure to save. I traced the activities of shutdownconfig and found that it is misled by the way I boot the PC having the problem (not the one that has sufficient space).

I always boot from a CD but rely on matching puppy main files on hard-drive. Three partitions are available for pupsave files, FS types ntfs, vfat and ext2. For this command:
Code:
PARTSLIST="`probepart -m 2> /dev/null | grep '^/dev/' | grep "$expBOOTDRV" | grep -E 'f2fs|ext2|ext3|ext4|reiserfs|msdos|vfat|minix|ntfs|btrfs' | cut -f 1-3 -d '|' | sed -e 's/msdos/vfat/g'`"
$expBOOTDRV is "/dev/sr". Its file system type is iso9660, so is disqualified as a target partition. The hard drive partitions are ignored, including the one containing the puppy main file being used!

Shouldn't there be further searching for a place to put the pupsave file, as has always been done?

This explains why there has been no report of the problem, because it requires my type of boot arrangement, which is necessary to avoid adding dual booting to a Vista PC. But it appears to be more complicated than I suspected.

Where do we go from here, to fix it?
Richard
Back to top
View user's profile Send private message 
LazY Puppy


Joined: 21 Nov 2014
Posts: 2007
Location: Germany

PostPosted: Sat 28 Mar 2015, 22:41    Post subject:  

Hi.

I have a general question regarding building Puppy from Woof/WoofCE.

If you finished a first version and published it how is that to be continued when users gave information about bugs and issues of the first build?

Do you again a Woof/WoofCE build or is any further fixed version just a remaster after the first build?

Thanks.

_________________
RSH

"you only wanted to work your Puppies in German", "you are a separatist in that you want Germany to secede from Europe" (musher0) Laughing

No, but I gave my old drum kit away for free to a music store collecting instruments for refugees! Wink
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2971

PostPosted: Sun 29 Mar 2015, 00:56    Post subject:  

rerwin wrote:

Where do we go from here, to fix it?
Richard

Good catch Richard.
Indeed the presence of a subdir with the puppy files trips the logic.
Assuming that you indeed you have a folder with the sfs and (older) savefiles check this patch to see if it fixes it.
Code:
--- a/usr/sbin/shutdownconfig   2015-01-11 17:05:26.000000000 +0800
+++ b/usr/sbin/shutdownconfig   2015-03-29 04:45:53.143279555 +0800
@@ -136,7 +136,7 @@
   expBOOTDRV="/dev/`echo ${PDEV1} | sed -e 's%[0-9]*$%%'`"
   PCHOOSE="yes"
  fi
- if [ "$xPSUBDIR" ];then #if pup installed in a sub-directory, allow save-file in another partition (in same drive)...
+ if [ "$xPSUBDIR" -a "$PMEDIA" != "cd" ];then #if pup installed in a sub-directory, allow save-file in another partition (in same drive)...
   expBOOTDRV="/dev/`echo ${PDEV1} | sed -e 's%[0-9]*$%%'`"
   PCHOOSE="yes"
  fi


(now in woof-CE)

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
Hesse James


Joined: 08 Feb 2010
Posts: 75

PostPosted: Sun 29 Mar 2015, 06:17    Post subject:  

Hello
I just found out that the used JWM-976 cannot display additional vertical trays correctly like:

<Tray autohide="true" border="0" y="40" halign="left" width="100" layout="vertical">

A switch back to JWM-905 from Slacko solved this issue.
Have a nice day.

Christian
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1889
Location: Maine, USA

PostPosted: Sun 29 Mar 2015, 13:57    Post subject:  

mavrothal,
Thank you for the fix. It restores the capability to save from a boot from CD with the main file already on hard drive.

Somewhat related to this, in that it involves rebooting the first time with the new pupsave file, is the apparent inability to retain the selection of the VESA video driver. To recover from booting with pfix=ram (or pupsave number 0) to a blank screen that gradually becomes lighter, I have to ctrl-alt-bksp and run xorgwizard to select "vesa" and then enter "xwin".

When I reboot the the newly created pupsave file, I have to repeat that sequence, suggesting that my previous selection of vesa was not retained in the new pupsave. Not a showstopper, but maybe something easy to fix by someone knowledgeable of the video stuff.
Richard
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2971

PostPosted: Sun 29 Mar 2015, 14:20    Post subject:  

rerwin wrote:
Somewhat related to this, in that it involves rebooting the first time with the new pupsave file, is the apparent inability to retain the selection of the VESA video driver.

I can not reproduce that in tahr. Is it with both savefile and savefolder?
If you boot another puppy in the same machine, how the /etc/X11/xorg.conf looks in the newly created savefile/folder?

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1889
Location: Maine, USA

PostPosted: Sun 29 Mar 2015, 15:09    Post subject:  

mavrothal,
Thanks for the quick response. After posting it, I remembered that my test is on my updated test version of lupu 5.2.8.7, not tahrpup. I do not have the video problem with tahrpup, so canot reproduce it myself, either.

I should not have mentioned it here, since the problem is probably in the lupu version of rc.shutdown, which is much different that tahr's.

But thanks for the suggestion, so I can pursue it on my own.

I tested your fix on tahrpup, too, with the same positive result.
R

A few minutes later: The new pupsave file is empty except for an empty "lost+found" directory, which explains why I have to re-do the vesa selection. As that pertains only to the special luci version of the save-to-directory upgrade, I will take any discussion of this problem over to the lupu 5.2.8.7 thread.
R
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2971

PostPosted: Sun 29 Mar 2015, 16:28    Post subject:  

rerwin wrote:
A few minutes later: The new pupsave file is empty except for an empty "lost+found" directory, which explains why I have to re-do the vesa selection. As that pertains only to the special luci version of the save-to-directory upgrade, I will take any discussion of this problem over to the lupu 5.2.8.7 thread.
R
Confused
Are you using the Luci_SaveDir-6.pet as base or something else?

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1889
Location: Maine, USA

PostPosted: Sun 29 Mar 2015, 17:03    Post subject:  

Yes, Luci_SaveDir-6.pet. I am taking its content (and that of the tarball, but not the savefolder creation code) as the base of my integrated update to 5.2.8.7. I need to update it for the 20141203 release and merge a petget script with that of the "petget rewrite" package. All of that will go into my "zz_...update" package that makes the puppy basic infrastructure changes.

One thing I am adding that you did not (although the history comment is there) is the inclusion of whiteout files in the new pupsave. That would seem to be appropriate for woof-CE -- but I have just not gotten around to submitting it, among other fixes to lupu that might port to woof-CE. The patch to rc.shutdown for lupu is:
Code:
--- rc.shutdown-lucisavedir   2015-03-29 17:00:36.080211101 -0400
+++ rc.shutdown   2015-03-29 12:55:23.000000000 -0400
@@ -52,6 +52,7 @@
 #111208 rerwin: add user flash-drive save-control option
 #120103 karl godt: error unmounting stray partitions. 120103 karl godt: more tweaks.
 #120220 unmount network shares before taking down the network
+#120408 Retain deletions by copying whiteout files.
 
 clear
 exec 1> /dev/null 2>&1
@@ -417,7 +418,11 @@
     touch "/tmp/save1stpup/${BASENAME}" --reference="$ONEDIR"
    fi
    cp -a $ONEDIR/* /tmp/save1stpup/${BASENAME}/ #v2.16exp3
-   [ "$BASENAME" = "root" ] && cp -a $ONEDIR/.[0-9a-zA-Z]* /tmp/save1stpup/${BASENAME}/ #v2.16exp4
+   if [ "$BASENAME" = "root" ];then #120408...
+    cp -a $ONEDIR/.[0-9a-zA-Z]* /tmp/save1stpup/${BASENAME}/ #v2.16exp4
+   else
+    cp -a $ONEDIR/.wh.* /tmp/save1stpup/${BASENAME}/
+   fi #120408 end
   done
   sync
   [ -L /tmp/save1stpup ] || umount /tmp/save1stpup
That should fit easily into the mainstream version of rc.shutdown.
R

Two hours later: I reran my conversion of the content of Luci_SaveDir-6 plus the "cd" fix, with the result that the new pupsave does contain the appropriate directories. So, I need to fix my original version. Sorry for the false alarm.
Richard
Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3177
Location: wales

PostPosted: Mon 30 Mar 2015, 07:30    Post subject:  

bigpup wrote:
Here is a bug with a solution fix.

Problem with Bulgarian keyboard layout variant
Subject description: Keyboard layout variant resets after reboot
http://www.murga-linux.com/puppy/viewtopic.php?t=98251


thanks ...i've added the fix .... hope it doesn't break anything Smile

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3177
Location: wales

PostPosted: Mon 30 Mar 2015, 08:08    Post subject:  

LazY Puppy wrote:
Hi.

I have a general question regarding building Puppy from Woof/WoofCE.

If you finished a first version and published it how is that to be continued when users gave information about bugs and issues of the first build?

Do you again a Woof/WoofCE build or is any further fixed version just a remaster after the first build?

Thanks.


hi LazY Puppy,

apart from the first 2 tahrpup alpha iso's (which i remastered) all the rest are woof CE builds.
one thing i found useful when tahrpup was in testing was to have an update/bugfix mechanism, so that when bugs were reported and fixed, these could be applied immediately for users, and it also served gather all the fixes into one place, which could then easily be added to the next build.

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2971

PostPosted: Mon 30 Mar 2015, 08:15    Post subject:  

666philb wrote:
one thing i found useful when tahrpup was in testing was to have an update/bugfix mechanism, so that when bugs were reported and fixed, these could be applied immediately for users, and it also served gather all the fixes into one place, which could then easily be added to the next build.


And hopefully when you get the time provide (individual) patches for the relevant ones for woof-CE Wink

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3177
Location: wales

PostPosted: Mon 30 Mar 2015, 12:32    Post subject:  

mavrothal wrote:


And hopefully when you get the time provide (individual) patches for the relevant ones for woof-CE Wink


my main computer is down at the moment but i'll have another go at git when it's fixed

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3177
Location: wales

PostPosted: Mon 30 Mar 2015, 12:40    Post subject: Re: Tharpup 6.0.2 devx sfs
Subject description: path is all mixed up in header files of glib gtk etc...
 

keyboard wrote:


That is not the package I am compiling , I am compiling my own software but glade, gtk cairo and other header files are mixed up.

And no I can't put it in better words than this , a developer would understand this i presume.


hi keyboard,

if you can be more specific, the devx can be fixed if need be.
all the .dev files are from ubuntu.debs and should be in the same place as ubuntu has them. there is the possibility that some are missing.

let me know

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8675
Location: qld

PostPosted: Tue 31 Mar 2015, 21:29    Post subject: Re: Tharpup 6.0.2 devx sfs
Subject description: path is all mixed up in header files of glib gtk etc...
 

666philb wrote:
keyboard wrote:


That is not the package I am compiling , I am compiling my own software but glade, gtk cairo and other header files are mixed up.

And no I can't put it in better words than this , a developer would understand this i presume.


hi keyboard,

if you can be more specific, the devx can be fixed if need be.
all the .dev files are from ubuntu.debs and should be in the same place as ubuntu has them. there is the possibility that some are missing.

let me know


There is no problem with the devx as far as I can tell. I compile my own programs all the time linking with gtk, cairo, xlib whatever.

keyboard, what programming environment have you come from? In linux pkg-config is the program you need to find headers. You add it to your commandline.

For example, you have :
Code:
gcc dailog.c -o dailog -lm

.. which is telling the compiler to link with libm, but as you can see from your errors, none of the gtk headers are found.

Try something like this :
Code:
gcc dailog.c -o dailog `pkg-config --libs --cflags gtk+-2.0`



HTH

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 35 of 56 [830 Posts]   Goto page: Previous 1, 2, 3, ..., 33, 34, 35, 36, 37, ..., 54, 55, 56 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1997s ][ Queries: 13 (0.0229s) ][ GZIP on ]