mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6377] claws-mail: window doesn't paint / is unresponsive with "fancy" plugin #3254
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3254
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Dieterbe on GitHub (Jun 11, 2024).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6377
Description
Today I did some maintenance on my laptop, involving:
(✨ ✨ I use Arch, btw ✨ ✨)
All my apps etc seem to work fine still, except for claws-mail.
the app starts, but the window doesn't render properly (my window manager is i3). if claws-mail starts in a different workspace, then switching to it, doesn't show anything.
if i start claws-mail in the same workspace, you can see the rendered application, however it does not respond to any mouse clicks, like it is stuck / frozen. the mouse cursor keeps spinning
Steps to Reproduce
I don't use any custom config for claws-mail (that i know of). my /etc/firejail/claws-mail.profile is identical to the file found in the current latest firejail git.
LC_ALL=C firejail claws-mailtriggers the problem (confirmed with both claws 4.2 and 4.3)LC_ALL=C firejail --noprofile /usr/bin/claws-maildoes not have the problem. the app works fine (confirmed with both claws 4.2 and 4.3)Here is the output of all 4 cases: https://gist.github.com/Dieterbe/04485d729c6d8fa31e3b61ef6dac4707
Expected behavior
claws-mail renders, and responds to interactivity, i can use the app
Actual behavior
app doesn't render / freezes
Environment
42bdb78800Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)Log
see link above
@kmk3 commented on GitHub (Jun 11, 2024):
It's hard to tell what the issue is from the logs.
I'd try commenting lines in claws-mail.profile until it works to narrow it
down.
@ghost commented on GitHub (Jun 11, 2024):
Side note
https://gist.github.com/Dieterbe/04485d729c6d8fa31e3b61ef6dac4707#file-claws-4-2-0-1-via-firejail-txt-L27
https://gist.github.com/Dieterbe/04485d729c6d8fa31e3b61ef6dac4707#file-claws-4-3-0-1-via-firejail-txt-L27
Whenever you see this warning, it's a reminder to always use
absolutepaths. Firecfg places the symlinks in /usr/local/bin and that has precedence. I'm pretty sure this isn't related to your current issue. Still good practice though, so you're absolutely sure Firejail doesn't try to run the sandbox twice.@ghost commented on GitHub (Jun 11, 2024):
Some things to try:
temporarily downgradeto claws-mail 4.2.0-1 and run that without firejail (just to rule out it's something CM-related, which isn't clear if you've tried that yet)allowing python(and test that in a claws-mail.local)--debugflag to get a more verbose log from the appHTH
@ghost commented on GitHub (Jun 11, 2024):
Experienced intermittent ISP networking troubles during IRC communication with @Dieterbe. Issue still unresolved after checking CM configuration/mail storage paths and whitelisting ~/.cache/claws-mail. Issue is still unresolved.
@kmk3 commented on GitHub (Jun 14, 2024):
@Dieterbe
Please consider reporting this issue to the plugin developers as well.
I'm not familiar with the plugin, but I'd expect html rendering in general to
work without needing hardware acceleration.
@Dieterbe commented on GitHub (Jun 15, 2024):
they don't use github. i can't be bothered to sign up to their mailing list or bug tracker. if someone else wants to do that, feel free.