-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Locate plasma panel settings save function in KDE4 code #12
Comments
Please, confirm. |
Ok! I'll do it later. |
Do you mean panel on my custom kde? That may be strange, but I can't find there any panel... |
I guess it is because some components are missing. You can still proceed pp. 1-4 on your main installation. Please, tell me the results. |
I couldn't figure out how to determine the process that makes changes in ~/.kde ... How it should be done? |
It depends on result from p. 3. Please, show me the diff (use Github Gist service). |
Output of diff: https://gist.github.com/mechanician/c873edad177223684ca2 |
So, it's a
will list all processes with open files inside that dir. |
Obtained results are below:
But: to alive panel I had to kill above process and after that resart plasma-desktop. May be there is more correct way to "break" created pipe? |
So, what was the sequence in detail? You tried p.1 and found nothing? This means that process doesn't hold config open, right? Then you tried p.2 and this above result is from p.2? This strange because I see only .lock and no pipe! Anyway, you found what was required. I thought they may be routed config through dbus to a special service and now I see that they modify it directly. There is nothing wrong to kill a process. But, if you're curious, you could feed real config through pipe and see what happens:
I don't think that it will work as expected, because seek() don't work on pipes. But it may unfreeze process and give you a chance to return back normal config. |
I guess I know what's going on with absent pipe in lsof. Maybe open() is blocked unless both ends open it (3 variants: rw-rw, r-w or w-r). So the file was not open yet at that time -- hence no fd in lsof! F.ex. if you did:
After that it may be |
Exactly. Firstly I tried p.1 and there was nothing, so I went to p. 2. As you said, after
|
Great! Regarding p.5 what branch did you compiled? KDE Workspace should contain necessary widget. Try to add it manually:
|
Difficult to say about branсh, but may be the following is what you asked... :
About adding the widget manually: when 'add widget' is clicked nothing happens. |
Please, ensure that files under |
Yes, there are those files:
How to check if the last one is installed to right place and KDE knows about it? While Xephyr was working no any phrases with 'task' occurred in error output .
|
These locations are inside build tree. Where they are inside installation tree? |
|
Can you please examine with P.S. be ready to deal with respawners. KDE4 respawns |
Please, confirm. |
Hi! Sorry for the late answer. |
Great! Welcome back any time! |
do
cp -a ~/.kde /tmp/
right-click on panel, 'Task Manager Settings', invert 'Only show tasks from the current screen' flag, press OK.
compare /tmp/.kde and ~/.kde:
Locate the changes reflected by flag change.
locate the process that does that change. How -- your suggestion. Or you can ask me.
hook on file write: in GDB
b write
, do the change, show the stack trace to me.The text was updated successfully, but these errors were encountered: