Seriously. Are you folks really that bitter about this Mint thing? I
know you know that Mint is nothing more than Ubuntu Linux with usable
desktops (i.e. Cinnamon and MATE), for those people that find your
tablet-izing Unity desktop simply unusable.
Heck, Mint is not even a fork but simply a layer of packages on top of
Ubuntu Linux -- really, no different than installing a bunch of packages
out of a PPA. Do you simply refuse to support Ubuntu Linux packages
simply because a PPA may have installed some unrelated packages?
You can see clearly from the apport output that this report is for an
"unmodified" gnome-keyring package straight out of your own
repositories:
Package: gnome-keyring 3.2.2-2ubuntu4
apt-cache validates this assertion also:
$ apt-cache policy gnome-keyring
gnome-keyring:
Installed: 3.2.2-2ubuntu4
Candidate: 3.2.2-2ubuntu4
Version table:
*** 3.2.2-2ubuntu4 0
500 http://apt.interlinx.bc.ca/ubuntu/ precise/main i386 Packages
100 /var/lib/dpkg/status
So, are you really going to play this sour grapes game or are you going
to do the right thing here?
--
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/1033904
Title:
memory leak in gnome-keyring-daemon
Status in “gnome-keyring” package in Ubuntu:
Invalid
Bug description:
The gnome-keyring-daemon is leaking memory, quite badly. My current
gnome-keyring-daemon process's usage:
$ cat /proc/25537/status
Name: gnome-keyring-d
State: S (sleeping)
Tgid: 25537
Pid: 25537
PPid: 1
TracerPid: 0
Uid: 1001 1001 1001 1001
Gid: 1001 1001 1001 1001
FDSize: 256
Groups: 4 20 24 25 29 30 44 46 106 107 108 111 121 133 142 146 1001
1010 1011 2000
VmPeak: 1191980 kB
VmSize: 1191980 kB
VmLck: 776 kB
VmPin: 0 kB
VmHWM: 20496 kB
VmRSS: 17740 kB
VmData: 1180548 kB
VmStk: 136 kB
VmExe: 912 kB
VmLib: 6172 kB
VmPTE: 636 kB
VmSwap: 28 kB
Threads: 141
SigQ: 0/31006
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000005001
SigIgn: 0000000000001000
SigCgt: 0000000180010000
CapInh: 0000000000000000
CapPrm: 0000000000004000
CapEff: 0000000000004000
CapBnd: ffffffffffffffff
Cpus_allowed: f
Cpus_allowed_list: 0-3
Mems_allowed: 1
Mems_allowed_list: 0
voluntary_ctxt_switches: 9754
nonvoluntary_ctxt_switches: 270
As you can see, 1GB of ram for such a trivial (in terms of data use)
process is simply insane. This will continue (as it has in the past)
until the process gets an ENOMEM and exits and a new one is started in
it's place, only to fall victim to the same fate.
ProblemType: Bug
DistroRelease: LinuxMint 12
Package: gnome-keyring 3.2.2-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
Uname: Linux 3.2.0-26-generic-pae i686
NonfreeKernelModules: ksplice_dewe07wg_vmlinux_new ksplice_dewe07wg
ksplice_t0vennht_vmlinux_new ksplice_t0vennht ksplice_xmujt7c9_vmlinux_new
ksplice_xmujt7c9 ksplice_l34fkoxc_ttm_new ksplice_l34fkoxc
ksplice_3e1g28bz_vmlinux_new ksplice_3e1g28bz ksplice_4qv4fmpp_vmlinux_new
ksplice_4qv4fmpp ksplice_r0kvmav6_vmlinux_new ksplice_r0kvmav6 ksplice_20ua8hym
ksplice_ifvi3ya6 ksplice_dde1axkc ksplice_s4l4rfyg
ksplice_unoti1kb_snd_usb_audio_new ksplice_unoti1kb ksplice_7he9oi11
ksplice_ik8iovr1 ksplice_obg057es_vmlinux_new ksplice_obg057es
ApportVersion: 2.0.1-0ubuntu11
Architecture: i386
Date: Tue Aug 7 05:59:23 2012
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop:
2012-03-21T15:31:45
mtime.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop:
2012-02-23T18:28:50
mtime.conffile..etc.xdg.autostart.gnome.keyring.secrets.desktop:
2012-02-23T18:26:38
mtime.conffile..etc.xdg.autostart.gnome.keyring.ssh.desktop:
2012-03-21T15:32:22
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1033904/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
