Your message dated Fri, 22 Feb 2008 00:16:49 -0500 with message-id <20080222051649.GA13725@connexer.com> and subject line Re: Bug#466959: wmakerconf: Program committed suicide has caused the Debian Bug report #466959, regarding wmakerconf: Program committed suicide 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 owner@bugs.debian.org immediately.) -- 466959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466959 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: wmakerconf: Program committed suicide
- From: Damon Carr <damon@agilefactor.com>
- Date: Thu, 21 Feb 2008 23:48:22 -0500
- Message-id: <[🔎] 1203655702.14625.1.camel@lclsrvr.damon.wikaba.com>
Package: wmakerconf Version: 2.11-5 Severity: important File: /usr/bin/wmakerconf *** Please describe what you were doing when the application crashed *** (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1219691984 (LWP 15002)] 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0xb788e6b3 in waitpid () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7f669e8 in ?? () from /usr/lib/debreaper/libviaticum.so #3 0x00003a9b in ?? () #4 0xbfad1f44 in ?? () #5 0x00000000 in ?? () Thread 1 (Thread -1219691984 (LWP 15002)): #0 0xffffe410 in __kernel_vsyscall () No symbol table info available. #1 0xb788e6b3 in waitpid () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0xb7f669e8 in ?? () from /usr/lib/debreaper/libviaticum.so No symbol table info available. #3 0x00003a9b in ?? () No symbol table info available. #4 0xbfad1f44 in ?? () No symbol table info available. #5 0x00000000 in ?? () No symbol table info available. #0 0xffffe410 in __kernel_vsyscall () -- System Information: Debian Release: lenny/sid APT prefers gutsy-updates APT policy: (500, 'gutsy-updates'), (500, 'gutsy-security'), (500, 'gutsy-proposed'), (500, 'gutsy-backports'), (500, 'gutsy') Architecture: i386 (i686) Kernel: Linux 2.6.24.2 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages wmakerconf depends on: ii bzip2 1.0.4-0ubuntu2 high-quality block-sorting file co ii libc6 2.6.1-1ubuntu10 GNU C Library: Shared libraries ii libglib2.0-0 2.14.1-1ubuntu1 The GLib library of C routines ii libgtk2.0-0 2.12.0-1ubuntu3 The GTK+ graphical user interface ii libhtml-parser-perl 3.56-1 A collection of modules that parse ii libwraster3 0.92.0-6.1 Shared libraries of Window Maker r ii libwww-perl 5.805-1 WWW client/server library for Perl ii libx11-6 2:1.1.1-1ubuntu4 X11 client-side library ii lynx-cur [lynx] 2.8.7dev5-1 Text-mode WWW Browser with NLS sup ii wget 1.10.2-3ubuntu1 retrieves files from the web ii wmaker 0.92.0-6.1 NeXTSTEP-like window manager for X ii wmakerconf-data 0.90.0.0-3 Data files for wmakerconf, a confi wmakerconf recommends no packages.
--- End Message ---
--- Begin Message ---
- To: 466959-done@bugs.debian.org
- Cc: 466959-submitter@bugs.debian.org
- Subject: Re: Bug#466959: wmakerconf: Program committed suicide
- From: Roberto C. Sánchez <roberto@connexer.com>
- Date: Fri, 22 Feb 2008 00:16:49 -0500
- Message-id: <20080222051649.GA13725@connexer.com>
- Mail-followup-to: 466959-done@bugs.debian.org, 466959-submitter@bugs.debian.org
- In-reply-to: <[🔎] 1203655702.14625.1.camel@lclsrvr.damon.wikaba.com>
- References: <[🔎] 1203655702.14625.1.camel@lclsrvr.damon.wikaba.com>
This bug report is next to useless. On Thu, Feb 21, 2008 at 11:48:22PM -0500, Damon Carr wrote: > Package: wmakerconf > Version: 2.11-5 > Severity: important > File: /usr/bin/wmakerconf > > *** Please describe what you were doing when the application crashed *** > > (no debugging symbols found) > Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". > (no debugging symbols found) > (no debugging symbols found) > [Thread debugging using libthread_db enabled] > [New Thread -1219691984 (LWP 15002)] > 0xffffe410 in __kernel_vsyscall () > #0 0xffffe410 in __kernel_vsyscall () > #1 0xb788e6b3 in waitpid () from /lib/tls/i686/cmov/libc.so.6 > #2 0xb7f669e8 in ?? () from /usr/lib/debreaper/libviaticum.so > #3 0x00003a9b in ?? () > #4 0xbfad1f44 in ?? () > #5 0x00000000 in ?? () > > Thread 1 (Thread -1219691984 (LWP 15002)): > #0 0xffffe410 in __kernel_vsyscall () > No symbol table info available. > #1 0xb788e6b3 in waitpid () from /lib/tls/i686/cmov/libc.so.6 > No symbol table info available. > #2 0xb7f669e8 in ?? () from /usr/lib/debreaper/libviaticum.so > No symbol table info available. > #3 0x00003a9b in ?? () > No symbol table info available. > #4 0xbfad1f44 in ?? () > No symbol table info available. > #5 0x00000000 in ?? () > No symbol table info available. > #0 0xffffe410 in __kernel_vsyscall () > The backtrace containes no useful data. Additionally, you did not follow the instruction to "Please describe what you were doing when the application crashed". > -- System Information: > Debian Release: lenny/sid > APT prefers gutsy-updates > APT policy: (500, 'gutsy-updates'), (500, 'gutsy-security'), (500, 'gutsy-proposed'), (500, 'gutsy-backports'), (500, 'gutsy') > Architecture: i386 (i686) > In case you did not notice, you are running Ubuntu, but you filed this bug in the Debian BTS. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.comAttachment: signature.asc
Description: Digital signature
--- End Message ---