[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

2016-09-01 Thread rdz
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 an

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

2016-08-18 Thread rdz
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

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

2016-08-16 Thread rdz
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 => /usr/lib/i386-linux-gnu/libupower-glib.so.

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

2016-08-16 Thread rdz
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 notifica

[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

2016-07-06 Thread rdz
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 experience