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 659412 - crash in Sudoku: trying to run remotely
crash in Sudoku: trying to run remotely
Status: RESOLVED DUPLICATE of bug 656770
Product: gnome-games-superseded
Classification: Deprecated
Component: BugBuddyBugs
2.32.x
Other All
: Normal critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2011-09-18 19:31 UTC by rodney
Modified: 2011-09-19 04:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description rodney 2011-09-18 19:31:43 UTC
Version: 2.32.1

What were you doing when the application crashed?
trying to run remotely	


Distribution: openSUSE 11.4 (x86_64)
Gnome Release: 2.32.1 (null) (SUSE)
BugBuddy Version: 2.32.0

System: Linux 2.6.37.6-0.7-default #1 SMP 2011-07-21 02:17:24 +0200 x86_64
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

Traceback (most recent call last):
  • File "/usr/bin/gnome-sudoku", line 67 in <module>
    start_game()
  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/gnome_sudoku.py", line 22 in start_game
    main.start_game()
  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/main.py", line 1003 in start_game
    u = UI()
  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/main.py", line 157 in __init__
    self.setup_gui()
  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/main.py", line 205 in setup_gui
    self.initialize_prefs()
  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/main.py", line 420 in initialize_prefs
    self.gconf[k] = v
  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 31 in __setitem__
    self.set_value (key, val)
  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/gtk_goodies/gconf_wrapper.py", line 86 in set_value
    apply (func, (self._domain + key, value))
GError: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Error connecting: Connection refused)


----------- .xsession-errors (238 sec old) ---------------------
(gpk-update-icon:2798): PackageKit-DEBUG: role now get-distro-upgrades
(gpk-update-icon:2798): PackageKit-DEBUG: not disconnecting as never connected
(gpk-update-icon:2798): PackageKit-DEBUG: current:	/821_ebedaaab_data
(gpk-update-icon:2798): PackageKit-DEBUG: emit added: /821_ebedaaab_data
(gpk-update-icon:2798): PackageKit-DEBUG: current:	/821_ebedaaab_data
(gpk-update-icon:2798): PackageKit-DEBUG: emit added: /821_ebedaaab_data
(gpk-update-icon:2798): PackageKit-DEBUG: role now get-distro-upgrades
(gpk-update-icon:2798): PackageKit-DEBUG: already processing request 0x3, so ignoring
(gpk-update-icon:2798): PackageKit-DEBUG: already processing request 0x3, so ignoring
(gpk-update-icon:2798): PackageKit-DEBUG: emit transaction-list-changed (when idle)
(gpk-update-icon:2798): PackageKit-DEBUG: last:	/821_ebedaaab_data
(gpk-update-icon:2798): PackageKit-DEBUG: emit removed: /821_ebedaaab_data
(gpk-update-icon:2798): PackageKit-DEBUG: last:	/821_ebedaaab_data
(gpk-update-icon:2798): PackageKit-DEBUG: emit removed: /821_ebedaaab_data
(gpk-update-icon:2798): PackageKit-DEBUG: notify::connected
--------------------------------------------------
Comment 1 Akhil Laddha 2011-09-19 04:31:00 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 bug 656770 ***