GNOME Bugzilla – Bug 349913
crash in camel_url_new_with_base (base=0x0, url_string=0x0)
Last modified: 2008-02-20 05:37:39 UTC
What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.90 2006-07-24 (Ubuntu) BugBuddy Version: 2.15.90 Memory status: size: 163737600 vsize: 0 resident: 163737600 share: 0 rss: 36044800 rss_rlim: 0 CPU usage: start_time: 1154691571 rtime: 0 utime: 513 stime: 0 cutime:487 cstime: 0 timeout: 26 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231694160 (LWP 5032)] [New Thread -1312896096 (LWP 5053)] [New Thread -1321288800 (LWP 5050)] [New Thread -1303520352 (LWP 5042)] [New Thread -1295127648 (LWP 5041)] [New Thread -1286734944 (LWP 5040)] [New Thread -1278342240 (LWP 5038)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 69970
Thread 1 (Thread -1231694160 (LWP 5032))
Add connector keyword and assign it to the mailer component. Set target milestone to 2.8.
i'd love to see a description here to know what jie was doing when the application crashed... beginning of the stacktrace looks similar to bug 348866.
I don't remember what I was doing when the crash occured.
This is an evolution exchange problem. changing the product
*** Bug 355397 has been marked as a duplicate of this bug. ***
*** Bug 357652 has been marked as a duplicate of this bug. ***
stacktrace with line numbers available at bug 360939.
*** Bug 360939 has been marked as a duplicate of this bug. ***
(In reply to comment #7) > stacktrace with line numbers available at bug 360939. > Samuel: Thanks for the trace with debug symbols (bug#360939). From the backtrace, it looks like you tried to edit an already (mis)configured exchange account. Is it so? Also, it will be useful to know more elaborate steps to reproduce this bug, as a "null string" (url_string=0x0) in frame#7 of Thread1 is not an expected one. A "null" check can fix this crasher, however, would like to know what made it to send a "null" string.
This problem happend, first, while trying to configure Evolution to use Exchange so I guess you can say it had not been configured correctly...yet. I'll attempt to recreate the problem by deleting my current configuration and creating an Exchange profile for Evolution. I'll post my results here after the holidays. Cheers, Sam
*** Bug 383330 has been marked as a duplicate of this bug. ***
*** Bug 392344 has been marked as a duplicate of this bug. ***
*** Bug 394517 has been marked as a duplicate of this bug. ***
*** Bug 394974 has been marked as a duplicate of this bug. ***
*** Bug 398413 has been marked as a duplicate of this bug. ***
*** Bug 406234 has been marked as a duplicate of this bug. ***
*** Bug 412242 has been marked as a duplicate of this bug. ***
https://launchpad.net/ubuntu/+source/evolution/+bug/98728 also has debug symbols.
*** Bug 431257 has been marked as a duplicate of this bug. ***
*** Bug 431500 has been marked as a duplicate of this bug. ***
*** Bug 440282 has been marked as a duplicate of this bug. ***
*** Bug 445404 has been marked as a duplicate of this bug. ***
varadhan, please also see bug 425093 (which does not look like exchange to me), and bug 410750 which is probably a dup?
*** Bug 431585 has been marked as a duplicate of this bug. ***
*** Bug 447912 has been marked as a duplicate of this bug. ***
*** Bug 449124 has been marked as a duplicate of this bug. ***
hmm, so can anybody of the reporters please answer varadhan's question in comment 9: "Also, it will be useful to know more elaborate steps to reproduce this bug"? Thanks in advance for your help to fix this?
Here was my situation when my problem occurred.. My domain password had expired. In the domain authentication process, I changed my domain password to a new one (on my Windows XP computer). Later (about 2 hrs), I fired up Evolution on my Linux (FC7) workstation. It prompted me that the authentication had failed and to re-enter the password. When I had entered my new password and then submitted it, it immediately crashed. I've got two FC7 workstations, and they both had similar issues (I didn't submit the second since it was like the first).
(In reply to comment #28) > Here was my situation when my problem occurred.. > > My domain password had expired. In the domain authentication process, I > changed my domain password to a new one (on my Windows XP computer). Later > (about 2 hrs), I fired up Evolution on my Linux (FC7) workstation. It prompted > me that the authentication had failed and to re-enter the password. When I had > entered my new password and then submitted it, it immediately crashed. > > I've got two FC7 workstations, and they both had similar issues (I didn't > submit the second since it was like the first). > Thanks for the update, Michael. Did you get similar trace as reported in this bug or a different one? If its a different one, would you mind attaching it here - with debug symbols? Thanks again - let me work on the scenario that you mentioned above.
*** Bug 449503 has been marked as a duplicate of this bug. ***
*** Bug 451076 has been marked as a duplicate of this bug. ***
*** Bug 453393 has been marked as a duplicate of this bug. ***
*** Bug 465394 has been marked as a duplicate of this bug. ***
*** Bug 473730 has been marked as a duplicate of this bug. ***
*** Bug 474121 has been marked as a duplicate of this bug. ***
*** Bug 471205 has been marked as a duplicate of this bug. ***
*** Bug 476174 has been marked as a duplicate of this bug. ***
*** Bug 477935 has been marked as a duplicate of this bug. ***
*** Bug 478276 has been marked as a duplicate of this bug. ***
*** Bug 481514 has been marked as a duplicate of this bug. ***
*** Bug 482794 has been marked as a duplicate of this bug. ***
from bug 360939:
+ Trace 167297
*** Bug 485658 has been marked as a duplicate of this bug. ***
*** Bug 486293 has been marked as a duplicate of this bug. ***
*** Bug 491342 has been marked as a duplicate of this bug. ***
*** Bug 498729 has been marked as a duplicate of this bug. ***
*** Bug 496337 has been marked as a duplicate of this bug. ***
*** Bug 494176 has been marked as a duplicate of this bug. ***
*** Bug 498809 has been marked as a duplicate of this bug. ***
*** Bug 478628 has been marked as a duplicate of this bug. ***
*** Bug 463166 has been marked as a duplicate of this bug. ***
*** Bug 482197 has been marked as a duplicate of this bug. ***
*** Bug 503693 has been marked as a duplicate of this bug. ***
could have been already fixed by bug 500233
Andre you are right.
*** Bug 500233 has been marked as a duplicate of this bug. ***
this has been fixed and committed in revision 8355. the fix will be included in the next stable release 2.22 (march 2008).
*** Bug 506878 has been marked as a duplicate of this bug. ***
*** Bug 514316 has been marked as a duplicate of this bug. ***
*** Bug 504196 has been marked as a duplicate of this bug. ***
*** Bug 505546 has been marked as a duplicate of this bug. ***
*** Bug 509450 has been marked as a duplicate of this bug. ***
*** Bug 508063 has been marked as a duplicate of this bug. ***
*** Bug 516298 has been marked as a duplicate of this bug. ***