Your message dated Tue, 6 May 2014 23:58:44 +0200 with message-id <201405062358.45778.hol...@layer-acht.org> and subject line thanks for letting us know has caused the Debian Bug report #747226, regarding procps: bugrep...@ravor.org 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 ow...@bugs.debian.org immediately.) -- 747226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: procps Version: 1:3.3.3-3 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (900, 'stable'), (650, 'testing'), (600, 'unstable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages procps depends on: ii initscripts 2.88dsf-41+deb7u1 ii libc6 2.13-38+deb7u1 ii libncurses5 5.9-10 ii libncursesw5 5.9-10 ii libprocps0 1:3.3.3-3 ii libtinfo5 5.9-10 ii lsb-base 4.1+Debian8+deb7u1 Versions of packages procps recommends: ii psmisc 22.19-1+deb7u1 procps suggests no packages. -- no debconf information Hey guys, since some days i have a weird issue using ps and top. Each time i try to call them via script or command line, they crash with "Signal 11 (SEGV)" and i didn't manage to repair that. I dont even know, what caused this problem in first place. I already tried to reinstall procps-package and ispell which seems to be related to the problem. ps-Output: root@s93:~# ps Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report this bug top-Output: root@s93:~# top signal 11 (SEGV) was caught by top, please see http://www.debian.org/Bugs/Reporting strace of ps (just last few lines): open("/proc/uptime", O_RDONLY) = 3 lseek(3, 0, SEEK_SET) = 0 read(3, "236610.02 1308470.52\n", 2047) = 21 open("/proc/sys/kernel/pid_max", O_RDONLY) = 4 read(4, "32768\n", 24) = 6 close(4) = 0 mmap(NULL, 139264, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f1bb0004000 mprotect(0x7f1bb0025000, 4096, PROT_NONE) = 0 time(NULL) = 1399280678 open("/proc/meminfo", O_RDONLY) = 4 lseek(4, 0, SEEK_SET) = 0 read(4, "MemTotal: 16212768 kB\nMemF"..., 2047) = 1198 open("/usr/share/ispell/mwl0", O_RDONLY) = -1 ENOENT (No such file or directory) --- SIGSEGV (Segmentation fault) @ 0 (0) --- write(2, "Signal 11 (SEGV) caught by ps (p"..., 57Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3). ) = 57 write(2, "ps:", 3ps:) = 3 write(2, "display.c:59: ", 14display.c:59: ) = 14 write(2, "please report this bug", 22please report this bug) = 22 write(2, "\n", 1 ) = 1 close(1) = 0 close(2) = 0 exit_group(1) = ? Problem seems to lie here, but anyway i dont know how to fix it... open("/usr/share/ispell/mwl0", O_RDONLY) = -1 ENOENT (No such file or directory) Any help would be appreciated.
--- End Message ---
--- Begin Message ---Hi, thanks for letting us know that the issue wasn't really one, closing this bug. cheers, Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
