abrt version: 1.1.13
cmdline: /usr/bin/python /usr/libexec/telepathy-sunshine
comment: It does not happen always, i believe that it may only happen when i add more than one contact. Unfortunately i am not sure.
reason: group.py:52:create_group:RuntimeError: dictionary changed size during iteration
release: Fedora release 13 (Goddard)
group.py:52:create_group:RuntimeError: dictionary changed size during iteration
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/sunshine/util/decorator.py", line 130, in async_function
File "/usr/lib/python2.6/site-packages/sunshine/channel/group.py", line 52, in create_group
for group in self.conn.profile.groups:
RuntimeError: dictionary changed size during iteration
Local variables in innermost frame:
group: <sunshine.lqsoft.pygadu.models.GaduContactGroup object at 0x2775a90>
g: <sunshine.lqsoft.pygadu.models.GaduContactGroup object at 0x280d350>
h: <md5 HASH object @ 0x28022b8>
self: <sunshine.channel.group.SunshineGroupChannel at /org/freedesktop/Telepathy/Connection/sunshine/gadugadu/_35672780/channel5 at 0x280ae50>
group_xml: <Element Group at 2802518>
How to reproduce
1. Add new gadugadu contact
2. Change alias
Created an attachment (id=446766)
OS Release: Fedora release 13 (Goddard)
How to reproduce
1. configure a GG account
2. add a contact
3. expect a crash
Could you check is that bug occurs in sunshine from GIT: git://git.collabora.co.uk/git/telepathy-sunshine.git ?
Hold on, I'll upload a package
Here it is, latest git code packaged:
While I was able to reproduce it a while ago, the problem seems to be gone now - which might indicate it was fixed by an update to some other package. Can you please test again?
And here's the latest git code package:
I could not reproduce it for while now. Tried povided package and still no luck so it is good.
telepathy-sunshine-0.2.0-1.fc15 has been submitted as an update for Fedora 15.
telepathy-sunshine-0.2.0-1.fc14 has been submitted as an update for Fedora 14.
telepathy-sunshine-0.2.0-1.fc13 has been submitted as an update for Fedora 13.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing telepathy-sunshine-0.2.0-1.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
telepathy-sunshine-0.2.0-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
telepathy-sunshine-0.2.0-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
telepathy-sunshine-0.2.0-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.