Hello, I've fixed the plugin by bumping weather API version to 2.0
Patch is attached
--- xfce4-weather-plugin-0.8.10.orig/panel-plugin/weather.c
+++ xfce4-weather-plugin-0.8.10/panel-plugin/weather.c
@@ -619,17 +619,14 @@ update_handler(plugin_data *data)
end_tm = *localtime(_t);
Please, can you explain why this bug is marked as serious?
Regards,
Eriberto
Your message dated Tue, 15 Sep 2020 22:38:17 -0400
with message-id
and subject line Re: cups-browsed.service Hangs on Shutdown
has caused the Debian Bug report #969355,
regarding cups-browsed.service Hangs on Shutdown
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 16 Sep 2020 02:33:27 +
with message-id
and subject line Bug#969795: fixed in 2vcard 0.6-4
has caused the Debian Bug report #969795,
regarding 2vcard: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has been
Package: python
Version: 2.7.17-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kouth...@gmail.com
Dear Maintainer,
What led up to the situation?
```
$ sudo apt-get install python
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package: lilyterm
Version: 0.9.9.4+git20150208.f600c0-5
Severity: grave
Justification: renders package unusable
It appears that lilyterm is unable to start, running lilyterm gives the
following errors:
** Message: 11:20:26.198: Can NOT connect to a existing lilyterm socket!
(lilyterm:4801):
Your message dated Wed, 16 Sep 2020 01:18:26 +
with message-id
and subject line Bug#968630: fixed in html5lib 1.1-2
has caused the Debian Bug report #968630,
regarding html5lib: autopkgtest regression: 995 failed
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> tag -1 pending
Bug #968630 [src:html5lib] html5lib: autopkgtest regression: 995 failed
Added tag(s) pending.
--
968630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #968630 in html5lib reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Étienne Mollier writes:
> Wow, thanks for the comprehensive background information. In
No problem.
> case someone else (me in a not so near future for instance)
> stumbles upon this again, I keep note that reducing the size of
> BLASTDB_LMDB_MAP_SIZE a bit might help:
One final
Package: bind-host
Version: 1:9.13.3-1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The `bind-host` package in experimental is missing both the executable
and the manpage.
esk@esk-xps:~$ dpkg -L bind-host
/.
/usr
/usr/bin
/usr/share
/usr/share/doc
close 936724 3.0.0-1
thanks
This bug was fixed in 3.0.0 when it was ported to python 3. Changes below:
Changes:
ifupdown2 (3.0.0-1) unstable; urgency=medium
.
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with
Processing commands for cont...@bugs.debian.org:
> close 967953 3.0.0-1
Bug #967953 [ifupdown2] Package not installable in sid due to missing
dependencies python-argcomplete and python-ipaddr
Marked as fixed in versions ifupdown2/3.0.0-1.
Bug #967953 [ifupdown2] Package not installable in sid
Processing commands for cont...@bugs.debian.org:
> close 927134 3.0.0-1
Bug #927134 [src:ifupdown2] src:ifupdown2: Please port to python3
Marked as fixed in versions ifupdown2/3.0.0-1.
Bug #927134 [src:ifupdown2] src:ifupdown2: Please port to python3
Marked Bug as done
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> close 936724 3.0.0-1
Bug #936724 [src:ifupdown2] ifupdown2: Python2 removal in sid/bullseye
Marked as fixed in versions ifupdown2/3.0.0-1.
Bug #936724 [src:ifupdown2] ifupdown2: Python2 removal in sid/bullseye
Marked Bug as done
> thanks
Stopping
close 927134 3.0.0-1
thanks
This bug was fixed in 3.0.0 when it was ported to python 3. Changes below:
Changes:
ifupdown2 (3.0.0-1) unstable; urgency=medium
.
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with
close 967953 3.0.0-1
thanks
This bug was fixed in 3.0.0 when it was ported to python 3. Changes below:
Changes:
ifupdown2 (3.0.0-1) unstable; urgency=medium
.
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with
Am 15.09.20 um 22:22 schrieb Joel Rivera:
> Bastian,
>
> correct me if I'm wrong, but you're suggesting to remove [1] in favor of [2]?
That is right.
> I've been trying to update editline to the fork that seems to have been
> evolved from the original debian sources at [3]. My interest in
Your message dated Tue, 15 Sep 2020 22:48:29 +
with message-id
and subject line Bug#970390: fixed in nvidia-graphics-drivers-legacy-390xx
390.138-4
has caused the Debian Bug report #970390,
regarding nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available for
i386
to be marked as
Processing commands for cont...@bugs.debian.org:
> severity 942915 serious
Bug #942915 [src:ca-certificates] ca-certificates: Python2 removal in
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942915:
Forwarded: https://invent.kde.org/pim/akonadi/-/merge_requests/32
Hey,
I have pushed the needed changes to upstream. The AppArmor profile is living
there.
hefee
--
On Samstag, 15. Februar 2020 21:08:15 CEST Bastien Roucariès wrote:
> Package: akonadi-backend-postgresql
> Version: 4:19.08.3-1
Source: aseba
Version: 1.6.0-5
Severity: serious
Tags: bullseye, sid
aseba build-depends on the "python" binary package which is no longer built by the
"python-defaults" source package.
In unstable it is present as a cruft package but said cruft package is
uninstallable due to strictly
Felix Lechner dixit:
>Uploaded, although I am still looking for it on the buildds:
First it must be ACCEPTED, then the dak run for incoming must
run, then B-Ds are checked, then it gets into Needs-Build status,
and only then the buildds pick it up.
It’s there now:
Dixi quod…
>It’s there now: https://buildd.debian.org/status/package.php?p=wolfssl
… and already FTBFSing on s390x:
/usr/bin/ld: src/.libs/libwolfssl.so: undefined reference to `ByteReverseWords'
bye,
//mirabilos
--
[16:04:33] bkix: "veni vidi violini"
[16:04:45] bkix: "ich kam, sah und
Hi Thorsten,
Uploaded, although I am still looking for it on the buildds:
> wolfssl_4.5.0+dfsg-1_source.changes uploaded successfully to localhost
> along with the files:
> wolfssl_4.5.0+dfsg-1.dsc
> wolfssl_4.5.0+dfsg.orig.tar.xz
> wolfssl_4.5.0+dfsg-1.debian.tar.xz
>
Your message dated Tue, 15 Sep 2020 20:48:59 +
with message-id
and subject line Bug#969663: fixed in wolfssl 4.5.0+dfsg-1
has caused the Debian Bug report #969663,
regarding wolfssl: CVE-2020-12457 CVE-2020-15309 CVE-2020-24585 CVE-2020-24613
to be marked as done.
This means that you claim
Processing control commands:
> reassign -1 src:silver-platter 0.3.0+git20200611.b4292bf-1
Bug #969665 {Done: Jelmer Vernooij } [src:breezy-debian,
src:silver-platter] breezy-debian breaks silver-platter autopkgtest: cannot
import name 'MissingUpstreamTarball'
Bug reassigned from package
Control: reassign -1 src:silver-platter 0.3.0+git20200611.b4292bf-1
Control: fixed -1 0.3.0+git20200906.d2bd137-1
Hi Jelmer,
On 15-09-2020 13:18, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:breezy-debian,
On Tue, Sep 15, 2020 at 10:56:22AM +0200, Andreas Tille wrote:
> Hi Moritz,
>
> On Mon, Aug 31, 2020 at 08:59:37PM +0200, Moritz Mühlenhoff wrote:
> > On Fri, Aug 30, 2019 at 07:30:23AM +, Matthias Klose wrote:
> > > Package: src:pbgenomicconsensus
> > > Version: 2.3.2-5
> > > Severity:
Processing control commands:
> close -1 0.2.2-1
Bug #970412 [src:rust-rand-chacha] src:rust-rand-chacha: fails to migrate to
testing for too long: unsatified Build-Depends on s390x
Marked as fixed in versions rust-rand-chacha/0.2.2-1.
Bug #970412 [src:rust-rand-chacha] src:rust-rand-chacha:
Source: rust-rand-chacha
Version: 0.2.1-1
Severity: serious
Control: close -1 0.2.2-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 961335
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are
On Mon, Sep 14, 2020 at 12:17:00AM +0200, Marcos Fouces wrote:
> Hi Moritz!
>
> Yes, i uploaded it to salsa.d.o and i am waiting for Frontdesk aproval
> to become DD (that should happens in a few days) in order to upload it
> myself instead of asking for sponsorship.
>
> Its new home is here:
Bastian,
correct me if I'm wrong, but you're suggesting to remove [1] in favor of [2]?
I've been trying to update editline to the fork that seems to have been evolved
from the original debian sources at [3]. My interest in particular is due to
that is a dependency of the Nix package manager
Source: html5lib
Version: 1.0.1-3
Severity: serious
Control: close -1 1.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 968630
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are
Source: python-uvicorn
Version: 0.11.3-1
Severity: serious
Control: close -1 0.11.5-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing
Processing control commands:
> close -1 0.11.5-1
Bug #970411 [src:python-uvicorn] src:python-uvicorn: fails to migrate to
testing for too long: depends on non-migrating package
Marked as fixed in versions python-uvicorn/0.11.5-1.
Bug #970411 [src:python-uvicorn] src:python-uvicorn: fails to
Processing control commands:
> close -1 1.1-1
Bug #970410 [src:html5lib] src:html5lib: fails to migrate to testing for too
long: autopkgtest regressions
Marked as fixed in versions html5lib/1.1-1.
Bug #970410 [src:html5lib] src:html5lib: fails to migrate to testing for too
long: autopkgtest
Processing control commands:
> close -1 1.31.0-1
Bug #970409 [src:google-http-client-java] src:google-http-client-java: fails to
migrate to testing for too long: depends on non-migrating package
Marked as fixed in versions google-http-client-java/1.31.0-1.
Bug #970409
Source: google-http-client-java
Version: 1.27.0-3
Severity: serious
Control: close -1 1.31.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between
Source: facter
Version: 3.11.0-4.3
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
facter currently fails to build:
| cd /<>/obj-x86_64-linux-gnu/lib && /usr/bin/c++
-DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T
Processing commands for cont...@bugs.debian.org:
> #
> https://buildd.debian.org/status/fetch.php?pkg=cpp-hocon=amd64=0.1.7-1%2Bb3=1599808899=0
> tags 970379 + sid bullseye ftbfs
Bug #970379 [cpp-hocon] FTBFS: cpp-hocon fails to build against boost1.71
Added tag(s) sid, bullseye, and ftbfs.
>
Processing control commands:
> severity 942964 serious
Bug #942964 [src:avw.lv2] avw.lv2: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> forcemerge 942964 -1
Bug #942964 [src:avw.lv2] avw.lv2: Python2 removal in sid/bullseye
Bug #970405 [src:avw.lv2] avw.lv2
Control: severity 942964 serious
Control: forcemerge 942964 -1
On 2020-09-15 20:20:24 +0100, peter green wrote:
> Source: avw.lv2
> Version: 0.1.6~dfsg0-1
> Severity: serious
> Tags: bullseye, sid
>
> avw.lv2 build-depends on the "python" binary package which is no longer built
> by the
Processing commands for cont...@bugs.debian.org:
> severity 968756 important
Bug #968756 [inkscape] inkscape: Inkscape crash on multiple undo-redo actions
Severity set to 'important' from 'critical'
> tags 968756 + help - upstream
Bug #968756 [inkscape] inkscape: Inkscape crash on multiple
Hi Aaron,
Aaron M. Ucko, on 2020-09-14 17:36:14 -0400:
>
> Thanks for clarifying. AFAICT, this environment imposes a tighter limit
> than native arm64 hardware, and versions 2.10.0-1 and 2.10.0-3 both hit
> it. Rough bisection via the BLASTDB_LMDB_MAP_SIZE environment variable
> gives an
Your message dated Wed, 16 Sep 2020 01:05:17 +0530
with message-id
and subject line Re: mrbayes: ftbfs with GCC-10
has caused the Debian Bug report #957564,
regarding mrbayes: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Source: flowcanvas
Version: 0.7.1+dfsg0-0.5
Severity: serious
Tags: bullseye, sid
flowcanvas build-depends on the "python" binary package which is no longer built by the
"python-defaults" source package.
In unstable it is present as a cruft package but said cruft package is
uninstallable due
Processing commands for cont...@bugs.debian.org:
> severity 942960 serious
Bug #942960 [src:catch] catch: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942960:
Source: avw.lv2
Version: 0.1.6~dfsg0-1
Severity: serious
Tags: bullseye, sid
avw.lv2 build-depends on the "python" binary package which is no longer built by the
"python-defaults" source package.
In unstable it is present as a cruft package but said cruft package is
uninstallable due to
Your message dated Tue, 15 Sep 2020 20:03:33 +0100
with message-id
and subject line re: python-coverage: Unversioned Python removal in sid/bullseye
has caused the Debian Bug report #967200,
regarding python-coverage: Unversioned Python removal in sid/bullseye
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> reopen 963827
Bug #963827 {Done: Gianfranco Costamagna }
[src:virtualbox] [virtualbox] guests limited to 800x600
Bug reopened
Ignoring request to alter fixed versions of bug #963827 to the same values
previously set
> severity 963827 important
Your message dated Tue, 15 Sep 2020 20:41:08 +0200
with message-id <160019526899.413201.18322213813565356783@localhost>
and subject line Re: Bug#969331: rviz: [rospack] Error: no such package
media_export
has caused the Debian Bug report #969331,
regarding rviz: [rospack] Error: no such package
Re-opening. This is most certainly *not* fixed.
I have a Debian Sid installation (with a Gnome environment) in a VBox
VM, fully up-to-date, and the problem still exists with this.
When the problem surfaced, I had to restore from backup and place a
hold on kernel and virtualbox-guest-* package
As an update on this, I've gotten acmetool 0.2 to build on buster. The
following packages need backporting:
- golang-github-gofrs-uuid
- golang-golang-x-xerrors
- golang-github-google-go-cmp
- golang-gopkg-square-go-jose.v2
- golang-gopkg-hlandau-acmeapi.v2
- acmetool
The 5 golang-* packages are
Felix Lechner dixit:
>> Is there anything I can help to ensure it’s not autoremoved?
>
>I just saw it this morning and plan to upload 4.5.0 later today. From
>what I understand, closing #969663 should postpone the autoremoval
>process?
Thanks!
The autoremoval will go on until a version with
Hi Thorsten,
> Is there anything I can help to ensure it’s not autoremoved?
I just saw it this morning and plan to upload 4.5.0 later today. From
what I understand, closing #969663 should postpone the autoremoval
process?
Kind regards
Felix
Your message dated Tue, 15 Sep 2020 16:03:40 +
with message-id
and subject line Bug#970232: fixed in mir 1.8.0+dfsg1-8
has caused the Debian Bug report #970232,
regarding mir FTBFS: symbol differences
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Debian testing autoremoval watch dixit:
>polyphone 2.2.0.20200612+dfsg1-1 is marked for autoremoval from testing on
>2020-10-20
>
>It (build-)depends on packages with these RC bugs:
>969663: wolfssl: CVE-2020-12457 CVE-2020-15309 CVE-2020-24585 CVE-2020-24613
> https://bugs.debian.org/969663
Is
Your message dated Tue, 15 Sep 2020 15:18:30 +
with message-id
and subject line Bug#963088: fixed in bppsuite 2.4.1-3
has caused the Debian Bug report #963088,
regarding bppsuite: autopkgtest failure on arm64: precision issue in reference
data
to be marked as done.
This means that you claim
Dear Sascha,
On Tue, Sep 15, 2020 at 04:32:02PM +0200, Sascha Steinbiss wrote:
>
> I can confirm that that was the issue. I have pushed a fix to git and
> will make an upload later if there are no objections.
No objections for fixing a bug at all. ;-)
Thanks a lot
Andreas.
--
Hi all,
>> you once wrote that test. Do you have any idea how to fix it?
>
> Since this is just a warning, it might be sufficient to simply add
>
> Restrictions: allow-stderr
>
> That would make sure that printing a warning to stderr does not cause
> the test to fail. I will test this later
Hi all,
> you once wrote that test. Do you have any idea how to fix it?
Since this is just a warning, it might be sufficient to simply add
Restrictions: allow-stderr
That would make sure that printing a warning to stderr does not cause
the test to fail. I will test this later and fix it if
Processing commands for cont...@bugs.debian.org:
> notfound 970390 nvidia-graphics-drivers-legacy-390xx/390.138-1
Bug #970390 [src:nvidia-graphics-drivers-legacy-390xx]
nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available for i386
No longer marked as found in versions
Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.138-1
Severity: serious
nvidia-graphics-drivers-legacy-390xx 390.138-3 is not available
for i386, so that it cannot even be installed on amd64 with i386
as a foreign architecture.
According to
Processing commands for cont...@bugs.debian.org:
> # fails to install → release critical
> severity 970191 serious
Bug #970191 [bookworm] bookworm: Python3 syntax errors at configure step
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need
Your message dated Tue, 15 Sep 2020 11:18:41 +
with message-id
and subject line Bug#969809: fixed in chafa 1.4.1-2
has caused the Debian Bug report #969809,
regarding chafa: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 15 Sep 2020 11:21:21 +
with message-id
and subject line Bug#957600: fixed in netkit-ftp 0.17-34.1.1
has caused the Debian Bug report #957600,
regarding netkit-ftp: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 15 Sep 2020 11:15:56 +
with message-id <20200915111556.ga3512...@jelmer.uk>
and subject line Fixed in newer silver-platter
has caused the Debian Bug report #969665,
regarding breezy-debian breaks silver-platter autopkgtest: cannot import name
'MissingUpstreamTarball'
Hi,
If anyone wants to take over I'm more than fine with that. The amount of work I
have at the moment barely permits me from maintaining projects. It's most
sensible that someone actively using this project on Debian maintains it, as
is, I'm not using it much anymore and am not working in HPC
Your message dated Tue, 15 Sep 2020 09:33:32 +
with message-id
and subject line Bug#970336: fixed in cl-contextl 1:20200201.git5d18a71-1
has caused the Debian Bug report #970336,
regarding ecl breaks cl-contextl autopkgtest: not of the expected type SYMBOL
to be marked as done.
This means
Hi Sascha,
you once wrote that test. Do you have any idea how to fix it?
Steffen, you know that package. Any idea what to do?
Kind regards
Andreas.
On Mon, Sep 14, 2020 at 10:15:12PM +0200, Paul Gevers wrote:
> Source: rna-star
> Version: 2.7.5c+dfsg-1
> X-Debbugs-CC:
Your message dated Tue, 15 Sep 2020 09:18:26 +
with message-id
and subject line Bug#970335: fixed in cffi 1:0.22.1-2
has caused the Debian Bug report #970335,
regarding ecl breaks cffi autopkgtest: Don't know how to REQUIRE rt..
to be marked as done.
This means that you claim that the
Your message dated Tue, 15 Sep 2020 09:18:32 +
with message-id
and subject line Bug#969596: fixed in minimap2 2.17+dfsg-12
has caused the Debian Bug report #969596,
regarding src:minimap2: fails to migrate to testing for too long: FTBFS on
multiple arches
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> reassign 970336 cl-contextl 1:20160313.git5894fba-1
Bug #970336 [src:ecl, src:cl-contextl] ecl breaks cl-contextl autopkgtest: not
of the expected type SYMBOL
Bug reassigned from package 'src:ecl, src:cl-contextl' to 'cl-contextl'.
No longer
Processing commands for cont...@bugs.debian.org:
> severity 967909 serious
Bug #967909 [src:editline] editline: Please remove in favour of libedit
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
967909:
Processing commands for cont...@bugs.debian.org:
> reassign 970335 cffi 1:0.22.1-1
Bug #970335 [src:ecl, src:cffi] ecl breaks cffi autopkgtest: Don't know how to
REQUIRE rt..
Bug reassigned from package 'src:ecl, src:cffi' to 'cffi'.
No longer marked as found in versions cffi/1:0.22.1-1 and
Hi Moritz,
On Mon, Aug 31, 2020 at 08:59:37PM +0200, Moritz Mühlenhoff wrote:
> On Fri, Aug 30, 2019 at 07:30:23AM +, Matthias Klose wrote:
> > Package: src:pbgenomicconsensus
> > Version: 2.3.2-5
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> >
unsubscribe
On Mon, Sep 14, 2020 at 11:21 PM Paul Gevers wrote:
> Source: rampler
> Version: 1.1.1-2
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
>
> Dear maintainer(s),
>
> You recently added an autopkgtest to your
Your message dated Tue, 15 Sep 2020 10:08:05 +0200
with message-id <816ecdb0-a1be-c34b-4e0b-a94305115...@debian.org>
and subject line Re: [virtualbox] guests limited to 800x600
has caused the Debian Bug report #963827,
regarding [virtualbox] guests limited to 800x600
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> retitle 951508 lmod: broken on all architectures except x86_64 (wrong search
> path)
Bug #951508 [lmod] lmod: wrong search path on PowerPC system
Changed Bug title to 'lmod: broken on all architectures except x86_64 (wrong
search path)' from
Package: syslog-ng
Version: 3.19.1-5
Severity: grave
Dear maintainers,
On amd64, i have following error
==> /var/log/syslog-ng/current_logs/BY_FACILITY.kern.notice.log <==
2020-09-15T08:25:53+02:00 s_dev_kernel_kmsg@asus-190 kernel:
6,35313,87037029084,-;syslog-ng[10311]: segfault at 0
81 matches
Mail list logo
