You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded the .deb and installed it as root. I started sniffnet from commandline and from app menu.
I then downloaded the AppImage, set chmod 755, and started that.
In both cases, the terminal shows the app name and version (Sniffnet 1.5.0), the GUI window opens shortly for a split-second, with only dark background and no content, then I see "Abgebrochen (Speicherabzug geschrieben)" (= Core dumped).
Same for sniffnet from .deb and AppImage:
Is this the only output you have in the terminal? If so, why do you say that this is similar to #1125?
By the way, that one was already solved simply by setting the needed capabilities, as documented in the install instructions.
However I believe they are different issues, but to be sure I need to understand if this is all the output you have.
If so, why do you say that this is similar to #1125 ?
Merely because both are crashes on startup. I agree that they are different bugs. I am used to ignorant triagers who would duplicate my bug to that one. I mentioned it only to prevent this one to be closed as dup and to highlight the differences.
Activity
benbucksch commentedon Apr 17, 2026
#1125 is similar. But unlike the error there, I have
DISPLAY=":0"set in my environment.Of course, I am starting the app as normal user, not as root.
GyulyVGC commentedon Apr 17, 2026
Hey @benbucksch thanks for the report
I think this has to do with the graphic library in use.
Please try setting the environment variable
ICED_BACKEND=tiny-skiaand retry launching the DEB.This tells the app to use an alternative graphical renderer in case the default one doesn't work.
benbucksch commentedon Apr 17, 2026
@GyulyVGC Thanks for the quick and meaningful reaction!
Unfortunately, that still crashes:
(core dumped)
GyulyVGC commentedon Apr 17, 2026
Mm I see.
Is this the only output you have in the terminal? If so, why do you say that this is similar to #1125?
By the way, that one was already solved simply by setting the needed capabilities, as documented in the install instructions.
However I believe they are different issues, but to be sure I need to understand if this is all the output you have.
benbucksch commentedon Apr 17, 2026
Yes. Unfortunately.
Merely because both are crashes on startup. I agree that they are different bugs. I am used to ignorant triagers who would duplicate my bug to that one. I mentioned it only to prevent this one to be closed as dup and to highlight the differences.