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 348768 - snarky weekly bug report
snarky weekly bug report
Status: RESOLVED DUPLICATE of bug 344196
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.6.0
Other other
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-07-26 10:55 UTC by Herbert Carl Meyer
Modified: 2006-07-26 15:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Herbert Carl Meyer 2006-07-26 10:55:10 UTC 
Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution Exchange
Severity: blocker
Version: GNOME2.14.2 2.6.0
Gnome-Distributor: Red Hat, Inc
Synopsis: snarky weekly bug report
Bugzilla-Product: Evolution Exchange
Bugzilla-Component: Connector
Bugzilla-Version: 2.6.0
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:

evolution connector is still broke

Steps to reproduce the crash:

1.  finsh weds morning stuff

2.  re-arm exchange account in evolution

3.  wait for crash, attempt clever abuse of droid who will mark this bug
report as duplicate of bug #yada-yada and close it.

Expected Results:

working evolution access of exchange server

How often does this happen?

every time I am stupid enough to re-arm exchange account

Additional Information:

FIX THE DAMN BUGS (plural). 86'ing bug reports is not coping with the
error. If you wanna work that way GO WORK FOR MICROSOFT. They are always
hiring idiots.


Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.6'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208215872 (LWP 3244)]
[New Thread -1384129632 (LWP 3286)]
[New Thread -1363149920 (LWP 3276)]
[New Thread -1351533664 (LWP 3270)]
[New Thread -1340847200 (LWP 3268)]
[New Thread -1280783456 (LWP 3267)]
[New Thread -1270293600 (LWP 3266)]
[New Thread -1259394144 (LWP 3265)]
(no debugging symbols found)
0x001d1402 in __kernel_vsyscall ()

+ Trace 69643

Thread 3 (Thread -1363149920 (LWP 3276))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 camel_exchange_store_connected
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #11 camel_object_trigger_event
    from /usr/lib/libcamel-1.2.so.0
  • #12 camel_stub_send
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #13 start_thread
    from /lib/libpthread.so.0
  • #14 clone
    from /lib/libc.so.6 




------- Bug created by bug-buddy at 2006-07-26 10:55 -------
Comment 1 Karsten Bräckelmann 2006-07-26 11:56:02 UTC 
(In reply to comment #0)

> Steps to reproduce the crash:
[...]
> 3.  wait for crash, attempt clever abuse of droid who will mark this bug
> report as duplicate of bug #yada-yada and close it.

> Additional Information:
> 
> FIX THE DAMN BUGS (plural). 86'ing bug reports is not coping with the
> error. If you wanna work that way GO WORK FOR MICROSOFT. They are always
> hiring idiots.

Thanks for your opinion. I'd better not write mine. </sarcasm>

You are seriously confusing the bugsquad in general with the developers of an app in particular. While bug 348037 was pretty much fun to read, this is not.

Also, you just insulted me (well the entire bugsquad) who are doing all this work on a volunteer basis. You do realize all I get for this work is your fucking comment and attitude, right?


Kindly take your personal opinion elsewhere.
Comment 2 Karsten Bräckelmann 2006-07-26 13:00:40 UTC 
Interesting side note:  According to the reported version, you are still using Evolution and Evolution-Exchange 2.6.0, as shipped with FC5 install media.

However, there are updates available by FC5. Packages for the entire Evo 2.6.2 stack are available from a FC update mirror near you for 7 weeks already.

How could you possibly expect any issue to be fixed, without updating?
Comment 3 André Klapper 2006-07-26 13:15:12 UTC 
dear herbert,
thanks for taking the time to report this. i really appreciate your detailed description on how to reproduce this bug and your will to help microsoft improving their impressive software.
if you find some spare time between two rants, please report this bug to the fedora bug tracking system also. have fun, and get an up-to-date version by the way.

your good ol' andre

*** This bug has been marked as a duplicate of 344196 ***
Comment 4 Olav Vitters 2006-07-26 15:45:13 UTC 
(In reply to comment #1)
> You are seriously confusing the bugsquad in general with the developers of an
> app in particular. While bug 348037 was pretty much fun to read, this is not.

To follow up on Karten. Contructive comments regarding actual bugs are appreciated. Rants are not. Crashers are frustating, but there is nothing that bugsquad can do about it. More developers would be nice and are wanted. If you want to discuss process issues with the developers, use a mailinglist. Bugzilla is stricly about the actual bugs/enhancements (eg.. how to reproduce solve them, not about comparing developers to idiots).
Failing to show common courtesy may result in your Bugzilla account being disabled. See also http://live.gnome.org/CodeOfConduct