viking crashed with SIGSEGV in g_list_find()

Bug #259866 reported by raycock
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
viking (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: viking

No maps on startup.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/viking
Package: viking 0.9.4.20080614-1
ProcAttrCurrent: unconfined
ProcCmdline: viking
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: viking
StacktraceTop:
 g_list_find () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: viking crashed with SIGSEGV in g_list_find()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
raycock (raycock2) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_list_find () from /usr/lib/libglib-2.0.so.0
vik_aggregate_layer_move_layer (val=0x897f040,
layers_move_item (vlp=0x86dc358, up=1)
g_cclosure_marshal_VOID__VOID ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in viking:
importance: Undecided → Medium
Revision history for this message
Paul Gevers (paul-climbing) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Changed in viking (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for viking (Ubuntu) because there has been no activity for 60 days.]

Changed in viking (Ubuntu):
status: Incomplete → Expired
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.