Bug 1526838 - Osmo needs libnotify support
Summary: Osmo needs libnotify support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: osmo
Version: 27
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Ranjan Maitra
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-17 22:12 UTC by Todd
Modified: 2018-01-16 17:13 UTC (History)
2 users (show)

Fixed In Version: osmo-0.4.2-2.fc26 osmo-0.4.2-2.fc27
Clone Of:
Environment:
Last Closed: 2018-01-16 16:53:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
EL Linux spec file (13.97 KB, text/plain)
2017-12-17 22:12 UTC, Todd
no flags Details

Description Todd 2017-12-17 22:12:51 UTC
Created attachment 1369189 [details]
EL Linux spec file

This is from a conversation with Max Gordienko, Osmo's developer, the Osmo mailing list:

On 12/16/2017 08:44 PM, ToddAndMargo wrote:
>      $ rpm -qa \*osmo\*
>      osmo-0.4.2-1.fc27.x86_64>
>
>      And it beeps a lot with out any of the pop ups.
>      And 'notify-send Test "I'm a test."' does work.
>
 >     What am I doing wrong?  Is Osmo looking for libnotify in the wrong place?

On 12/17/2017 01:08 PM, Max Gordienko wrote:
> It looks like Redhat has build osmo without libnotify support.
> You need to rebuild it from sources with the libnotify-devel package
> installed.
> Otherwise address this with the Fedora package maintainer.
> 
>    Max

Osmo's pop ups are CRITICAL to my business.  I would sincerely appreciate it if you would address this as soon as absolutely possible.

I have attached Nux!'s spec file from his spin for EL Linux where lib notify is supported.


Many thanks,
-T

Comment 1 Todd 2017-12-18 02:29:09 UTC
Panic is over.  You can reduce the priority to Normal.

I rebuild Nux!'s srpm (the spec files I attached) from El Linux 7, where lib notify does work and now I am getting my pop ups perfectly.

Nux!'s srpm:
    https://li.nux.ro/download/nux/tmp/osmo7/

Comment 2 Todd 2018-01-04 01:33:39 UTC
I noticed that this bug, also reported by me, has been ignored since Fedora 25:

https://bugzilla.redhat.com/show_bug.cgi?id=1458685

Please FIX !!!!!

Comment 3 Fedora Update System 2018-01-04 15:13:52 UTC
osmo-0.4.2-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7e0514c1c8

Comment 4 Fedora Update System 2018-01-04 15:14:04 UTC
osmo-0.4.2-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-488af62c30

Comment 5 Fedora Update System 2018-01-05 11:02:11 UTC
osmo-0.4.2-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-7e0514c1c8

Comment 6 Fedora Update System 2018-01-05 11:58:46 UTC
osmo-0.4.2-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-488af62c30

Comment 7 Fedora Update System 2018-01-16 16:53:45 UTC
osmo-0.4.2-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2018-01-16 17:13:18 UTC
osmo-0.4.2-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.