gltext crashed with SIGSEGV in _IO_link_in()

Bug #428974 reported by Angel Guzman Maeso
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xscreensaver (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xscreensaver

Just with my screensaver run.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Sep 13 17:42:55 2009
Disassembly: 0xb854748f: Cannot access memory at address 0xb854748f
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/xscreensaver/gltext
Package: xscreensaver-gl 5.08-0ubuntu4
ProcCmdline: gltext -root
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 LANGUAGE=es_ES.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SegvAnalysis:
 Segfault happened at: 0xb854748f: Cannot access memory at address 0xb854748f
 PC (0xb854748f) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? ()
 _IO_link_in () from /lib/libc.so.6
 _IO_file_init () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 fopen () from /lib/libc.so.6
Title: gltext crashed with SIGSEGV in _IO_link_in()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
_IO_new_file_init (fp=0x9bcfb28) at fileops.c:154
__fopen_internal (filename=0x5ff406 "/proc/meminfo",
_IO_new_fopen (filename=0x5ff406 "/proc/meminfo",
phys_pages_info (format=<value optimized out>)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xscreensaver (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in xscreensaver (Ubuntu):
status: New → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Is this still an issue in Ubuntu 10.04 or 12.04 LTS?

Changed in xscreensaver (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Angel Guzman Maeso (shakaran) wrote :

This bug is pretty old (3 years ago). I am running now Ubuntu 12.10 Quantal fully update with another laltop. I don't see this error anymore, but I cannot say you if it is fixed at some point or if it is still a issue.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks, I'll close the report then. We can reopen it if it happens again.

Changed in xscreensaver (Ubuntu):
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.