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
*** Bug 12413 has been marked as a duplicate of this bug. ***
CC: (none) => laidlaws
Keywords: (none) => TriagedAssignee: bugsquad => thierry.vignaud
Summary: mgaapplet crashed => mgaapplet crashed (GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files)
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.
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
(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.
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
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?
I guess so. Should be some coming today (new systemd was pushed)
The systemd updates just arrived. The applet ran normally. So this bug is fixed for me. Thanks for the quick help.
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.
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.
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.
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).
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.
I think this comment was for another bug no? e.g. bug #12305
(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.
*** Bug 12458 has been marked as a duplicate of this bug. ***
CC: (none) => prodromos_81
*** Bug 12456 has been marked as a duplicate of this bug. ***
CC: (none) => andybiker
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
(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?
(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
(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.
(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
and notification-daemon-0.7.6-3.mga4.i586 was
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.
*** Bug 12418 has been marked as a duplicate of this bug. ***
CC: (none) => axonefr
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.
To expand on the above, I just ran auto-update and got 12 packages. My uptime is 6.5 hours.
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
Fixed as of mgaonline-3.10
Status: NEW => RESOLVEDResolution: (none) => FIXED
*** Bug 12615 has been marked as a duplicate of this bug. ***
CC: (none) => klwilcoxon
*** Bug 12628 has been marked as a duplicate of this bug. ***
CC: (none) => joebolin
*** Bug 12630 has been marked as a duplicate of this bug. ***
CC: (none) => alain
*** Bug 12644 has been marked as a duplicate of this bug. ***
*** Bug 12641 has been marked as a duplicate of this bug. ***
CC: (none) => wlyle
*** Bug 12646 has been marked as a duplicate of this bug. ***
CC: (none) => laurent.protois
*** Bug 12624 has been marked as a duplicate of this bug. ***
CC: (none) => hageshi_midori
*** Bug 12649 has been marked as a duplicate of this bug. ***
*** Bug 12661 has been marked as a duplicate of this bug. ***
CC: (none) => dennisgrif
*** Bug 12701 has been marked as a duplicate of this bug. ***
CC: (none) => christian.volatier
*** Bug 12798 has been marked as a duplicate of this bug. ***
CC: (none) => solo-pavel
*** Bug 12821 has been marked as a duplicate of this bug. ***
CC: (none) => lebarhon
*** Bug 13446 has been marked as a duplicate of this bug. ***
CC: (none) => en493
*** Bug 13599 has been marked as a duplicate of this bug. ***
CC: (none) => dave