Bug 118735 - DCOP call reparseConfiguration doesn't work.
Summary: DCOP call reparseConfiguration doesn't work.
Status: RESOLVED NOT A BUG
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-20 18:40 UTC by Kurt Hindenburg
Modified: 2005-12-21 17:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Hindenburg 2005-12-20 18:40:03 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Compiled From Sources
OS:                Linux

dcop konsole-$PID MainApplication-Interface reparseConfiguration 
does not actually call the reparseConfiguration().  The reparseConfiguration does work, tested.


Strange, use
% dcop konsole-$PID konsole reparseConfiguration
which works.
Comment 1 Kurt Hindenburg 2005-12-20 18:42:15 UTC
Han, did 
% dcop konsole-$PID MainApplication-Interface reparseConfiguration 

actually work in KDE 3.4.x? 

The correct call is 
% dcop konsole-$PID konsole reparseConfiguration 
which works for me.
Comment 2 Kurt Hindenburg 2005-12-21 17:58:59 UTC
I'm getting quite confused.
The following happened: I upgraded to kde-3.5.0 using the RPMS from the 
kde-redhat project, for Fedora Core 4.
dcop konsole-$PID konsole reparseConfiguration
no longer worked. Of that I'm certain.
I'm almost certain that reparseConfiguration no longer showed up in kdcop 
under konsole but only under MainApplication-Interface. In fact, I'm almost 
certain that the konsole entry was missing.
That's why I changed my command.

Then I got the sources, to try my lock with gdb. These source were a newer 
release. I had no luck debugging, but the original
dcop konsole-$PID konsole reparseConfiguration
worked again.
These RPMS are quite heavily patched, and I guess, also by the rapid 
appearance of a newer release, that something had gone wrong there.

I'm sorry to have bothered you all, about a clearly downstream problem.

Thanks,

Han Holl