Your message dated Tue, 1 Apr 2025 21:15:58 +0200
with message-id <[email protected]>
and subject line Re: upower segfault on my ARM laptop
has caused the Debian Bug report #812844,
regarding upower segfault on my ARM laptop
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.)
--
812844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812844
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upower
Version: 0.99.3-1+b3
Severity: important
upower does segfault every time; well the kernel is maybe a bit weird.
It's the ChromeOS one recompiled by the semi-automated Arch bootstrap
to enable features needed by systemd.
systemd[1]: Starting Daemon for power management...
systemd[1]: Started Daemon for power management.
upowerd[2045]: ** (upowerd:2045): CRITICAL **:
dbus_g_connection_register_g_object:
assertion 'g_variant_is_object_path (at_path)' failed
upowerd[2045]: process 2045: arguments to dbus_message_new_signal() were
incorrect,
assertion "_dbus_check_is_valid_path (path)" failed in file
../../dbus/dbus-message.c line 1433.
upowerd[2045]: This is normally a bug in some application using the D-Bus
library.
upowerd[2045]: process 2045: arguments to dbus_message_iter_init_append() were
incorrect, assertion "message !=
NULL" failed in file ../../dbus/dbus-message.c line 2462.
upowerd[2045]: This is normally a bug in some application using the D-Bus
library.
systemd[1]: upower.service: Main process exited, code=killed, status=11/SEGV
systemd[1]: upower.service: Unit entered failed state.
systemd[1]: upower.service: Failed with result 'signal'.
This is the last device opened: (reproducible)
strace -e open -f /lib/upower/upowerd
[pid 2311]
open("/sys/devices/soc0/sound.8/sound/card1/input5/event5/../capabilities/sw",
O_RDONLY|O_LARGEFILE) = 14
Greets,
Alexandre
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (450, 'unstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386
Kernel: Linux 3.10.18-5-ARCH (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF8, LC_CTYPE=fr_BE.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages upower depends on:
ii dbus 1.10.6-1
ii libc6 2.21-6
ii libdbus-1-3 1.10.6-1
ii libdbus-glib-1-2 0.106-1
ii libglib2.0-0 2.46.2-3
ii libgudev-1.0-0 230-2
ii libimobiledevice6 1.2.0+dfsg-2+b1
ii libplist3 1.12-3.1
ii libupower-glib3 0.99.3-1+b3
ii libusb-1.0-0 2:1.0.20-1
ii udev 228-4+b1
Versions of packages upower recommends:
ii policykit-1 0.105-14.1
upower suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
forwarded 812844 https://bugs.freedesktop.org/show_bug.cgi?id=93095
tags 812844 + fixed-upstream
thanks
This is supposedly fixed upstream. So closing the downstream bug report
accordingly.
Thanks for the reference to the upstream bug tracker.
Michael
On Wed, 27 Jan 2016 08:17:27 +0100 Alexandre Detiste
<[email protected]> wrote:
Package: upower
Version: 0.99.3-1+b3
Severity: important
upower does segfault every time; well the kernel is maybe a bit weird.
It's the ChromeOS one recompiled by the semi-automated Arch bootstrap
to enable features needed by systemd.
systemd[1]: Starting Daemon for power management...
systemd[1]: Started Daemon for power management.
upowerd[2045]: ** (upowerd:2045): CRITICAL **: dbus_g_connection_register_g_object:
assertion 'g_variant_is_object_path (at_path)' failed
upowerd[2045]: process 2045: arguments to dbus_message_new_signal() were
incorrect,
assertion "_dbus_check_is_valid_path (path)" failed in file
../../dbus/dbus-message.c line 1433.
upowerd[2045]: This is normally a bug in some application using the D-Bus
library.
upowerd[2045]: process 2045: arguments to dbus_message_iter_init_append() were
incorrect, assertion "message !=
NULL" failed in file ../../dbus/dbus-message.c line 2462.
upowerd[2045]: This is normally a bug in some application using the D-Bus library.
systemd[1]: upower.service: Main process exited, code=killed, status=11/SEGV
systemd[1]: upower.service: Unit entered failed state.
systemd[1]: upower.service: Failed with result 'signal'.
This is the last device opened: (reproducible)
strace -e open -f /lib/upower/upowerd
[pid 2311]
open("/sys/devices/soc0/sound.8/sound/card1/input5/event5/../capabilities/sw",
O_RDONLY|O_LARGEFILE) = 14
Greets,
Alexandre
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (450, 'unstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386
Kernel: Linux 3.10.18-5-ARCH (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF8, LC_CTYPE=fr_BE.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages upower depends on:
ii dbus 1.10.6-1
ii libc6 2.21-6
ii libdbus-1-3 1.10.6-1
ii libdbus-glib-1-2 0.106-1
ii libglib2.0-0 2.46.2-3
ii libgudev-1.0-0 230-2
ii libimobiledevice6 1.2.0+dfsg-2+b1
ii libplist3 1.12-3.1
ii libupower-glib3 0.99.3-1+b3
ii libusb-1.0-0 2:1.0.20-1
ii udev 228-4+b1
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
