Bug 297731 - Dolphin crashes after copying a pictures directory from a SDCARD to my ~
Summary: Dolphin crashes after copying a pictures directory from a SDCARD to my ~
Status: RESOLVED DUPLICATE of bug 297422
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 2.0
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-08 18:25 UTC by Martín Cigorraga
Modified: 2012-04-08 18:45 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martín Cigorraga 2012-04-08 18:25:41 UTC
Application: dolphin (2.0)
KDE Platform Version: 4.8.2 (4.8.2) (Compiled from sources)
Qt Version: 4.8.1
Operating System: Linux 3.3.1-1-lqx x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I was surfing the net with Chromium 18.0.1025.151.
Running KDE 4.8.2 on Arch Linux up-to-date.

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff70a598780 (LWP 6239))]

Thread 2 (Thread 0x7ff6f170b700 (LWP 6240)):
#0  0x00007ff707b9c06f in poll () from /lib/libc.so.6
#1  0x00007ff704ab9dc8 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007ff704aba289 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007ff7091edaa6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#4  0x00007ff7091bd7d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#5  0x00007ff7091bda27 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6  0x00007ff7090bdd27 in QThread::exec() () from /usr/lib/libQtCore.so.4
#7  0x00007ff70919d5ff in ?? () from /usr/lib/libQtCore.so.4
#8  0x00007ff7090c0d4b in ?? () from /usr/lib/libQtCore.so.4
#9  0x00007ff708e30e0e in start_thread () from /lib/libpthread.so.0
#10 0x00007ff707ba41ed in clone () from /lib/libc.so.6

Thread 1 (Thread 0x7ff70a598780 (LWP 6239)):
[KCrash Handler]
#6  0x0000000003250a90 in ?? ()
#7  0x00007ff70832eaf4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#8  0x00007ff708333973 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#9  0x00007ff709f85796 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#10 0x00007ff7091be9ec in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#11 0x00007ff70832f37b in QApplicationPrivate::dispatchEnterLeave(QWidget*, QWidget*) () from /usr/lib/libQtGui.so.4
#12 0x00007ff7083aaac7 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#13 0x00007ff7083d26e2 in ?? () from /usr/lib/libQtGui.so.4
#14 0x00007ff704ab98bd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#15 0x00007ff704aba0b8 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0x00007ff704aba289 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#17 0x00007ff7091eda3f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#18 0x00007ff7083d236e in ?? () from /usr/lib/libQtGui.so.4
#19 0x00007ff7091bd7d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#20 0x00007ff7091bda27 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#21 0x00007ff7091c2585 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#22 0x00007ff6f70b6477 in kdemain () from /usr/lib/libkdeinit4_dolphin.so
#23 0x00000000004083e4 in _start ()

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

Possible duplicates by query: bug 297719, bug 297620, bug 297598, bug 297597, bug 297590.

Reported using DrKonqi
Comment 1 Peter Penz 2012-04-08 18:45:27 UTC

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