[Desktop-packages] [Bug 1011073] Re: NetworkManager submenus sometimes unpopulated
I think the icon set and everything else are Ubuntu default, I do not recall doing anything to the look and feel besides changing the background image (and having the left-hand side bar being displayed at all times). System Settings - Appearance - Theme says Ambiance (default). The system is Ubuntu 12.04, x86_64, all packages up-to-date. -- 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/1011073 Title: NetworkManager submenus sometimes unpopulated Status in “network-manager” package in Ubuntu: Triaged Bug description: Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1011073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1011073] Re: NetworkManager submenus sometimes unpopulated
In reply to Mathieu: It usually takes days, not hours, before I notice the problem, but I think I have never gone more than three days without. I have run an instance of valgrind --leak-check=full --trace- children=yes --log-file=nm-applet-%p.log nm-applet in a console and hit Ctrl-C when I noticed the problem. I'm attaching a bzip2 compressed log file. The console output was --snip ** Message: applet now removed from the notification area (nm-applet:10742): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `dest_y = 0 dest_y + dest_height = dest-height' failed ** Message: No keyring secrets found for WLAN-001A4F3AD299/802-11-wireless-security; asking user. ^C** Message: PID 0 (we are 10742) sent signal 2, shutting down... --snap (Note: The No keyring secrets message is related to a different problem.) ** Attachment added: Log generated by valgrind --leak-check=full --trace-children=yes --log-file=nm-applet-%p.log nm-applet https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1011073/+attachment/3251319/+files/nm-applet-10742.log.bz2 -- 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/1011073 Title: NetworkManager submenus sometimes unpopulated Status in “network-manager” package in Ubuntu: Incomplete Bug description: Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1011073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1011073] Re: NetworkManager submenus unpopulated
I'm affected by this too. It seems to happen intermittently without any obvious connection to anything else. I most often notice it more or less directly following a resume from suspend, though that may be a coincidence since that's also the time when I most often want to manually connect to my VPN, having just opened my laptop at a place away from home. Another symptom when the bug occurs: The nm-indicator does not react to clicks on any of the items. While it may list some Wifi networks as well as 3G connections and the Enable … checkboxes, clicking any of them simply does nothing. Wifi networks can't be changed, 3G connections can't be brought up, networking can't be disabled. It's as if the indicator has lost partial connectivity to the network-manager proper. Other network-manager interfaces continue to work, both nmcli/nm-tool and System Settings → Network list all available connections and can bring them up. Looking through the network-manager bugs on launchpad at least #1012154 and #1000948 seem to be duplicates of this. (I'm commenting here since so far this is the most active one.) -- 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/1011073 Title: NetworkManager submenus unpopulated Status in “network-manager” package in Ubuntu: Confirmed Bug description: Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1011073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 884856] Re: gnome-keyring integration breaks some GPG functions
Ok, it seems I misunderstood the gnome-keyring-daemon startup procedure.
Apparently --daemonize --login spawns kind of an empty shell for the
functionality (accepting the password through PAM) but does not actually
initialize any functionality. For that additional calls the gnome-
keyring-daemon with the options --start --components=… (listing the
desired component or components) are necessary. As such the PAM module
call is actually correct and the fault for gnome-keyring-daemon
uncontrollably taking over GPG functions lies elsewhere. (It's just
rather confusing because the later calls to --start --components don't
leave any traces and looking at the running process list will only show
one gnome-keyring-daemon process with --daemonize --login.)
In theory, and apparently in some practical cases as evidenced by
comment 4 and some other hints on the web, the modules should be started
by the session and selectable in gnome-session-properties. However, that
doesn't seem to be the case, for Oneiric at least: I tried creating a
new user account on my system, and tried a friend's installation (to
exclude the possibility of something being wrong with my installation):
There is no entry for any gnome-keyring-daemon module in the startup
programs list.
Instead, there are multiple /etc/xdg/autostart/gnome-keyring-….desktop files,
one each for gpg, secrets, pkcs11 and ssh with no obvious UI to disable any of
them.
WORKAROUND: Removing the /etc/xdg/autostart/gnome-keyring-gpg.desktop file
releases (after logging out and in again) gnome-keyring-daemon's grip over the
GPG agent functionality and lets gpg and gpgsm work normally again.
-- Steps to reproduce --
1. On a normal Ubuntu Oneiric installation log in normally.
2. Open a Terminal
3. echo $GPG_AGENT_INFO
-- Actual results --
/tmp/keyring-some random string/gpg:0:1
-- Expected results (and actual results after applying workaround) --
/tmp/gpg-random string/S.gpg-agent:random number:1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/884856
Title:
gnome-keyring integration breaks some GPG functions
Status in “gnome-keyring” package in Ubuntu:
Confirmed
Bug description:
In recent Ubuntu releases (not sure how far back, but at least
Oneiric) gnome-keyring offers gpg-agent integration and is enabled by
default. The gpg-agent protocol implementation of gnome-keyring is
very incomplete and hence breaks at least the smartcard functions of
gpg and most functions of gpgsm.
Steps to reproduce (smartcard):
1. Acquire a smartcard reader, an OpenPGP smartcard and install pcsc-lite
2. Start a normal new Ubuntu desktop session
3. strace gpg --card-status
Actual results:
...
socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path=/tmp/keyring-p6oNWL/gpg}, 25) = 0
...
write(3, SCD SERIALNO openpgp, 20)= 20
write(3, \n, 1) = 1
read(3, ERR 103 unknown command\n, 1002) = 24
...
The printout on stdout is
selecting openpgp failed: unknown command
OpenPGP card not available: general error
Expected results: The agent should know the SCD command and act
accordingly.
Steps to reproduce(gpgsm):
1. Migrate from an old installation that includes X.509 certificates and
private keys in gpgsm.
2. strace gpgsm -K
Actual results:
...
socket(PF_FILE, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_FILE, path=/tmp/keyring-p6oNWL/gpg}, 25) = 0
...
write(4, HAVEKEY 62B64B58FF1BD7E0B48FE51A..., 48) = 48
write(4, \n, 1) = 1
read(4, ERR 103 unknown command\n, 1002) = 24
...
Expected results: The agent should know the HAVEKEY command and act
accordingly.
Due to the way the gnome-keyring is activated in recent releases no easy
workaround is possible. Removing the GPG_AGENT_INFO environment variable makes
the individual examples work (they will just start their own agent if
necessary), but that's not possible (and certainly not configurable) on a
system level. gnome-keyring-daemon allows in principle to deactivate the faulty
gpg module (there is a command line option --components that accepts a list of
any combination of pkcs11,secrets,ssh,gpg).
But currently the gnome-keyring-daemon is started through the
pam_gnome_keyring.so PAM module which uses a hard-coded command line
(--daemonize --login).
Steps to resolve this problem: At least a) disable the gpg gnome-keyring
module by default in the PAM module, and/or b) make the command line options
that the module uses user configurable. Or c) extend gnome-keyring with all the
missing functionality (and play a constant game of catch-up), or d) leave
gpg-agent operations to the gpg-agent and try to solve whatever problem the
gnome-keyring gpg-agent emulation was meant to solve in another manner.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
[Desktop-packages] [Bug 884856] [NEW] gnome-keyring integration breaks some GPG functions
Public bug reported:
In recent Ubuntu releases (not sure how far back, but at least Oneiric)
gnome-keyring offers gpg-agent integration and is enabled by default.
The gpg-agent protocol implementation of gnome-keyring is very
incomplete and hence breaks at least the smartcard functions of gpg and
most functions of gpgsm.
Steps to reproduce (smartcard):
1. Acquire a smartcard reader, an OpenPGP smartcard and install pcsc-lite
2. Start a normal new Ubuntu desktop session
3. strace gpg --card-status
Actual results:
...
socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path=/tmp/keyring-p6oNWL/gpg}, 25) = 0
...
write(3, SCD SERIALNO openpgp, 20)= 20
write(3, \n, 1) = 1
read(3, ERR 103 unknown command\n, 1002) = 24
...
The printout on stdout is
selecting openpgp failed: unknown command
OpenPGP card not available: general error
Expected results: The agent should know the SCD command and act
accordingly.
Steps to reproduce(gpgsm):
1. Migrate from an old installation that includes X.509 certificates and
private keys in gpgsm.
2. strace gpgsm -K
Actual results:
...
socket(PF_FILE, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_FILE, path=/tmp/keyring-p6oNWL/gpg}, 25) = 0
...
write(4, HAVEKEY 62B64B58FF1BD7E0B48FE51A..., 48) = 48
write(4, \n, 1) = 1
read(4, ERR 103 unknown command\n, 1002) = 24
...
Expected results: The agent should know the HAVEKEY command and act
accordingly.
Due to the way the gnome-keyring is activated in recent releases no easy
workaround is possible. Removing the GPG_AGENT_INFO environment variable makes
the individual examples work (they will just start their own agent if
necessary), but that's not possible (and certainly not configurable) on a
system level. gnome-keyring-daemon allows in principle to deactivate the faulty
gpg module (there is a command line option --components that accepts a list of
any combination of pkcs11,secrets,ssh,gpg).
But currently the gnome-keyring-daemon is started through the
pam_gnome_keyring.so PAM module which uses a hard-coded command line (
--daemonize --login).
Steps to resolve this problem: At least a) disable the gpg gnome-keyring module
by default in the PAM module, and/or b) make the command line options that the
module uses user configurable. Or c) extend gnome-keyring with all the missing
functionality (and play a constant game of catch-up), or d) leave gpg-agent
operations to the gpg-agent and try to solve whatever problem the gnome-keyring
gpg-agent emulation was meant to solve in another manner.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-keyring 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Mon Oct 31 05:41:24 2011
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=de_DE.utf8
SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (17 days ago)
** Affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug oneiric running-unity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/884856
Title:
gnome-keyring integration breaks some GPG functions
Status in “gnome-keyring” package in Ubuntu:
New
Bug description:
In recent Ubuntu releases (not sure how far back, but at least
Oneiric) gnome-keyring offers gpg-agent integration and is enabled by
default. The gpg-agent protocol implementation of gnome-keyring is
very incomplete and hence breaks at least the smartcard functions of
gpg and most functions of gpgsm.
Steps to reproduce (smartcard):
1. Acquire a smartcard reader, an OpenPGP smartcard and install pcsc-lite
2. Start a normal new Ubuntu desktop session
3. strace gpg --card-status
Actual results:
...
socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path=/tmp/keyring-p6oNWL/gpg}, 25) = 0
...
write(3, SCD SERIALNO openpgp, 20)= 20
write(3, \n, 1) = 1
read(3, ERR 103 unknown command\n, 1002) = 24
...
The printout on stdout is
selecting openpgp failed: unknown command
OpenPGP card not available: general error
Expected results: The agent should know the SCD command and act
accordingly.
Steps to reproduce(gpgsm):
1. Migrate from an old installation that includes X.509 certificates and
private keys in gpgsm.
2. strace gpgsm -K
Actual results:
...
socket(PF_FILE, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_FILE, path=/tmp/keyring-p6oNWL/gpg}, 25) = 0
...
write(4, HAVEKEY 62B64B58FF1BD7E0B48FE51A..., 48) = 48
write(4, \n, 1) = 1
read(4, ERR 103 unknown command\n, 1002) = 24
[Desktop-packages] [Bug 884856] Re: gnome-keyring integration breaks some GPG functions
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/884856
Title:
gnome-keyring integration breaks some GPG functions
Status in “gnome-keyring” package in Ubuntu:
New
Bug description:
In recent Ubuntu releases (not sure how far back, but at least
Oneiric) gnome-keyring offers gpg-agent integration and is enabled by
default. The gpg-agent protocol implementation of gnome-keyring is
very incomplete and hence breaks at least the smartcard functions of
gpg and most functions of gpgsm.
Steps to reproduce (smartcard):
1. Acquire a smartcard reader, an OpenPGP smartcard and install pcsc-lite
2. Start a normal new Ubuntu desktop session
3. strace gpg --card-status
Actual results:
...
socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path=/tmp/keyring-p6oNWL/gpg}, 25) = 0
...
write(3, SCD SERIALNO openpgp, 20)= 20
write(3, \n, 1) = 1
read(3, ERR 103 unknown command\n, 1002) = 24
...
The printout on stdout is
selecting openpgp failed: unknown command
OpenPGP card not available: general error
Expected results: The agent should know the SCD command and act
accordingly.
Steps to reproduce(gpgsm):
1. Migrate from an old installation that includes X.509 certificates and
private keys in gpgsm.
2. strace gpgsm -K
Actual results:
...
socket(PF_FILE, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_FILE, path=/tmp/keyring-p6oNWL/gpg}, 25) = 0
...
write(4, HAVEKEY 62B64B58FF1BD7E0B48FE51A..., 48) = 48
write(4, \n, 1) = 1
read(4, ERR 103 unknown command\n, 1002) = 24
...
Expected results: The agent should know the HAVEKEY command and act
accordingly.
Due to the way the gnome-keyring is activated in recent releases no easy
workaround is possible. Removing the GPG_AGENT_INFO environment variable makes
the individual examples work (they will just start their own agent if
necessary), but that's not possible (and certainly not configurable) on a
system level. gnome-keyring-daemon allows in principle to deactivate the faulty
gpg module (there is a command line option --components that accepts a list of
any combination of pkcs11,secrets,ssh,gpg).
But currently the gnome-keyring-daemon is started through the
pam_gnome_keyring.so PAM module which uses a hard-coded command line
(--daemonize --login).
Steps to resolve this problem: At least a) disable the gpg gnome-keyring
module by default in the PAM module, and/or b) make the command line options
that the module uses user configurable. Or c) extend gnome-keyring with all the
missing functionality (and play a constant game of catch-up), or d) leave
gpg-agent operations to the gpg-agent and try to solve whatever problem the
gnome-keyring gpg-agent emulation was meant to solve in another manner.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-keyring 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Mon Oct 31 05:41:24 2011
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=de_DE.utf8
SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (17 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/884856/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
