"Use of uninitialized value $class in hash element" message during package install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
spell (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: spell
When installing package spell, I was confronted with the following:
-------
$ sudo aptitude install spell
[sudo] password for ricardo:
The following NEW packages will be installed:
iamerican{a} ispell{a} spell
0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 606kB of archives. After unpacking 1,782kB will be used.
Do you want to continue? [Y/n/?] y
Get:1 http://
Get:2 http://
Get:3 http://
Fetched 606kB in 5s (102kB/s)
Preconfiguring packages ...
Use of uninitialized value $class in hash element at /usr/share/
Selecting previously deselected package ispell.
(Reading database ... 311582 files and directories currently installed.)
Unpacking ispell (from .../ispell_
Selecting previously deselected package iamerican.
Unpacking iamerican (from .../iamerican_
Selecting previously deselected package spell.
Unpacking spell (from .../archives/
Processing triggers for doc-base ...
Processing 1 added doc-base file(s)...
Registering documents with scrollkeeper...
Processing triggers for man-db ...
Processing triggers for install-info ...
Setting up iamerican (3.1.20.0-7) ...
Setting up ispell (3.1.20.0-7) ...
Setting up spell (1.0-24) ...
-------
The package installed successfully, but the message may indicate a deeper problem
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: spell 1.0-24
ProcVersionSign
Uname: Linux 2.6.35-25-generic i686
Architecture: i386
Date: Tue Feb 8 04:20:25 2011
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcEnviron:
LANGUAGE=
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: spell
Thanks for reporting this issue.
While I saw the same message when installing spell on Ubuntu 10.10, it was not shown when installing it on Ubuntu 11.04. Therefore I would assume this issue has been resolved in the meantime. Since 10.10 reached end of life on April 10, 2012, the fix will unfortunately not be backported.
Feel free to report any bugs you find in the future.