Red Hat Bugzilla – Bug 446883
Last modified: 2008-09-10 03:14:56 EDT
Description of problem:
i launched the application without effect.
so, i tryed to launch the application from terminal and here it is the output i had:
Locale::gettext is not available. This will work, but localization will *not* be
syntax error at /usr/share/dayplanner/dayplanner-daemon line 116, near "SOCK_STREAM
syntax error at /usr/share/dayplanner/dayplanner-daemon line 509, near "SOCK_STREAM
Execution of /usr/share/dayplanner/dayplanner-daemon aborted due to compilation
syntax error at /usr/bin/dayplanner-daemon line 116, near "SOCK_STREAM
syntax error at /usr/bin/dayplanner-daemon line 509, near "SOCK_STREAM
Execution of /usr/bin/dayplanner-daemon aborted due to compilation errors.
*** (Day Planner 0.8.1) Warning: Unable to start daemon!
Died at /usr/bin/dayplanner line 5376.
Krzysztof, please add
and update to 0.9.1 which will fix this crash. TIA!
Krzysztof, any plans?
In order to fix this bug I updated to 0.9.1 now on F-9 and devel. Also
Krzysztof, PLEASE respond to this bug within 2 weeks, otherwise you are
considered missing in action.
dayplanner-0.9.1-1.fc9 has been submitted as an update for Fedora 9
dayplanner-0.9.1-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update dayplanner'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-6625
dayplanner-0.9.1-2.fc9 has been submitted as an update for Fedora 9
dayplanner-0.9.1-3.fc9 has been submitted as an update for Fedora 9
Sorry, but I was on holiday and I hadn't time. I decided to orphane some package:
* dayplanner -- An easy and clean Day Planner
* jabbin -- Instant messaging and VoIP Jabber client
* taskcoach -- Your friendly task manager
If someone is interesting please contact me.
dayplanner-0.9.1-3.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.