GNOME Bugzilla – Bug 449961
crash in Gimmie: cd /usr/port/....... gim...
Last modified: 2007-06-22 06:23:32 UTC
What were you doing when the application crashed? cd /usr/port/....... gimmie make make install restart add on panel error..... Distribution: Unknown Gnome Release: 2.18.2 2007-06-20 (FreeBSD GNOME Project) BugBuddy Version: 2.18.1 System: FreeBSD 6.2-RELEASE-p5 FreeBSD 6.2-RELEASE-p5 #1: Fri Jun 22 09:32:40 YEKST 2007 root@BSD.rosresurs.local:/usr/src/sys/i386/compile/BSD_KERNEL i386 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: nuoveXT-1.6 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 (121 sec old) --------------------- /usr/local/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /usr/local/etc/gdm/PreSession/Default: running: /usr/local/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "mdl" /usr/local/etc/gdm/Xsession: Beginning session setup... /usr/local/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session SESSION_MANAGER=local/BSD.rosresurs.local:/tmp/.ICE-unix/1034 ** (gnome-session:1034): WARNING **: Host name lookup failure on localhost. Initializing gnome-mount extension (nautilus:1082): Liboobs-WARNING **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files (nautilus:1082): Liboobs-WARNING **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files seahorse nautilus module initialized -------------------------------------------------- Traceback (most recent call last):
+ Trace 142819
for filename in os.listdir(self.note_path):
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 latest software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 419492 ***