[dolphin] [Bug 362439] dolphin crashed every time i copy ore move a file with acl's that is mounted over nfs3

[boospy via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362439

--- Comment #1 from boospy  ---
Also on NFS4.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 362439] New: dolphin crashed every time i copy ore move a file with acl's that is mounted over nfs3

[boospy via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362439

Bug ID: 362439
   Summary: dolphin crashed every time i copy ore move a file with
acl's that is mounted over nfs3
   Product: dolphin
   Version: 15.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: li...@osit.cc

Hello, 

i've running a Kubuntu 16.04 as client machine. As nfsserver is an Proxmox4.2
(Debian 8 Kernel 4.4). Shares are mounted over FSTAB with ACLoption. So at the
most time when i copy ore move a file in or from an ACLplace dolphin crashed
with errermessage "Permissions can not be changed PID: 11374 Signal:
Segmentation fault" 

But all changes are done. Everything is fine, only dolphin crashed. With Ubuntu
16.04 nautilus an copy over CMD everything goes fine. Strange thing is, when i
say:

mount | grep acl 

nothing is going. On an older clientsystem like Ubuntu 14.04 there is this
flag. But yes it works over CMD and nautilus, so i thing this is new and
normal. 

Reproducible: Always

Steps to Reproduce:
1. add an nfsshare:
/export *(acl,async,no_subtree_check,fsid=0,rw)
/home   *(acl,async,no_subtree_check,rw,no_root_squash)

2. Set the mount in fstab:
nfsserver:/home/   /home/daten_nfsserver/  nfs
rw,_netdev,acl,intr,soft,bg,noauto,x-systemd.automount 0   0

3. copy ore move some files with acl's

Actual Results:  
It copies but dolphin crashes

Expected Results:  
:) not crashing

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 361868] Baloo crashes every time i change an filename, or add a new file

[boospy via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361868

--- Comment #1 from boospy  ---
When i touched a file, here is the CMD output. Maybe it is helpfull:

KCrash: Attempting to start /usr/bin/baloo_file from kdeinit
sock_file=/run/user/10001/kdeinit5__0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = baloo_file path = /usr/bin pid = 29076
KCrash: Arguments: /usr/bin/baloo_file 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/10001/kdeinit5__0
QSocketNotifier: Invalid socket 4 and type 'Read', disabling...
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 5 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 7 and type 'Exception', disabling...

-- 
You are receiving this mail because:
You are watching all bug changes.

[Baloo] [Bug 361868] New: Baloo crashes every time i change an filename, or add a new file

[boospy via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361868

Bug ID: 361868
   Summary: Baloo crashes every time i change an filename, or add
a new file
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: li...@osit.cc
CC: pinak.ah...@gmail.com

Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-18-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Balooservice is stopped

- Custom settings of the application:
I set customfolders outside my home. Folder they are on an NFSshare. The share
is permanently mounted in the FSTAB. Unix ACLs are used too.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff8ace888c0 (LWP 17346))]

Thread 2 (Thread 0x7ff763193700 (LWP 32311)):
[KCrash Handler]
#6  0x7ff8ac0573c2 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#7  0x7ff8ac073896 in Baloo::PostingCodec::decode(QByteArray const&) ()
from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x7ff8ac05f814 in Baloo::PostingDB::get(QByteArray const&) () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#9  0x7ff8ac0703c6 in Baloo::WriteTransaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#10 0x7ff8ac068032 in Baloo::Transaction::commit() () from
/usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#11 0x0041c8e0 in Baloo::NewFileIndexer::run() ()
#12 0x7ff8ab986343 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7ff8ab98984e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7ff8aa5ed6fa in start_thread (arg=0x7ff763193700) at
pthread_create.c:333
#15 0x7ff8aaf96b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7ff8ace888c0 (LWP 17346)):
#0  0x7ff8aaf869cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff8a819e6c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff8a815ae04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff8a815b2c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff8a815b42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff8abbc0a9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff8abb67dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff8abb6fe8c in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x0041698c in main ()

Possible duplicates by query: bug 356445.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.