| Summary: | crash of dolphin after dragging a .avi into vlc player | ||
|---|---|---|---|
| Product: | [Plasma] Oxygen | Reporter: | nydel |
| Component: | style | Assignee: | Hugo Pereira Da Costa <hugo.pereira.da.costa> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | hugo.pereira.da.costa, kdebugs, perso |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.11.2 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
nydel
2013-11-30 17:33:03 UTC
i wanna add (in case helpful) that desktop effects are enabled and working, and dolphin /may/ have been slightly transparent but has no application-specific window appearance specifications This could also be bug 293863, but those do not have Oxygen in the backtrace. @Christophe Thanks for posting the other report. In fact I have also seen weird behaviors and crashes in my own qt apps with drag and drop. My "gut" feeling is that there is something broken (and unreproducible unfortunately) in current Qt4 drag and drop ... Yes, drag and drop in Qt is dangerous, because it uses a local event loop. This unfortunately is not changed for Qt 5. Created attachment 87228 [details]
New crash information added by DrKonqi
dolphin (4.13.0) on KDE Platform 4.13.0 using Qt 4.8.6
- What I was doing when the application crashed:
Likewise, I had just dragged a folder of MP3s into vlc's playlist, and dolphin crashed a couple seconds later.
-- Backtrace (Reduced):
#7 0xb5a9afbb in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x8e987e0, receiver=receiver@entry=0x997da30, event=event@entry=0xbff4f5b4) at kernel/qcoreapplication.cpp:1063
#8 0xb5ff67d1 in QApplicationPrivate::notify_helper (this=0x8e987e0, receiver=0x997da30, e=0xbff4f5b4) at kernel/qapplication.cpp:4563
#9 0xb5ffd2d3 in QApplication::notify (this=0xbff50180, receiver=receiver@entry=0x997da30, e=e@entry=0xbff4f5b4) at kernel/qapplication.cpp:4353
#10 0xb6b470a4 in KApplication::notify (this=0xbff50180, receiver=0x997da30, event=0xbff4f5b4) at ../../kdeui/kernel/kapplication.cpp:311
#11 0xb5a9ae4a in QCoreApplication::notifyInternal (this=0xbff50180, receiver=receiver@entry=0x997da30, event=event@entry=0xbff4f5b4) at kernel/qcoreapplication.cpp:953
Hi, Just for the record, a user report the same bug on the Debian bug Tracker, with backtracks : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733199 Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! 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 mark the bug 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |