Bug 261760 - Dolphin crashed when adding Information Panel
Summary: Dolphin crashed when adding Information Panel
Status: RESOLVED DUPLICATE of bug 257944
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-01 01:59 UTC by linuxg33k4life
Modified: 2011-01-01 14:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description linuxg33k4life 2011-01-01 01:59:08 UTC 
Application: dolphin (1.5.9)
KDE Platform Version: 4.5.85 (4.6 Beta2)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-rc5-12-desktop x86_64
Distribution: "openSUSE 11.4 Milestone 5 of 6 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was browsing a folder, and then exited dolphin when it crashed.

- Custom settings of the application:
Just added the Information Panel right before I closed dolphin.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Aborted
[KCrash Handler]
#6  0x00007f4c39f61ad5 in raise () from /lib64/libc.so.6
#7  0x00007f4c39f62fd6 in abort () from /lib64/libc.so.6
#8  0x00007f4c39f9cdf3 in __libc_message () from /lib64/libc.so.6
#9  0x00007f4c39fa23d6 in malloc_printerr () from /lib64/libc.so.6
#10 0x00007f4c3a33c2d9 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib64/libstdc++.so.6
#11 0x00007f4c39f645d1 in __run_exit_handlers () from /lib64/libc.so.6
#12 0x00007f4c39f64625 in exit () from /lib64/libc.so.6
#13 0x0000000000407600 in _start ()

Possible duplicates by query: bug 261706, bug 261644, bug 261573, bug 261508, bug 261329.

Reported using DrKonqi
Comment 1 Dario Andres 2011-01-01 14:22:05 UTC 
[Comment from a bug triager]
This is an OpenSuse+Strigi bug being tracked at bug 257944. Regards

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