~sircmpwn/aerc2#331:
Panic when trying to open unread message

Whenever I try to open an unread message, aerc panics with the following output:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x5a7d75]

goroutine 92 [running]:
bufio.(*Scanner).Scan(0xc00026ef40, 0xc0002c4000)
    /usr/lib/go/src/bufio/scan.go:213 +0x75
git.sr.ht/~sircmpwn/aerc/widgets.(*PartViewer).attemptCopy.func4(0xc000562000, 0xc0002e2d60)
    /home/philipp/.cache/pikaur/build/aerc/src/aerc-0.3.0/widgets/msgviewer.go:591 +0x574
created by git.sr.ht/~sircmpwn/aerc/widgets.(*PartViewer).attemptCopy
    /home/philipp/.cache/pikaur/build/aerc/src/aerc-0.3.0/widgets/msgviewer.go:565 +0x144

Opening an already read message works without problems. I run aerc version 0.3.0 installed from the AUR.

Status
REPORTED
Submitter
~ferruck
Assigned to
No-one
Submitted
13 days ago
Updated
30 minutes ago
Labels
No labels applied.

~labrat 13 days ago

Which backend do you use and which email provider if it's IMAP?

Outlook's exchange server has various issues

~ferruck 13 days ago

Yes, it's IMAP and the provider is your-server.de (Hetzner), so no Outlook here.

~ferruck an hour ago

I just confirmed that this issue is still present with current HEAD.

Since this is a real show-stopper for me, I just wanted to ask if there's anything I can do to help fixing this issue. Can I provide some more detailed logs (and if yes, how)?

~labrat 30 minutes ago

Well, if you can reproduce it locally it would be helpful to actually debug the code (and then fixing it ;) )

If you don't want to do that, you can get logs by redirecting stdout to a file aerc > aerc.log

Does this always happen or only sometimes?

Register here or Log in to comment, or comment via email.