Crash on start of davmail.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: openjdk-6-jre-headless 6b23~pre10-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.19~ppa1-generic-tuxonice 3.0.4
Uname: Linux 3.0.0-12-generic-tuxonice x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 11 09:39:21 2011
ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java
ProcCmdline: java -Xmx512M -cp /usr/share/davmail/davmail.jar:/usr/share/java/swt.jar::/usr/share/davmail/lib/activation-1.1.1.jar:/usr/share/davmail/lib/commons-codec-1.3.jar:/usr/share/davmail/lib/commons-collections-3.1.jar:/usr/share/davmail/lib/commons-httpclient-3.1.jar:/usr/share/davmail/lib/commons-logging-1.0.4.jar:/usr/share/davmail/lib/htmlcleaner-2.1.jar:/usr/share/davmail/lib/jackrabbit-webdav-1.4.jar:/usr/share/davmail/lib/jcharset-1.3.jar:/usr/share/davmail/lib/jcifs-1.3.14.jar:/usr/share/davmail/lib/jdom-1.0.jar:/usr/share/davmail/lib/junit-3.8.1.jar:/usr/share/davmail/lib/log4j-1.2.16.jar:/usr/share/davmail/lib/mail-1.4.3.jar:/usr/share/davmail/lib/slf4j-api-1.3.1.jar:/usr/share/davmail/lib/slf4j-log4j12-1.3.1.jar:/usr/share/davmail/lib/stax-api-1.0.1.jar:/usr/share/davmail/lib/stax2-api-3.0.3.jar:/usr/share/davmail/lib/woodstox-core-asl-4.0.9.jar:/usr/share/davmail/lib/xercesImpl-2.8.1.jar davmail.DavGateway
Signal: 6
SourcePackage: openjdk-6
StacktraceTop:
?? () from /usr/lib/libgconf-2.so.4
dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: java crashed with SIGABRT in dbus_connection_dispatch()
UpgradeStatus: Upgraded to oneiric on 2011-10-04 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #824982, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.