Bug 12263 - Bug command fails in the installer tty2
Summary: Bug command fails in the installer tty2
Status: RESOLVED DUPLICATE of bug 14435
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-10 15:18 CET by claire robinson
Modified: 2015-02-17 21:50 CET (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
bug do not work, plus "too many levels of recursion in macro expansion" during install (555.14 KB, application/x-gzip)
2014-02-03 11:49 CET, Morgan Leijström
Details

Description claire robinson 2014-01-10 15:18:27 CET
Classic 4RC DVD 64 Build 5 new today (Date.txt 10/1/14)

Investigating bug 10722 required grabbing some logs during an upgrade.

Inserted a vfat usb stick and entered 'bug' into tty2 but it fails apparently unable to locate the usb stick.

See photo for log on tty3
https://dl.dropboxusercontent.com/u/4147101/mga4rc/DSC02476.JPG

I was able to manually mount the USB stick to rescue the logs.

Reproducible: 

Steps to Reproduce:
claire robinson 2014-01-10 15:19:04 CET

CC: (none) => ennael1, mageia
Whiteboard: (none) => 4RC

Comment 1 Manuel Hiebel 2014-01-13 00:21:27 CET
if I use "bug sdb"

I get "output in file /fd/report.bug failed: read only-file system"

Hardware: i586 => All

Comment 2 Morgan Leijström 2014-02-03 11:28:48 CET
I get the same as claire on 4 final, network install.
(The five last lines starting with *error)

Manuel: you forgot a detail: "bug sdb1" works
(bug needs a partition with one of the supported file systems)

CC: (none) => fri
Whiteboard: 4RC => (none)

Comment 3 Morgan Leijström 2014-02-03 11:49:42 CET
Created attachment 4923 [details]
bug do not work, plus "too many levels of recursion in macro expansion" during install
Comment 4 Rémi Verschelde 2015-02-17 21:50:50 CET
The bug in comment 0 is superseded by bug 14435.
Maybe a separate bug report should be filed for the issue in comment 1 though, if it's still reproducible.

*** This bug has been marked as a duplicate of bug 14435 ***

Status: NEW => RESOLVED
CC: (none) => remi
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.