<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Le 08/08/2012 16:31, Evan Dandrea a écrit : </div> <blockquote cite="mid:CAOe9oG7_ngZmfe1abQ1PwuVpUZHZ0AMMAKhuh8N9EQFw53fWsA@mail.gmail.com" type="cite"> <blockquote type="cite"> <pre wrap="">- password prompts locking your screen because an error happened to a service running with another user than yours </pre> </blockquote> <pre wrap=""> Is this happening automatically, or after you click on something? </pre> </blockquote> It usually happens when a process from another user hits an issue, e.g start a guest session, closing it, you will like have one of those showing in your session <blockquote cite="mid:CAOe9oG7_ngZmfe1abQ1PwuVpUZHZ0AMMAKhuh8N9EQFw53fWsA@mail.gmail.com" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">- we don't know if users make the connection between the issue and those dialogs (what if gedit hits an issue when closing it, then apport takes a minute to process the datas and then you get a dialog ... by the time you moved to something else and wonder wth you get a gedit error when you stopped using it for a minute) </pre> </blockquote> <pre wrap=""> If this is proving to be a problem, I'm sure we can find optimizations to apport in R. Let me know if it is.</pre> </blockquote> I'm not sure how to figure it out, but for sure I see often delay here between an issue and the dialog telling about it <blockquote cite="mid:CAOe9oG7_ngZmfe1abQ1PwuVpUZHZ0AMMAKhuh8N9EQFw53fWsA@mail.gmail.com" type="cite"> <pre wrap=""> </pre> <blockquote type="cite"> <pre wrap="">That would be a good step indeed, we discussed that in the past but that's not easy to do unfortunately and we didn't see so much progress on that front so far but if somebody has good ideas how to do it in an reliable way, or time to work on that, please let us know </pre> </blockquote> <pre wrap=""> Can you elaborate on the discussion that's taken place around this idea? Could we not modify the session manager to write the graphical login and logout (started) time to disk? Then, if a crash occurs between the logout time and login time, we wait to report it until we have a crash that's after the login time. </pre> </blockquote> Some work was done on the past in <a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/ubuntu/+source/apport/+bug/460932">https://bugs.launchpad.net/ubuntu/+source/apport/+bug/460932</a> from the bug "so we reject a crash if: - $DBUS_SESSION_BUS_ADDRESS exists, but we get a d-bus error when trying to connect to it (shutting down session bus) - org.gnome.SessionManager exists on the bus, but the call fails - calling IsSessionRunning() returns false (being shut down)" " - Ignore a crash if gnome-session is running and says that the session is being shut down. These often die because X.org or other services are going away, are usually harmless, and just cause a lot of clutter in bug trackers. (LP: <a title="Do not catch crashes which happen at logout" href="https://bugs.launchpad.net/bugs/460932" class="bug-link">#460932</a>)" It seems that cut a number of those but doesn't cover all the cases, we need somebody to sit down and look at the cases where it's still happening and how we could cover them... (maybe just reject any issue with a timestamp before the session start?) Cheers, Sebastien Bacher </body> </html>