Bug 726271

Summary:	Start LSB stopped at SuSEFirewall2 phase 2 in failsafe mode
Product:	[openSUSE] openSUSE 12.1	Reporter:	yu zhang <pswzyu>
Component:	X.Org	Assignee:	E-mail List <xorg-maintainer-bugs>
Status:	RESOLVED NORESPONSE	QA Contact:	E-mail List <xorg-maintainer-bugs>
Severity:	Major
Priority:	P3 - Medium	CC:	meissner
Version:	RC 1
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	I waited about 10mins, nothing happened~ I'm using asus eeepc 1001pxd with a eth card I've never heard. Here is my hwinfo output

Description yu zhang 2011-10-25 01:30:19 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1

I tried connected and disconnected from a wired network , and it always stops at here.
After it is waiting here I can still switch between ttys.

Reproducible: Always

Steps to Reproduce:
1.enter the failsafe mode
2.
3.
Actual Results:  
stop at "Started LSB: SuSEFirewall2 phase 2 ."

Expected Results:  
go through like 11.4 and enter kdm

modprobe vboxguest failed

Comment 1 Ludwig Nussel 2011-10-25 12:19:10 UTC

I doubt this has anything to do with SuSEfirewall2, it's just the last message on screen.

Comment 2 Frederic Crozat 2011-10-25 12:29:09 UTC

what happens if you press "enter" ?

and if you wait two or three minutes ?

Comment 3 yu zhang 2011-10-30 12:13:35 UTC

Created attachment 459454 [details]
I waited about 10mins, nothing happened~ I'm using asus eeepc 1001pxd with a eth card I've never heard. Here is my hwinfo output

I waited about 10mins, nothing happened~
I'm using asus eeepc 1001pxd with a eth card I've never heard.
Here is my hwinfo output

Comment 4 yu zhang 2011-10-30 12:23:28 UTC

I tried pressing enter key just now, the shows "Welcome to openSUSE 12.1RC1........ login :" after (in new lines, but not clearing screen) "Started LSB: SuSEFirewall2 phase 2 ." 
Then I tried to login, and succeeded. But I got into console mode, not X(I think should be kde in failsafed X).

Comment 5 Frederic Crozat 2011-10-31 13:01:37 UTC

looks like X isn't starting

Comment 6 Marcus Meissner 2012-10-04 11:56:12 UTC

any updates? its a year old bug?

Comment 7 Stefan Dirsch 2012-12-12 11:43:01 UTC

Seems this issue has disappeared meanwhile - together with the reporter?