Bug 259571 - "Present Windows" desktop effect crashes Kwin when the minus key is pressed too many times
Summary: "Present Windows" desktop effect crashes Kwin when the minus key is pressed t...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-12-12 05:12 UTC by Andrew Lambert
Modified: 2018-09-20 22:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Lambert 2010-12-12 05:12:59 UTC
Application: kwin (4.5.1 (KDE 4.5.1))
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-23-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
I was messing around with the "Present Windows" desktop effect and pressed the + and - keys to find that doing so seemed to add and remove new instances of the desktop.

- Unusual behavior I noticed:
 Pressing - again when there was only one desktop left caused Kwin to immediately crash.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fd3ce25d7a0 (LWP 1816))]

Thread 2 (Thread 0x7fd3a94d9710 (LWP 1819)):
#0  0x00007fd3cdade2e3 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007fd3ca32476e in qt_safe_select (nfds=23, fdread=0x1e968e0, fdwrite=0x1e96b78, fdexcept=0x1e96e10, orig_timeout=0x0) at kernel/qcore_unix.cpp:82
#2  0x00007fd3ca329beb in QEventDispatcherUNIXPrivate::doSelect (this=0x1e96720, flags=<value optimized out>, timeout=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:219
#3  0x00007fd3ca32a81b in QEventDispatcherUNIX::processEvents (this=0x1e437b0, flags=) at kernel/qeventdispatcher_unix.cpp:919
#4  0x00007fd3ca2f9a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fd3ca2f9dec in QEventLoop::exec (this=0x7fd3a94d8cb0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fd3ca2042fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fd3ca2d95f8 in QInotifyFileSystemWatcherEngine::run (this=0x1e8dd80) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fd3ca20727e in QThreadPrivate::start (arg=0x1e8dd80) at thread/qthread_unix.cpp:266
#9  0x00007fd3cb82c953 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007fd3c9f7c971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#11 0x00007fd3cdae594d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fd3ce25d7a0 (LWP 1816)):
[KCrash Handler]
#6  0x00007fd3cde1c8d3 in KWin::Workspace::clientArea (this=0x177b990, opt=KWin::MaximizeArea, screen=1, desktop=1) at ../../kwin/geometry.cpp:261
#7  0x00007fd3cde1cb32 in KWin::Workspace::clientArea (this=0x177b990, opt=KWin::MaximizeArea, p=<value optimized out>, desktop=0) at ../../kwin/geometry.cpp:305
#8  0x00007fd3cde1d14c in KWin::Workspace::clientArea (this=0x177b990, opt=KWin::MaximizeArea, c=0x304d8e0) at ../../kwin/geometry.cpp:310
#9  0x00007fd3cde23251 in KWin::Client::changeMaximize (this=0x304d8e0, vertical=false, horizontal=false, adjust=true) at ../../kwin/geometry.cpp:2253
#10 0x00007fd3cde243d9 in KWin::Client::checkWorkspacePosition (this=0x304d8e0) at ../../kwin/geometry.cpp:1115
#11 0x00007fd3cde25eac in KWin::Workspace::updateClientArea (this=0x177b990, force=<value optimized out>) at ../../kwin/geometry.cpp:228
#12 0x00007fd3cddb9e5f in KWin::Workspace::setNumberOfDesktops (this=0x177b990, n=0) at ../../kwin/workspace.cpp:1724
#13 0x00007fd3b500ca35 in KWin::DesktopGridEffect::grabbedKeyboardEvent (this=0x1c9a160, e=0x7fff99ed0150) at ../../../kwin/effects/desktopgrid/desktopgrid.cpp:803
#14 0x00007fd3cddf6012 in KWin::Workspace::workspaceEvent (this=<value optimized out>, e=<value optimized out>) at ../../kwin/events.cpp:548
#15 0x00007fd3cddd323e in KWin::Application::notify (this=0x7fff99ed0f70, o=0x18475e0, e=0x1) at ../../kwin/main.cpp:370
#16 0x00007fd3ca2facdc in QCoreApplication::notifyInternal (this=0x7fff99ed0f70, receiver=0x18475e0, event=0x7fff99ed0150) at kernel/qcoreapplication.cpp:732
#17 0x00007fd3c94f24ba in QKeyMapper::sendKeyEvent (keyWidget=0x18475e0, grab=<value optimized out>, type=QEvent::KeyPress, code=45, modifiers=<value optimized out>, text=..., autorepeat=true, count=1, nativeScanCode=82, nativeVirtualKey=65453, nativeModifiers=16) at kernel/qkeymapper_x11.cpp:1867
#18 0x00007fd3c94f4ac0 in QKeyMapperPrivate::translateKeyEvent (this=0x7fff99ed0330, keyWidget=0x18475e0, event=<value optimized out>, grab=2) at kernel/qkeymapper_x11.cpp:1837
#19 0x00007fd3c94cbcb4 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff99ed0d30) at kernel/qapplication_x11.cpp:3429
#20 0x00007fd3c94f8b6f in QEventDispatcherX11::processEvents (this=<value optimized out>, flags=) at kernel/qeventdispatcher_x11.cpp:132
#21 0x00007fd3ca2f9a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#22 0x00007fd3ca2f9dec in QEventLoop::exec (this=0x7fff99ed0eb0, flags=) at kernel/qeventloop.cpp:201
#23 0x00007fd3ca2fdebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#24 0x00007fd3cddd4f9d in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kwin/main.cpp:531
#25 0x00007fd3cda1dd8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff99ed1578) at libc-start.c:226
#26 0x0000000000400669 in _start ()

Possible duplicates by query: bug 179309, bug 179153.

Reported using DrKonqi
Comment 1 Martin Flöser 2010-12-12 08:49:29 UTC
The description of your crash report does not match the crash itself. First of 
all I assume you used DesktopGrid effect (Ctrl+F8) and not Present Windows 
(ctrl+f9 or Ctrl+f10) and the crashtrace says that you used a keyboard which 
resulted in the crash.

Can you please verify the steps to reproduce the crash?

Please also try to update to a later revision of KDE 4.5. Several crashes in 
the DesktopGrid effect have been fixed since the release of 4.5.1 which is 
included in Kubuntu. The current release is 4.5.4 which is available in a PPA.
Comment 2 Martin Flöser 2010-12-18 11:34:50 UTC
we need to know if this is reproducable in later version. Quite some crashes have been fixed in 4.5.x|x>1
Comment 3 Andrew Crouthamel 2018-09-20 22:04:50 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Lambert 2018-09-20 22:13:37 UTC
This report is 8 years old and I don't remember any details. I don't even remember reporting it.