from:"Frank"





On 1/5/23 13:12, Andrew M.A. Cater wrote:



I am getting close to reinstalling Debian ( shades of Windows) !



Debian sid is unstable by name mostly because of package churn and large
transitions like this. Unfortunately, it's not intended for inexeperienced
users - you are expected to be able to resolve most problems yourself - "if
it breaks, you get to keep both pieces".

Lots of folk go to use sid because they want to be very up to date when
the boringness of Debian stable with security support and defined upgrade
paths is more appropriate for them.

If something is going to update 80 packages at once, try manually using
apt or apt-get to install five at a time - take it more steadily and take
notes of any package breakage, maybe.

Look in the Debian bugs database / the Debian package tracker to see
what bugs have been recorded against lightdm recently.



  I've been running Sid for about 10 years and yes it has broken from 
time to time, but, with some knowledge and a lot of help from the people 
on this list I have always managed to put the two pieces back together.
 At the same time I also run Fedora on another partition which I 
believe is a little more leading edge than Sid. It too breaks time to 
time. And to add to the mix I have just

started running OpenSuse Tumbleweed which  keeps me on
my toes.  I guess I am a bear for punishment.  One day soon I will drop 
two of the three. Until then I appreciate

everyone's help.



With every good wish, as ever,

Andy Cater


Thanks for any help.






--
Frank McCormick

Re: debian sid no boot after this morning's update





On 1/5/23 14:45, Charles Curley wrote:

On Thu, 5 Jan 2023 09:12:58 -0500
Frank  wrote:


    Yes, the file exists and is owned by lightdm. I don't know whether
this is
correct as I can't find any info on who should own it.


It would be more useful to those trying to help you if you showed the
actual results rather than telling us what you find significant. 


   Agreed in retrospect



Like
so:

root@hawk:~# ls -ld /var/lib/lightdm
drwxr-x--- 6 lightdm lightdm 4096 Oct 29  2021 /var/lib/lightdm
root@hawk:~# ls -la /var/lib/lightdm
total 28
drwxr-x---  6 lightdm lightdm 4096 Oct 29  2021 .
drwxr-xr-x 70 rootroot4096 Sep 30 16:10 ..
drwxr-xr-x  7 lightdm lightdm 4096 Oct 29  2021 .cache
drwx--  5 lightdm lightdm 4096 Mar  5  2022 .config
drwxr-xr-x  4 rootroot4096 Dec 19 11:54 data
drwxr-xr-x  3 lightdm lightdm 4096 Oct 29  2021 .local
-rw---  1 lightdm lightdm  686 Jan  5 11:35 .Xauthority
root@hawk:~#

Note that I include the trailing prompt to show that the command ended
rather than that the result was truncated.

This is from a working system which I have rebooted since most of those
dates. You may find it useful to check against your directory.




  I did indeed. In checking what I had there were a couple of 
differences which hadn't seemed to make much difference. But I have 
fixed those now.


I appreciate your help.


--
Frank McCormick

Re: debian sid no boot after this morning's update





On 1/5/23 13:44, Greg Wooledge wrote:

On Thu, Jan 05, 2023 at 06:12:07PM +, Andrew M.A. Cater wrote:

On Thu, Jan 05, 2023 at 09:12:58AM -0500, Frank wrote:


There are other strange things going on which may or not be related. I tried
to
reinstall lightdm and the greeter using apt. (The Debian partition is
mounted
on my Fedora partition) but apt failed saying it could not contact
debian.deb to
gain access to the needed files. I downloaded the files from Fedora and
moved them
to Debian but dpkg said it could not access them !!??



If you're using raw dpkg tp install them - you are root? If using su, it
needs to be su - to get roots login environment.


Unless you create an /etc/default/su file to fix what Debian broke.

unicorn:~$ cat /etc/default/su
ALWAYS_SET_PATH yes

That restores the PATH behavior to how it was before Debian switched
upstream sources for su in buster.

Anyway, it sounded like the OP had some permission/ownership changes
which were breaking things, but they managed to find them and revert
them.  Or some of them.  We'll have to await further details.



  I managed to fix most of the problem permissions, and just now fixed 
the rest with the help of Charles Curley's posting of the permission on 
his system.


I think we are now back to normal, whatever that means.

Thanks all

--
Frank McCormick

Re: debian sid no boot after this morning's update





On 1/5/23 09:53, Greg Wooledge wrote:
/snip/

Error writing X authority: Failed to open X authority
/var/lib/lightdm/.Xauthority: Permission denied

Does that file exist?  If so, ls -ld /var/lib/lightdm/.Xauthority

If not, ls -ld /var/lib/lightdm

Hell, just do both regardless of whether the file currently exists.
It's one command with two lines of output.  Should be the first thing
you do.


   Yes, the file exists and is owned by lightdm. I don't know whether this is
correct as I can't find any info on who should own it.
I tried moving it out of the way hoping lightdm or the greeter would
recreate but no luck.


Hmm, that's weird indeed.  If the file is owned by lightdm (the user),
that implies that lightdm (the program) was able to write it in the past.
If it can't do so now, then we have to try to guess what changed which
could lead to this result.

Possibility 1: lightdm (the program) no longer runs as lightdm (the user).

Pissibility 2: a new restriction has been added to the service which
launches lightdm (the program).  Something at the AppArmor level, or at
the systemd unit level, perhaps.


It is strange as there were no updates yesterday of lightdm or the greeter.


How about in recent days?  Maybe a change occurred a few days ago, but
you hadn't rebooted, so the changes didn't actually have any impact yet.


The GTK
greeter was updated the day before but Debian started and ran fine after
that.


I don't know what this is.  A separate package?


Lightdm uses various greeters which provide various login appearances to 
the user.



This is confusing.  Are you saying that you have a multi-boot system,
with both Debian and Fedora installed on the same hard drive?  And that
you booted into Fedora, then mounted the Debian root file system somewhere,
and then chrooted into it?



Yes I have a multi boot system. I only mounted Debian in Fedora to read 
log files, and move the two deb files to debian. I downloaded them in 
fedora.



but apt failed saying it could not contact
debian.deb to
gain access to the needed files. 




Wait... you DID NOT chroot into the Debian file system after mounting it?!

How in the hell did you expect ANYTHING to work...?


  No, I was not trying to use Debian commands from Fedora. I was in the 
Debian emergency shell. I am no system admin, but I do know that won't work.
As it turns out dpkg failed because of other problems. A bunch of files 
and directories related to sudo had been changed to being owned by me 
instead of root. This I absolutely do not understand!! I had to fix them 
one by one in the Debian emergency shell.




OK, basic primer:

mkdir /debian
mount /dev/whatever /debian
chroot /debian

There's fancy crap you can do involving bind mounts of /proc and so on,
but you probably don't need all that.

That said, I think you've jumped ahead too far.  Your Debian system
apparently boots just fine -- it just doesn't run X.  


That wasn't the problem. Seemingly it ran X  but lightdm didn't run so X 
was killed. That's what it looked like.


So boot Debian,

either normally, or with the "systemd.unit=multi-user.target" kernel
parameter, login on a regular text console, and fix it from there.

  Once I fixed the sudo problem, dpkg worked and I reinstalled lightdm 
and the  greeter it uses. The system then booted fine but I have no idea 
how it got into that state.




Another thing you could try would be to boot your previous kernel, in
case it was a kernel update that broke lightdm.  It might not make any
difference, but hey, it's worth trying.

Another other thing you could try would be to run 'startx' from a
regular text console after booting Debian and logging in on said console.
If X starts correctly that way, then you know the problem is truly in
the DM, not in X, video drivers, video firmware, etc.  We suspect this
already, but confirmation is always good.



   These are good ideas I will try then next time I have a similar 
problem, hopefully never.


Thanks for all your help and advice.
--
Frank McCormick

Re: debian sid no boot after this morning's update





On 1/5/23 09:24, Eduardo M KALINOWSKI wrote:

On 05/01/2023 11:12, Frank wrote:
Is there a way to reinstall lightdm and the greeter from Fedora ?? 
Perhaps using chroot

which I have zero knowledge of.


Since the problem seems to be the display manager/greeter, there's a 
good chance that you can press Ctrl+F1 (or F2, F3...) to reach a 
console, so no need to a console to reinstall debian packages. Try also 
Ctrl+Alt+Fn.



  I never tried that unfortunately. It might have saved me a lot of 
trouble.  I finally got lightdm and it's greeter reinstalled after 
fixing some other problems and the system then booted fine.  The strange 
thing in my mind is how the whole thing happened, as only the lightdm 
greeter had been updated and that was a few days ago.

Thanks for the suggestion - Ill try to keep it in mind.

--
Frank McCormick

Re: debian sid no boot after this morning's update

2023-01-05 Thread Frank


On 2023-01-04 11:23 p.m., Greg Wooledge wrote:

On Wed, Jan 04, 2023 at 11:03:15PM -0500, Frank wrote:

** (process:734): WARNING **: 22:32:38.355: Error reading existing
Xauthority: Failed to open file ?/var/lib/lightdm/.Xauthority?: Permission
denied
Error writing X authority: Failed to open X authority
/var/lib/lightdm/.Xauthority: Permission denied

Does that file exist?  If so, ls -ld /var/lib/lightdm/.Xauthority

If not, ls -ld /var/lib/lightdm

Hell, just do both regardless of whether the file currently exists.
It's one command with two lines of output.  Should be the first thing
you do.


  Yes, the file exists and is owned by lightdm. I don't know whether 
this is

correct as I can't find any info on who should own it.
I tried moving it out of the way hoping lightdm or the greeter would
recreate but no luck.



See if you can figure out which user lightdm is trying to run as.
Try to make it so that user can write that file, either by removing
the existing file, or chowning it, or fixing the permissions on the
directory.  Whatever is indicated by the lightdm changelog.  Hopefully
there's a note in the lightdm changelog about this.  Or in NEWS.


 There are no notes or news file for lightdm so I am in the dark.

It is strange as there were no updates yesterday of lightdm or the 
greeter. The GTK
greeter was updated the day before but Debian started and ran fine after 
that.


There are other strange things going on which may or not be related. I 
tried to
reinstall lightdm and the greeter using apt. (The Debian partition is 
mounted
on my Fedora partition) but apt failed saying it could not contact 
debian.deb to
gain access to the needed files. I downloaded the files from Fedora and 
moved them

to Debian but dpkg said it could not access them !!??

Is there a way to reinstall lightdm and the greeter from Fedora ?? 
Perhaps using chroot

which I have zero knowledge of.

I am getting close to reinstalling Debian ( shades of Windows) !

Thanks for any help.

Re: debian sid no boot after this morning's update

2023-01-04 Thread Frank


On 2023-01-04 7:30 p.m., Frank wrote:

Just went back to my Debian Sid installation this evening to discover
it won't boot.
There were 88 updates this morning so I suspect my problem is
related to that.

Has anyone else run into this? How would I go about diagnosing
what's wrong? I tried booting in emergency mode but don't know
what to look for.


  Adding more info.


  All i get is a flashing cursor on a black screen.

  Digging around in the emergency shell I found two logs related to
lightdm. It seems it is having problems running the greeter.

This is part of the lightdm log

[+0.33s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
[+0.33s] DEBUG: Session pid=734: Started with service 'lightdm-greeter', 
username 'lightdm'
[+0.35s] DEBUG: Session pid=734: Authentication complete with return 
value 0: Success

[+0.35s] DEBUG: Seat seat0: Session authenticated, running command
[+0.35s] DEBUG: Session pid=734: Running command 
/usr/sbin/lightdm-gtk-greeter

[+0.35s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+0.35s] DEBUG: Session pid=734: Logging to 
/var/log/lightdm/seat0-greeter.log

[+0.37s] DEBUG: Activating VT 7
[+0.37s] DEBUG: Activating login1 session c5
[+0.37s] DEBUG: Seat seat0 changes active session to c5
[+0.37s] DEBUG: Session c5 is already active
[+0.37s] DEBUG: Greeter closed communication channel
[+0.37s] DEBUG: Session pid=734: Exited with return value 1
[+0.37s] DEBUG: Seat seat0: Session stopped
[+0.37s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+0.37s] DEBUG: Seat seat0: Stopping
[+0.37s] DEBUG: Seat seat0: Stopping display server
[+0.37s] DEBUG: Sending signal 15 to process 720
[+0.38s] DEBUG: Seat seat0 changes active session to
[+0.52s] DEBUG: Process 720 exited with return value 0
[+0.52s] DEBUG: XServer 0: X server stopped

This is the greeter log

** (process:734): WARNING **: 22:32:38.355: Error reading existing 
Xauthority: Failed to open file ?/var/lib/lightdm/.Xauthority?: 
Permission denied
Error writing X authority: Failed to open X authority 
/var/lib/lightdm/.Xauthority: Permission denied

debian sid no boot after this morning's update

2023-01-04 Thread Frank


Just went back to my Debian Sid installation this evening to discover
it won't boot.
There were 88 updates this morning so I suspect my problem is
related to that.

Has anyone else run into this? How would I go about diagnosing
what's wrong? I tried booting in emergency mode but don't know
what to look for.

The emergency prompt suggested journalctl -xb so that's what
I did but I didn't see anything obviously wrong.

Right now I am at my wits end. Good thing I have a working
Fedora partition.

Help!

Re: "usermod: user user is currently used by process" while using (trying to) thunderbird to back up my gmail account's data ...

2022-11-06 Thread Frank


Op 06-11-2022 om 16:38 schreef Albretch Mueller:

  on debian live:

$ uname -a
Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02)
x86_64 GNU/Linux
$

  I am running:

$ thunderbird --version
  Thunderbird 91.13.0
$

  to download all the data in my gmail account via POP3, but
Thunderbird seems to be making assumptions about where to put your
data and I haven't found a way to tell it where to put it;
If all you want to do is make thunderbird put (most of) its data 
elsewhere, you could change the profiles.ini file that exists in 
~/.thunderbird. Mine has this:


[Install9238613B8C3D2579]
Default=/data/thunderbird

[Profile0]
Name=default
IsRelative=0
Path=/data/thunderbird
Default=1

[General]
StartWithLastProfile=1
Version=2

Except for the few files/directories that need to be in ~/.thunderbird, 
all thunderbird data ends up in /data/thunderbird.
Of course, you should make sure the actual profile data is in the right 
location before you run thunderbird like this.


Regards,
Frank

Re: t-bird screwing up

2022-10-30 Thread Frank


Op 30-10-2022 om 20:15 schreef Fred:

On 10/30/22 07:54, gene heskett wrote:

Greetings all;

One or maybe more of my t-bird msg filters has gotten the path to move 
a msg to local folders/name
has somehow gotten contaminated with a "nobody" user in the path, 
which of course does not exist,
so apparently that filter is sending msgs from a good friend to 
/dev/null.  This is not at all nice.


How to fix, I can't find it in any of the config options.

Thanks all for any help. In the meantime I'll nuke the malformed filter

Cheers, Gene Heskett.


I am having trouble with T-bird also (102.3.0 32 bit).  The address book 
is no longer on the normal message page but is now under tools. However, 
it does not scroll.  Furthermore the hiding scroll bar on T-bird and 
Firefox is really annoying.  Something that isn't broken should not be 
"fixed".


I'm not seeing those address book issues here (TB 102.4.1).

Scroll bars: Preferences (scroll down) -> Configuration editor -> 
layout.testing.overlay-scrollbars.always-visible = true


Regards,
Frank

Re: signing up to fourms

2022-10-19 Thread Frank


Op 19-10-2022 om 11:16 schreef Curt:

On 2022-10-19, Bruce H.  wrote:


Am I going to have to find another distro or can you all get your shit together 
so I can join the forums and use a Debian distro?


You don't need to join anything. Just point your newsreader to
'news.gmane.io'; 'gmane.linux.debian.user'.

Anyhow, maybe if you can't figure out how to sign up, they're filtering
potential users by technical ability.

:-)



He's rambling about forums. I think he may be confusing the mailing
lists with the actual forums at forums.debian.net.

Re: Fw: Forced to Purge Thunderbird

2022-10-13 Thread Frank


On 2022-10-13 10:32, lists tomgeorge.info wrote:



*From:* lists tomgeorge.info
*Sent:* Thursday, October 13, 2022 10:13 AM
*To:* debianu...@lists.debain.org 
*Subject:* Forced to Purge Thunderbird
The company hosting my domain name has forced a switch to microsoft 
outlook. No longer supports pop3 protocol.


Result: Thunderbird frozen, all address list lost.

outlook works, must log on for each email account, does not seem to 
link responses by subject.


I would like to switch to new host which can use thunderbird

Any suggestions


Do they not support IMAP ? If they do Thunderbird handles IMAP on
my machine with no problems.

Frank

Re: usrmerge

2022-10-03 Thread Frank


Sent this earlier, but it doesn't show up on the list, so I must have
used 'reply to sender' instead of 'reply to list'... :(

Op 03-10-2022 om 15:30 schreef billium:

There was no failed or manual moves.  usrmerge may have failed during
previous upgrades and I may not have noticed.

Please do not waste any time on this as no one else has reported errors.


Actually...

https://askubuntu.com/questions/1426981/unable-to-upgrade-usrmerge-due-to-both-lib-x86-64-linux-gnu-libc-so-6-and-usr

No real answers/solutions there either, though.


  It is not that difficult to install :) .


True.


Thanks again for your time.


You're welcome.

Regards,
Frank

Re: usrmerge

2022-10-03 Thread Frank


Op 02-10-2022 om 21:29 schreef billium:

/usr/bin /usr/lib* & /usr/sbin are directories

/lib/x86_64-linux-gnu & /usr/lib/x86_64-linux-gnu are directories

/lib/x86_64-linux-gnu/libc.so.6 /usr/lib/x86_64-linux-gnu/libc.so.6 are
both files

Before the fault occurred I had made no changes (except apt update
/upgrade).

After the fault, I tried changing the root directory (/lib /bin) files
to sym links but got bored by the time I had done thirty different files.


Bad idea anyway. It's not about symlinking individual files. Everything
is moved to the corresponding subdirectories in /usr and the directories
in the root are replaced by symlinks. There are only six of those on my
system (also debian testing).


I undid the above changes, and the system works o.k., just not upgradeable.


Right. I still don't get how that libc.so.6 file could have ended up in
two places (earlier failed usrmerge? another script? manually after
all?), but in my view there are only two possible ways to fix this: the
clean one (reinstalling) and the messy one (completing the usrmerge
manually).
Be aware that the latter comes with no guarantees whatsoever and will
probably fail massively if you didn't fully restore the above changes
(i.e. left a symlink somewhere).

If you want to go the messy route, I'll need to check a couple of things
first. Can't do that until later today.

Regards,
Frank

Re: usrmerge

2022-10-02 Thread Frank


Op 02-10-2022 om 19:12 schreef billium:

/bin, /lib(*) and /sbin are directories not links, sorry I did not make
that clear.


And the corresponding items in /usr? Also directories?

What about /lib/x86_64-linux-gnu/libc.so.6 and
/usr/lib/x86_64-linux-gnu/libc.so.6? Both files?

And /lib/x86_64-linux-gnu and /usr/lib/x86_64-linux-gnu? Both directories?

Did you by any chance copy (or move or symlink) individual files before
the usrmerge upgrade?

Regards,
Frank

Re: sshd package systemd misconfiguration?

2022-09-16 Thread Frank


Op 16-09-2022 om 09:17 schreef Michael:

with ssh@.service it is completely different. for each connection there
is a dedicated sshd process being started, and each one of them has the
same /run/sshd directory assigned. and that's the problem if you have
more than one connection to a given host. as soon as the first
connection is terminated, the /run/sshd directory disappears, and the
other sshd's might run into problems.


Apparently this has already been 'fixed' for bookworm. That is, the
service section of the ssh@.service file currently includes
RuntimeDirectoryPreserve=yes.

Maybe file a bug report to have this added for bullseye?

Regards,
Frank

Re: Seeing progross during fsck on boot

2022-09-03 Thread Frank McCormick





On 9/3/22 04:56, Mike wrote:

On Fri, Sep 02, 2022 at 12:31:35AM +0200, DdB wrote:

Just thinking about your request ...

Imagine this: You run "fsck -N ..." and get a rough estimate about the
time necessary to get the I/O and the job done, then it would be easy to
set up some timed countdown in parallel with the real fsck job, just for
you to have an idea about the time left.

Alternatively, copy the whole device to another place, peform the fsck
there and decide, if copying back the result would be faster of just
running fsck on the original device.

What i am intending to make you think about: Sometimes it is way more
difficult and time consuming to get a rough estimate of some result,
than to actually just get it for real. (You may talk to some math PHD
about that.) ... not worth the effort, because even you would prefer to
get the result as fast as possible and not wait twice the time just to
know ahead of time, when the job is likely to finish.

Does that make sense to you too?




Hi,

Thanks for the replies.

Rereading my original request, I think perhaps I wasn't entirely clear
on a couple of points:

1) When there server starts, the default behaviour is to fsck the disks
if they have been longer than 120 days (or something like that) without
a fsck.  It's a server and runs 24x7, so you can bet your bottom dollar
that if if it does reboot, it will need to fsck.  You can also bet that
it was an uncontrolled shutdown because the UPS caught fire or
something, so it's probably wise to run fsck.  I haev no issue with this
happening

2) I'm not too worried about how long it's actually going to take.  The
main issue is that I've had a couple of instances where the box has
rebooted, I've sat around waiting for it to reboot, wondered why it
hasn't, plugged a monitor in and seen jack on the screen, then just as I
panic about what major issue could be wrong with it and key CTRL+ALT+DEL
to see if I missed anything... I see the disk lights are solid on and
assume it must be running fsck.  Sometimes it does find some erros and
spits that out to the screen.  Otherwise it just sits there like a dog
that's been shown a card trick.

Maybe I'm being nostalgic but I seem to recall in days gone by that fsck
printed a progress bar out of hashes to show how it was getting along.

Someone asked about the file systems in use.  Some are ext3 and some are
ext4.

TL;DR: When my server boots up and decdies to spent four hours fscking
the disks, I'd just like to see some indiction that it's still alive and
doing something :-)

Regards,
Mike.


This is from the e2fsck manual. It may be relevant


SIGNALSThe following signals have the following effect when sent 
to e2fsck.


SIGUSR1   This  signal causes e2fsck to start displaying a 
completion bar or emitting progress information.  (See 
discussion of the -C option.)


SIGUSR2   This signal causes e2fsck to stop displaying a 
completion bar or emitting progress information.



--
Frank McCormick

Re: SSH resources, specifically on certificates (certificate authentication)

2022-07-14 Thread Frank Pikelner

On Thu, Jul 14, 2022 at 8:56 AM  wrote:
>
> 
>
> dsr, Thanks for the reply!
>
> Like I said, I think I went down a rabbit hole, and I wish I had realized that
> before I went there.
>
> I've invested quite a few calendar days (and "spare" manhours) in trying to
> figure this out, so I'm not quite ready to give up.
>
> I do have some ideas (an idea) for another pass through some of the
> documentation that might clarify what I need / want to know, but, especially
> if that doesn't work, I may write a WikiLearn page or two that mainly just
> warns about the rabbit hole.
>
> I'm almost certain I will be back with some specific questions that maybe you
> or someone else on the list can answer.
>
> Thanks again!
>
> On Thursday, July 14, 2022 02:11:30 AM Dan Ritter wrote:
> > Dan Purgert wrote:
> ...
> > > > > On Jul 13, 2022, rhkra...@gmail.com wrote:
> > > > > > I seem to have gone down a rabbit hole.
>
> > Right, the problem is in everything to support that: running a
> > certificate authority in a secure manner is extremely
> > non-trivial. Running it in a secure and reliable manner is even
> > more non-trivial.
> >
> > In general, I don't recommend it. Consider this:
> >
> > - an SSH certificate has a date on which it will expire. When
> > that day comes, it will stop functioning. If you don't have
> > infrastructure to remind you to re-issue this in advance, you
> > may be locked out of whatever you are trying to access.
> >
> > - conversely, if you want to revoke an SSH certificate before
> > the expiration date, you need to maintain and distribute a
> > revocation list of all the certs that you no longer approve of.
> > Miss a machine and the old cert is still valid up to the
> > expiration date.
> >
> > For most people in most cases, those are not the behaviors that
> > they want.
> >
> > > I've never seen this implemented in any place I've worked in
> > > the last 2 decades (granted, I "only" have said 2 decades of
> > > "professional" experience); rather they've always used either (a) keys,
> > > or (b) password + RSA Token (or other 2FA / TOTP mechanism)
> >
> > And the reason is that those fit what people want more closely
> > than the cert mechanism.
> >
> > If you've got a very large organization, you may want to support
> > the infrastructure to generate new SSH certs for people daily,
> > with expiration dates of 24 hours. Then you need to make sure
> > that mechanism is working perfectly and has appropriate
> > redundancy, so that you don't accidentally lock out the whole
> > organization tomorrow.
> >
> > -dsr-
>
> --


SSH certificate authentication is not complicated and has many
advantages. Some organizations use SSH certificates to provide limited
access for admins to servers. In my opinion using SSH certificates is
preferred to just using ssh keys. There are a number of guides on how
to implement ssh certificates - if you are unable to locate, ping me
directly and I may have a document I wrote for myself a while back.

Best,

Frank

Re: digikam import fails

2022-06-16 Thread Frank


On 2022-06-16 16:23, gene heskett wrote:

On 6/16/22 15:42, mick crane wrote:

On 2022-06-16 20:19, gene heskett wrote:


The shell I ran digikam from is reporting screens full of
missing this and that despite the installation of digikam
pulling in:
 0 upgraded, 261 newly installed, 0 to remove and 0 not upgraded.
Need to get 273 MB of archives.
After this operation, 726 MB of additional disk space will be used.

Then when I run it, there are hundred of missing that and than lines
spit out in the shell I launched it from.


try gphoto2 ?
if camera is on list
http://gphoto.org/proj/libgphoto2/support.php
should you not be able to mount it as a filesystem ?
I like geeqie for viewing images.

mick


I installed it, but:
gene@coyote:~$ sudo apt install gphoto2
[sudo] password for gene:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libcdk5nc6
Suggested packages:
  gthumb
The following NEW packages will be installed:
  gphoto2 libcdk5nc6
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 320 kB of archives.
After this operation, 1,341 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://deb.debian.org/debian bullseye/main amd64 libcdk5nc6 
amd64 5.0.20180306-3 [129 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 gphoto2 amd64 
2.5.27-1 [191 kB]

Fetched 320 kB in 0s (858 kB/s)
Selecting previously unselected package libcdk5nc6:amd64.
(Reading database ... 136011 files and directories currently installed.)
Preparing to unpack .../libcdk5nc6_5.0.20180306-3_amd64.deb ...
Unpacking libcdk5nc6:amd64 (5.0.20180306-3) ...
Selecting previously unselected package gphoto2.
Preparing to unpack .../gphoto2_2.5.27-1_amd64.deb ...
Unpacking gphoto2 (2.5.27-1) ...
Setting up libcdk5nc6:amd64 (5.0.20180306-3) ...
Setting up gphoto2 (2.5.27-1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u3) ...
-.-.-.
gene@coyote:~$ gphoto2
Usage: gphoto2 [-?qvalLnPTDR] [-?|--help] [--usage] [--debug]
    [--debug-loglevel=STRING] [--debug-logfile=FILENAME] [-q|--quiet]
    [--hook-script=FILENAME] [--stdout] [--stdout-size] 
[--auto-detect]
    [--show-exif=STRING] [--show-info=STRING] [--summary] 
[--manual] [--about]
    [--storage-info] [--shell] [-v|--version] [--list-cameras] 
[--list-ports]
    [-a|--abilities] [--port=FILENAME] [--speed=SPEED] 
[--camera=MODEL]

    [--usbid=USBIDs] [--config] [--list-config] [--list-all-config]
    [--get-config=STRING] [--set-config=STRING] 
[--set-config-index=STRING]
    [--set-config-value=STRING] [--reset] [--keep] [--keep-raw] 
[--no-keep]

    [--wait-event=COUNT, SECONDS, MILLISECONDS or MATCHSTRING]
    [--wait-event-and-download=COUNT, SECONDS, MILLISECONDS or 
MATCHSTRING]
    [--capture-preview] [--show-preview] [-B|--bulb=SECONDS] 
[-F|--frames=COUNT]

    [-I|--interval=SECONDS] [--reset-interval] [--capture-image]
    [--trigger-capture] [--capture-image-and-download]
    [--capture-movie=COUNT or SECONDS] [--capture-sound]
    [--capture-tethered=COUNT, SECONDS, MILLISECONDS or MATCHSTRING]
    [-l|--list-folders] [-L|--list-files] [-m|--mkdir=DIRNAME]
    [-r|--rmdir=DIRNAME] [-n|--num-files] [-p|--get-file=RANGE]
    [-P|--get-all-files] [-t|--get-thumbnail=RANGE] 
[-T|--get-all-thumbnails]
    [--get-metadata=RANGE] [--get-all-metadata] 
[--upload-metadata=STRING]
    [--get-raw-data=RANGE] [--get-all-raw-data] 
[--get-audio-data=RANGE]
    [--get-all-audio-data] [-d|--delete-file=RANGE] 
[-D|--delete-all-files]
    [-u|--upload-file=FILENAME] [--filename=FILENAME_PATTERN] 
[-f|--folder=FOLDER]
    [-R|--recurse] [--no-recurse] [--new] [--force-overwrite] 
[--skip-existing]

gene@coyote:~$





You've obviously got GThumb installed - it **usually** comes with the 
Gthumb photo import

tool which I suspect uses the GPhoto2 library(s).

Check with apt whether it's a separate download. I use it all the time
except when I am in Mate when the Caja file manager loads up my camera
automatically. Do you have any desktop  like Gnome or Mate ?

Re: Firefox insists to be default !?

2022-01-12 Thread Frank




Me too. Firefox 95.0.2 in Mate fully updated. I have had this problem 
before but it always sorted itself out later.




On 2022-01-12 14:52, Miroslav Skoric wrote:

Hi all,

After the recent upgrade of Firefox (and Thunderbird) in oldoldstable 
(Mate desktop), Firefox always asks me to be default browser, even 
though I have set it as default in Mate's default applications, and 
respond to that asking by click on 'dont ask me again'.


Furthermore, Thunderbird is also set as a default email client. 
However, if I click on a weblink in Thunderbird mail, another 
Thunderbird session opens (instead opening Firefox). And when I close 
both software, and return to Mate control panel to check again for 
default applications ... voila ... Thunderbird seems as magically 
selected for both mail client and web browser there!


How to prevent that misbehaviour? All worked well with previous 
versions of Firefox and Thunderbird. What went wrong with new versions?


Misko

Re: Thunderbird en firefox-esr

2021-12-13 Thread Frank Voncken

Paul van der Vlis schreef op ma 13-12-2021 om 09:28 [+0100]:
> Op 13-12-2021 om 01:04 schreef Paul van der Vlis:
> > Op 08-12-2021 om 22:04 schreef Paul van der Vlis:
> > > Op 28-11-2021 om 12:50 schreef Paul van der Vlis:
> > > > Hoi,
> > > > 
> > > > Het lijkt er op dat er toch eindelijk nieuwe versies aankomen
> > > > van 
> > > > Thunderbird en Firefox-esr. Op beide waren er problemen met 
> > > > compileren op i386, maar die lijken nu opgelost:
> > > > https://buildd.debian.org/status/package.php?p=thunderbird
> > > > https://buildd.debian.org/status/package.php?p=firefox-esr
> > > > 
> > > > Ik verwacht Thunderbird in een paar dagen, en Firefox-ESR met
> > > > wat 
> > > > geluk volgend weekend.
> > > 
> > > Dat blijkt niet uit te komen.

Firefox-esr versie 91 is zojuist in de testing beland. Ik heb hem nu :-
)

Frank

Re: suitable email agent

2021-12-12 Thread Frank Hwa


off the subject, does shentel now use mail2world as the email hosting?

shentel.net.60  IN  MX  10 mx1.pangia.biz.
shentel.net.60  IN  MX  10 mx2.pangia.biz.


When I used shentel years ago, they were not hosted by mail2world.



On 2021/12/13 11:38, gene wrote:

That looks as it it would be happy with my cuurent fetchmail/procmail sucking
my imap account at my isp.

Re: Agenda software

2021-12-12 Thread Frank Voncken

Geert Stappers schreef op zo 12-12-2021 om 19:36 [+0100]:
> 
> Hoi,
> 
> Wat gebruiken jullie zoal aan agenda software?
> 
> 
Agenda van Gnome: nog beetje beperkt in functionaliteiten, maar
communiceert goed met mijn Nextcloud-agenda (via Gnome Online Account,
GOA). Elke persoon in ons gezin heeft eigen agenda-kleur, wel handig.

Agenda van e-mail client Evolution: uitgebreider, vooral betere
zoekmogelijkheden. Communiceert ook goed met GOA. Ook hier meerdere
accounts met eigen agendakleur mogelijk.

Frank

Re: laptop start niet meer op na suspend

2021-12-06 Thread Frank Voncken

Geert Stappers schreef op ma 06-12-2021 om 12:09 [+0100]:
> 
> 
> > > Zelf gebruik ik daarom vaak wat oudere hardware, of hardware
> > > waarvan
> > > ik gehoord heb dat hij het goed doet onder Linux.
> > 
> > Het gebeurt op een Tuxedo-laptop, een Linux-laptop dus. Het zou dus
> > in
> > principe gewoon moeten werken. Mmm, ik zal eens bij Tuxedo navragen
> > hoe
> > ze dat gedaan hebben op hun ondersteunde OS (meestal LTS-versie van
> > Budgie, Kubuntu, e.d.). Meestal krijg ik snel reactie.
> 
> Advies: Vraag expliciet naar wat het "wakker worden signaal" is.
>  
> In het antwoord verwacht ik iets van een hardware eigenschap.

Ik had al een mail gestuurd naar Tuxedo voordat ik die tip kon
gebruiken. Ik heb wel inmiddels reactie ontvangen. Volgens hen zou ik
twee dingen kunnen proberen: nvidia-driver gebruiken of een ouder Linux
kernel gebruiken.

De eerste suggestie heb ik uitgeprobeerd, en inderdaad, de laptop komt
na suspend weer tot leven. Ik weet niet of dat verrassend is. Wel
jammer dat ik in dit geval een proprietary driver moet gebruiken.
Overigens lijkt hybernation (met die echo disk commando) ook met
nvidia-driver niet goed te gaan.

De tweede suggestie: ik weet nog niet hoe ik dat moet doen. Misschien
dat, als het lukt met het gebruiken van een ouder Linux kernel,
waarschijnlijk  met een ouder kernel nvidia-driver niet nodig is??


Frank

Re: laptop start niet meer op na suspend

2021-12-06 Thread Frank Voncken

richard lucassen schreef op zo 05-12-2021 om 16:00 [+0100]:
> On Sun, 05 Dec 2021 14:55:24 +0100
> Frank Voncken  wrote:
> 
> > > Ja, jij wel, maar de computer, komt die dan wel uit suspend? :-)
> > 
> > Ja, de computer ook :-)

Ik moet daar helaas op terugkomen: het wordt na 

   echo mem > /sys/power/state 

niet meer wakker... :-(

> 
> Misschien dat gebruiken als suspend/hibernate als workaround.
> Overigens
> is dit het hibernate commando:
> 
> echo disk > /sys/power/state


Het vreemde is dat ongeveer 15 seconden na invoeren van echo disk >
/sys/power/state de laptop spontaan weer wakker wordt met in de
terminal de volgende foutmelding:

   bash: echo: schrijffout: Geen ruimte meer over op apparaat

Vreemd...

Re: laptop start niet meer op na suspend

2021-12-06 Thread Frank Voncken

Paul van der Vlis schreef op ma 06-12-2021 om 10:00 [+0100]:
> Op 05-12-2021 om 13:23 schreef Frank Voncken:
> > Beste allen,
> > 
> > Ik heb een vervelend probleem: laptop start niet meer op na
> > suspend. Ik
> > moet steeds hard reset gebruiken om de laptop opnieuw te kunnen
> > gebruiken. Gegevens van de laptop:
> > 
> >   * Debian bookworm met Linux 5.15
> >   * Gnome 41.1 en Wayland
> >   * AMD Ryzen 7 5800H
> >   * grafische kaart RTX 3060 / AMD Renoir
> >   * nouveau driver (dus geen nvidia driver, nouveau werkt hier
> >     vlekkeloos)
> >   * amdgpu en firmware-linux-nonfree zijn geïnstalleerd
> > 
> > Wat ik tot nu toe heb gedaan:
> >   * GRUB_CMDLINE_LINUX="init_on_alloc=0" toevoegen aan de lijn
> >     GRUB_CMDLINE_LINUX=" " binnen etc/default/grub zoals ik elders
> > heb
> >     gezien op een Debian forum -> het helpt helaas niet
> >   * het uitschakelen van suspend volgens instructies
> >     op https://wiki.debian.org/Suspend helpt wel (logisch), maar ik
> > denk
> >     dat men suspend niet zomaar mag uitschakelen vanwege de
> >     energiehuishouding. Bovendien lost dat het suspend/resume
> > probleem
> >     niet op.
> >   * journalctl -b -1 biedt geen informatie omdat in de journal de
> >     laatste regel "systemd-sleep: Entering sleep state 'suspend'"
> > is.
> >     Geen enkele regel over poging tot resume. Na een hard reset
> > blijkt
> >     in journalctl een gat in tijd te zitten tussen die suspend-
> > regel en
> >     het opnieuw opstarten van de laptop.
> > 
> > Ik zie ook nieuws in de Phoronix dat AMD met een fix voor
> > suspend/resume zou komen in Linux 5.15
> > (
> > https://www.phoronix.com/forums/forum/software/mobile-linux/1277837-amd-has-an-important-suspend-resume-fix-with-linux-5-15
> > ). Nog niets van gemerkt.
> > 
> > Enig idee?
> 
> Dit is vaak het probleem met nieuwe hardware, dat er nog
> kinderziektes 
> zijn qua Linux. Je bent goed bezig door het nieuwste kernel te 
> gebruiken. Wellicht is het probleem opgelost in kernel 5.16 of 5.17.

Zowel op kernel 5.14 als op kernel 5.15 lukt het niet. Laten we hopen
dat het opgelost wordt in kernel 5.16!

> 
> Zelf gebruik ik daarom vaak wat oudere hardware, of hardware waarvan
> ik 
> gehoord heb dat hij het goed doet onder Linux.

Het gebeurt op een Tuxedo-laptop, een Linux-laptop dus. Het zou dus in
principe gewoon moeten werken. Mmm, ik zal eens bij Tuxedo navragen hoe
ze dat gedaan hebben op hun ondersteunde OS (meestal LTS-versie van
Budgie, Kubuntu, e.d.). Meestal krijg ik snel reactie.

>  Soms is het ook een 
> kwestie van "testen en eventueel terugsturen". Dan boot ik vanaf USB
> om 
> te testen.
> 
> Overigens kun je instellen wat er gebeurd als je de klep dicht doet.
> Dat 
> doe ik normaal in de instellingen van de desktop die ik gebruik.

Oké, ik ga voorlopig suspend uitzetten als ik de klep dichtdoe.

Groet,

Frank

Re: laptop start niet meer op na suspend

richard lucassen schreef op zo 05-12-2021 om 16:00 [+0100]:
> On Sun, 05 Dec 2021 14:55:24 +0100
> Frank Voncken  wrote:
> 
> > > Ja, jij wel, maar de computer, komt die dan wel uit suspend? :-)
> > 
> > Ja, de computer ook :-)
> 
> Misschien dat gebruiken als suspend/hibernate als workaround.

Dat kan, ja. Overigens gebruikt mijn niet-zo-technische vrouw de laptop
ook. En uit gewoonte doet zij de deksel soms dicht (ik ook) om het
korte tijd later weer te gebruiken. Maar door het dicht te doen, komt
de laptop in suspend mode terecht en krijg ik het daarna niet meer
gewekt. Uiteraard kan ik de suspend mode door het sluiten van de deksel
uitschakelen met binnen in /etc/systemd/logind.conf:

   [Login]
   HandleLidSwitch=ignore
   HandleLidSwitchDocked=ignore

Maar of dat goed voor de laptop is, weet ik niet...

> Overigens
> is dit het hibernate commando:
> 
> echo disk > /sys/power/state
> 
> Maar dat wist je misschien al :)
> 

Nee, dat wist ik niet. Mijn kennis reikt niet zo ver als die van velen
van jullie (respect voor jullie!!)

Frank

Re: laptop start niet meer op na suspend

richard lucassen schreef op zo 05-12-2021 om 14:44 [+0100]:
> On Sun, 05 Dec 2021 14:21:54 +0100
> Frank Voncken  wrote:
> 
> > > > Ik heb een vervelend probleem: laptop start niet meer op na
> > > > suspend.
> > > 
> > > Suspend en hibernate geeft wel vaker problemen. Wat gebeurt er
> > > als
> > > je:
> > > 
> > > echo mem > /sys/power/state
> > > 
> > > als root draait? Komt-ie er dan wel uit?
> > 
> > Ik kom er wel uit, ja. Dus echo mem > /sys/power/state werkt
> > normaal.
> 
> Ja, jij wel, maar de computer, komt die dan wel uit suspend? :-)

Ja, de computer ook :-)

Re: laptop start niet meer op na suspend

Richard Lucassen schreef op zo 05-12-2021 om 14:04 [+0100]:
> On Sun, 05 Dec 2021 13:23:34 +0100
> Frank Voncken  wrote:
> 
> > Ik heb een vervelend probleem: laptop start niet meer op na
> > suspend.
> 
> Suspend en hibernate geeft wel vaker problemen. Wat gebeurt er als
> je:
> 
> echo mem > /sys/power/state
> 
> als root draait? Komt-ie er dan wel uit?
> 
> R.
> 

Hallo Richard,

Ik kom er wel uit, ja. Dus echo mem > /sys/power/state werkt normaal.

Frank

laptop start niet meer op na suspend

Beste allen,

Ik heb een vervelend probleem: laptop start niet meer op na suspend. Ik
moet steeds hard reset gebruiken om de laptop opnieuw te kunnen
gebruiken. Gegevens van de laptop:

* Debian bookworm met Linux 5.15
* Gnome 41.1 en Wayland
* AMD Ryzen 7 5800H
* grafische kaart RTX 3060 / AMD Renoir
* nouveau driver (dus geen nvidia driver, nouveau werkt hier
vlekkeloos)
* amdgpu en firmware-linux-nonfree zijn geïnstalleerd

Wat ik tot nu toe heb gedaan:
* GRUB_CMDLINE_LINUX="init_on_alloc=0" toevoegen aan de lijn
GRUB_CMDLINE_LINUX=" " binnen etc/default/grub zoals ik elders heb
gezien op een Debian forum -> het helpt helaas niet
* het uitschakelen van suspend volgens instructies
op https://wiki.debian.org/Suspend helpt wel (logisch), maar ik denk
dat men suspend niet zomaar mag uitschakelen vanwege de
energiehuishouding. Bovendien lost dat het suspend/resume probleem
niet op.
* journalctl -b -1 biedt geen informatie omdat in de journal de
laatste regel "systemd-sleep: Entering sleep state 'suspend'" is.
Geen enkele regel over poging tot resume. Na een hard reset blijkt
in journalctl een gat in tijd te zitten tussen die suspend-regel en
het opnieuw opstarten van de laptop.

Ik zie ook nieuws in de Phoronix dat AMD met een fix voor
suspend/resume zou komen in Linux 5.15
(https://www.phoronix.com/forums/forum/software/mobile-linux/1277837-amd-has-an-important-suspend-resume-fix-with-linux-5-15
). Nog niets van gemerkt.

Enig idee?

Frank

Re: Can't do apt-update because code name is changed from bullseye to bookworm

2021-08-18 Thread Frank


Op 18-08-2021 om 06:51 schreef Richard Forst:


When doing apt-get update, debian throws following error. It looks like because 
the code name changed from bullseye to bookworm.

E: Repository 'http://security.debian.org testing-security InRelease' changed 
its 'Codename' value from 'bullseye-security' to 'bookworm-security'
N: This must be accepted explicitly before updates for this repository can be 
applied. See apt-secure(8) manpage for details.
E: Repository 'https://deb.debian.org/debian testing InRelease' changed its 
'Codename' value from 'bullseye' to 'bookworm'
N: This must be accepted explicitly before updates for this repository can be 
applied. See apt-secure(8) manpage for details.
N: Skipping acquire of configured file 'main/binary-i386/Packages' as 
repository 'https://download.zulip.com/desktop/apt stable InRelease' doesn't 
support architecture 'i386'

However in my sources.list is neither bullseye nor bookworm as below (I use 
testing-security). How can I fix this error?Thanks


The Suite for testing changed from bullseye to bookworm, so you get this
message. Fix it by adding the --allow-releaseinfo-change switch to
apt-get update.
By the way, there hasn't been anything in testing-security for years, so
you might as well remove it from your sources.list.

Regards,
Frank

Re: [SOLVED] Re: Issues with Bullseye

2021-08-15 Thread Frank


Op 15-08-2021 om 18:01 schreef Hans:

Hi all,

discovered something. It looks like the keys are still not synced to the
mirrors.

I changed from ftp.de.debian.org to deb.debian.org, and all is working like a
charm.

So, I suppose, this issue might be solved.

But it would be nice to add a package with the actual keys into the repo. The
keys in the package "debian-archive-keyring" are too old (2012.1.1).


They're not. They're 2021.1.1.

Re: Issues with Bullseye

2021-08-15 Thread Frank


Op 15-08-2021 om 16:51 schreef Hans:

Am Sonntag, 15. August 2021, 16:36:05 CEST schrieb Brian:
Yes, you are very right!


There isn't any such thing as being "too critical" when it comes to
technical matters :).

A link to the page you were looking at might help.


To everyone:

I have still the problem, that the debian/bullsye repo can not be
authenticated. Copying the Release.gpg from the repo to
/etc/apt/trusted.gpg.d/ did not help.


That doesn't surprise me. That's a signature, not a key.


It would really help, if there could be an upgraded debian-archive-keyring
package or a little documentation, how to add/import the keys into
trusted.gpg.d/ since apt-key does not work any more.

Simply copying does not work(!) and the documentation really lacks some
information, which would help.


Simply copying works, if you use the correct file. If the key is
armored, make sure the extension is .asc. Otherwise it should be .gpg.

But downloading an up-to-date version (2021.1.1) of
debian-archive-keyring and installing that (using dpkg -i if necessary -
see below for a direct url) should suffice.

Regards,
Frank

http://deb.debian.org/debian/pool/main/d/debian-archive-keyring/debian-archive-keyring_2021.1.1_all.deb

Re: security.debian.org bullseye/updates Release does not have a Release file

2021-08-15 Thread Frank


Op 15-08-2021 om 08:23 schreef John Covici:

Hi.  I did a apt-get update  changing from buster to bullseye and got
the above message -- should I just wait a few days and try again or
something else?

Thanks.


bullseye/updates is not the location for bullseye's security repo.
Change the relevant line in your sources.list to:

deb http://security.debian.org/debian-security/ bullseye-security main

Add contrib and non-free at the end if you use them.

Regards,
Frank

Re: Upgrade problems?

2021-07-21 Thread Frank McCormick





On 7/21/21 12:24 PM, Greg Wooledge wrote:

On Wed, Jul 21, 2021 at 12:04:13PM -0400, Frank McCormick wrote:

frank@fedora ~$ stat /
   File: /
   Size: 4096    Blocks: 8  IO Block: 4096 directory
Device: 806h/2054d  Inode: 2   Links: 18
Access: (0555/dr-xr-xr-x)  Uid: (    0/    root)   Gid: ( 1000/ frank)
Context: system_u:object_r:root_t:s0
Access: 2021-07-21 10:22:56.572440309 -0400
Modify: 2021-06-26 15:48:58.771330459 -0400
Change: 2021-06-27 10:10:28.333447227 -0400
Birth: 2021-06-11 13:38:48.0 -0400

Looks like owned by root but access by frank ?

Will chown work ?


Your hostname is "fedora"?  Um.  Skipping that for now

Yes, chown would work, although chgrp would be the more "natural" pick.

Either   chown 0:0 /   or   chgrp 0 /

While you're poking around in there, the permissions are also different
from what one would normally expect on Debian.  chmod 755 /

Then again, if this isn't actually a Debian host, the 555 permissions
on the root directory might be normal.




   Good grief!

This comment stirred my memory and I realized I had rebooted into Fedora 
34 AFTER I had updated Debian Bullseye.


>Your hostname is "fedora"?  Um.  Skipping that for now >

Nevertheless, I am still pullzed by those errors.


 Back in Debian is redid the debug suggestions.

frank@franklin:~$ stat /

File: /
Size: 4096Blocks: 8  IO Block: 4096
directory
Device: 801h/2049d  Inode: 2   Links:18
Access: (0755/drwxr-xr-x)  Uid: (0/root)   Gid: (0/root)
Access: 2021-07-21 10:28:15.256580076 -0400 Modify: 2021-07-21 
10:14:11.300131364 -0400 Change: 2021-07-21 10:20:43.718277098 -0400

Birth: 2020-07-12 12:23:46.0 -0400

(sorry about the wrapping)

frank@franklin:~$ ls -ld /

drwxr-xr-x 18 root root 4096 Jul 21 10:14 /

So "/" is owned by root with proper permissions!

What now ??

Sorry folks.


Frank

--
Frank McCormick

Re: Upgrade problems?

2021-07-21 Thread Frank McCormick


On 2021-07-21 10:52 a.m., Kushal Kumaran wrote:


On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick  
wrote:

Got a bunch of strange errors during this morning upgrade of Bullseye.


Setting up systemd (247.3-6) ... Detected unsafe path transition / →
/run during canonicalization of /run. Detected unsafe path transition
/ → /run during canonicalization of /run/lock. Detected unsafe path
transition / → /var during canonicalization of /var. Detected unsafe


/snip/

frank@fedora ~$ stat /
  File: /
  Size: 4096    Blocks: 8  IO Block: 4096 directory
Device: 806h/2054d  Inode: 2   Links: 18
Access: (0555/dr-xr-xr-x)  Uid: (    0/    root)   Gid: ( 1000/ frank)
Context: system_u:object_r:root_t:s0
Access: 2021-07-21 10:22:56.572440309 -0400
Modify: 2021-06-26 15:48:58.771330459 -0400
Change: 2021-06-27 10:10:28.333447227 -0400
Birth: 2021-06-11 13:38:48.0 -0400

Looks like owned by root but access by frank ?

Will chown work ?


Thanks

Upgrade problems?

2021-07-21 Thread Frank McCormick




Got a bunch of strange errors during this morning upgrade of Bullseye.


Setting up systemd (247.3-6) ... Detected unsafe path transition / → 
/run during canonicalization of /run. Detected unsafe path transition / 
→ /run during canonicalization of /run/lock. Detected unsafe path 
transition / → /var during canonicalization of /var. Detected unsafe 
path transition / → /var during canonicalization of /var/lib. Detected 
unsafe path transition / → /var during canonicalization of 
/var/lib/systemd. Detected unsafe path transition / → /run during 
canonicalization of /run. Detected unsafe path transition / → /run 
during canonicalization of /run/systemd. Detected unsafe path transition 
/ → /run during canonicalization of /run/systemd. Detected unsafe path 
transition / → /run during canonicalization of /run/systemd. Detected 
unsafe path transition / → /run during canonicalization of /run/systemd. 
Detected unsafe path transition / → /run during canonicalization of 
/run/systemd. Detected unsafe path transition / → /run during 
canonicalization of /run/systemd. Detected unsafe path transition / → 
/run during canonicalization of /run/systemd. Detected unsafe path 
transition / → /run during canonicalization of /run/systemd/netif. 
Detected unsafe path transition / → /run during canonicalization of 
/run/systemd/netif. Detected unsafe path transition / → /run during 
canonicalization of /run/systemd/netif.



So far, doesn't seem to affect the operation of the computer.


Thanks

--
Frank McCormick

Re: Thunderbird problems

2021-06-14 Thread Frank McCormick





On 6/14/21 9:46 PM, Robbi Nespu wrote:

On 6/15/21 6:24 AM, Frank McCormick wrote:
The latest version of Thunderbird which was updated recently is giving 
me problems connecting to gmail.


How can I downgrade Thunderbird on this machine? I am running
Bullseye





Let me guess, you unable to connect imap and smtp right? I having that 
kind of issue.


$ apt-cache policy thunderbird
thunderbird:
   Installed: 1:78.11.0-1
   Candidate: 1:78.11.0-1
   Version table:
  *** 1:78.11.0-1 500
     500 http://ftp.jp.debian.org/debian bullseye/main amd64 Packages
     100 /var/lib/dpkg/status


with setting up few thing below, I can see it said unable to connect to 
imap..


$ export MOZ_LOG=IMAP:5,timestamp
$ export MOZ_LOG_FILE=/tmp/imap_thunderbird.log
$ thunderbird
$ tail -f /tmp/imap_thunderbird.log # on separate terminal

I give up to check further so, I clear up the account (keep data) and 
re-add the account and sync from start again. Now I can use...to connect 
and see my email, but failure when sending out email. it have smtp issue 
too (change MOZ_LOG=SMTP:5,timestamp).. the remove the account and 
resync for second time, look resolve my issues


what waste of bandwidth for today




  I downloaded he generic 64 bit version of Thunderbird from the 
Mozilla website and set it up in my home directory. Works fines, 
connects everywhere so obviously the problem is with the Debian build of 
Thunderbird.

I filed a bug report with Mozilla. Perhaps I should do the same with Debian?


--
Frank McCormick

Thunderbird problems

2021-06-14 Thread Frank McCormick

The latest version of Thunderbird which was updated recently is giving 
me problems connecting to gmail.


How can I downgrade Thunderbird on this machine? I am running
Bullseye


--
Frank McCormick

Re: passwordless SSH

2021-06-03 Thread Frank Pikelner

It is much better to use SSH certificates, not a great deal of extra work,
but well worth it. Simplifies management and works well for automation.

Best,

Frank

On Thu, Jun 3, 2021 at 5:15 PM David Wright 
wrote:

> On Sat 29 May 2021 at 18:25:50 (-0400), Bob Weber wrote:
>
> > Now follow the instructions at:
> >
> > https://linuxize.com/post/how-to-setup-passwordless-ssh-login/
> >
> > You will need to follow those instructions for each linux server you
> > want to backup.  The .ssh directory will be under the directory listed
> > in the passwd file (/var/lib/backuppc).? DO NOT USE A PASSWORD TO
> > create the key pair files! They should go into the
> > /var/lib/backuppc/.ssh directory (only do this ONCE!).  In step 03.
> > the username should be root@ip-address (you will need root access on
> > that machine to backup all files from the backuppc user on the
> > backuppc server).  In step 04 you should be able to "ssh
> > root@ip-address" without a password.
>
> I do this as a matter of course when I set up my machines …
>
> > THESE COMMANDS ARE RUN ON EACH SERVER TO BE BACKED UP.
>
> … (not the backuppc stuff, but just the passwordless login) …
>
> > If yyou can't "ssh root@ip-address" without a password you may also
> need the line
> >
> > "PermitRootLogin yes"
> >
> > in the /etc/ssh/sshd_config file on each server to be backed up.
>
> I avoid this wrinkle with a trick that's especially simple when it's
> done first thing after installation (but it's easy at any time).
>
> On machine A:
>
>   # ssh-copy-id -i ~/.ssh/id_rsa.pub @hostB
>
> where the sysadminuser¹ is as yet unconfigured for passwordless
> login by ssh. On machine B, as sysadminuser:
>
>   $ /bin/su -
>   # mv -i /home//.ssh/authorized_keys /root/.ssh/
>   # chown 0.0 /root/.ssh/authorized_keys
>
> If sysadminuser already had some keys in authorized_keys,
> then root will need to edit the key from the last line of
> /home//.ssh/authorized_keys rather than just
> moving the file (and make sure you don't leave behind a
> backup in /home//.ssh/authorized_keys~).
>
> Alternatively, you can move sysadminuser's authorized_keys
> out of the way while you type the lines shown above, and then
> move it back. (Stay logged in to sysadminuser while you do this.)
>
> > If you want to you can follow the instructions at "Disabling SSH
> > Password Authentication".  Be very careful to follow the instructions
> > closely.  These are not needed to get backuppc running!  You will need
> > to be able to sudo into root from an unprivileged user to get root
> > access so be VERY careful to follow the instructions.
>
> ¹ I'm assuming root and sysadminuser are the same person, and others
>   don't (yet) have access to the machine.
>
> Cheers,
> David.
>
>

Re: thunderbird

2021-05-30 Thread Frank McCormick





On 5/30/21 4:24 PM, Doug McGarrett wrote:



On 5/30/21 4:04 PM, Joe wrote:

On Sun, 30 May 2021 18:29:11 +
fxkl47BF  wrote:


for a few decades i have used pine/alpine.
i'm considering a new mail application.
there are more out there than you can shake a stick at.
what are your thoughts of thunderbird.


A bit slow and heavy for my liking. I used to use it, then switched to
Claws-Mail, which is faster and seems to do what I need.


Thunderbird will find all the esoteric locations, etc. that email
systems need to function. Claws mail does not. If I knew how
to find the necessary information, I would try claws mail.
--doug



I tried Claws mail a few years ago. I could never get it setup properly 
for IMAP. Thunderbird did it flawlessly.

--
Frank McCormick

Re: FileZilla / ftp / GnuTLS error connecting to sites with Testing/Bullseye

2021-02-13 Thread Frank


Op 13-02-2021 om 14:56 schreef songbird:

Frank wrote:

Op 12-02-2021 om 22:18 schreef Gary Dale:

...

I can do the same with Dolphin but I find it clumsy. FileZIlla is made
to let you transfer files between local and remote directories.


That's exactly what I do with caja, either from one tab to the other or
between separate windows. I'm not sure what's supposed to be clumsy
about it.


   probably the part about the remote machine not being accessible
to casual logging in or browsing.  at least for my own purposes
there's no other method to get to that machine unless i want to
use a horrible web interface.


Ok. My setup, using bookmarks and login data in the keyring, allows me
to browse any of my remotes after two mouse clicks: one to open the
bookmark list and one to select the site.


   when i transfer files back and forth for the website i'm not
always using direct copies and only in one direction being
important.

   if i make a change on the website end and don't want my next
batch of transferred files to clobber it FileZilla has the
options for not having that happen.  in a batch of 1500 files
with many subdirectories that isn't possible with a simple copy
from one tab to another.


Right. That makes sense. I hardly ever want what's on a site and the
local copy to differ, so for me copying between tabs/windows is fine.

Regards,
Frank

Re: FileZilla / ftp / GnuTLS error connecting to sites with Testing/Bullseye

2021-02-13 Thread Frank


Op 12-02-2021 om 22:18 schreef Gary Dale:

On 2021-02-12 14:12, Frank wrote:

Op 12-02-2021 om 18:19 schreef Gary Dale:

I appreciate the people doing this, but this is a serious issue. I have
to resort to firing up a VM or resorting to the command line on my local
server to update my web sites because I can't do it from Testing.

What file manager do you use?

I stopped using FileZilla for ftps years ago and only use MATE's caja
these days. Hasn't stopped working and I keep my (bullseye) system
up-to-date, so whatever TLS library caja is using, this bug doesn't
affect it.

Regards,
Frank


I can do the same with Dolphin but I find it clumsy. FileZIlla is made
to let you transfer files between local and remote directories.


That's exactly what I do with caja, either from one tab to the other or
between separate windows. I'm not sure what's supposed to be clumsy
about it.

Re: FileZilla / ftp / GnuTLS error connecting to sites with Testing/Bullseye

2021-02-12 Thread Frank de Bruijn


Op 12-02-2021 om 20:15 schreef Paul Scott:

On 2/12/21 12:12 PM, Frank wrote:

Op 12-02-2021 om 18:19 schreef Gary Dale:

I appreciate the people doing this, but this is a serious issue. I have
to resort to firing up a VM or resorting to the command line on my local
server to update my web sites because I can't do it from Testing.

What file manager do you use?

I stopped using FileZilla for ftps years ago and only use MATE's caja
these days. Hasn't stopped working and I keep my (bullseye) system
up-to-date, so whatever TLS library caja is using, this bug doesn't
affect it.



gFtp seems to fail also.  Do you know what works for Gnome on sid?


No idea, sorry.

I use Xfce, but I don't like Thunar, so I installed caja. caja is based 
on GNOME's nautilus, so would expect that to work as well. Haven't tried 
it though.


Regards,
Frank

Re: FileZilla / ftp / GnuTLS error connecting to sites with Testing/Bullseye

2021-02-12 Thread Frank


Op 12-02-2021 om 18:19 schreef Gary Dale:

I appreciate the people doing this, but this is a serious issue. I have
to resort to firing up a VM or resorting to the command line on my local
server to update my web sites because I can't do it from Testing.

What file manager do you use?

I stopped using FileZilla for ftps years ago and only use MATE's caja
these days. Hasn't stopped working and I keep my (bullseye) system
up-to-date, so whatever TLS library caja is using, this bug doesn't
affect it.

Regards,
Frank

Re: Firefox problem

2021-02-05 Thread Frank Miles

On Wed, 03 Feb 2021 05:20:01 +0100, Charles Curley wrote:

> On Tue, 2 Feb 2021 23:12:52 - (UTC)
> Frank Miles  wrote:
> 
>> With the most recent Firefox update, some of the widgets on a 
>> Bibliocommons (library) website cease working.  They still work
>> either using the Epiphany browser, or my android phone.
>> 
>> Any recommendations on how I might debug this?
> 
> Sometimes Firefox loses its marbles. To check on this, shut Firefox
> down, move ~/.mozilla aside (rename it), then start Firefox up again.
> 
> If that solves the problem, you have some re-installing to do. If that
> doesn't solve the problem, reverse the above.

That fixes it!  As such, I presume it's a matter of piece-by-piece
"installing" add-ons and configuration settings, not installing Firefox
itself since that "works".

Thanks for the tip!!
  Frank

Firefox problem

2021-02-02 Thread Frank Miles

With the most recent Firefox update, some of the widgets on a 
Bibliocommons (library) website cease working.  They still work
either using the Epiphany browser, or my android phone.

Any recommendations on how I might debug this?

Running DebianAmd64 'Buster'.

Thanks for any suggestions!
  -Frank

Re: [OT] Wifi AP for Gigabit LAN/WAN

2021-01-25 Thread Frank Michael Dienst


Hi,


have a look to ubiquiti-AP.

https://www.ui.com/unifi/unifi-ap-ac-pro/

The AP-AC-Pro systems with two RJ45-connectors work with bonding up to 
2,5 Gbit.




Am 25.01.21 um 20:16 schrieb basti:

Hello,
at the moment I use 802.11n /2.4GHz wifi. I get 1 Gbit down/250 Mbit up
WAN in 2 months.
I'm search for wifi AP to get the best out of my WAN connection.
I know I need 5GHz wifi.

Are there any recommends?

best regards




--
This email was Virus checked by Sophos UTM. http://www.sophos.de


smime.p7s
Description: S/MIME cryptographic signature

Re: pgadmin4 en poort 80 reeds ingebruik

2021-01-23 Thread Frank Voncken

Geert Stappers schreef op za 23-01-2021 om 16:55 [+0100]:
> On Sat, Jan 23, 2021 at 04:08:04PM +0100, Frank Voncken wrote:
> > Geert Stappers schreef op za 23-01-2021 om 15:54 [+0100]:
> > > Echter denk ik dat hem niets vertelt is over de "port already in
> > > use".
> > > 
> > > Het VM-traject is de moeite waard om in te gaan. Mogelijk om
> > > pgadmin4
>     Het VM-traject is de moeite waard om in te gaan. Mogelijkheid om
> pgadmin4
> > > eerder aan de praat te krijgen, zou voor mij zijn kijken wat er
> > > op de
> > > HTTP poort luistert:
> > > 
> > >   sudo ss -ltp | grep http
> > 
> > Output van de commando:
> > 
> > sudo ss -ltp | grep http
> > [sudo] wachtwoord voor familie: 
> > LISTEN 0  511  0.0.0.0:http    0.0.0.0:*   
> > users:(("nginx",pid=703,fd=6),("nginx",pid=702,fd=6),("nginx",pid=7
> > 01,f
> > d=6),("nginx",pid=700,fd=6),("nginx",pid=699,fd=6),("nginx",pid=698
> > ,fd=
> > 6),("nginx",pid=697,fd=6),("nginx",pid=696,fd=6),("nginx",pid=695,f
> > d=6)
> > )
> > LISTEN 0  511 [::]:http   [::]:*   
> > users:(("nginx",pid=703,fd=7),("nginx",pid=702,fd=7),("nginx",pid=7
> > 01,f
> > d=7),("nginx",pid=700,fd=7),("nginx",pid=699,fd=7),("nginx",pid=698
> > ,fd=
> > 7),("nginx",pid=697,fd=7),("nginx",pid=696,fd=7),("nginx",pid=695,f
> > d=7)
> > )
> > 
> > Hoe interpeteer je dat? 
> > 
> 
> Dat webserver nginx reeds poort 80 ingebruik heeft.
> Dat nu bekend is wat de oorzaak van de 
> > > > jan 23 13:34:36 envy apachectl[7499]: (98)Address already in
> > > > use: AH00072: make_sock: could not bind to address [::]:80
> is
> 
> Dat er nu gekozen moet worden welke service poort 80 krijgt.
> 
> 
>   systemctl --failed
>   # kijk wat er faalt
>   sudo systemctl stop nginx
>   sudo systemctl start "de gefaalde service"
>   systemctl --failed
>   # waarschijnlijk is nu geen gefaalde dienst
>   probeer  pgadmin4
> 
Super! pgadmin4 is normaal en zonder fout geïnstalleerd! Echter,
probeer ik de desktop app PG Admin4 op te starten, dan lukt het niet:
het programma sluit meteen zichzelf af. De app werd niet opgestart.
Waarschijnlijk toch dependencies problemen... Mmm, hoewel ik weer wat
geleerd heb van systemctl --failed (geweldige commando!), heb ik de
neiging om Bas gelijk te geven en het maar op te geven.

Op het andere forum Debian GIS kwam iemand met een losse pgadmin4 deb-
pakket dat geschikt zou zijn voor Bullseye. Daarnaast stelt Richard
Duivenvoorde een alternatief voor: DBeaver (https://dbeaver.io). Ik ga
beide mogelijkheden bekijken.

Frank

Re: pgadmin4 en poort 80 reeds ingebruik

2021-01-23 Thread Frank Voncken

Geert Stappers schreef op za 23-01-2021 om 15:54 [+0100]:
> 
> > apache2_invoke: Enable module wsgi
> > Job for apache2.service failed because the control process exited
> > with
> > error code.
> > See "systemctl status apache2.service" and "journalctl -xe" for
> > details.
> > invoke-rc.d: initscript apache2, action "restart" failed.
> > ● apache2.service - The Apache HTTP Server
> >  Loaded: loaded (/lib/systemd/system/apache2.service; enabled;
> > vendor preset: enabled)
> >  Active: failed (Result: exit-code) since Sat 2021-01-23
> > 13:34:36 CET; 6ms ago
> >    Docs: https://httpd.apache.org/docs/2.4/
> >     Process: 7496 ExecStart=/usr/sbin/apachectl start (code=exited,
> > status=1/FAILURE)
> >     CPU: 15ms
> > 
> > jan 23 13:34:36 envy systemd[1]: Starting The Apache HTTP Server...
> > jan 23 13:34:36 envy apachectl[7499]: (98)Address already in use:
> > AH00072: make_sock: could not bind to address [::]:80
> 
> IPv6 poort 80 reeds ingebruik
> 
> 
> > jan 23 13:34:36 envy apachectl[7499]: (98)Address already in use:
> > AH00072: make_sock: could not bind to address 0.0.0.0:80
> 
> IPv4 poort 80 reeds ingebruik
> 
> 
> > jan 23 13:34:36 envy apachectl[7499]: no listening sockets
> > available, shutting down
> > jan 23 13:34:36 envy apachectl[7499]: AH00015: Unable to open logs
> > jan 23 13:34:36 envy apachectl[7496]: Action 'start' failed.
> > jan 23 13:34:36 envy apachectl[7496]: The Apache error log may have
> > more information.
> > jan 23 13:34:36 envy systemd[1]: apache2.service: Control process
> > exited, code=exited, status=1/FAILURE
> > jan 23 13:34:36 envy systemd[1]: apache2.service: Failed with
> > result 'exit-code'.
> > jan 23 13:34:36 envy systemd[1]: Failed to start The Apache HTTP
> > Server.
> > Instellen van pgadmin4-desktop (4.29) ...
> > Instellen van pgadmin4-web (4.29) ...
> > Instellen van pgadmin4 (4.29) ...
> > Bezig met afhandelen van triggers voor desktop-file-utils (0.26-1)
> > ...
> > Bezig met afhandelen van triggers voor gnome-menus (3.36.0-1) ...
> > Bezig met afhandelen van triggers voor mailcap (3.68) ...
> > 
> > 
> > Kennelijk wil "The Apache HTTP Server niet opgestart worden. Ik heb
> > gisteravond aan Sebastiaan Couwenberg (van het Debian GIS project)
> > een
> > iets andere vraag gesteld, maar wel hierover. Hij zegt dat pgadmin4
> > "waarschijnlijk het problematische dependencies heeft waardoor het
> > alleen op oudere systemen [dan Bullseye, FVO] werkt". Hij
> > suggereert om
> > "buster VM opzetten met KVM en virt-manager of virtualbox". Geen
> > idee
> > hoe ik dat ga doen, dus ik ga de vraag posten op forum van het
> > Debian
> > GIS project zoals Sebastiaan het mij adviseert. 
> 
> Weet dat Bas een erg slimme gast is,  danwel dat ik hoog heb staan.
> Zijn advies om virtualisation te gebruiken om een werkende combinatie
> te kunnen is een goed advies. 

Johan van de Wauw in de Debian GIS mailing list gaf zojuist aan dat hij
goede ervaring met PGAdmin4 in combinatie met Docker heeft. Ik ben niet
bekend met Docker, en kijkende in de website van Docker staat dat het
alleen met Debian 10 en 9 gebruikt kan worden. Geen Bullseye dus. 
Zucht...


> Echter denk ik dat hem niets vertelt
> is over de "port already in use".
> 
> Het VM-traject is de moeite waard om in te gaan. Mogelijk om pgadmin4
> eerder aan de praat te krijgen, zou voor mij zijn kijken wat er op de
> HTTP poort luistert:
> 
>   sudo ss -ltp | grep http

Output van de commando:

sudo ss -ltp | grep http
[sudo] wachtwoord voor familie: 
LISTEN 0  511  0.0.0.0:http0.0.0.0:*   
users:(("nginx",pid=703,fd=6),("nginx",pid=702,fd=6),("nginx",pid=701,f
d=6),("nginx",pid=700,fd=6),("nginx",pid=699,fd=6),("nginx",pid=698,fd=
6),("nginx",pid=697,fd=6),("nginx",pid=696,fd=6),("nginx",pid=695,fd=6)
)
LISTEN 0  511 [::]:http   [::]:*   
users:(("nginx",pid=703,fd=7),("nginx",pid=702,fd=7),("nginx",pid=701,f
d=7),("nginx",pid=700,fd=7),("nginx",pid=699,fd=7),("nginx",pid=698,fd=
7),("nginx",pid=697,fd=7),("nginx",pid=696,fd=7),("nginx",pid=695,fd=7)
)

Hoe interpeteer je dat? 

> 
> 
> 
> > Het resultaat van hun antwoord zal ik hier posten zodat de vraag op
> > onze forum goed afgesloten kan worden. Wordt vervolgd!
> 
> 
> Goed bezig

Dank je! Volhouder wint (soms...)
> 
Groet,
Frank

Re: pakket uit een 'andere Debian' ophalen, pgadmin4

2021-01-23 Thread Frank Voncken

Geert Stappers schreef op vr 22-01-2021 om 23:24 [+0100]:
> On Fri, Jan 22, 2021 at 09:59:49PM +0100, Frank Voncken wrote:
> > Beste mensen,
> > 
> > Voor een cursus moet ik PGAdmin4 installeren op mijn laptop met
> > Bullseye. Omdat PGAdmin4 niet in het pakket zit, volgde ik de
> > aanwijzingen op de website:
> > https://www.pgadmin.org/download/pgadmin-4-apt/
> > 
> > Resultaat is het volgende:
> > 
> > sudo sh -c 'echo "deb 
> > https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/$(lsb_release -
> > cs) pgadmin4 main" > /etc/apt/sources.list.d/pgadmin4.list && apt
> > update'
> > Geraakt:1 http://security.debian.org/debian-security bullseye-
> > security
> > InRelease
> > Geraakt:2 http://deb.debian.org/debian bullseye InRelease
> > Geraakt:3 http://deb.debian.org/debian bullseye-updates
> > InRelease 
> > Genegeerd:4 
> > https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/bullseye pgadmi
> > n4 InRelease
> > Fout:5
> > https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/bullseye pgadmi
> > n4 Release
> >   404  Not Found [IP: 2a02:16a8:dc51::55 443]
> > Pakketlijsten worden ingelezen... Klaar
> > E: De pakketbron '
> > https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/bullseye pgadmi
> > n4
> > Release' heeft geen Release-bestand.
> > N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan
> > niet veilig gebeuren en is daarom standaard uitgezet.
> > N: Zie de man-pagina apt-secure(8) voor details over het aanmaken
> > van een pakketbron en over de configuratie langs gebruikerskant.
> > 
> > Kennelijk kan het niet direct voor Bullseye. Omdat de website zegt
> > dat
> > het wel beschikbaar is voor Buster, moet ik waarschijnlijk op een
> > of op
> > andere manier in sources.list iets van Buster toevoegen zodat het
> > pakket pgadmin4 opgehaald kan worden. Is het mogelijk om een pakket
> > uit
> > een 'lagere' versie van Debian op te halen? Zo ja, hoe kan ik het
> > doen?
> 
> Merk op dat niet gevraagd wordt hoe verstandig dat is,
> dus wordt er ook verder niets over gezegd.

Tsja, PG Admin is wel een vereiste voor de cursus. Ik zal de
cursusleider hierover hebben.

> 
> 
> Het is 
> > sudo sh -c 'echo "deb  
> > https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/$(lsb_release -
> > cs) pgadmin4 main" > /etc/apt/sources.list.d/pgadmin4.list && apt
> > update'
> waar het allemaal gebeurde.  Om bij lagere versie pgadmin4 te komen:
> 
>   sudo $EDITOR /etc/apt/sources.list.d/pgadmin4.list
>   # Verander
>   #  deb
> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/bullseye pgadmin4
> main
>   # in
>   #  deb
> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/buster pgadmin4
> main
>   # bewaar bestand, verlaat editor
>   sudo apt update
> 
> En dan zou installatie
> 
>   sudo apt install pgadmin4
> 
> moeten lukken.
> 
> 
> Vertel a.u.b. een keer hoe het gegaan is.
> 
> 
> Groeten
> Geert Stappers

Bedankt voor de aanwijzing! Het resultaat is het volgende:

sudo apt install pgadmin4
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd   
De statusinformatie wordt gelezen... Klaar
De volgende extra pakketten zullen geïnstalleerd worden:
  libapache2-mod-wsgi-py3 pgadmin4-desktop pgadmin4-server pgadmin4-web
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
  libapache2-mod-wsgi-py3 pgadmin4 pgadmin4-desktop pgadmin4-server
pgadmin4-web
0 opgewaardeerd, 5 nieuw geïnstalleerd, 0 te verwijderen en 2 niet
opgewaardeerd.
Er moeten 71,7 MB aan archieven opgehaald worden.
Na deze bewerking zal er 293 kB extra schijfruimte gebruikt worden.
Wilt u doorgaan? [J/n] j
Ophalen:1 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/buster
pgadmin4/main amd64 pgadmin4-server amd64 4.29 [71,3 MB]
Ophalen:2 http://deb.debian.org/debian bullseye/main amd64 libapache2-
mod-wsgi-py3 amd64 4.7.1-3+b1 [99,7 kB]
Ophalen:3 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/buster
pgadmin4/main amd64 pgadmin4-desktop amd64 4.29 [385 kB]  
Ophalen:4 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/buster
pgadmin4/main all pgadmin4-web all 4.29 [2.360 B] 
Ophalen:5 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/buster
pgadmin4/main all pgadmin4 all 4.29 [836 B]   
71,7 MB opgehaald in 13s (5.605 kB/s) 
Voorheen niet geselecteerd pakket libapache2-mod-wsgi-py3 wordt
geselecteerd.
(Database wordt ingelezen ... 436166 bestanden en mappen momenteel
geïnstalleerd.)
Uitpakken van .../libapache2-mod-wsgi-py3_4.7.1-3+b1_amd64.deb wordt
voorbereid...
Bezig m

pakket uit een 'andere Debian' ophalen

2021-01-22 Thread Frank Voncken

Beste mensen,

Voor een cursus moet ik PGAdmin4 installeren op mijn laptop met
Bullseye. Omdat PGAdmin4 niet in het pakket zit, volgde ik de
aanwijzingen op de website:
https://www.pgadmin.org/download/pgadmin-4-apt/

Resultaat is het volgende:

sudo sh -c 'echo "deb
https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/$(lsb_release -cs)
pgadmin4 main" > /etc/apt/sources.list.d/pgadmin4.list && apt update'
Geraakt:1 http://security.debian.org/debian-security bullseye-security
InRelease
Geraakt:2 http://deb.debian.org/debian bullseye InRelease
Geraakt:3 http://deb.debian.org/debian bullseye-updates InRelease 
Genegeerd:4
https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/bullseye pgadmin4
InRelease
Fout:5 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/bullseye
pgadmin4 Release
  404  Not Found [IP: 2a02:16a8:dc51::55 443]
Pakketlijsten worden ingelezen... Klaar
E: De pakketbron
'https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/bullseye pgadmin4
Release' heeft geen Release-bestand.
N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet
veilig gebeuren en is daarom standaard uitgezet.
N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van
een pakketbron en over de configuratie langs gebruikerskant.

Kennelijk kan het niet direct voor Bullseye. Omdat de website zegt dat
het wel beschikbaar is voor Buster, moet ik waarschijnlijk op een of op
andere manier in sources.list iets van Buster toevoegen zodat het
pakket pgadmin4 opgehaald kan worden. Is het mogelijk om een pakket uit
een 'lagere' versie van Debian op te halen? Zo ja, hoe kan ik het doen?

Groet,
Frank

Re: apt-key deprecated

2021-01-12 Thread Frank


Op 12-01-2021 om 07:47 schreef Erwan David:

Hello,
to install signal desktop client, I followed their instructions, which
is to add their repository and, obviously their Kry.

However, I got a warning
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d
instead (see apt-key(8)).

But how to do this ?

man apt-key says :
Note: Instead of using this command a keyring should be placed directly
in the /etc/apt/trusted.gpg.d/ directory with a descriptive name and
either "gpg" or "asc" as file extension.

So the question is how can I get a keyring file from the key file I
downloaded ?


If that's the keys.asc file that starts with

-BEGIN PGP PUBLIC KEY BLOCK-

then that *is* the (ascii armoured) keyring file.

You can put that in /etc/apt/trusted.gpg.d/

Regards,
Frank

(solved) Re: fibre problem with Intel 82571EB

2020-11-23 Thread Frank Weißer


Thanks to Wolfgang from > debian-...@lists.debian.org

the following did the trick:


IMO this is not a network card issue.
I guess renaming the interface names would help.

Only do the following if the system isn't used by anyone else...

(0) Put down the MAC addresses of eth3 and eth4 (eth4 should be eth0 and
 eth3 should be eth1 later)
(1) Remove 'net.ifnames=0' from the kernel command line in /etc/default/grub
(2) Run 'update-grub'
(3) Reboot. 'ip a' will show you the persistent network interface names
(probably something like enpXsY, where Y is the slot name) and MACs
(4) Add MAC matching lines at the begin of /etc/network/interfaces, e.g.:
rename enp0s3=eth0
rename enp0s8=eth1
(5) Reboot and check if everything works, otherwise fix the renaming lines


Frank Weißer:

Hi folks!
Situation:
Debian-Edu 10 Server with

eth0 NC(=unused)
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network 
Connection (rev 02)
     Subsystem: Fujitsu Technology Solutions 82566DM-2 Gigabit 
Network Connection

     Kernel driver in use: e1000e

eth1-4
eth1 NC
eth2 NC
eth3 flags=4163  mtu 1500
     inet 192.168.0.254  netmask 255.255.255.0
eth4 flags=4163  mtu 1500
     inet 10.0.2.2  netmask 255.0.0.0
04:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet 
Controller (Fiber) (rev 06)

     Subsystem: Intel Corporation PRO/1000 PF Quad Port Server Adapter
     Kernel driver in use: e1000e

I can reach tjener via fibre cable and switch and use it with scp, smb 
and so on.

But dhcp, bxe-boot and ltsp-clients don't work.

dhcp requests via
#dhclient eth4
need about 70 seconds to give me an ip. Network manager already gives up 
in that time. Even connecting direct (with a media converter, not using 
other fiber cables or switches) doesn't work.

So cable/switch don't seam to hurt.

How can I tell 82571EB to do its work?

If I switch eth4's address to eth0 (copper) everything works fine. So 
services seem to be running


appreciating any answer

readu
Frank

fibre problem with Intel 82571EB

2020-11-20 Thread Frank Weißer


Hi folks!
Situation:
Debian-Edu 10 Server with

eth0 NC(=unused)
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network 
Connection (rev 02)
Subsystem: Fujitsu Technology Solutions 82566DM-2 Gigabit 
Network Connection

Kernel driver in use: e1000e

eth1-4
eth1 NC
eth2 NC
eth3 flags=4163  mtu 1500
inet 192.168.0.254  netmask 255.255.255.0
eth4 flags=4163  mtu 1500
inet 10.0.2.2  netmask 255.0.0.0
04:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet 
Controller (Fiber) (rev 06)

Subsystem: Intel Corporation PRO/1000 PF Quad Port Server Adapter
Kernel driver in use: e1000e

I can reach tjener via fibre cable and switch and use it with scp, smb 
and so on.

But dhcp, bxe-boot and ltsp-clients don't work.

dhcp requests via
#dhclient eth4
need about 70 seconds to give me an ip. Network manager already gives up 
in that time. Even connecting direct (with a media converter, not using 
other fiber cables or switches) doesn't work.

So cable/switch don't seam to hurt.

How can I tell 82571EB to do its work?

If I switch eth4's address to eth0 (copper) everything works fine. So 
services seem to be running


appreciating any answer

readu
Frank

Re: Hiding an app

2020-10-13 Thread Frank McCormick





On 10/13/20 1:37 PM, Carl Fink wrote:

On 10/13/20 12:17 PM, Frank McCormick wrote:


I am running the Mate desktop on Debian Bullseye. I just installed 
TZclock after removing the Mate clock from the taskbar.

One annoyance is TZclock appears on the taskbar. Does anyone
know how to prevent this?


Is it in the Notification Area? Right click in a blank part of the area 
(I use the top row of pixels) and choose


Panel >> Panel Preferences

Unselect TZClock.



   No, it appears in the window list area, the same area where other 
running applications appear. Other window managers provide a way to skip 
the task bar for applications, but I can't find any way to do it in Mate.


--
Frank McCormick

Hiding an app

2020-10-13 Thread Frank McCormick




I am running the Mate desktop on Debian Bullseye. I just installed 
TZclock after removing the Mate clock from the taskbar.

One annoyance is TZclock appears on the taskbar. Does anyone
know how to prevent this?

Thanks

--
Frank McCormick

Re: can't boot to a graphical interface.

2020-10-03 Thread Frank McCormick





On 10/3/20 11:20 AM, Kent West wrote:



On Sat, Oct 3, 2020 at 8:01 AM songbird <mailto:songb...@anthive.com>> wrote:


Frank McCormick wrote:
 > While compiling an application today my Debian bullseye system
somehow
 > got messed up. It will boot to a CLI but no X, apparently because
for
 > some reason the system is unable to access some files in
 > /usr/share/dbus-1. It keeps saying access denied. The directories
and
 > files are owned by root, and if I noot to a CLI I have no trouble
 > accessing them using sudo and midnight commander.
 >
 > I tried reinstalling systemd but it ended with the same problem.


On my bullseye/sid lappie, for comparison to yours:

kent@westk-9463:~$ ls -lah /usr/share/dbus-1/
total 84K
drwxr-xr-x   8 root root 4.0K Sep 17 19:55 .
drwxr-xr-x 610 root root  20K Sep  5 16:26 ..
drwxr-xr-x   2 root root 4.0K Aug  6 20:50 accessibility-services
drwxr-xr-x   2 root root  12K Aug  6 21:03 interfaces
drwxr-xr-x   2 root root  20K Aug  6 20:55 services
-rw-r--r--   1 root root 3.6K Jul  2 08:19 session.conf
drwxr-xr-x   2 root root 4.0K Sep 17 19:55 session.d
-rw-r--r--   1 root root 5.7K Jul  2 08:19 system.conf
drwxr-xr-x   2 root root 4.0K Sep 17 19:55 system.d
drwxr-xr-x   2 root root 4.0K Aug  6 21:08 system-services

kent@westk-9463:~$ ls -lahd /usr/share/dbus-1/
drwxr-xr-x 8 root root 4.0K Sep 17 19:55 /usr/share/dbus-1/




My system now is back to **normal**. I re-installed
about a dozen packages including systemd.
I also changed one mode  to match yours.

frank@franklin:~$ ls -lah /usr/share/dbus-1/
total 44K
drwxr-xr-x   6 root root 4.0K Oct  3 10:08 .
drwxr-xr-x 246 root root  12K Oct  2 16:56 ..
drwxr-xr-x   2 root root 4.0K Oct  3 10:08 interfaces
drwxr-xr-x   2 root root 4.0K Oct  3 09:20 services
-rw-r--r--   1 root root 3.6K Jul  2 09:19 session.conf
-rw-r--r--   1 root root 5.7K Jul  2 09:19 system.conf
drwxr-xr-x   2 root root 4.0K Oct  3 10:08 system.d
drwxr-xr-x   2 root root 4.0K Oct  3 10:08 system-services

Still don't know what the h*ll happened.

Thanks Kent
--
Frank McCormick

can't boot to a graphical interface.

2020-10-02 Thread Frank McCormick

While compiling an application today my Debian bullseye system somehow 
got messed up. It will boot to a CLI but no X, apparently because for 
some reason the system is unable to access some files in 
/usr/share/dbus-1. It keeps saying access denied. The directories and 
files are owned by root, and if I noot to a CLI I have no trouble 
accessing them using sudo and midnight commander.


I tried reinstalling systemd but it ended with the same problem.

Can anyone help?

Thanks


--
Frank McCormick

Re: dns cache for localdomain via djbdns

2020-08-12 Thread Patrick Frank




On 12.08.20 15:28, Dan Ritter wrote:

Greg Wooledge wrote:

On Wed, Aug 12, 2020 at 02:59:23PM +0200, Patrick Frank wrote:



Greg writes: You can execute the "./run" script by hand for testing
purposes [...]

When I tried "exec envuidgid Gnscache ..." it logged me out.


Greg writes: unicorn:~$ ls -l /etc/dnscache/

This directory is missing the "supervise" directory.


Dan writes: svc -d /service/dnscache

It outputs: unable to control /service/dnscache: file does not exist


P.

dns cache for localdomain via djbdns

2020-08-12 Thread Patrick Frank


Hello,

on a Debian 10 host I created a virtual machine with very basic features
to build a dns cache for my home network with djbdns. I fail to understand
how Daemontools are used properly.

Following the instructions on http://cr.yp.to/djbdns/install.html went okay.
http://cr.yp.to/djbdns/run-cache-x.html at step 5 is where I am stuck.

When I go to /service/dnscache and execute "run" it says "starting" so I
try svstat /service/dnscache which outputs:
"/service/dnscache: unable to open supervise/ok: file does not exist"

Any hints, please?

P.

Re: Slic3r --gui won't run

2020-07-19 Thread Frank


Op 19-07-2020 om 16:32 schreef Reco:

On Sun, Jul 19, 2020 at 10:28:08AM -0400, Gene Heskett wrote:

Whats my sources.list suposed to look like?


One of the possible ways of doing it:

deb http://ftp.debian.org/debian/ stretch main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free

Reco


Don't use ftp.debian.org.

https://wiki.debian.org/ftp.debian.org

Regards,
Frank

Re: Update errors

2020-07-08 Thread Frank McCormick





On 7/8/20 10:45 AM, Sven Joachim wrote:

On 2020-07-08 10:20 -0400, Frank McCormick wrote:


Apt flagged a couple of errors during this morning upate.


Warnings, not errors, and they are coming from dpkg.


dpkg: warning: unable to delete old directory
'/usr/share/fonts/woff/font-awesome': Directory not empty dpkg:
warning: unable to delete old directory '/usr/share/fonts/woff':
Directory not empty dpkg: warning: unable to delete old directory
'/usr/share/fonts/svg/font-awesome': Directory not empty dpkg:
warning: unable to delete old directory '/usr/share/fonts/svg':
Directory not empty dpkg: warning: unable to delete old directory
'/usr/share/fonts/eot/font-awesome': Directory not empty dpkg:
warning: unable to delete old directory '/usr/share/fonts/eot':
Directory not empty

Should I go in an remove these directories/files...or just leave it alone ?


I have deleted the spurious .uuid files and their parent directories as
they are cruft, but leaving them in place would not cause harm either.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040

Cheers,
Sven



Seems this bug has been around for quite a while.

Thanks
--
Frank McCormick

Update errors

2020-07-08 Thread Frank McCormick


Apt flagged a couple of errors during this morning upate.

dpkg: warning: unable to delete old directory 
'/usr/share/fonts/woff/font-awesome': Directory not empty dpkg: warning: 
unable to delete old directory '/usr/share/fonts/woff': Directory not 
empty dpkg: warning: unable to delete old directory 
'/usr/share/fonts/svg/font-awesome': Directory not empty dpkg: warning: 
unable to delete old directory '/usr/share/fonts/svg': Directory not 
empty dpkg: warning: unable to delete old directory 
'/usr/share/fonts/eot/font-awesome': Directory not empty dpkg: warning: 
unable to delete old directory '/usr/share/fonts/eot': Directory not empty


Should I go in an remove these directories/files...or just leave it alone ?



--
Frank McCormick

HP Device Manager loses network printer on shutdown

2020-05-18 Thread Frank Weißer


Hi!

Everytime I start my workstation (DebianEdu 9) I have to re-run setup of 
the HP Device Manager , because the LaserJet Pro 200 color, connected 
via network, is lost. The setup routine dousn't need to connect to hp 
again, as id did at the first installation of the printer.


Where do I have to take a look?

Any help appreciated.

readU
Frank

Re: make apt show packages in column

2020-05-17 Thread Frank


Op 17-05-2020 om 02:39 schreef Ihor Antonov:

Hi

when installing a package with multiple dependencies apt gives an output:
(example: apt install gnome)


The following NEW packages will be installed:

  accountsservice aisleriot apache2-bin apg baobab bluez bluez-obexd
  bogofilter ogofilter-bdb bogofilter-common bolt brasero-common
  caribou cheese cheese-common chrome-gnome-shell cracklib-runtime
  dconf-cli dleyna-server eog evince evince-common evolution
  evolution-common evolution-data-server evolution-data-server-common
  evolution-plugin-bogofilter evolution-plugin-pstimport
  evolution-plugins file-roller five-or-more
   ..

output truncated

It is very inconvenient to inspect the list of installed packages in
such output. Is it possible to make apt output this in a column?


Try the --verbose-versions switch?

apt-get --verbose-versions install gnome

seems to do what you want (at least it does here).

Regards,
Frank

Re: 'Oeps! Er is iets misgegaan.'

2020-04-17 Thread Frank Voncken




Frank Voncken schreef op vr 17-04-2020 om 07:37 [+]:
> Nog wat vergeten te vermelden: het opstarten van de laptop op vorige
> Linux header biedt ook geen soelaas.
> 
> 17 apr. 2020 09:33:59 Frank Voncken :
> 
> 
> > Bij het opstarten van mijn laptop met bullseye kreeg ik de
> > bovenstaande melding, zie ook bijlage. Ik probeerde het op mijn
> > andere oude laptop (ook met bullseye), daar kreeg ik ook dezelfde
> > melding. Ik vermoed dat er iets gruwelijks misgegaan is met een
> > update. In de rescue mode probeerde ik een apt update uit te
> > voeren, maar ik krijg geen contact met deb.debian.org.
> > Waarschijnlijk geen internetverbinding, ook niet met een kabel.
> > 
> > Hoe kan ik het oplossen?
> > 
> > Groet,
> > Frank

Ik heb het gelukkig weten te oplossen. Ik heb de laptop opgestart vanaf
usb stick met Debian installer en daar de rescue mode gebruikt. Alleen
daar heb ik wel internetverbinding, in tegenstelling tot de rescue mode
vanaf grub scherm tijdens de boot. Nadat ik in de rescue mode van
Debian installer was gekomen, was het even zoeken naar de juiste
partitie waar ik shell commando's kan uitvoeren. Vervolgens heb ik apt
update en apt upgrade uitgevoerd: er bleken weer nieuwe gnome-shell
pakketten beschikbaar te zijn. Et voilà, ik heb normale Gnome
inlogscherm terug!

Vermoedelijk waren er bij de voorlaatste update & upgrade corrupte
pakketten (gnome-shell?) meegestuurd.

Groet,
Frank

Re: 'Oeps! Er is iets misgegaan.'

2020-04-17 Thread Frank Voncken

Nog wat vergeten te vermelden: het opstarten van de laptop op vorige Linux 
header biedt ook geen soelaas.

17 apr. 2020 09:33:59 Frank Voncken :

> Bij het opstarten van mijn laptop met bullseye kreeg ik de bovenstaande 
> melding, zie ook bijlage. Ik probeerde het op mijn andere oude laptop (ook 
> met bullseye), daar kreeg ik ook dezelfde melding. Ik vermoed dat er iets 
> gruwelijks misgegaan is met een update. In de rescue mode probeerde ik een 
> apt update uit te voeren, maar ik krijg geen contact met deb.debian.org. 
> Waarschijnlijk geen internetverbinding, ook niet met een kabel.
> 
> Hoe kan ik het oplossen?
> 
> Groet,
> Frank
> 
> 2 apr. 2020 22:36:30 Paul van der Vlis :
> 
> 
> > Hoi
> > 
> > De Pinephone is weer te bestellen:
> > https://www.pine64.org/2020/04/02/pinephone-ubports-community-edition-pre-orders-now-open/
> > Je schijnt er ook Debian op te kunnen draaien:
> > https://www.reddit.com/r/pinephone/comments/flzldb/debian_phosh_on_pinephone_is_my_favorite_so_far/
> > 
> > Groeten,
> > Paul
> > 
> > -- 
> > Paul van der Vlis Linux systeembeheer Groningen
> > https://www.vandervlis.nl/
> > 
> > 
> > 
> 
>

Systemd logging stopped (SOLVED)

I have since rebooted to a  shutdown and logging is back. I don't know 
why simple reboots didn't solve the problem but

it's solved now.

--
Frank McCormick

More info on systemd logging fail


Looking at dmesg I see a bunch of lines like this:

Stopping User Runtime Directory /run/user/118...
[   55.241395] systemd[897]: user-runtime-dir@118.service: Failed to 
connect stdout to the journal socket, ignoring: Connection refused

[   55.249255] systemd[1]: run-user-118.mount: Succeeded.

Started Run anacron jobs.
[ 2846.911055] systemd[2236]: anacron.service: Failed to connect stdout 
to the journal socket, ignoring: Connection refused

[ 2846.915533] systemd[1]: anacron.service: Succeeded.

Those are just two example of "failing to connect stdout to the journal 
socket"




--
Frank McCormick

Re: systemd logging stopped





On 2/4/20 11:30 AM, john doe wrote:

On 2/4/2020 4:56 PM, Frank McCormick wrote:

Noticed this morning that systemd is no longer logging boots on my machine.
There is a  log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find it.
I am running Debian Sid fully updated.

Can anyone help?



https://lists.debian.org/debian-user/2020/02/msg2.html

HTH.

--
John Doe



Yes, that's the one. But the message implies everything should happen 
automatically. In my case all it did was to stop logging.



--
Frank McCormick

Re: systemd logging stopped





On 2/4/20 11:31 AM, Peter Ehlert wrote:


On 2/4/20 7:56 AM, Frank McCormick wrote:
Noticed this morning that systemd is no longer logging boots on my 
machine.

There is a  log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find it.
I am running Debian Sid fully updated.



I got updated systemd (244.1-2) to 244.1-3 this morning, don't know if 
it relates... I have not rebooted for a few days





  Yes so did I, but still lo logging. systemd logs end at midnight last 
night when I suspended the system.

I have rebooted twice since.


--
Frank McCormick

systemd logging stopped