Host: h370 Kernel: 6.1.0-23-amd64 arch: x86_64 bits: 64 Desktop: KDE
> > Plasma
> >
> > v: 5.27.5 Distro: Debian GNU/Linux 12 (bookworm)
> >
> > rd@h370:~$
> >
> > It uses bridging network connections with libvirt work unreliable.
>
Am Donnerstag, 29. August 2024, 20:31:10 CEST schrieb Tim Woodall:
> On Wed, 28 Aug 2024, Rainer Dorsch wrote:
> > In the systemd log, the first entry indicating network problems is that
> > the DNS server switches to another interface. But it could easily be a
> > consequence and not the cause of
NU/Linux 12 (bookworm)
> rd@h370:~$
>
> It uses bridging network connections with libvirt work unreliable.
>
> I have in /etc/network/interface bridging networks e.g.
>
> iface eno1.2 inet manual
>
> # libvirt VM
> auto br2
> iface br2 inet dhcp
> # Use the MAC ad
On Wed, 28 Aug 2024, Rainer Dorsch wrote:
In the systemd log, the first entry indicating network problems is that the DNS
server switches to another interface. But it could easily be a consequence and
not the cause of the issue:
Aug 28 06:57:54 h370 dhclient[1195]: DHCPREQUEST for 192.168.4.203
Hello,
I have a (for me) weird problem on a bookworm system
rd@h370:~$ inxi -S
System:
Host: h370 Kernel: 6.1.0-23-amd64 arch: x86_64 bits: 64 Desktop: KDE Plasma
v: 5.27.5 Distro: Debian GNU/Linux 12 (bookworm)
rd@h370:~$
It uses bridging network connections with libvirt work unreliable
On Fri 01 Sep 2023 at 21:31:39 (+0100), Brad Rogers wrote:
> On Fri, 1 Sep 2023 14:02:31 -0600 D. R. Evans wrote:
>
> >So how do I fix this so that the networking is configured to work
> >correctly during the boot sequence, as it has always done before?
>
> I had changing ethernet port issues and
On Fri, 1 Sep 2023 18:33:51 -0400
Greg Wooledge wrote:
...
> Standard installation. But as you noted, it's optional. Debian *also*
> allows the use of Network Manager, systemd-networkd, and probably several
> other systems for configuring one's network(s).
Yes - I use iwd for basic (wireless)
On 02/09/2023 13:09, Brad Rogers wrote:
On Sat, 2 Sep 2023 12:08:37 +0100
Brian wrote:
Hello Brian,
I did not write any of the text you quote.
You did, but it was not what Timothy was responding to.
What you wrote was quoted right at the bottom of the message, and
irrelevant to Timothy's
On 2023-09-02, Brian wrote:
> On Sat 02 Sep 2023 at 19:37:22 +0100, Brian wrote:
>
>> On Sat 02 Sep 2023 at 08:19:56 -0600, D. R. Evans wrote:
>>
>> [...]
>>
>> > I will file a bug report.
>>
>> You have filed the report against general. This is a non-optimal
>> package. Someone may or may not
On Fri 01 Sep 2023 at 21:57:39 (-0400), Greg Wooledge wrote:
> On Fri, Sep 01, 2023 at 08:40:43PM -0500, David Wright wrote:
> > I know you have a low opinion of allow-hotplug, but I can't see that
> > auto/allow-auto is necessarily better for the naive user that doesn't
> > install a DE for whatev
evelopers deal with the exact cause and
> finding a proper fix.)
I've not used NM, but I looked at the man page for nmcli on archlinux,
and it says:
"down [id | uuid | path | apath] ID...
Deactivate a connection from a device without preventing the
device from further auto-a
Brian wrote on 9/2/23 04:51:
Installation over ethernet, no DE - ifupdown provided.
Installation over ethernet or wireless with a DE - network-manager provided.
Yep, that one's exactly what I experienced.
Although the machine is used more like a server than a desktop, it has DE
(KDE) to make
Brian wrote on 9/2/23 13:01:
Send a mail to
cont...@bugs.debian.org
Ib the mail body put
ressign 1051086 installation-report
thanks
Sorry. That's "reassign".
Done. Thank you.
I pondered where to assign in, and couldn't see anywhere that the report
really fit. (I interpreted "i
On Sat 02 Sep 2023 at 19:37:22 +0100, Brian wrote:
> On Sat 02 Sep 2023 at 08:19:56 -0600, D. R. Evans wrote:
>
> [...]
>
> > I will file a bug report.
>
> You have filed the report against general. This is a non-optimal
> package. Someone may or may not move it to a better place.
>
> Doing it
On Sat 02 Sep 2023 at 08:19:56 -0600, D. R. Evans wrote:
[...]
> I will file a bug report.
You have filed the report against general. This is a non-optimal
package. Someone may or may not move it to a better place.
Doing it for yourself:
Send a mail to
cont...@bugs.debian.org
Ib the mail b
Michael Kjörling wrote on 9/2/23 03:23:
You might want to poke around a little among the files in
/etc/NetworkManager, particularly /e/NM/system-connections. That's
what NetworkManager _should_ be using to set up the interfaces. See if
there's something there to explain the two seemi
Starting a new thread so that this doesn't get lost in the postings in the
original thread.
The original thread was started at:
https://lists.debian.org/debian-user/2023/09/msg00024.html
That post contains a description of the problem.
I now have a workaround (although not an explanation) fo
On Sat, 2 Sep 2023 08:44:38 -0400
Greg Wooledge wrote:
Hello Greg,
>Because we've already deleted the message from person
I can understand that for the occasional slip up (1), but when the
perpetrator does it habitually
(1) Over-zealous with the delete key, for example.
--
Regards
On Sat, Sep 02, 2023 at 01:09:45PM +0100, Brad Rogers wrote:
> Which begs the question:
> Why do some people respond to a message from person Y, when they're
> /actually/ dealing with something written by person X?
Because we've already deleted the message from person X, and didn't
notice the issu
"D. R. Evans" writes:
> I don't think that debian has used used /etc/network/interfaces for a
> while, at least not by default. Certainly there's nothing useful there
> on the machine that I just upgraded and whose networking is failing to
> configure itself correctly.
I used to think that too.
On Sat, 2 Sep 2023 12:08:37 +0100
Brian wrote:
Hello Brian,
>I did not write any of the text you quote.
You did, but it was not what Timothy was responding to.
What you wrote was quoted right at the bottom of the message, and
irrelevant to Timothy's response.
Which begs the question:
Why do
On Sat, Sep 2, 2023 at 6:34 AM Brian wrote:
> On Fri 01 Sep 2023 at 16:56:42 -0600, D. R. Evans wrote:
>
> > Michel Verdier wrote on 9/1/23 15:06:
> >
> > >
> > > If you want old names put in /etc/default/grub
> > >
> > > GRUB_CMDLINE_LINUX="net.ifnames=0"
> > >
> >
> > Nice to know, but I'll sta
On Fri 01 Sep 2023 at 22:32:00 +, Andy Smith wrote:
> Hello,
>
> On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote:
> > I don't think that debian has used used /etc/network/interfaces for a while,
> > at least not by default.
>
> All of my Debian servers (and desktops) have an
> /e
On Fri 01 Sep 2023 at 16:56:42 -0600, D. R. Evans wrote:
> Michel Verdier wrote on 9/1/23 15:06:
>
> >
> > If you want old names put in /etc/default/grub
> >
> > GRUB_CMDLINE_LINUX="net.ifnames=0"
> >
>
> Nice to know, but I'll stay with the new names, I think.
>
> > network manager is good
a little among the files in
/etc/NetworkManager, particularly /e/NM/system-connections. That's
what NetworkManager _should_ be using to set up the interfaces. See if
there's something there to explain the two seemingly being intertwined.
You might already have done this, of course, an
David Wright wrote on 9/1/23 19:40:
I don't see that the OP is doing anything complicated that requires
rc.local to run at all. They just need to distinguish between the two
Correct. I was simply trying to workaround the problem by putting commands
into rc.local that are known to work when I
On Fri, Sep 01, 2023 at 08:40:43PM -0500, David Wright wrote:
> I know you have a low opinion of allow-hotplug, but I can't see that
> auto/allow-auto is necessarily better for the naive user that doesn't
> install a DE for whatever reason.
>
> AIUI auto gives you a one-shot attempt to start the n
On Fri 01 Sep 2023 at 17:38:48 (-0400), Greg Wooledge wrote:
> On Fri, Sep 01, 2023 at 03:18:47PM -0600, D. R. Evans wrote:
> > [[ I speculate wildly that systemd or something doesn't complete configuring
> > the network until after rc.local has finished processing (I know that
> > rc.local execute
Michel Verdier wrote on 9/1/23 15:06:
If you want old names put in /etc/default/grub
GRUB_CMDLINE_LINUX="net.ifnames=0"
Nice to know, but I'll stay with the new names, I think.
network manager is good for changing networks. For a server the network
must not change normally. So you could p
Andy Smith wrote on 9/1/23 16:32:
Your situation appears to have been triggered by the renaming of
your network interfaces (which was warned about in the release
These weird names like "Wired connection enp11s0(eth0)" were names that the
debian installer came up with several OS versions ago (
On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote:
> Greg Wooledge wrote on 9/1/23 15:38:
>
> > In particular, when using /etc/network/interfaces, only interfaces that
> > are marked as "auto" need to be up, to satisfy this criterion. An
>
> I don't think that debian has used used /etc
Hello,
On Fri, Sep 01, 2023 at 04:16:46PM -0600, D. R. Evans wrote:
> I don't think that debian has used used /etc/network/interfaces for a while,
> at least not by default.
All of my Debian servers (and desktops) have an
/etc/network/interfaces file and ifupdown installed. It depends upon
choice
Greg Wooledge wrote on 9/1/23 15:38:
In particular, when using /etc/network/interfaces, only interfaces that
are marked as "auto" need to be up, to satisfy this criterion. An
I don't think that debian has used used /etc/network/interfaces for a while,
at least not by default. Certainly there
On Fri, Sep 01, 2023 at 03:18:47PM -0600, D. R. Evans wrote:
> [[ I speculate wildly that systemd or something doesn't complete configuring
> the network until after rc.local has finished processing (I know that
> rc.local executes late in the boot process, but I don't think that that
> means that
Thank you for your thoughts...
As people are addressing the rc.local issue (I now realise that I shouldn't
have mentioned it :-) )... I just checked, and:
1. rc.local is being executed;
2. it is executing the nmcli commands;
3. the commands are successful.
But it remains true that when the bo
On 2023-09-01, D. R. Evans wrote:
> The machine has two ethernet ports, which used to be eth0 and eth1 in the old
> days, but are now magically called "Wired connection enp11s0(eth0)" and "Wired
> connection enp12s0(eth1)".
If you want old names put in /etc/default/grub
GRUB_CMDLINE_LINUX="net.i
On 2023-09-01 at 16:50, Greg Wooledge wrote:
> On Fri, Sep 01, 2023 at 08:32:40PM +, Michael Kjörling wrote:
>
>> I don't think /etc/rc.local is executed by default on modern Debian
>> systems. Have you checked to make sure that rc-local.service is
>> enabled and actually gets started during b
On Fri, Sep 01, 2023 at 08:32:40PM +, Michael Kjörling wrote:
> I don't think /etc/rc.local is executed by default on modern Debian
> systems. Have you checked to make sure that rc-local.service is
> enabled and actually gets started during boot? Is there anything
> relevant in the logs for tha
On 1 Sep 2023 14:02 -0600, from doc.ev...@gmail.com (D. R. Evans):
> Well, great, sort-of, except that every time I reboot I have to manually
> issue the two above nmcli commands to take down and bring back up enp11s.
>
> I tried putting them in my rc.local file, but that had no effect (for
> reas
On Fri, 1 Sep 2023 14:02:31 -0600
"D. R. Evans" wrote:
Hello D.,
>So how do I fix this so that the networking is configured to work
>correctly during the boot sequence, as it has always done before?
I had changing ethernet port issues and found that creating
/etc/systemd/network/99-default.link
I just upgraded my main server to bookworm, having successfully, over the
course of the past couple of months, methodically upgraded my other machines
with only minor issues.
Unfortunately, the upgrade of the server, the most important of my machines,
has not been smooth at all, even though no
On Sat, Jul 15, 2023 at 1:09 PM David Mehler wrote:
>
> [...]
>
> "2. "I noticed that when I change UsePAM yes to UsePAM no then this
> issue is resolved."
>
> BINGO! I flipped that UsePAM setting to no and the problem has gone away.
If you need a datapoint about UsePAM... I've been setting it
On Sat 15 Jul 2023, at 17:52, David Mehler wrote:
[...]
> Regarding the original issue of the systemd upgrade and the invalid
> attributes [...] here is the output that I've got:
>
[...]
> Cannot set file attributes for '/var/log/journal', maybe due to
> incompatibility in specified attributes, pr
Hello,
Thanks. The ssh issue has been solved.
"The same symptoms appear in an answer to
https://superuser.com/questions/166359/why-is-my-ssh-login-slow
which includes various solutions, some more permanent/apparently
likely to help you than others.
Just out of interest, is the su command (on
On Sat 15 Jul 2023, at 13:09, Gareth Evans wrote:
>
> 2. "I noticed that when I change UsePAM yes to UsePAM no then this
> issue is resolved."
>
> There may be security (or other) issues with (2).
See, for example:
https://unix.stackexchange.com/questions/673153/sshd-what-are-the-practical-e
On Wed 12 Jul 2023, at 18:29, Gareth Evans wrote:
>> On 12 Jul 2023, at 15:12, David Mehler wrote:
>> [sshd login takes a long time]
> [...]
> Does
>
> ssh -vvv ...
>
> (at client) shed any light?
Replying to an off-list message from David in which he stated ssh -vvv waits
after
> debug1:
> On 12 Jul 2023, at 15:12, David Mehler wrote:
>
> Hello,
>
> I'm running Debian 12 on a vps. I just upgraded it and am now
> apparently running the latest systemd version 252.12-1. I saw an error
> about invalid attributes on /var/log/journal then it said ignoring.
> I've seen others with t
Hello,
I'm running Debian 12 on a vps. I just upgraded it and am now
apparently running the latest systemd version 252.12-1. I saw an error
about invalid attributes on /var/log/journal then it said ignoring.
I've seen others with this error but only in reference as far as I can
tell to the btrfs f
On 2023-05-10 09:28:51 -0400, Greg Wooledge wrote:
> On Wed, May 10, 2023 at 03:19:31PM +0200, Vincent Lefevre wrote:
> > On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> > > Note: if you play with .ssh/rc, be careful as there is a risk
> > > that you may not log in any more with ssh in case
On Wed, May 10, 2023 at 03:19:31PM +0200, Vincent Lefevre wrote:
> On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> > Note: if you play with .ssh/rc, be careful as there is a risk
> > that you may not log in any more with ssh in case of mistake
> > (I'm wondering whether there is an undocumen
On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> Note: if you play with .ssh/rc, be careful as there is a risk
> that you may not log in any more with ssh in case of mistake
> (I'm wondering whether there is an undocumented way to skip it).
For this point, there are solutions there:
https
On 2023-05-10 14:36:25 +0200, Vincent Lefevre wrote:
[...]
> zira:~> ssh cventin xterm
> Connected to cventin (from 140.77.51.8)
> OS: Debian GNU/Linux 12 (bookworm) [x86_64]
> DISPLAY: localhost:11.0
>
> and xterm is started as expected. FYI, some data, like DISPLAY, are
> output by my .ssh/rc sc
On 2023-05-09 20:07:26 +0200, zithro wrote:
> On 09 May 2023 18:06, Vincent Lefevre wrote:
> > On 2023-05-05 15:04:27 +0200, zithro wrote:
> > >
> > > journalctl after GUI LOGOFF
> > > -
On 2023-05-09 14:17:14 -0400, Dan Ritter wrote:
> zithro wrote:
> > On 09 May 2023 17:47, Vincent Lefevre wrote:
> > > BTW, you should also try GNU Screen to see if you have the same issue
> > > with it (this could help debugging).
> >
> > Do you mean trying "ssh u@h screen" ?
> > Never tried scr
On 2023-05-09 19:44:48 +0200, zithro wrote:
> On 09 May 2023 17:47, Vincent Lefevre wrote:
> > Hi,
> >
> > On 2023-05-04 21:07:17 +0200, zithro wrote:
> > > Here is what happens chronologically :
> > >
> > > 1. I start various SSH connections to a
zithro wrote:
> On 09 May 2023 17:47, Vincent Lefevre wrote:
> > BTW, you should also try GNU Screen to see if you have the same issue
> > with it (this could help debugging).
>
> Do you mean trying "ssh u@h screen" ?
> Never tried screen with GUI apps, does that work ?
Not in a useful way. For
On Tue, May 09, 2023 at 08:07:26PM +0200, zithro wrote:
> I use Ctrl-D to close ssh sessions, "~." does not work, I get "bash: command
> not found".
To use the tilde commands in the ssh client, they have to be at the
"beginning of a line", which means you have to press Enter first. Or
at least ha
On 09 May 2023 18:06, Vincent Lefevre wrote:
On 2023-05-05 15:04:27 +0200, zithro wrote:
journalctl after GUI LOGOFF
[...]
May 05 14:09:14 debzit sshd[14246
On 09 May 2023 17:47, Vincent Lefevre wrote:
Hi,
On 2023-05-04 21:07:17 +0200, zithro wrote:
Here is what happens chronologically :
1. I start various SSH connections to a host, some normal, some with X
forwarding, like that: "ssh user@host" and "ssh -X -n user@host GUI_APP&
On 2023-05-05 15:04:27 +0200, zithro wrote:
>
> journalctl after GUI LOGOFF
>
[...]
> May 05 14:09:14 debzit sshd[14246]: Received disconnect from IP.IP.IP.IP
>
Hi,
On 2023-05-04 21:07:17 +0200, zithro wrote:
> Here is what happens chronologically :
>
> 1. I start various SSH connections to a host, some normal, some with X
> forwarding, like that: "ssh user@host" and "ssh -X -n user@host GUI_APP"
> (like firejail
On 06 May 2023 07:07, to...@tuxteam.de wrote:
On Sat, May 06, 2023 at 10:24:52AM +0700, Max Nikulin wrote:
Thanks both for the pointers, will report back with results
On 05 May 2023 19:14, Max Nikulin wrote:
Does it happen for newly created user with no customization?
Never tried !
I recommended to do it just for a case that you added something to init
files for the "zithro" user.
AFAIK I didn't customize a lot, as I'm rarely logging to X.
But it won't
On 06 May 2023 06:45, David Wright wrote:
*I login to VC1 and startx for an Xserver*
I think that's why you don't have my problem, your user is always logged
in, even when you close X.
Is the greeter just deferring the ssh command until you login?
Nope, they work without X "direct" login.
On 05/05/2023 12:33, David wrote:
That sounds like what is documented here, with the solution at the end:
$ apt show dbus-user-session
I have tried quite similar steps, it seems the cause is not
dbus-user-session per se.
I have a laptop with Debian 11 bullseye and "minimalistic" KDE
(origi
On Sat, May 06, 2023 at 10:24:52AM +0700, Max Nikulin wrote:
> On 05/05/2023 20:04, zithro wrote:
> > journalctl after GUI LOGOFF
>
> I do not see obvious problems. What might be inspected more closely:
>
> > May 05 14:09:14 debzit systemd[711]: Stopping D-Bus User Message Bus...
>
On Fri 05 May 2023 at 13:59:37 (+0200), zithro wrote:
> On 05 May 2023 07:33, David wrote:
> > On Thu, 4 May 2023 at 19:07, zithro wrote:
> >
> > > this is a rather strange problem, I hope the title is explicit enough.
> >
> > Subject: Logging off an X s
machine, do
> > > > some stuff, then hit "log off" from the desktop menu.
> > > > Immediately, ALL the previous SSH connections started in step 1
> > > > get closed, hence all the shells and the GUI apps (firefox, etc) !
> ...
> > > A wild gu
.
May 05 14:09:14 debzit systemd[711]: Started D-Bus User Message Bus.
Why it started again from the same systemd user session if it is logout?
I would compare with logout messages when there are no ssh connections.
May 05 14:09:14 debzit sshd[14246]: Received disconnect from IP.IP.IP.IP
port
evious SSH connections started in step 1
get closed, hence all the shells and the GUI apps (firefox, etc) !
...
A wild guess is that it might be force close of systemd user session,
however it should not happen.
...
Isn't it this issue?
https://news.ycombinator.com/item?id=19023885
The discuss
er-session should keep daemon
running till at least one session is alive. It is surprise that logoff
from desktop session kills d-bus despite other connections.
Does it happen for newly created user with no customization?
Never tried !
I recommended to do it just for a case that you added so
On 05 May 2023 16:10, to...@tuxteam.de wrote:
I have now full logs of before/after GUI logon/logoff, I posted them in the
other post.
Will try to make sense of it with this lead ... after a needed break ^^
I saved that for a look during weekend, now I'm supposed to fix
an update of... forget it
On Fri, May 05, 2023 at 03:26:12PM +0200, zithro wrote:
> On 05 May 2023 14:11, to...@tuxteam.de wrote:
[...]
> > No DE, just a window manager (fvwm2).
>
> Isn't that fluxbox ? That's the GUI I used on Slackware.
> Simple, lean, efficient !
No, quite a bit older. Fluxbox 2000-ish, fvwm 199-smal
On 05 May 2023 14:11, to...@tuxteam.de wrote:
On Fri, May 05, 2023 at 01:58:55PM +0200, zithro wrote:
On 05 May 2023 06:32, to...@tuxteam.de wrote:
dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
no dbus (still, Debian buster, and X).
I'm on bullseye, I know how to sw
So, previous post was BEFORE logging in into GUI via VNC.
Now, I have outputs from after GUI LOGIN and after GUI LOGOFF.
I've removed the maximum of useless lines (audio, GUI apps, gvfs stuff,
etc), but tried to keep the most about systemd and dbus, as I'm clueless
about what you wanna read ...
On Fri, May 05, 2023 at 01:58:55PM +0200, zithro wrote:
> On 05 May 2023 06:32, to...@tuxteam.de wrote:
> > dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
> > no dbus (still, Debian buster, and X).
>
> I'm on bullseye, I know how to switch back to old init, but have no cl
On 05 May 2023 07:33, David wrote:
On Thu, 4 May 2023 at 19:07, zithro wrote:
this is a rather strange problem, I hope the title is explicit enough.
Subject: Logging off an X session closes all ssh -X connections
started previously from outside X
Yeah, I meant title==subject, I was hoping
On 05 May 2023 06:32, to...@tuxteam.de wrote:
dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
no dbus (still, Debian buster, and X).
I'm on bullseye, I know how to switch back to old init, but have no clue
about Dbus (kinda a Linux-GUI-with-systemd noob).
Which DE/DM y
On 05 May 2023 05:30, David Wright wrote:
Isn't it this issue?
https://news.ycombinator.com/item?id=19023885
Looks like it, yes !
I'm afraid I can't replicate the problem, though, as I don't have
a "log off" button or menu entry. That might suggest that the
problem is in something I don't r
On 05 May 2023 04:13, Max Nikulin wrote:
On 05/05/2023 02:07, zithro wrote:
2. using VNC or rdesktop, I then log on to X on the machine, do some
stuff, then hit "log off" from the desktop menu.
Immediately, ALL the previous SSH connections started in step 1 get
closed, hence all the
On Thu, 4 May 2023 at 19:07, zithro wrote:
> this is a rather strange problem, I hope the title is explicit enough.
Subject: Logging off an X session closes all ssh -X connections
started previously from outside X
> Here is what happens chronologically :
>
> 1. I start various SSH
On Fri, May 05, 2023 at 09:13:04AM +0700, Max Nikulin wrote:
> On 05/05/2023 02:07, zithro wrote:
> > 2. using VNC or rdesktop, I then log on to X on the machine, do some
> > stuff, then hit "log off" from the desktop menu.
[...]
> Perhaps it may be related to user D-Bus sessions, however I would
On Fri 05 May 2023 at 09:13:04 (+0700), Max Nikulin wrote:
> On 05/05/2023 02:07, zithro wrote:
> > 2. using VNC or rdesktop, I then log on to X on the machine, do
> > some stuff, then hit "log off" from the desktop menu.
> > Immediately, ALL the previous SSH connec
On 05/05/2023 02:07, zithro wrote:
2. using VNC or rdesktop, I then log on to X on the machine, do some
stuff, then hit "log off" from the desktop menu.
Immediately, ALL the previous SSH connections started in step 1 get
closed, hence all the shells and the GUI apps (firefox, etc) !
Hi all,
this is a rather strange problem, I hope the title is explicit enough.
Here is what happens chronologically :
1. I start various SSH connections to a host, some normal, some with X
forwarding, like that: "ssh user@host" and "ssh -X -n user@host GUI_APP"
(l
On Sun 05 Mar 2023 at 20:57:25 (+), Albretch Mueller wrote:
> On 3/5/23, David Wright wrote:
> >
> > I run installed systems, so wifi passwords are either in individual
> > /var/lib/iwd/.psk files (with iwd), or collectively in
> > /etc/wpa_supplicant/.conf (with wpasupplicant/systemd-networkd
David Wright writes:
> So what was wrong with using a .link file like:
>
> [Match]
> Type=wwan
> [Link]
> NamePolicy=keep kernel
>
> or
>
> [Match]
> Type=wwan
> [Link]
> Name=my4g
>
> Did this not work?
Nothing was wrong but I just added a few lines to my management script
to do
On 3/5/23, David Wright wrote:
> On Sun 05 Mar 2023 at 02:42:46 (+), Albretch Mueller wrote:
>> On 3/4/23, David Wright wrote:
>> > Also, now that the firmware is in place, if you repeat those steps,
>> > you're /likely/ to find that ath10k_pci is busy, because the link
>> > will be configure
On Sun 05 Mar 2023 at 21:22:10 (+0200), Anssi Saari wrote:
> Curt writes:
>
> > * UNPREDICTABILITY
> > it turns out even after all this [**an enumeration of complications and
> > corner
> > cases**] there are still reported cases of interfaces changing their name
> > on a
> > reboot.
>
> I hav
On Sun 05 Mar 2023 at 02:42:46 (+), Albretch Mueller wrote:
> On 3/4/23, David Wright wrote:
> > Also, now that the firmware is in place, if you repeat those steps,
> > you're /likely/ to find that ath10k_pci is busy, because the link
> > will be configured automatically in the first few secon
I thought “unpredictability” was the name of my daily drama show, but
apparently “I am not the only one”. Yes, I know javascript is the
primary vector they use to mess with whomever they choose, regardless
of if they wear a “tiny tin hat” or expensive shoes.
In my case, among many other things, t
On Sun, Mar 05, 2023 at 09:22:10PM +0200, Anssi Saari wrote:
> I have just this fun kind of unpredictability in my router's 4G
> module. Mostly, it comes up as wwan0 but sometimes it's wwx. So
> I put something in my 4G management script to rename such interface if
> there's no wwan0.
If you're ru
Curt writes:
> * UNPREDICTABILITY
> it turns out even after all this [**an enumeration of complications and corner
> cases**] there are still reported cases of interfaces changing their name on a
> reboot.
I have just this fun kind of unpredictability in my router's 4G
module. Mostly, it comes u
2023-03-04, Jeffrey Walton wrote:
> On Sat, Mar 4, 2023 at 12:12 PM David Wright wrote:
>>
>> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
>> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
>> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
>> > > > The
On 3/4/23, David Wright wrote:
> Also, now that the firmware is in place, if you repeat those steps,
> you're /likely/ to find that ath10k_pci is busy, because the link
> will be configured automatically in the first few seconds after
> booting up.
I would always go into exposed mode using a DL
On Sat, Mar 4, 2023 at 12:12 PM David Wright wrote:
>
> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > > The 'p' is a pci bus, the 's' is a slot numbe
On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
> > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > > does not move around once installe
On Sat 04 Mar 2023 at 00:03:16 (+), Albretch Mueller wrote:
> On 3/3/23, David Wright wrote:
> >
> > Try removing the atheros module with:
> >
> > # rmmod ath10k_pci
> >
> > (check its name in /proc/modules), and then reload it with
> >
> > # modprobe ath10k_pci
> >
> > and check dmesg aga
On 3/3/23, Dan Ritter wrote:
> ... the messages you
> are seeing are from the first 88.2 seconds after boot.
Most probably and luckily no one has reported such problems, but from
the corner from which I see reality it may as well be not "after
boot". I haven't exactly timed it (I will when I get
On Fri, Mar 03, 2023 at 06:09:40PM -0500, Greg Wooledge wrote:
> On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > does not move around once installed, the interface will always have
> > the same name like 'en
1 - 100 of 1022 matches
Mail list logo
