Random Window Closing

Good day all,
I just started using Arch this weekend. Liking the experience of learning and playing so far.
i installed xfce as my de. My problem is that at random times -not usually often but still annoying- the windows I have open will just close on their own leaving me just the desktop background (none) and conky. I have to reopen the windows again and if I didn't save i would lose any changes made to document.
Can anyone shed some light on 1. the cause of this and 2. over a solution or a path to one.
Thanks a mil guys and girls.
Regards.

skunktrader wrote:Maybe the windows are not actually closing. You may have accidentally switched to a different workspace by spinning the wheel on your mouse while the pointer was on the desktop.
Check that by hitting Alt-Tab to step through the open windows; regardless of whether they are on a different desktop.
Also, open a terminal window and launch the GUI app from the terminal. You will get to see the stdout and stderr streams from the program to the terminal.
If none of these suggestions help, we will move on to running a program under gdb to get a core dump

Similar Messages

Random Window Closing When Using Color Labels

Any help appreciated.
When using color labels, every 2nd or 3rd time I set a color, the finder window I'm working in closes by itself. When I reopen a new window, it puts you back at the top level, and I have to re-drill down to where I was. This happens whether or not any apps are open.
Using OS 10.4.8, pretty sure it's the latest version. I have almost no software on this machine - it's a dedicated music computer. I use labels extensively, and this never happened on my old G5 or Powerbook (both with 10.4.8). So far I'm attributing it to the Mac Pro.
Mac Pro/2x2.66 Dual-Core Mac OS X (10.4.8) 4GB RAM
Mac Pro/2x2.66 Dual-Core Mac OS X (10.4.8) 4GB RAM

Create a new account, name it "test" and see how color labels work in that User acct? (That will tell if your problem is systemwide or limited to your User acct.) This account is just for test, do nothing further with it.
Open System Preferences >> Accounts >> "+" make it an admin account.
Let us know and we'll troubleshoot this further.
-mj
[email protected]

How to tell embedded jinitator applet is still running when window closed

Hello, we are trying to accomplish the same thing that is mentioned in this post from Metalink. I've searched for a solution and hope someone here can help. Instead of restating the issue I think David Wilson does a good job of explaining what is needed. Can anyone please suggest a possible solution?
From: David Wilton 07-Oct-05 01:08
Subject: How to tell embedded jinitator applet is still running when window closed
How to tell embedded jinitator applet is still running when window closed
Hi,
We run an oracle 10g forms application through 9iAS over an intranet. All users are running windows 2000 professional.
We run separate frame = true but I would like to switch to separate frame = false
With separate frame = true if the user clicks the outer windows "X" close button (forms mdi window) the user is prompted to save changes before the application ends.
BUT
when using separate frame = false
If the user clicks the upper window "X" button (no longer form mdi window but regular browser window) the window and application is abruptly closed.
I'm interested in using a onbeforeunload function to confirm if the user wants to close the window. This would be placed in the basejini.htm file. This could always ask if the user wants to exit or not. If they click OK then the window closes but if they click "Cancel" you are returned to the forms application exactly where you left. something like event.returnvalue="do you really want to exit?";
However if the user exited using the normal exit form method then the applet is already closed before the onbeforeunoad event fires and there is nothing to go back to and I want the window to close automatically. This is accomplished using close.html file in post forms trigger.
So what I want and what I think many may also want is the check if the embedded applet is still running and if so prompt the user to return to the application or continue to close. Of course If the applet is no longer running then just close because there is no reason confirm closing anymore.
Does anyone have a html/JavaScript solution that can be placed in the jinitiator.htm file? or similar?
Thank you
David
[email protected]
From: Andrew Lenton 07-Oct-05 08:58
Subject: Re : How to tell embedded jinitator applet is still running when window closed
I don't know if this is exactly what you are after but you can add the following to the top of your basejini.htm file and it should prompt the user before exiting the IE window.
<BODY %HTMLbodyAttrs%>
%HTMLbeforeForm%
<SCRIPT>

</SCRIPT>
From: Oracle, mohammed pasha 07-Oct-05 09:55
Subject: Re : How to tell embedded jinitator applet is still running when window closed
David,
Well I could not understand your complete requirement.
Refer to Note.201481.1 How to Close the Browser Window When Closing Forms And How to Simulate SeparateFrame By Javascript
Note.115905.1 How to Close Browser Window When Closing Webforms Applet
Kind Regards,
Anwar
From: David Wilton 07-Oct-05 14:37
Subject: Re : How to tell embedded jinitator applet is still running when window closed
Thank you for your reply and yes you did not understand my question fully.
Sorry if this is a long reply
I am able to close the browser window using information in notes 115905.1 and 201481.1, this is not the issue. We implemented this several years ago. It is workable for both separate frame = true or false.
It is most important to not allow the user to end their forms application by closing the windows browser, they must close using normal form exit commands.
What I want is to have separate frame = false, the big drawback to this option is the user can exit the application and bypass all forms code by pressing the windows "X" close button. This is why we need the code as just provided by Andrew Lenton above in this thread.
BUT Andrew's code will always prompt the user before closing the window and I do not want that. I want the user to be prompted only under scenario 2 listed below.
Here's the 2 case scenario for exiting the application.
1. If the user closes properly and uses exit form which fires all normal form triggers including post_form with it's call to close.html file.
All uncommitted changes are saved or rollback and the users session is ended normally both on the database and in the application server.
All browser windows will close, great all is good. And without Andrew's code the window will close but with Andrew's code the user will be prompted to close or not, if they select Cancel the window will remain but the applet has already ended so why prompt? ...This is what I want to avoid.
2. In the forms app. if the user clicks the windows "X" close button with uncommitted changes. The browser just closes the changes are rollback without prompting the user to save. The users sessions are now lost and still running in the database and application server until they are timed out.
If I use Andrew's code then the user will be prompted to continue to close or go back, if they click Cancel to go back then focus returns to the forms application and the user can continue to work. If the user clicks OK then the window closes and unfortunately their sessions are still lost until timed out.
So what I desire is to add to Andrew's code to check if the embedded applet is still running and prompt the user to close or not accordingly.
Something like:
Basejini.htm like
</HEAD>
<SCRIPT LANGUAGE="JavaScript">
function maximizeWindow()
window.moveTo(0,0);
window.resizeTo(screen.availWidth,screen.availHeight);
function confirm(){
If(document.embeddedapplet.closed())
Win.opener = self;
win.close();
Else if
event.returnValue = "Closing Forms Application. OK to continue?";
</SCRIPT>
<BODY %HTMLbodyAttrs%, onload="maximizeWindow()", onbeforeunload="confirm()">
%HTMLbeforeForm%
I hope this explains my requirements.
David
From: Oracle, Evelene Raechel 10-Oct-05 06:45
Subject: Re : How to tell embedded jinitator applet is still running when window closed
Hi,
Note.199928.1 How to Alert User on Closing Client's Browser Window in Webforms
Regards,
Rachel
From: David Wilton 11-Oct-05 17:40
Subject: Re : How to tell embedded jinitator applet is still running when window closed
I'm sorry this is not helpful at all.
Note 199928.1 is only an alert which does not stop the closing of the window and still displays as an alert if the user does close properly using exit form ... so why would you want to display the alert then?
This is exaclty what I do not want and why I want to determine if the applet is still running before displaying any kind of message.
David
From: Oracle, Evelene Raechel 17-Oct-05 12:23
Subject: Re : How to tell embedded jinitator applet is still running when window closed
Closing thread.
Thanks,

Hello,
I had the same issue last year - wanting to provide a warning on closing the browser, but only if the Forms session is still running. The approach I took is described below, see also the thread where I originally posted this at Closing brower window
Hi there,I've had a similar requirement - or rather, the two conflicting requirements: to warn when the browser is being closed, but for the app to be able to close the browser without a warning being fired.
To always provide a warning when someone (the user or the Forms app) tries to go to a different page (e.g. your close.htm), use Javascript like:
function confirmExit(){
if(appletRunning==true) {
msg="Closing this window or navigating to another page will end your SomeGreatApp session.";
window.event.returnValue=msg;
And make a call to confirmExit() in the onBeforeUnload event of your main page.
You'll notice I first check an 'appletRunning' variable before displaying the warning. This Javascript variable is set to true by my app when it starts up, using an embedded Javabean that calls out to Javascript. Once that variable is set to true, then the warning will be displayed if the user tries to shut the browser by clicking on the 'x' button, or to go to a different URL.
When my app is shutting down, it uses the same Javabean to set appletRunning back to false. It then navigates to a close.htm - which will be done without a warning being displayed.
See Re: How can a Javabean call Javascript function of the basejpi.html?? for example code on how to call Javascript from a bean embedded in your Forms app.
Hope these ideas help you out, it's worked for me (so far, anyway!!)
James

When I open itunes I get a 'DATA EXECUTION PREVENTION' 'Windows closed program'. Can anybody help please.

When open iTunes it starts OK then a message from Windows appears, 'DATA EXECUTION PREVENTION Windows closed program'. Then the whole thing shuts down. Does anybody know how to sort this out please. I am using XP operating system and have recently updated iTunes. Thanks

Hi alanfromharlow,
It sounds as if iTunes is failing to launch properly on your Windows computer. You don’t mention what version of Windows you have, but one of these two articles should be useful to you -
iTunes for Windows Vista, Windows 7, or Windows 8: Fix unexpected quits or launch issues
http://support.apple.com/kb/TS1717
iTunes for Windows XP: Troubleshooting unexpected quits, freezes, or launch issues
http://support.apple.com/kb/TS1421
Thanks for using Apple Support Communities.
Best,
Brett L

Data changes saved when pop-up window closed instead of using Save button/action.

We encountered an odd application behavior and we cannot tell if this is standard functionality or not. When a spec is an a workflow step that is Signature Request, the Requestee can open a link to view the spec. When the user also has edit permissions, they get the edit icon in the popup window. We had a user that editted the spec then decided not to save the changes, so used the Close (red ex on popup) instead of the Action: Cancel button on the application menu. User expected that changes made would not be saved. It turns out that clicking the window closed save the modifications without any warning. User expected Close to work like Cancel instead of Save. Is this normal application behavior?
Details. Version 6.1.1.1 on IE9 with popup.

Did they make a change, close the popup, then workflow the Signature Request? Is so, then this is behavior we expect: When you are viewing a spec, you are viewing the in memory version of it, meaning that if you edit the spec, the changes are made to the in-memory version. If then clicked close, the in memory data is still loaded for that spec, and it may be that the signature request workflow event then saves the spec with those changes. The cancel button would have reverted the changes.
You can, however, log an Enhancement Request for having the window close act like the Cancel.
Thanks
Ron

Window closing error

i written a java program for swing form. the form having default window close button. if i click on close button i displayed a dialog contained Yes-No-Calcel . if i click on cancel it will be exit. How can i stop the window closing.

Look at this codes:
import java.awt.event.*;
import javax.swing.*;
public class ClosingFrame extends JFrame {
     public ClosingFrame() {
          super("Closing frame");
          setDefaultCloseOperation(JFrame.DO_NOTHING_ON_CLOSE);
          addWindowListener(new WindowAdapter() {
               public void windowClosing(WindowEvent e) {
                    int res = JOptionPane.showConfirmDialog(ClosingFrame.this, "Do you want to quit?", "Exit", JOptionPane.YES_NO_OPTION);
                    if (res == JOptionPane.YES_OPTION) {
                         System.out.println("Bye");
                         System.exit(0);
                    else {
                         System.out.println("So you stay!");
          setSize(200,200);
          setLocationRelativeTo(null);
          setVisible(true);
     public static void main(String[] args) {
          new ClosingFrame();
}Denis

Catching window closing events from JFrame

I'm having problems catching windowClosing() events from a JFrame (just doesn't get to my event listener it would seem!).
I register and setup a window listener in the constructor of my JFrame class. Prior to this I set the default close operation as DO_NOTHING_ON_CLOSE (as you're suppose to if tyou want to handle window closing events).
When user clicks on x (window terminate) button (in WIN systems), nothing is dispatched to my event listener. Any ideas?
Extract from constructor:
setDefaultCloseOperation(DO_NOTHING_ON_CLOSE);
addWindowListener(new MainWindowListener(this));
MainWindowListener looks as follows (EDImemConvert extends JFrame):
class MainWindowListener extends WindowAdapter
private EDImemConvert f;
public MainWindowListener(EDImemConvert f)
this.f = f;
public void windowClosing(WindowEvent e)
System.out.println("gets here...");
f.ReturnResources();
f.dispose();
System.exit(0);
}

This works for meimport java.awt.*;
import java.awt.event.*;
import javax.swing.*;
public class Test extends JFrame {
public Test() {
    addWindowListener(new WindowAdapter() {
      public void windowClosing(WindowEvent we) { System.exit(0); }
    setSize(300,300);
    setVisible(true);
public static void main(String args[]) { new Test(); }
}Normally, I just use this line
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
instead of adding a listener. It will clean up everything nicely.

Dispose objects during window closing

I use vb to call java application through batch file (.bat) to connect to another java app to send message. Since the java application is executing in command prompt window, if the window accidentally closed, is it possible to close the connection, terminate loop, dispose objects properly during window closing? most importantly, the program at the other side knows the the connection is closed and message stop sending by the java app? Any suggestion?
Thanks.

Does your app have a fixed main window from where you launch other windows? If so, don't call System.exit(0) in windowClosing event for any of those windows except the main window and it would solve your problem.
Otherwise you would need to somehow keep track of all the open windows in your application and in the windowClosing method you would check to see how many windows are open currently. If the window being closed is the only window open at that time, call System.exit(0). Else don't call it.
Hope this helps.

MacBook Pro, randomly Windows 7 doesn't start and screen goes blank

Hi, I installed Windows 7 (Ultimate 64-bit) using the BootCamp on my MacBook Pro (MBP) i7, mid 2010. Installation was successful without any issues. This is my first Mac and, for now, I primarily use Windows on my MBP. The problem: After selecting Windows OS, randomly, Windows doesn't start and the screen goes blank. When this happens, most of the time I have to press the power button twice and press the Option key again to restart in Windows. Sometimes I have to hold down power button for several seconds to turn off MBP, then power it back on to start over. Windows 7 seems to restart on second try every time.
I can tell when the screen will go blank and Windows will not start, when the blinking cursor does not appear on upper left corner of the screen. Also, I enabled Windows OS Boot Log and nothing displays when this happens.
I took in my MBP, twice, to local Apple store Genius Bar and I was told that it was a Windows problem and I must purchase AppleCare Protection Plan to get help resolving the blank screen. It was explained to me that AppleCare had Windows experts who can help with resolving the issue. Therefore I purchased the AppleCare Protection Plan and spoke to AppleCare directly and still no resolution.
Any help you can provide would be greatly appreciated. Thanks in advance.

There is a forum specifically for Boot Camp, this is a general MBP forum and most of us don't use Boot Camp or Windows. The link to that forum is:
http://discussions.apple.com/category.jspa?categoryID=237
Apple does support Boot Camp however if your problem is with Windows Apple does not support a Microsoft product. You would need to contact Microsoft for help.
Roger

Assignment Window Closed

After insert employer information in assignment window (GOSI Details saudi arabia) the window closed suddenly.
any hints

The problem that i should enter this type of information (GOSI) .
Emp A when i insert GOSI Info and commit form its close .
Emp B if GOSI Info missing i can open Assignment window without any problem.
Also the assignment window in fastpath after serching its close immediataly.
Regards.

Safari crash when window closed

Like the post earlier, safari crashes when a window closed. I used to have Speed Download, however, it is no longer on my system, and when i searched for it (and permutations of it I found nothing.
I tried looking in the crash log, but I dont know what Im looking for.
I would appreciate any further suggestions.
Thanks

Hello Illan Wall and welcome to discussions,
Speed Down Load MUST be removed by using their own un-installer package that comes with it.
Did you do that or did you just trash the Application?
Hope that helps some
Regards
Ian

Detect window closing event in AIR application

How do I detect the window closing event in an AIR app? Tried
the following.
deactivate and windowDeactivate events in the
WindowedApplication tag.
addEventListener(Event.CLOSING, onClose);
addEventListener(AIREvent.APPLICATION_DEACTIVATE onClose);
addEventListener(AIREvent.WINDOW_DEACTIVATE, onClose);
None of them seem to work.
Any ideas?
Thanks
CS

The following works for me:
<mx:WindowedApplication xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute"
closing="traceEvent(event)"
windowDeactivate="traceEvent(event)"
applicationDeactivate="traceEvent(event)">
<mx:Script>
<![CDATA[
public function traceEvent(event:Event):void{
trace(event.type);
]]>
</mx:Script>
</mx:WindowedApplication>
As does:
<mx:WindowedApplication xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute"
applicationComplete="init()">
<mx:Script>
<![CDATA[
import mx.events.AIREvent;
public function init():void{
this.addEventListener(Event.CLOSING, traceEvent);
this.addEventListener(AIREvent.WINDOW_DEACTIVATE,
traceEvent);
this.addEventListener(AIREvent.APPLICATION_DEACTIVATE,
traceEvent);
public function traceEvent(event:Event):void{
trace(event.type);
]]>
</mx:Script>
</mx:WindowedApplication>

How to trap client browser window closing thru JSP or servlets

How to trap client browser window closing thru JSP or servlets?
Gunjan

Hi
Though some JavaScripts may provide you with solutions , yet there is no reliable way to detect the closing of the browser by the servlet. One way to achieve detection of user quitting a session is setting session timeouts ion the server side. This can be done either through the web.xml file or programatically by setting the session.setMaxInactiveInterval().
Good Luck!
Eshwar Rao
Developer Technical Support
Sun microsystems Inc
http://www.sun.com/developers/support

Messages default with texting window closed?

Is there any way I can make Messages default with the Messages texting window closed. I use the ichat features only and the Messages texting window is irritating. Any thoughts...

You can't do this. Close it when you open it

Random Connection Closed Errors using UCP

Hey All;
I am trying to figure out why we are seeing quite a few random connection closed errors in our applications that are using Oracle UCP ver 11.2.0.1.0 connection pooling.
The errors happen at arbitrary jdbc usage source code locations (e.g.: spots that check a connection's auto commit mode, spots that spool through a result set, spots that do yada..) that consume a connection, and are not affiliated with what is being done with the connection (SQL being ran).
The architecture is Tomcat 7, hitting Oracle 10g Enterprise Edition Release 10.2.0.4.0 (RAC). The structure of the code (it's a web app) is such that we have a servlet filter that assigns a http request thread a connection from the pool on an incoming request, then that same connection is closed at the completion of that request's handling. No code uses connections other than code related to handling an http request. And, no threads are spawned off of that request handling thread. And, no code whatsoever (other than the servlet filter's finally block) ever closes a DB connection.
Also, the number of connections in the pool is quite adequate for the usage of the pool. That is, the ceiling is likely never hit. Even if it were---- having an outstanding connection suddenly 'closed out' wouldn't be the proper behavior there.
What are the things that can cause a connection to be 'closed out from under you' ? Meaning, the connection is valid when taken from the pool, but arbitrarily in the middle of usage--- it gets closed.
I am pretty stumped at this point.
Any ideas?
Thanks--

Here are a few sample stacks. Keep in mind that the line of code where the exception actually happens is arbitrary. We see the exception happen at ANY line that is a consumer of a connection. For example... it could happen that it blows up on the 'Nth' iteration while trucking through a result set. Suddenly at say... iteration 143 the connection is suddenly closed out from under the connection's handle.
As far as threads are concerned, each http request that creates a controller servlet instance is assigned it's own connection to use through the handling of that request. That connection instance is assigned as a ThreadLocal instance. Any DB usage that thread has is via that connection. The servlet filter ensures the handle is assigned when the request comes in, then is cleaned up as that request is completely handled in the same filter's finally block (this is a pattern that dozens of web apps we have have been using for going on 10 years now). This is not an ejb app. Straight Tomcat 7 web app using MVC pattern where C is a servlet.
The curious thing here in my mind is that we only have two apps in our collection that are using this new UCP pooling driver (most other are using a tomcat pool). And, only those two are seeing this behavior.
I am not balking at the threads concern--- it's just hard to square that with how we handle threading in such a 'single thread per http request' manner.
And, if it were the case that the pool is handing out the same connection handle to more than one thread because of having multiple entrant threads to the pool accessor method---- it's difficult to buy that it's that common for us to have multiple entrant threads at the same moment in those very short time span it takes for a pool to hand out a connection (given the traffic usage pattern for the app).
Here are the 'known deltas' I am aware of between the two apps that have this behavior, and the couple of dozen we have that do not:
1) these two apps are on Tomcat 7 (most others are Tom 5, Resin, or JBoss)
2) these two apps are using the Ora UCP pool. (most others use Tomcat pool)
~~~~~~~~~ Stack 1 ~~~~~~~~~~~~~~~~~~
01-Dec-2010 12:34:13.479 [ERROR] JDBCExceptionReporter: The connection is closed: The connection is closed
01-Dec-2010 12:34:13.479 [ERROR] PartsGroupingPanel: getDealersInventoryRow() pvid FO03348
org.hibernate.exception.GenericJDBCException: could not inspect JDBC autocommit mode
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:91)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:79)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
at org.hibernate.jdbc.JDBCContext.afterNontransactionalQuery(JDBCContext.java:228)
at org.hibernate.impl.SessionImpl.afterOperation(SessionImpl.java:437)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1134)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at com.dmotorworks.partinventory.dao.ClientParametersDAO.getAllDealers(ClientParametersDAO.java:20)
~~~~~~~~~ Stack 2 ~~~~~~~~~~~~~~~~~~
01-Dec-2010 11:23:54.889 [ERROR] PartsSearchDAO: getDealerInventoryLineItemsNofN()
java.sql.SQLException: The connection is closed: The connection is closed
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:526)
at oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.java:510)
at oracle.ucp.jdbc.proxy.JDBCConnectionProxyFactory.invoke(JDBCConnectionProxyFactory.java:245)
at $Proxy0.prepareStatement(Unknown Source)
at com.dmotorworks.partinventory.dao.PartsSearchDAO.getDealerInventoryLineItemsNofN(PartsSearchDAO.java:246)

Random Window Closing

Similar Messages

Maybe you are looking for