Re: Package policy?

[Charles Kroeger]

It's the Lord's will Hans, you have to accept it. Follow the prophet sid.

-- 
Deo Soli Debianea Invicto Seculari

Xorg.0.log inflating possibly due to 'client bug: Invalid path /dev/input/eventxx'

[Martin Gagnon]

Hello,

I have set up 40 identical systems with Debian 12.0: same SBC, same OS
version, same preseed file. These systems use a touchscreen monitor with an
eGalax USB controller. eGalax driver was installed on all of the 40 systems
and everything works fine except for 2 systems that are connected to an Elo
USB touchscreen monitor. These 2 systems log continuously in Xorg.0.log
filling up the hard drive at a rate of ~1MB/min. Please see attached file
for an excerpt of the content dumped into Xorg.0.log.

Can anyone help me understand what's happening and how to fix/prevent this?

Do not hesitate to request additional information if that can help.
Kindly let me know if this should be posted on some other list.

Thank you,
Martin


system-09.Xorg.0.log
Description: Binary data

Re: Weird messages on logs.

[Henning Follmann]

On Tue, Aug 08, 2023 at 03:12:59PM -0400, Maureen L Thomas wrote:
> 
Thanks for not top posting. I fixed it for you...

> On 8/8/23 7:57 AM, Henning Follmann wrote:
> > On Tue, Aug 08, 2023 at 12:01:08AM -0400, Maureen L Thomas wrote:
> > >  3:24:29 PM systemd: Failed to start tracker-extract-3.service - Tracker
> > > metadata extractor.
> > >  3:24:29 PM systemd: Failed to start tracker-extract-3.service - Tracker
> > > metadata extractor.
> > >  3:23:59 PM systemd: Failed to start tracker-extract-3.service - Tracker
> > > metadata extractor.
> > >  3:23:29 PM systemd: Failed to start
> > > app-gnome-gnome\x2dkeyring\x2dsecrets-1958.scope - Application launched by
> > > gnome-session-binary.
> > >  3:23:29 PM systemd: Failed to start
> > > app-gnome-gnome\x2dkeyring\x2dpkcs11-1959.scope - Application launched by
> > > gnome-session-binary.
> > > 
> > >   These are the message I have in my logs.  I have no idea what it is 
> > > about.
> > > I would appreciate any help from you guys.
> > > 
> > > Thanks
> > > 
> > > Moe
> > 
> > Hello,
> > what release is this on?
> > On Buster I had also some issues with tracker mainly due to apparmor
> > missing some rules. I have not seen this so far on Bullseye.
> > -H
> > 
> Sorry, it was late when I posted this.  I am using Bookworm and checked the
> log not figuring on finding anything and found this. My system has been
> upgrade to the last fixes.  I am using a Lanova all in one machine.
> 
> Moe
> 

Ok does this error persist?
If the indexer is done and pretty much only has to index new stuff,
hopefully this resolves on its own.

However if this persists there might be a timing issue here.
You could use dconf-editor to tweak the tracker. 
You can install dconf-editor which might be easier than changing is on the
command line via gsettings.

The settings are presentent as a tree and you would be interestedin
org.freedesktop.tracker 
there should be a setting like "wait for extractor-fs"
Try to switch that on.

HTH

-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Weird messages on logs.

[Maureen L Thomas]

Sorry, it was late when I posted this.  I am using Bookworm and checked 
the log not figuring on finding anything and found this. My system has 
been upgrade to the last fixes.  I am using a Lanova all in one machine.


Moe

On 8/8/23 7:57 AM, Henning Follmann wrote:

On Tue, Aug 08, 2023 at 12:01:08AM -0400, Maureen L Thomas wrote:

 3:24:29 PM systemd: Failed to start tracker-extract-3.service - Tracker
metadata extractor.
 3:24:29 PM systemd: Failed to start tracker-extract-3.service - Tracker
metadata extractor.
 3:23:59 PM systemd: Failed to start tracker-extract-3.service - Tracker
metadata extractor.
 3:23:29 PM systemd: Failed to start
app-gnome-gnome\x2dkeyring\x2dsecrets-1958.scope - Application launched by
gnome-session-binary.
 3:23:29 PM systemd: Failed to start
app-gnome-gnome\x2dkeyring\x2dpkcs11-1959.scope - Application launched by
gnome-session-binary.

  These are the message I have in my logs.  I have no idea what it is about.
I would appreciate any help from you guys.

Thanks

Moe


Hello,
what release is this on?
On Buster I had also some issues with tracker mainly due to apparmor
missing some rules. I have not seen this so far on Bullseye.
-H

Re: BAD signature from "Debian CD signing key [RESOLVED]

[Jeffrey Walton]

On Tue, Aug 8, 2023 at 11:18 AM Matthieu Roquejoffre
 wrote:
>
> On 2023-08-08 at 03:37 p.m., Juan R.D. Silva wrote:> The problem is
> resolved. My fault. :-).
> Could you please explain to us what the cause of your issue was and how
> you solved it ?
> This could be useful for anyone facing a similar issue.

When I read that, I thought the same thing. Then I remembered he was
using GnuPG, which is a raging dumpster fire. Any problems with gpg
can be traced back to its awful usability. It was not OP's fault;
rather it was gpg's fault.

> Relevant xkcd: https://xkcd.com/979/

++

Jeff

Re: logging no longer standard?

[tomas]

On Tue, Aug 08, 2023 at 10:33:04AM -0400, gene heskett wrote:
> On 8/8/23 00:51, to...@tuxteam.de wrote:

[...]

> > See, if you "do" AppImages you are multiplying your system's complexity.

[...]

> And that's sad, Tomas.  The current, nominally 7 day old AppImage of
> OpenSCAD can load and render a complex gfx design in seconds [...]

It may be, but that's how things are in life: you can chose between
solid, stable and tested *and* playing well with the rest of the
system -- or new & shiny, with the latest bells, whistles and the
occasional built in fireworks. The latter is called "bleeding edge"
for a reason.

Engineering tradeoffs and that.

[I skimmed the rest of your post but decided to leave it at that:
I can't deal with that many things at once]

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Package policy?

[Brad Rogers]

On Tue, 08 Aug 2023 16:24:45 +0200
Hans  wrote:

Hello Hans,

>I can only guess, the package maintainers removed it, because it did
>not work somewhow, but why then put it back again?

They didn't put it back.  It was never removed from Sid (things rarely
are)[1].  It was removed from Testing in Oct 2022 due to having
dependency issues (they can't be satisfied). Because of that removal,
the package isn't in the current Debian release - Bookworm.

See; https://tracker.debian.org/pkg/roger-router
Which has a pointer to the bug report;
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019303
The final line of the reply reads (in part)
  "This is going to be ... fun"
by which I assume they mean "A lot of work".

[1]  It's Sid - EXPECT breakage at some point.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
Is she really going out with him?
New Rose - The Damned


pgpqjSjdgo9qB.pgp
Description: OpenPGP digital signature

Re: BAD signature from "Debian CD signing key [RESOLVED]

[Matthieu Roquejoffre]

On 2023-08-08 at 03:37 p.m., Juan R.D. Silva wrote:> The problem is 
resolved. My fault. :-).
Could you please explain to us what the cause of your issue was and how 
you solved it ?
This could be useful for anyone facing a similar issue.

Relevant xkcd: https://xkcd.com/979/

-- 
Matthieu Roquejoffre 
Fingerprint: 0591 eccd 7f11 454b eb7f e81c b3dc 5a41 7fe4 5f42

Re: Package policy?

[Tixy]

On Tue, 2023-08-08 at 16:24 +0200, Hans wrote:
> Hi folks, 
> 
> sometimes I do not understand, how debian is handling packages. Here is 
> another weired case.
> 
> Package roger-router: available in bullseye, NOT available in bookworm, but 
> again available in sid???

Probably because it had a critical bug that did get fixed in time for
the Bookworm release so it was removed from Bookworm. It probably was
ever removed from sid, just Bookworm when it was 'testing'.

> 
> I can only guess,

You don't have to guess, you can look at the package tracker...
https://tracker.debian.org/pkg/roger-router

>  the package maintainers removed it, because it did not work 
> somewhow, but why then put it back again?

It's not been put back again, it's still not in 'testing' because it's
been broken for nearly a year. The package tracker shows it's history,
looks like one of the libraries it depends on isn't present in the
correct version.

-- 
Tixy

Re: logging no longer standard?

[gene heskett]

On 8/8/23 00:51, to...@tuxteam.de wrote:

On Mon, Aug 07, 2023 at 05:32:03PM -0400, gene heskett wrote:

[...]


Ohhhkaaay, but why then do I get a message if looking at the journal as user
1000, that the user must be a member of the adm group to see all the log,


...unless you use sudo.


AND adding me to the adm group doesn't change what I can see using sudo?  I


As sudo you can see *all* (I don't know a lot about systemd's journal, but

I do some sysadmin for food, and the boxes at work do systemd, so the basic
knowledge is there. And the above belongs to the basic knowledge.

Now let's be scientific: what evidence makes you assume that there's anything
in the logs you are not shown?


see gigabytes of stuff from kwin etc, but nary a syllable from what isn't
working because something blocks it.


Perhaps "what isn't working" isn't logging to the syslogs at all? (this
hunch has come up elsewhere in this thread). Another possibility: it is
in the logs, but hidden under so much stuff that you don't see it.


And neither does grep.


See, if you "do" AppImages you are multiplying your system's complexity.
Each AppImage is like a little operating system (without the kernel) where
the application provider dictates the rules, not Debian (that's why I
avoid them like the plague).


And that's sad, Tomas.  The current, nominally 7 day old AppImage of 
OpenSCAD can load and render a complex gfx design in seconds. the repo 
version, dated from 2021, takes around an hour. You are missing out on 
some seriously improved code. ditto for cura and digikam. Running 
kiauh.sh at least weekly does the job of keeping klipper, mainsail and 
moonraker for 3d printing uptodate, its working great but is being 
developed daily. Klipper is learning how to drive a printer fast w/o 
making its frame ring like a bell, which you see as ripples in the 
surface of something printed after some feature of the print has changed 
the direction of the print heads travel. And because it is all web 
based, I can run that printer from a web browser on any other machine on 
my local net and watch the print being built in real time w/o a camera. 
All the heavy lifting is being done on an $85 bananapi. If and when I 
get done with the current rebuilds in progress, there will be 5 
bananapi's running a 5 printer farm.  There are already 4 other machines 
here running the master version of linuxcnc which will in time become 
linuxcnc v3.0.  If I don't miss roll call first. Parts are being made on 
one printer to fix the others.


Cheers


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Package policy?

[Hans]

Hi folks, 

sometimes I do not understand, how debian is handling packages. Here is 
another weired case.

Package roger-router: available in bullseye, NOT available in bookworm, but 
again available in sid???

I can only guess, the package maintainers removed it, because it did not work 
somewhow, but why then put it back again?

And if doing so, i.e. for testing purposes, why not doing so with other 
packages, which were removed (for example webmin and usermin, which were never 
retested again)?

The ways of package maintainers and the Lord are impervious.

Have fun!

Hans

Re: /etc/resolv.conf changes every booting time

[Eduardo M KALINOWSKI]

On 07/08/2023 23:45, gene heskett wrote:

On 8/7/23 21:47, Greg Wooledge wrote:

Start a new thread, and treat the problem seriously.  Show us the
commands you're running and their output.  Show us the relevant
parts of your configuration.

That particular problem has been solved, Greg, and 60 days later there's 
no way I can recreate all that.


There is at my age some considerable truth in the remark that I can't 
remember what I had for breakfast or if I even had any.  It might be 
funny to the younger folks here, until they can't recall it either...



Don't just tack it onto a different thread and make vague statements.
That won't solve anything.


Go back and look at me vs digikam. 

> [snip]

He just told you to not hijack threads, and there you go and your 
immediate reply is to start talking about something completely unrelated 
to the rest of the discussion.


--
If little else, the brain is an educational toy.
-- Tom Robbins

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: logging no longer standard?

[gene heskett]

On 8/7/23 23:17, Greg Wooledge wrote:

On Mon, Aug 07, 2023 at 10:57:41PM -0400, gene heskett wrote:

On 8/7/23 22:08, Max Nikulin wrote:

I have no idea which way you may break journald and why you have not
just installed rsyslog yet if you trust it more and have a hope to find
there more info than in journalctl output. journalctl has a number
option for filtering: per unit, --system, --user, etc.


Show me anyplace in the man page where "--user" occurs, please. Its not
there in my man page.


unicorn:~$ man journalctl | grep -- --user
--user, --system, --directory, and --file options, see below.
--system, --user
Show messages from service of current user (with --user). If
The --user option affects how --unit arguments are treated. See
With --user, all --unit arguments will be converted to match user
messages as if specified with --user-unit.
--user-unit=
troff: :1187: warning [p 13, 6.3i]: can't break line

That's 7 instances in my man page, although some of those are apparently
part of "--user-unit".

Of course, all of this is a gigantic red herring.  If you have a problem
with something called an "AppImage", whatever the hell that is, the
details are not likely to show up in system logs.

If you don't like journalctl and related things, install rsyslog.  It
will take less than a minute, and then your system logging will be back
to normal.  You can read the files in /var/log/ just like always.

Meanwhile, you will need to find out where your "AppImage" thing is
actually logging, if indeed it does ANY kind of logging at ALL.  It's
probably not using syslog().  Ask people who use the thing in question.
Those people may or may not be on debian-user.

There are rather copius msgs output to the shell windows that launch 
them, Connecting those msgs to the name of a package to install to fix 
that, doesn't seem possible.  It will name a function call that reports 
the error, but not the package containing that function.


digikam for example, does report what I assume is the package name, just 
running it, reports a couple screens full of Exiv2 errors, but Exiv2 is 
installed. It cannot write to my raid. Shotwell just does it, but in a 
format digikam can't see, buried in a directory structure based on the 
date/time it was done. Less than helpful.


Thanks Greg.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Weird messages on logs.

[Henning Follmann]

On Tue, Aug 08, 2023 at 12:01:08AM -0400, Maureen L Thomas wrote:
>  3:24:29 PM systemd: Failed to start tracker-extract-3.service - Tracker
> metadata extractor.
>  3:24:29 PM systemd: Failed to start tracker-extract-3.service - Tracker
> metadata extractor.
>  3:23:59 PM systemd: Failed to start tracker-extract-3.service - Tracker
> metadata extractor.
>  3:23:29 PM systemd: Failed to start
> app-gnome-gnome\x2dkeyring\x2dsecrets-1958.scope - Application launched by
> gnome-session-binary.
>  3:23:29 PM systemd: Failed to start
> app-gnome-gnome\x2dkeyring\x2dpkcs11-1959.scope - Application launched by
> gnome-session-binary.
> 
>  These are the message I have in my logs.  I have no idea what it is about. 
> I would appreciate any help from you guys.
> 
> Thanks
> 
> Moe


Hello,
what release is this on?
On Buster I had also some issues with tracker mainly due to apparmor
missing some rules. I have not seen this so far on Bullseye.
-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: logging no longer standard?

[Henning Follmann]

On Mon, Aug 07, 2023 at 05:32:03PM -0400, gene heskett wrote:
> On 8/7/23 13:23, Henning Follmann wrote:
> > On Mon, Aug 07, 2023 at 09:41:11AM -0400, gene heskett wrote:
> > > On 8/7/23 07:50, Henning Follmann wrote:
> > > > On Sat, Aug 05, 2023 at 03:12:39PM -0400, Greg Wooledge wrote:
> > > > > On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
> > > > > > On Sat, 5 Aug 2023 15:09:41 +
> > > > > > Andy Smith  wrote:
> > > > > 
> > > > [...]
> > > > > In some cases, the release notes actually do tell you how to get back
> > > > > to normal.
> > > >err,
> > > > "how to get back."
> > > > Normal is the new systemd
> > > > 
> > [deleted rant novella]
> > 
> > Breathe!
> > 
> > Your issues are not solved by or caused by either of journald or rsyslog.
> > These are just writing what is given to them to somewhere.
> > If it is not in the log it's someone else's fault.
> > 
> > -H
> Ohhhkaaay, but why then do I get a message if looking at the journal as user
> 1000, that the user must be a member of the adm group to see all the log,
> AND adding me to the adm group doesn't change what I can see using sudo?  I
> see gigabytes of stuff from kwin etc, but nary a syllable from what isn't
> working because something blocks it.
> 
> Cheers, Gene Heskett.

I have no idea what is going on on your system. The history of this
mailing list is littered with threads where you do things the "Gene" way and
shooting yourself in the foot. I just assume it's another one.

I am out of this subthread.

-H


-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: why dpms in bullseye fails?

[hlyg]

Thank davidson!  i've switched to bookworm.  Thanks anyway!