this post was submitted on 17 Aug 2023
22 points (95.8% liked)
linux4noobs
1340 readers
1 users here now
linux4noobs
Noob Friendly, Expert Enabling
Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.
Seeking Support?
- Mention your Linux distro and relevant system details.
- Describe what you've tried so far.
- Share your solution even if you found it yourself.
- Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
- Properly format any scripts, code, logs, or error messages.
- Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.
Community Rules
- Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
- Posts must be Linux oriented
- Spam or affiliate links will not be tolerated.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would start by pasting important parts of the error ("Cannot load required OTR library") into a search engine and seeing if someone else has the same issue
Since the error contains a few file paths, I would then use utilities specific to my distribution to find what packages they belong to. I would remove the files (if they exist), re-install those packages and see if files are begin installed to those locations
I would then see if there's a crashlog in dmesg and repeat the above steps for any libraries mentioned in the log
I would then attempt running Thunderbird with a debugger like GDB to try to find the function that causes the crash
I would then try forwarding the email to myself, removing half of the HTML content and seeing if it crashes. If it does, the issue could be in the other half, so I remove that half instead and see if it crashes again. If it doesn't, I know it's an issue with the HTML, so I do a rough binary search to narrow the email down to the offending part
If it's not an issue with the HTML, I would check the email header and compare it with headers from other emails to see if something stands out. I would first have to do some research on what's inside an email header, though