Hundreds of 'soffice.bin' after startup

Bug #103266 reported by Dmitry Maruschenko
16
Affects Status Importance Assigned to Milestone
oooqs2-kde (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

My operating system is Kubuntu Linux 7.04 (with daily dist-upgrades).

After KDE startup my system slows down and then hungs up totally. 'ps ax' shows me hundreds of 'soffice.bin' processes in memory:

< ... >

7192 ? R
0:00 /bin/sh /usr/lib/openoffice/program/soffice -nologo -nodefault -splash-pipe=5
 7206 ? R 0:00 find /home/admin/.mozilla/firefox -name cert8.db
 7220 ? R
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7221 ? S
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7222 ? S
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5

< ... >

 7237 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7238 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7239 ? R
0:00 /bin/sh /usr/lib/openoffice/program/soffice -nologo -nodefault -splash-pipe=5
 7240 ? R
0:00 /bin/sh /usr/lib/openoffice/program/soffice -nologo -nodefault -splash-pipe=5
 7241 ? S 0:00 /bin/sh /usr/bin/ooffice -nologo -nodefault
 7242 ? S
0:00 /usr/lib/openoffice/program/ooqstart -nologo -nodefault
 7243 ? R
0:00 /usr/lib/openoffice/program/ooqstart -nologo -nodefault
 7244 ? R
0:00 /usr/lib/openoffice/program/ooqstart -nologo -nodefault
 7245 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7246 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7247 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7248 ? S 0:00 head -n 1
 7249 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7250 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7251 ? D

< ... >

0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7295 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5
 7296 ? D
0:00 /usr/lib/openoffice/program/soffice.bin -nologo -nodefault -splash-pipe=5

...and so on. When I am quick enough to do 'killall soffice.bin' before my system is owned by these 'soffice.bin's, I can work as usual. But the same thing can happen during my normal work and I don't know what causes such behaviour.

The same thing was with Kubuntu 6.10.

I have OpenOffice 2.2 installed with oooqs2-kde. KDE resumes last session on startup. 'soffice.bin' is excluded from KDE session management.

Revision history for this message
Harald Sitter (apachelogger) wrote :

gotta report to upstream

Changed in oooqs2-kde:
assignee: nobody → apachelogger
status: Unconfirmed → Confirmed
Revision history for this message
Manu (manu59240) wrote :

same problem on kubuntu 7.04 with oooqs2-kde : distro hangs up after few seconds at start-up.
A "top" showed that soffice.bin ran in multiple instances.

apt-get remove oooqs2-kde resolved the problem.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Bug #50136 came up with a patch, which actually seems to fix the issue. I'll talk to upstream to have a look into it and maybe release a new version.

Revision history for this message
111 (789560) wrote :

The same problem on Kubuntu 7.10, thought the multiple instances often vanished after some minutes. This happens only if the "use openoffice.org 2 quickstart mode" option in oooqs2 is enabled.
Maybe you can add an option to confine how long oooqs2 may wait untill it starts an other openoffice instance?

Revision history for this message
Harald Sitter (apachelogger) wrote :

This package was removed from the archives for upcoming 9.10 release. It is horribly broken and apparently unmaintained. There is little interest to pursue this issue. I recommend to not use oooqs2-kde.

Changed in oooqs2-kde (Ubuntu):
assignee: Harald Sitter (apachelogger) → nobody
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.