-
Notifications
You must be signed in to change notification settings - Fork 52
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
Module Manager problems in 4.0.7 (Ubuntu Linux) #831
Comments
Same issue with the xiphos from ppa. |
The doubled up/down spinners happens on Windows too. See #829 |
the doubled arrows have been fixed (#829, #877). |
closing this for now, lacking specific information about what could go wrong here. if a concrete repeat-by can be offered in the future, this can be re-opened and analyzed. |
Did a compete removal of previous Xiphos version (4.0.4 from Ubuntu) and installed 4.0.7 from the Crosswire ppa, Started Xiphos from a terminal in Ubuntu 16.04, select Edit->Module Manager, select Module Sources->Add/Remove, select Load Standard button. Application locks for about 30 seconds, then opens a Xiphos message window stating, "Could not load standard sources from CrossWire." Close message window, close Module Manager, application locks up. Messages in the terminal I had opened Xiphos in states, "Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged." and "(xiphos:29952): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed". Xiphos locks when I try to close it with a message, "This window is not responding, Do you want to force the application to exit, or wait for it to respond?" Xiphos must be forced to quit. Even without trying to do anything in the Module Manager (i.e. simply opening it and closing it), the Xiphos application will lock up and must be forced to quit as described.
Additional observation: Upon opening Xiphos, the Book, Chapter and Version spinner controls each display double up/down arrows. Moving the mouse cursor over the spinners reduces them down to single spinners. Might not be related, but could be a GUI pointer lost somewhere.
The text was updated successfully, but these errors were encountered: