Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Crash with message The default display was not found. #15

Closed
GoogleCodeExporter opened this issue Mar 13, 2015 · 4 comments
Closed

Crash with message The default display was not found. #15

GoogleCodeExporter opened this issue Mar 13, 2015 · 4 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Restart computer with really slow hard disk and lots of background IO
activity.
2. Wait for Growl to auto-start with windows.

What is the expected output? What do you see instead?
Expected Growl to load.
Instead get stacktrace:
Growl.GrowlException: The default display was not found. It is suggested
that Growl be re-installed to restore any missing files.
   at Growl.Controller.LoadDisplays()
   at Growl.Controller.Initialize(String appPath, ISynchronizeInvoke
synchronizingObject)
   at Growl.Program.InitializeApplication()
   at Growl.Program.initializationTimer_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

What version of the product are you using? On what operating system?
2.0.0.20, Windows XP

Please provide any additional information below.
Not sure this will repeat reliably; probably some sort of timing issue.

Original issue reported on code.google.com by eric.zei...@gmail.com on 21 Aug 2009 at 4:09
@GoogleCodeExporter
Copy link
Author 

the exception message "The default display was not found" occurs when the user
preference for the default display to use points to a display that is no longer
available. the display loading happens synchronously and the code that sets the
default also runs synchronously, after the loading, so (at least in theory) as 
slow
harddrive/lots of IO shouldnt affect it.

just as a test, try this:

1. make sure Growl is not running
2. go to '%USERPROFILE%\Local Settings\Application Data\Growl\2.0.0.0\'
3. open the 'user.config' file and find the section for DefaultDisplay - what 
is it
set to?
4. optionally, change the value to Standard (which should always be installed 
and
available), save the file, and restart Growl

let me know if that helps or if you still intermittently get this error.

Original comment by briandun...@gmail.com on 21 Aug 2009 at 8:47

@GoogleCodeExporter
Copy link
Author 

My display is set to Visor.  I'll see if it happens with Standard.

Unfortunately, the error isn't due to a missing display. I can just start Growl
manually and it doesn't seem to happen until next reboot.

Original comment by eric.zei...@gmail.com on 21 Aug 2009 at 9:38

@GoogleCodeExporter
Copy link
Author 

ok - i just thought i would try to rule out the easier solutions first. i will 
take a
look and see if there is some threading stuff going on that could possibly 
cause a
timing issue like this. thanks for replying.

Original comment by briandun...@gmail.com on 22 Aug 2009 at 12:38

@GoogleCodeExporter
Copy link
Author 

this should be fixed in v2.0.2 (2.0.2.8). please try it out and let me know if 
you
are still experiencing the issue.

Original comment by briandun...@gmail.com on 22 Mar 2010 at 5:40

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter