Bug 134515

Summary: GIMP crashes on AMD K6-2
Product: [openSUSE] SUSE LINUX 10.0 Reporter: S. B. <sb56637>
Component: X11 ApplicationsAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED WONTFIX QA Contact: Stefan Dirsch <sndirsch>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i586   
OS: Other   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description S. B. 2005-11-18 23:50:41 UTC 
Hi,

I have SuSE 10.0 Final on a computer with a 300MHz AMD K6-2 processor, which is essentially an i586 processor.  When I go to run the default GIMP supplied on the CD's, it run the setup wizard (tilecache size, where to put config, etc.) and then immediately segfaults.  The startup splash never appears.  It gives me no clear error, simply "illegal instruction" when run from a command line.

Thanks!
Comment 1 Michael Gross 2005-11-21 15:43:52 UTC 
Please create a backtrace with gdb (after installing the debuginfo-package) or with ltrace/strace and attach it here. Probably GIMP was compiled using an instruction that is not understood by the K6 processor.
Comment 2 Michael Gross 2005-12-06 15:02:12 UTC 
Sorry, but I have to close this bug because of the missing information. If you can provide them, please reopen this report and attach the file(s).
Comment 3 Stephan Kulow 2008-06-25 09:34:05 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:35:46 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:41:35 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:53:03 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(