Bug 12416 - mgaapplet crashed (GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files)
Summary: mgaapplet crashed (GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
: 12413 12458 12615 12624 12628 12630 12641 12644 12646 12649 12661 12701 12798 12821 13446 13599 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-01-24 14:08 CET by Stephen Pettin
Modified: 2014-06-27 12:27 CEST (History)
18 users (show)

See Also:
Source RPM: mgaonline-3.8-1.mga4
CVE:
Status comment:


Attachments
The output of lspcidrake command. (3.77 KB, text/plain)
2014-01-24 14:08 CET, Stephen Pettin
Details

Description Stephen Pettin 2014-01-24 14:08:25 CET
Created attachment 4863 [details]
The output of lspcidrake command.

The "mgaapplet" program crashed. Drakbug-16.26.1 caught it.

I was at work and got home this morning and saw this bug information. I'm running Openbox.


GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files at /usr/lib/perl5/vendor_perl/5.18.1/i386-linux-thread-multi/Glib/Object/Introspection.pm line 59.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm:295
Gtk3::__ANON__() called from /usr/bin/mgaapplet:230

Theme name: oxygen-gtk
Kernel version = 3.12.8-desktop586-1.mga4
Distribution=Mageia release 4 (Cauldron) for i586
CPU=Intel(R) Core(TM)2 CPU          4400  @ 2.00GHz
Comment 1 Manuel Hiebel 2014-01-24 15:16:19 CET
*** Bug 12413 has been marked as a duplicate of this bug. ***

CC: (none) => laidlaws

Manuel Hiebel 2014-01-24 15:17:48 CET

Keywords: (none) => Triaged
Assignee: bugsquad => thierry.vignaud

Thierry Vignaud 2014-01-24 18:18:24 CET

Summary: mgaapplet crashed => mgaapplet crashed (GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files)

Comment 2 Doug Laidlaw 2014-01-25 03:15:46 CET
I am completely confused.  I saw an update to mgaonline come down and installed without any problems. (see Bug 12143 Comment 6) 

Now my version of mgaonline is the same as Stephen's, and it is misbehaving.
Comment 3 Colin Guthrie 2014-01-25 12:35:23 CET
Hmm, what desktop are you on?

The .service files mentioned here are actually dbus .service files (these predate the systemd .service files)

Basically what it's saying is that there is no notification daemon running (i.e. some desktops have this built in: GNOME, Cinnamon, Mate, KDE all do IIRC), but others need to run a separate daemon which is activated automatically via dbus.

So:

 1. What desktop?
 2. Does installing "notification-daemon make this problem go away?

CC: (none) => mageia

Comment 4 Doug Laidlaw 2014-01-25 12:57:05 CET
(In reply to Colin Guthrie from comment #3)
> Hmm, what desktop are you on?
> 
> The .service files mentioned here are actually dbus .service files (these
> predate the systemd .service files)
>
Yes, I understood which ones they were
> 
> Basically what it's saying is that there is no notification daemon running
> (i.e. some desktops have this built in: GNOME, Cinnamon, Mate, KDE all do
> IIRC), but others need to run a separate daemon which is activated
> automatically via dbus.
> 
> So:
> 
>  1. What desktop?
      XFCE
>  2. Does installing "notification-daemon make this problem go away?

It is already there: "Package notification-daemon-0.7.6-3.mga4.i586 is already installed."

But it isn't in the output of "ps aux"

And there is no entry for it in the system services enable list.
Comment 5 Colin Guthrie 2014-01-25 13:27:35 CET
It won't appear in the system services enable list as this is not a system service. As mentioned above it's a dbus service, and is unrelated to systemd services.

This is also a *user* daemon, not one run by the system.

What's interesting is that notification-daemon no longer seems to provide a dbus .service file for bus activation.

Anyway, it seems this package conflicts with xfce4-notifyd which is the desktop you're using. Perhaps you should install it instead?

It *does* install a bus-activation file:
/usr/share/dbus-1/services/org.xfce.xfce4-notifyd.Notifications.service
Comment 6 Doug Laidlaw 2014-01-25 13:36:13 CET
Have installed that.  It removed notification-daemon-0.7.6-3.mga4.i586 as conflicting.

Now to test it.  Do I just sit back and wait for updates?
Comment 7 Colin Guthrie 2014-01-25 13:42:33 CET
I guess so. Should be some coming today (new systemd was pushed)
Comment 8 Doug Laidlaw 2014-01-25 16:30:51 CET
The systemd updates just arrived.  The applet ran normally.

So this bug is fixed for me.  Thanks for the quick help.
Comment 9 Colin Guthrie 2014-01-25 17:19:57 CET
Well, there is still some kind of bug somewhere as you were not running a notification agent under xfce which is bad. Lots of things stop working, but it's less of a mgaonline issue and more of a general packaging one.
Comment 10 Doug Laidlaw 2014-01-25 17:33:05 CET
It has probably been going on for some time. Every time I started Totem, I got a dbus message like that.  It isn't there now.

I am wondering where that leaves Stephen, if he isn't running Xfce, but I suppose that isn't my concern.

I occasionally go into KDE, and I may have lost the notification there, but it is unlikely to matter during a brief visit.

I just looked at the Cinnamon desktop.  It installed a different network manager.  They all have a complete setup of their own.  If I had a "pure" Xfce system I would have had the correct notif daemon.
Comment 11 Stephen Pettin 2014-01-25 19:25:30 CET
I've only seen this happen while running Openbox environment. The mgaapplet error message appears when doing nothing. The first time I noticed it I was at work and when I came home, I seen the message.

When running KDE4, I haven't ran across this since upgrading to Mga4. I haven't ran any updates today but do see systemd included in the latest updates.
Comment 12 Colin Guthrie 2014-01-25 19:41:31 CET
The main issue is that nothing is starting a notification daemon on some light-weight desktops. As mentioned above, KDE, GNOME and several others all have such a system running as part of their regular session, but notification-daemon doesn't start itself as it can cause problems.

Long term, the only real solution would be to add an xdg .desktop file to the notification-daemon package which starts it on those desktops known to need it (much like we did with mate-polkit).
Comment 13 Stephen Pettin 2014-01-27 19:04:35 CET
That sounds good for the long term fix. What happens, in my case, when the swap partition changes or any partition UUID changes? Is it a way to fall back to Safe Mode instead of dropping to the console screen with some cryptic error messages? 
Maybe the error message can give a better explanation on how to solve it.

I understand it may take quite a bit to do this and may need more man power also. This is just a suggestion.

Thnx.
Comment 14 Colin Guthrie 2014-01-27 19:31:13 CET
I think this comment was for another bug no? e.g. bug #12305
Comment 15 Stephen Pettin 2014-01-27 19:49:11 CET
(In reply to Colin Guthrie from comment #14)
> I think this comment was for another bug no? e.g. bug #123

oops, sorry. Yes it was in the wrong bug. I see you added it to the correct one.

Thnx.
Comment 16 Thierry Vignaud 2014-01-28 07:32:52 CET
*** Bug 12458 has been marked as a duplicate of this bug. ***

CC: (none) => prodromos_81

Comment 17 Thierry Vignaud 2014-01-28 07:33:02 CET
*** Bug 12456 has been marked as a duplicate of this bug. ***

CC: (none) => andybiker

Comment 18 Marja Van Waes 2014-01-28 17:34:07 CET
just hit the same crash with round 4 classical DVD, 32bits, soon after booting into a newly installed system that didn't fetch updates after install

CC: (none) => marja11

Comment 19 Colin Guthrie 2014-01-28 17:36:17 CET
(In reply to Marja van Waes from comment #18)
> just hit the same crash with round 4 classical DVD, 32bits, soon after
> booting into a newly installed system that didn't fetch updates after install

What desktop? Do you have a notification daemon installed?
Comment 20 Marja Van Waes 2014-01-28 19:17:41 CET
(In reply to Colin Guthrie from comment #19)
> (In reply to Marja van Waes from comment #18)
> > just hit the same crash with round 4 classical DVD, 32bits, soon after
> > booting into a newly installed system that didn't fetch updates after install
> 
> What desktop? Do you have a notification daemon installed?

xfce

a notifications daemon is the thing that give the red round icon with exclamation mark when there are updates? I thought that thing was part of mgaapplet

If yes, then it was undoubtedly installed
Comment 21 Colin Guthrie 2014-01-28 19:25:47 CET
(In reply to Marja van Waes from comment #20)
> (In reply to Colin Guthrie from comment #19)
> > (In reply to Marja van Waes from comment #18)
> > > just hit the same crash with round 4 classical DVD, 32bits, soon after
> > > booting into a newly installed system that didn't fetch updates after install
> > 
> > What desktop? Do you have a notification daemon installed?
> 
> xfce
> 
> a notifications daemon is the thing that give the red round icon with
> exclamation mark when there are updates? 

No, that's just mgaapplet itself.

> I thought that thing was part of mgaapplet

Correct :)

The notification daemon is the thing that displays the actual bubble and has a button inside it.

On XFCE you should have xfce4-notifyd as noted in comment 5. If it's not installed when selecting XFCE, we should add that as a suggest/require of task-xfce.

I've commit this change to svn and requested a push, but if it doesn't make it it's an easy errata.
Comment 22 Marja Van Waes 2014-01-28 20:44:03 CET
(In reply to Colin Guthrie from comment #21)

> 
> On XFCE you should have xfce4-notifyd as noted in comment 5. If it's not
> installed when selecting XFCE, we should add that as a suggest/require of
> task-xfce.
> 
> I've commit this change to svn and requested a push, but if it doesn't make
> it it's an easy errata.

Thx, Colin, it was indeed not installed
Comment 23 Marja Van Waes 2014-01-28 20:45:58 CET
and notification-daemon-0.7.6-3.mga4.i586
 was
Comment 24 Colin Guthrie 2014-01-28 20:52:17 CET
Yeah, problem is with notification-daemon, it no longer provides the files to bus activate by default. It's generally considered bad. All the other DEs will start their preferred notification agent during their session startup, so we should probably do that for xfce4 really, but this is a quick fix.
Comment 25 Thierry Vignaud 2014-01-28 23:11:59 CET
*** Bug 12418 has been marked as a duplicate of this bug. ***

CC: (none) => axonefr

Comment 26 Doug Laidlaw 2014-01-30 18:09:25 CET
I am not sure, but after installing xfce4-notifyd, mgaapplet seems to run only once in each session.  The update frequency is set at 3 hours.
Comment 27 Doug Laidlaw 2014-01-30 18:13:17 CET
To expand on the above, I just ran auto-update and got 12 packages.  My uptime is 6.5 hours.
Comment 28 Mageia Robot 2014-02-04 03:37:52 CET
commit ee9dc74d8eb47c1444072ae1905e0bb69b6aface
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Tue Feb 4 03:37:06 2014 +0100

    fix crashing if there's not notification daemon (mga#12416)
---
 Commit Link:
   http://gitweb.mageia.org/software/mgaonline/commit/?id=ee9dc74d8eb47c1444072ae1905e0bb69b6aface
Comment 29 Thierry Vignaud 2014-02-05 00:29:00 CET
Fixed as of mgaonline-3.10

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 30 Manuel Hiebel 2014-02-05 22:57:14 CET
*** Bug 12615 has been marked as a duplicate of this bug. ***

CC: (none) => klwilcoxon

Comment 31 Manuel Hiebel 2014-02-06 16:38:36 CET
*** Bug 12628 has been marked as a duplicate of this bug. ***

CC: (none) => joebolin

Comment 32 Manuel Hiebel 2014-02-06 16:38:48 CET
*** Bug 12630 has been marked as a duplicate of this bug. ***

CC: (none) => alain

Comment 33 Remco Rijnders 2014-02-07 08:13:31 CET
*** Bug 12644 has been marked as a duplicate of this bug. ***
Comment 34 Remco Rijnders 2014-02-07 08:14:46 CET
*** Bug 12641 has been marked as a duplicate of this bug. ***

CC: (none) => wlyle

Comment 35 Remco Rijnders 2014-02-07 10:02:17 CET
*** Bug 12646 has been marked as a duplicate of this bug. ***

CC: (none) => laurent.protois

Comment 36 Remco Rijnders 2014-02-07 10:37:42 CET
*** Bug 12624 has been marked as a duplicate of this bug. ***

CC: (none) => hageshi_midori

Comment 37 Remco Rijnders 2014-02-07 13:29:28 CET
*** Bug 12649 has been marked as a duplicate of this bug. ***
Comment 38 Manuel Hiebel 2014-02-09 19:54:00 CET
*** Bug 12661 has been marked as a duplicate of this bug. ***

CC: (none) => dennisgrif

Comment 39 Manuel Hiebel 2014-02-10 16:58:49 CET
*** Bug 12701 has been marked as a duplicate of this bug. ***

CC: (none) => christian.volatier

Comment 40 Manuel Hiebel 2014-02-17 17:19:25 CET
*** Bug 12798 has been marked as a duplicate of this bug. ***

CC: (none) => solo-pavel

Comment 41 Thierry Vignaud 2014-02-22 21:59:02 CET
*** Bug 12821 has been marked as a duplicate of this bug. ***

CC: (none) => lebarhon

Comment 42 Manuel Hiebel 2014-05-31 10:25:03 CEST
*** Bug 13446 has been marked as a duplicate of this bug. ***

CC: (none) => en493

Comment 43 Thierry Vignaud 2014-06-27 12:27:23 CEST
*** Bug 13599 has been marked as a duplicate of this bug. ***

CC: (none) => dave


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