Public bug reported:
Binary package hint: texmacs
Caused during the upgrade to:
Description:Ubuntu 9.10
Release:9.10
ProblemType: Package
Architecture: amd64
Date: Wed Sep 1 09:14:48 2010
Dependencies:
DistroRelease: Ubuntu 9.10
ErrorMessage:
ErrorMessage: subprocess installed
** Attachment added: VarLogDistupgradeAptlog.gz
https://bugs.launchpad.net/bugs/628074/+attachment/1534442/+files/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
Fixed with the following:
aptitude install gnome-icon-theme
--
package texmacs-common 1:1.0.7.2-1 failed to install/upgrade:
https://bugs.launchpad.net/bugs/628074
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Hi,
Sorry for the delay in my reply.
This seemed to be in just one install. I believe that it was a bad
install. I have not been able to repeat it since.
Thank you for looking into it.
A.
Hmm...perl still exists in all versions of ubuntu
(http://packages.ubuntu.com/edgy/perl/perl).
It
Public bug reported:
Binary package hint: rsnapshot
rsnapshot depends on perl, however this is now called perl-base.
I believe that changing the dependancy to perl-base should allow the
package to be installed without errors.
System:
newly installed ubuntu-6.06.1-server-amd64
Error output:
The above problems only seem to manifest with edgy. I have now installed
dapper and do not have the ls -latr problem, or the cron segfaults, and
postfix problem.
However tar crashes with the 4500+ directory:
Command run: cd /user # directory has 4500+ directories with 250Gs of data
Command run:
Confirmed that this happens after a reboot. Did not happen after a umount and
remount.
Confirmed that running ls -l before running ls -latr means no segmentation
faults.
Confirmed another program that segfaults in the backgroud.
kernel: [ 3690.913237] cron[4023]: segfault at 2b96e84cd3b8
Public bug reported:
I have a directory with 4500+ entries, ls -l works fine, however ls
-latr produced a segfault:
[104865.917689] ls[4834]: segfault at 2b75d64ec3b8 rip
2b75d3f1226f rsp 7fffd70d5f60 error 4
Problem was not consistent. I got 2 segfaults, however once ls -l worked
