Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1895896 - Color is not reset if crontab ends with a comment line
Summary: Color is not reset if crontab ends with a comment line
Keywords:
Status: CLOSED DUPLICATE of bug 1838180
Alias: None
Product: Fedora
Classification: Fedora
Component: cronie
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matej Mužila
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-09 11:27 UTC by Jonathan Wakely
Modified: 2021-02-11 15:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-11 15:17:25 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jonathan Wakely 2020-11-09 11:27:39 UTC 
Description of problem:

'crontab -l' changes terminal colour for comment lines, but doesn't reset it.


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

cronie-1.5.5-2.fc32.x86_64

How reproducible:

Always

Steps to Reproduce:
1. crontab -l > /tmp/crontab
2. echo '# this is a comment' >> /tmp/crontab
3. crontab /tmp/crontab
4. crontab -l

Actual results:

The terminal colour is changed.

Expected results:

My usual terminal colours are used.

Additional info:

This was fixed upstream but there hasn't been a new release yet:
https://github.com/cronie-crond/cronie/issues/45
Comment 1 Wolfgang Denk 2021-02-11 07:25:46 UTC 
same problem still present in Fedora 33:

cronie-1.5.5-4.fc33.x86_64
Comment 2 Wolfgang Denk 2021-02-11 07:28:00 UTC 
See also bug #1838180
Comment 3 Jonathan Wakely 2021-02-11 15:17:25 UTC 
It's a dup, thanks.

*** This bug has been marked as a duplicate of bug 1838180 ***
Note You need to log in before you can comment on or make changes to this bug.