[Bug 29622] Re: Many web browsers not print the headers and footers.

2007-06-07 Thread John Willauer
Firefox 2.0.0.4, when run under Ubuntu Fisty 7.04 would print two almost
blank pages for each page printed.  Both almost blank pages had a thin
line of dots at the top of each page, which later appeared to be
attempts to print the page's header and footer.

Firefox has two sets of margin adjustments, one for the page and another
for the sheet to be printed.

It appears that the default margin information Firefox sends to CUPS is
wrong.

To print both a pages header and footer properly on my HP PSC-2175 I had
to set the page and sheet margins as follows:

 File  Print Setup  Margins  Headers/Footers
  Top: 0.5  Left: 0.5  Right: 0.8  Bottom: 0.8

 File  Print  Properties
  Top: 0.25  Bottom: 0.5  Left: 0.25  Right: 0.5

-- 
Many web browsers not print the headers and footers.
https://bugs.launchpad.net/bugs/29622
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for epiphany-browser in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 82992] sbackup lock not stored in /var/lock

2007-03-07 Thread John Willauer
Public bug reported:

Binary package hint: sbackup

When I run sbackup it would not execute for several days.

After setting up cron to send me e-mail when executed, received e-mail
stating Another Simple Backup daemon already running: exiting

I found an form posting for this message at:
http://www.ubuntuforums.org/archive/index.php/t-220996.html

The forum posting reported that ...problem was caused by a lock file
left over in /root.

After examining the sbackup source code, I discovered that this poblem
was caused by the location of the lock being redefined.  In sbackupd
lockfile is initialized to point to /var/lock/sbackup.lock.  Loading
the sbackup config file resets lockfile to point to the current
default directory by not explicitly pointing to /var/lock/sbackup.lock.

Thus when sbackupd is executed by root the current directory is /root,
thus the lock is set in /root.

** Affects: sbackup (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Desktop Bugs
 Status: Confirmed

-- 
sbackup lock not stored in /var/lock
https://launchpad.net/bugs/82992

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs