On 3/1/11 2:19 PM, Maria Mckinley wrote:
On 3/1/11 10:44 AM, Maria Mckinley wrote:
I am having this problem after upgrading from Lenny to Squeeze. It is
stuck on this screen for a few minutes, and then goes into some strange
state where the screen is not getting a signal, but the machine
I am having this problem after upgrading from Lenny to Squeeze. It is
stuck on this screen for a few minutes, and then goes into some strange
state where the screen is not getting a signal, but the machine appears
to be doing something, and I have to reset the power to get it to
reboot. I can
On 3/1/11 10:44 AM, Maria Mckinley wrote:
I am having this problem after upgrading from Lenny to Squeeze. It is
stuck on this screen for a few minutes, and then goes into some strange
state where the screen is not getting a signal, but the machine appears
to be doing something, and I have
for the bug you reported.
On Mon, Nov 16, 2009 at 04:00:53PM -0800, Maria McKinley wrote:
When a user tries to make any changes to filters from the squirrelmail
filters interface, then he/she gets the following sorts of errors
(depending on what changes he/she is trying to make):
Warning: Cannot modify
Jan Hauke Rahm wrote:
Hi Maria,
thanks for your report. It seems you've found reportbug quite usefull,
huh? :)
On Thu, Nov 12, 2009 at 02:27:47PM -0800, Maria Mckinley wrote:
When a user tries to make any changes to filters from the squirrelmail
filters interface, then he/she gets
Package: avelsieve
Version: 1.9.7-6+lenny1
Severity: normal
When a user tries to make any changes to filters from the squirrelmail filters
interface, then he/she gets the following sorts of errors (depending on what
changes he/she is trying to make):
Warning: Cannot modify header information -
I am having a similar problem, and portmap 6.0-9 does not solve my
problem either. On my setup, rpc.statd does not start because portmap
does not start, so my nfs mounts do not happen. I end up booting with
the read only file system mounted by initrd. I did also try adding
ASYNCMOUNTNFS=no to
Oops, hit send too soon. I was able to get portmap working using the
older version (etch portmap 5-26), but statd still did not start up. It
complains that: Opening /var/run/rpc.statd.pid failed: Read-only file
system. Which seems crazy, as the whole point of this is to have /
mounted over
I am having a similar problem, and portmap 6.0-9 does not solve my
problem either. On my setup, rpc.statd does not start because portmap
does not start, so my nfs mounts do not happen. I end up booting with
the read only file system mounted by initrd. I did also try adding
ASYNCMOUNTNFS=no to
9 matches
Mail list logo
