I am using a custom LVM setup. Similar to what https://launchpad.net
/~daniel-mehrmann described in https://bugs.launchpad.net/ubuntu/+source
/initramfs-tools/+bug/1768230/comments/42.
I've manually installed the debs from
https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.2/+build
Unfortunately, nothing better than just:
killall xfsettingsd; killall xfce4-volumed; sleep 6; xfsettingsd &
xfce4-volumed &
I don't think it is a problem with the locker itself though, to me it
looks like it's just a trigger for an issue in xfce4-volumed or
something related to its interactio
Thanks Timo - I only had light-locker installed, so I did this:
1. Uninstall light-locker
2. Install xcreensaver
3. Reboot
Agreed, it seems to be working fine now, so might be something related
either to light-locker or how it interacts with xfsettingsd.
Thanks for posting a workaround!
--
You
Thanks Timo. Check the comment #7 I posted on the launchpad bug -
(https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1395547/comments/7).
It actually goes down for me too, though it takes a bit longer, 3
minutes on my particular machine.
I tried the thing you used to reproduce:
xm
As per request by Thaddaeus Tintenfisch (thad-fisch) on 2014-12-13:,
I've created a bug report on bugzilla.xfce.org:
https://bugzilla.xfce.org/show_bug.cgi?id=11497
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I ran a strace on the xfsettingsd pid, logged out, logged in and I could
see a lot of these repeating:
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3,
revents=POLLOUT}])
writev(3, [{"\20\0\3\0\3\0\0\0AltL", 12}, {NULL, 0}, {"", 0}], 3) = 12
poll([{fd=3, events=POLLIN}], 1, 42949
Added lshw output.
Answers to other questions:
>> OS: Ubuntu 14.10 64bits
<
Linux aclap 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
>> GPU: AMD ???
<
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Madison [Mobility Rade
I sometimes see these in a terminal after unlocking the screen:
xmodmap: please release the following keys within 2 seconds:
r (keysym 0x72, keycode 27)
Control_R (keysym 0xffe4, keycode 105)
Not sure if that is related at all to this bug.
--
You received this bug notification because
After reading the bug I mentioned in #6, I tried waiting after logging
in. The CPU usage went down in about 3 minutes without restarting
xfsettingsd. This leads me to believe these bugs are more related than I
thought. Contrary to #10 in that bug
(https://bugs.launchpad.net/ubuntu/+source/linux/+bu
May be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/998310, using
Xubuntu 14.10. The behavior doesn't look completely the same, only
similar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
May be related to
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1395547,
using Xubuntu 14.10. The behavior doesn't look completely the same, only
similar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
- xfce4-volumed seems not to be working properly after that
- Restarting xfce4-volumed fixes the multimedia keys not working. One CPU core
is still used by xfsettingsd
- Restarting both xfsettingsd and xfce4-volumed or just xfce4-volumed fixes the
CPU issue
- If I kill xfsettingsd, leave xfce4-vo
Public bug reported:
Just upgraded to Xubuntu 14.10, had issues with fglrx (see
http://askubuntu.com/questions/552795/xubuntu-14-10-upgrade-issues-with-
fglrx), went back to radeon drivers. Now it looks to be OK, however
after locking the screen using xflock4 and unlocking, I get these three
proce
13 matches
Mail list logo
