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 23 Apr 2014, 21:17
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Precise Puppy 5.6.1-final, May 29, 2013
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 16 of 19 [274 Posts]   Goto page: Previous 1, 2, 3, ..., 14, 15, 16, 17, 18, 19 Next
Author Message
Sylvander

Joined: 15 Dec 2008
Posts: 3263
Location: West Lothian, Scotland, UK

PostPosted: Tue 11 Jun 2013, 14:26    Post subject:  

Installed Psync-2.9.
Seems to be working OK.
How should I test it?
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 854

PostPosted: Tue 11 Jun 2013, 15:10    Post subject: Re: Recent versions of hwclock are incompatible with . . .  

Sylvander wrote:
How should I test it?

1. Run this command and verify that the output is "HWCLOCKTIME=localtime":
Code:
grep "^HWCLOCKTIME" /etc/clock

2. Run this command:
Code:
rm /etc/adjtime

3. Run Psync and synchronise your clock.

4. Run this command and verify that the output is "LOCAL":
Code:
tail -1 /etc/adjtime

If this test was run using Psync 2.8 on a recent Puppy, the output would be "UTC", which is wrong, and would cause the time problem you reported earlier.
Back to top
View user's profile Send private message 
Sylvander

Joined: 15 Dec 2008
Posts: 3263
Location: West Lothian, Scotland, UK

PostPosted: Tue 11 Jun 2013, 15:15    Post subject:  

Completed items 1 through 4, and here's the results:
Code:
# grep "^HWCLOCKTIME" /etc/clock
HWCLOCKTIME=localtime
# rm /etc/adjtime
# tail -1 /etc/adjtime
LOCAL
#

All seems well to me. Very Happy
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 854

PostPosted: Tue 11 Jun 2013, 15:22    Post subject: Re: Recent versions of hwclock are incompatible with . . .  

Great! Thanks for testing.
Back to top
View user's profile Send private message 
watchdog

Joined: 28 Sep 2012
Posts: 434

PostPosted: Wed 12 Jun 2013, 05:17    Post subject: Scanned doc in 5.6.1 and internet fax  

Scanned documents (pdf, jpeg in doc files,...) are not accepted in upload by my internet fax service. The same procedure has success in slacko 5.5. The error in precise is something of the kind "file empty (but it's not empty and I can open it with epdfview) or wrong MIME type".

EDIT: solved by:

Code:
update-mime-database /usr/share/mime
Back to top
View user's profile Send private message 
npierce

Joined: 28 Dec 2009
Posts: 854

PostPosted: Thu 13 Jun 2013, 22:03    Post subject: Drive icons may pile up when displayed at right edge.
Subject description: This happens on 1366x768 screen when ROX grid step is Medium or Coarse.
 

In 2009, shinobar solved a problem which caused the drive icons to pile up on top of each other at certain screen resolutions, such as 800x600, if ROX-Filer's grid step is set to Medium or Coarse. At that time drive icons were always displayed along the bottom edge of the pinboard.

Now drive icons may be displayed along any edge of the pinboard, and recently Ghost Dog ran into a problem when displaying icons along the right edge. (See forum thread: Drive Icons All Bunched Up In The Corner.)

Ghost Dog has since verified that the resolution of the screen that exhibited this problem was 1366x768. This indicated that the problem was similar to the problem shinobar solved for drive icons along the bottom at 800x600.

The problem happens only when the screen width is not an exact multiple of ROX-FIler's grid step (just like the 2009 problem only happened when the screen height was not an exact multiple of the grid step). For more details, see my attempt at an explanation posted here: http://www.murga-linux.com/puppy/viewtopic.php?p=705520#705520

After Ghost Dog verified that this problem occurred on a 1366x768 screen, I was able to borrow a PC that supported that resolution and so test my theory. Now I have a suggested fix.

Actually, I am attaching four versions of pup_event_frontend_d that correct this problem. One is based on the single-script version of pup_event_frontend_d, as included with recent Puppies. But Barry has been busy and developed a new and improved modular version for use in future Puppies. So I also ported my changes to the appropriate modules of that version. Those two versions contain the fix (based on shinobar's code) as well as some other minor improvements (inspired partly by other contributors to the above thread). Then I decided to make a version of each of those which have just the minimal changes needed to fix the problem, without the minor improvements.


Attached are four versions of the daemon:

1. Drop-in replacement for Precise 5.5, 5.6, 5.6.1, Slacko 5.5, Racy 5.5.
Minimal changes.

2. Drop-in replacement for Precise 5.5, 5.6, 5.6.1, Slacko 5.5, Racy 5.5.
Some of the math moved out of free_coord().

3. Based on current Woof.
Minimal changes.

4. Based on current Woof.
Some of the math moved out of free_coord().

In #1 and #3 I simply added a few lines so that the X coordinates receive the same correction that the Y coordinates have received since shinobar fixed them in 2009.

In #2 and #4 I have added that correction but moved it and much of the related math out of the free_coord() function. This was inspired by posts from Karl Godt and MinHundHettePerro, both of whom pinpointed the problem, and suggested code to fix it which also moved needlessly repetitive code out of the function so that it wasn't repeated for every icon.

Among the stuff moved in #2 and #4, was the code that reads ROX-Filer's Options file. At first I wondered if that might be a bad thing since this daemon would no longer be aware of changes to "pinboard_grid_step", unless it was restarted. Looking closer I realised that this wasn't really a problem because it doesn't really matter if the daemon is aware of changes to "pinboard_grid_step" or not, since after that value is changed, correct icon placement cannot be guaranteed until the daemon is restarted (usually by restarting the X server).

Although there is no guarantee that icons will be placed correctly if "pinboard_grid_step" is changed unless this daemon is restarted, in most cases they will be placed properly. The only time they won't be is when the user wants the icons along the bottom edge of the pinboard (the default) and has a screen resolution with a height which isn't an exact multiple of 32, such as 800x600, or when the user wants the icons along the right edge of the pinboard and has a screen resolution with a width which isn't an exact multiple of 32, such as 1366x768.

In other words, since the daemon should be restarted anyway after changing "pinboard_grid_step" by any user who uses one of the screen resolutions just mentioned, the behavior that occurs if the daemon isn't restarted isn't really worth describing.

But I like to be complete, so will do so anyway. Feel free to skip this part.


(-- Start of exceedingly boring stuff --)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(The "pinboard_grid_step" values that I mention below are limited to the three values available through the ROX-Filer Options menu: 2 (Fine), 16 (Medium), and 32 (Coarse).)

Current daemon:
    Height not a multiple of 32, and icons along bottom edge:

      After changing "pinboard_grid_step", plugging in a new drive may cause its icon to appear on top of preexisting drive icons, but not on top of icons for other drives added since the grid step was changed.

    Width not a multiple of 32, and icons along right edge:

      This doesn't work at all with current daemon if grid step is changed from "fine" (the default) -- even if the daemon is restarted.

    Any other combination:

      Icons will be displayed correctly.


Daemons #1 or #3 above:

    Height not a multiple of 32, and icons along bottom edge, or width not a multiple of 32 and icons along right edge:

      After changing "pinboard_grid_step", plugging in a new drive may cause its icon to appear on top of preexisting drive icons, but not on top of icons for other drives added since the grid step was changed.

    Any other combination:

      Icons will be displayed correctly.


Daemons #2 or #4 above:
    Height not a multiple of 32, and icons along bottom edge, or width not a multiple of 32 and icons along right edge:

      After changing "pinboard_grid_step" to a larger value than it was when this daemon was started, plugging in a new drive may cause its icon to appear on top of other new drives that were added since the grid step was changed, but not on top of preexisting drive icons.

      After changing "pinboard_grid_step" to a smaller value than it was when this daemon was started, plugging in a new drive will cause its icon to be displayed correctly.

    Any other combination:

      Icons will be displayed correctly.


Again, it is important to remember that the above describes what could happen only if the daemon is not restarted after the grid step is changed. If it is restarted, daemons #1, #2, #3, and #4 will display the icons correctly in all cases, and the current daemon will also display the icons correctly in all cases except the one case where icons are on the right and the screen width is not a multiple of 32.

(Actually, I should point out that a screen height or width that is not a multiple of 32, but is a multiple of 16 will always work correctly with a grid step of 16 (Medium). But I have lumped 16 together with 32 in the above description because life is too short to spend trying to describe each possible case. Suffice it to say that in some cases above which cause incorrect icon placement when the grid step is 32, there would not be a problem with a grid step of 16, if the appropriate screen dimension was a multiple of 16. Note that neither height at 800x600, nor the width at 1366x768 is a multiple of 32 or 16, so in those cases it is appropriate to lump 32 and 16 together.)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(-- End of exceedingly boring stuff --)

(Resumption of moderately boring stuff. Smile )


In my #4 daemon, free_coord() SCRN_X and SCRN_Y are no longer used. They are still used in frontend_startup, but the only function currently using them is the first, unused definition of free_coord. If that unused definition was eliminated, there would probably no longer be a need to pass SCRN_X and SCRN_Y to the other scripts. But I've not tested that, so have left that as-is for now.

By the way, in the current Woof version, I noticed that frontend_change didn't source gettext.sh (needed for call to create_icon_func() ), so I've added that and defined TEXTDOMAIN and OUTPUT_CHARSET.

Please note that in the .tar.gz for the modular version, #3 and #4 below, I've only included the modules that I changed. The other modules are also needed for it to run (see Barry's blog: new pup_event_frontend).
pup_event_frontend_d_1_onescript_min.tar.gz
Description  Single script, minimal changes
gz

 Download 
Filename  pup_event_frontend_d_1_onescript_min.tar.gz 
Filesize  10.3 KB 
Downloaded  140 Time(s) 
pup_event_frontend_d_2_onescript.tar.gz
Description  Single script, repetitive code moved out of free_coord()
gz

 Download 
Filename  pup_event_frontend_d_2_onescript.tar.gz 
Filesize  10.48 KB 
Downloaded  142 Time(s) 
pup_event_frontend_d_3_modular_min.tar.gz
Description  Modular, minimal changes
gz

 Download 
Filename  pup_event_frontend_d_3_modular_min.tar.gz 
Filesize  8.16 KB 
Downloaded  147 Time(s) 
pup_event_frontend_d_4_modular.tar.gz
Description  Modular, repetitive code moved out of free_coord()
gz

 Download 
Filename  pup_event_frontend_d_4_modular.tar.gz 
Filesize  11.15 KB 
Downloaded  139 Time(s) 
Back to top
View user's profile Send private message 
BarryK
Puppy Master


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

PostPosted: Sat 15 Jun 2013, 05:49    Post subject:  

npierce,
That's great, thanks for the in-depth analysis and solution.

Note, pup_event is currently under development in Woof, and the files are changing. The "modular" tarballs that npierce posted above are no longer applicable -- that is, they are modifications of older scripts, not the latest in Woof.

I have gone for no.3, as it is the simplest, and implemented it in Woof.

I will upload Woof tonight, also Raring Puppy (built from Ubuntu 13.04 DEBs) with all the latest goodies.

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
npierce

Joined: 28 Dec 2009
Posts: 854

PostPosted: Sat 15 Jun 2013, 07:03    Post subject:  

Barry,

You're welcome. Thanks for implementing this.
Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 1936
Location: Ontario Canada

PostPosted: Sat 15 Jun 2013, 15:33    Post subject:  

BarryK wrote:


I will upload Woof tonight, also Raring Puppy (built from Ubuntu 13.04 DEBs) with all the latest goodies.


Will you be starting a thread for feedback?

Last edited by Billtoo on Mon 17 Jun 2013, 07:20; edited 3 times in total
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 4767
Location: GB

PostPosted: Sun 16 Jun 2013, 04:48    Post subject:  

You did better than me, Bill. Can't get any picture by any method, any driver [XP@3000/1Mb/Radeon7000-64]. This is particularly annoying because the 'Test now' always gives 'OK' whether I use 'unaccelerated', 'Radeon' or 'let it choose'. Sometimes can get back to a prompt but it doesn't help; sometimes just a flashing cursor.
Seem to remember issues with Rarin' previously. One step forward, two steps back is the strategy at Canonical?!

Later: stuck an nV MX440/128n card in. Interesting; picture came up at correct resolution then straightaway returned me to a prompt. Selected nouveau driver and came up with the wrong resolution! Unable to select another. Got the same PPM=prompt feature as Bill, supra.

This one has a very long way to go. Get the feeling that BK's skills would be best deployed on honing Precise, Wary and Racy - possibly ARMs ?
Back to top
View user's profile Send private message 
anikin

Joined: 10 May 2012
Posts: 395

PostPosted: Sun 16 Jun 2013, 06:56    Post subject:  

Moving this post to the Raring-5692 thread.

My apologies.

Last edited by anikin on Mon 17 Jun 2013, 12:19; edited 1 time in total
Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 1936
Location: Ontario Canada

PostPosted: Sun 16 Jun 2013, 07:59    Post subject:  

. message offtopic - removed
Last edited by Billtoo on Mon 17 Jun 2013, 07:22; edited 2 times in total
Back to top
View user's profile Send private message 
OscarTalks

Joined: 05 Feb 2012
Posts: 753
Location: London, England

PostPosted: Sun 16 Jun 2013, 08:01    Post subject:  

I have moved this message to the new Raring Puppy 5.6.92 thread here:-

http://www.murga-linux.com/puppy/viewtopic.php?t=86776

Apologies for any inconvenience.

_________________
Oscar in England


Last edited by OscarTalks on Mon 17 Jun 2013, 10:49; edited 1 time in total
Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 1936
Location: Ontario Canada

PostPosted: Sun 16 Jun 2013, 23:07    Post subject:  

message offtopic - removed
Last edited by Billtoo on Mon 17 Jun 2013, 07:23; edited 1 time in total
Back to top
View user's profile Send private message 
Jasper


Joined: 25 Apr 2010
Posts: 1034
Location: England

PostPosted: Mon 17 Jun 2013, 06:54    Post subject:  

Though on 15th June 2013, on page 16 above, BarryK wrote
Quote:
I will upload Woof tonight, also Raring Puppy (built from
Ubuntu 13.04 DEBs) with all the latest goodies.

this is still a Precise Puppy thread - so it seems wholly inappropriate to post Raring comments here?
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 16 of 19 [274 Posts]   Goto page: Previous 1, 2, 3, ..., 14, 15, 16, 17, 18, 19 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.1419s ][ Queries: 13 (0.0558s) ][ GZIP on ]