GConf error: Type mismatch: Expected `string' got `list' for key /apps/evolution/shell/network_config/ignore_hosts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evolution |
Fix Released
|
Medium
|
|||
evolution (Ubuntu) |
Fix Released
|
Low
|
Didier Roche-Tolomelli | ||
Maverick |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: evolution
uploaded to -proposed:
evolution (2.30.3-1ubuntu7) maverick-proposed; urgency=low
* debian/
- backport from upstream, change the migration to 2.30 for people
using /apps/evolution
* debian/
- show signature if you have one account and aren't in express mode
(LP: #649609)
Test case:
1. check that you were in a proxy configuration and that you get the error 2.30.3-1ubuntu6
2. install from -proposed the new version
3. restart evolution and check that you don't have anymore this error dialog at start.
--------------
When I start evolution I get a dialog saying:
GConf error: Type mismatch: Expected `string' got `list' for key /apps/evolution
You need to apply the upstream commit aa61df9 for this bug.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu6
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelMo
Architecture: i386
Date: Tue Oct 12 09:01:31 2010
ProcEnviron:
PATH=(custom, user)
LANG=en_CA.utf8
SHELL=/bin/bash
SourcePackage: evolution
Changed in evolution: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in evolution (Ubuntu): | |
assignee: | nobody → Didier Roche (didrocks) |
importance: | Undecided → Low |
Changed in evolution (Ubuntu): | |
status: | New → Triaged |
description: | updated |
Changed in evolution (Ubuntu Maverick): | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: |
added: verification-done removed: verification-needed |
I really have to wonder why evolution's 2.32 release was not used for Maverick which is a gnome 2.32 release.
Now that evolution has released 2.32 they are no longer landing bug fixes to their gnome-2-32 branch, so the responsibility of watching their gnome-2-32 branch for bug fixes and backporting them to your 2.30 based release is going to land in your lap. I hope you take this responsibility seriously and don't just ignore your out-of-date evolution release.