Bug 1168104

Summary:	Menu item Device missing in kstars
Product:	[Fedora] Fedora	Reporter:	andha
Component:	kstars	Assignee:	Than Ngo <than>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	20	CC:	jreznik, kevin, ltinkl, lupinix.fedora, rdieter, rnovacek, than
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kstars-4.14.3-1.fc20.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-06 02:38:08 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:
Bug Depends On:	1169089
Bug Blocks:

Description andha 2014-11-26 07:01:29 UTC

Description of problem:
When starting kstars on a Fedora 20 system, the menu item
Device is missing.

Version-Release number of selected component (if applicable):
Kstars 2.2.0 running on KDE 4.14.3

How reproducible:
Every time

Steps to Reproduce:
1. Start kstars
2. Check for menu item Device
3.
  
Actual results:
Not found

Expected results:
Should be there. Can't communicate with telescope without it.

Additional info:
A similar problem occurred in Fedora 13. See bugzilla bug 640522

Comment 1 Kevin Kofler 2014-11-30 07:26:07 UTC

KStars now wants libindi 0.9.8, we only have 0.9.6 in F20.

We're also missing a BuildRequires: pykde4, and astrometry.net which is probably not packaged yet.

Comment 2 Kevin Kofler 2014-11-30 07:40:10 UTC

(Actually, for pykde4, there's already a runtime Requires, which is probably sufficient, it's the usual "runtime requirements checked at build time" nonsense.)

I filed bug #1169089 against libindi requesting a libindi upgrade on Fedora 20. I hope we can get that, or I'll have to figure out how to make this work with the old version.

Comment 3 Christian Dersch 2014-11-30 11:01:27 UTC

astrometry.net is not yet packaged. It is useful for an alignment of the telescope. KStars provides online and offline plate solving, for the offline solving you need astrometry.net with a huge set of catalog data (>20GB for a common Celestron C8 telescope) to get it working well. For the online solving you just need some kind of internet connection.

Comment 4 Kevin Kofler 2014-12-01 01:24:28 UTC

Looks like Rex Dieter's simple CMakeLists.txt hack to build against 0.9.6 would have worked, but we're now preparing a grouped update with libindi 0.9.9 and rebuilt indi-apogee and kstars. The kstars build is here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=8267033

Comment 5 Fedora Update System 2014-12-01 06:26:48 UTC

kstars-4.14.3-1.fc20.2,indi-apogee-1.0-14.fc20.1,libindi-0.9.9-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/kstars-4.14.3-1.fc20.2,indi-apogee-1.0-14.fc20.1,libindi-0.9.9-1.fc20

Comment 6 Fedora Update System 2014-12-03 01:03:44 UTC

Package kstars-4.14.3-1.fc20.2, indi-apogee-1.0-14.fc20.1, libindi-0.9.9-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kstars-4.14.3-1.fc20.2 indi-apogee-1.0-14.fc20.1 libindi-0.9.9-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-16108/kstars-4.14.3-1.fc20.2,indi-apogee-1.0-14.fc20.1,libindi-0.9.9-1.fc20
then log in and leave karma (feedback).

Comment 7 andha 2014-12-04 17:54:30 UTC

Menu items are now back and seems to work,

Comment 8 Kevin Kofler 2014-12-04 20:34:32 UTC

Please do not close the bug before the update actually hits the stable updates repository. The Fedora update system (Bodhi) will close it automatically.

Comment 9 Fedora Update System 2014-12-06 02:38:08 UTC

kstars-4.14.3-1.fc20.2, indi-apogee-1.0-14.fc20.1, libindi-0.9.9-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.