Your message dated Sat, 16 May 2020 21:13:09 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-gtkpod-devel] Bug#941703: Bug#941703: 
libimobiledevice6: Crashes upower with stack smashing when connecting an iPhone
has caused the Debian Bug report #941703,
regarding upower: stack smashing detected
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.)


-- 
941703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941703
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upower
Version: 0.99.11-1
Severity: important

Dear Maintainer,

When I plug in my iPhone, upowerd crashed systematically with this in logs:

nov. 06 13:59:23 asp016 systemd[1]: Starting Daemon for power management...
nov. 06 13:59:24 asp016 systemd[1]: Started Daemon for power management.
nov. 06 13:59:29 asp016 upowerd[26386]: *** stack smashing detected ***:
<unknown> terminated
nov. 06 13:59:29 asp016 systemd[1]: Started Process Core Dump (PID 26417/UID
0).
nov. 06 13:59:29 asp016 systemd[1]: upower.service: Main process exited,
code=dumped, status=6/ABRT
nov. 06 13:59:29 asp016 systemd[1]: upower.service: Failed with result 'core-
dump'.
nov. 06 13:59:29 asp016 systemd-coredump[26418]: Process 26386 (upowerd) of
user 0 dumped core.

                                                 Stack trace of thread 26386:
                                                 #0  0x00007f9ca62ed081
__GI_raise (libc.so.6)
                                                 #1  0x00007f9ca62d8535
__GI_abort (libc.so.6)
                                                 #2  0x00007f9ca632edb8
__libc_message (libc.so.6)
                                                 #3  0x00007f9ca63bd80d
__GI___fortify_fail_abort (libc.so.6)
                                                 #4  0x00007f9ca63bd7c2
__stack_chk_fail (libc.so.6)
                                                 #5  0x00007f9ca64ad4b7
idevice_new (libimobiledevice.so.6)

                                                 Stack trace of thread 26388:
                                                 #0  0x00007f9ca63a2d0f
__GI___poll (libc.so.6)
                                                 #1  0x00007f9ca651d09e n/a
(libglib-2.0.so.0)
                                                 #2  0x00007f9ca651d1bf
g_main_context_iteration (libglib-2.0.so.0)
                                                 #3  0x00007f9ca651d211 n/a
(libglib-2.0.so.0)
                                                 #4  0x00007f9ca6545d0d n/a
(libglib-2.0.so.0)
                                                 #5  0x00007f9ca647bfb7
start_thread (libpthread.so.0)
                                                 #6  0x00007f9ca63ad2cf __clone
(libc.so.6)

                                                 Stack trace of thread 26390:
                                                 #0  0x00007f9ca63a80a9 syscall
(libc.so.6)
                                                 #1  0x00007f9ca65683a2
g_cond_wait_until (libglib-2.0.so.0)
                                                 #2  0x00007f9ca64ee4a1 n/a
(libglib-2.0.so.0)
                                                 #3  0x00007f9ca64eea92
g_async_queue_timeout_pop (libglib-2.0.so.0)
                                                 #4  0x00007f9ca65464a9 n/a
(libglib-2.0.so.0)
                                                 #5  0x00007f9ca6545d0d n/a
(libglib-2.0.so.0)
                                                 #6  0x00007f9ca647bfb7
start_thread (libpthread.so.0)
                                                 #7  0x00007f9ca63ad2cf __clone
(libc.so.6)

                                                 Stack trace of thread 26389:
                                                 #0  0x00007f9ca63a2d0f
__GI___poll (libc.so.6)
                                                 #1  0x00007f9ca651d09e n/a
(libglib-2.0.so.0)
                                                 #2  0x00007f9ca651d403
g_main_loop_run (libglib-2.0.so.0)
                                                 #3  0x00007f9ca678a8f6 n/a
(libgio-2.0.so.0)
                                                 #4  0x00007f9ca6545d0d n/a
(libglib-2.0.so.0)
                                                 #5  0x00007f9ca647bfb7
start_thread (libpthread.so.0)
                                                 #6  0x00007f9ca63ad2cf __clone
(libc.so.6)
nov. 06 13:59:29 asp016 systemd[1]: [email protected]:
Succeeded.
nov. 06 13:59:29 asp016 systemd[1]: upower.service: Service RestartSec=100ms
expired, scheduling restart.


How can I help?



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages upower depends on:
ii  dbus               1.12.16-2
ii  libc6              2.29-3
ii  libglib2.0-0       2.62.2-2
ii  libgudev-1.0-0     233-1
ii  libimobiledevice6  1.2.1~git20181030.92c5462-1
ii  libplist3          2.0.1~git20190104.3f96731-1
ii  libupower-glib3    0.99.11-1
ii  libusb-1.0-0       2:1.0.23-1
ii  udev               242-7

Versions of packages upower recommends:
ii  policykit-1  0.105-26

upower suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Version: 1.2.1~git20190921.a9e69b1-1

On Tue, 2019-10-15 at 16:08 +0200, Yves-Alexis Perez wrote:
> On Mon, 2019-10-14 at 18:35 -0500, Diego Escalante Urrelo wrote:
> > Anyway, thanks for your work on this. Let me know if I can help with
> > anything else.
> 
> I'm still waiting for the binNMU or the package from NEW to be accepted,
> unfortunately.

It seems that I forgot to close this one.
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl7AO0YACgkQ3rYcyPpX
RFvvMggAiZMSy2aHPiHWFWJql4H9rurhyiz4PHpf+76C6qs+PtM+45Duk7E8t5VX
h7YdVc8ZQqYWsb+w+fAORi4VL7/HUaSnFfk3aq65/PDA5Uw4mmiCNLHK5nDSSf+1
V3rCH+ZkNHk6mZjb2DujPspkgu1lu8CF6xkvzw/c+02N4UWu3BTJKyVIG67QwJTZ
XkRAcTTs+nXXxWeIRKNvTSDmsJC6uNDe/klAYgmNoBnCPHobDmnffMDRWA8OAJ5A
DO/5vIroyyvmsgOoZao/lw1JxGbtO76ip+0NFAO7oRfG1Pabq3dWQC7js1B1AAHo
fYI1I//62sfq5Ya1MgNZqCR0YX8vog==
=G5Eg
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to