| 2008-01-23 01:19:11 |
Ross Peoples |
bug |
|
|
added bug |
| 2008-01-30 23:36:30 |
Hans van den Bogert |
network-manager: status |
New |
Confirmed |
|
| 2008-01-30 23:36:30 |
Hans van den Bogert |
network-manager: assignee |
|
gandalf-die-laterne |
|
| 2008-04-15 20:25:37 |
SteBo |
network-manager: assignee |
gandalf-die-laterne |
asac |
|
| 2008-04-24 00:41:37 |
Bryce Harrington |
network-manager: importance |
Undecided |
High |
|
| 2008-04-29 09:20:39 |
Matt Zimmerman |
network-manager: assignee |
asac |
|
|
| 2008-09-10 23:54:25 |
Alexander Sack |
network-manager: bugtargetdisplayname |
network-manager (Ubuntu) |
Ubuntu |
|
| 2008-09-10 23:54:25 |
Alexander Sack |
network-manager: bugtargetname |
network-manager (Ubuntu) |
ubuntu |
|
| 2008-09-10 23:54:25 |
Alexander Sack |
network-manager: statusexplanation |
The bug actually occurred in KDE3, not KDE4. Setting to network-manager since it affects Gnome as well as KDE. |
not a network manager bug. most likely a kde admin or ifupdown issue. |
|
| 2008-09-10 23:54:25 |
Alexander Sack |
network-manager: title |
Bug #185209 in network-manager (Ubuntu): "[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure" |
Bug #185209 in Ubuntu: "[hardy] Manually Configuring Network Causes Massive, Unreversable, Failure" |
|
| 2010-05-20 15:39:23 |
Michael Onnen |
removed subscriber Michael Onnen |
|
|
|
| 2014-02-23 20:30:38 |
P. Mohseni |
removed subscriber P. Mohseni |
|
|
|
