I've encountered the same problem on Gentoo[1] with an Officejet 5610.
Using the old hpijs (foomatic) PPD works fine, but the new hpcups PPD has
broken margins. I will paste the important differences in the PPDs:
# hplip-3.9.4b-r1:
CustomMedia "A4/A4 210x297mm" 595.00 842.00 10.00 36.00 10.00 9.0
Public bug reported:
Binary package hint: update-manager
Running do-release-upgrade on latest 9.04 / Jaunty within a Linux-Vserver Guest
yields:
(see attachment for full log)
$ do-release-upgrade -m server -d
...
Preparing to replace upstart 0.3.9-8 (using .../upstart_0.6.3-10_amd64.deb) ...
Un
Output on terminal
** Attachment added: "do-release-upgrade.txt"
http://launchpadlibrarian.net/33906654/do-release-upgrade.txt
--
Setting up upstart within linux-vserver fails if telinit is not running
https://bugs.launchpad.net/bugs/454783
You received this bug notification because you are a
** Attachment added: "apt-term.log"
http://launchpadlibrarian.net/33906680/apt-term.log
--
Setting up upstart within linux-vserver fails if telinit is not running
https://bugs.launchpad.net/bugs/454783
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "apt.log"
http://launchpadlibrarian.net/33906664/apt.log
--
Setting up upstart within linux-vserver fails if telinit is not running
https://bugs.launchpad.net/bugs/454783
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "main.log"
http://launchpadlibrarian.net/33906687/main.log
--
Setting up upstart within linux-vserver fails if telinit is not running
https://bugs.launchpad.net/bugs/454783
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm this, but reported upstream instead:
Issue 64449: Unable to use font family Terminus for fixed-width font
http://code.google.com/p/chromium/issues/detail?id=64449
** Bug watch added: code.google.com/p/chromium/issues #64449
http://code.google.com/p/chromium/issues/detail?id=6444
File "/tmp/tmp3Pqofq/DistUpgradeController.py", line 206, in _sshMagic
"-p",str(port)])
def _sshMagic(self):
""" this will check for server mode and if we run over ssh.
if this is the case, we will ask and spawn a additional
daemon (to be sure we have a spare on
Public bug reported:
Binary package hint: update-manager-core
Problems upgrading Ubuntu Server 8.04.1 to 8.10:
The release upgrade helper "do-release-upgrade" shipped with upgrade-
manager-core on an Ubuntu 8.04.1 Server tries to start an additional ssh
daemon if run in server mode and if it can
Actually it is "fixed" with recent Linux-VServer + 2.6.26+ versions. I
still don't see this as a vserver bug. The bug is in NPTL / glibc, as
stated above and described in the official documentation. There were
lots of changes to clone(2) and the namespace handling in between
vanilla kernel 2.6.19 a
Scott, this is not my problem and well known. In fact, as you can see in
[4] of the original post, I did all that and it didn't help. I invested
some time and finally found the exact problem.
Anyone who is still encountering this (which is likely with the current
stable vserver patch which hasn't
** Attachment added: "init.c"
http://launchpadlibrarian.net/35729710/init.c
--
upstart incompatible with linux-vserver
https://bugs.launchpad.net/bugs/482292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
And for the record, getpid(2) caching is bad! See
http://lkml.org/lkml/2004/6/5/88
--
upstart incompatible with linux-vserver
https://bugs.launchpad.net/bugs/482292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This fix allows upstart's /sbin/init to obtain the real PID in any case,
not the cached one.
** Attachment added: "Proposed fix"
http://launchpadlibrarian.net/35731565/fix-upstart-vserver-compatibility.patch
--
upstart incompatible with linux-vserver
https://bugs.launchpad.net/bugs/482292
Yo
Yes, I can confirm it's fixed in MySQL 5.1.37 shipped with Ubuntu
Karmic. The fix should be backported to Jaunty, though.
--
MySQL 5.1 optimizer not using index
https://bugs.launchpad.net/bugs/482121
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
Binary package hint: dbmail
Using current DBMail (2.2.11 as packaged or 2.2.13 from upstream) with
the current MySQL server version (5.1) shipped with Ubuntu is unusable.
The MySQL server does not use the index and falls back to a full table
scan. This is a regression between
Thanks to Harald Reindl who pointed this exact problem out upstream:
http://bugs.mysql.com/bug.php?id=46508
The bug is fixed in mysql-server version 5.1.37, which is shipped with new
Ubuntu Karmic.
Ubuntu Jaunty users will have to backport it or upgrade.
** Bug watch added: MySQL Bug System #46
** Attachment added: "do-release-upgrade.log"
http://launchpadlibrarian.net/35661404/do-release-upgrade.log
--
upstart incompatible with linux-vserver
https://bugs.launchpad.net/bugs/482292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
Binary package hint: upstart
I'm using Ubuntu guest systems with Linux-VServer[1] since Edgy Eft / 6.10.
The last few upgrades worked out well (well, with some hassles here and
there...) using:
do-release-upgrade -m server
However, this is not the case with the current up
19 matches
Mail list logo
