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 511822 - crash in Sudoku: Distribution: Ubuntu 7.1...
crash in Sudoku: Distribution: Ubuntu 7.1...
Status: RESOLVED DUPLICATE of bug 418427
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
2.20.x
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-24 16:12 UTC by yoshiro_sasaki
Modified: 2008-01-25 04:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description yoshiro_sasaki 2008-01-24 16:12:16 UTC 
Version: 2.20.1

What were you doing when the application crashed?
Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

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 ---------------------
Traceback (most recent call last):

+ Trace 186641

  • File "/usr/games/gnome-sudoku", line 20 in <module> 
    from gnome_sudoku.gnome_sudoku import start_game
ImportError: No module named gnome_sudoku.gnome_sudoku 
Traceback (most recent call last):

+ Trace 186641

  • File "/usr/games/gnome-sudoku", line 20 in <module> 
    from gnome_sudoku.gnome_sudoku import start_game
ImportError: No module named gnome_sudoku.gnome_sudoku 
Traceback (most recent call last):

+ Trace 186641

  • File "/usr/games/gnome-sudoku", line 20 in <module> 
    from gnome_sudoku.gnome_sudoku import start_game
ImportError: No module named gnome_sudoku.gnome_sudoku 
--------------------------------------------------
Traceback (most recent call last):

+ Trace 186641

  • File "/usr/games/gnome-sudoku", line 20 in <module> 
    from gnome_sudoku.gnome_sudoku import start_game
ImportError: No module named gnome_sudoku.gnome_sudoku 



Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

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 ---------------------
Traceback (most recent call last):

+ Trace 186641

  • File "/usr/games/gnome-sudoku", line 20 in <module> 
    from gnome_sudoku.gnome_sudoku import start_game
ImportError: No module named gnome_sudoku.gnome_sudoku 
Traceback (most recent call last):

+ Trace 186641

  • File "/usr/games/gnome-sudoku", line 20 in <module> 
    from gnome_sudoku.gnome_sudoku import start_game
ImportError: No module named gnome_sudoku.gnome_sudoku 
Traceback (most recent call last):

+ Trace 186641

  • File "/usr/games/gnome-sudoku", line 20 in <module> 
    from gnome_sudoku.gnome_sudoku import start_game
ImportError: No module named gnome_sudoku.gnome_sudoku 
--------------------------------------------------
Traceback (most recent call last):

+ Trace 186641

  • File "/usr/games/gnome-sudoku", line 20 in <module> 
    from gnome_sudoku.gnome_sudoku import start_game
ImportError: No module named gnome_sudoku.gnome_sudoku 






Comment 1


Thomas Andersen





          2008-01-25 04:03:03 UTC
        



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 418427 ***