> The UID can actually matter. We have a frequently reported non-bug that > graphical KDE applications will not work (and abort with a qFatal, which > fires the SIGABRT signal) if you run them under tools like su or sudo > because they won't find some resources (usually the D-Bus session service, > sometimes the DISPLAY environment variable for the X display is also lost). > Even the upstream crash handler DrKonqi will then crash, because it is also > a graphical KDE application and runs in the same context, so even if KCrash > is enabled and starts DrKonqi, we still end up with an ABRT report. UID=0 is > a telltale sign that it is likely this issue again, at least it raises a red > flag. (The proper way to run KDE applications as root is to run them under > kdesu.) So actually you're not looking for the UID but whether the application ran as root. That's enough info and I'm Ok with that. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
