Bug 1528215
| Summary: | unable to debug when crash happens | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||||||||
| Component: | anaconda | Assignee: | Dusty Mabe <dustymabe> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | rawhide | CC: | anaconda-maint-list, dustymabe, jonathan, kellin, mkolman, vanmeeuwen+fedora, v.podzimek+fedora, vponcova, wwoods | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2017-12-21 14:50:57 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1370790 [details]
anaconda.log
Created attachment 1370791 [details]
syslog
Created attachment 1370792 [details]
packaging.log
just wondering how I got assigned this bug? (In reply to Dusty Mabe from comment #4) > just wondering how I got assigned this bug? That's definitely wrong - but I also wonder how that happened. This is a duplicate of bug 1526861 - the "Debug" button expect Tmux to run TTY1, so it does not work if Tmux is not there. *** This bug has been marked as a duplicate of bug 1526861 *** (In reply to Martin Kolman from comment #5) > (In reply to Dusty Mabe from comment #4) > > just wondering how I got assigned this bug? > That's definitely wrong - but I also wonder how that happened. This seems to be the cause: https://pagure.io/fedora-infrastructure/issue/6593 |
Created attachment 1370789 [details] screencast Description of problem: Please see the attached screencast for more information,thanks. Version-Release number of selected component (if applicable): Fedora-Workstation-netinst-x86_64-Rawhide-20171220.n.0.iso How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: