263874 – yast2 crashes during hw configuration

Bug 263874 - yast2 crashes during hw configuration

Summary: yast2 crashes during hw configuration

Status:	RESOLVED DUPLICATE of bug 263199

Alias:	None

Product:	openSUSE 10.3
Classification:	openSUSE
Component:	Installation (show other bugs)
Version:	Alpha 3
Hardware:	PowerPC Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2007-04-12 14:54 UTC by peter czanik
Modified:	2007-04-16 09:14 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	Other
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
YaST2 logs attached (704.18 KB, application/x-compressed-tar) 2007-04-12 14:56 UTC, peter czanik	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description peter czanik 2007-04-12 14:54:30 UTC

Tested on Pegasos PPC and EFIKA, YaST2 crashes during hw configuration just after release notes are showed. The text on screen is:

/usr/lib/YaST2/startup/YaST2.call: line 464: 3524 Killed $OPT_FBITERM y2base "$Y2_MODULE_NAME" $Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS

Comment 1 peter czanik 2007-04-12 14:56:41 UTC

Created attachment 130764 [details]
YaST2 logs attached

Comment 2 peter czanik 2007-04-12 19:16:55 UTC

I just made a new install using the serial console, and YaST2 did not crash. Obviously, there was no X configuration this time. The machine has a Radeon board. Can this be related to 263199 ?

Comment 3 Martin Vidner 2007-04-16 09:14:43 UTC

The last line of the log is "2007-04-12 16:51:30 <1> ppcfactory(3524) [YCP] clients/x11_proposal.ycp:99 Loading library cache..." so I assume that it is indeed just a consequence of the X server crash.

(Hint: writing "bug 263199" instead of "263199" will automatically make
a hyperlink to that bug.)

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