Bug 256735 - I want 2 save an iso-image in rekonq
Summary: I want 2 save an iso-image in rekonq
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: kwin
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Packages Linux
: NOR crash (vote)
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-12 20:50 UTC by Mario Zimpel
Modified: 2011-05-07 10:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Zimpel 2010-11-12 20:50:46 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-22-generic i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
I want 2 save an iso-image in rekonq.
- Unusual behavior I noticed:
different colours for all kinds of Information, because changing of composite or of the theme.

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

Thread 2 (Thread 0xaede0b70 (LWP 1660)):
#0  0x01705e36 in clock_gettime () from /lib/librt.so.1
#1  0x089f350b in do_gettime () at tools/qelapsedtimer_unix.cpp:105
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:119
#3  0x08aca6e5 in QTimerInfoList::updateCurrentTime (this=0x914e608) at kernel/qeventdispatcher_unix.cpp:339
#4  0x08aca72a in QTimerInfoList::timerWait (this=0x914e608, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0x08acbcab in QEventDispatcherUNIX::processEvents (this=0x914d528, flags=...) at kernel/qeventdispatcher_unix.cpp:906
#6  0x08a98609 in QEventLoop::processEvents (this=0xaede0280, flags=) at kernel/qeventloop.cpp:149
#7  0x08a98a8a in QEventLoop::exec (this=0xaede0280, flags=...) at kernel/qeventloop.cpp:201
#8  0x08994b7e in QThread::exec (this=0x914d0a0) at thread/qthread.cpp:490
#9  0x08a7735b in QInotifyFileSystemWatcherEngine::run (this=0x914d0a0) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x08997df9 in QThreadPrivate::start (arg=0x914d0a0) at thread/qthread_unix.cpp:266
#11 0x00b4fcc9 in start_thread () from /lib/libpthread.so.0
#12 0x001e06ae in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb788b720 (LWP 1642)):
[KCrash Handler]
#7  KWin::DimInactiveEffect::windowActivated (this=0x91afe40, w=0x92e3958) at ../../../kwin/effects/diminactive/diminactive.cpp:137
#8  0x00d80fd4 in KWin::EffectsHandlerImpl::windowActivated (this=0x9007138, c=0x92e3958) at ../../kwin/effects.cpp:308
#9  0x00d2844a in KWin::Workspace::setActiveClient (this=0x8f97970, c=0x9344618) at ../../kwin/activation.cpp:261
#10 0x00d285ae in KWin::Client::setActive (this=0x9344618, act=true) at ../../kwin/activation.cpp:882
#11 0x00d28e24 in KWin::Workspace::takeActivity (this=0x8f97970, c=0x9344618, flags=1, handled=false) at ../../kwin/activation.cpp:372
#12 0x00d28f80 in KWin::Workspace::requestFocus (this=0x8f97970, c=0x9302048, force=false) at ../../kwin/activation.cpp:328
#13 0x00d299e6 in KWin::Workspace::activateNextClient (this=0x8f97970, c=0x932fdf8) at ../../kwin/activation.cpp:461
#14 0x00cdda77 in KWin::Client::releaseWindow (this=0x932fdf8, on_shutdown=false) at ../../kwin/client.cpp:244
#15 0x00d138dd in KWin::Client::unmapNotifyEvent (this=0x932fdf8, e=0xbfa1c0ec) at ../../kwin/events.cpp:809
#16 0x00d14fa4 in KWin::Client::windowEvent (this=0x932fdf8, e=0xbfa1c0ec) at ../../kwin/events.cpp:655
#17 0x00d157e4 in KWin::Workspace::workspaceEvent (this=0x8f97970, e=0xbfa1c0ec) at ../../kwin/events.cpp:307
#18 0x00cecb32 in KWin::Application::x11EventFilter (this=0xbfa1c2d4, e=0xbfa1c0ec) at ../../kwin/main.cpp:363
#19 0x02eaeeb0 in qt_x11EventFilter (ev=0xbfa1c0ec) at kernel/qapplication_x11.cpp:408
#20 0x02ebfab0 in QApplication::x11ProcessEvent (this=0xbfa1c2d4, event=0xbfa1c0ec) at kernel/qapplication_x11.cpp:3248
#21 0x02ef0fc7 in QEventDispatcherX11::processEvents (this=0x8ed3998, flags=...) at kernel/qeventdispatcher_x11.cpp:132
#22 0x08a98609 in QEventLoop::processEvents (this=0xbfa1c224, flags=) at kernel/qeventloop.cpp:149
#23 0x08a98a8a in QEventLoop::exec (this=0xbfa1c224, flags=...) at kernel/qeventloop.cpp:201
#24 0x08a9d00f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#25 0x02e2ce07 in QApplication::exec () at kernel/qapplication.cpp:3672
#26 0x00ceec54 in kdemain (argc=3, argv=0xbfa1c534) at ../../kwin/main.cpp:531
#27 0x080485ab in main (argc=3, argv=0xbfa1c534) at kwin_dummy.cpp:3

Reported using DrKonqi
Comment 1 Rohan Garg 2010-12-31 16:50:06 UTC
Hi
This seems to be more of a kwin issue than a rekonq issue, could you please check if the KDE 4.5.4 bug fix releases fixed your issue? 
Thanks
Comment 2 Thomas Lübking 2010-12-31 17:25:28 UTC
I'd be not so sure.
KWin crashed, yes (shouldn't happen, maybe the adjusted autofocus strategy will work around this) - but it looks a lot like a "follow up" crash (a client/groupmember "vanished" "unexpectedly" during the activation - this would be rekonq, i assume...) so

-> there might have been an original issue with rekonq.

@Mario
Can you please elaborate on the "unusual behaviour" comment? (i can make nothing out of it, sorry)
Comment 3 Martin Flöser 2011-05-07 10:27:21 UTC
we need more info on how to reproduce the crash.