Now I had a bit time to observe this bug deeper. Mentioned error is because 
apport isn't running. Well, no problem so far as I tried to start apport. But 
nothing - no message, no apport. Had a look into init script file - ok: there's 
a file under default which is originally set to disable apport (first matter! 
think of common users!). Right - I enabled to start apport, but got only the 
following error during start-up process:
 * Starting automatic crash report generation: apport                           
                                                                             
/etc/init.d/apport: 24: runlevel: not found
exit: 24: Illegal number: Starting

What is that illegal number about to do?? What does it tell me? Where is
it coming from?

Ok - if nothing helps one step usually always helps out: remove with apt-get 
and purge everything, than reinstall. But surprise:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
apt-get --purge remove apport
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  apport*
0 upgraded, 0 newly installed, 1 to remove and 5 not upgraded.
1 not fully installed or removed.
After this operation, 553kB disk space will be freed.
Do you want to continue [Y/n]? Y
dpkg: error processing apport (--purge):
 Package is in a very bad inconsistent state - you should
 reinstall it before attempting a removal.
Errors were encountered while processing:
 apport
E: Sub-process /usr/bin/dpkg returned an error code (1)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++

Damn - I was so close. Ok, dpkg wants me to reinstall and so I tried
with no better result:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
apt-get --reinstall install apport
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Suggested packages:
  apport-gtk apport-qt python-launchpadlib
The following packages will be upgraded:
  apport
1 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
1 not fully installed or removed.
Need to get 0B/113kB of archives.
After this operation, 0B of additional disk space will be used.
Lese Changelogs... Fertig
(Reading database ... 268384 files and directories currently installed.)
Preparing to replace apport 1.0-0ubuntu5 (using 
.../apport_1.0-0ubuntu5.2_all.deb) ...
 * Stopping automatic crash report generation: apport                           
                                                                             
/etc/init.d/apport: 24: runlevel: not found
exit: 24: Illegal number: Stopping
invoke-rc.d: initscript apport, action "stop" failed.
dpkg: warning - old pre-removal script returned error exit status 2
dpkg - trying script from the new package instead ...
 * Stopping automatic crash report generation: apport                           
                                                                             
/etc/init.d/apport: 24: runlevel: not found
exit: 24: Illegal number: Stopping
invoke-rc.d: initscript apport, action "stop" failed.
dpkg: error processing /var/cache/apt/archives/apport_1.0-0ubuntu5.2_all.deb 
(--unpack):
 subprocess new pre-removal script returned error exit status 2
 * Starting automatic crash report generation: apport                           
                                                                             
/etc/init.d/apport: 24: runlevel: not found
exit: 24: Illegal number: Starting
invoke-rc.d: initscript apport, action "start" failed.
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/apport_1.0-0ubuntu5.2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++

There's no way in and no way out and I don't have a clue about this "runlevel: 
not found" stuff. I'm far from a newbix, but that's totally new to me.
So what to do here?

-- 
[Jaunty] apport is not starting
https://bugs.launchpad.net/bugs/369670
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to