[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-25 Thread Alejandro Morales Lepe
I also experienced this. ** Attachment added: "Pantallazo.png" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/965686/+attachment/3103222/+files/Pantallazo.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-11 Thread Nicolas Delvaux
Ok. Against which package should I report it? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/965686 Title: Upgrade from lucid trigger an unreadable error dialog (font issue?) To

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-11 Thread Mathieu Trudel-Lapierre
It's going to be very hard to fix this in nm-applet; the issue really comes from the fact that fontconfig or gtk or some other low-level part is getting broken by the upgrade. We do expect people to reboot after running the dist-upgrade though. Nicolas, since it's obviously wrong, please file a se

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-10 Thread Nicolas Delvaux
Well, as shown in the screenshot in my first comment, the "boxes chars" not only appear in this error message, but also in the network-manager applet (and probably elsewhere). Should I report a new bug for this issue? -- You received this bug notification because you are a member of Ubuntu Deskto

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-10 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution - 3.2.3-0ubuntu6 --- evolution (3.2.3-0ubuntu6) precise; urgency=low * debian/libevolution.preinst: if upgrading from versions prior to 3.2.0; kill all instances of evolution-alarm-notify to avoid an unreadable error message about

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-10 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/evolution/ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/965686 Title: Upgrade from lucid trigger an unreadable error dialog (font iss

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-06 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/965686 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, whi

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-04 Thread Mathieu Trudel-Lapierre
Yeah, sounds like a reasonable way to fix this kind of issue; I'll check if there is a way to stop just the alarm-notify binary and possibly the calendar and addressbook factories. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolut

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-02 Thread Martin Pitt
Mathieu, we could run the counterpart of "evolution --force-shutdown" in the preinst if the upgrade detects that we are upgrading from an old version? I. e. kill all running e-a-n instances? There might be a more elegant solution to detect that situation at runtime, but I don't think we should was

[Bug 965686] Re: Upgrade from lucid trigger an unreadable error dialog (font issue?)

2012-04-02 Thread Steve Langasek
Given that this error message comes from evolution, I'm not sure there's much that can be done from update-manager to address it; I think the package itself would need to take care to notice that it's in an inconsistent state somehow and avoid such broken pop-ups. ** Package changed: update-manage