Back to bug 19796
Who | When | What | Removed | Added |
---|---|---|---|---|
walters | 2009-02-02 08:43:42 UTC | CC | walters | |
Status | NEW | ASSIGNED | ||
walters | 2009-02-03 11:54:47 UTC | Status | ASSIGNED | RESOLVED |
Resolution | --- | DUPLICATE | ||
purplefloyd | 2009-06-04 06:53:29 UTC | CC | purplefloyd | |
Status | RESOLVED | REOPENED | ||
Resolution | DUPLICATE | --- | ||
purplefloyd | 2009-06-04 12:19:49 UTC | Attachment #22384 Attachment is obsolete | 0 | 1 |
purplefloyd | 2009-06-04 12:20:17 UTC | Attachment #26440 Attachment mime type | application/octet-stream | text/plain |
Attachment #26440 Attachment is patch | 0 | 1 | ||
walters | 2009-07-13 10:17:31 UTC | Status | REOPENED | ASSIGNED |
gicmo | 2010-02-25 15:09:34 UTC | CC | gicmo | |
christian | 2010-05-18 10:01:01 UTC | CC | christian | |
smcv | 2011-01-11 04:10:29 UTC | Whiteboard | threads | |
danny.smit.0 | 2011-06-21 05:18:43 UTC | CC | danny.smit.0 | |
smcv | 2014-09-10 16:56:15 UTC | Summary | dbus_connection_send_with_reply + usage of pending have severe timing issues | dbus_connection_send_with_reply() is not safe if another thread is dispatching the connection |
smcv | 2014-09-10 16:56:26 UTC | Priority | highest | medium |
Severity | blocker | normal | ||
msniko14 | 2014-09-23 13:55:43 UTC | Priority | medium | highest |
Status | ASSIGNED | RESOLVED | ||
Version | 1.2.x | 1.5 | ||
Keywords | cleanup0407, i18n, janitor, l10n, security | |||
Hardware | Other | All | ||
CC | msniko14 | |||
Resolution | --- | FIXED | ||
Severity | normal | critical | ||
smcv | 2014-09-23 14:39:14 UTC | Keywords | cleanup0407, i18n, janitor, l10n, security | |
Priority | highest | medium | ||
Status | RESOLVED | REOPENED | ||
Resolution | FIXED | --- | ||
Severity | critical | normal | ||
smcv | 2014-09-25 14:51:47 UTC | Assignee | hp | dbus |
QA Contact | johnp | dbus | ||
gitlab-migration | 2018-10-12 21:05:42 UTC | Status | REOPENED | RESOLVED |
Resolution | --- | MOVED |
Back to bug 19796
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.