Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-12-30 Thread Neil Williams
On Thu, 30 Dec 2010 13:47:24 -0400 Joey Hess wrote: > Stupid proof of concept (but not good enough for 256-way cpu) patch: > > --- stat-intr.c.old 2010-12-30 13:33:45.700814058 -0400 > +++ stat-intr.c 2010-12-30 13:35:13.208825814 -0400 > @@ -139,9 +139,9 @@ > f2=fopen("

Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-12-30 Thread Joey Hess
We have a bug report with an interrupts file included. (Attached to this email for convenience.) Install that file into place or modify procmeter to use it, and you will be able to reproduce the segfault. Backtrace: Program received signal SIGSEGV, Segmentation fault. Initialise (options=0x0) at

Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-12-30 Thread Hideki Yamane
Hi, On Wed, 29 Dec 2010 22:58:14 + Neil Williams wrote: > I disagree. The segmentation fault occurs each time on my amd64 sid > system. Has the symlink changed on your system? > > /usr/bin/procmeter3 -> procmeter3-xaw > seg fault > > /usr/bin/procmeter3 -> procmeter3-gtk > works fine. Bo

Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-12-30 Thread Neil Williams
On Thu, 30 Dec 2010 01:32:34 -0800 Alex Goebel wrote: > Both procmeter3-xaw and procmeter3-gtk2 work on my amd64 sid system, > so something might be wrong on your side. That doesn't help! - you provide almost no detail of your system. Could you use reportbug to submit such comments in future ple

Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-12-30 Thread Alex Goebel
Both procmeter3-xaw and procmeter3-gtk2 work on my amd64 sid system, so something might be wrong on your side. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-12-29 Thread Neil Williams
On Thu, 30 Dec 2010 07:28:10 +0900 Hideki Yamane wrote: > I cannot reproduce segfault in my environment (squeeze amd64, sid > i386), procmeter3 just works. I would suggest to downgrade severity. I disagree. The segmentation fault occurs each time on my amd64 sid system. Has the symlink changed

Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-12-29 Thread Hideki Yamane
Hi, I cannot reproduce segfault in my environment (squeeze amd64, sid i386), procmeter3 just works. I would suggest to downgrade severity. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@

Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-12-27 Thread Julien Cristau
user release.debian@packages.debian.org usertag 602975 squeeze-will-remove kthxbye On Tue, Nov 9, 2010 at 17:48:50 -0500, John E. Davis wrote: > Package: procmeter3 > Version: 3.5c-1 > Severity: grave > > I am running an up-to-date Debian squeeze 64 system. procmeter3 SEGVs > right away up

Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup

2010-11-09 Thread John E. Davis
Package: procmeter3 Version: 3.5c-1 Severity: grave I am running an up-to-date Debian squeeze 64 system. procmeter3 SEGVs right away upon startup: $ procmeter3 zsh: segmentation fault procmeter3 I have no .procmeterrc file. I suggested a severity of "grave" because the SEGV makes it unu