[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#871643: marked as done (crda: Process '/sbin/crda' failed with exit code 249)

Your message dated Tue, 18 Jan 2022 06:02:26 +0000
with message-id <[🔎] E1n9hZa-0007Gj-Em@fasolo.debian.org>
and subject line Bug#1003903: Removed package(s) from unstable
has caused the Debian Bug report #871643,
regarding crda: Process '/sbin/crda' failed with exit code 249
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
871643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871643
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: crda
Version: 3.18-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Start of the PC
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
check journalctl
   * What was the outcome of this action?
guy@debian:~$ journalctl | grep /crda
août 10 09:23:16 debian systemd-udevd[252]: Process '/sbin/crda' failed with
exit code 249.
août 10 11:27:56 debian systemd-udevd[14694]: Process '/sbin/crda' failed with
exit code 255.


   * What outcome did you expect instead?
no error for crda
*** End of the template - remove these template lines ***
additional info
root@debian:/lib/udev/rules.d# iw reg get
global
country FR: DFS-ETSI
        (2402 - 2482 @ 40), (N/A, 20), (N/A)
        (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW
        (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
        (57000 - 66000 @ 2160), (N/A, 40), (N/A)

root@debian:/lib/udev/rules.d# cat  /lib/udev/rules.d/85-regulatory.rules
# Runs CRDA for kernel wireless regulatory events.
# For more information see:
# http://wireless.kernel.org/en/developers/Regulatory/CRDA

KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform",
RUN+="/sbin/crda"
root@debian:/lib/udev/rules.d#






-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages crda depends on:
ii  iw                4.9-0.1
ii  libc6             2.24-12
ii  libnl-3-200       3.2.27-2
ii  libnl-genl-3-200  3.2.27-2
ii  libssl1.1         1.1.0f-3
ii  wireless-regdb    2016.06.10-1

crda recommends no packages.

crda suggests no packages.

-- Configuration Files:
/etc/default/crda changed:
REGDOMAIN=FR


-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 4.14+git20191112.9856751-1+rm

Dear submitter,

as the package crda has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1003903

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: