Bug 384575 - Suspend fails if baloo file is running
Summary: Suspend fails if baloo file is running
Status: RESOLVED FIXED
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.38.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-10 21:04 UTC by Txutxifel
Modified: 2018-11-26 19:42 UTC (History)
1 user (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 Txutxifel 2017-09-10 21:04:20 UTC
if i boot my PC (and my laptop) I can't suspend in the first instants. I have to wait several minutes because of baloo_file

If I try, i got a hang for several time and got the lock screen again without suspendig. 

I found in dmesg:

2017-09-10T22:53:41.205545+02:00 PC001 kernel: [  194.644616] baloo_file      D    0  3424   3377 0x00000004
2017-09-10T22:53:41.205547+02:00 PC001 kernel: [  194.644622] Call Trace:
2017-09-10T22:53:41.205551+02:00 PC001 kernel: [  194.644635]  ? __schedule+0x238/0x870
2017-09-10T22:53:41.205555+02:00 PC001 kernel: [  194.644640]  schedule+0x39/0x90
2017-09-10T22:53:41.205557+02:00 PC001 kernel: [  194.644652]  request_wait_answer+0x8a/0x1d0 [fuse]
2017-09-10T22:53:41.205562+02:00 PC001 kernel: [  194.644659]  ? finish_wait+0x80/0x80
2017-09-10T22:53:41.205565+02:00 PC001 kernel: [  194.644666]  __fuse_request_send+0x62/0x80 [fuse]
2017-09-10T22:53:41.205569+02:00 PC001 kernel: [  194.644674]  fuse_readdir+0x13b/0x820 [fuse]
2017-09-10T22:53:41.205572+02:00 PC001 kernel: [  194.644682]  ? __fsnotify_parent+0x91/0x120
2017-09-10T22:53:41.205574+02:00 PC001 kernel: [  194.644687]  iterate_dir+0x169/0x190
2017-09-10T22:53:41.205576+02:00 PC001 kernel: [  194.644692]  SyS_getdents+0x8d/0x100
2017-09-10T22:53:41.205579+02:00 PC001 kernel: [  194.644695]  ? fillonedir+0xb0/0xb0
2017-09-10T22:53:41.205582+02:00 PC001 kernel: [  194.644702]  ? entry_SYSCALL_64_fastpath+0x1e/0xa9
2017-09-10T22:53:41.205584+02:00 PC001 kernel: [  194.644706]  entry_SYSCALL_64_fastpath+0x1e/0xa9
2017-09-10T22:53:41.205586+02:00 PC001 kernel: [  194.644710] RIP: 0033:0x7f5111ee772b
Comment 1 Nate Graham 2018-11-26 19:42:46 UTC
This has been fixed in a later version.