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 Wed 19 Jun 2013, 08:46
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Quirky 1.3 feedback and bug reports
Moderators: Flash, Ian, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 3 of 4 Posts_count   Goto page: Previous 1, 2, 3, 4 Next
Author Message
upnorth


Joined: 11 Jan 2010
Posts: 262
Location: Wisconsin UTC-6 (-5 DST)

PostPosted: Wed 29 Sep 2010, 19:05    Post_subject: unsquash puppy.sfs then mksquashfs squashfs-root
Sub_title: unsquash puppy.sfs then mksquashfs squashfs-root puppy.sfs
 

when i unsquashed the puppy.sfs file, then resquashed, all from another running system, the file puppy.sfs is then no longer seen by the initrd during bootup. It drops out right away. Is there a trick to this for the new signature system?
Back to top
View user's profile Send_private_message Visit_website 
zygo

Joined: 08 Apr 2006
Posts: 208
Location: UK

PostPosted: Thu 30 Sep 2010, 12:09    Post_subject: Bug in Nathan wallpaper setter  

I want a certain image for the desktop wallpaper. It is not shown in the wallpaper setter. I shut it down then copy my image to the directory. I restart the wallpaper setter select my image and click view. Everything is fine until I click apply. The wallpaper does not change. I click view and the default wallpaper is now shown. I look in ROX and yes my file has been overwritten with the default -- only the name remains.
Back to top
View user's profile Send_private_message 
James C


Joined: 26 Mar 2009
Posts: 4768
Location: Kentucky

PostPosted: Fri 01 Oct 2010, 02:05    Post_subject:  

Still running on my test box......nothing wrong that hasn't been mentioned previously.Nice release. Smile
Back to top
View user's profile Send_private_message 
Michalis

Joined: 08 Jan 2008
Posts: 237
Location: Greece

PostPosted: Sat 02 Oct 2010, 09:39    Post_subject:  

There is a bug in puppy for long time, since puppy 4 at least and infects quirky also of course, which nobody could reproduce it and thous I thought that was some kind of my mistake. Accidentally I found what is causing it.

The bug is that I can't copy and paste from the terminal "rxvt" to Geany using the middle mouse key. When I try, it copies [null] and the reason is the language selected. If I select Greek (and I suppose any non western character language) it doesn't work, but when I select English it does copy paste fine.

Generally puppy has problems with foreign languages and it doesn't look nice. I hope to move to a more international puppy sometime.
Back to top
View user's profile Send_private_message 
mjaksen

Joined: 06 Jun 2008
Posts: 30

PostPosted: Sat 02 Oct 2010, 15:06    Post_subject:  

Quirky 1.30 shutdown without creating a save file. This happened twice.

Compaq Presario/R3000 (Athlon XP 3000+) Frugal install booted from hard disk via grub.

Shame because everything else worked nicely.
Back to top
View user's profile Send_private_message 
rcrsn51


Joined: 05 Sep 2006
Posts: 7833
Location: Stratford, Ontario

PostPosted: Sat 02 Oct 2010, 16:05    Post_subject:  

Quote:
Quirky 1.30 shutdown without creating a save file. This happened twice.

Try this: select Menu > Shutdown > Exit to Prompt
Then type: reboot
Back to top
View user's profile Send_private_message 
maddox

Joined: 28 Sep 2007
Posts: 453
Location: sometimes in France

PostPosted: Sun 03 Oct 2010, 22:28    Post_subject:  

Noticed In Quirky/Wary that pmount has an incorrect translation variable at lines 72 & 75-> $m_34 it should refer to m_31="KILL"
line 72-> m_35="If you press the \"$m_34\" button, Puppy will attempt to
kill the offending programs for you. Only do this as a
last resort. "
line 75-> m_36="Firstly you should try to close the programs
manually, so do not press \"$m_34\"."

pmount still contains 2 buttons that are not taken into account, lines 419-420, it's an easy fix
the OK variable is already present (m_38), just missing the CANCEL for it to be complete.
There are spare variable numbers 40-49, which i think pertain to the relevant part of the script,
so I added a new translation variable : m_40="CANCEL" #your choice of nber here
then changed lines 419-420 in pmount
<button ok></button> ... <button><input file stock=\"gtk-ok\"></input><label>$m_38</label></button>
<button cancel></button> ... <button><input file stock=\"gtk-cancel\"></input><label>$m_40</label></button>
Back to top
View user's profile Send_private_message 
Terryphi


Joined: 02 Jul 2008
Posts: 700
Location: West Wales, Britain.

PostPosted: Mon 04 Oct 2010, 02:19    Post_subject: Re: unsquash puppy.sfs then mksquashfs squashfs-root
Sub_title: unsquash puppy.sfs then mksquashfs squashfs-root puppy.sfs
 

upnorth wrote:
when i unsquashed the puppy.sfs file, then resquashed, all from another running system, the file puppy.sfs is then no longer seen by the initrd during bootup. It drops out right away. Is there a trick to this for the new signature system?


It is described in Barry's blog here:

http://bkhome.org/blog/?viewDetailed=01806

It appears it can only be done using the appropriate version of Puppy/Quirky. The necessary DISTRO_IDSTRING is read from /etc/DISTRO_SPECS .
Back to top
View user's profile Send_private_message Visit_website 
upnorth


Joined: 11 Jan 2010
Posts: 262
Location: Wisconsin UTC-6 (-5 DST)

PostPosted: Mon 04 Oct 2010, 12:25    Post_subject: echo -n "$DISTRO_IDSTRING" >> pup-431.sfs
Sub_title: /mnt/home/quirky>echo -n "q130100920100026" >> puppy.sfs
 

Very Happy Thanks!

Thats the part I missed:
eg
echo -n "$DISTRO_IDSTRING" >> pup-431.sfs

so I used from:
/mnt/home/quirky>

#echo -n "q130100920100026" >> puppy.sfs

and it booted Cool
Back to top
View user's profile Send_private_message Visit_website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6874
Location: Perth, Western Australia

PostPosted: Tue 05 Oct 2010, 05:46    Post_subject:  

tronkel wrote:
BarryK wrote:

Quote:
So, you would have got that 5 second pause before, but without the "pause" message.


This "pausing" message is displayed in red as a single word on my system. I have no nested Puppy folders on this system. So this message may well have existed within the start-up script for ages, but has never before appeared - maybe because it was never needed.

I'll have to eliminate the possibility of a bad ISO burn to CD. A gut-feeling tells me that this is a boot problem as such and may not necessarily related to the new method that has been implemented in order to search for Puppy files within nested folders. The MD5SUM for the ISO was OK.

I'll re-burn the ISO to CD using Puppy instead of Debian Squeeze this time and report back what I find.


I should put some extra info echo'ed to screen, that will show up if you boot with "loglevel=7" boot param -- well, perhaps that boot param will give you the info you seek anyway. What you need to know is what partition/drive is being attempted to mount and failing.

Ok, I have added extra echo statements in the init script to report failure to mount. The next Wary will have this, and if you boot with "loglevel=7" the message will appear on screen.

_________________
http://bkhome.org/blog2/
Back to top
View user's profile Send_private_message Visit_website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6874
Location: Perth, Western Australia

PostPosted: Tue 05 Oct 2010, 05:50    Post_subject:  

tronkel wrote:
The burner, which is also used to boot the live CD is an external USB device connected to the main PC via a USB hub.


The extra message isn't really needed. I know from my own experience with an external USB CD drive that you would have been getting the 5-sec pause before, but without the "pausing" message.

_________________
http://bkhome.org/blog2/
Back to top
View user's profile Send_private_message Visit_website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6874
Location: Perth, Western Australia

PostPosted: Tue 05 Oct 2010, 06:00    Post_subject: Re: unsquash puppy.sfs then mksquashfs squashfs-root
Sub_title: unsquash puppy.sfs then mksquashfs squashfs-root puppy.sfs
 

upnorth wrote:
when i unsquashed the puppy.sfs file, then resquashed, all from another running system, the file puppy.sfs is then no longer seen by the initrd during bootup. It drops out right away. Is there a trick to this for the new signature system?


After recreating puppy.sfs, do this:

echo -n 'w081100929084800' >> puppy.sfs

...or, whatever the id-string is in Quirky 1.3 (I'm running Wary right now)

The id-string is found in /etc/DISTRO_SPECS:

DISTRO_IDSTRING='w081100929084800'

This is only needed if the simplified filenames are chosen when building Puppy. For the next Wary I will use the traditional naming, so it will be 'wary_090.sfs' and will not need the id-string.

The 'init' script looks for the correct id-string on the end of puppy.sfs because there is no identification in its filename.


EDIT: I see some of the guys have already answered the question!

_________________
http://bkhome.org/blog2/

Edited_time_total
Back to top
View user's profile Send_private_message Visit_website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6874
Location: Perth, Western Australia

PostPosted: Tue 05 Oct 2010, 06:02    Post_subject: Re: unsquash puppy.sfs then mksquashfs squashfs-root
Sub_title: unsquash puppy.sfs then mksquashfs squashfs-root puppy.sfs
 

double post
_________________
http://bkhome.org/blog2/

Edited_time_total
Back to top
View user's profile Send_private_message Visit_website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 6874
Location: Perth, Western Australia

PostPosted: Tue 05 Oct 2010, 06:20    Post_subject:  

maddox wrote:
Noticed In Quirky/Wary that pmount has an incorrect translation variable at lines 72 & 75-> $m_34 it should refer to m_31="KILL"
line 72-> m_35="If you press the \"$m_34\" button, Puppy will attempt to
kill the offending programs for you. Only do this as a
last resort. "
line 75-> m_36="Firstly you should try to close the programs
manually, so do not press \"$m_34\"."

pmount still contains 2 buttons that are not taken into account, lines 419-420, it's an easy fix
the OK variable is already present (m_38), just missing the CANCEL for it to be complete.
There are spare variable numbers 40-49, which i think pertain to the relevant part of the script,
so I added a new translation variable : m_40="CANCEL" #your choice of nber here
then changed lines 419-420 in pmount
<button ok></button> ... <button><input file stock=\"gtk-ok\"></input><label>$m_38</label></button>
<button cancel></button> ... <button><input file stock=\"gtk-cancel\"></input><label>$m_40</label></button>


Thanks for that, I have fixed pmount.

_________________
http://bkhome.org/blog2/
Back to top
View user's profile Send_private_message Visit_website 
Proudog

Joined: 27 Feb 2009
Posts: 158

PostPosted: Sat 09 Oct 2010, 11:40    Post_subject: Bug in gtkdialog-yafsplash  

I found this little bug when a try /usr/sbin/filemnt. When yaf-splash is invoked with the parameter option -font "xxx" it's reported a "false" output, and not is screening the message.

Edited
Line error be changed in gtkdialog-splash:

Code:
#100917 if old yaf-splash installed, and '-font' param, execute old yaf-splash.

if [ -f /usr/X11R7/bin/yaf-splash ];then #100917
-  [ "`echo "$*" | grep ' \-font '`" != "" ] && exec /usr/X11R7/bin/yaf-splash $@ #BK
+ [ "`echo "$*" | grep '\-font'`" != "" ] && exec /usr/X11R7/bin/yaf-splash $@ #Bug-fix
fi


It's a simple sintaxis on spaces error.

Note: I like gtkdialog yaf-splash, is a UTF-8 complaint.
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 3 of 4 Posts_count   Goto page: Previous 1, 2, 3, 4 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


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