Bug 299480 - KWin crash changing Gwenview screen mode
Summary: KWin crash changing Gwenview screen mode
Status: RESOLVED DUPLICATE of bug 288454
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:
Depends on:
Blocks:
 
Reported: 2012-05-06 01:30 UTC by fsanchez
Modified: 2013-09-09 12:00 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (3.67 KB, text/plain)
2013-04-13 08:56 UTC, Nikola Schnelle
Details
New crash information added by DrKonqi (1.99 KB, text/plain)
2013-09-08 18:18 UTC, Alexander
Details

Note You need to log in before you can comment on or make changes to this bug.
Description fsanchez 2012-05-06 01:30:31 UTC
Application: kwin (4.8.3 (4.8.3))
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: Kwin crashed when changing several times the view mode in Gwenview, from normal to full-screen. 
It's the very first time I see it, so I'm not quite sure if what I've described is what make KWin crash. 

Additional info from "System settings/Desktop effects/Advanced" window:
Composition: OpenGL
Window tooltips: only for shown windows
scaling: precise
***Suspend effects on full screen mode: NO***
Use shaders OpenGL 2
Use VSync

Video card: NVidia 8200GM 
Driver: 295.40

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fde9acb27c0 (LWP 1789))]

Thread 3 (Thread 0x7fde76402700 (LWP 1808)):
#0  0x00007fde9a4c9823 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007fde95c12366 in qt_safe_select (nfds=28, fdread=0x7fde6c000ae8, fdwrite=0x7fde6c000d80, fdexcept=0x7fde6c001018, orig_timeout=<optimized out>) at kernel/qcore_unix.cpp:83
#2  0x00007fde95c177b2 in QEventDispatcherUNIXPrivate::doSelect (this=0x7fde6c000930, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223
#3  0x00007fde95c17ca3 in QEventDispatcherUNIX::processEvents (this=0x7fde6c000910, flags=...) at kernel/qeventdispatcher_unix.cpp:926
#4  0x00007fde95be4c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fde95be4ed7 in QEventLoop::exec (this=0x7fde76401cd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fde95ae3fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007fde95bc49ff in QInotifyFileSystemWatcherEngine::run (this=0x2244a90) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fde95ae6fcb in QThreadPrivate::start (arg=0x2244a90) at thread/qthread_unix.cpp:298
#9  0x00007fde96734b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007fde8ed0ee9a in start_thread (arg=0x7fde76402700) at pthread_create.c:308
#11 0x00007fde9a4d04bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fde75c01700 (LWP 1809)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fde96f89222 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007fde96f89259 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007fde96734b74 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#4  0x00007fde8ed0ee9a in start_thread (arg=0x7fde75c01700) at pthread_create.c:308
#5  0x00007fde9a4d04bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fde9acb27c0 (LWP 1789)):
[KCrash Handler]
#6  0x0000003200000001 in ?? ()
#7  0x00007fde94fe90b3 in QETWidget::translateMouseEvent (this=0x29ceee0, event=0x7fff4677fa00) at kernel/qapplication_x11.cpp:4358
#8  0x00007fde94fe7bae in QApplication::x11ProcessEvent (this=0x7fff4677fd10, event=0x7fff4677fa00) at kernel/qapplication_x11.cpp:3732
#9  0x00007fde95011b3a in QEventDispatcherX11::processEvents (this=0x1b3cad0, flags=...) at kernel/qeventdispatcher_x11.cpp:132
#10 0x00007fde95be4c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#11 0x00007fde95be4ed7 in QEventLoop::exec (this=0x7fff4677fc50, flags=...) at kernel/qeventloop.cpp:204
#12 0x00007fde95be9f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#13 0x00007fde9a7fba06 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#14 0x00007fde9a3ff76d in __libc_start_main (main=0x400630, argc=3, ubp_av=0x7fff46780438, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff46780428) at libc-start.c:226
#15 0x0000000000400661 in _start ()

This bug may be a duplicate of or related to bug 288454.

Possible duplicates by query: bug 296326, bug 294814, bug 294726, bug 293733, bug 291460.

Reported using DrKonqi
Comment 1 Thomas Lübking 2012-05-06 11:17:34 UTC
What window decoration do you use?
Comment 2 fsanchez 2012-05-06 14:34:44 UTC
Oxygen nowadays. As I said, the crash appeared when I swiched many time from normal mode to full-screen. 
What I was trying to do, exactly was rename with F2 an image in Gwenview, but it changed the name of other image. So I unselect the image I was trying to rename, and select it again... _many_ times. In 3 of this times, I pressed the button "full screen" insetad of "+". At the 3rd one, KWin crashed.

That was what I was doing when KWin crashed. But... I don't know, maybe it was for another reason. Another different (from usual) thing I had in my desktop at that moment, was a "no title bar" for Firefox.

Well, I don't know what else :-|
Comment 3 Nikola Schnelle 2013-04-13 08:56:37 UTC
Created attachment 78855 [details]
New crash information added by DrKonqi

kwin (4.10.2) on KDE Platform 4.10.2 using Qt 4.8.2

- What I was doing when the application crashed:
Changed view mode from "full screen" to "browse" mode.

-- Backtrace (Reduced):
#8  0xb546d56f in QETWidget::translateMouseEvent (this=0x919f288, event=0xbff5de1c) at kernel/qapplication_x11.cpp:4358
#9  0xb546bb2d in QApplication::x11ProcessEvent (this=0xbff5e044, event=0xbff5de1c) at kernel/qapplication_x11.cpp:3732
#10 0xb54999f8 in QEventDispatcherX11::processEvents (this=0x9056eb8, flags=...) at kernel/qeventdispatcher_x11.cpp:132
#11 0xb5ef36ad in QEventLoop::processEvents (this=0xbff5dfa4, flags=...) at kernel/qeventloop.cpp:149
#12 0xb5ef3949 in QEventLoop::exec (this=0xbff5dfa4, flags=...) at kernel/qeventloop.cpp:204
Comment 4 Alexander 2013-09-08 18:18:10 UTC
Created attachment 82222 [details]
New crash information added by DrKonqi

kwin (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.5

- What I was doing when the application crashed:

Launch Gwenview in fullscreen mode and then exit (press Esc), then press Alt-Tab to swtich to Desktop.

-- Backtrace (Reduced):
#5  0x0000003ff4a40004 in QETWidget::translateMouseEvent(_XEvent const*) () from /lib64/libQtGui.so.4
#6  0x0000003ff4a3e39c in QApplication::x11ProcessEvent(_XEvent*) () from /lib64/libQtGui.so.4
#7  0x0000003ff4a65880 in QEventDispatcherX11::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtGui.so.4
#8  0x0000003ff2178ecf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#9  0x0000003ff21791c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
Comment 5 Thomas Lübking 2013-09-09 12:00:18 UTC
This is a direct dupe of bug #317720 thus very likely #288454

The interesting aspect of comment #4 though is, that apparently the titlebar/decoration is not invoked at all while with the tabbox (likely) QML is (as with the many Aurorae/DeclarativeView bugs asumed as dupes by bugzilla)

*** This bug has been marked as a duplicate of bug 288454 ***