Back to bug 68610
Who | When | What | Removed | Added |
---|---|---|---|---|
smcv | 2013-08-27 13:36:13 UTC | Attachment #84714 Attachment is obsolete | 0 | 1 |
smcv | 2013-08-29 10:37:44 UTC | URL | http://cgit.freedesktop.org/~smcv/dbus/log/?h=threadsafe-get-tmpdir-68610 | |
Whiteboard | review? | |||
smcv | 2013-08-29 12:07:20 UTC | Summary | _dbus_get_tmpdir() isn't thread-safe | various thread-safety issues involving static variables |
smcv | 2013-08-29 12:08:02 UTC | URL | http://cgit.freedesktop.org/~smcv/dbus/log/?h=threadsafe-get-tmpdir-68610 | http://cgit.freedesktop.org/~smcv/dbus/log/?h=static-var-safety-68610 |
smcv | 2013-09-02 16:33:08 UTC | Attachment #84715 Attachment is obsolete | 0 | 1 |
Attachment #84830 Attachment is obsolete | 0 | 1 | ||
Attachment #84831 Attachment is obsolete | 0 | 1 | ||
Attachment #84832 Attachment is obsolete | 0 | 1 | ||
Attachment #84833 Attachment is obsolete | 0 | 1 | ||
Attachment #84834 Attachment is obsolete | 0 | 1 | ||
Attachment #84837 Attachment is obsolete | 0 | 1 | ||
smcv | 2013-09-03 12:29:40 UTC | CC | thiago, walters | |
smcv | 2013-09-03 12:29:55 UTC | Attachment #85080 Attachment is obsolete | 0 | 1 |
msniko14 | 2014-09-23 13:56:58 UTC | Priority | medium | highest |
Status | ASSIGNED | RESOLVED | ||
Version | unspecified | 1.5 | ||
Keywords | cleanup0407, i18n, janitor, l10n, security | |||
Hardware | Other | All | ||
CC | msniko14 | |||
Resolution | --- | FIXED | ||
Severity | normal | critical | ||
smcv | 2014-09-23 15:32:20 UTC | Keywords | cleanup0407, i18n, janitor, l10n, security | |
Priority | highest | medium | ||
Status | RESOLVED | REOPENED | ||
Resolution | FIXED | --- | ||
Severity | critical | normal | ||
smcv | 2014-09-24 12:14:06 UTC | Status | REOPENED | ASSIGNED |
smcv | 2014-09-25 14:59:31 UTC | QA Contact | dbus | |
gitlab-migration | 2018-10-12 21:16:49 UTC | Resolution | --- | MOVED |
Status | ASSIGNED | RESOLVED |
Back to bug 68610
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.