the
>> mapfile change.
>
> Yes, I have installed 3.1.4 from sid and it fixes the bug. Thank you
> for taking care of this.
I can confirm this also resolves my problem with mdadm spinning forever.
Thank you all,
Daniel
--
✣ Daniel Pittman✉ dan...@rimspace.
Eduard Bloch writes:
> * Daniel Pittman [Thu, Aug 19 2010, 06:28:01PM]:
>> Eduard Bloch writes:
G'day Eduard. Sorry for the long delay in responding to this bug report, and
your changes. I regret holding up so long on that.
[...]
>> > I found a couple of issues which
a (malloc, mmap) rw- 1019932
RO data r-- 0
Unreadable--- 131352
Unknown0
I attached the code for proc-maps, but it basically just sums memory
allocations. On the same hunch /proc/.../maps and /proc/.../smaps are bot
ities
Versions of packages udev recommends:
ii pciutils 1:3.1.4-1 Linux PCI Utilities
ii usbutils 0.86-2 Linux USB utilities
udev suggests no packages.
-- debconf information:
udev/new_kernel_needed: false
udev/reboot_needed:
--
✣ Daniel Pitt
Timo Sirainen writes:
> On Sep 15, 2009, at 9:10 AM, Daniel Pittman wrote:
>
>> Sep 15 16:03:31 krosp IMAP(daniel): : Fatal: io_loop_handle_add:
>> epoll_ctl(1, 0): Operation not permitted
Sorry to take so long to follow up on this.
> Do you have rawlog enabled? IIRC that
ries
ii libssl0.9.8 0.9.8k-5 SSL shared libraries
dovecot-imapd recommends no packages.
dovecot-imapd suggests no packages.
-- no debconf information
--
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
♽ made with 100 percent pos
ries
ii libssl0.9.8 0.9.8k-5 SSL shared libraries
dovecot-imapd recommends no packages.
dovecot-imapd suggests no packages.
-- no debconf information
--
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
♽ made with 100 percent pos
Sven Joachim writes:
> On 2009-08-22 03:06 +0200, Daniel Pittman wrote:
>
>> Package: nvidia-kernel-source
>> Version: 185.18.31-1
>> Severity: grave
>>
>> After upgrading to the 185.18.31 packages from 185.18.14, X caused a kernel
>> panic with a NULL
8.14-2 NVIDIA binary Xorg driver
nvidia-kernel-source suggests no packages.
-- no debconf information
--
✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
Looking for work? Love Perl? In Melbourne
Package: libplist-utils
Version: 0.12-1
Severity: grave
Justification: renders package unusable
libplist-utils ships /usr/bin/plist as a symbolic link, but not the actual
binary:
] ls -l /usr/bin/plutil*
lrwxrwxrwx 1 root root 11 2009-05-31 16:22 /usr/bin/plutil -> plutil-0.12
It should probabl
Package: libpar-packer-perl
Version: 0.982-2
Severity: grave
File: /usr/bin/pp
Justification: renders package unusable
G'day.
After y'all resolved #451600 by renaming /usr/bin/par.pl to /usr/bin/par-archive
the pp process for generating stand-alone Perl scripts is broken:
] pp -P -e '1;'
Can't o
Ola Lundqvist writes:
> If you could try this fix out it would be really great.
> A built package for amd64 is available at:
> http://apt.inguza.org/vzctl/
Ah. I am on amd64, and that is an i386 package without source.
Anyway, I grabbed the source, manually applied the patch and downgraded
the
Kir Kolyshkin writes:
> This is caused by newer kernel headers (in this case on a build system
> that was used to build this vzctl package), and is fixed in
> vzctl-3.0.23. See the following git commit:
vzctl 3.0.23-2 is available in experimental, so I have installed it and
tested it on my machi
Package: vzctl
Version: 3.0.22-14
Severity: grave
Justification: renders package unusable
When trying to start a VE I get the following output:
] sudo vzctl start sd-dev
Starting VE ...
VE is mounted
Unable to set capability: Operation not permitted
Unable to set capability
VE start failed
VE is
Package: subversion
Version: 1.2.3dfsg1-3
Severity: grave
G'day.
I have run into a problem where I can't commit a change to my subversion
repository via HTTP/SSL.
The problem seems identical to the one described in this bug report, but
my issues continue despite running the version that claims t
Package: squid
Version: 2.5.9-4
Severity: serious
This applies to 2.5.9-5 - I downgraded to be able to check for duplicate
bug reports.
I get this assertion failure, and abort:
assertion failed: store_swapout.c:232: "mem->inmem_lo == 0"
Regards,
Daniel
-- System Information:
Debian Rel
Package: squid
Version: 2.5.9-2
Severity: grave
After upgrading to 2.5.9-3, squid would routinely fail with this
assertion:
2005/04/02 12:01:48| assertion failed: stmem.c:93: "current_offset ==
target_offset"
The process seemed to restart automatically, and perform an DIRTY cache
rebuild.
I ha
17 matches
Mail list logo
