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 412477 - crash in Sudoku: I was editing the "numbe...
crash in Sudoku: I was editing the "numbe...
Status: RESOLVED DUPLICATE of bug 406649
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: 2007-02-27 00:37 UTC by Vassilis Pandis
Modified: 2007-02-27 00:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Vassilis Pandis 2007-02-27 00:37:52 UTC 
What were you doing when the application crashed?
I was editing the "number field" and the "note field" . This is reproducable but takes a little patience. You have to keep editing them and it will crash after 2-3 minutes of editing. I cannot describe a way to recreate this reliably all the time - just keep playing with it. It crashed once while playing, which is why I noticed.


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.17.91 2007-02-12 (Ubuntu)
BugBuddy Version: 2.17.3

System: Linux 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

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

+ Trace 114205

  • File "/usr/games/gnome-sudoku", line 7 in <module> 
    crappy_command
NameError: name 'crappy_command' is not defined 
checking for valid crashreport now
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
got DevicePresenceNotify event (reltype=15)
--------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1039, in entry_callback
    self.remove(widget.x,widget.y)
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1146, in remove
    self.entry_validate(linked_entry)
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1078, in entry_validate
    self.__entries__[conflict].set_error_highlight(True)
KeyError: None
Comment 1 Vassilis Pandis 2007-02-27 00:41:38 UTC 
Ignore the 'crappy_command' reference (unless of course it is relevant). I was debugging why this was not getting picked up by Ubuntu's bug reporting tool that sends stuff to launchpad instead of gnome's bugzilla. All "crappy_command" is is an entry "crappy_command" as the first line of /usr/bin/gnome-sudoku. It refers to nothing, is just an invalid statement.
Comment 2 Vassilis Pandis 2007-02-27 00:51:16 UTC 

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