On Wednesday 10 September 2014 04:19 PM, Laurent Bigonville wrote:
Le Wed, 10 Sep 2014 12:04:13 +0530,
Ritesh Raj Sarraf<r...@researchut.com> a écrit :
>On Tuesday 09 September 2014 05:34 PM, Laurent Bigonville wrote:
> >Well I guess using a daemon is more generic and indeed more flexible
> >(not sure using a systemd/upstart user job will work for system
> >crash report).
>The whole reason of using a daemon was to not be bound by any single
>software and be self-independent.
>
> >Will you look at it?
>Yes. I am.
>
Thanks! My (system) C skills are quite rusty I must admit:)
I just uploaded -3 build to experimental. In this build, apport-notifyd
should be better at tracking the inotify events. For now, based on my
tests, I'm only acting on IN_CREATE event (see manpage for details and
the git commit log for my reasoning). With this build, apport-notifyd
should be able to track and pop-up apport on crash events.
There's one catch though. Applications that crash during OS boot up
until apport-notifyd is started, they will not get tracked. My plan is
to later add some code in the daemon to, upon startup, look at any crash
reports that were generated.
Some time back you mentioned that root reports were not being tracked by
apport. That should not be the case. When apport sees a report from a
different uid, it triggers gksu. That'd mean we need to add gksu/kdesudo
to Recommends for apport. Can you test it ?
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
