Wow, I'm so pleased I was able to help. I used to work for Global
Product Support at Silicon Graphics, and this reminds me of how much I
enjoyed that job :) Now I do web application development, which can be
pleasing at times too.
--
You received this bug notification because you are a member of
Dear Max
You nailed it! Your last suggestion regarding gnome-settings-daemon and
unity-settings-daemon was pointing me to the right direction. I indeed
was running gnome-settings-daemon and the problem disappears when
running unity-settings-daemon instead.
I'm running fluxbox as window manager
Hrm. It's almost like it's not really the same issue (particularly not
the same *cause*).
Can you check that upowerd is actually running? :
$ ps faux | grep upowerd
maxw 4799 0.0 0.0 21296 932 pts/1S+ 10:38 0:00
\_ grep --color=auto upowerd
root 2515 0.0
Thanks, Max, for all the suggestions. Don't be sorry for giving clues...
* While I trigger the error, nothing is written to /var/log/syslog. Also
there is no indication of 'error while loading shared libraries'.
* I looked for any binary in /usr/bin/ and /bin that might is linked to
something in
Is it upowerd that is crashing or something else? I think I noticed
messages in /var/log/syslog. That might identify some other binary that
is failing to load - perhaps grep the logs for 'error while loading
shared libraries'?
Alternatively, you could try ldd on all the binaries in /usr/bin and
Thanks for the suggestion. I cannot spot anything 'unusual' in the
output. Or is there?
ldd -r /usr/lib/upower/upowerd
linux-gate.so.1 => (0xb77ed000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb7725000)
libupower-glib.so.3 =>
I would do :
[~]$ ls -l /usr/lib/upower/upowerd
-rwxr-xr-x 1 root root 227400 Feb 23 09:07 /usr/lib/upower/upowerd
[~]$ ldd -r !$
ldd -r /usr/lib/upower/upowerd
and look for anything unusual in the output...iirc mine contained a lib
from /use/local, which is non standard, but it could be
I said in my previous post that I do _not_ have
usr/local/lib/libimobiledevice.so.6 installed. Also, I'm running Ubuntu
16.04 _i386_, not amd64. Thus, I assume there is another trigger that
exhibits the bug than the one described in the first post of this
thread.
--
You received this bug
I also do not have /usr/local/lib/libimobiledevice.so.6 on 16.04 amd64
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1577760
Title:
Screen Display 'Apply' fails
Status in upower
I'm experiencing the same problem, but I don't have
/usr/local/lib/libimobiledevice.so.6 installed. So it seems that there
are more than one condition that triggers the exact same behaviour. I'm
using i386 16.04 (not amd64), though.
I still don't have a clue what is causing this. BTW. I
> So, why is upowerd getting linked to
/usr/local/lib/libimobiledevice.so.6 in the first place?
well, upower is linked to libimobiledevice.so.6, then the glibc loader
is looking for available versions in the standard path and "/usr/local"
has the priority, it's there to let admins setup local
Ah, I think I just 'got' what you were suggesting. If I move the
/usr/local/lib/libimobiledevice* away, and then look at the ldd output
from upowerd, I see that it indeed shows it linked to libusbmuxd.so.4,
rather than .2.
[~]$ ldd -r /usr/lib/upower/upowerd | grep usbmuxd
libusbmuxd.so.4
For the record :
[~]$ ls -l /usr/local/lib/libimobiledevice.so.6*
lrwxrwxrwx 1 root root 25 Apr 12 15:32 /usr/local/lib/libimobiledevice.so.6
-> libimobiledevice.so.6.0.0
-rwxr-xr-x 1 root root 143216 Apr 12 15:32
/usr/local/lib/libimobiledevice.so.6.0.0
So, those were made 'quite some
could you test if the theory of the previous comment is true?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1577760
Title:
Screen Display 'Apply' fails
Status in upower package in
Your issue seems to be due to a local installation
libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6
(0x7f3d990ba000)
Does it work if you delete that local library (which is taking over the
system one)? (you should also remove the workaround to make sure it
works without it)
**
** Changed in: upower (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1577760
Title:
Screen Display 'Apply' fails
Status in upower package in
[~]$ dpkg -l | grep upower
ii libupower-glib3:amd640.99.4-2
amd64abstraction for power management -
shared library
ii upower 0.99.4-2
could you provide the output of those commands?
- dpkg -l | grep upower
- ls -l /usr/lib/upower/upowerd
- ldd -r /usr/lib/upower/upowerd
** Changed in: upower (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
Max Waterman, for now, let this be recast to the upower package, given
this issue has been root caused to it pointing to the wrong file
version.
** Changed in: xorg (Ubuntu)
Importance: Low => Medium
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upower (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
** Package changed: xorg (Ubuntu) => upower (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1577760
Title:
Screen Display 'Apply' fails
Status in upower package in Ubuntu:
** Tags added: regression-release
** Description changed:
- When I click on the 'Apply' button of the 'Screen Display' utility
- (without setting anything), I get an error dialog :
+ Since upgrading to 16.04, when I click on the 'Apply' button of the
+ 'Screen Display' utility (without setting
Correct, the problem started when I *upgraded* from 15.10 to 16.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1577760
Title:
Screen Display 'Apply' fails
Status in xorg package in
Max Waterman, thank you for reporting this and helping make Ubuntu
better.
To clarify, did this issue not occur in a release prior to 16.04?
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Changed in: xorg (Ubuntu)
Status: Confirmed => Incomplete
--
You received this
** Tags added: bios-outdated-1.21
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1577760
Title:
Screen Display 'Apply' fails
Status in xorg package in Ubuntu:
Confirmed
Bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1577760
Prompted by all the upowerd errors in syslog, I tried to run it
manually...
[~]$ gnome-settings-daemon --replace
(gnome-settings-daemon:8495): libupower-glib-WARNING **: Couldn't connect to
proxy: Error calling StartServiceByName for org.freedesktop.UPower:
I notice that one of my monitors is 'lost' (the BenQ one) if the laptop
is allowed to go to sleep and then awoken. The 'Screen Display' tool is
still 'non-functional'.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
This is the xdpyinfo output with the monitors running in 'mirror' mode after
booting the laptop docked with monitors attached.
(I attach this because I imagine the one obtained by the bug tool was probably
not the same)
** Attachment added: "xdpyinfo.txt with monitors attached."
I should add that, if I boot my laptop with it in the doc and monitors
connected, then they are configured in 'mirrored' mode, and work as
expected. Of course, that's not what I want and any attempt to use the
'Screen Display' tool to change the configuration fails with the error
mentioned above.
30 matches
Mail list logo
