Your message dated Fri, 20 Dec 2019 21:43:35 -0300
with message-id
<CAAfdZj97Mm+0mZZQ3MGm=rp-alg5-sd-+qour8835cyp-lh...@mail.gmail.com>
and subject line Re: iwd: Crash on failed scan request
has caused the Debian Bug report #914433,
regarding iwd: Crash on failed scan request
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
914433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914433
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iwd
Version: 0.12-2~1.gbp11d954
Severity: normal
Hi,
Don't be scared about the version number, it is just my local version
disabling the stacktrace printing. I got a crash on iwd with the
following trace:
(gdb) bt
#0 0x00005650f60e721d in l_dbus_message_new_error_valist (method_call=0x0,
name=0x5650f60ffcd0 "net.connman.iwd.Failed", format=0x5650f60ffcbf "Operation
failed",
args=args@entry=0x7ffdabdc4d60) at ell/dbus-message.c:364
#1 0x00005650f60e732f in l_dbus_message_new_error (method_call=<optimized
out>, name=<optimized out>, format=<optimized out>) at ell/dbus-message.c:388
#2 0x00005650f60a7cf6 in station_dbus_scan_triggered (err=-100,
user_data=0x5650f8032de0) at src/station.c:1970
#3 0x00005650f60b1e25 in scan_request_trigger_failed
(sr=sr@entry=0x5650f803c930, err=err@entry=-100) at src/scan.c:130
#4 0x00005650f60b374c in scan_triggered (msg=<optimized out>,
userdata=0x5650f802d150) at src/scan.c:244
#5 0x00005650f60e0c0e in process_unicast (nlmsg=0x7ffdabdc4f30,
genl=0x5650f802dab0) at ell/genl.c:414
#6 received_data (io=<optimized out>, user_data=0x5650f802dab0) at
ell/genl.c:546
#7 0x00005650f60ddbd3 in io_callback (fd=<optimized out>, events=1,
user_data=0x5650f802dc30) at ell/io.c:126
#8 0x00005650f60dce8d in l_main_iterate (timeout=<optimized out>) at
ell/main.c:389
#9 0x00005650f60dcf5c in l_main_run () at ell/main.c:436
#10 l_main_run () at ell/main.c:418
#11 0x00005650f60dd13b in l_main_run_with_signal (callback=<optimized out>,
user_data=0x0) at ell/main.c:551
#12 0x00005650f609ae2d in main (argc=<optimized out>, argv=<optimized out>) at
src/main.c:509
AFAICT, I did not trigger that scan request, or at least not manually.
I'm using the NM iwd plugin.
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages iwd depends on:
ii libc6 2.27-8
ii libreadline7 7.0-5
iwd recommends no packages.
iwd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Dec 19, 2019, 18:15 Andreas Henriksson <[email protected]> wrote:
> Control: tags -1 + moreinfo
>
> Hello Felipe Sateler,
>
> On Fri, Nov 23, 2018 at 09:25:08AM -0300, Felipe Sateler wrote:
> > Package: iwd
> > Version: 0.12-2~1.gbp11d954
> [...]
> > I got a crash on iwd with the following trace:
> >
> > (gdb) bt
> > #0 0x00005650f60e721d in l_dbus_message_new_error_valist
> (method_call=0x0, name=0x5650f60ffcd0 "net.connman.iwd.Failed",
> format=0x5650f60ffcbf "Operation failed",
> > args=args@entry=0x7ffdabdc4d60) at ell/dbus-message.c:364
> > #1 0x00005650f60e732f in l_dbus_message_new_error
> (method_call=<optimized out>, name=<optimized out>, format=<optimized out>)
> at ell/dbus-message.c:388
> > #2 0x00005650f60a7cf6 in station_dbus_scan_triggered (err=-100,
> user_data=0x5650f8032de0) at src/station.c:1970
> > #3 0x00005650f60b1e25 in scan_request_trigger_failed
> > (sr=sr@entry=0x5650f803c930,
> err=err@entry=-100) at src/scan.c:130
> > #4 0x00005650f60b374c in scan_triggered (msg=<optimized out>,
> userdata=0x5650f802d150) at src/scan.c:244
> [...]
>
> Are you (still) able to reproduce this issue? What's the latest version
> of iwd you've tested?
>
> A number of stability fixes has gone in since the 0.12 release so I'd
> suspect that this issue might have been fixed since. If it's still an
> issue I'd like to know.
>
Indeed, I have not seen this in a while. Should another crash happen I'll
report again.
Saludos
> Regards,
> Andreas Henriksson
>
--- End Message ---
