** Changed in: network-manager (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1568829
Title:
nm-applet icon not sh
Thanks Aron and Sebastien, I can confirm that version
1.2.2-0ubuntu0.16.04.1 from xenial-proposed fixes the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1568829
Title
The fixed version is in yakkety and there is a SRU waiting in the review
queue which includes that change
** Package changed: network-manager-applet (Ubuntu) => network-manager
(Ubuntu)
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: network-manage
** Changed in: network-manager-applet
Status: Unknown => Fix Released
** Changed in: network-manager-applet
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https:/
** Changed in: network-manager-applet
Importance: Undecided => Unknown
** Changed in: network-manager-applet
Status: New => Unknown
** Changed in: network-manager-applet
Remote watch: None => GNOME Bug Tracker #769324
** Changed in: network-manager-applet (Ubuntu)
Importance: Criti
The attachment "lp1568829.debdiff" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
The upstream patch was included in NM 1.2.2 so Yakkety is not affected,
only Xenial is.
The attached debdiff contains the upstream patch backported to Xenial.
The resulting package resolve the issue. If anything is missing for the
SRU process, please let me know.
** Patch added: "lp1568829.debdif
This was fixed upstream:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=3d505b3f87c9cb9bfdc9b9a1fc67f57330701d03
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchp
Thanks Alberto. https://bugzilla.gnome.org/show_bug.cgi?id=769324
** Description changed:
+ Steps to reproduce:
+
+ 1. (Re-)mount /proc with hidepid=1 (or =2)
+ 2. Restart nm-applet
+
+ nm-applet's icon does not reappear after the restart. This used to work
+ with version 1.0.
+
+
+ Original
** Summary changed:
- nm-applet icon not showing
+ nm-applet icon not showing when /proc is mounted with hidepid!=0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1568829
Please:
1. Report to (http://tinyurl.com/jc88oby).
2. Paste the new report link here.
3. Set this bug status back to "confirmed".
Thank you.
** Also affects: network-manager-applet
Importance: Undecided
Status: New
** Changed in: network-manager-applet (Ubuntu)
Status: Confirme
** Changed in: network-manager-applet (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager-applet (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubun
Indeed, the fact that this fails because of hidepid means it's something
more systemic than nm-applet -- the bug should be reported upstream, and
we need to find out all the processes impacted by this (probably quite
many things that depend on DBus, if I was to guess).
--
You received this bug no
"Could not determine request UID" gave me a hint perhaps failing to get
correct user from proc :-)
This may be a bit more global issue rather than something confined to
Network Manager considering gdm3 also fails to boot with this option on.
(Haven't really dig deep, but perhaps systemd, polkit, c
On 2016-04-22 05:08 PM, Hideki Saito wrote:
> I think I see what's going on. This seems to happen when hidepid is
> set to anything other than 0.
Hmm, I use hidepid=2,gid=27. Where gid 27 is the sudo group which I'm
part of. Nice catch.
It would be really nice not to have to resort to hidepid=0 t
I think I see what's going on.
This seems to happen when hidepid is set to anything other than 0. Remounted
/proc with hidepid=0 and this seems to be fixed. Though, it used to work with
other hidepid option, and is still an issue, but this may be an workaround for
those affected...
--
You rece
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager-applet (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https:
After verifying systemctl status network-manager that it is running, it
seems to be every interaction from the user seems to be failing.
sudo nmcli g
(process:3936): nmcli-CRITICAL **: Error: Could not create NMClient object:
Unable to authenticate request..
sudo nmcli c
(process:3943): nmcli-CR
So I stopped NM and started it back only to notice that my old nm-applet
was still running (still no icon). To be sure I was doing it the way you
needed I killed nm-applet, then started NM with --debug (that's what
I've attached).
When NM was running with --debug, it didn't spawn nm-applet but I s
The errors there look like the issue would be about NetworkManager not
running. Are you sure it is started at the time? You wouldn't then have
to restart nm-applet -- nm-applet does not show if it can't talk to NM.
Otherwise, I suppose there may be issues with policykit or some other
authenticati
20 matches
Mail list logo
