Ubuntu
glabels package

glabels crashed with SIGSEGV

Bug #149139 reported by Microstorm87 on 2007-10-04

This bug report is a duplicate of: Bug #129518: glabels crashes when switching paper size in template selector dialog. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	glabels (Ubuntu)	Incomplete	Medium	Basilio Kublik

Bug Description

Programm Glabel crash when I select type "other"

ProblemType: Crash
Architecture: i386
Date: Thu Oct 4 22:26:19 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/glabels
NonfreeKernelModules: cdrom
Package: glabels 2.1.3-1build1
PackageArchitecture: i386
ProcCmdline: glabels
ProcCwd: /home/administrator
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=it_IT.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: glabels
Stacktrace: #0 0x080ba9c7 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: glabels crashed with SIGSEGV
Uname: Linux ubuntu-laptop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner uml-net video

Tags:

Revision history for this message

Microstorm87 (bustofrancesco-deactivatedaccount) wrote on 2007-10-04:

Dependencies.txt Edit (4.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (596 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (27.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (666 bytes, text/plain; charset="utf-8")
Registers.txt Edit (478 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2007-10-06: Symbolic stack trace

Stacktrace.txt (retraced) Edit (23 bytes, text/plain)

StacktraceTop:?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2007-10-06: Stack trace with source code

StacktraceSource.txt Edit (24 bytes, text/plain)

Revision history for this message

Basilio Kublik (sourcercito) wrote on 2007-11-27:

Hi there
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.

Thanks in advance