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 271734 - strange message in status bar: 'Working 0x86d6688 (...)'
strange message in status bar: 'Working 0x86d6688 (...)'
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: High normal
: Future
Assigned To: Milan Crha
Evolution QA team
: 314561 340744 (view as bug list)
Depends on:
Blocks: 327508 327510
 
 
Reported: 2005-01-25 16:03 UTC by tom quas
Modified: 2007-10-25 18:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Pickture of "Working..." messages (19.92 KB, image/png)
2005-05-08 20:55 UTC, Ted Gould
  Details
untested patch for "Working" statusbar. (1.10 KB, patch)
2005-08-30 11:45 UTC, André Klapper
none Details | Review
Fix (740 bytes, patch)
2006-04-21 08:43 UTC, Sankar P
committed Details | Review
proposed evo patch (1.75 KB, patch)
2007-10-22 17:10 UTC, Milan Crha
committed Details | Review

Description tom quas 2005-01-25 16:03:41 UTC
My Evo status bar shows that strange message 'Working 0x86d6688 (...)' in
the Mailer no matter what I do. Switching folder, messages etc. does not
make it go away.
Comment 1 André Klapper 2005-01-31 11:59:12 UTC
well, at least it's a known issue, see for example
<http://lists.ximian.com/archives/public/evolution/2004-August/038917.html>.

you use IMAP, i guess?
Comment 2 André Klapper 2005-01-31 12:00:39 UTC
perhaps, perhaps related to bug 258663? (also about "working (...)"
never going away...
Comment 3 tom quas 2005-01-31 13:26:38 UTC
yeah, I got mailboxes configured using IMAP, though none of them is
actually being used; all my activated mailboxes use 'Maildir'.

hmm, just tried the junk stuff as described in #58663; it seems to be
gone now
Comment 4 Not Zed 2005-02-10 06:13:13 UTC
fixed i guess
Comment 5 bugreports 2005-04-05 16:43:36 UTC
This is evolution 2.2.1.1 and I again see Working 0x33d5ba18 (...) in
my status bar currently...
Comment 6 Ted Gould 2005-05-08 20:54:30 UTC
Definitely still happens for me.  All my mailboxes are IMAP.  It seems to happen
more regularly when I leave Evolution online for extended periods of time.  If I
go offline, read my e-mail, and then resync it doesn't seem to happen as often.

2.2.1.1 Ubuntu PPC
Comment 7 Ted Gould 2005-05-08 20:55:31 UTC
Created attachment 46191 [details]
Pickture of "Working..." messages

This is just a picture to prove I'm not crazy :)
Comment 8 André Klapper 2005-08-27 18:33:39 UTC
*** Bug 314561 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2005-08-27 18:34:14 UTC
copying comments of duplicate bug 314561 by Benjamin Berg:

"Looks like there is a small typo in mail/mail-mt.c:960. This can result in a
message in the status bar in the form of "Working 0x4f6db2d3".
Replacing the %p with %s should fix this. It also looks like the string is not
translatable currently."

would like to set target to 2.4 since this is a bug with high visibility, anyway
no target milestone existing yet, so putting to 2.5.
Comment 10 André Klapper 2005-08-27 18:53:20 UTC
so that would be the line
             what = g_strdup_printf("Working %p", msg);

just writing this down because "line 960" changes as time goes by... :-)

<http://cvs.gnome.org/viewcvs/evolution/mail/mail-mt.c?r1=1.82&r2=1.83>
Comment 11 André Klapper 2005-08-30 11:45:23 UTC
Created attachment 51552 [details] [review]
untested patch for "Working" statusbar.

untested patch to fix the offset display of the "working" message in statusbar;
also adds internationalization (hum... really 18 characters between "i" and
"n", cool) to the string... :-)
Comment 12 André Klapper 2005-08-30 11:48:06 UTC
hmm... needs translator comments, i wouldn't now what "working %s" should say if
i had to translate that.
Comment 13 parthasarathi susarla 2005-12-23 03:45:00 UTC
Hey andre, thanks for the patch. But 'msg' is not a string its a structure. So %s wont work.
IMHO, its best to remove the string or just have "Working..."
Although i agree it would be a totally vague message.
Comment 14 André Klapper 2006-01-03 00:29:21 UTC
partha: so, conclusion? i'd like to fix this for 2.6. just tell me exactly what to do, and keep the translators in mind... :-)
Comment 15 André Klapper 2006-02-07 12:28:17 UTC
partha: *PING*

we're heading string freeze next monday.
if we use "Working..." we need a translator comment. proposals?
Comment 16 Harish Krishnaswamy 2006-02-13 12:29:39 UTC
I vote for just getting rid of the message altogether - I do not see it being very useful for a user.
Comment 17 André Klapper 2006-02-13 13:48:46 UTC
i uncommented the string in cvs:
http://cvs.gnome.org/viewcvs/evolution/mail/mail-mt.c?r1=1.93&r2=1.94

closing as fixed.
Comment 18 Jeffrey Stedfast 2006-02-13 18:30:51 UTC
The only thing that worries me about the committed patch is that the real problem may not be solved - what's creating worker threads without a description? and why are they never exiting like they should?

I just feel that the patch simply hides the real problem...
Comment 19 André Klapper 2006-02-13 18:45:53 UTC
jeff, you're definitely right. reopen?
Comment 20 Veerapuram Varadhan 2006-02-14 21:18:57 UTC
The supposed fix (comment#19) introduced a crash. So, reopening the bug and raising the severity.

	MAIL_MT_UNLOCK (mail_msg_lock);
	if (msg->ops->describe_msg)
		what = msg->ops->describe_msg (msg, FALSE);
		/* uncommenting because message is not very useful for a user, see bug 271734
		else {
			what = g_strdup_printf("Working %p", msg);
		}
		*/

in the above code, "what" is a char*, that is uninitialized.  By commenting out the else part, "what" remains unitialized and crashes in further calls that use "what".
Comment 21 Veerapuram Varadhan 2006-02-15 10:01:37 UTC
Ok, Partha has reverted back the changes.. the commented lines are uncommented now.  Lowering the severity, however, the bug is till open as per comment#18.
Comment 22 André Klapper 2006-03-05 01:22:18 UTC
changing target milestone from 2.5 to future. sorry, too many bugs, too less time.
Comment 23 Sankar P 2006-04-21 08:43:49 UTC
Created attachment 64012 [details] [review]
Fix

There is no use of showing a HEXA-String to the user. Will set it to an empty (not NULL) string. Will not crash/show-cryptic-messages. 

The original issue of why some unnamed operations are created is still to be found out anyway.
Comment 24 Harish Krishnaswamy 2006-04-21 09:12:06 UTC
While the Hexa-string made no sense to me either, it always gave me valuable feedback that some activity was still in progress and I would do well to wait or at least not close the app, during some painfully long operations.

Setting this to an empty string nudges the usability a few notches below. Again, can we get rid of the unnamed operations instead ?
Comment 25 Vincent Untz 2006-04-21 09:27:15 UTC
(In reply to comment #24)
> While the Hexa-string made no sense to me either, it always gave me valuable
> feedback that some activity was still in progress and I would do well to wait
> or at least not close the app, during some painfully long operations.

Well, sometimes the hexa string just sits there, while there's no activity. So I'm not sure we can say this is good feedback...
Comment 26 André Klapper 2006-05-09 01:34:14 UTC
*** Bug 340744 has been marked as a duplicate of this bug. ***
Comment 27 Harish Krishnaswamy 2006-08-05 05:38:34 UTC
(In reply to comment #25)
> Well, sometimes the hexa string just sits there, while there's no activity. So
> I'm not sure we can say this is good feedback...

I am seeing this now, too. This is perhaps because there is no status update after 
the activity is complete. 

This begs a decision from the usability and mail folks.
Adding 'usability' keyword and srag to the CC list.
Comment 28 Milan Crha 2007-10-22 17:10:48 UTC
Created attachment 97650 [details] [review]
proposed evo patch

for evolution;

Show description of operation, if available, instead of empty string and end activity properly, if operation ended before/during activity start.
Comment 29 Srinivasa Ragavan 2007-10-23 05:37:33 UTC
Milan, looks fine to me. Commit to stable/head. (I haven't tested this as I can't reproduce this always).
Comment 30 Milan Crha 2007-10-23 08:47:33 UTC
Committed to trunk. Committed revision 34411.
Committed to stable. Committed revision 34412.