Hi! Did anyone else observe the behavior from subject?
I tried to move the NetworkManager starting from systemd to cron
(because it takes to much to start and it is in critical-chain)
and while it worked, the xorg no longer started up, and the journal show
xorg core dumping...
Anyone have any i
On Wed, Dec 05, 2012 at 12:13:37AM +1030, Tim wrote:
> > Actually, I think it's not just okay to talk about upcoming changes
> > here, but a really good idea. I apologize for just giving the Gnome
> > version and not mentioning the corresponding Fedora version, but in
> > any case I was not talking
On Tue, Dec 04, 2012 at 09:02:07AM -0430, Patrick O'Callaghan wrote:
> The Fedora Test List is for discussing all testing of Fedora-related
> software, not just unreleased distros. The User list (i.e. this one) is
Sure. But I wasn't talking about testing at all.
--
Matthew Miller ☁☁☁ Fedora Cl
Allegedly, on or about 04 December 2012, jarmo sent:
> I think, networkmanager is separate program. Can be used in KDE also.
> Both has Applet which have their behaviours with left/right mouse
> clicks.
Yes, NetworkManager is the underlying system that takes care of
automatically (*) managing the
Allegedly, on or about 03 December 2012, Matthew Miller sent:
> Actually, I think it's not just okay to talk about upcoming changes
> here, but a really good idea. I apologize for just giving the Gnome
> version and not mentioning the corresponding Fedora version, but in
> any case I was not talkin
On Mon, 2012-12-03 at 22:49 -0500, Matthew Miller wrote:
> On Tue, Dec 04, 2012 at 01:50:18PM +1030, Tim wrote:
> > >> Well, what version are you using? I'm on Fedora 17, now. The current
> > >> release of Fedora. My Gnome desktop has different results for left or
> > >> right clicking on the Ne
Mon, 3 Dec 2012 18:55:00 -0500
Matthew Miller kirjoitti:
> On Mon, Dec 03, 2012 at 09:07:09PM +1030, Tim wrote:
> > > Yeaah, so, in Gnome 3.6, you get the same thing on left or right
> > > click.
> > Well, what version are you using? I'm on Fedora 17, now. The
> > current release of Fedora. My
On Tue, Dec 04, 2012 at 01:50:18PM +1030, Tim wrote:
> >> Well, what version are you using? I'm on Fedora 17, now. The current
> >> release of Fedora. My Gnome desktop has different results for left or
> >> right clicking on the NetworkManager icon.
> > Yep -- that's Gnome 3.4. In the upcoming F
Tim:
>> Well, what version are you using? I'm on Fedora 17, now. The current
>> release of Fedora. My Gnome desktop has different results for left or
>> right clicking on the NetworkManager icon.
Matthew Miller:
> Yep -- that's Gnome 3.4. In the upcoming F18 release, Gnome 3.6 changes the
> beh
On Mon, Dec 03, 2012 at 09:07:09PM +1030, Tim wrote:
> > Yeaah, so, in Gnome 3.6, you get the same thing on left or right
> > click.
> Well, what version are you using? I'm on Fedora 17, now. The current
> release of Fedora. My Gnome desktop has different results for left or
> right clicking on
Allegedly, on or about 30 November 2012, Matthew Miller sent:
> Yeaah, so, in Gnome 3.6, you get the same thing on left or right
> click.
Well, what version are you using? I'm on Fedora 17, now. The current
release of Fedora. My Gnome desktop has different results for left or
right clicking on
On Fri, Nov 30, 2012 at 06:20:26PM +1030, Tim wrote:
> Allegedly, on or about 29 November 2012, Alex sent:
> > How do I even access the NM network management GUI from within GNOME?
> Why do people find this so hard? It was bloody obvious from the first
> time I ever saw the Gnome desktop after log
Allegedly, on or about 29 November 2012, Alex sent:
> How do I even access the NM network management GUI from within GNOME?
Why do people find this so hard? It was bloody obvious from the first
time I ever saw the Gnome desktop after log-in. And barely different
from other releases of Gnome, as
On Thu, 29 Nov 2012 17:01:47 -0500 Alex wrote:
> > Make sure that NM is masked and network.service is correctly
> > configured and operational. After that, report separately any
> > issues that you might have with other apps.
>
> Very helpful, thanks so much. Do you know of a doc that explains th
On Thu, 29 Nov 2012 17:03:11 -0500 Alex wrote:
> The whole "mask" thing looks like a hack to me in the first place, but
> I guess I can understand, considering the 'network' method has
> probably been deprecated for at least a few versions now.
There is a genuine explanation for masking, based on
On Thu, 29 Nov 2012 17:03:11 -0500
Alex wrote:
> The whole "mask" thing looks like a hack to me in the first place
The hack is that it is named "mask". It should be named "disable"
because "disable" essentially does nothing useful at all. (It
really means "don't start at boot, but anytime anyone
Hi,
>> systemctl stop NetworkManager.service
>> systemctl mask NetworkManager.service
>
> Ooops, sorry, make that
>
>systemctl mask NetworkManager.service
>systemctl stop NetworkManager.service
>
> First mask it, then stop it. Otherwise, some app my restart NM again
> before you manage
Hi,
>> How do I properly disable NetworkManager so applications don't think
>> my wired network is offline?
>
> First, do a
>
> systemctl stop NetworkManager.service
> systemctl mask NetworkManager.service
>
> Get well informed about the mask command in "man systemctl".
Awesome, that fixed it
On Thu, 29 Nov 2012 22:27:29 +0100 Marko Vojinovic
wrote:
> First, do a
>
> systemctl stop NetworkManager.service
> systemctl mask NetworkManager.service
Ooops, sorry, make that
systemctl mask NetworkManager.service
systemctl stop NetworkManager.service
First mask it, then stop it. O
On Thu, 29 Nov 2012 15:07:02 -0500 Alex wrote:
> How do I properly disable NetworkManager so applications don't think
> my wired network is offline?
First, do a
systemctl stop NetworkManager.service
systemctl mask NetworkManager.service
Get well informed about the mask command in "man syste
Hi,
> How do I properly disable NetworkManager so applications don't think
> my wired network is offline? I'm using a network bridge for kvm, and
> it's always been easier to use the old style networking. I've run the
> following commands to disable it and enable regular network services:
>
> sy
21 matches
Mail list logo