signal handler prevents apport crash reporting

Bug #145653 reported by Alexander Sack on 2007-09-27
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Alexander Sack

Bug Description

Binary package hint: network-manager

the nm signal handler catches crash signal and prevents apport crash reporting.

for gutsy final we don't want catch the following signals in src/nm-logging.c:

                case SIGSEGV:
                case SIGBUS:
                case SIGILL:
                case SIGABRT:
                        nm_warning ("Caught signal %d. Generating backtrace...", signo);
                        nm_logging_backtrace ();
                        exit (1);

Alexander Sack (asac) on 2007-09-27
Changed in network-manager:
assignee: nobody → asac
importance: Undecided → High
status: New → In Progress
Alexander Sack (asac) on 2007-10-02
Changed in network-manager:
status: In Progress → Fix Committed
Alexander Sack (asac) wrote :

network-manager (0.6.5-0ubuntu15) gutsy; urgency=low

  * debian/patches/41z_lp138217_use_timeout_to_schedule_activation.patch,series:
    don't use idle_source to schedule activation, but rest a bit by using a
    timeout_source with 250ms delay (LP: #138217).
  * debian/network-manager.postinst: sleep 2 seconds after
    (LP: #146757).
  * debian/patches/41w_lp145683_cancel_scan_in_supplicant_cleanup.patch,series: first part
    for lp145683 - cancel pending scans on terminate (LP: #145683).
  * debian/patches/41wa_lp145683_wpa_ctrl_check_select_result_for_error.patch,series:
    second part to fix lp145683; test select result for errors (in case of
    TERMINATE) (LP: #145683).
  * debian/patches/41y_queue_if_dbus_name_is_taken_on_startup.patch,series: make
    restart of network manager more failsafe and even allow to take over name
    ownership. When ownership is taken over (dbus signal |NameLost| received), we
    shutdown cleanly by sending |X| through |nm_shutdown_pipe| (LP: #85113).
  * debian/patches/41x_lp145653_reraise_fatal_signals.patch: re-raise fatal
    signals (LP: #145653).

 -- Alexander Sack <email address hidden> Tue, 02 Oct 2007 13:32:50 +0200

Changed in network-manager:
status: Fix Committed → Fix Released
Matt Zimmerman (mdz) wrote :

This has regressed in Intrepid; the patch appears to have been dropped.

Changed in network-manager:
milestone: ubuntu-7.10-rc → none
status: Fix Released → Confirmed
Alexander Sack (asac) wrote :

new patch landed in bzr today.

Changed in network-manager:
status: Confirmed → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 0.7~~svn20080818t061112+eni0-0ubuntu1

network-manager (0.7~~svn20080818t061112+eni0-0ubuntu1) intrepid; urgency=low

  * fix LP: #255844 - add update-notifier-common to the Depends
    - update debian/control
  * fix LP: #255958 - nm-tool broken on nm 0.7; we properly run make install
    for test/ source directory with proper DESTDIR in
    binary-install/network-manager:: cdbs target; in turn we dont explicitly
    install the nm-tool binary in network-manager.install
    - update debian/rules
    - update network-manager.install
  * adjust patches for new upstream codebase
    - update debian/patches/05-debian_backend.patch
    - update debian/patches/50_gcc43.patch
    - remove debian/patches/19_interfaces_can_have_more_than_one_instance.patch
    - update debian/patches/series
  * adjust files installed in libnm-util-dev package: we add
    nm-setting-ip6-config.h and we remove nm-setting-vpn-properties.h from
    and to the .install list
    - update debian/libnm-util-dev.install
  * add gtk-doc-tools to build-depends
    - update debian/control
  * Fix LP: #145653 - "signal handler prevents apport crash reporting"
    - add debian/patches/70_lp145653_no_sigaction_for_crashes.patch
    - update debian/patches/series

 -- Alexander Sack <email address hidden> Mon, 18 Aug 2008 21:27:59 +0200

Changed in network-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers