On 10/08/2023 16:53, gene heskett wrote:
On 8/9/23 21:15, Max Nikulin wrote:
On 08/08/2023 09:57, gene heskett wrote:
dbus-update-activation-environment: error: unable to connect to
D-Bus: Failed to connect to socket /run/user/1000/bus: Connection
refused
...
Try to figure out at which
On 8/9/23 21:24, Max Nikulin wrote:
On 08/08/2023 19:07, gene heskett wrote:
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.
I have an impression that properly built AppImage should
On 8/9/23 21:15, Max Nikulin wrote:
On 08/08/2023 09:57, gene heskett wrote:
Xsession: X session started for gene at Tue 27 Jun 2023 02:58:23 PM EDT
^^^
dbus-update-activation-environment: error: unable to connect to D-Bus:
Failed to
On 08/08/2023 19:07, gene heskett wrote:
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.
I have an impression that properly built AppImage should come with all
necessary libraries
On 08/08/2023 09:57, gene heskett wrote:
Xsession: X session started for gene at Tue 27 Jun 2023 02:58:23 PM EDT
^^^
dbus-update-activation-environment: error: unable to connect to D-Bus:
Failed to connect to socket /run/user/1000/bus:
On 8/9/23 10:47, debian-u...@howorth.org.uk wrote:
gene heskett wrote:
Someplace where an AppImage looking for a missing dependency might
express its displeasure at not finding everything it needs?
I've always thought that was a main advantage of starting anything from
the command line -
gene heskett wrote:
> Someplace where an AppImage looking for a missing dependency might
> express its displeasure at not finding everything it needs?
I've always thought that was a main advantage of starting anything from
the command line - there's an obvious place for the output - the
gene heskett wrote:
>songbird wrote:
...
>>man journald.conf...
>
> I've looked at that, even looked at the file. It is all systemd
> related, no mention of user stuffs. Its as if a 3 meter tall board
> fence has been built around the systemd stuff that user apps can't get thru.
no, i
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
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
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
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 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
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.
On 8/7/23 22:08, Max Nikulin wrote:
On 08/08/2023 00:35, gene heskett wrote:
There is not a way to have it start doing the trace when I click on
the save to disk button.
Really? And certainly --attach/-p option is not a rescue.
Sending output to a file, filtering specific calls, increasing
On 08/08/2023 00:35, gene heskett wrote:
There is not a way to have it start doing the trace when I click on the
save to disk button.
Really? And certainly --attach/-p option is not a rescue.
Sending output to a file, filtering specific calls, increasing per line
size limit are useless
On 8/7/23 20:00, songbird wrote:
gene heskett wrote:
...
I believe konsole is unlimited by default. On checking in settings, its
not listed. Scrollback is from my /tmp, which would be on my raid10, so
maybe that something else that is blocked from useing my raid10. IDK.
ulimit reports
gene heskett wrote:
...
> I believe konsole is unlimited by default. On checking in settings, its
> not listed. Scrollback is from my /tmp, which would be on my raid10, so
> maybe that something else that is blocked from useing my raid10. IDK.
> ulimit reports unlimited. And there is 32G of
On 8/7/23 16:16, songbird wrote:
gene heskett wrote:
...
Many times over the last 25 years. However this problem occurs when it
has already output several gigabytes of previous data the shell has
scrolled off the end of th buffer.. There is not a way to have it start
doing the trace when I
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
gene heskett wrote:
...
> Many times over the last 25 years. However this problem occurs when it
> has already output several gigabytes of previous data the shell has
> scrolled off the end of th buffer.. There is not a way to have it start
> doing the trace when I click on the save to disk
On 8/7/23 12:19, songbird wrote:
gene heskett wrote:
...
Absolutely none of that makes it to the log I can read with sudo.
This causes me to ask about any new ACL's bookworm might have put in
place, but questions about that have so far been totally ignored. I
according to an ls -lR, own that
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
gene heskett wrote:
...
> Absolutely none of that makes it to the log I can read with sudo.
>
> This causes me to ask about any new ACL's bookworm might have put in
> place, but questions about that have so far been totally ignored. I
> according to an ls -lR, own that raid10 lock, stock and
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
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."
On 06/08/2023 02:03, Joe wrote:
I use 'tail -f ' at least
once a week
journalctl -f
Hello,
On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
> On Sat, 5 Aug 2023 15:09:41 +
> Andy Smith wrote:
> > For those of us who do care, installing rsyslog takes seconds.
> > Disabling the systemd journal (if you want to)_ takes another few
> > seconds. This email took longer.
>
>
On Sat, Aug 05, 2023 at 08:03:27PM +0100, Joe wrote:
> On Sat, 5 Aug 2023 15:09:41 +
> Andy Smith wrote:
> > The release notes in particular are essential reading since
> > otherwise a person won't know about major components that have
> > changed, been replaced etc.
>
> Indeed, but they
On Sat, 5 Aug 2023 15:09:41 +
Andy Smith wrote:
> Hello,
>
> On Sat, Aug 05, 2023 at 09:23:25AM -0400, Greg Wooledge wrote:
> > In any case, this is not a popular change.
>
> I don't think that's clear. I think that amongst a population of
> people who care deeply about logging it's
Hello,
On Sat, Aug 05, 2023 at 09:23:25AM -0400, Greg Wooledge wrote:
> In any case, this is not a popular change.
I don't think that's clear. I think that amongst a population of
people who care deeply about logging it's generally unfavourable,
and I myself don't particularly enjoy using
Hello,
On Sat, Aug 05, 2023 at 08:56:36AM -0400, Carl Fink wrote:
> It is highly probable that I'm being grumpy because Debian changed
> something that I was used to for decades, without my realizing it.
…because you didn't read the release notes that are absolutely
required reading to
* 2023-08-05 09:23:25-0400, Greg Wooledge wrote:
> In any case, this [systemd journal] is not a popular change. I don't
> remember ever hearing a single person say "Wow, I'm so glad they did
> this!" I've seen many complaints. Most often, people just (re)install
> rsyslog and move on with their
On 8/5/23 14:56, Carl Fink wrote:
On 8/5/23 02:54, Michel Verdier wrote:
On 2023-08-04, Carl Fink wrote:
Today, on my Bullseye system, X crashed and restarted. Naturally, I thought
I'd check my logs to see if I could find out why.
Well, no ... because syslog does not exist.
If you don't
On Sat, Aug 05, 2023 at 02:12:31PM +0100, Brian wrote:
> Does this clarify?
>
> https://wiki.debian.org/Rsyslog#Deprecation_in_Bookworm
Ah, I didn't know about that page. It links to bug #1018788 which
says, among other things,
The main reason here is, that I want to avoid that log data
On Sat, Aug 05, 2023 at 08:56:36AM -0400, Carl Fink wrote:
> It is highly probable that I'm being grumpy because Debian changed something
> that
> I was used to for decades, without my realizing it. I'm more interested in
> *using* my
> computer than learning whole new paradigms about, say,
On Sat 05 Aug 2023 at 08:56:36 -0400, Carl Fink wrote:
> On 8/5/23 02:54, Michel Verdier wrote:
> > On 2023-08-04, Carl Fink wrote:
> >
> > > Today, on my Bullseye system, X crashed and restarted. Naturally, I
> > > thought
> > > I'd check my logs to see if I could find out why.
> > >
> > >
On 8/5/23 02:54, Michel Verdier wrote:
On 2023-08-04, Carl Fink wrote:
Today, on my Bullseye system, X crashed and restarted. Naturally, I thought
I'd check my logs to see if I could find out why.
Well, no ... because syslog does not exist.
If you don't have syslog your logs will be on
On 2023-08-04, Carl Fink wrote:
> Today, on my Bullseye system, X crashed and restarted. Naturally, I thought
> I'd check my logs to see if I could find out why.
>
> Well, no ... because syslog does not exist.
If you don't have syslog your logs will be on journald.
But X logs could be in
On Fri, Aug 04, 2023 at 10:40:37PM -0400, Carl Fink wrote:
> Today, on my Bullseye system, X crashed and restarted. Naturally, I thought
> I'd check my logs to see if I could find out why.
>
> Well, no ... because syslog does not exist.
>
> Is it really the default to have no/very little logging
Today, on my Bullseye system, X crashed and restarted. Naturally, I
thought I'd check my logs to see if I could find out why.
Well, no ... because syslog does not exist.
Is it really the default to have no/very little logging when using
mostly the default install? (I just installed syslog-ng,
41 matches
Mail list logo
