| 2008-10-18 05:28:39 |
sonny |
bug |
|
|
added bug |
| 2008-11-11 04:29:45 |
Daniel Hollocher |
jockey: status |
New |
Confirmed |
|
| 2008-11-11 04:29:45 |
Daniel Hollocher |
jockey: statusexplanation |
|
I'm also experiencing this, on a clean and upgraded install of intrepid |
|
| 2008-11-11 04:35:33 |
Daniel Hollocher |
bug |
|
|
added attachment 'jockey.log' (jockey.log) |
| 2008-11-11 12:26:59 |
Daniel Hollocher |
bug |
|
|
added attachment 'jockey.log' (jockey.log) |
| 2008-11-11 12:57:07 |
Daniel Hollocher |
jockey: status |
Confirmed |
New |
|
| 2008-11-11 12:57:07 |
Daniel Hollocher |
jockey: statusexplanation |
I'm also experiencing this, on a clean and upgraded install of intrepid |
well, I tried removing the driver, and removing all downloaded packages, but the bug does not reoccur. So much for tracking it down. |
|
| 2009-02-18 10:14:59 |
Martin Pitt |
jockey: status |
New |
Incomplete |
|
| 2009-02-18 10:14:59 |
Martin Pitt |
jockey: statusexplanation |
well, I tried removing the driver, and removing all downloaded packages, but the bug does not reoccur. So much for tracking it down. |
There is indeed nothing in either log file which would explain this. Instead, the stderr output rather smells like a bug in D-Bus. Did you ever encounter this again? |
|
| 2009-09-30 19:44:26 |
Daniel Hollocher |
removed subscriber Daniel Hollocher |
|
|
|
