NetworkManager crashed with SIGSEGV in killswitch_getpower_reply() ... g_slice_alloc()

[Atanas Atanasov]

Binary package hint: network-manager

NetworkManager crashed right after I ran udpate-manager. Might be unrelated.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

InterestingModules: b44 ndiswrapper
NonfreeKernelModules: fglrx
Package: network-manager 0.7~~svn20081018t105859-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/NetworkManager
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 g_set_error () from /usr/lib/libglib-2.0.so.0
 dbus_set_g_error ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
 dbus_g_proxy_end_call ()
Title: NetworkManager crashed with SIGSEGV in g_slice_alloc()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups:

WpaSupplicantLog:

[Apport retracing service (apport)]

StacktraceTop:IA__g_set_error (err=0x7fff6de7c848, domain=130, code=32,
dbus_set_g_error (gerror=0x7fff6de7c848, error=<value optimized out>)
dbus_g_proxy_end_call_internal (proxy=0x9f9f50, call_id=<value optimized out>,
dbus_g_proxy_end_call (proxy=0x1, call=0x7fac65e4c810, error=0x1,
killswitch_getpower_reply (proxy=0x9f9f50, call_id=0x1,

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 277185, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[Alexander Sack (asac)]

Charlie, do you have any believe that both are dupes? g_slice_alloc crashes don't indicate a duplicate on its own as its just the function used to allocate memory. This is used everywhere.

[Charlie Kravetz (cjkgeek)]

Alexander, apparently too tired at the time. I thought the stack traces, procmaps compared closely. I did not go by the g_slice_alloc as a search on both launchpad and other bug reporting software showed it to be too wide a search field. Perhaps I mixed up my reports, I´m sorry for duping this one. I´ll work harder at this to get them right next time, and stop at the too tired stage.

[Alexander Sack (asac)]

Charlie, no problem. you are welcome. i just don't know your background. Thus these "simple" hints. Keep up your good work. if you want to help more efficiently on NM bugs feel free to ping me on #ubuntu-bugs or somewhere.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Rolf Leggewie (r0lf)]

I have to say that this bug and bug 277185 *do* look a lot alike, right down to this happening when (dist-)upgrading the system.

[Thomas Hood (jdthood)]

Has anyone seen this bug in Precise or Quantal?

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]