On 12/20/23 04:38, Samuel Sieb wrote:
On 12/19/23 21:31, Robert McBroom via users wrote:
On 12/19/23 01:53, Samuel Sieb wrote:
This is the problem you need to resolve.
I don't know why. You'll need to find out why the dbus broker can't
run. I would have expected more details in the log.
-
On Dec 20, 2023, at 00:31, Robert McBroom via users
wrote:
>
> Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR
> launcher_run_child @ ../src/launch/launcher.c +347: Permission denied
> Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR service_add
> @ ../src/lau
On Wed Dec20'23 02:11:00AM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Wed, 20 Dec 2023 02:11:00 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: Network problems with f39
>
> On 12/20/23 01:47, Ranjan Maitra
On 12/20/23 01:47, Ranjan Maitra via users wrote:
This may be thoroughly unrelated, but my wife has had this problem on a Dell
for years (largely regularly), and me only intermittently over the past few
months (F38 or F39). I think it may be dependent on the service provider
because the same s
: Samuel Sieb
> Date: Wed, 20 Dec 2023 01:38:01 -0800
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: Network problems with f39
>
> On 12/19/23 21:31, Robert McBroom via users wrote:
> >
> > On 12/19/23 01:53, Samuel Sie
On 12/19/23 21:31, Robert McBroom via users wrote:
On 12/19/23 01:53, Samuel Sieb wrote:
This is the problem you need to resolve.
I don't know why. You'll need to find out why the dbus broker can't
run. I would have expected more details in the log.
--
I'm not sure what to look for in the
On 12/19/23 01:53, Samuel Sieb wrote:
On 12/18/23 22:12, Robert McBroom via users wrote:
Upgraded legacy bios laptop from f37 to f39. Use command line boot.
User login cycles and returns to login prompt.
Can boot system on command line as root. The network does not connect
with a dependency
On 12/18/23 22:12, Robert McBroom via users wrote:
Upgraded legacy bios laptop from f37 to f39. Use command line boot.
User login cycles and returns to login prompt.
Can boot system on command line as root. The network does not connect
with a dependency failure on NetworkManager. Not cleared
users
Subject: Re: Network problems
Olav Vitters wrote:
> On Fri, May 11, 2012 at 12:44:16PM +0100, Timothy Murphy wrote:
>> I couldn't find a clear account of the effect of the line
>> anywhere in the shorewall documentation.
>
> Add it, apply the changes and run the follo
Olav Vitters wrote:
> On Fri, May 11, 2012 at 12:44:16PM +0100, Timothy Murphy wrote:
>> I couldn't find a clear account of the effect of the line
>> anywhere in the shorewall documentation.
>
> Add it, apply the changes and run the following as root:
> iptables -t nat -L -n
>
> That'll tell you
On Fri, May 11, 2012 at 12:44:16PM +0100, Timothy Murphy wrote:
> I couldn't find a clear account of the effect of the line
> anywhere in the shorewall documentation.
Add it, apply the changes and run the following as root:
iptables -t nat -L -n
That'll tell you what it does.
--
Regards,
Olav
-
Reindl Harald wrote:
>> I've found from this that I don't really understand how networking works,
>> and I'm writing now to ask for some help with this.
> google for POSTROUTING / MASQUERADE (iptables)
Thanks for your response;
but I think I do understand what IP masquerading is.
Just to repeat
try with
traceroute destination.host
traceroute6 destination.host
suomi
On 05/09/2012 03:52 PM, Timothy Murphy wrote:
I've been trying to move from one home network server to another
(because of hard disk problems with the first).
I've found from this that I don't really understand how networ
Am 09.05.2012 15:52, schrieb Timothy Murphy:
> I've been trying to move from one home network server to another
> (because of hard disk problems with the first).
>
> I've found from this that I don't really understand how networking works,
> and I'm writing now to ask for some help with this.
>
14 matches
Mail list logo
