Your message dated Thu, 12 Jan 2012 16:56:30 +0100
with message-id <[email protected]>
and subject line close #640247
has caused the Debian Bug report #640247,
regarding jed: Fails to start correctly (gdbm-module.so not found)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
640247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640247
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: jed
Version: 1:0.99.19-2
Severity: important
After libslang2 got upgraded from 2.2.4-2 to 2.2.4-3, jed stopped
working (properly): upon start (even without ~/.jedrc), it shows the
error message
Error linking to gdbm-module.so: gdbm-module.so: cannot open shared
object file: No such file or directory
and leaves the user in some very basic, (for me) unusable mode (^Ke:
quit, ^Kg: get file, ^K^W: write file).
Downgrading to 2.2.4-2 makes jed work again.
There is a notable difference in available libraries (and their
paths!) between of the two libslang2 versions that might be the cause
of jed tripping:
$ ldconfig -p | grep slang
Version 2.2.4-2:
libslang.so.2 (libc6,x86-64) => /lib/libslang.so.2
Version 2.2.4-3:
libslang.so.2 (libc6,x86-64) => /lib/x86_64-linux-gnu/libslang.so.2
libslang.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libslang.so
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'unstable'), (25, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Versions of packages jed depends on:
ii jed-common 1:0.99.19-2
ii libc6 2.13-16
ii libgpm2 1.20.4-4
ii libslang2 2.2.3-3
jed recommends no packages.
Versions of packages jed suggests:
ii gpm 1.20.4-4
-- no debconf information
--- End Message ---
--- Begin Message ---
After giving up the hold on libslang2-2.2.4-2 and updating it to
libslang2-2.2.4.5, this bug's symptoms seem to be gone, jed starts
up normally now.
/mjk
--- End Message ---
