[Desktop-packages] [Bug 1409032] Re: gvfsd-smb: very high CPU utilisation

2016-08-15 Thread cogset
Does the fact that I see this behavior in *Trusty* (see comment
[url=https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/comments/33]33[/url]
mean that I'm experiencing this  same bug, or is it another issue
altogether for which I should open a separate bug?

Please notice that (as stated in comment 33) I've actually purged all
samba packages from this system, the only things left behind are some
samba libraries, and yet the  gvfsd-dnssd process would randomly start
for no reason that I can thin kof and load the CPU to the max.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1409032

Title:
  gvfsd-smb: very high CPU utilisation

Status in samba:
  Unknown
Status in gvfs package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in gvfs package in Fedora:
  Unknown

Bug description:
  Example:

  I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb
  (browsing within Gnome to find the share), gvfsd-smb uses up to 50%
  CPU which slows down the entire system when accessing the network
  share. Mounting using sudo ($ sudo mount -t smbfs -o
  guest,nounix,noperm //server/share /media/share) so that cifs is used
  uses around 8% CPU. The difference is dramatic!

  If I didn't have sudo access my machine would grind to a halt when
  trying to use the remote share.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Fri Jan  9 14:32:20 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1409032/+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 1409032] Re: gvfsd-smb: very high CPU utilisation

2016-06-20 Thread cogset
I think I may have the same issue in Trusty, possibly even worse: the
gvfsd-smb process would randomly start and totally max out the CPU for
no apparent reason - the thing is, not only I don't use samba at all, I
have actually *purged* all samba packages from this system.

I really can't see how this process, which should be spawned by samba,
should even start at all (let alone load the CPU to its max) when samba
isn't even installed any more in my system.

This being an old laptop which easily overheats, after getting nowhere
trying to figure out why gvfsd-smb does this, I've resolved to remove
the executable bit from  gvfsd-smb and  gvfsd-dnssd (which also starts
for no apparent reason) and finally got rid of this big issue.

But nonetheless I believe that such an annoying (and potentially
harmful) long-standing bug should be properly investigated and fixed
once and for all.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1409032

Title:
  gvfsd-smb: very high CPU utilisation

Status in gvfs package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in samba package in Fedora:
  Unknown

Bug description:
  Example:

  I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb
  (browsing within Gnome to find the share), gvfsd-smb uses up to 50%
  CPU which slows down the entire system when accessing the network
  share. Mounting using sudo ($ sudo mount -t smbfs -o
  guest,nounix,noperm //server/share /media/share) so that cifs is used
  uses around 8% CPU. The difference is dramatic!

  If I didn't have sudo access my machine would grind to a halt when
  trying to use the remote share.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Fri Jan  9 14:32:20 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+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 1538104] [NEW] traps: mate-notification message in logs

2016-01-26 Thread cogset
Public bug reported:

I'm always seeing this message after boot in Ubuntu-Mate 15.04 in
syslog, kern.log and dmesg and also with journactl --boot:

traps: mate-notificati[1409] trap int3 ip:7f67f920ed00 sp:7ffd6097e640
error:0

what does this mean?


 
Ubuntu release and package version:

Ubuntu 15.04

mate-desktop 1.8.2+dfsg1-2
mate-desktop-common  1.8.2+dfsg1-2
mate-desktop-environment-core1.8.0+9

Kernel: 3.19.0-47-generic x86_64 (64 bit gcc: 4.9.2)
Desktop: MATE 1.8.2 (Gtk 3.14.13) dm: lightdm Distro: Ubuntu 15.04 vivid

** Affects: seahorse (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1538104

Title:
  traps: mate-notification message in logs

Status in seahorse package in Ubuntu:
  New

Bug description:
  I'm always seeing this message after boot in Ubuntu-Mate 15.04 in
  syslog, kern.log and dmesg and also with journactl --boot:

  traps: mate-notificati[1409] trap int3 ip:7f67f920ed00 sp:7ffd6097e640
  error:0

  what does this mean?

  

   
  Ubuntu release and package version:

  Ubuntu 15.04

  mate-desktop   1.8.2+dfsg1-2
  mate-desktop-common1.8.2+dfsg1-2
  mate-desktop-environment-core  1.8.0+9

  Kernel: 3.19.0-47-generic x86_64 (64 bit gcc: 4.9.2)
  Desktop: MATE 1.8.2 (Gtk 3.14.13) dm: lightdm Distro: Ubuntu 15.04 vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1538104/+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 1538086] [NEW] Seahorse has no option to export/import passwords

2016-01-26 Thread cogset
Public bug reported:

Seahorse  3.15.90-0ubuntu1  in Ubuntu15.04 still has no option for
exporting and importing stored passwords ( see: bug
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/550101 and
comment
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/550101/comments/19
) : since it can  manage importing and exporting of gpg keys, and it
also has this additional ability to store encrypted passwords, it would
make sense to also manage  these stored passwords as well.

That would greatly add to its usability as a password manager as well,
in addition to  being a gpg key manager.

** Affects: seahorse (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1538086

Title:
  Seahorse has no option to export/import passwords

Status in seahorse package in Ubuntu:
  New

Bug description:
  Seahorse  3.15.90-0ubuntu1  in Ubuntu15.04 still has no option for
  exporting and importing stored passwords ( see: bug
  https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/550101 and
  comment
  https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/550101/comments/19
  ) : since it can  manage importing and exporting of gpg keys, and it
  also has this additional ability to store encrypted passwords, it
  would make sense to also manage  these stored passwords as well.

  That would greatly add to its usability as a password manager as well,
  in addition to  being a gpg key manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1538086/+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 550101] Re: Export of keys and keyrings is not available

2016-01-22 Thread cogset
This issue is still present in Ubuntu 15.10: Seahorse  to date still has
no option to export/import stored passwords.

This kinda hinders its abilities as a password manager: even if it's
probably meant to be mainly a gpg key management interface, it also has
this ability to store passwords, so not being able to export/import
those as well detracts from its usability forcing users to seek
alternative solutions.

Given that there has been no activity in this bug since 2014 (see
comment above), should eventually a new bug be opened tagging current
and future releases?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/550101

Title:
  Export of keys and keyrings is not available

Status in seahorse:
  New
Status in seahorse package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: seahorse

  When I try to export key or keyring, the menu is grayed out. Thus I
  cannot make backups of my keys.

  That would be only a inconvenience, if I could just backup keys by
  copying seahorse configuration directory. I guess I can do that, if
  only I knew, where it actually is. It is certainly NOT .gnupg, because
  when I delete it (in recovery mode, as root), the keys are still there
  and .gnupg folder is as good as new.

  It would be very nice to do something about this. When I made a
  keyring and put all my brand new passwords there, the seahorse somehow
  managed to lose all keys in it.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: seahorse 2.29.91-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-17-generic i686
  Architecture: i386
  Date: Sun Mar 28 11:06:43 2010
  ExecutablePath: /usr/bin/seahorse
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091203)
  ProcEnviron:
   LANG=lv_LV.utf8
   SHELL=/bin/bash
  SourcePackage: seahorse

To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/550101/+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 1470862] Re: When using fglrx module, the virtual consoles are blank and useless

2015-12-13 Thread cogset
That was (probably) more or less a given, this is clearly  an ATI/fglrx
issue.

What I don't understand is why is considered somehow acceptable to
suffer such an issue, or why the recommended "fix" (?) would be to get
rid of the fglrx driver altogether.

ATI support for Linux may be considerably worse than Nvidia (as
recognized by many people in the know), but if the package exists in the
Ubuntu repository it should work without rendering the virtual consoles
useless, and this issue shouldn't slip all the way from 14.04 to 15.10.

That

>removing fglrx drivers is some sort of workaround, but presumably
people that did install fglrx in the first place >want fglrx for some
reason

is the appropriate line of reasoning: the official package exists and
should be installable without breaking anything major such as the
virtual consoles.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1470862

Title:
  When using fglrx module, the virtual consoles are blank and useless

Status in fglrx-installer-updates package in Ubuntu:
  Confirmed

Bug description:
  When the PC boots it shows the sddm login, but if I switch to the
  first virtual console using Ctrl+Alt+F1, the console is blank. The
  other consoles are in the same state. Only the virtual console with
  the sddm login, is running fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates 2:15.200-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul  2 15:31:28 2015
  SourcePackage: fglrx-installer-updates
  UpgradeStatus: Upgraded to vivid on 2015-03-12 (112 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+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 1470862] Re: When using fglrx module, the virtual consoles are blank and useless

2015-10-30 Thread cogset
>The "who" command verified to me all my tty consoles are fully
functional, only their displays are blacked out.

We know that already, the issue is that they are not really usable if
blacked out: we have a monitor/display for a reason.


We also know that getting rid of the fglrx driver solves the issue right away, 
unfortunately the fglrx driver also exists for a reason, which would be that 
the open source driver can't do the same things: at least in my experience, I'm 
stuck with very basic graphics, I can't set the monitor brightness, I can't use 
hardware acceleration or use Compiz effects.
These are real drawbacks, if I have to do without this stuff, I may as well do 
without the ATI video card and use the integrated graphics on the motherboard.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1470862

Title:
  When using fglrx module, the virtual consoles are blank and useless

Status in fglrx-installer-updates package in Ubuntu:
  Confirmed

Bug description:
  When the PC boots it shows the sddm login, but if I switch to the
  first virtual console using Ctrl+Alt+F1, the console is blank. The
  other consoles are in the same state. Only the virtual console with
  the sddm login, is running fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates 2:15.200-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul  2 15:31:28 2015
  SourcePackage: fglrx-installer-updates
  UpgradeStatus: Upgraded to vivid on 2015-03-12 (112 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+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 1470862] Re: When using fglrx module, the virtual consoles are blank and useless

2015-10-05 Thread cogset
This is also happening in Ubuntu Trusty 14.04.3 LTS : right after
installing fglrx-updates and fglrx-amdcccle-updates the virtual consoles
become unusable, i.e. totally blank.

Again, as bad as the AMD support for Linux may be, as a matter of fact
the proprietary driver is (unfortunately) still better then its open
source counterpart: display quality is noticeably better, screen
adjustments are way easier and more fine tunable than messing around
with xrandr, composite window  managers don't work properly or don't
work at all  with the open source driver.

Much as I would like to do without the proprietary AMD driver, I need to
use it to have my hardware working as I want, so please fix this issue.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1470862

Title:
  When using fglrx module, the virtual consoles are blank and useless

Status in fglrx-installer-updates package in Ubuntu:
  Confirmed

Bug description:
  When the PC boots it shows the sddm login, but if I switch to the
  first virtual console using Ctrl+Alt+F1, the console is blank. The
  other consoles are in the same state. Only the virtual console with
  the sddm login, is running fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates 2:15.200-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul  2 15:31:28 2015
  SourcePackage: fglrx-installer-updates
  UpgradeStatus: Upgraded to vivid on 2015-03-12 (112 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+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 1470862] Re: When using fglrx module, the virtual consoles are blank and useless

2015-07-20 Thread cogset
In reply to comment https://bugs.launchpad.net/ubuntu/+source/fglrx-
installer-updates/+bug/1470862/comments/5

>I recommend you to get rid of fglrx. Open source drivers for AMD work
today like a charm.

I beg to differ: much as I would really like to get rid of any non-free
components, without the fglrx driver *I can't even set the display
brightness* let alone do more refined tweaks, furthermore it is needed
for a composite window manager (such as Compiz) to work.

I'm not saying that  open source video drivers don't work, I just can't
do all the things I want with them -besides, I know for a fact that
virtual consoles didn't disappear in previous Ubuntu releases when using
the fglrx driver, so it's clearly a regression that should be fixed
ASAP.

I can't tell if the problem is the latest fglrx driver itself or some
grub setting or whatever, anyways I've tried some suggested workaround
such as turning off the graphical terminal or changing the screen
resolution in /etc/default/grub and  unfortunately it didn't work.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1470862

Title:
  When using fglrx module, the virtual consoles are blank and useless

Status in fglrx-installer-updates package in Ubuntu:
  Confirmed

Bug description:
  When the PC boots it shows the sddm login, but if I switch to the
  first virtual console using Ctrl+Alt+F1, the console is blank. The
  other consoles are in the same state. Only the virtual console with
  the sddm login, is running fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates 2:15.200-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul  2 15:31:28 2015
  SourcePackage: fglrx-installer-updates
  UpgradeStatus: Upgraded to vivid on 2015-03-12 (112 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+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 1470862] Re: When using fglrx module, the virtual consoles are blank and useless

2015-07-15 Thread cogset
I'm affected by this bug too in Ubuntu Mate 15.04 amd64, after installing 
fglrx-core 2:15.200-0ubuntu4 ,
 fglrx  2:15.200-0ubuntu4  and fglrx-amdcccle   2:15.200-0ubuntu4  the six 
virtual consoles are blank, only  Ctrl+Alt+F7 works to get back to the 
graphical environment.

Removing the fglrx packages brings back the consoles.

In past Ubuntu releases (Lucid and Precise) I did not have this bug,
although the fglrx driver in that case had been manually installed
starting from the installer downloaded from the AMD site rather than
directly installing the fglrx packages from the official Ubuntu repo.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1470862

Title:
  When using fglrx module, the virtual consoles are blank and useless

Status in fglrx-installer-updates package in Ubuntu:
  Confirmed

Bug description:
  When the PC boots it shows the sddm login, but if I switch to the
  first virtual console using Ctrl+Alt+F1, the console is blank. The
  other consoles are in the same state. Only the virtual console with
  the sddm login, is running fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates 2:15.200-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul  2 15:31:28 2015
  SourcePackage: fglrx-installer-updates
  UpgradeStatus: Upgraded to vivid on 2015-03-12 (112 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+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 1424119] Re: Edit Connections...now insensitive by default in network manager's menu

2015-05-08 Thread cogset
I still had the bug with network-manager-gnome 0.9.4.1-0ubuntu2.5 in
Mint13 (based on Ubuntu 12.04 LTS), I've had to revert  to version
0.9.4.1-0ubuntu2.1 to get rid of it.

-- 
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/1424119

Title:
  Edit Connections...now insensitive by default in network manager's
  menu

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Precise:
  Fix Released

Bug description:
  [SRU justification]

  [Impact]

  grayed out on network-manager-applet, can't click

  arno@arno-1000H:~$ lsb_release -rd
  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04
  arno@arno-1000H:~$ apt-cache policy network-manager-gnome
  network-manager-gnome:
    Installé : 0.9.4.1-0ubuntu2.4
    Candidat : 0.9.4.1-0ubuntu2.4
   Table de version :
   *** 0.9.4.1-0ubuntu2.4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.9.4.1-0ubuntu2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

  Might be after upgrade to network-manager-gnome 0.9.4.1-0ubuntu2.4,
  the item Edit Connections... at the bottom of the network manager's
  menu is now insensitive i.e. grayed out, therefore user cannot
  configure his/her connections as indicated in
  http://docs.xubuntu.org/1204/internet-networks.html#network-
  connections

  workaround : launch /usr/bin/nm-connection-editor to display the
  network connections window and have access to the settings.

  [Test Case]
  after updating network-manager-gnome on laptop, you can always see this 
problem.

  [Regression Potential]

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1424119/+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