Bug 598782 – sys-power/upower-0.99.4: Program received signal SIGSEGV, Segmentation fault.

• Product: Gentoo Linux
• Status: RESOLVED UPSTREAM

[Description Alexandr Tiurin 2016-11-02 13:28:23 UTC]

gdb --args upower -d
GNU gdb (Gentoo 7.10.1 vanilla) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from upower...Reading symbols from /usr/lib64/debug//usr/bin/upower.debug...done.
done.
(gdb) run
Starting program: /usr/bin/upower -d
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff5d9f700 (LWP 18466)]
[New Thread 0x7ffff559e700 (LWP 18467)]

(upower:18462): libupower-glib-WARNING **: Couldn't connect to proxy: Error calling StartServiceByName for org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.freedesktop.UPower: Permission denied

(upower:18462): GLib-GIO-CRITICAL **: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7bbe327 in up_client_get_devices (client=client@entry=0x614620) at up-client.c:102
102     up-client.c: No such file or directory.
(gdb) bt
#0  0x00007ffff7bbe327 in up_client_get_devices (client=client@entry=0x614620) at up-client.c:102
#1  0x00000000004016f8 in main (argc=1, argv=0x7fffffffded8) at up-tool.c:312


Reproducible: Always

Steps to Reproduce:
upower -d
Actual Results:  
upower -d

(upower:18489): libupower-glib-WARNING **: Couldn't connect to proxy: Error calling StartServiceByName for org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.freedesktop.UPower: Permission denied

(upower:18489): GLib-GIO-CRITICAL **: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
zsh: segmentation fault  upower -d

[Comment 1 Alexandr Tiurin 2016-11-02 13:29:21 UTC]

Created attachment 452176 [details]
emerge --info

[Comment 2 Lara Maia 2017-03-09 18:36:46 UTC]

I think we do not have to worry about this bug. The error occurs because dbus-daemon was not started. The default dbus services on openrc and systemd are okay, so this was caused by some exoteric configuration.

See:

lara@Amora ~ $ killall -15 dbus-daemon
lara@Amora ~ $ upower -d

(upower:798): libupower-glib-WARNING **: Couldn't connect to proxy: Could not connect: No such file or directory

(upower:798): GLib-GIO-CRITICAL **: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Segmentation fault
lara@Amora ~ $ sudo mkdir -p /var/run/dbus && sudo dbus-daemon --system --nopidfile
lara@Amora ~ $ upower -d
Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply:         no
  updated:              Thu Mar  9 15:18:37 2017 (0 seconds ago)
  has history:          no
  has statistics:       no
  unknown
    warning-level:       none
    icon-name:          ''

Daemon:
  daemon-version:  0.99.4
  on-battery:      no
  lid-is-closed:   no
  lid-is-present:  no
  critical-action: (null)
lara@Amora ~ $ 

It is still a bug, but does not affect the normal operation of upower or other programs

[Comment 3 Pacho Ramos 2017-06-18 09:09:40 UTC]

Then, please report this directly to upstream to also know if they are willing to support that strange setup :/
https://bugs.freedesktop.org