After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607908 - error window too wide
error window too wide
Status: RESOLVED FIXED
Product: empathy
Classification: Core
Component: Accounts
2.29.x
Other Linux
: Low normal
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-01-24 05:10 UTC by Omer Akram
Modified: 2010-02-17 10:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
attachment left behind I guess (179.00 KB, image/png)
2010-01-24 05:16 UTC, Omer Akram
  Details
http://git.collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/wrap-error-607908 (1.28 KB, patch)
2010-02-16 17:10 UTC, Guillaume Desmottes
accepted-commit_now Details | Review

Description Omer Akram 2010-01-24 05:10:43 UTC
to reproduce start ubuntu from a live session/for the first time after install I guess open empathy and try to make a new account after giving all information a keyring window comes up wait for 15-20 secs and the error comes up as attached in the image. that error message did not even fit 1440x900 screen.
Comment 1 Omer Akram 2010-01-24 05:15:02 UTC
I think I also faced the same error on my netbook with empathy 2.29.5 a few days ago but that window was not too wide(normal sized)
Comment 2 Omer Akram 2010-01-24 05:16:01 UTC
Created attachment 152127 [details]
attachment left behind I guess
Comment 3 Guillaume Desmottes 2010-02-16 17:10:05 UTC
Created attachment 153942 [details] [review]
http://git.collabora.co.uk/?p=user/cassidy/empathy;a=shortlog;h=refs/heads/wrap-error-607908

 src/empathy-account-assistant.c |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)
Comment 4 Cosimo Cecchi 2010-02-17 00:47:49 UTC
Review of attachment 153942 [details] [review]:

Looks good to me.
Comment 5 Guillaume Desmottes 2010-02-17 10:08:06 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.