Bug 1297214
Summary: | Xiphos does not launch in Fedora 23 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ervin <ervindiner> |
Component: | gnome-software | Assignee: | Richard Hughes <rhughes> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | ervindiner, klember, pckeving2, rhughes |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-01 15:34:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ervin
2016-01-10 16:40:13 UTC
I forgot to mention that there are two Xiphos packages, one gtk2 and one gtk3. I have not tested the gtk2 package from Yumex. (In reply to Ervin from comment #1) > I forgot to mention that there are two Xiphos packages, one gtk2 and one > gtk3. > I have not tested the gtk2 package from Yumex. Is it plausible the GTK3 one does not work? Well the GTK3 version works, and worked when installed from Yumex. I don't have the option to choose between Gtk2 and Gtk3 in gnome-software so I don't know which package gnome-software installed. Let me know if you need me to do another test. However I think it must be a missing dependency. After upgrading with fedup to fedora 22 Xiphos would not launch. Erased and reinstalled xiphos-gtk3. Still will not launch from menu. Wait icon hangs for 20 seconds then disappears. Does launch from terminal with this error: GConf Error: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. I don't think this is a GNOME Software bug, sorry. |