Strange, An hour later I can no longer reproduce the problem. I have _not_ logged out/rebooted/etc. So no idea what would have cleared up the problem. Greg On Dec 9, 2007 2:39 PM, Greg Freemyer wrote:

On Dec 9, 2007 2:26 PM, Bryen wrote:

...

On Sun, 2007-12-09 at 14:07 -0500, Greg Freemyer wrote:

...

I find this hard to believe, but I'm able to repeatably lock my GUI (KDE) via oocalc and a simple "file - save as" command.

If I cntrl-alt-F2 and use that console to kill oocalc associated process, everything is working again.

Very strange. Do other people have this problem?

I'm running OO 2.3.0 build 2.3.0.1.3 from the Open Office Build Service.

Greg

I had a similar problem under GNOME that was traced back to the CRUX desktop theme. Once I changed to a different desktop theme, the problem went away. I don't know much about KDE, but if you can change desktop themes, try that and then see if it doesn't lock up anymore.

...

---Bryen---

I'm running the out of the box theme. Haven't yet experimented with that aspect of KDE.

I just did a right-click configure desktop and don't see an easy way to set a theme.

Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf

The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com

-- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, 2007-12-09 at 15:57 -0500, Greg Freemyer wrote:

On Dec 9, 2007 3:28 PM, Volker wrote:

...

I had this problem from the very beginning of my out-of-the-box install and no solution yet.

A couple hours later and my problem disappeared. Hope you figure yours out as well.

To anybody that has the problem ... it is perhaps worth starting ooo from a terminal and seeing if it outputs any diagnostics when things go wrong. It might also be easier to kill it :) Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-12-09 at 20:19 -0500, Patrick Shanahan wrote:

Nope, freezes the X display, all but the mouse pointer :^(

and you cannot recover, even by ssh'ing in and restarting xdm or dropping to runlevel 3 or 1. Only a system restart recovers!

OOo can use some 3D effects: try disabling them. Also, you can choose to use dialogs from OOo or via gnome/kde/whatever: try changing that, switching to the other type of dialog. Those two things have been known in the past to cause problems to OOo. I vote for 3D :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHXJtStTMYHG2NR9URAv9KAJ4/xOfL23PR31F6lHTv31YPXvIt7gCgkI+Y S5YcextovjjT9DDAy3u/wtk= =VgDb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Dec 9, 2007 8:19 PM, Patrick Shanahan wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

* Dave Howorth [12-09-07 19:56]:

...

To anybody that has the problem ... it is perhaps worth starting ooo from a terminal and seeing if it outputs any diagnostics when things go wrong. It might also be easier to kill it :)

Nope, freezes the X display, all but the mouse pointer :^(

and you cannot recover, even by ssh'ing in and restarting xdm or dropping to runlevel 3 or 1. Only a system restart recovers!

- -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org

I run into this problem, only I don't have to restart. I hit ctrl+alt+f1, log in, and su to root. I init 3 and ps my username. I then kill all my username processes. After that is done, I init 5 and I'm back in business. No reboot. After X is back up and running, I can then go back to oocalc and the same thing that locked up X doesn't anymore. I go a couple of days w/o problems with oocalc, then it starts all over. Then I just rinse and repeat. It's a pain. I've tried updating, turning off the use of java. I'll try the suggestion about 3D to see of that helps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 * John (raz0r) [12-10-07 08:20]:

I run into this problem, only I don't have to restart. I hit ctrl+alt+f1, log in, and su to root. I init 3 and ps my username. I then kill all my username processes. After that is done, I init 5 and I'm back in business. No reboot.

I would, but have no keyboard. BUT, ssh from another machine, then restarting xdm or dropping to runlevels 3 or 1 do not unfreeze the display or enable the keyboard. ONLY a system restart recovers. I just reconfirmed above, result was forced restart. BUT, now I can start oocalc (didn't try any others) and work as expected, appears fully functional. go figure ????? one thing, I did uncomment 'noopengl' in /usr/bin/soffice. # Uncomment the line below if you suspect that OpenGL is not # working on your system. SAL_NOOPENGL=true; export SAL_NOOPENGL but I did this prior to the last test which forced a restart. The code should not have any more effect after the restart than prior ?? - -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFHXVjzClSjbQz1U5oRAiX+AJ0TEZFrBpUgl9N5xw2gwCx8L8+LlQCfZKrm 0q4KjB04/uElZWNszFEEiz4= =DETx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Dave Howorth wrote:

On Sun, 2007-12-09 at 15:57 -0500, Greg Freemyer wrote:

...

On Dec 9, 2007 3:28 PM, Volker wrote:

...

I had this problem from the very beginning of my out-of-the-box install and no solution yet.

A couple hours later and my problem disappeared. Hope you figure yours out as well.

To anybody that has the problem ... it is perhaps worth starting ooo from a terminal and seeing if it outputs any diagnostics when things go wrong. It might also be easier to kill it :)

Cheers, Dave

You can store the warning/error messages with oocalc &> oocalc.log Also, try running it with strace, e.g. strace -f oocalc &> oocalc.strace.log You might get a clue about the cause in the log file. The OOo messages will be in there too, with more context. Oh, and IME Beagle is a dog, at least under 10.2 There's a clue in the name ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, 2007-12-09 at 15:57 -0500, Greg Freemyer wrote:

On Dec 9, 2007 3:28 PM, Volker wrote:

...

Am Sonntag, 9. Dezember 2007 20:07:46 schrieb Greg Freemyer:

...

I find this hard to believe, but I'm able to repeatably lock my GUI (KDE) via oocalc and a simple "file - save as" command.

If I cntrl-alt-F2 and use that console to kill oocalc associated process, everything is working again.

Very strange. Do other people have this problem?

I'm running OO 2.3.0 build 2.3.0.1.3 from the Open Office Build Service.

Oddly enough, now I am seeing a problem that might be related...

I don't use KDE much, but my wife does, and when she logs on, the system seems to "hang" for several (5-7) minutes after saving a web page in Firefox, or a spreadsheet in OO. So much so that if she logs off her session, it appears the X-server has died. (no NumLoc key, etc.). I ssh'd in and Beagle was eating my entire CPU... Three times now, by the time I walked back into this room, KDM had finally returned to allow me to log on. I then checked, and Beagle was idle... So I retract my earlier post that OO was working fine for me...I wasn't using it in KDE. I wonder if Beagle is getting a "lock" on the scheduler? More checking here required! Tom in NM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org