Bug 632278 - incorrect setting in /usr/bin/sunbird
Summary: incorrect setting in /usr/bin/sunbird
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sunbird
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 633083 (view as bug list)
Depends On:
Blocks: 632485
TreeView+ depends on / blocked
 
Reported: 2010-09-09 15:05 UTC by Aram Agajanian
Modified: 2010-12-03 16:50 UTC (History)
6 users (show)

Fixed In Version: sunbird-1.0-0.31.b3pre.fc13
Clone Of:
Environment:
Last Closed: 2010-12-03 16:50:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Corrected Sunbird executable (3.85 KB, patch)
2010-11-06 12:49 UTC, Nathan Thomas 		no flags Details | Diff
View All

Description Aram Agajanian 2010-09-09 15:05:07 UTC 
Description of problem:
incorrect moz_libdir setting in /usr/bin/sunbird

Version-Release number of selected component (if applicable):
sunbird-1.0-0.28.b2pre.fc13.x86_64

How reproducible:
happens every time

Steps to Reproduce:
1. upgrade to sunbird-1.0-0.28.b2pre.fc13.x86_64
2. run sunbird command
3.
  
Actual results:
The following error message is printed on the terminal.

Cannot find Calendar runtime directory. Exiting.


Expected results:
sunbird window should appear and it should run without error.

Additional info:
I found the solution to this in the following forum thread:
http://fedoraforum.org/forum/showthread.php?p=1321911
Comment 1 Jan Kratochvil 2010-09-23 14:40:23 UTC 
*** Bug 633083 has been marked as a duplicate of this bug. ***
Comment 2 Nathan Thomas 2010-11-06 12:49:29 UTC 
Created attachment 458317 [details]
Corrected Sunbird executable

I've attached a corrected /usr/bin/sunbird script that should fix this bug.

Nathan
Comment 3 Jan Kratochvil 2010-12-03 16:50:36 UTC 
It works now in sunbird-1.0-0.31.b3pre.fc13.x86_64:
https://admin.fedoraproject.org/updates/sunbird-1.0-0.31.b3pre.fc13
 - Probably the change there: Wrong library path fixed
Note You need to log in before you can comment on or make changes to this bug.