Bug 419157 - sax2: YaST2 keyboard module blanks screen
Summary: sax2: YaST2 keyboard module blanks screen
Status: RESOLVED DUPLICATE of bug 389072
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Factory
Hardware: Other Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-21 11:33 UTC by Karl Eichwalder
Modified: 2008-08-27 02:35 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Eichwalder 2008-08-21 11:33:05 UTC
The YaST CC (gtk flavor) in Gnome is running.  If I click "Keyboard Layout", the screen blanks for 1-2 seconds, then SaX2 starts.  Is it possible to avoid this screen blanking?  I think this did not happen in the past.
Comment 1 Stefan Dirsch 2008-08-21 11:40:07 UTC
I'm afraid, that's not possible. Marcus?
Comment 2 Marcus Schaefer 2008-08-21 13:23:37 UTC
I'm sorry for detection purposes an X Server needs to be started in order
to get a display to access the randr extension data. The screen blank in
that situation seems not avoidable
Comment 3 Karl Eichwalder 2008-08-21 13:45:41 UTC
So we must display a warning, pleaseg, before actually trying the detection.

I just tried again and the detection takes longer the several seconds.  The the innocent user it could look like a hardware crash.
Comment 4 Stefan Dirsch 2008-08-21 14:35:05 UTC
(In reply to comment #2 from Marcus Schaefer)
> I'm sorry for detection purposes an X Server needs to be started in order
> to get a display to access the randr extension data. The screen blank in
> that situation seems not avoidable

But we don't need this RANDR extension data for changing keyboard only configuration. We're talking about the YaST2 keyboard module, which
starts the SaX2 keyboard module directly. Marcus?


Comment 5 Marcus Schaefer 2008-08-21 14:38:24 UTC
Stefan the initial detection process doesn't make a difference between
keyboard or monitor. It detects everything and stores that. If you call
sax2 or yast2 from a running X11 session it also will not re-detect but
just read that cached information. In that case there is also no screen
blanking. Only on first call or when called from a text console the
detection runs again
Comment 6 Stefan Dirsch 2008-08-21 14:50:40 UTC
(In reply to comment #5 from Marcus Schaefer)
> Stefan the initial detection process doesn't make a difference between
> keyboard or monitor. It detects everything and stores that. 

Ok. This is what I expected.

> If you call
> sax2 or yast2 from a running X11 session it also will not re-detect but
> just read that cached information. In that case there is also no screen
> blanking. Only on first call or when called from a text console the
> detection runs again

For me the detection always runs - from a running X11 session. :-( No matter
if I start a YaST2-x11 module or SaX2 itself.

~> sax2
SaX: root Password: 
SaX: initializing please wait...
SaX: your current configuration will not be read in

<<< VTswitch to linux console; Xserver probing; VTswitch back to X >>>

SaX: access to your display has been granted
SPP: prepare device [0] profile: Depth24
SPP: prepare device [0] profile: Intel
SPP: calling device [0] profile script: Intel
SPP: prepare device [0] profile: AIGLX
SPP: prepare device [0] profile: Composite
SPP: prepare device [0] profile: Virtual2k
SPP: prepare device [1] profile: synaptics
SPP: including prepared profile(s)...
SPP: prepare device [0] profile: nobus
SPP: including prepared profile(s)...

SaX: startup
SaX: X-Server: :0.0 -> grant
SaX: using cache data...
Comment 7 Stefan Dirsch 2008-08-27 02:35:39 UTC
This issue becomes obsolete with the proposal in Bug #389072, comment #9.

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