lxqt-globalkeysd crashed with SIGSEGV in __run_exit_handlers()

Bug #1748987 reported by Don Forigua
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxqt-globalkeys (Ubuntu)
New
Undecided
Unassigned

Bug Description

I install lxqt from ubuntu minimal iso and i install lxde desktop and i have this bug

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: lxqt-globalkeys 0.12.0-3ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: LXQt
Date: Mon Feb 12 15:24:20 2018
ExecutablePath: /usr/bin/lxqt-globalkeysd
ProcCmdline: lxqt-globalkeysd
ProcEnviron:
 LANGUAGE=es_CO:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc3dab08e15 <__run_exit_handlers+69>: mov (%rcx),%rdx
 PC (0x7fc3dab08e15) ok
 source "(%rcx)" (0xb1fcd2dc83890) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lxqt-globalkeys
StacktraceTop:
 __run_exit_handlers (status=1, listp=0x7fc3daea76f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:55
 __GI_exit (status=<optimized out>) at exit.c:105
 _XDefaultIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: lxqt-globalkeysd crashed with SIGSEGV in __run_exit_handlers()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Don Forigua (ingforigua) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1713644, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.