** Description changed: Binary package hint: debconf Running the adept updater via the system tray icon and updating to the latest releases for 7.10 beta, I noticed that when I had it showing me details, I was seeing "stack smashing detected" warnings and then perl was being aborted which corresponds to the packages that failed and caused the errors to be generated. This ultimately caused Adept to error out with the following error "There was an error commiting changes. Possibly there was a problem downloading some packages or the commit would break packages.". I have not yet tried to manually upgrade via apt-get dist-upgrade to see if that fixes anything, though I don't think it will. I'll probably try a reboot and see if any of the packages that had been upgraded just needed to be in a clean state or something. This was on a fresh install of 7.10 beta2 that I've updated every couple of days as I've had time to play with things. ProblemType: Crash Architecture: i386 Date: Tue Jul 31 21:16:57 2007 Disassembly: 0xfe5aa510: DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/sbin/dpkg-preconfigure InterpreterPath: /usr/bin/perl NonfreeKernelModules: nvidia Package: debconf 1.5.14 PackageArchitecture: all ProcCmdline: /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt ProcCwd: /home/james ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: debconf StacktraceTop: ?? () ?? () from /lib/libc.so.6 abort () from /lib/libc.so.6 ?? () from /lib/libc.so.6 ?? () Title: dpkg-preconfigure crashed with SIGSEGV in abort() Uname: Linux frodo 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux UserGroups: + SegvAnalysis: + Segfault happened at: 0xfe5aa510: + PC (0xfe5aa510) not located in a known VMA region (needed executable region)! + SegvReason: executing unknown VMA
-- dpkg-preconfigure crashed with SIGSEGV in abort() https://bugs.launchpad.net/bugs/129604 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
