wifi-radar crashed with SIGSEGV in gdk_window_enable_synchronized_configure()

[Williams Christ]

Binary package hint: wifi-radar

Wifi-radar crashes each time I start up Ubuntu 9.10

information:

wifi-radar:
  Installiert: 2.0.s05-1
  Kandidat: 2.0.s05-1
  Versions-Tabelle:
 *** 2.0.s05-1 0
        500 http://de.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Nov 1 21:47:45 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/sbin/wifi-radar
InterpreterPath: /usr/bin/python2.6
Package: wifi-radar 2.0.s05-1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -OO /usr/sbin/wifi-radar -d
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x23449d <gdk_window_enable_synchronized_configure+29>: mov 0xc(%edi),%esi
 PC (0x0023449d) ok
 source "0xc(%edi)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: wifi-radar
StacktraceTop:
 gdk_window_enable_synchronized_configure ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_cclosure_marshal_VOID__VOID ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: wifi-radar crashed with SIGSEGV in gdk_window_enable_synchronized_configure()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

[Rick (rickledford)]

I "opened" the menu for the wireless icon with a left click just after boot (within seconds of the icon appearing after login). The icon indicated that the wireless network was already active. The crash occurred just after I closed the menu and opened the audio adjustment menu next to it.

[rafe (rafe1980)]

The crash happened immediately for me, without clicking the icon. Actually, the tray icon never even appeared. No wifi networks had been configured yet, so it may have been trying to display a dialog for configuration purposes.

[ottosykora (ottosykora)]

After able to clear the first problem by deleting the log file from the old version, now next problem as here.
It starts this time, but crashes soon therafter.

[Rick (rickledford)]

I left my computer running all day. When I returned home in the evening I found this crash report active.

[ottosykora (ottosykora)]

Now starts crashing when running , just so , no obvious reasons or when attempt made to close the wifi-radar.

[Josh (satish-joshi)]

After able to clear the first problem by deleting the log file from the old version, now next problem as here.
It asked me password for a connection. Crashed when I clicked cancel.

[Bill Milman (bill-milman)]

I was able to clear the first problem by deleting the log file from the old version after a remove and reinstall, now the problem is here.
It crashes on soon after startup.

[Sean Robinson (seankrobinson)]

I'm not sure this is directly related to WiFi Radar (it may or may not). If you uninstall WiFi Radar and reboot, does anyone still get this crash? (Meaning that the crash is not caused by WiFi Radar.)

[Ivar Snaaijer (ivar-snaaijer)]

In my case it seems to be relalted with a crash of the router, i need to restart it before it works again. (possible relation with bug #475193 , for which i spoke too soon)

[coco (costantino-gualano)]

this happens on start-up, since I installed karmic

[Rick (rickledford)]

This happens on startup since I installed Ubuntu 10.4

[Sean Robinson (seankrobinson)]

Looking back through this bug history, I am guessing that no one reporting is really using WiFI Radar. I believe that Network Manager is being used for network connections and WiFi Radar is crashing as it tries to compete for the wireless hardware. Can anyone seeing this crash confirm that they are using WiFI Radar for wireless connections?

Just as a note, WiFi Radar and Network Manager do not play well together as they both try to accomplish the same tasks. Think of it like trying to edit one spreadsheet file with OpenOffice Calc and KSpread at the same time, something is going to go wrong. So, I recommend only using one wireless connection manager. Of course, I recommend WiFi Radar, but YMMV.