GNOME Bugzilla – Bug 455691
crash in Sudoku: starting the application...
Last modified: 2007-07-10 21:51:33 UTC
What were you doing when the application crashed? starting the application. It started crashing on startup after I ran apt-get update and apt-get upgrade today, 7-10-2007 Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.20-1-486 #1 Tue Apr 24 21:08:25 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Amaranth 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 --------------------- /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "ffreeloader" /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/lappy:/tmp/.ICE-unix/3964 Window manager warning: Failed to read saved session file /home/ffreeloader/.metacity/sessions/default0.ms: Failed to open file '/home/ffreeloader/.metacity/sessions/default0.ms': No such file or dire ** Message: Not starting remote desktop server ** (gnome-cups-icon:4050): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:4050): WARNING **: IPP request failed with status 1280 Initializing gnome-mount extension Unable to open desktop file /var/lib/menu-xdg/applications/menu-xdg/X-Debian-Apps-Tools-k3b.desktop for panel launcher: No such file or directory TypeError: function takes exactly 0 arguments (1 given) -------------------------------------------------- TypeError: function takes exactly 0 arguments (1 given)
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 453825 ***