banshee r2109 - in trunk/banshee: . ext/hal-sharp src/Core/Banshee src/Core/Banshee.Base/Banshee.Cdrom.Nautilus
- From: abock svn gnome org
- To: svn-commits-list gnome org
- Subject: banshee r2109 - in trunk/banshee: . ext/hal-sharp src/Core/Banshee src/Core/Banshee.Base/Banshee.Cdrom.Nautilus
- Date: Wed, 21 Feb 2007 18:35:16 +0000 (GMT)
Author: abock
Date: 2007-02-21 18:35:15 +0000 (Wed, 21 Feb 2007)
New Revision: 2109
ViewCVS link: http://svn.gnome.org/viewcvs/banshee?rev=2109&view=rev
Modified:
trunk/banshee/ChangeLog
trunk/banshee/ext/hal-sharp/Manager.cs
trunk/banshee/src/Core/Banshee.Base/Banshee.Cdrom.Nautilus/NautilusDriveFactory.cs
trunk/banshee/src/Core/Banshee/banshee.in
Log:
2007-02-21 Aaron Bockover <abock gnome org>
* src/Core/Banshee/banshee.in: Do not use @MONO@, which hard codes the
mono runtime location; just use mono and let the right one be chosen
from PATH - useful when working with parallel mono environments
* src/Core/Banshee.Base/Banshee.Cdrom.Nautilus/NautilusDriveFactory.cs:
Add an explicit null check for HalCore.Manager to get around any potential
SEGV signal issues when throwing NullReferenceException; ensures that
even if HAL isn't available, the app should continue to load, regardless
of signal settings (which determine if SEGV can chain up to
NullReferenceException by being handled by the runtime))
* ext/hal-sharp/Manager.cs: Do the same as the above, plus throw a
more descriptive exception with cute DBus details
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]