gitg crashed with SIGABRT in g_assertion_message() when called from CLI with PWD set in a git repo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gitg (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
From within present working directory that is a git repository I did:
gitg &
I was then going to click on a log entry to inspect what the changeset had brought in but gitg exited and provided the error that I am not reporting.
I had rebooted my PC about 10 minutes before this. Prior to that I had completed a distribution upgrade from Ubuntu 14.04 to 16.04 via the using the `do-release-upgrade -d` command. Before the upgrade I had been regularly using gitg to view git log data and generate git commits for this repository.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gitg 3.17.1-1
ProcVersionSign
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 8 15:34:00 2016
ExecutablePath: /usr/bin/gitg
InstallationDate: Installed on 2015-03-12 (453 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: gitg
Signal: 6
SourcePackage: gitg
StacktraceTop:
g_assertion_
g_assertion_
?? () from /usr/lib/
?? () from /usr/lib/
g_object_unref () from /usr/lib/
Title: gitg crashed with SIGABRT in g_assertion_
UpgradeStatus: Upgraded to xenial on 2016-06-08 (0 days ago)
UserGroups: adm cdrom dialout dip lpadmin mock plugdev sambashare sudo
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 #1561949, 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.