Open ff2000 opened 11 years ago
Well this is important... I dont know what top() is...
I need the following information:
Should have been top not top() - hope you know that ;) "Nothing obvious" == "no process with with unexpected high CPU load"
Version: the most recent releases available when I reported this: WorkFlow-0.4.1 kde-4.10.1 Gentoo
Graphics card: Intel HD3000 (i7 2600K) xorg-server-1.13.1, xf86-video-intel-2.21.4
Only disabling the kwin script and using the plasmoid works fine (no delay) (thought my last sentence was clear enough ;))
Στις 26/03/2013 06:48 μμ, ο/η ff2000 έγραψε:
Should have been top not top() - hope you know that ;) "Nothing obvious" == "no process with with unexpected high CPU load"
Version: the most recent releases available when I reported this: WorkFlow-0.4.1 kde-4.10.1 Gentoo
Graphics card: Intel HD3000 (i7 2600K) xorg-server-1.13.1, xf86-video-intel-2.21.4
Only disabling the kwin script and using the plasmoid works fine (no delay) (thought my last sentence was clear enough ;))
Ok...
is that the first kwin script you are using or running in your system?
is that the first kwin script you are using or running in your system?
No. Also running "Opacity menu".
No. Also running "Opacity menu".
- Ok, just to be sure try using only the WorkFlow script and nothing else from kwin scripts
- Try using the: www.opentoolsandspace.org/Art/tests/kwin-script-samegame.kwinscript and disable anything else. It is just the samegame in a KWin Script it can be triggered with BottomRight corner. It crashes on logging out the kwin but you can uninstall it afterwards. What we need to know if it creates the same issue in logging in.
- Ok, just to be sure try using only the WorkFlow script and nothing else from kwin scripts Enabling/Disabling Opacity Menu does not have any influence on startup time when WorkFlow is running.
- Try using the: www.opentoolsandspace.org/Art/tests/kwin-script-samegame.kwinscript samegame does not delay Login time. (But Quit-Button does not work, need to kwin --replace)
(btw: already had that sometimes before. Your krinscript was a gz-compressed tarball and my kde can't import those; have to uncompress and rezip... Any idea what I am missing?)
But I have some additional information: Can trigger this by simply running kwin --replace. tail -f .xsession-errors gave me this before the hang: kwin(5370) KActivities::InfoPrivate::initializeCachedData: Locking mutex for name kwin(5370) KActivities::InfoPrivate::initializeCachedData: Locking mutex for icon
and that after: kwin(5370) KActivities::InfoPrivate::nameCallFinished: Unlocked mutex kwin(5370) waitForCallFinished: Trying to lock mutex kwin(5370) KActivities::Info::name: Returning name "Desktop" kwin(5370) KActivities::InfoPrivate::iconCallFinished: Unlocked mutex kwin(5370) waitForCallFinished: Trying to lock mutex kwin(5370) KActivities::Info::icon: Returning icon ""
Ok.. :) I wouldnt have debugged that one.... It appears that because activitymanager is not ready to provide information for the activities. KWin was waiting for these information because of my script. Try to install the workflow plasmoid from branch "0.4.x-loginissue" . I have made asynchronous calls for accessing activities in initialization, that should probably fix that issue... If it fixes it it will also be merged to version 0.4.2
(btw: already had that sometimes before. Your krinscript was a gz-compressed tarball and my kde can't import those; have to uncompress and rezip... Any idea what I am missing?) well, sometimes the way I am creating the tar.gz files from dolphin it creates that issue. I dont know what's wrong but I forgot to check it out before publishing in order to create again... :)
In general I am not that good with CLI, so your command:
kwin --replace. tail -f .xsession-errors
is it correct? the dot after replace confuses me... :)
On Wednesday 27 March 2013 05:59:05 Michail Vourlakos wrote:
Try to install the workflow plasmoid from branch "0.4.x-loginissue" Installed from that branch, but did not reduce login time. I also got a nasty crash:
Application: WorkFlow Workarea Manager (workareamanagerd), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f975e145780 (LWP 16868))]
Thread 2 (Thread 0x7f975ba64700 (LWP 16871)): [KCrash Handler]
apps-dbus-1.6.8-r1/work/dbus-1.6.8/dbus/dbus-pending-call.c:692
/var/tmp/paludis/sys-apps-dbus-1.6.8-r1/work/dbus-1.6.8/dbus/dbus- connection.c:2374
at qdbus_symbols_p.h:309
at qdbusintegrator.cpp:1781
(this=0x2315a60) at qdbuspendingcall.cpp:245
(this=
watcher=
/var/tmp/paludis/kde-base- kactivities-4.10.1/work/kactivities-4.10.1/src/lib/core/consumer.cpp:162
/home/franz/src/kde/plasmoids/workflow/workflow- project/qdbus/WorkareaManager.cpp:83
QStringList ()(KActivities::Controller), KActivities::Controller*>::runFunctor (this=0x23153b0) at /usr/include/qt4/QtCore/qtconcurrentstoredfunctioncall.h:267
/usr/include/qt4/QtCore/qtconcurrentrunbase.h:106
/usr/include/qt4/QtCore/qtconcurrentrunbase.h:97
concurrent/qthreadpool.cpp:107
thread/qthread_unix.cpp:338
../sysdeps/unix/sysv/linux/x86_64/clone.S:115
Thread 1 (Thread 0x7f975e145780 (LWP 16868)):
/lib64/libpthread.so.0
thread/qwaitcondition_unix.cpp:86
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
msecs=-1) at concurrent/qthreadpool.cpp:298
__in_chrg=
__in_chrg=
QGlobalStaticDeleter
Ok a new commit then...
I disabled asychronous call for workareamanagerd. It shouldnt crash now even though in my system doesnt crash at all...
Tell me what will happen with the messages you mentioned before about:
kwin(5370) KActivities::InfoPrivate::initializeCachedData: Locking mutex for name kwin(5370) KActivities::InfoPrivate::initializeCachedData: Locking mutex for icon
Oh... and please make a restart in order to activate the new workareamanagerd
Activating the KWin script and the next login takes longer. I watched with top() and nothing obvious happens, feels like a "sleep()"... I would like to use this instead of the plasmoid, find the popup not so pleasing...