public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "András Csányi" <sayusi.ando@sayusi.hu>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] KDE and NetworkManager
Date: Tue, 16 Jul 2013 18:59:00 +0200	[thread overview]
Message-ID: <CALzub=ohMu_hG1gprsh+YXWNFfrBQA5XhLXAxZct-0cOFshA3w@mail.gmail.com> (raw)
In-Reply-To: <CADPrc80GiQgOhmq1hOj+6EO_1xHHwTr2K0b9RUJ5Laj3sUB0Rw@mail.gmail.com>

On 15 July 2013 21:08, Canek Peláez Valdés <caneko@gmail.com> wrote:
> On Mon, Jul 15, 2013 at 1:26 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>> On 15/07/2013 18:44, András Csányi wrote:
>>> Hi All,
>>>
>>> I would like to get some help regarding networkmanager and KDE.
>>>
>>> I have installed the networkmanager package on my machine and I also
>>> have networkmanagement kde application installed. My problem is that
>>> as a user I'm not able to abb network connection using network manager
>>> in kde. There is no way to run this application as root and I'm not
>>> able to login as root into KDE.
>
> Is your user included in the plugdev group, as the networkmanager
> ebuild recommends?

No. It was not part of that group. The install was a part of a bigger
set of packages and I haven't read the output. It is my bad. on the
other hand, the tutorial why does not mention about anything?

I added the the user to that group and the wicd working well. I
dropped networkmanager as far as it was possible. It is part of the
unity environment.

>>> At the moment I don't have any network connection on that machine. If
>>> I want it then I have to remove networkmanager package and let the
>>> rc-process to handle the networks.
>>>
>>> Is there a place where that is described how possible to solve this
>>> issue? Is there a tutorial about networkmanager where the
>>> configuration is described or something like this? What right is
>>> needed or something? I have googled a few hours but I haven't found
>>> anything.
>
> Again, try adding your user to the plugdev group.
>
>>> I appreciate your help!
>>
>>
>> unmerge nm and everything associated with it.
>> Comment out all lines in /etc/conf.d/net
>>
>> emerge wicd with the USE flags of your choice.
>>
>> All your problems will instantly go away, stay away, and wicd will do
>> the right thing always for networking. I promise.
>
> If the problem is that the user is not in the plugdev group, it will
> also happen with wicd, which makes this one of the worsts pieces of
> advice I have seen in this list. Which is a lot to say.

Yes, it happened the same with wicd as well. After I added the user to
the plugdev group everything is working fine.

>> networkmanager is a horribly broken piece of shit that per user reports
>> never seems to actually work for people.
>
> It works for me. In all kind of networks in several continents, with
> all kind of WEP, WPA, and WPA2 networks, connecting through my
> cellphone and obviously with ethernet too.
>
> Funny you said that Alan, when was the last time you heard about a
> problem with NM in the list? I count less than 20 mails *mentioning*
> NM in the list in 2013, and none of them are (IIRC) direct problems
> with NM.
>
>> You should not use software like that.
>
> You should do a little more research before saying something like that
> about a piece of software that just works most of the time.

I understand Alan feelings. The strange is that Ubuntu use wicd. I
don't know whether by default or not.


--
--  Csanyi Andras (Sayusi Ando)  -- http://sayusi.hu --
http://facebook.com/andras.csanyi
--  ""Trust in God and keep your gunpowder dry!" - Cromwell


  parent reply	other threads:[~2013-07-16 16:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 16:44 [gentoo-user] KDE and NetworkManager András Csányi
2013-07-15 18:26 ` Alan McKinnon
2013-07-15 19:08   ` Canek Peláez Valdés
2013-07-16 12:16     ` Todd Goodman
2013-07-16 12:31       ` Bruce Hill
2013-07-16 16:59     ` András Csányi [this message]
2013-07-16 17:09       ` Canek Peláez Valdés
2013-07-16 18:20         ` Bruce Hill
2013-07-16 18:47           ` Stroller
2013-07-16 19:21             ` Bruce Hill
2013-07-17  8:04           ` András Csányi
2013-07-17  8:12             ` Алексей Мишустин
2013-07-17  8:15               ` Алексей Мишустин
2013-07-17  9:35             ` Neil Bothwick
2013-07-17 11:39               ` András Csányi
2013-07-17 12:35                 ` Neil Bothwick
2013-07-17 12:42                   ` András Csányi
2013-07-17 12:49                 ` Bruce Hill
2013-07-19  7:35                   ` András Csányi
2013-07-19  8:17                     ` Neil Bothwick
2013-07-19  8:24                       ` András Csányi
2013-07-17 11:59             ` Bruce Hill
2013-07-17 12:18               ` András Csányi
2013-07-17 13:03                 ` Bruce Hill
2013-07-17 13:46                   ` Neil Bothwick
2013-07-19  7:16                   ` András Csányi
2013-07-16 17:43       ` Alan McKinnon
2013-07-16 18:44         ` András Csányi
2013-07-16 18:13       ` Bruce Hill
2013-07-15 19:03 ` Andrés Becerra Sandoval

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALzub=ohMu_hG1gprsh+YXWNFfrBQA5XhLXAxZct-0cOFshA3w@mail.gmail.com' \
    --to=sayusi.ando@sayusi.hu \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox