Created attachment 194247 [details]
Xorg.0.log

Created attachment 194248 [details]
Xorg.99.log

Hmm, the logs doesn't lead me to an error. Could you reproduce the
problem if you call the following:

  init 3
  sax2
  --> click on change configuration
  --> click on ok/save

send the newly written /var/log/SaX.log file

Thanks

From command line it happens if i call --> click on change configuration
From GUI it happens after SaX2.It shows me only: SaX2 Importing Data and then nothing (attachced snapshot)

Created attachment 194633 [details]
sax snapshot

Created attachment 194635 [details]
newer SaX log

it looks like it has crashed for some reason. Could you try the
following:

- on your running session type

  /usr/sbin/xapi

does it crash ? if yes could you run the binary in gdb and send a backtrace
it makes sense to have the sax2 debuginfo installed for the following

  gdb /usr/sbin/xapi
  run
  bt

thanks

command /usr/sbin/xapi launched sax2, but after changing resolution i couldn't neither test it nor saved it.
I obtained messages about configuration failures.Attached snapshots.

Created attachment 194770 [details]
saving configuration failed

Created attachment 194771 [details]
testing configuration failed

Created attachment 194773 [details]
the newest xorg log

ah that's ok I guess you called xapi as normal user so you don't
have rights to create xorg.conf. Strange enough I thought the application
would crash

if you call

   su
   /usr/sbin/xapi

but be careful you are now able to write xorg.conf

I tried it as root, but nothing happened.After changing of resolution and monitor i clicked on test or save, but nothing happened.SaX2 was like "frozen".I was able to close it only via System Activity -> Kill Process (Ctrl+Esc)
Just to be sure i've attached the newest sax log

Created attachment 195060 [details]
the newest sax.log

could you run it in gdb to find out which function it calls last ?
I suggest to install the sax2 debuginfo package and after that call

   su root
   gdb xapi
   ---> run
   ---> bt (if the debugger allos you that when it hangs)

by the way _don't_ click on test. This runs another X-Server and could
bite us with searching for the problem at this stage. So use the save
button not the test button

thanks

SaX2 is still frozen after saving.It looks like on attached snapshot.

Created attachment 195769 [details]
attached "frozen" sax

Created attachment 195771 [details]
and here you are output gdb

#0  0xffffe410 in __kernel_vsyscall ()
#8  0xb7ead8b4 in SaX::SaXProcessCall::start () from /usr/lib/libsax.so.7

there must be some process called by sax2 which does not end and
cause the GUI to be in sleep mode. Could you check with

  pstree

what processes runs when sax2 is in that strange state ?

Thanks

(In reply to comment #19 from Marcus Schaefer)
> #0  0xffffe410 in __kernel_vsyscall ()
> #8  0xb7ead8b4 in SaX::SaXProcessCall::start () from /usr/lib/libsax.so.7
> 
> there must be some process called by sax2 which does not end and
> cause the GUI to be in sleep mode. 

I dont't know, but could it be this reason?
When i wanted to save settings of SaX2(clicking on save button), it froze (on attached snapshot "frozen" sax)
So, then i had to kill SaX2 via Ctrl+Esc -> system activity -> kill process -> xapi

Could you check with
> 
>   pstree
> 
> what processes runs when sax2 is in that strange state ?
> 
> Thanks

user@linux-554y:~/Desktop> pstree
init─┬─acpid
     ├─auditd─┬─audispd───{audispd}
     │        └─{auditd}
     ├─avahi-daemon
     ├─avahi-dnsconfd
     ├─console-kit-dae───62*[{console-kit-dae}]
     ├─cron
     ├─cupsd
     ├─2*[dbus-daemon]
     ├─dcopserver
     ├─dhcpcd
     ├─gconfd-2
     ├─hald───hald-runner─┬─hald-addon-acpi
     │                    ├─hald-addon-inpu
     │                    └─2*[hald-addon-stor]
     ├─kaccess
     ├─kded
     ├─kded4
     ├─kdeinit─┬─kio_file
     │         └─klauncher
     ├─kdeinit4─┬─firefox───firefox-bin───6*[{firefox-bin}]
     │          ├─kate───bash───pstree
     │          ├─kio_file
     │          ├─klauncher
     │          └─kwin
     ├─kdesud
     ├─kdm─┬─Xorg
     │     └─kdm───startkde─┬─kwrapper4
     │                      └─ssh-agent
     ├─klipper
     ├─klogd
     ├─kmix
     ├─knetworkmanager
     ├─knotify4───13*[{knotify4}]
     ├─konsole───bash───su───bash───xapi───isax
     ├─krunner───{krunner}
     ├─ksmserver───{ksmserver}
     ├─master─┬─pickup
     │        └─qmgr
     ├─6*[mingetty]
     ├─nscd───8*[{nscd}]
     ├─opensuseupdater
     ├─plasma───{plasma}
     ├─portmap
     ├─powersaved
     ├─resmgrd
     ├─sshd
     ├─syslog-ng
     └─udevd 

─konsole───bash───su───bash───xapi───isax

can you dig into that isax process more detailed ?

ps aux | grep isax

thanks

linux-554y:/home/user # ps aux | grep isax
root      3776 85.2  2.7  40428 35840 pts/3    R+   20:21   0:08 /usr/bin/perl /usr/sbin/isax -f /var/lib/sax/apidata -c /var/lib/sax/xorg.conf
root      3790  0.0  0.0   3044   736 pts/2    R+   20:21   0:00 grep isax

ok, so now we should be able to reproduce it:

1) could you send the file /var/lib/sax/apidata
2) if you manually call:

   /usr/sbin/isax -f /var/lib/sax/apidata -c /var/lib/sax/xorg.conf

   can you see any error messages. The process hands right ?

Created attachment 196803 [details]
/var/lib/sax/apidata

(In reply to comment #23 from Marcus Schaefer)
> ok, so now we should be able to reproduce it:
> 
> 1) could you send the file /var/lib/sax/apidata
> 2) if you manually call:
> 
>    /usr/sbin/isax -f /var/lib/sax/apidata -c /var/lib/sax/xorg.conf
> 
>    can you see any error messages. The process hands right ?
> 
No, i can't see any error.Nothing happens.

oh this is the wrong Modes section bug

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