Comment 0 for bug 1859823

Revision history for this message
El jinete sin cabeza (ejsc-deactivatedaccount) wrote :

I don't know why it happens.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: flameshot 0.6.0+git20191001-1
Uname: Linux 5.4.11-050411-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 15 08:11:06 2020
ExecutablePath: /usr/bin/flameshot
InstallationDate: Installed on 2018-12-02 (408 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: flameshot
ProcEnviron:
 LANG=es_CL.UTF-8
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x5562087ff2e0: (bad)
 PC (0x5562087ff2e0) in non-executable VMA region: 0x5562085c5000-0x556208c2f000 rw-p [heap]
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: flameshot
StacktraceTop:
 ()
 ()
 <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6
 ()
 ()
Title: flameshot crashed with SIGSEGV
UpgradeStatus: Upgraded to focal on 2018-12-02 (408 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator: