Public bug reported:
Binary package hint: python2.6
The python2.6-doc package has a symlink to jquery.js which points to the
wrong place.
The symlink is made to be to
../../../../javacript/jquery.js
instead of
../../../../javacript/jquery/jquery.js
** Affects: python2.6 (Ubuntu)
Importance
A kludgey fix is to have in /etc/e2fsck.conf something like:
[options]
buggy_init_scripts = 1
The trigger for this seems to be an incomplete/faulty restore of the syetm
time from the hardware clock before running the fsck -a. To the best I can
see, hwclock is not being set/corrected at all befor
same thing is happening to me too. Current kramic builds no longer turn off the
LCD screen using dpms. "xset q" shows dpms enabled, but all the timeouts set to
0.
My xorg.conf settings seem to be ignored:
Section "ServerFlags"
Option "BlankTime" "5"
Option "StandbyTime" "10"
The fsck failure is caused by the superblock's last mount time being
into the future. The message printed is fsck repeatedly complaining that
each of my 3 partitions has that last mount time in the future. I'm in a
GMT-04 timezone, and the time difference being printed by fsk is exactly
those 4 hou
Public bug reported:
if there is a failure in fsck, the new upstrat-based mountall will loop
(almost) indefinitely trying to mount/check partitions that keep on
failing. Eventually the script dies with some erros that would result in
a "Give the root password prompt", but I had that happen only af
related: #422869
--
Superblock last mount times cause fsck to fail
https://bugs.launchpad.net/bugs/423247
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
When the hardware clock is stored in UTC, the issue is of particular
visibility to those living in GMT-hh timezones and whose system clocks
"go back" in time on every boot until they're re-adjusted from the
hardware clock.
--
fsck halts bootup when checked file has timestamp in the future from ot
I am also getting this on my karmic upgrade from jaunty. I am running
with UTC=yes in my rcS. The problem in my case seems to arise from the
fact that the init scripts do not restore the system clock from the
hardware clock before launching into fsck.
I had to put the following into my /etc/init/m
looks like the latest batch of updates fixed this issue for me...
** Changed in: gutenprint (Ubuntu)
Status: New => Invalid
--
Printing test page on a Generic PCL5/PCL5c/PCL5e printer fails
https://bugs.launchpad.net/bugs/352545
You received this bug notification because you are a member
Public bug reported:
Binary package hint: foomatic-db-gutenprint
After upgrading to jaunty beta and installing all the latest updates
available as of today, I can no longer print on my Generic PCL 5e
printer. When I select to print a test page, a document is sent to the
printer, but the printout
10 matches
Mail list logo
