desktop-packages team mailing list archive

[Tormod Volden <602028@xxxxxxxxxxxxxxxxxx>]

This was most likely a one-off problem, maybe a hardware problem. Unless
it can be reproduced or confirmed by others, the report can be closed.

** Changed in: xscreensaver (Ubuntu)
       Status: Confirmed => Incomplete

** Changed in: xscreensaver (Ubuntu)
     Assignee: (unassigned) => Tormod Volden (tormodvolden)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xscreensaver in Ubuntu.
https://bugs.launchpad.net/bugs/602028

Title:
  xscreensaver crashed with SIGSEGV

Status in xscreensaver package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xscreensaver

  i was away so dont know if screensaver started working but this crash
  was already waiting

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: xscreensaver 5.10-3ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  Architecture: i386
  Date: Mon Jul  5 23:07:35 2010
  ExecutablePath: /usr/bin/xscreensaver
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
  ProcCmdline: xscreensaver -no-splash
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.utf8
  SegvAnalysis:
   Segfault happened at: 0x66c422 <__kernel_vsyscall+2>:	ret
   PC (0x0066c422) ok
   destination "(%esp)" (0xbfa383d8) ok
   SP (0xbfa383d8) ok
   Reason could not be automatically determined. (Unhandled exception in kernel code?)
  Signal: 11
  SourcePackage: xscreensaver
  StacktraceTop: ?? ()
  Title: xscreensaver crashed with SIGSEGV
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/602028/+subscriptions