Activity log for bug #158548
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2007-10-30 03:29:58 | Philip Peitsch | bug | added bug | ||
| 2008-03-20 12:33:49 | Basilio Kublik | network-manager: importance | Undecided | Low | |
| 2008-03-20 12:33:49 | Basilio Kublik | network-manager: status | New | Incomplete | |
| 2008-04-17 19:35:40 | Pedro Villavicencio | network-manager: status | Incomplete | Invalid | |
| 2008-04-21 13:24:23 | Philip Peitsch | network-manager: status | Invalid | New | |
| 2008-05-08 13:48:17 | Basilio Kublik | network-manager: status | New | Incomplete | |
| 2008-05-08 15:21:19 | Philip Peitsch | bug | added attachment 'lspci_syslog_output.tar.bz2' (lspci and syslog output) | ||
| 2008-11-29 18:06:13 | Evan Nelson | bug | added attachment 'syslog_lspci-vvnn.tar.gz' (syslog_lspci-vvnn.tar.gz) | ||
| 2009-01-17 15:29:01 | Martin Mai | network-manager: status | Incomplete | Triaged | |
| 2009-01-17 15:29:01 | Martin Mai | network-manager: statusexplanation | Hi there if you still experience this issue in an up-to-date Hardy Heron system, could you please include your /var/log/syslog file as a separated attachment, just after you experience this problem, also please include the output of the command lspci -vvnn as another attachment. Thanks in advance. | ||
| 2012-10-30 19:18:19 | Thomas Hood | network-manager (Ubuntu): status | Triaged | Fix Released |
