[amd64] bumps crashed with SIGSEGV in __libc_start_main() [PutPixel32()]

Bug #103975 reported by Chuck Adams
48
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xscreensaver (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xscreensaver

missing /usr/share/screenbackgrounds or something like that. Error message goes away
when bug report starts up.

TIA

ProblemType: Crash
Architecture: amd64
Date: Fri Apr 6 20:01:09 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/xscreensaver/bumps
Package: xscreensaver-data-extra 4.24-5ubuntu2
PackageArchitecture: amd64
ProcCmdline: bumps -root
ProcCwd: /home/adams
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/lib/xscreensaver:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/adams/bin
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
Uname: Linux kubuntu7 2.6.20-14-generic #2 SMP Mon Apr 2 16:32:46 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: amd64 saucy
Revision history for this message
Chuck Adams (k7qo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:Execute (pBumps=0x7fff74d211d0) at bumps.c:467
screenhack (pDisplay=0x614be0, Win=<value optimized out>) at bumps.c:545
main (argc=1, argv=0x7fff74d216c8) at screenhack.c:679
__libc_start_main () from /lib/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in xscreensaver:
importance: Undecided → Medium
Changed in xscreensaver:
status: Unconfirmed → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote : Re: [apport] bumps crashed with SIGSEGV in __libc_start_main() [PutPixel32()]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in xscreensaver:
assignee: nobody → tormodvolden
status: Confirmed → Incomplete
Revision history for this message
Tormod Volden (tormodvolden) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xscreensaver:
assignee: tormodvolden → nobody
status: Incomplete → Invalid
Revision history for this message
martyfelker (martyfelker-gmail) wrote :

Happen to me (xscreensaver/bumps) on Ubuntu9 13.10 amd64 after copying an exremley large file (77.5GB). Xscreensaver was left running so I can't exactly say when it appered

Revision history for this message
Mamoru TASAKA (mtasaka) wrote :
Revision history for this message
Mamoru TASAKA (mtasaka) wrote :

(As I wrote in the previous comment, this issue is really 64 bit specific, does not happen on 32 bit)

Revision history for this message
martyfelker (martyfelker-gmail) wrote :

Not fixed for 6 years. Should not be this complex I think

Ubuntu 13.10 <xscreensver was running as were two downloads>

Mamoru TASAKA (mtasaka)
Changed in xscreensaver (Ubuntu):
status: Invalid → New
tags: added: saucy
Changed in xscreensaver (Ubuntu):
status: New → Confirmed
status: Confirmed → New
Revision history for this message
Tormod Volden (tormodvolden) wrote :

I have a pre-release for xscreensaver 5.22 in my PPA, if anyone wants to install that instead. It is the Debian version without Ubuntu patches, so you might want to remove the old packages before installing these to avoid certain upgrade issues. The Precise package should work fine in any newer release as well.

https://launchpad.net/~tormodvolden/+archive/ppa/+packages?field.name_filter=xscreensaver&field.status_filter=published

tags: added: amd64
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xscreensaver (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (5.4 KiB)

This bug was fixed in the package xscreensaver - 5.26-1ubuntu1

---------------
xscreensaver (5.26-1ubuntu1) utopic; urgency=low

  * Dropped Ubuntu changes:
    - Ubuntu delta to the screensavers sets.
    - Keep Debian Vcs-* links instead of the ~ubuntu-desktop team bzr
      repository: the Desktop team does not have interest any more.
    - The Ubuntu changes to the descriptions.
  * Merge from Debian unstable. (LP: #1283459) Remaining changes:
    - debian/control:
      + Breaks/Replaces: the old changes are not needed anymore, but the
        new changes the screensavers sets needs it.
    - debian/rules:
      + Use /usr/share/backgrounds as image directory.
      + Add translation domain to .desktop files.
    - debian/source_xscreensaver.py:
      + Add apport hook.
    - debian/xscreensaver.dirs:
      + Install /usr/share/backgrounds. By default, settings search in
        /usr/share/backgrounds and without it, it displays an error.
    - debian/patch/90_ubuntu-branding.patch: Use Ubuntu branding.
    - debian/patches/60_sequential_glslideshow.patch:
      + Allow going through images sequentially rather than just at random in
        the GLSlideshow hack.

xscreensaver (5.26-1) unstable; urgency=low

  * New upstream release 5.26, changes since 5.23:
    - Updated feed-loading for recent Flickr changes.
    - Updated `webcollage' for recent Google changes.
    - Added Instagram and Bing as `webcollage' image sources.
    - Updated to latest autoconf.
    - Bug fixes.
  * Drop patch applied upstream:
    - debian/patches/12_upstream_use_cppflags.patch
  * Bump Standards-Version to 3.9.5 (no changes needed)

xscreensaver (5.23-1) unstable; urgency=low

  * New upstream release 5.23 (Closes: #729311)
    - New hack, geodesic
    - More heuristics for using RSS feeds as image sources
    - Improved Wikipedia parser
    - Updated webcollage for recent Flickr changes
    - Added Android to bsod
    - Made quasicrystal work on weak graphics cards
    - Better compression on icons, plists and XML files
    - Reverted that DEACTIVATE change. Bad idea.
    - Phosphor now supports amber as well as green
  * Dropped patches applied upstream:
    - 12_upstream_quasicrystal_texture_width.patch
    - 14_upstream_hexadrop_keyboard_exit.patch
    - 15_upstream_activate_faster_nontty.patch
  * debian/patches/12_upstream_use_cppflags.patch:
    Make sure CPPFLAGS are used (fixes hardening warnings)
  * debian/control: Update VCS fields (fixes Lintian warning)

xscreensaver (5.22-1) unstable; urgency=low

  * New upstream release 5.22 (Closes: #699833), changes since 5.15:
    - XInput devices now also ignore small mouse motions
    - Loading images via RSS feeds is much improved
    - Enlarged the texture image for lament
    - Made pipes be ridiculously less efficient, but spin
    - Added better mouse control to rubik, cube21, crackberg, and julia
    - Cosmetic improvements to queens and endgame
    - sonar can now ping local subnet on DHCP
    - Most savers now resize/rotate properly
    - New version of `fireworkx'
    - Minor fixes to `distort', `fontglide', `xmatrix'
    - New MacOS crash in `bsod'
    - New mode in `lcdscrub'
    - Gnome/KD...

Read more...

Changed in xscreensaver (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.