qterminal crashed at login to lubuntu.

Bug #1548003 reported by Lyn Perrine
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qterminal (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I loged into lubuntu xenial with the gtk2 version of LXDE and had manually installed qterminal and on the first time I booted into LXDE without opening any programs saw apport say qterminal has crashed and had the option to send this crash report.

I expected to start LXDE and log into tthe desktop without any crashes instead qterminal crashed.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: qterminal 0.6.0+20150802-2
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: LXDE
Date: Thu Feb 18 14:50:50 2016
ExecutablePath: /usr/bin/qterminal
InstallationDate: Installed on 2015-11-17 (96 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151116)
ProcCmdline: qterminal
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: qterminal
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Lyn Perrine (walterorlin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f9dfcd65559 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0 0x00007f9dfcd65559 in ?? ()
 #1 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Alf Gaida (agaida) wrote :

should be closed or retested with a current xenial package (0.6.0+20160104-1)

Revision history for this message
Alf Gaida (agaida) wrote :

not reproducible with current xenial (16.04.1) nor yakkety - so i mark this bug as invalid

Changed in qterminal (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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