Bug 18935 - /usr/sbin/crda failed with exit code 249
Summary: /usr/sbin/crda failed with exit code 249
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-13 00:57 CEST by Bit Twister
Modified: 2021-02-14 21:26 CET (History)
1 user (show)

See Also:
Source RPM: crda-3.18-7.mga7.src.rpm
CVE:
Status comment:

Attachments
/etc/default/crda file (551 bytes, text/plain)
2016-08-05 21:30 CEST, Bit Twister 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2016-07-13 00:57:31 CEST 
Description of problem:

6_s1:  journal snippet
systemd-udevd[562]: Process '/usr/sbin/crda' failed with exit code 249.

Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. clean install+updates Mageia-6-A_NETWORK_INSTALL-x86_64-DVD.iso
2. journalctl | grep /crda


Guessing /etc/default/crda missing some region code.
Marja Van Waes 2016-07-13 09:02:41 CEST

Assignee: bugsquad => tmb
Source RPM: (none) => crda
CC: (none) => marja11

Comment 1 Bit Twister 2016-08-05 21:30:15 CEST 
Created attachment 8310 [details]
/etc/default/crda file

Workaround. 
Save attachment as /etc/default/crda and change REGDOMAIN= per the instructions.
Bit Twister 2017-01-31 08:51:35 CET

Source RPM: crda => crda-3.18-5.mga6.src.rpm
Status comment: (none) => 6_s2
Summary: 6_s1: '/usr/sbin/crda' failed with exit code 249 => /usr/sbin/crda failed with exit code 249

Bit Twister 2017-01-31 18:28:41 CET

Status comment: 6_s2 => (none)
Keywords: (none) => 6sta2

Bit Twister 2018-09-05 00:21:49 CEST

Source RPM: crda-3.18-5.mga6.src.rpm => crda-3.18-7.mga7.src.rpm

Comment 2 Frédéric "LpSolit" Buclin 2021-02-14 21:26:52 CET 
crda has been removed from Mageia 8. Closing.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.