Package: snmpd
Version: 5.4.1~dfsg-8.1
Severity: grave
Justification: renders package unusable
Since upgrading from etch (stable) to testing, snmpd is reporting this in
syslog:
Sep 30 06:25:22 quark snmpd[4507]: netsnmp_assert rc == 0 failed
if-mib/ifTable/ifTable_data_access.c:210 _check_interf
I confirm that 46.4 fixes the bug.
It seems that the /var/cache/apt/*.bin files are regenerated when
invalid ones are found.
Many thanks!
Jan Evert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Margarita,
Margarita Manterola wrote:
On 12/5/06, Jan Evert van Grootheest <[EMAIL PROTECTED]>
wrote:
I am getting upset now
Apt-get is again segfaulting!
Yesterday I removed the *.bin files from /var/cache/apt. Then ran
apt-get update, apt-get -V upgrade and apt-get clean.
Now I
I am getting upset now
Apt-get is again segfaulting!
Yesterday I removed the *.bin files from /var/cache/apt. Then ran
apt-get update, apt-get -V upgrade and apt-get clean.
Now I do apt-get update and it segfaults again!!!
Grmbl.
-- Jan Evert
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
Hi,
After reading comments of Gordon and Florian, I also tried removing the
*.bin files from /var/cache/apt/.
Apt-get now works again.
At first I thought that Gordons issue and mine were different due to the
totally different backtraces.
However, now that the same action fixes it, it might be
By the way, I also have an amd64 system (running the amd64 arch) that
doesn't show this problem!
(with apt 0.6.42.6)
-- Jan Evert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I've installed the newer 46.3 version and it also crashes.
However the backtrace is a bit more readable:
(gdb) bt
#0 0xb7d3b2f3 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7ebe316 in std::string::compare () from /usr/lib/libstdc++.so.6
#2 0xb7fb35d1 in debPackagesIndex::FindInCache ()
Package: apt
Version: 0.6.46.2
Severity: grave
Justification: renders package unusable
Whenever I do something with apt-get, it segfaults. Specifically, it
seems that it crashes
when reading package lists. For example, 'update' fetches all files and
displays the 'Fetched...'
line and it also di
Stephen Frost wrote:
* Stephen Frost ([EMAIL PROTECTED]) wrote:
Right, with the defaults... The idea was to reduce those. I've played
with this some in preparation of 251-6. Try:
reconn_maxconntries = 2
reconn_tries = 1
reconn_sleeptime = 1
reconn_maxsleeptime = 8
I guess I could ha
Stephen Frost wrote:
* Steinar H. Gunderson ([EMAIL PROTECTED]) wrote:
On Tue, Oct 03, 2006 at 11:28:34PM -0700, Steve Langasek wrote:
Can we just fix libnss-ldap already to use a sensible default bind policy,
please?
Sure, I could do that (removing the boot-time workarounds), a
Jan Evert van Grootheest wrote:
Rene,
Jan Evert van Grootheest wrote:
Rene,
[...]
read-only (the title-bar shows this and I can't make changes). I can,
however, create and modify files in that same directory using touch and
vi.
And? What are the permissions or the dir and file? Is
Rene,
Jan Evert van Grootheest wrote:
Rene,
[...]
read-only (the title-bar shows this and I can't make changes). I can,
however, create and modify files in that same directory using touch and
vi.
And? What are the permissions or the dir and file? Is it on some nfs
thing
without lo
Rene,
Rene Engelhard wrote:
Am Montag, 9. Oktober 2006 13:52 schrieb Jan Evert van Grootheest:
When I open a document that should be writable, the document is opened
Why do you think so?
Because the day before the update I created that document. Using OOo.
I've never had problems like
Package: openoffice.org
Version: 2.0.4~rc3-1
Severity: grave
Justification: renders package unusable
When I close a read-only document, OOo simply freezes. The window is no
longer updated.
I don't know why the document is readonly (I created another bug for
that, but in hindsight, all problems see
Package: openoffice.org
Version: 2.0.4~rc3-1
Severity: grave
Justification: renders package unusable
When I open a document that should be writable, the document is opened
read-only (the title-bar shows this and I can't make changes). I can,
however, create and modify files in that same directory
Steve,
Steve Langasek wrote:
On Wed, Oct 04, 2006 at 02:14:13AM +0200, Steinar H. Gunderson wrote:
The first one is that it attempts to touch a file in a directory that
does not exist. /etc/init.d/libnss-ldap needs /lib/init/rw to exist but
does not make sure.
Simple fix is to create the dir ma
Package: libnss-ldap
Version: 251-5.2
Severity: critical
Justification: breaks the whole system
This version of libnss-ldap attempts to do something about the issue
that the ldap server might be unreachable due to not-yet started
services. (i.e. bind-policy soft)
Well. There are two simple techn
17 matches
Mail list logo
