Your message dated Mon, 16 Jun 2008 07:07:47 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#449106: Do you still get this in 0.4.10?
has caused the Debian Bug report #449106,
regarding aptitude segfaults after trying to "Mark all upgradable packages to
be upgraded" ('U' key)
to be marked as done.This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 449106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449106 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: aptitude Version: 0.4.7-1 Severity: normal To reproduce segfault I do: 1) Run aptitude, installing/removing any package (for example I selected gsmc package for purging ('_'), pressed 'g' two times, removing process started, "Press return to continue." -- ok, in main screen now) 2) Pressing 'U' () and segfault: bob:~# aptitude (Reading database ... 322182 files and directories currently installed.) Removing gsmc ... Purging configuration files for gsmc ... Press return to continue. Ouch! Got SIGSEGV, dying.. Segmentation fault bob:~# In gdb (running from src/ directory "dgb ./aptitude" in aptitude sources and repeating actions described upper): Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7b62a60 (LWP 19171)] 0xb7e731b6 in pkgRecords::Lookup () from /usr/lib/libapt-pkg-libc6.6-6.so.4.6 (gdb) (gdb) bt #0 0xb7e731b6 in pkgRecords::Lookup () from /usr/lib/libapt-pkg-libc6.6-6.so.4.6 #1 0x080ec987 in pkg_description_widget::set_package (this=0x89d1b08, [EMAIL PROTECTED], [EMAIL PROTECTED]) at pkg_view.cc:239 #2 0x080ed774 in info_area_multiplex::set_package (this=0x89d2ca8, [EMAIL PROTECTED], [EMAIL PROTECTED]) at pkg_view.cc:379 #3 0x080edad5 in info_area_multiplex::reset_package (this=0x89d2ca8) at pkg_view.cc:440 #4 0x0810d5e2 in do_mark_upgradable () at /usr/include/sigc++-2.0/sigc++/signal.h:544 #5 0x081ac7f2 in vscreen_widget::handle_key (this=0x8398660, [EMAIL PROTECTED]) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:440 #6 0x081d9041 in vs_passthrough::handle_key (this=0x8398660, [EMAIL PROTECTED]) at vs_passthrough.cc:94 #7 0x081ac6d5 in vscreen_widget::dispatch_key (this=0x8398660, [EMAIL PROTECTED]) at vscreen_widget.cc:263 #8 0x081c69b1 in vs_menubar::handle_key (this=0x838e120, [EMAIL PROTECTED]) at vs_menubar.cc:634 #9 0x081ac6d5 in vscreen_widget::dispatch_key (this=0x838e120, [EMAIL PROTECTED]) at vscreen_widget.cc:263 #10 0x081aabd1 in input_thread::get_input_event::dispatch (this=0x8a305b8) at vscreen.cc:281 #11 0x081a35af in vscreen_mainloop (synch=0) at vscreen.cc:1024 #12 0x0810f148 in ui_main () at ui.cc:2662 #13 0x08053e99 in main (argc=Cannot access memory at address 0x0 ) at main.cc:581 (gdb) Bug seems to be simply reproduced, so I will not spend my time on debugging... Aptitude configuration: bob:~# cat /etc/apt/sources.list deb http://194.97.2.68/debian/ sid main non-free contrib deb-src http://194.97.2.68/debian/ sid main non-free contrib deb http://ftp.debian.org/debian sid main non-free contrib deb http://ftp.debian.org/debian stable main non-free contrib deb-src http://ftp.debian.org/debian sid main non-free contrib bob:~# bob:~# cat /etc/apt/sources.list.d/winehq.list deb http://wine.budgetdedicated.com/apt etch main #WineHQ - Debian 4.0 "Etch" deb-src http://wine.budgetdedicated.com/apt etch main #WineHQ - Debian 4.0 "Etch" bob:~# bob:~# cat /etc/apt/preferences Package: * Pin: origin Pin-Priority: 510 Package: * Pin: origin 194.97.2.68 Pin-Priority: 501 Package: * Pin: origin wine.budgetdedicated.com Pin-Priority: 510 Package: * Pin: release a=stable Pin-Priority: 495 Package: * Pin: release a=testing Pin-Priority: 497 bob:~# bob:~# cat /etc/apt/apt.conf.d/01autoremove APT { NeverAutoRemove { "^linux-image.*"; "^linux-restricted-modules.*"; }; }; bob:~# cat /etc/apt/apt.conf.d/70debconf // Pre-configure all packages with debconf before they are installed. // If you don't like it, comment it out. DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt || true";}; bob:~#bob:~# -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (501, 'unstable'), (500, 'unstable'), (495, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-k7 (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.6-6 0.7.9 Advanced front-end for dpkg ii libc6 2.6.1-6 GNU C Library: Shared libraries ii libgcc1 1:4.2.2-3 GCC support library ii libncursesw5 5.6+20071013-1 Shared libraries for terminal hand ii libsigc++-2.0-0c2a 2.0.17-2 type-safe Signal Framework for C++ ii libstdc++6 4.2.2-3 The GNU Standard C++ Library v3 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc 0.4.7-1 English manual for aptitude, a ter ii libparse-debianchangelog-perl 1.1.1-1 parse Debian changelogs and output -- no debconf information
--- End Message ---
--- Begin Message ---Version: 0.4.10-1 On Sun, Jun 15, 2008 at 05:44:44PM +0400, Bob Rutsky <[EMAIL PROTECTED]> was heard to say: > Hello! > > > I think these bugs were probably fixed in 0.4.10. I would appreciate it > > if you could check whether you still encounter it and let me know if it > > appears to be gone (in which case I'll close the bug). > > Hm... I use aptitude 0.4.11 now, looks like this bug is fixed, and can be > closed. Ok, then I'll close it. Daniel
--- End Message ---
