Bug 398961 - Dolphin crash following rename of KDE Activity
Summary: Dolphin crash following rename of KDE Activity
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 17.04.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2018-09-22 15:26 UTC by jetojedno
Modified: 2018-11-12 16:05 UTC (History)
2 users (show)

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 jetojedno 2018-09-22 15:26:07 UTC
Application: dolphin (17.04.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.155-68-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:
I renamed an Activity, then started the (renamed) activity.  Dolphin crashed as the activity started.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f60ec64b900 (LWP 6352))]

Thread 4 (Thread 0x7f60bc2c0700 (LWP 6362)):
#0  0x00007f60ebf0330d in poll () at /lib64/libc.so.6
#1  0x00007f60e0a9d314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f60e0a9d42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f60e62001ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f60e61adbfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f60e5fe8f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f60e5feda29 in  () at /usr/lib64/libQt5Core.so.5
#7  0x00007f60e1624724 in start_thread () at /lib64/libpthread.so.0
#8  0x00007f60ebf0be8d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f60c1e86700 (LWP 6359)):
#0  0x00007f60e16290ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f60cd281b4b in  () at /usr/lib64/dri/r600_dri.so
#2  0x00007f60cd2818c7 in  () at /usr/lib64/dri/r600_dri.so
#3  0x00007f60e1624724 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f60ebf0be8d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f60cee44700 (LWP 6354)):
#0  0x00007f60ebf0330d in poll () at /lib64/libc.so.6
#1  0x00007f60e0a9d314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f60e0a9d42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f60e62001ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f60e61adbfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f60e5fe8f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f60e6614295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x00007f60e5feda29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f60e1624724 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f60ebf0be8d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f60ec64b900 (LWP 6352)):
[KCrash Handler]
#6  0x00007f60ec2162bf in  () at /usr/lib64/libkdeinit5_dolphin.so
#7  0x00007f60ec21f599 in  () at /usr/lib64/libkdeinit5_dolphin.so
#8  0x00007f60ec221234 in  () at /usr/lib64/libkdeinit5_dolphin.so
#9  0x00007f60e97d9019 in KMainWindow::readPropertiesInternal(KConfig*, int) () at /usr/lib64/libKF5XmlGui.so.5
#10 0x00007f60e97d9152 in KMainWindow::restore(int, bool) () at /usr/lib64/libKF5XmlGui.so.5
#11 0x00007f60ec2250fb in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#12 0x00007f60ebe3f725 in __libc_start_main () at /lib64/libc.so.6
#13 0x0000000000400789 in _start ()

Reported using DrKonqi
Comment 1 Julian Steinmann 2018-09-22 15:49:24 UTC
Hello and thank you for reporting your issue. You are currently using Dolphin 17.04.2, which is already more than 18 months old. Please consider updating Dolphin (the experimental packages for openSUSE should already include 18.08) and try to reproduce the issue. Another important action would be to install the debug packages for Dolphin and then upload a new, complete backtrace. Thanks!
Comment 2 Andrew Crouthamel 2018-10-21 05:03:55 UTC
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!
Comment 3 Bug Janitor Service 2018-11-12 16:05:36 UTC
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!