Bug 560614

Summary: crash detected in noseguy
Product: [Fedora] Fedora Reporter: Maik Strewe <mstrewe>
Component: xscreensaverAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:a7b8c37ae1837361b0592e8efd781d8f856345af
Fixed In Version: 5.10-5.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-05 01:38:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
XScreenSaver.ad
none
.xscreensaver of home directory
none
.xsession-errors
none
.xsession-errors.old
none
rpm -qa output none

Description Maik Strewe 2010-02-01 11:47:51 UTC
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: noseguy -root -window-id 0x5200742
component: xscreensaver
executable: /usr/libexec/xscreensaver/noseguy
kernel: 2.6.31.12-174.2.3.fc12.i686
package: xscreensaver-extras-1:5.10-4.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

Comment 1 Maik Strewe 2010-02-01 11:47:53 UTC
Created attachment 388016 [details]
File: backtrace

Comment 2 Mamoru TASAKA 2010-02-01 17:02:49 UTC
Do you see noseguy crash when launching noseguy
from the terminal like below?
$ /usr/libexec/xscreensaver/noseguy

If so are there any messages on the terminal?

Comment 3 Maik Strewe 2010-02-02 13:02:09 UTC
No I dont start from terminal.
I've done an ssh -X session from Desktop to laptop(here the error happands) end start gnome session on laptop. To test the speed of remote X forwarding with encryption i start Screensaver(within gnome session) so i have no error message for you ... sorry

Comment 4 Mamoru TASAKA 2010-02-02 13:11:05 UTC
Thank you for reply.

Then would you
- attach the following files (of the machine in which crash happened)?
  * /etc/xscreensaver/XScreenSaver.ad
  * ~/.xscreensaver (of the user using screensaver), if any
  * ~/.xsession-errors

- and show the result of the following?
  $ rpm -qa | grep font | sort

Comment 5 Maik Strewe 2010-02-02 13:22:33 UTC
Created attachment 388287 [details]
XScreenSaver.ad

Comment 6 Maik Strewe 2010-02-02 13:23:56 UTC
Created attachment 388288 [details]
.xscreensaver of home directory

Comment 7 Maik Strewe 2010-02-02 13:25:02 UTC
Created attachment 388289 [details]
.xsession-errors

Comment 8 Maik Strewe 2010-02-02 13:25:28 UTC
Created attachment 388291 [details]
.xsession-errors.old

Comment 9 Maik Strewe 2010-02-02 13:52:23 UTC
Created attachment 388297 [details]
rpm -qa output

Comment 10 Mamoru TASAKA 2010-02-02 14:03:08 UTC
(In reply to comment #8)
> Created an attachment (id=388291) [details]
> .xsession-errors.old    

Well, may be this crash happened when X session was about
to shut down (during logout) or so and X resource was no
longer available at that time.
So while it seems this is not easily reproducible, I will add
a patch which may prevent this from happening.

Comment 11 Fedora Update System 2010-02-02 17:30:45 UTC
xscreensaver-5.10-5.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/xscreensaver-5.10-5.fc12

Comment 12 Fedora Update System 2010-02-02 17:31:14 UTC
xscreensaver-5.10-5.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/xscreensaver-5.10-5.fc11

Comment 13 Fedora Update System 2010-02-05 01:29:43 UTC
xscreensaver-5.10-5.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 14 Fedora Update System 2010-02-05 01:38:02 UTC
xscreensaver-5.10-5.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.