Bug 432346 - After Networkmanager upgrade the gnome network/Bluetooth icons dissappear from pannel
After Networkmanager upgrade the gnome network/Bluetooth icons dissappear fro...
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-02-11 09:14 EST by J.Jansen
Modified: 2008-08-02 19:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-11 10:00:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description J.Jansen 2008-02-11 09:14:52 EST
Description of problem:
After upgrade to NetworkManager-0.7.0-0.6.7.svn3235.fc8 the gnome desktop icons
for the network and Bluetooth have disappeared.
The direct-net connection still works and "/usr/bin/nm-tool" just shows the
available networks.
When adding "Network-monitor" to the pannel is displays a "disconnected network"
and when selecting the icon it says : SIOCGIFFLAGS error: no such device

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.upgrade NetworkManager 
2.restart the machine
3.start a gnome session
Actual results:
no Bluetouth and network icons in the panel. The items are not selectable

Expected results:
should display display the icons

Additional info:
Comment 1 Dan Williams 2008-02-11 09:38:58 EST
Can you double-check whether you have a "notification area" applet in your
panel?  Both the BT applet and NM use the notification area to show themselves.
 Try adding another notification area applet, then logging out and back in.
Comment 2 J.Jansen 2008-02-11 10:00:25 EST
You are right the notification area was not present.
I have no idea what caused its removal from the panel.


Note You need to log in before you can comment on or make changes to this bug.