Hello, when I started gnome, my icon of update-notifier, on system tray, is always red and, on mouse over, says "There is an error during update" So i click on it, put the root password, and update-manager says "your system is up-to-date" At this point I try to re-lunch it manually, from terminal, with killall update-notifier && update-notifier and I get this error: [ 139.996718] apt-check[2609]: segfault at 0 ip b75d7b16 sp bfa8c998 error 6 in libc-2.11.2.so[b7563000+140000] Thanks.
tag 597124 moreinfo thanks Can you still reproduce this? If you can, please provide a backtrace of running 'python /usr/lib/update-notifier/apt-check'.
Hi Julian Andres, for sure. Here's the required information. :~$ gdb python GNU gdb (GDB) 7.2-debian Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/python...(no debugging symbols found)...done. (gdb) run /usr/lib/update-notifier/apt-check Starting program: /usr/bin/python /usr/lib/update-notifier/apt-check [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. 0xb7cfdb16 in memcpy () from /lib/i686/cmov/libc.so.6 Thanks. Fabrizio. Il giorno mar, 21/09/2010 alle 18.08 +0200, Julian Andres Klode ha scritto:
Sorry, my previous e-mail has been sent incomplete. More output of gdb #0 0xb7cfdb16 in memcpy () from /lib/i686/cmov/libc.so.6 #1 0xbfffa990 in ?? () #2 0xb79d8300 in pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) () from /usr/lib/libapt-pkg.so.4.10 #3 0xb79cb8ee in pkgCacheFile::BuildCaches(OpProgress*, bool) () from /usr/lib/libapt-pkg.so.4.10 #4 0xb79cba64 in pkgCacheFile::Open(OpProgress*, bool) () from /usr/lib/libapt-pkg.so.4.10 #5 0xb7a67d27 in ?? () from /usr/lib/python2.6/dist-packages/apt_pkg.so #6 0x080accbd in ?? () #7 0x0806232a in PyObject_Call () #8 0x080e016b in PyEval_EvalFrameEx () #9 0x080e2507 in PyEval_EvalCodeEx () #10 0x080e098b in PyEval_EvalFrameEx () #11 0x080e2507 in PyEval_EvalCodeEx () #12 0x080e2607 in PyEval_EvalCode () #13 0x080ffcbd in PyRun_FileExFlags () #14 0x080fff22 in PyRun_SimpleFileExFlags () #15 0x0805dd81 in Py_Main () #16 0x0805cf6b in main () Thanks again. Il giorno mar, 21/09/2010 alle 20.01 +0200, Fabrizio Regalli ha scritto:
tag 597124 - moreinfo reassign 597124 apt thanks [Fabrizio: Please do not top-post] [Reassigning to APT - APT team: context can be found below] According to the backtrace, the bug appears to be in APT. Quoting the remaining message, as deity@lists.debian.org is part of the discussion now (due to the reassign).