After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574785 - crash in Sudoku: i make a desktop icon: g...
crash in Sudoku: i make a desktop icon: g...
Status: RESOLVED DUPLICATE of bug 444693
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
unspecified
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-10 16:50 UTC by pitwalker
Modified: 2009-03-10 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description pitwalker 2009-03-10 16:50:27 UTC
Version: 2.24.1.1

What were you doing when the application crashed?
i make a desktop icon:
gksu -w /usr/games/gnome-sudoku
click it


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.1 2008-10-24 (Ubuntu)
BugBuddy Version: 2.24.1

System: Linux 2.6.27-13-generic #1 SMP Thu Feb 26 07:26:43 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: (null)
Icon Theme: (null)

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 (29288506 sec old) ---------------------
tracker-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfce4-menu-plugin: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
thunar-tpa: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gtk-recordMyDesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
DBus connection has been lost, trackerd will now shutdown
xfce-mcs-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfce4-places-plugin: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnometris: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-sudoku: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
--------------------------------------------------
Traceback (most recent call last):
  • File "/usr/games/gnome-sudoku", line 50 in <module>
    start_game()
  • File "/var/lib/python-support/python2.5/gnome_sudoku/gnome_sudoku.py", line 21 in start_game
    main.start_game()
  • File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 1051 in start_game
    u = UI()
  • File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 172 in __init__
    self.setup_gui()
  • File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 231 in setup_gui
    self.initialize_prefs()
  • File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 512 in initialize_prefs
    self.gconf[k]=v
  • File "/var/lib/python-support/python2.5/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 30 in __setitem__
    self.set_value (key, val)
  • File "/var/lib/python-support/python2.5/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 83 in set_value
    apply (func, (self._domain + key, value))
GError: Nem sikerült kapcsolatot teremteni a konfigurációs kiszolgálóval; az egyik lehetséges ok, hogy engedélyezni kell a TCP/IP-hálózatkezelést az ORBit számára, vagy NFS zárolások maradtak fent egy rendszerösszeomlás miatt. További információ: http://www.gnome.org/projects/gconf/. (Részletek - 1: Nem sikerült kapcsolatot szerezni a munkamenethez: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Comment 1 Fabio Durán Verdugo 2009-03-10 18:40:01 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.


*** This bug has been marked as a duplicate of 444693 ***