On Thu, Mar 3, 2016 at 4:58 PM, Andreas Fett <andreas.f...@secunet.com> wrote: > On 03/03/16 16:24, Aleksander Morgado wrote: >> I'm assuming ModemManager runs as root; is there any other program >> making use of the proxy here? mbimcli maybe? In order to avoid these >> kind of issues, the quickest solution is to always run everything as >> root, or under sudo for what it's worth. Maybe mbimcli with a normal >> user starts the proxy and MM with uid 0 tries to access it and uids >> don't match? >> >> Another option is to manually run the proxy before MM is started; e.g.: >> >> [terminal 1] $ sudo /usr/libexec/mbim-proxy --verbose >> [terminal 2] $ sudo /usr/sbin/ModemManager --debug > > I did that (see attached logs). Everything is run as root. The outcome > however is quite the same. > > I also attached a try with mbimcli after a fresh boot with neither > mbim proxy nor ModemManger running. > > To me the mbimcli output an the mbim-proxy log look quite similar. > > Any hints what else I could try?
Oh, please note that if you're running the proxy, either manually or launched automatically by MM, then all your "mbimcli" commands need to be run with the extra "-p" option. -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
