Bug 388004 - Save / Open File Dialog hangs on autofs mounts
Summary: Save / Open File Dialog hangs on autofs mounts
Status: RESOLVED DUPLICATE of bug 373352
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.32.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2017-12-18 08:19 UTC by Rolf
Modified: 2018-03-12 02:12 UTC (History)
3 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 Rolf 2017-12-18 08:19:26 UTC
Application: dolphin (17.04.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to save some attachements from an eMail.

- Unusual behavior I noticed:
Lately, I realized that depending where I work with my notebook (which location / network) I have big problems from different applications to access the file system (open or especially store files)

- Custom settings of the application:
I have set autofs. So depending if I work in the office (to access NAS, Server, etc) or at home office (NAS) or on the road (eg at girl friends place) with no external storage.
That was working fine for the last almost 2 years. But in the last weeks, I got big troubles. It often takes a long time (up to minutes) to open the file save dialog. And it takes long again, when changing directories.
This problem occures much more, when out of the office where I utilize the system most (Thought: There might be stored paths in the "last used files" section, which are not accessable, when not in that network.)

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

Thread 3 (Thread 0x7fbd4ffff700 (LWP 5553)):
#0  0x00007fbd6d46020d in poll () at /lib64/libc.so.6
#1  0x00007fbd61ffd314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fbd61ffd42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fbd677601ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007fbd6770dbfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007fbd67548f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007fbd67b74295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x00007fbd6754da29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007fbd62b84744 in start_thread () at /lib64/libpthread.so.0
#9  0x00007fbd6d468aad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fbd55f9f700 (LWP 5552)):
#0  0x00007fbd6d46020d in poll () at /lib64/libc.so.6
#1  0x00007fbd5fb7a3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x00007fbd5fb7bfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007fbd584fa0d9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007fbd6754da29 in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007fbd62b84744 in start_thread () at /lib64/libpthread.so.0
#6  0x00007fbd6d468aad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fbd6dba5900 (LWP 5551)):
[KCrash Handler]
#6  0x00007fbd675c132c in QMapDataBase::freeTree(QMapNodeBase*, int) () at /usr/lib64/libQt5Core.so.5
#7  0x00007fbd675c134d in QMapDataBase::freeTree(QMapNodeBase*, int) () at /usr/lib64/libQt5Core.so.5
#8  0x00007fbd675c133a in QMapDataBase::freeTree(QMapNodeBase*, int) () at /usr/lib64/libQt5Core.so.5
#9  0x00007fbd675c133a in QMapDataBase::freeTree(QMapNodeBase*, int) () at /usr/lib64/libQt5Core.so.5
#10 0x00007fbd675c133a in QMapDataBase::freeTree(QMapNodeBase*, int) () at /usr/lib64/libQt5Core.so.5
#11 0x00007fbd675c134d in QMapDataBase::freeTree(QMapNodeBase*, int) () at /usr/lib64/libQt5Core.so.5
#12 0x00007fbd675c133a in QMapDataBase::freeTree(QMapNodeBase*, int) () at /usr/lib64/libQt5Core.so.5
#13 0x00007fbd675c133a in QMapDataBase::freeTree(QMapNodeBase*, int) () at /usr/lib64/libQt5Core.so.5
#14 0x00007fbd545f7896 in  () at /usr/lib64/qt5/plugins/styles/oxygen.so
#15 0x00007fbd545f80e9 in  () at /usr/lib64/qt5/plugins/styles/oxygen.so
#16 0x00007fbd545cf2e0 in  () at /usr/lib64/qt5/plugins/styles/oxygen.so
#17 0x00007fbd545cf309 in  () at /usr/lib64/qt5/plugins/styles/oxygen.so
#18 0x00007fbd68690049 in QApplication::~QApplication() () at /usr/lib64/libQt5Widgets.so.5
#19 0x00007fbd6d782562 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#20 0x00007fbd6d39f6e5 in __libc_start_main () at /lib64/libc.so.6
#21 0x0000000000400789 in _start ()

Possible duplicates by query: bug 387954, bug 387944, bug 387887, bug 387842, bug 387840.

Reported using DrKonqi
Comment 1 Rolf 2018-03-11 15:55:56 UTC
Problem further narrowed down:

autofs  and KDE-FileDialog

When away from network any app using standard KDE-FileDialog is hanging for a long time.
Every change in directory tree is then starting long hanging again.

Reproducable: Always
- Go away from network with most used autofs drives
- Us file open or store on any app using KDE-FileDialog

As soon as autofs is stopped (systemctl stop autofs), problem goes away.

=> so it is a combination of autofs with KDE-FileDialog.

Partial work around:
- LibreOffice: Change preferences to use LibreOffice Dialogs
- Thunderbird + Firefox: Remove kmozillahelper from system
  (However, with any update it is re-installed again)
However, other apps using KDE-FileDialog still affected.
Comment 2 Nate Graham 2018-03-12 02:12:39 UTC

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