[apport] xrdb crashed with SIGFPE

Bug #90196 reported by kwoz
140
Affects Status Importance Assigned to Milestone
x11-xserver-utils (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xrdb

Trying to enable the desktop effects

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 6 10:51:36 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/xrdb
Package: xrdb 1:1.0.2-0ubuntu2
PackageArchitecture: i386
ProcCmdline: xrdb -nocpp -merge
ProcCwd: /
ProcEnviron:
 LANGUAGE=en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 8
SourcePackage: xrdb
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux blockhead 2.6.20-9-386 #2 Mon Feb 26 02:58:41 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
kwoz (rigtong) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in xrdb:
assignee: nobody → ubuntu-x-swat
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in xrdb:
status: Unconfirmed → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Are you guys able to reproduce the xrdb crash constantly? Do you have a '/etc/X11/Xsession.d/30xorg-common_xresources' file?

Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

Timo, yes i have that file, i hadn't rebooted yet, i'll try rebooting probobly tommorow... and i think it might be constant.

Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

fresh reboot and i got yet another crash of xrdb, and i am also attaching the dump that it generated... to be precise the file, /var/crash/_usr_bin_xrdb.1001.crash

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Ok, thanks. Do you get the crash if you move '/etc/X11/Xsession.d/30xorg-common_xresources' to another place? You don't need to reboot, logout/login should do fine.

it seems that for some reason xrdb crashes if -nocpp is used for xrdb.

Revision history for this message
didier (did447-deactivatedaccount) wrote :

I can't reproduce it but from a strings CoreDump
...
-DEXT_SHAPE -DSCREEN_NUM=0 -DWIDTH=1024 -DHEIGHT=768
...

vs killing -4 a working xrdb
...
-DSCREEN_NUM=0 -DWIDTH=1152 -DHEIGHT=864 -DX_RESOLUTION=4299
...

It looks like screen->mwidth is not set by Xorg or libxcb; cf. xrdb.c:DoScreenDefines()

What does xdyinfo return?

Revision history for this message
Ken Phillis Jr (kphillisjr) wrote :

actually, this is a fairly similar but to what happened with QT-X11-Free, so I'll go ahead and paste the results of mine... i actually have a TV as one of my monitors and i didn't bother to fix my xorg because i don't know the mm size of my screen...

xdpyinfo | grep -a2 dimen

screen #0:
  dimensions: 1280x1024 pixels (370x280 millimeters)
  resolution: 88x93 dots per inch
  depths (7): 24, 1, 4, 8, 15, 16, 32
--

screen #1:
  dimensions: 800x600 pixels (0x0 millimeters)
  resolution: -2147483648x-2147483648 dots per inch
  depths (7): 24, 1, 4, 8, 15, 16, 32

Revision history for this message
DarkMageZ (darkmagez) wrote :

i can reproduce this almost at will.
this machine can become a nuclear penguin as it is of low importance.
i'll be around on irc.freenode.net in #ubuntu-bugs.

Revision history for this message
DarkMageZ (darkmagez) wrote :

sorry, i forgot about comment 8 when i read this 8 hours ago. yes moving that file seems to resolve the issue.

Revision history for this message
DarkMageZ (darkmagez) wrote :

i take back my last comment... it has no/unmeasurable effect. the "almost at will" part took effect while i was testing.

i've got a THEORY of replication, and it is probably only one of the ways to do it.

set xorg.conf up with a bunch of resolutions. gdm will use the preferred one.

set desktop to a lower resolution.

open gnome font properties and click details

(repeat till replicate)

you will notice that the font sizes in gdm for your logon details vary from restart to restart.

Revision history for this message
Han Pilmeyer (pilux) wrote :

Crashing on startup after Gutsy install.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

pretty sure this is fixed by now. If it still happens in lucid or newer, please open a new bug.

Changed in x11-xserver-utils (Ubuntu):
assignee: Ubuntu-X (ubuntu-x-swat) → nobody
status: Confirmed → 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.