[kde-solaris] Re: artsd/artswrapper

[Stefan Teleman]

Hi!

About artsd (and artswrapper): are they installed setuid root ? if 
not, they should -- otherwise they will keep complaining. and /tmp 
and /opt should be mounted to allow setuid.

the directory /tmp/mcop-${USER} -- if the ownerships are not right, 
you can just change their ownerships to their rightful owner (as 
root).

Let me know. :-)

--Stefan

-----

On Wednesday 01 October 2003 07:56, michael.szengel at philips.com wrote:
> Hi Stefan,
>
> I wonder why you have ~40 MB for every kdeinit on your Linux box
> when I see only ~18 MB at my (SuSE 8.2, KDE 3.1).
> Just curious, if your final binaries contain debugging code or not
> and how well equipped is you workstation. I have 640 MB RAM and a
> Gig swap but still run into memory shortage problems, although I
> run much less apps than usually.
>
> And I do not think, kbear has a problem but rather klauncher. From
> my understanding, klauncher dies when it loses the communication
> with the client app and I think it should not.
> Here is a snippet from the log with the important lines.
>
> kio_file: ========= LIST file:/cw/RPM/PKG =========
> kio_file: ============= COMPLETED LIST ============
> kio_file: =============== BYE ===========
> kio_file: Put
> /cw/RPM/PKG/pinfo-0.6.7-1.3.0.sparc64-solaris2.8-cw.rpm kio_file:
> Appending .part extension to
> /cw/RPM/PKG/pinfo-0.6.7-1.3.0.sparc64-solaris2.8-cw.rpm
> kio_file: Put /cw/RPM/PKG/png-1.2.5-1.3.0.sparc64-solaris2.8-cw.rpm
> kio_file: Appending .part extension to
> /cw/RPM/PKG/png-1.2.5-1.3.0.sparc64-solaris2.8-cw.rpm
> kdeinit: PID 26152 terminated.
> Sep 18 11:43:22 regulus last message repeated 12 times
> kio_file: ========= LIST file:/cw/RPM/PKG =========
> kio_file: ============= COMPLETED LIST ============
> kio_file: =============== BYE ===========
> kparts: d3c30 emitting activePartChanged 3a2840
> kparts: DockMainWindow::createGUI for KBearFileSysPart
> kparts: deactivating GUI for KBearFileSysPart
> kparts: d3c30 emitting activePartChanged 183458
> kparts: DockMainWindow::createGUI for KBearFileSysPart
> kparts: deactivating GUI for KBearFileSysPart
> kparts: d3c30 emitting activePartChanged 3a2840
> kparts: DockMainWindow::createGUI for KBearFileSysPart
> kparts: deactivating GUI for KBearFileSysPart
> kdeinit: Got EXEC_NEW 'kio_kbearftp' from launcher.
> kdeinit: fork() failed!
>
> : Not enough space
>
> klauncher: Exiting on read_socket errno: 29
> kio_file: Done
> DCOP aborting call from 'kbear' to 'klauncher'
> DCOP: unregister 'klauncher'
> kbear: ERROR: ERROR 3: couldn't create slave : Can't talk to
> klauncher kio_file: FileProtocol::stat details=2
> kbear: ERROR: ERROR 3: couldn't create slave : Can't talk to
> klauncher kbear: ERROR: ERROR 3: couldn't create slave : Can't talk
> to klauncher kbear: ERROR: ERROR 3: couldn't create slave : Can't
> talk to klauncher kbear: ERROR: ERROR 3: couldn't create slave :
> Can't talk to klauncher kbear: ERROR: ERROR 3: couldn't create
> slave : Can't talk to klauncher kbear: ERROR: ERROR 3: couldn't
> create slave : Can't talk to klauncher kbear: ERROR: ERROR 3:
> couldn't create slave : Can't talk to klauncher
>
>
> I still have a problem with artsd. It is complaining about access
> rights to /tmp/mcop-user.
> This directory is owned by root and not me. But it has been created
> during session startup and, hence, I can not fix it with a chmod
> line in startkde.
> Any suggestions how to fix this?
>
>
>
> Wish you a nice day
> Michael
>
>
>
>
>
>
>
>
>
>
> Stefan Teleman <Stefan.Teleman at morganstanley.com>
> 09/25/2003 03:46 PM
> Please respond to Stefan.Teleman
>
>
>         To:     Michael Szengel/DRS/SC/PHILIPS at EMEA1
> kde-solaris at mail.kde.org
>         cc:
>         Subject:        memory consumption
>         Classification:
>
>
>
> Hi
>
> ~40MB for a kdeinit instance is normal. That's what it is on my
> box, and
> that's about what it is on my Linux box as well running 3.0.5a.
>
> Did you by any chance save kbear in a session, and then restore the
> session
> at login. this could very well be a kbear bug. i sometimes see this
> kbear
> problem on Linux KDE. if it is a kbear bug, i would need some
> documented
> behavior before i can submit a bug to kbear, otherwise it will be
> classified
> as "UNCONFIRMED". :-)
>
> --Stefan

-- 
Stefan Teleman          'Nobody Expects the Spanish Inquisition'
steleman at nyc.rr.com                          -Monty Python