dring crashed with SIGABRT

Bug #1760797 reported by Sosha
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ring (Ubuntu)
New
Undecided
Unassigned

Bug Description

after login session...

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ring-daemon 20180228.1.503da2b~ds1-1build1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr 3 06:37:08 2018
Disassembly: No registers.
ExecutablePath: /usr/lib/ring/dring
InstallationDate: Installed on 2017-09-02 (212 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/lib/ring/dring
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Registers: The program has no registers now.
Signal: 6
SourcePackage: ring
Stacktrace: No stack.
StacktraceTop:

ThreadStacktrace:

Title: dring crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

Revision history for this message
Sosha (soshaw) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace: No stack.
StacktraceSource:

StacktraceTop:

ThreadStacktrace:

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
themusicgod1 (themusicgod1) wrote :
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.