Bug#1072299: Compositor-related crashes

I'm going to need a spot of help with this. I have Chromium running under GDB, with surprisingly low overhead (I can browse like normal if I drop the --single-process flag). As far as I could find, the "trap invalid opcode" error reported in syslog is synonymous with a SIGILL, so I set "handle

Bug#241787: options to seperate hosts and for log compaction would both be nice

On Sun, 12 May 2024 17:01:36 +0100 Richard Lewis wrote: > > This bug is nearly 20 years old. (It is a shame no-one replied - the links > > no longer work and there is not enough info recorded to action) > > > > Unless anyone is watching and can proivde more i

Bug#654557: logcheck-database: pure-ftpd rules need update

On Sat, 1 Jun 2024 at 14:21, Kiss Gabor (Bitman) wrote: > > On Sat, 1 Jun 2024, Richard Lewis wrote: > > > > does not cover log entry > > > > > > Jan 4 07:23:42 gatling pure-ftpd: (?@203.158.197.21) [INFO] Logout. > > > > > > The problem i

Bug#651319: ignore.d.server/nagios: SERVICE FLAPPING line doesn't allow whitespace

On Wed, 07 Dec 2011 09:39:55 -0800 andrew bezella wrote: > Package: logcheck-database > Version: 1.3.13 > Severity: minor > > in most cases whitespace is allowed in SERVICE names, but for the > SERVICE FLAPPING ALERT it is not. using the cases where > whitespace is allowed as a template, i made

Bug#591757: logcheck-database: please update ignore rules for nagios

On Thu, 05 Aug 2010 11:28:16 +0200 Albert Dengg wrote: > please update the ignore rules for nagios: > nagios (at least nagios3) will write two lines for each passive > service check that it resives through nsca: > nagios3: EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;... > nagios3:

Bug#590677: [logcheck-database] additional rules for nagios/radius

On Wed, 28 Jul 2010 13:52:44 +0200 Hendrik Jaeger wrote: > Package: logcheck-database > Severity: wishlist > Tags: patch > > > Hi, > > check_radius output filter: > > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ check_radius: rc_avpair_gen: > received VSA attribute with unknown Vendor-Id [[:digit:]]+$ A

Bug#690607: logcheck-database: consider to add a line to ignore.d.server/cyrus-imapd

On Tue, 16 Oct 2012 03:04:36 +0200 Sebastian Steinhuber wrote: > Package: logcheck-database > Version: 1.3.15 > Severity: minor > Tags: patch > > Dear Maintainer, > to drop messages of the form: > > Oct 15 21:01:22 dds cyrus/cyr_expire[26497]: DIGEST-MD5 common mech free > > I added a line (#13)

Bug#764062: logcheck-database: does not filter amavis CLEAN messages

On Fri, 17 Oct 2014 00:57:07 +0200 =?UTF-8?B?SsOpcsO0bWUgRHJvdWV0?= wrote: > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ amavis\[[[:digit:]]+\]: > \([-[:digit:]]+\) Passed (CLEAN|SPAM(MY)?)( {RelayedInbound})?,( LOCAL)?( > \[(IPv6:)?[[:xdigit:].:]{3,39}\](:[[:xdigit:]]{0,5})?){0,2} <[^>]*> -> >

Bug#689418: logcheck-database: refine sendmail STARTTLS rule

On Tue, 02 Oct 2012 14:28:24 +0200 > With sendmail, self-signed certificates trigger a warning like: > > | Oct 2 13:02:07 hostname sm-mta[24652]: STARTTLS=client, > relay=host.example., version=TLSv1/SSLv3, verify=FAIL, > cipher=DHE-RSA-AES256-SHA, bits=256/256 > > There is a logcheck rule for

Bug#632825: logcheck: New ignore rule for arpwatch

On Wed, 06 Jul 2011 10:22:21 +0200 Wojciech Nizinski wrote: > Please add following ignore rule for arpwatch: > > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ arpwatch: short \(want 42\)$ It's a shame no-one replied since 2011, Is there still interest in adding this rule to logcheck-database? it looks

Bug#778905: logcheck: logging changes in spamd

control: tags -1 + moreinfo thanks On Sat, 21 Feb 2015 14:57:15 + Andrew Gallagher wrote: > spamd no longer suffixes "(closed before headers)" with "at /usr/sbin/spamd > line N" > > Updated rule attached. This may also apply to other errors that I haven't > been able to test yet. It's a

Bug#740203: logcheck-databse: proposed ignore rules for hostapd

control: tags -1 + moreinfo thanks On Wed, 26 Feb 2014 22:21:18 +0100 Gabriel Niebler wrote: > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ hostapd: [[:alnum:]]+: STA > ([0-9a-f]{2}:){5}[0-9a-f]{2} IEEE 802\.11: authenticated$ > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ hostapd: [[:alnum:]]+: STA

Bug#686144: logcheck: ignore.d.server/imapproxy regex for LOGIN and LOGOUT lines from syslog wrong

control: tags -1 + moreinfo On Wed, 29 Aug 2012 07:03:36 +0200 Sven Fischer wrote: > Package: logcheck > Version: 1.3.13 > Severity: normal > > In ignore.d.server/imapproxy the first two lines (LOGIN and LOGOUT) for the > regex contain double quotes. These are too much, hence the regex does not

Bug#654557: logcheck-database: pure-ftpd rules need update

control: tags -1 + moreinfo thanks On Wed, 04 Jan 2012 09:58:11 +0100 Gabor Kiss wrote: > /etc/logcheck/ignore.d.server/pure-ftpd rule > > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ pure-ftpd: > \([._[:alnum:]-]+@[._[:alnum:]-]+\) \[INFO\] Logout\.$ > > does not cover log entry > > Jan 4 07:23:42

Bug#652537: Please add rule for inetutils-syslogd

control: tags -1 moreinfo On Sun, 18 Dec 2011 11:11:13 + debian-b...@nospam.pz.podzone.net wrote: > Package: logcheck > Version: 1.2.69 > > The inetutils-syslogd (2:1.5.dfsg.1-9) package provides a system > logging daemon. syslogd periodically logs the following message: > > Dec 17 00:29:11

Bug#1072299: Compositor-related crashes

On Fri, 2024 May 31 21:49-04:00, Andres Salomon wrote: > Oh! Apparently my info is outdated. According to > , this was fixed back in August. It does > indeed look like > > has the dbgsym

Bug#909036: logcheck: Please update ignore rules for named GeoIP (after upgrade to Strech)

control: tags -1 + confirmed On Mon, 17 Sep 2018 20:48:12 +0200 mi te wrote: > Package: logcheck > Version: 1.3.18 > Severity: normal > > Dear Maintainer, > > After upgrade to Stretch, get a notification from logcheck every time after > BIND is restarted for logrotate. > They should be added to

Bug#547774: dovecot-related rules against logcheck

On Thu, 30 May 2024 at 20:43, Boyd Stephen Smith Jr. wrote: > > On Thursday, May 30, 2024 12:37:49 PM CDT Richard Lewis wrote: > > Is there still interest in updating rules for dovecot? > > Best I can volunteer is my current dovecot-local that is in active use. > (Attached.)

Bug#691258: Missing / in RE for "reducing the advertised EDNS UDP packet size"

On Tue, 23 Oct 2012 17:55:06 +0200 =?utf-8?B?TG/Dr2M=?= Minier wrote: > Package: logcheck > Version: 1.3.15 > Severity: minor > Tags: patch > > Hi, > > Got this log from time to time in System Events: > Oct 23 13:48:16 pig2 named[28880]: success resolving >

Bug#1072299: Compositor-related crashes

On Fri, 2024 May 31 18:36-04:00, Andres Salomon wrote: > > I'm going from memory here, but I believe the dak installation on > security.debian.org doesn't keep dbgsym packages for historical reasons. > Thus, they're only available once chromium gets moved to > stable-proposed-updates.

Bug#687990: logcheck-database: bind: "updating zone...PTR" and "signer...approved"

On Tue, 18 Sep 2012 06:00:06 +0200 Paul Muster wrote: > Update: > > > (1) please change > > > > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ named\[[[:digit:]]+\]: client > > [.:[:xdigit:]]+#[[:digit:]]+: updating zone '[-._[:alnum:]]+/IN': > > (adding an RR|deleting rrset) at '[._[:alnum:]-]+' A$ >

Bug#590675: [logcheck-database] additional rules for bind

On Wed, 28 Jul 2010 13:49:43 +0200 Hendrik Jaeger wrote: > Package: logcheck-database > Severity: wishlist > Tags: patch > > Hi, > > We have some additional rules for bind: > > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ named\[[0-9]+\]: > (general: )?(info: )?received control channel command 'stats'$

Bug#1072317: Redundant build when making packed_resources

Package: chromium Version: 125.0.6422.141-1 Severity: minor This is something I've noticed in the course of the build that has been annoying me for some time, and I thought I'd write it up. Here is an excerpt from the build log which illustrates the problem: [...] [61738/61742] AR

Bug#1072299: Compositor-related crashes

Sigh, spoke too soon. Chromium still crashes in both modes (tab and browser) even without Firefox running, but much less frequently. I had a good half-hour without crashes after closing Firefox, enough to lead me to think that was the cause. At this point, we're probably better off waiting to

Bug#1072299: Compositor-related crashes

I believe I've found a correlation: The crashes seem to have started with an instance of firefox-esr (115.11.0esr-1~deb12u1) that I was running on the side, since earlier today. Once I closed Firefox, the crashiness went away, completely. (This is on the same laptop that needs --use-gl=egl to

Bug#1072299: Compositor-related crashes

Package: chromium Version: 125.0.6422.112-1~deb12u1 Severity: important Recently, I have been observing crashes of individual tabs, and even of the entire browser, when navigating some Web pages. The crashed tabs correlate with the following syslog messages (multiple instances listed below):

Bug#1054393: dns-root-data: New IPs for b.root-servers-net 2023-11-27

So was it decided not to fix this in stable (bookworm)? That's a pity. Richard

Bug#1070482: systemd: tmpfiles.d not cleaning /var/tmp by default

Luca Boccassi writes: > Here's two paragraphs, one for each change, for the release notes: - More context and explanation would be helpful - suggestions below, - Based on the discussion on d-devel, the tmpfs change is much less controversial and so should be lower down. - how do we

Bug#778903: logcheck: saslauthd logging has changed

On Sat, 21 Feb 2015 14:53:21 + Andrew Gallagher wrote: > New versions of saslauthd say "pam_unix(smtp:auth)" instead of "(pam_unix)". > New rule is: > > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ saslauthd\[[[:digit:]]+\]: > pam_unix\(smtp:auth\) authentication failure; logname= uid=0 euid=0

Bug#765944: logcheck-database: improved openvpn rules

On Sun, 19 Oct 2014 14:06:02 +0100 Peter Wyss wrote: > Package: logcheck-database > The logcheck ignore.d.server rules for openvpn need some adjustments. > > The following 2 entries need to be adjusted to include [AF_INET]: > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ >

Bug#693183: Please include ignore.d.server rules for DMA

On Wed, 14 Nov 2012 03:50:07 +0100 Carlos Alberto Lopez Perez wrote: > Package: logcheck-database > Hello, > > After deploying DMA, I found that logcheck is not filtering the typical > notification messages of mail delivery that any mailer daemon generates. > > I successfully filtered all this

Bug#1002453: logcheck: [logcheck-database] rules for opensmtpd

On Wed, 22 Dec 2021 11:08:09 +0100 Amadego wrote: > These are a proposal for escluding lines that are not harmful: > > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ smtpd\[[[:digit:]]+\]: > [[:xdigit:]]{16} mta (connecting|connected|disconnected|tls ciphers=).*$ > ^\w{3} [ :[:digit:]]{11}

Bug#625894: logcheck-database: /etc/logcheck/ignore.d.server/spamd regexp broken, triggered by unusual Message-Id

On Thu, 09 May 2013 14:49:29 -0700 Gerald Turner wrote: > Gerald Turner writes: > > Hello, there are a few commas that are out of place in one of the > > spamassassin expressions: > > FYI, but is still present in logcheck-database 1.3.15 (wheezy). (hello again) It looks like the spamd rules

Bug#590674: [logcheck-database] rules for atftpd

On Wed, 28 Jul 2010 13:47:53 +0200 Hendrik Jaeger wrote: > Package: logcheck-database > We use these rules for atftpd messages: > > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ atftpd\[[[:digit:]]+\]: > timeout: retrying...$ ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ > atftpd\[[[:digit:]]+\]: Fetching

Bug#925248: /etc/logcheck/ignore.d.server/postfix: update rule for log message written when TLS connection is established

On Fri, 22 Mar 2019 03:41:03 +0900 Yasuhiro KIMURA wrote: > There is following rule in ignore.d.server/postfix. > > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ postfix/smtpd?\[[[:digit:]]+\]: > ((Anonymous|Trusted|Verified) )?TLS connection established (to|from) > [^[:space:]]+:

Bug#547774: dovecot-related rules against logcheck

Hi, logcheck has several old bugs suggesting new rules for dovecot. It's a pitty no-one replied, but let's change that now. Unfortuntely, the patches in these bugs do not cleanly apply to the latest version. I had a look at updating but not being a dovecot user akes it less thn feasible Is

Bug#1070440: mesa-va-drivers: vaapi cannot find target for triple amdgcn

This must have been because of a local installation of self compiled Mesa that I thought I couldn't get to be used by programs. Removing it solved the issue. Case closed, sorry about that.

Bug#1072105: /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring.

On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi wrote: > On Tue, 28 May 2024 17:44:54 +0200 Michael Biebl > > Please do not not ship conflicting configuration for /run/lock > > > > /usr/lib/tmpfiles.d/debian.conf:d /run/lock1777 root root - - > > /usr/lib/tmpfiles.d/legacy.conf:d

Bug#987971: (for post boomworm)

control: tags -1 wontfix control: retitle -1 remove logcheck user on purge Tagging wontfix: debian policy is to not remove system users, since they may still open files

Bug#401259: logcheck: logcheck needs to override locale for grep

On Sat, 3 Apr 2010 02:07:20 +0400 Dmitry Semyonov wrote: > Another reason to set LC_ALL=C is grep slowness in UTF-8 locale. > Depending on used patterns, I saw "grep -E" to be 6 times slower > compared to C locale, and I guess this was not the worst case. The > performance problem seems to be

Bug#198762: logcheck: Rewriting log lines to be more easily human readable

On Wed, 25 Jun 2003 10:35:02 -0400 Erik Jacobson wrote: > While looking through a few pages worth of FTP logs and other such > things in my logcheck reports, I would think that many people might find > the ability to have rewrite rules for logcheck. It would enable > administrators to sift out

Bug#690145: bad rule in ignore for saslauthd (patch included)

On Wed, 10 Oct 2012 09:24:26 -0400 CJ Fearnley wrote: > File: /etc/logcheck/ignore.d.server/saslauthd > The following patch fixes a bug in the regex for ignoring > useless lines from saslauthd authentication failures > (/etc/logcheck/ignore.d.server/saslauthd) on this Squeeze system: > >

Bug#617232: logcheck: ignore regexes match ipv4 addresses only, causing false positives with ipv6 addresses.

On Mon, 07 Mar 2011 11:19:04 + "Benjamin M. A'Lee" wrote: > Various files under ignore.d.* use "[0-9.]{7,15}" to match an IPv4 > address, e.g., a connection to rsyncd. However, this does not match > IPv6 addresses, causing spurious reports. > > A better regexp might be something like:

Bug#1071501: Linux NFS client hangs in nfs4_lookup_revalidate

Dear Neil, I was running it on arm64, may that be the reason? Regards, Richard On May 27, 2024 4:02:32 AM GMT+02:00, NeilBrown wrote: >On Sun, 26 May 2024, Richard Kojedzinszky wrote: >> Dear Neil, >> >> According to my quick tests, your patch seems to fix this bug. Coul

Bug#1071501: Linux NFS client hangs in nfs4_lookup_revalidate

Dear Neil, According to my quick tests, your patch seems to fix this bug. Could you also manage to try my attached code, could you also reproduce the bug? Thanks, Richard 2024-05-24 07:29 időpontban Richard Kojedzinszky ezt írta: Dear Neil, I've applied your patch, and since

Bug#1071501: Linux NFS client hangs in nfs4_lookup_revalidate

Dear Neil, I've applied your patch, and since then there are no lockups. Before that my application reported a lockup in a minute or two, now it has been running for half an hour, and still running. Thanks, Richard 2024-05-24 01:31 időpontban NeilBrown ezt írta: On Fri, 24 May 2024

Bug#1071501: Linux NFS client hangs in nfs4_lookup_revalidate

Dear Neil, I've stripped the code more, which still triggers the bug for me. On Bookworm, to get the binary, simply: $ sudo apt-get install golang $ go build . And then give it an nfs mountpoint, e.g.: $ ./ds /mnt/nfs Meanwhile, I will try your patch too. Regards, Richard 2024-05-24 01

Bug#761813: grep and locales

On Tue, 14 Mar 2023 10:19:19 -0400 Simon Deziel wrote: > On 2023-03-14 08:49, Richard Lewis wrote: > > On Mon, 13 Mar 2023, 12:36 Simon Deziel, wrote: > > > >> egrep still consumes a lot of memory for me. A workaround I've been > >> using is to add th

Bug#630721: logcheck: improve support for non-POSIX charsets in generated report

On Thu, 16 Jun 2011 16:38:49 +0200 Nenad Cimerman wrote: TLDR: some time in the last 15 years, this bug against logcheck has been fixed, as far as i can tell > My system is setup with non-POSIX default locale (see below), using UTF-8 > character encoding. > This leads to many lines inside

Bug#1071501: Linux NFS client hangs in nfs4_lookup_revalidate

file operations, which will trigger a lockup in a few minutes. Please take a look at it. Thanks in advance, Richard 2024-05-23 14:12 időpontban Richard Kojedzinszky ezt írta: Dear devs, Now bisecting turned out that 3c59366c207e4c6c6569524af606baf017a55c61 is the bad commit for me. Strangely

Bug#1071501: Linux NFS client hangs in nfs4_lookup_revalidate

/trigger the issue. It even could be stripped down to minimal operations to trigger the bug. Thanks in advance, Richard 2024-05-23 09:10 időpontban Richard Kojedzinszky ezt írta: Dear NFS developers, I am running multiple PODs on a Kubernetes node, they all mount different NFS shares from

Bug#1071501: Linux NFS client hangs in nfs4_lookup_revalidate

on FreeBSD 13.3. Thanks in advance, Richard ds.tar Description: Unix tar archive

Bug#1071501: linux-image-6.1.0-21-arm64: Linux NFS client hangs in nfs4_lookup_revalidate

, and I did not find anything related to NFS. Regards, Richard 2024-05-20 21:07 időpontban Salvatore Bonaccorso ezt írta: Hi Richard, On Mon, May 20, 2024 at 09:27:24AM +, Richard Kojedzinszky wrote: Package: src:linux Version: 6.1.90-1 Severity: normal X-Debbugs-Cc: richard+debian+bugrep

Bug#1071556: Acknowledgement (Dvorak keymap not loaded after login)

I've reported this issue to the upstream project at https://github.com/neutrinolabs/xrdp/issues/3081 Ubuntu's version 0.9.24-4 in 24.04/noble is likewise affected.

Bug#1071556: Dvorak keymap not loaded after login

Package: xrdp Version: 0.9.24-5 Severity: important Recently, I have noticed that logging in via a recent version of xrdp, while using the Dvorak layout on the client, yields a QWERTY layout in the remote framebuffer after getting past the login dialog. This is incorrect behavior and has never

Bug#1071426: logcheck-database: smartd: Match nvme lines too

On Sun, 19 May 2024 at 05:06, Stefanos Harhalakis wrote: > See attached patch for matching NVMe devices too in smartd logs Thanks - yes i'd noticed that the rules for smartd need an update and this is on the radar - however, the update to the names of the .state files i was not aware of! I

Bug#1071377: chkrootkit: File name including a quote mark throws script off

On Sat, 18 May 2024 at 08:39, Shai Berger wrote: > This morning, when chkrootkit made its daily run, I had > in /tmp a file named: 'חברת חשמל לישראל בע"מ - חשבון דו חודשי.pdf' > (the single quote marks on the edges are not part of the name, but > the double quote mark in the middle is) > > This

Bug#1071501: linux-image-6.1.0-21-arm64: Linux NFS client hangs in nfs4_lookup_revalidate

Package: src:linux Version: 6.1.90-1 Severity: normal X-Debbugs-Cc: richard+debian+bugrep...@kojedz.in Dear Maintainer, I am running kubernetes on debian, and pods are mounting multiple nfs shares. I am running dovecot processes in PODs, which receive mails from the internet, and also serves

Bug#358965: RE: bash: Please support setting terminal title for screen

On Sun, 4 May 2014 22:33:23 +1000 Scott Leggett wrote: > I just spent half an hour figuring out how to get window titles to > reflect my session in byobu.. and I find the exact patch required is > already here (thanks Josh). > > I guess this is just a +1 for patching skel.bashrc so that ssh-ing

Bug#625895: logcheck-database: /etc/logcheck/ignore.d.server/dovecot rule misses unusual Message-Id

On Fri, 06 May 2011 11:32:03 -0700 Gerald Turner wrote: > Hello, I've seen some legitimate mails with unusual Message-Id headers > that cause logchecks dovecot delivery rule to be bypassed. > > Example: … sieve: msgid=<20110422T2108.GA.(stdi.s...@fsing.rootsland.net>: > stored mail into mailbox

Bug#491127: logcheck: please consider an option which will always check the entire log file

On Sun, 12 May 2024 at 19:57, Marc Haber wrote: > > On Sun, May 12, 2024 at 06:54:59PM +0100, R Lewis wrote: > > On Wed, 16 Jul 2008 23:15:51 +0200 Marc Haber > > wrote: > > > > > It would help with debugging to have an option that causes logcheck to > > > always look through the entire log

Bug#975694: [logcheck-database] stop filtering smartd attribute change events

control: tags -1 + moreinfo thanks On Wed, 25 Nov 2020 13:13:14 +0500 Alex Volkov wrote: > IDK how it was in 2006 when this stupid decision was made, but nowadays > `smartd` has all the needed filtering features in itself, in a case someone > gets "annoyed" by attribute changes. Yeah, sure, it

Bug#862638: logcheck: Please add suricata rules to logcheck

control: tags -1 moreinfo control: severity -1 wishlist thanks On Mon, 15 May 2017 10:42:03 +0200 > I am very happy with logcheck. It is great working and very usefull. However, > it would be nice, if you could add a ruleset for suricata (a successor to the > well known snort IDS), so I get

Bug#735287: logcheck: invent conditional logging

On Tue, 14 Jan 2014 13:33:25 +0100 Arne Wichmann wrote: > There is one thing I would like to have in logcheck for quite a long time > already: > > Invent a mechanism by which a pattern is only mailed (or not mailed) if > another pattern was seen a given time before it (or also possibly after >

Bug#919866: logcheck: Feature request: wildcards in .logfiles pathnames

On Sun, 20 Jan 2019 15:50:55 +0530 Charles Atkinson wrote: > Please consider introducing wildcards into the paths in the .logfiles > configuration files. Perhaps similar to the way they are used in logrotate's > paths. > A use case is when using logcheck to check logs from multiple

Bug#241787: options to seperate hosts and for log compaction would both be nice

> This bug is nearly 20 years old. (It is a shame no-one replied - the links > no longer work and there is not enough info recorded to action) > > Unless anyone is watching and can proivde more info about what the issue > is/was then i suggest we close it. A year later: closing. logcheck can

Bug#302379: dh_installlogcheck installs files as root:root 644, not root:logcheck 640

On Mon, 24 Aug 2009 08:36:21 -0400 =?iso-8859-1?B?RnLpZOlyaWMgQnJp6HJl?= wrote: > On Thu, Mar 31, 2005 at 09:54:34AM -0500, Marc Sherman wrote: > > I reported a bug on a couple clamav packages (302253, 302254) which > > noted that in Sarge, logcheck files are supposed to be root:logcheck > > 640,

Bug#383289: RFE: logtail locking

On Wed, 16 Aug 2006 05:33:26 -0500 bingo wrote: > It would be good if logtail supports locking. I think we need some more information if this bug is to be action-ed. logcheck uses logtail2 now (and syslog is not the default):so perhaps it is not relevant after nearly 20 years (there were other

Bug#750232: logtail2 should not not print the final log entry if it does not end with "\n"

On Mon, 2 Jun 2014 10:25:40 -0700 (PDT) Chris Stromsoe wrote: > logtail2 does not do any sanity checking on the final line of input to > make sure that it is complete and "\n" terminated. If syslog is not set > to flush on every write, it's possible for consecutive runs of logcheck to > get a

Bug#470997: logcheck: allow running w/o locking

On Fri, 14 Mar 2008 21:50:17 -0400 =?utf-8?b?RnLDqWTDqXJpYyBCcmnDqHJl?= < > When testing a checked-out copy of the rulefiles against an old log copy > and sending the output to stdout, I still have to use sudo because > logcheck insists on creating a lockfile. It'd be nice to provide an > option

Bug#470608: work-around for logcheck email charset

On Sat, 16 May 2020 17:12:42 -0700 Wade Richards wrote: > This is regarding Debian bug #47608 "wrong charset in logcheck mail > (charset=unknown-8bit)" > > > The maintainer has closed this bug as 'wontfix', but if an end-user is > looking for a work-around, you can add the following to your >

Bug#1033059: logcheck: NEWS advice how to deal with timestamps in different formats

On Sat, 18 Mar 2023 18:55:25 + Richard Lewis wrote: > On Sat, 18 Mar 2023, 15:12 Holger Levsen, wrote: > > > On Thu, Mar 16, 2023 at 06:00:06PM +, Holger Levsen wrote: > > > aaah, thanks! I only checked > > /usr/share/doc/logcheck/NEWS.Debian.gz &

Bug#583600: ignore individual entries but write summaries

On Fri, 28 May 2010 19:04:17 +0200 Holger Levsen wrote: > I often add logcheck ignore rules for security related events (like ssh login > attemps. etc), cause they are too many and login is protected reasonably > anyway. > > But then I would like to get summaries for some ignored patterns,

Bug#1070972: epiphany-browser fails to render webpages - blank pages

Package: epiphany-browser Version: 46.0-2 Severity: important X-Debbugs-Cc: bug.repor...@mail.sheugh.com Dear Maintainer, A previously installed debian system** was reconfigured via the intallation of debian-12-5 from a dvd. That 'bookworm' installation was updated to 'trixie' almost

Bug#1070717: Acknowledgement (linux-image-6.7.12-amd64: Mediatek mt7921e WiFi fails connecting after hibernation since 6.7.12)

Addendum: this is the output of dmesg related to mt7921e that shows up when this happens: [Th May  9 18:36:50 2024] mt7921e :01:00.0: firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7922_1.bin [Th May  9 18:36:50 2024] mt7921e :01:00.0: ASIC

Bug#1063900: gstreamer1.0-plugins-good: missing Breaks+Replaces: gstreamer1.0-plugins-ugly (<< 1.23)

lugins-ugly:amd64 1.24.3-1 amd64    GStreamer plugins from the "ugly" set Best. Richard

Bug#1049972: Upstream issue

For links, this seems to be https://github.com/rdiff-backup/rdiff-backup/issues/616. Apparently it's expected behaviour.

Bug#1070717: linux-image-6.7.12-amd64: Mediatek mt7921e WiFi fails connecting after hibernation since 6.7.12

ppressed [  435.827471] audit: type=1400 audit(1715094303.003:543): apparmor="ALLOWED" operation="open" class="file" profile="libreoffice-soffice" name="/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-org.kde.dolphin-6145.sco

Bug#1070671: Please include static library builds in libharfbuzz-dev

Package: libharfbuzz-dev Version: 8.3.0-2+b1 It is customary for -dev packages to provide static archive libraries in addition to the bare .so files for shared-library linking. The current version of libharfbuzz-dev only provides the latter, and thus does not allow applications to statically link

Bug#1070669: Please include a static library build in libdav1d-dev

Package: libdav1d-dev Version: 1.4.1-1 It is customary for -dev packages to provide a static archive library in addition to the bare .so file for shared-library linking. The current version of libdav1d-dev only provides the latter, and thus does not allow applications to statically link the

Bug#1070483: btrfs root volume being mounted as ro upon boot

Package: installation-reports Severity: important Boot method: USB stick Image version: https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-12.5.0-amd64-gnome.iso Date: 19.04.2024 Machine: Framework 16 Processor: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Memory: 2

Bug#1070281: logcheck: becomes less and less usable because of user-level logs

On Fri, 3 May 2024, 12:44 Francesco Potortì, wrote: > > > One cure would be to have logcheck ignore user-level messages, and only > care about system-level ones. Is that possible? > > > >maybe it is possible - how do you define "system-level message"? > > Those created by root-owned processes,

Bug#1070436: autopkgtest-virt-schroot: error when using 'unshare --net' even though schroot allows this

control: close 1070436 thanks On Sun, 5 May 2024, 19:10 Jochen Sprickerhof, wrote: > Hi Richard, > > * Richard Lewis [2024-05-05 11:32]: > >If i try and run tests that use 'unshare --net' with a > >schroot backend they fail inside autopkgtest even though > >this work

Bug#1070440: mesa-va-drivers: vaapi cannot find target for triple amdgcn

Package: mesa-va-drivers Version: 24.0.6-1+b1 Severity: important Dear Maintainer, I'm not sure if this is the right package to report this issue to, as there recently have been many package updates due to the time_t transition. But mpv, VLC and Firefox are no longer able to access VA-API while

Bug#1070436: autopkgtest-virt-schroot: error when using 'unshare --net' even though schroot allows this

Package: autopkgtest Version: 5.28 Severity: normal X-Debbugs-Cc: richard.lewis.deb...@googlemail.com Dear Maintainer, If i try and run tests that use 'unshare --net' with a schroot backend they fail inside autopkgtest even though this works in the schroot being used. This works fine in a

Bug#1070281: logcheck: becomes less and less usable because of user-level logs

control: reassign -1 logcheck-database thanks (this is mostly about logcheck-database) On Fri, 3 May 2024, 09:39 Francesco Potortì, wrote: > > > Starting maybe a couple years ago, logcheck spits an amount of stuff that > has now become unamnageable. logcheck-database was mostly dormant sround

Bug#1070152: chkrootkit: duplicate line from ifpromisc

On Thu, 2 May 2024, 03:45 Vincent Lefevre, wrote: > On 2024-05-01 19:05:06 +0100, Richard Lewis wrote: > > I agree that you should be able to filter out duplicate lines. And i > think > > this is possible with a custom filter. > > Yes, but "sed" may not b

Bug#1015201: logcheck: Update patterns, here: rsyslogd

lOn Mon, 29 Apr 2024, 14:19 Helge Kreutzmann, wrote: > Am Sat, Apr 27, 2024 at 07:11:40PM +0100 schrieb Richard Lewis: > > On Sun, 17 Jul 2022 17:28:11 +0100 Richard Lewis > > wrote: > > > Hi Helge. Apologies no-one has replied to this bug report for 2 years > &g

Bug#1070152: chkrootkit: duplicate line from ifpromisc

On Wed, 1 May 2024, 00:57 Vincent Lefevre, wrote: > On 2024-05-01 01:29:10 +0200, Vincent Lefevre wrote: > > For instance, /var/log/chkrootkit/log.expected contains > > > > WARNING: Output from ifpromisc: > > lo: not promisc and no packet sniffer sockets > > : PACKET >

Bug#1068161: Video playback regression

Hi Andres, On Tue, 2024 Apr 30 02:42-04:00, Andres Salomon wrote: > Please let me know if this is still broken with chromium 124. I'm happy to report that the issue appears to be resolved in the current 124.0.6367.78-1~deb12u1. (I did not test 124.0.6367.60.) Some additional info that I meant

Bug#1070109: fakechroot: apt crashes inside fakechroot

Package: fakechroot Version: 2.20.1+ds-17 Severity: important X-Debbugs-Cc: ri...@paraeasy.ch Dear Maintainer, We use fakechroot for building a live OS that starts out with debootstrap. This worked fine for a while, but started to fail last week. Now apt crashes when it ties to download

Bug#409444: logcheck: ignore "last line repeated $n times" if prevline matched

On Sat, 03 Feb 2007 10:29:38 +0100 Jonas Koelker wrote: > I (think I) want to see how many times the messages I care about are > repeated. This means I can't ignore "last line repeated $n times" > messages (obviously). But since those can also occur after messages > that are ignored, I can't

Bug#690608: logcheck-database: consider to add ignore.d.server/rrdcached

On Tue, 16 Oct 2012 03:14:20 +0200 Sebastian Steinhuber wrote: > Dear Maintainer, > to drop (slightly boring) messages from the package rrdcached of the > form: > Oct 15 22:59:29 dds rrdcached[12045]: flushing old values > > I added a file named ignore.d.server/rrdcached, containing the line: >

Bug#442244: [Logcheck-devel] Bug#442244: logcheck-database: should include the filters from cyrus-imapd-2.2

On Fri, 14 Sep 2007 14:06:58 +0200 martin f krafft wrote: > also sprach Alex Prinsier [2007.09.14.1344 > +0200]: > > Please copy over the filters from cyrus-imapd-2.2. I'm running > > logcheck on a loghost, which doesn't run cyrus itself. There might > > be a better alternative to copying the

Bug#588312: [Logcheck-devel] Bug#588312: logcheck-database: updated rules for many packages

Closing this bug from 2010 (14 years ago!) -- the then-maintainer found that most of the suggestions were either already present or should not actually be added, for various reasons. A requested was made to resubmit as more independent bugs - if that was done, we dont need this bug, and if not

Bug#511483: logcheck-database: please add rules for rkhunter

package: logcheck-database # think it's reasonable to add rkhunter rules - although the ones in this bug need updates severity 511483 normal tags 511481 - wontfix

Bug#592365: logcheck: ignore rules for transmission-daemon

On Tue, 10 Aug 2010 10:28:54 +1000 Nemo wrote: > > ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ > > transmission-daemon\[[[:digit:]]+\]: Saved > > "/var/lib/transmission-daemon/info/.*" \(bencode.c:1651\)$ > > ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ transmission-daemon\[[0-9]+\]: .* DHT > > announce

Bug#1015201: logcheck: Update patterns, here: rsyslogd

On Sun, 17 Jul 2022 17:28:11 +0100 Richard Lewis wrote: > > The pattern for rsyslogd can be improved. Please add the following > > line: > > > > imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' \(fd 3\) from > > systemd. \[v8.2206.0\] > > >

Bug#532719: [Logcheck-devel] Bug#532719: additional sample

On Tue, 16 Jun 2009 11:27:57 -0700 Russ Allbery wrote: > chrysn writes: > touch /etc/default/locale will also make these go away with no behavior > changes. In my experience, it happens on systems upgraded from older > versions of Debian but not with new installs. I think this is more a > bug

Bug#510472: logcheck-database: pam_unix messages could be ignored.

On Tue, 18 Aug 2009 20:24:31 -0400 =?iso-8859-1?B?RnLpZOlyaWMgQnJp6HJl?= wrote: > On Fri, Jan 02, 2009 at 10:21:51AM +0100, Jan Evert van Grootheest wrote: > > Package: logcheck-database > > Version: 1.2.68 > > > > It has now started to spam the logs with lots of > > Jan 2 09:22:57 sisko

  1   2   3   4   5   6   7   8   9   10   >