Bug 7092

Summary:	dolphin freeze after log in and a long term of non use
Product:	Mageia	Reporter:	alain deraedt <alainderaedt>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	balcaen.john, juan.baptiste, lmenut, mageia, shlomif
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kdebase4-runtime	CVE:
Status comment:
Attachments:	result obtained by typing dolphin on a terminal just after login

Description alain deraedt 2012-08-17 18:10:16 CEST

Description of problem:dolphin freezes just after login; here below I obtain when typing dolphin in a terminal:

[alain4@mageia2_64 ~]$ dolphin
"/usr/bin/dolphin(4231)" Soprano: "org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
"/usr/bin/dolphin(4231)" Soprano: "QLocalSocket::connectToServer: Invalid name"
"/usr/bin/dolphin(4231)" Soprano: "org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
"/usr/bin/dolphin(4231)" Soprano: "QLocalSocket::connectToServer: Invalid name"
"/usr/bin/dolphin(4231)" Soprano: "org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
"/usr/bin/dolphin(4231)" Soprano: "QLocalSocket::connectToServer: Invalid name"

Furthermore: if you don't use your computer for a while (for example 1 hour) no application reply, and the only thing you have to do is to reboot with Ctl+Alt+F2


Version-Release number of selected component (if applicable):


How reproducible:
1) try to open dolphin just after logged in
2) turn on your PC, log in under KDE,  make a walk with your pet during 1 hour and when back, try to use your PC again 

Steps to Reproduce:
1.
2.
3.

Comment 1 alain deraedt 2012-08-17 18:12:25 CEST

Created attachment 2652 [details]
result obtained by typing dolphin on a terminal just after login

Comment 2 Manuel Hiebel 2012-08-18 22:29:23 CEST

seems an nepomuk issue, ideas guys ? 

(please tell me if you don't want to be in my package exception for the kde team)

CC: sysadmin-bugs => balcaen.john, juan.baptiste, lmenut, nicolas.lecureuil, shlomif
Component: Release (media or process) => RPM Packages
Summary: FREEZE after log in and a long term of non use => dolphin freeze after log in and a long term of non use
Source RPM: (none) => kdebase4-runtime

Comment 3 John Balcaen 2012-08-18 22:51:16 CEST

(In reply to comment #2)
> seems an nepomuk issue, ideas guys ? 
Well i can't affirm that nepomuk is the cause here.
It seems that at least soprano is not working as expected but it should not block it.


(In reply to comment #0)
> Description of problem:dolphin freezes just after login; here below I obtain
> when typing dolphin in a terminal:
[...]
> How reproducible:
> 1) try to open dolphin just after logged in
> 2) turn on your PC, log in under KDE,  make a walk with your pet during 1 hour
> and when back, try to use your PC again 
I can't reproduce here with 4.8.5 (& i let my computer running at least 12 hours without me).
Do you have nepomuk enable ?
Do you set up nepomuk to start on a nfs share eventually  ?
(there is some know issues regarding nfs support in kio where kio can hangs completly until nfs came back...)

Comment 4 alain deraedt 2012-08-20 23:14:36 CEST

Nepomuk was enable, and I have disabled it.
Now it seems work better, exactly as the system learnt how to work.
Dolphin no longer freezes just after login, just a bit slow to start; but after 2 or 3 times opening dolphin, it normally works.
It's very strange.
I have not yet tried again to let the system running for 1 hour without using it, because lack of time.
I'll try later and post the result.

Comment 5 alain deraedt 2012-08-25 01:03:16 CEST

now everything fine works, I don't know why... let's cross fingers.

Luc Menut 2013-01-27 00:27:24 CET

Status: NEW => RESOLVED
Resolution: (none) => FIXED