FS#31483 - [sparkleshare] crash at start
Attached to Project:
Community Packages
Opened by Leonardo Ferreira Fontenelle (leonardof) - Sunday, 09 September 2012, 19:43 GMT
Last edited by Balló György (City-busz) - Tuesday, 16 October 2012, 17:24 GMT
Opened by Leonardo Ferreira Fontenelle (leonardof) - Sunday, 09 September 2012, 19:43 GMT
Last edited by Balló György (City-busz) - Tuesday, 16 October 2012, 17:24 GMT
|
Details
Description:
When I launch sparkleshare from GNOME Shell, the messaging tray shows up, but there's no icon in the messaging tray, or application window in any workspace. The only other evidence of SparkleShare having being launched is that the $HOME/SparkleShare folder was created. Launching the terminal emulator, if I run sparkleshare I receive an error message: "SparkleShare is already running." If I run "sparkleshare restart", I receive the following output: [leonardof@fortaleza ~]$ sparkleshare restart SparkleShare is not running, removing stale PID file... Starting SparkleShare... Done. [leonardof@fortaleza ~]$ Location not specified 15:40:58 | Config | Wrote to '/home/leonardof/.config/sparkleshare/config.xml' 15:40:58 | Config | Updated option notifications:True Exception in Gtk# callback delegate Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception. System.NullReferenceException: Object reference not set to an instance of an object at SparkleShare.SparkleSetup+<SparkleSetup>c__AnonStorey9.<>m__72 (System.Object , System.EventArgs ) [0x00000] in <filename unknown>:0 at Gtk.Application+InvokeCB.Invoke () [0x00000] in <filename unknown>:0 at GLib.Timeout+TimeoutProxy.Handler () [0x00000] in <filename unknown>:0 at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal) at GLib.Timeout+TimeoutProxy.Handler() at Gtk.Application.gtk_main() at Gtk.Application.Run() at SparkleShare.SparkleUI.Run() at SparkleShare.Program.Main(System.String[] args) Additional info: * package version(s) - sparkleshare 0.9.2-1 - rest is also up-to-date as of 2012-09-09 * config and/or log files etc. - default configuration. Maybe it's an upstream bug, but I don't think so. Could you please check if it isn't remediable with some change in the packaging? TIA. |
This task depends upon
Closed by Balló György (City-busz)
Tuesday, 16 October 2012, 17:24 GMT
Reason for closing: Fixed
Additional comments about closing: in 0.9.3-2
Tuesday, 16 October 2012, 17:24 GMT
Reason for closing: Fixed
Additional comments about closing: in 0.9.3-2
The config dir has only default settings; removing it doesn't change anything.