Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
alexkOffline
1 Post subject: Dolphin won't launch or very delayed launch  PostPosted: 16.10.2012, 03:07



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
Since DU last night, Dolphin takes a couple of minutes to start up, exhibits long lags in some initial operations such as file renaming and reports this on startup:
      Code:
dolphin(11217)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "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."

dolphin(11217)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:


      Code:
$ infobash -v3
Host/Kernel/OS  "AK1" running Linux 3.6-2.slh.3-aptosid-amd64 x86_64 [ sidux 2009-02 Αιθήρ - kde-full - (200907141427) ]
CPU Info        4x Intel Core i5-2500K @ 6144 KB cache flags( sse3 ht nx lm vmx ) clocked at [ 3301.000 MHz ]
Videocard       Intel 2nd Generation Core Processor Family Integrated Graphics Controller  X.Org 1.12.4  [ 1280x1024@60.0hz ]
Network cards   Intel 82579V Gigabit
Processes 188 | Uptime 16:03 | Memory 1410.7/7900.1MB | HDD WDC WD3200AAKS-0 Size 320GB (23%used) | Client Shell | Infobash v3.45


Last edited by alexk on 10.02.2013, 20:34; edited 7 times in total
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
piperOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 16.10.2012, 18:28
Moderator


Joined: 2010-09-11
Posts: 480
Location: cheektowaga, ny
Status: Offline
What happens when you run (as user) in konsole
      Code:
dbus-launch --exit-with-session dolphin

_________________
debian sid | apt-get into it
 
 View user's profile Send private message  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 16.10.2012, 23:47



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
"dbus-launch --exit-with-session dolphin" seems to work fine and so does "dbus-launch dolphin" but now, after another DU, if I try just "dolphin" on the cli or use the menu command, Dolphin doesn't open at all, even after several minutes. I'm also getting major latency in kmenuedit making it almost unusable and also had the whole KDE desktop become unresponsive, though it responded to Ctrl-Alt-Backspace to restart X.
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 17.10.2012, 12:06



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
Sporadic issue - after a small DU and then a reboot this morning, everything works fine. This happened once yesterday evening, as well. I was also having a lot of trouble logging out, having to kill sessions.
      Code:
$ tail /var/log/apt/history.log

Start-Date: 2012-10-16  22:22:07
Commandline: apt-get dist-upgrade
Upgrade: logrotate:amd64 (3.8.3-1, 3.8.3-3), libapt-inst1.5:amd64 (0.9.7.5, 0.9.7.6), apt-utils:amd64 (0.9.7.5, 0.9.7.6), apt:amd64 (0.9.7.5, 0.9.7.6), libapt-pkg4.12:amd64 (0.9.7.5, 0.9.7.6), timidity:amd64 (2.13.2-40, 2.13.2-40.1), vlc-data:amd64 (2.0.3-dmo4, 2.0.4-dmo1)
End-Date: 2012-10-16  22:22:57
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 18.10.2012, 15:50



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
Problem reappeared yesterday evening, then disappeared after another minor DU, a reinstall of kde-runtime package and reboot into previous 3.5 slh kernel.
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 20.10.2012, 00:18



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
This issue seems to have been resolved, currently using 3.6-2.slh.3 kernel again. I'll mark this thread solved (again).
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 05.11.2012, 04:08



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
This issue keeps on coming back, again today on a fully upgraded system with latest 3.6-5 kernel. It's always after one or more sleep cycles and I think has always been with two active logins. The issue only ever seems to affect one login out of the two, but varies from one to the other (today on both at different times). Dolphin won't launch or takes 50 seconds or more to launch, even with dbus-launch. KDE file dialogs in Libreoffice take 25 seconds or more to open and 25 s to close; LibreOffice native dialogs function normally. K-button can become unresponsive, kmenuedit and kwrite sometimes don't launch. Sleep and Log out on the affected logins don't work. A reboot solves the issue temporarily, as does a restart of KDE. I have also tried reinstalling kdelibs.
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 06.11.2012, 01:38



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
      Code:
$ dolphin
dolphin(7991)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "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."

QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permission denied
QFileSystemWatcher: failed to add paths: /var/lib/samba/usershares
dolphin(7991)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(7991)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(7991)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(7991)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(7991)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(7991)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
maureen@AK1:~$ dbus-launch dolphin
kdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
QDBusObjectPath: invalid path ""
QObject::connect: Cannot connect (null)::deviceFound(Device*) to BlueDevilDaemon::deviceFound(Device*)
QObject::connect: Cannot connect QTimer::timeout() to (null)::stopDiscovery()
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kded(8104)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.6'
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
No outputs have backlight property
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kded(8104) PowerDevilUPowerBackend::brightness: org.kde.powerdevil.backlighthelper.brightness failed
Object::connect: No such signal QDBusAbstractInterface::Changed()
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permission denied
QFileSystemWatcher: failed to add paths: /var/lib/samba/usershares
dolphin(8093)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
piperOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 06.11.2012, 06:47
Moderator


Joined: 2010-09-11
Posts: 480
Location: cheektowaga, ny
Status: Offline
hmm, should look like this
      Code:
piper@x1:~$ dolphin
dolphin(25228)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(25228)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(25228)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(25228)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(25228)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(25228)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
piper@x1:~$
and
      Code:
piper@x1:~$ dbus-launch dolphin
kdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(29106) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(29106) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(29106) kdemain: Emitting notifyDatabaseChanged ()
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Object::connect: No such signal QDBusAbstractInterface::Changed()
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.5'
kded(29105)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(29086)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(29086)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(29086)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(29086)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(29086)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(29086)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
piper@x1:~$


perhaps if your running samba or blutooth device(s) this might be a clue
      Code:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permission denied
QFileSystemWatcher: failed to add paths: /var/lib/samba/usershares
and also
      Code:
Cannot connect (null)::deviceFound(Device*) to BlueDevilDaemon::deviceFound(Device*)
      Code:
powerdevil.backlighthelper.brightness failed


all i can think of at the moment

_________________
debian sid | apt-get into it
 
 View user's profile Send private message  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 25.11.2012, 20:25



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
I'm still having this problem regularly, always after a few wake-from-suspend-to-RAM cycles, again today, without bluetooth installed and having resolved the samba issue by adding the user to sambashare group. I don't recall ever having this problem before October. I'm still getting the "kded(xxxx) PowerDevilUPowerBackend::brightness: org.kde.powerdevil.backlighthelper.brightness failed" message, also in .xsession-errors. I also seem to get the following message in .xsession-errors every time I open Dolphin from the K-menu:
      Code:
plasma-desktop(4593)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "/usr/share/applications/kde4/dolphin.desktop" not found
Failed to find service for KUrl("file:///usr/share/applications/kde4/dolphin.desktop")

      Code:
$ cat /usr/share/applications/kde4/dolphin.desktop
[Desktop Entry]
Name=Dolphin
Name[af]=Dolphin
Name[ar]=دولفين
...
Name[en_GB]=Dolphin
Name[eo]=Dolphin
Name[es]=Dolphin
...
Name[wa]=Dolphin
Name[x-test]=xxDolphinxx
Name[zh_CN]=Dolphin
Name[zh_TW]=Dolphin
Exec=dolphin %i -caption "%c" %u
Icon=system-file-manager
Type=Application
X-DocPath=dolphin/index.html
Categories=Qt;KDE;System;FileManager;
GenericName=File Manager
GenericName[af]=Lêerbestuurder
GenericName[ar]=مدير الملفات
...
GenericName[de]=Dateimanager
GenericName[el]=Διαχειριστής αρχείων
GenericName[en_GB]=File Manager
GenericName[eo]=Dosieradministrilo
GenericName[es]=Gestor de archivos
...
GenericName[zh_TW]=檔案管理程式
Terminal=false
MimeType=inode/directory;
InitialPreference=10
alex@AK1:~$ apt-file search /usr/share/applications/kde4/dolphin.desktop
dolphin: /usr/share/applications/kde4/dolphin.desktop

Ctrl+Alt+Backspace to go back to the KDM login always solves this issue, until a few more wake-from-suspend cycles brings it back.
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 26.11.2012, 18:14



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
I reset KDE settings in ~/.kde on one login and have purged and reinstalled all related KDE/QT packages that I can think of over the last month, including a number more yesterday. I haven't yet thoroughly tested on a regular user login, but on a test login with default KDE settings, with no other active logins, I wasn't able to reproduce the problem yesterday, after several suspend-to-RAM cycles.
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
slhOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 26.11.2012, 18:27



Joined: 2010-08-25
Posts: 737

Status: Offline
Your loopback (ip addr list lo) interface is up?
 
 View user's profile Send private message  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 27.11.2012, 03:40



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
Yes.

      Code:
# ip addr list lo
1: lo: (LOOPBACK,UP,LOWER_UP) mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

(Had to substitute () for <>)
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
slhOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 27.11.2012, 21:56



Joined: 2010-08-25
Posts: 737

Status: Offline
That looks fine.

In general a missing/ misconfigured loopback device does cause slow (starting and executing) applications, of course that isn't the only potential cause.

To debug this further, it might help to create a new user for testing - in order to rule out an affected local configuration.
 
 View user's profile Send private message  
Reply with quote Back to top
alexkOffline
Post subject: RE: Dolphin K*TimeZone* issue  PostPosted: 02.12.2012, 20:07



Joined: 2010-10-01
Posts: 185
Location: Bay state
Status: Offline
I did recreate a "test" user with default settings. However, I am not able to reproduce this problem on our two regular user logins at the moment, after quite a few sleep cycles. I did reset one of these logins to default .kde KDE settings a week ago. I'll wait a while longer before marking this issue as solved, as I've already had to undo that a couple of times.

This issue had been affecting Dolphin but also all KDE file dialogs in particular, such as in LibreOffice (with libreoffice-kde) or Kwrite, which would take 20 or more seconds to open at the same time that Dolphin would take 50 seconds or more to launch.
 
 View user's profile Send private message Yahoo Messenger  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio