localdef crashes on update (gutsy)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
language-support-fr (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: language-support-fr
Hello,
We discover first this bug while upgrading gutsy to hardy
(cf https:/
Seems this bug is also comming into gutsy : one of our computers completly crashes its update on localdef, so that we can't do anything.
the only thing we could do to pass away was to
- reboot (processes coulnd't be killed, event with kill -9 !)
- remove postinst file... which isn't really nice.
OS informations :
architecture => i386
kernelrelease => 2.6.22-15-generic
lsbdistdescription => Ubuntu 7.10
processor0 => Intel(R) Pentium(R) 4 CPU 2.60GHz
Package crashing :
iF language-support-fr 1:7.04+20070209 metapackage for French language support
apt-cache policy language-support-fr
language-
Installed: 1:7.04+20070209
Candidate: 1:7.04+20070209
Version table:
*** 1:7.04+20070209 0
500 http://
100 /var/lib/
Process list (snapshot, only those which are interesting for our case)
6475 ? Ss 13:10 /usr/bin/apt-get -q -y -o DPkg::Options:
6565 pts/1 Ss+ 0:00 \_ /usr/bin/dpkg --force-confold --status-fd 33 --configure openoffice.
6572 pts/1 S+ 0:00 \_ /bin/sh -e /var/lib/
6573 pts/1 S+ 0:00 \_ /bin/sh -e /usr/share/
6574 pts/1 S+ 0:00 \_ /bin/sh /usr/sbin/
6587 pts/1 S+ 0:00 \_ /bin/sh /usr/sbin/
6607 pts/1 R+ 12:30 \_ localedef --no-archive --magic=20051014 -i fr_BE -c -f UTF-8 fr_BE.UTF-8
6608 pts/1 Z+ 0:00 \_ [gzip] <defunct>
I don't know for now if it's only on this computer, and if it's only for this package; Seems that language-
Thanks in advance for workaround/fixe
Regards
C.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 249340, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.