GNOME Bugzilla – Bug 446899
crash in Gimmie: Clicking People > New pe...
Last modified: 2007-06-23 17:43:01 UTC
What were you doing when the application crashed? Clicking People > New person button Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (301713 sec old) --------------------- DEBUG::Sat Jun 09 10:43:40 GMT+01:00 2007::org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl::writeStats::211: java.io.FileNotFoundException: /Azureus_Stats.xml (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:179) at java.io.FileOutputStream.<init>(FileOutputStream.java:70) at org.gudy.azureus2.core3.stats.impl.StatsWriterImpl.write(StatsWriterImpl.java:64) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl.writeStats(StatsWriterPeriodicImpl.java:208) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl.update(StatsWriterPeriodicImpl.java:103) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl$1.runSupport(StatsWriterPeriodicImpl.java:240) at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69) DEBUG::Sat Jun 09 10:44:09 GMT+01:00 2007::com.aelitis.azureus.core.networkmanager.impl.NetworkConnectionImpl::notifyOfException::189: error.getMessage() == null MultiPeerDownloader::doProcessing::169,ReadController::doHighPriorityRead::224,ReadContr ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 140466
if gaim_dbus:
raise dbus.DBusException DBusException
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 418744 ***