Setserial's autosave doesn't work
Bug #46994 reported by
fubarbundy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
setserial (Debian) |
Fix Released
|
Unknown
|
|||
setserial (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
To reproduce: run dpkg-reconfigure setserial and change it to autosave once or autosave always. Run setserial /dev/ttyS0 to show the current state of your serial port (change device node as appropriate). This should usually show its UART status as 16550A. Now run setserial /dev/ttyS0 uart none and reboot.
Result: setserial /dev/ttyS0 still shows uart 16550A
Expected result: setserial /dev/ttyS0 should show uart none as it has been configured to always autosave the last configuration of the serial port and restore it on startup.
Changed in setserial: | |
assignee: | nobody → craig-decafbad |
Changed in setserial: | |
assignee: | craig-decafbad → nobody |
Changed in setserial (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
To reproduce: run dpkg-reconfigure setserial and change it to autosave once or autosave always. Run setserial /dev/ttyS0 to show the current state of your serial port (change device node as appropriate). This should usually show its UART status as 16550A. Now run setserial /dev/ttyS0 uart none and reboot.
Result: setserial /dev/ttyS0 still shows uart 16550A
Expected result: setserial /dev/ttyS0 should show uart none as it has been configured to always autosave the last configuration of the serial port and restore it on startup.