** Also affects: archlinux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272438
Title:
kwin 100% of cpu, second session
To manage notifications about th
** Description changed:
Steps to reproduce
Login as user1
Login as user2
Press Ctrl+Alt+F7 (to switch to first user)
kwin from second user starts to eat 100% of cpu.
Here is my investigation of what is going on
1) == GDB ==
I attached to running (and eating 100%
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kde-workspace (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272438
Title
** Changed in: kde-workspace (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272438
Title:
kwin 100% of cpu, second session
To manage notifications about this
I keep running into this every time I switch away from X. Here's a stack
trace with Qt debug symbols, in KDE 4.13.3:
#0 0x7f7514c4f8e3 in select () at ../sysdeps/unix/syscall-template.S:81
#1 0x7f750f0401c7 in qt_safe_select (nfds=23, fdread=0xcf7f88,
fdwrite=0xcf8220,
fdexcept=0xc
I've seen the lockup from kwin using 100% cpu on two different Kubuntu
14.04 machines, without needing to switch users. These machines were
ungrades from previous versions, 12.04 and 13.10.
I think its fixed by resetting the kwin configure file by:
run "System Settings"
select "Configure desktop
Was this ever reported upstream? If so would someone kindly piont me to
the upstream bug. I am currently seeing this on kubuntu-14.04 using kde
4.13.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.laun
Hi
Could you please install the Qt4 debug symbols (libqt4-dbg) and then submit a
bug report on https://bugs.kde.org/enter_bug.cgi?format=guided against the
'kwin' product.
If you're running KDE SC < 4.12 . I would recommend upgrading to KDE SC
4.12.1 via the Kubuntu Backports PPA ( https://launc
I am not sure, but it seems, that function denoted in gdb backtrace as
#0 0x7fa238b11303 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
is
bool QEventDispatcherX11::processEvents(QEventLoop::ProcessEventsFlags flags)
from
qt-src/src/gui/kernel/qeventdispatcher_x11.cpp
--
You received
