Ubuntu
ebox package

Removing ebox does not stop the daemon

Bug #234912 reported by William Lynch
2
Affects Status Importance Assigned to Milestone
ebox (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: ebox

I installed ebox to take a look at it, and removed it about an hour later. However, looking at my process table, I see the following:

root 13281 0.0 3.0 224976 29740 ? Ss 03:11 0:00 /usr/sbin/apache2 -k start -f /var/lib/ebox/conf/apache2.conf
ebox 13283 0.0 4.1 252800 40136 ? S 03:11 0:00 /usr/sbin/apache2 -k start -f /var/lib/ebox/conf/apache2.conf
ebox 13373 0.0 4.1 252540 39944 ? S 03:13 0:00 /usr/sbin/apache2 -k start -f /var/lib/ebox/conf/apache2.conf
ebox 13374 0.1 4.4 257108 42612 ? S 03:13 0:01 /usr/sbin/apache2 -k start -f /var/lib/ebox/conf/apache2.conf
ebox 13375 0.0 4.1 252560 39780 ? S 03:13 0:00 /usr/sbin/apache2 -k start -f /var/lib/ebox/conf/apache2.conf
ebox 13464 0.1 4.3 254132 41504 ? S 03:16 0:01 /usr/sbin/apache2 -k start -f /var/lib/ebox/conf/apache2.conf

Mind you, I've also uninstalled apache2. In my opinion, once eBox was removed, the prerm script should have run the stop script.

Related branches

lp:ubuntu/karmic/ebox
Javier Uruen Val (juruen)
Changed in ebox:
status: New → In Progress
Revision history for this message
Javier Uruen Val (juruen) wrote :

There was an attempt to stop the whole eBox in prerm, but there was a mistake.

I've already committed the fix to upstream. New packages for intrepid will ship this fix.

http://trac.ebox-platform.com/changeset?old_path=trunk&old=10418&new_path=trunk&new=10418

Thanks for your report!

Changed in ebox:
status: In Progress → Fix Committed
Revision history for this message
Javier Uruen Val (juruen) wrote :

Fix in upstream shouldn't change the Ubuntu status. So I'm changing it to confirmed.

Changed in ebox:
status: Fix Committed → Confirmed
Revision history for this message
William Lynch (wlynch) wrote :

I thought Fix committed was the status used to reference that it was fixed upstream, but it's not packaged in ubuntu yet.

https://help.launchpad.net/BugStatuses

Revision history for this message
Javier Uruen Val (juruen) wrote :

I thought so too, but I've been told the opposite on the IRC.

I guess the right thing to do would be adding a watcher for upstream bug using the "also affects" thing.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ebox - 0.12.4-0ubuntu1

---------------
ebox (0.12.4-0ubuntu1) jaunty; urgency=low

  * New upstream release. (LP: #318710, LP: #310045).
  * debian/control:
    - Bump standard version.
    - Depend on an apache2-mpm- rather then apache2 (LP: #225793).
    - Build depend on debconf-updatepo.
  * debian/rules:
    - Call debconf-updatepo from clean target.
  * debian/copyright:
    - Include section about apache-authcookie code.
  * debian/ebox.postrm:
    - Remove ebox log files (LP: #129738).
  * debian/ebox.prerm:
    - Stop ebox when the package is removed. (LP: #234912)
  * debian/watch:
    - add watch file.
  * debian/patches/01_add_apache_authcookie.dpatch
    - Patch to backport AuthCookie authentication for jaunty (LP: #255368).
  * debian/patches/02_dbus_gconf.dpatch
    - Patch to make gconf classes work with new gconf using dbus
      (LP: #314606).
  * debian/patches/03_js_libraries.dpatch
    - Patch to use javascript libraries that are already package for
      Jaunty

 -- Mathias Gug <email address hidden> Mon, 26 Jan 2009 18:21:18 -0500

Changed in ebox:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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