BeagleDaemon.exe crashed with signal 5

Bug #128771 reported by Nizar Kerkeni
14
Affects Status Importance Assigned to Milestone
beagle (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: beagle

A crash after login in gnome

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Jul 27 21:42:42 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/beagle/BeagleDaemon.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: beagle 0.2.17-1ubuntu1
PackageArchitecture: i386
ProcCmdline: beagled /usr/lib/beagle/BeagleDaemon.exe --replace --bg
ProcCwd: /home/kerkeni
ProcEnviron:
 SHELL=/bin/bash
 PATH=/opt/jdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fr_FR.UTF-8
Signal: 5
SourcePackage: beagle
Stacktrace:
 #0 0xb7ed2d2b in g_logv () from /usr/lib/libglib-2.0.so.0
 #1 0xb7ed2fa9 in g_log () from /usr/lib/libglib-2.0.so.0
 #2 0xb7ed3026 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
 #3 0x080e4b0b in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
Title: BeagleDaemon.exe crashed with signal 5
Uname: Linux Sayada2 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Nizar Kerkeni (nizarus) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in beagle:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in beagle:
status: Incomplete → 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.