missing alerts from Osmo in upgrade to F15: LXDE spin

[Ranjan Maitra]

Hi,

A month ago, I upgraded from Fedora 14 to Fedora 15 (LXDE spin). I have
been using the LXDE spin since Fedora 12. I use Osmo and find it pretty
adequate for my needs. However, up til Fedora 14, the osmo task manager
(or whatever it is called) would pop up an alert when the time to do a
particular task arrived. This pop-up feature appears to be missing or
has been unwittingly turned off (perhaps by me) in Fedora 15. The
button appears to be checked. How do I get this back?

Please let me know if I am not being clear, or if more information
would be helpful.

Many thanks and best wishes,
Ranjan
-- 
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

[Klaus Lichtenwalder]

Am 15.07.2011 04:33, schrieb Ranjan Maitra:
>  Hi,
>  
>  A month ago, I upgraded from Fedora 14 to Fedora 15 (LXDE spin). I have
>  been using the LXDE spin since Fedora 12. I use Osmo and find it pretty
>  adequate for my needs. However, up til Fedora 14, the osmo task manager
>  (or whatever it is called) would pop up an alert when the time to do a
>  particular task arrived. This pop-up feature appears to be missing or
>  has been unwittingly turned off (perhaps by me) in Fedora 15. The
>  button appears to be checked. How do I get this back?
>   
Ranjan,

it looks like notifications got lost in F15. Same problem in Xfce-based
environments. Probably this is due to the gnome3 migration, but this is
my theory... THere are some entries in diverse bugzillas, but up to now
no solution.

Klaus

-- 
------------------------------------------------------------------------
 Klaus Lichtenwalder, Dipl. Inform.,  http://www.lichtenwalder.name
 PGP Key fingerprint: BF52 72FA 1F5A 1E29 C0F8  498C C4C6 633C 2821 97DA

[Christoph Wickert]

Am Donnerstag, den 14.07.2011, 21:33 -0500 schrieb Ranjan Maitra:
>  Hi,
>  
>  A month ago, I upgraded from Fedora 14 to Fedora 15 (LXDE spin). I have
>  been using the LXDE spin since Fedora 12. I use Osmo and find it pretty
>  adequate for my needs. However, up til Fedora 14, the osmo task manager
>  (or whatever it is called) would pop up an alert when the time to do a
>  particular task arrived. This pop-up feature appears to be missing or
>  has been unwittingly turned off (perhaps by me) in Fedora 15.  
Hi,

thanks for your bug report, I hadn't noticed the problem yet.

The first thing I checked is if osmo is still compiled with notification
support. As you can see fro the build logs at
http://koji.fedoraproject.org/koji/buildinfo?buildID=223744 it still is
(we had some problems there in the past because I missed the libnotify
requirement). So the package *should* work.

Next thing I'd need to check is whether my patch for libnotify 0.7 is
broken. Before I dive deeper into the code I'd like you to test

      * what notification daemon is installed. Please give me the output
        of $ rpm -q notification-daemon xfce4-notifyd
      * what daemon is actually running. Look it up with e.g. 
        $ ps -A | grep notif
      * if you can send messages with
        $ notify-send "Test message"

Regards,
Christoph

[Ranjan Maitra]

Hi Christoph,

Thanks very much for looking into this!

On Fri, 15 Jul 2011 17:45:46 -0500 Christoph Wickert
<christoph.wickert(a)googlemail.com&gt; wrote:

>  Am Donnerstag, den 14.07.2011, 21:33 -0500 schrieb Ranjan Maitra:
>  > Hi,
>  > 
>  > A month ago, I upgraded from Fedora 14 to Fedora 15 (LXDE spin). I have
>  > been using the LXDE spin since Fedora 12. I use Osmo and find it pretty
>  > adequate for my needs. However, up til Fedora 14, the osmo task manager
>  > (or whatever it is called) would pop up an alert when the time to do a
>  > particular task arrived. This pop-up feature appears to be missing or
>  > has been unwittingly turned off (perhaps by me) in Fedora 15. 
>  
>  Hi,
>  
>  thanks for your bug report, I hadn't noticed the problem yet.
>  
>  The first thing I checked is if osmo is still compiled with notification
>  support. As you can see fro the build logs at
>  http://koji.fedoraproject.org/koji/buildinfo?buildID=223744 it still is
>  (we had some problems there in the past because I missed the libnotify
>  requirement). So the package *should* work.
>  
>  Next thing I'd need to check is whether my patch for libnotify 0.7 is
>  broken. Before I dive deeper into the code I'd like you to test
>  
>        * what notification daemon is installed. Please give me the output
>          of $ rpm -q notification-daemon xfce4-notifyd 

$ rpm -q notification-daemon xfce4-notifyd
notification-daemon-0.7.1-1.fc15.x86_64
package xfce4-notifyd is not installed

So, should the xfce4-notifyd be installed?

>        * what daemon is actually running. Look it up with e.g. 
>          $ ps -A | grep notif 

$ ps -A | grep notif
   21 ?        00:00:00 kacpi_notify
   31 ?        00:00:00 fsnotify_mark

>        * if you can send messages with
>          $ notify-send "Test message" 
"nothing" (as far as I can tell) happens....

Many thanks again, and best wishes,
Ranjan

[Christoph Wickert]

Am Samstag, den 16.07.2011, 08:35 -0500 schrieb Ranjan Maitra:
>  Hi Christoph,
>  
>  Thanks very much for looking into this! 
Hi Ranjan,

you are welcome.

>  $ rpm -q notification-daemon xfce4-notifyd
>  notification-daemon-0.7.1-1.fc15.x86_64
>  package xfce4-notifyd is not installed
>  
>  So, should the xfce4-notifyd be installed? 
Nope, either one should suffice.

>  $ ps -A | grep notif
>     21 ?        00:00:00 kacpi_notify
>     31 ?        00:00:00 fsnotify_mark
>  
>  >       * if you can send messages with
>  >         $ notify-send "Test message"
>  
>  "nothing" (as far as I can tell) happens.... 
Yeah, because there is no notification daemon running. It used to be
started by dbus-activation automatically but obviously this is no longer
true. I vaguely seem to remember that it's not needed in gnome-shell,
but they definitely should have notified me of this change. :(

The easiest way to start the daemon again is to run

cp /usr/share/applications/notification-daemon.desktop /etc/xdg/autostart

as root. On the next login you should have notifications again - not
only of osmo but other programs as well.

Please let me know if this fixes your problem.

Regards,
Christoph

[Ranjan Maitra]

Hi Christoph,

Thanks again!

>  Yeah, because there is no notification daemon running. It used to be
>  started by dbus-activation automatically but obviously this is no longer
>  true. I vaguely seem to remember that it's not needed in gnome-shell,
>  but they definitely should have notified me of this change. :(
>  
>  The easiest way to start the daemon again is to run
>  
>  cp /usr/share/applications/notification-daemon.desktop /etc/xdg/autostart
>  
>  as root. On the next login you should have notifications again - not
>  only of osmo but other programs as well.
>  
>  Please let me know if this fixes your problem. 
This did not seem to do anything. Here are the contents of
the /usr/share/applications/notification-daemon.desktop file, btw:

[Desktop Entry]
Name=Notification Daemon
Comment=Display notifications
Exec=/usr/libexec/notification-daemon
Terminal=false
Type=Application
NoDisplay=true

 
I wonder, should that last one be false, not true? I will try it with
that.

Thanks again!
Ranjan

[Ranjan Maitra]

On Sat, 16 Jul 2011 09:44:51 -0500 Ranjan Maitra <maitra(a)iastate.edu&gt;
wrote:

>  Hi Christoph,
>  
>  Thanks again!
>  
>  > Yeah, because there is no notification daemon running. It used to be
>  > started by dbus-activation automatically but obviously this is no longer
>  > true. I vaguely seem to remember that it's not needed in gnome-shell,
>  > but they definitely should have notified me of this change. :(
>  > 
>  > The easiest way to start the daemon again is to run
>  > 
>  > cp /usr/share/applications/notification-daemon.desktop /etc/xdg/autostart
>  > 
>  > as root. On the next login you should have notifications again - not
>  > only of osmo but other programs as well.
>  > 
>  > Please let me know if this fixes your problem.
>  
>  This did not seem to do anything. Here are the contents of
>  the /usr/share/applications/notification-daemon.desktop file, btw:
>  
>  [Desktop Entry]
>  Name=Notification Daemon
>  Comment=Display notifications
>  Exec=/usr/libexec/notification-daemon
>  Terminal=false
>  Type=Application
>  NoDisplay=true
>  
>   
>  I wonder, should that last one be false, not true? I will try it with
>  that.
>   
No, made no difference.....

Ranjan

[Christoph Wickert]

Am Samstag, den 16.07.2011, 09:51 -0500 schrieb Ranjan Maitra:
>  > [Desktop Entry]
>  > Name=Notification Daemon
>  > Comment=Display notifications
>  > Exec=/usr/libexec/notification-daemon
>  > Terminal=false
>  > Type=Application
>  > NoDisplay=true
>  > 
>  >  
>  > I wonder, should that last one be false, not true? I will try it with
>  > that. 
Yes, or removed.

>  No, made no difference..... 
can you send a message with notify-send when you manually
start /usr/libexec/notification-daemon from a terminal?

Regards,
Christoph

[Ranjan Maitra]

>  Yes, or removed.
>  
>  > No, made no difference.....
>  
>  can you send a message with notify-send when you manually
>  start /usr/libexec/notification-daemon from a terminal?
>   
$ /usr/libexec/notification-daemon
** (notification-daemon:31434): DEBUG: Adding id 1

Gdk-CRITICAL **: gdk_visual_get_red_pixel_details: assertion `GDK_IS_VISUAL (visual)'
failed
aborting...
Aborted




Note that the above happens when I go to another terminal and type

$ notify-send "Test message"  

after typing /usr/libexec/notification-daemon in the first.

Ranjan

[Ranjan Maitra]

Hi,

Anything new on this thread?

Many thanks,
Ranjan

On Sat, 16 Jul 2011 10:32:19 -0500 Ranjan Maitra <maitra(a)iastate.edu&gt;
wrote:

>  
>  > Yes, or removed.
>  > 
>  > > No, made no difference.....
>  > 
>  > can you send a message with notify-send when you manually
>  > start /usr/libexec/notification-daemon from a terminal?
>  > 
>  
>  $ /usr/libexec/notification-daemon
>  ** (notification-daemon:31434): DEBUG: Adding id 1
>  
>  Gdk-CRITICAL **: gdk_visual_get_red_pixel_details: assertion `GDK_IS_VISUAL (visual)'
> failed
>  aborting...
>  Aborted
>  
>  
>  
>  
>  Note that the above happens when I go to another terminal and type
>  
>  $ notify-send "Test message"  
>  
>  after typing /usr/libexec/notification-daemon in the first.
>  
>  Ranjan
>

[Christoph Wickert]

Am Samstag, den 06.08.2011, 09:16 -0500 schrieb Ranjan Maitra: 
>  Hi,
>  
>  Anything new on this thread? 
Hi Ranjan,

I'm afraid there are no news. It is a but in notification-daemon and the
bug report at https://bugzilla.gnome.org/show_bug.cgi?id=649588 is still
open.

My only idea at this point is to install xfce4-notifyd instead of
notification-daemon. Install one, then uninstall the other.

Regards,
Christoph

[Ranjan Maitra]

On Mon, 22 Aug 2011 17:52:56 -0500 Christoph Wickert
<christoph.wickert(a)googlemail.com&gt; wrote:

>  Am Samstag, den 06.08.2011, 09:16 -0500 schrieb Ranjan Maitra: 
>  > Hi,
>  > 
>  > Anything new on this thread?
>  
>  Hi Ranjan,
>  
>  I'm afraid there are no news. It is a but in notification-daemon and the
>  bug report at https://bugzilla.gnome.org/show_bug.cgi?id=649588 is still
>  open.
>  
>  My only idea at this point is to install xfce4-notifyd instead of
>  notification-daemon. Install one, then uninstall the other. 
Thanks very much, Christoph! I installed xfce4-notifyd and notification 
works (though not at pretty as the earlier notifications, but will do).
However, when I try to uninstall notification-daemon it takes blueman
down with it (and also gnome-session). Is it ok to erase blueman?

Best wishes,
Ranjan 



>  Regards,
>  Christoph
>  
>  
>  _______________________________________________
>  lxde mailing list
>  lxde(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/lxde
>

[Christoph Wickert]

Am Montag, den 22.08.2011, 21:22 -0500 schrieb Ranjan Maitra: 
>  On Mon, 22 Aug 2011 17:52:56 -0500 Christoph Wickert wrote:
>  
>  > My only idea at this point is to install xfce4-notifyd instead of
>  > notification-daemon. Install one, then uninstall the other.
>  
>  Thanks very much, Christoph! I installed xfce4-notifyd and notification 
>  works (though not at pretty as the earlier notifications, but will do).
>  However, when I try to uninstall notification-daemon it takes blueman
>  down with it (and also gnome-session). 
At least blueman is a bug in the packaging, this should no happen.

>  Is it ok to erase blueman? 
If don't need it, sure. But I suggest to leave notification-daemon
installed since everything works as it should now.

Regards,
Christoph