bamfdaemon crashed with signal 5 in _XReply()

Bug #1156384 reported by Ivan Brasil Fuzzer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bamf (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have no more information. The computer was lazy when the error appeared.

Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04

  Instalado: 0.4.0daily13.03.07-0ubuntu1
  Candidato: 0.4.0daily13.03.07-0ubuntu1
  Tabela de versão:
 *** 0.4.0daily13.03.07-0ubuntu1 0
        500 http://br.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: bamfdaemon 0.4.0daily13.03.07-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Sun Mar 17 21:01:28 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
InstallationDate: Installed on 2013-03-13 (4 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130313)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
Signal: 5
SourcePackage: bamf
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libwnck-3.so.0
Title: bamfdaemon crashed with signal 5 in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Ivan Brasil Fuzzer (ivanbrasil) wrote :
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 #1107926, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
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.