Bug#246604: marked as done (does not update /var/log/wtmp)
Your message dated Sat, 1 May 2004 15:07:21 +0200 with message-id <[EMAIL PROTECTED]> and subject line does not update /var/log/wtmp has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 29 Apr 2004 21:46:56 + >From [EMAIL PROTECTED] Thu Apr 29 14:46:56 2004 Return-path: <[EMAIL PROTECTED]> Received: from meinungsverstaerker.de (donnergurgler.meinungsverstaerker.de) [213.133.108.85] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BJJMu-000400-00; Thu, 29 Apr 2004 14:46:56 -0700 Received: from p508c8d9a.dip0.t-ipconnect.de ([80.140.141.154] helo=zocker.cafe.chummer.net) by donnergurgler.meinungsverstaerker.de with asmtp (Exim 3.35 #1 (Debian)) id 1BJJMs-0001mX-00 for <[EMAIL PROTECTED]>; Thu, 29 Apr 2004 23:46:54 +0200 Received: from chummer14.cafe.chummer.net ([192.168.0.24]) by zocker.cafe.chummer.net with esmtp (Exim 3.35 #1 (Debian)) id 1BJJMN-0008Lb-00; Thu, 29 Apr 2004 23:46:23 +0200 Received: from rt by chummer14.cafe.chummer.net with local (Exim 3.36 #1 (Debian)) id 1BJJMN-0001JC-00; Thu, 29 Apr 2004 23:46:23 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Reinhard Tartler <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: does not update /var/log/wtmp X-Mailer: reportbug 2.56 Date: Thu, 29 Apr 2004 23:46:23 +0200 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Score: 1 Package: kdm Version: 4:3.2.2-1 Severity: normal After upgrading to Version 3.2.2-1 kdm does no longer updates /var/log/wtmp. This is important for us as we do accounting based in the Information stored there. The version before (3.1) did update them. Reinhard -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.5 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] Versions of packages kdm depends on: ii debconf 1.4.22 Debian configuration management sy ii kdebase-bin 4:3.2.2-1KDE Base (binaries) ii kdelibs44:3.2.2-2KDE core libraries ii libart-2.0-22.3.16-3 Library of functions for 2D graphi ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libfam0c102 2.7.0-5 client library to control the FAM ii libgcc1 1:3.3.3-6GCC support library ii libice6 4.3.0-7 Inter-Client Exchange library ii libpam-runtime 0.76-19 Runtime support for the PAM librar ii libpam0g0.76-19 Pluggable Authentication Modules l ii libpng12-0 1.2.5.0-5PNG library - runtime ii libqt3c102-mt 3:3.2.3-2Qt GUI Library (Threaded runtime v ii libsm6 4.3.0-7 X Window System Session Management ii libstdc++5 1:3.3.3-6The GNU Standard C++ Library v3 ii libx11-64.3.0-7 X Window System protocol client li ii libxext64.3.0-7 X Window System miscellaneous exte ii libxrender1 0.8.3-7 X Rendering Extension client libra ii libxtst64.3.0-7 X Window System event recording an ii xbase-clients 4.3.0-7 miscellaneous X clients ii xlibs 4.3.0-7 X Window System client libraries m ii zlib1g 1:1.2.1-5compression library - runtime -- debconf-show failed --- Received: (at 246604-done) by bugs.debian.org; 1 May 2004 13:07:56 + >From [EMAIL PROTECTED] Sat May 01 06:07:56 2004 Return-path: <[EMAIL PROTECTED]> Received: from meinungsverstaerker.de (donnergurgler.meinungsverstaerker.de) [213.133.108.85] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BJuDk-0007J7-00; Sat, 01 May 2004 06:07:56 -0700 Received: from p508c8a1a.dip0.t-ipconnect.de ([80.140.138.26] helo=zocker.cafe.chummer.net) by donnergurgler.meinun
Bug#246850: knode: Data corruption & loss: sent articles, scorefile
Package: knode Version: 4:2.2.2-14.6 Severity: serious Knode appears to have a problem losing or corrupting user state data in scorefiles and sent message folders. I'm not sure of the precipitating event, more below. I've recently experienced data corruption and/or loss with knode. My scorefile has been emptied completely. The sent articles mbox is now corrupted and doesn't properly render in either mutt (mutt -Rf ) or knode. Headers from a corrupted article below. I've had a few unclean exit events in the past week or so, ranging from window manager shutdowns or segfaults, to a kernel panic. As I didn't check Knode immediately after either, I'm not sure which if any of these precipitated the failure. Other extant bugs indicate Knode caches data to save on exit, which may result in data loss or corruption. I can provide additional data / files on request. Sample broken mbox header: From [EMAIL PROTECTED] Mon Jan 01 00:00:00 1997 [EMAIL PROTECTED] Mon Jan 01 00:00:00 1997 X-KNode-Overview: Re: Clean up the Earthlink network earthlink.general-discus sion45 From: "Karsten M. Self" Subject: Re: Clean up the Earthlink network Newsgroups: earthlink.general-discussion Reply-To: kmself@ix.netcom.com Date: Thu, 09 Oct 2003 23:45:45 -0700 References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED] read1.news.atl.earthlink.net> Organization: Gestalt System User-Agent: KNode/0.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Status: O Content-Length: 1822 Lines: 45 Another segment shows the tail of one message, a spurious 'From ' line, and another post: -- Karsten M. Self http://kmself.home.netcom.com/ What Part of "Gestalt" don't you understand? Ford had another Pan Galactic Gargle Blaster, the drink which has been described as the alcoholic equivalent of a mugging - expensive From [EMAIL PROTECTED] Mon Jan 01 00:00:00 1997 e head. -- HHGTG From [EMAIL PROTECTED] Mon Jan 01 00:00:00 1997 X-KNode-Overview: Re: Want to stop spam and "Swen"? Do this. earthlink.genera l-discussion141 From: "Karsten M. Self" Subject: Re: Want to stop spam and "Swen"? Do this. Newsgroups: earthlink.general-discussion Reply-To: kmself@ix.netcom.com Date: Fri, 10 Oct 2003 00:08:14 -0700 References: <[EMAIL PROTECTED]> Organization: Gestalt System User-Agent: KNode/0.6.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Status: O Content-Length: 6008 Lines: 141 The scorefile currently reads in entirety: ...it previously had ~100 rules. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (950, 'testing'), (400, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.23-1-686 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages knode depends on: ii kdelibs3 4:2.2.2-13.woody.9 KDE core libraries (runtime files) ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libfam0c102 [libfam0] 2.7.0-5client library to control the FAM ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii libkdenetwork14:2.2.2-14.6 Common libraries needed for KDE ne ii libpng2 1.0.15-4 PNG library, older version - runti ii libqt23:2.3.2-14 Qt GUI Library (runtime version) ii libstdc++2.10-glibc2. 1:2.95.4-22The GNU stdc++ library ii xlibs 4.3.0-7X Window System client libraries m ii zlib1g1:1.2.1-5 compression library - runtime -- no debconf information
Bug#194248: kdebase: kde very slow to load
On Mon, 12 Apr 2004, Adeodato Simó wrote: > Antos Andras [Fri, 09 Apr 2004 19:58:52 +0200]: > > sometimes I get presented with a grey root window and nothing happens. > > Sometimes after 10-15 minutes eventually the kde desktop comes back. > > [...] > > The lo interface seem to be not active: > That's probably the culprit. Bring it up and try again. Yes, it seems that this did solve the problem! (I put auto lo iface lo inet loopback into /etc/network/interfaces) Thank you very much. Andras
Re: strange kdepim failure on m68k build
On Sat, May 01, 2004 at 01:47:51PM +0200, Michael Schmitz wrote: > > > /dev/sdc2 16G 3.9G 11G 26% /org > > > > > > which is what the buildd chroot lives on. I'm not sure what the problem > > > actually is, though. > > > > Maybe when kullervo rebooted it corrupted something, since the first > > time it tried to build it worked fine until it was shutdown in the > > middle of the build. As soon as it tried to build it the second time, on > > the same box, without rebuilding the chroot, it failed to build properly. > > According to the build log it looked like it just tried to resume the > > build more or less, so something must have gotten corrupted, at least > > afaict. > > Not likely - the build isn't just resumed but restarted from the > beginning (without unpacking the source again, though). If the package > fails to build on the second try, something might be wrong with the clean > target. The clean target works fine afaict, I test it everytime I upload since I build multiple times before each upload. If you look in the log output it seems whole directories are missing from the source, an indication to me at least that the box has corruption issues... Note that it retried a third time on kullervo and it FAILED AGAIN very oddly when it passed building on every other buildd. Also notice that both times it failed it failed due to missing files that should be there. Chris signature.asc Description: Digital signature
Re: strange kdepim failure on m68k build
> > /dev/sdc2 16G 3.9G 11G 26% /org > > > > which is what the buildd chroot lives on. I'm not sure what the problem > > actually is, though. > > Maybe when kullervo rebooted it corrupted something, since the first > time it tried to build it worked fine until it was shutdown in the > middle of the build. As soon as it tried to build it the second time, on > the same box, without rebuilding the chroot, it failed to build properly. > According to the build log it looked like it just tried to resume the > build more or less, so something must have gotten corrupted, at least > afaict. Not likely - the build isn't just resumed but restarted from the beginning (without unpacking the source again, though). If the package fails to build on the second try, something might be wrong with the clean target. Michael
