gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()

Bug #210226 reported by Robert Bernecky
88
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Fix Released
Medium
Bryce Harrington

Bug Description

Binary package hint: gnome-settings-daemon

gnome-setting daemon crashes after reboot. This is Alpha of Hardy Heron, dated approximately 2008-03-28.
There is an Nvidia graphics driver running for an ASUS N86000GT Silent dual-display (with different-sized displays,
just to make things harder).
The session is running gnome-failsafe, because the normal gnome session crashes within 10 seconds
after startup.

Tail end of dmesg reads:

   59.502233] gnome-settings-[6483]: segfault at 18 rip 7fe9a6c08894 rsp 7fffb8ca3308 error 4
[ 62.721308] gnome-settings-[6686]: segfault at 18 rip 7fd80f8f6894 rsp 7fff21992fc8 error 4
[ 62.950020] gnome-settings-[6696]: segfault at 18 rip 7f7578c68894 rsp 7fff8ad03338 error 4
[ 63.128081] gnome-settings-[6699]: segfault at 18 rip 7f52abe53894 rsp 7fffbdef0528 error 4
[ 63.909795] eth1: no IPv6 routers present
[ 63.972524] gnome-settings-[6725]: segfault at 18 rip 7fce9de79894 rsp 7fffaff16548 error 4
[ 64.148627] gnome-settings-[6728]: segfault at 18 rip 7f8ea77f5894 rsp 7fffb9891ec8 error 4
[ 64.316865] gnome-settings-[6731]: segfault at 18 rip 7f8012f47894 rsp 7fff24fe2618 error 4
[ 64.490909] gnome-settings-[6733]: segfault at 18 rip 7f659cfc5894 rsp 7fffaf060658 error 4
[ 64.668894] gnome-settings-[6735]: segfault at 18 rip 7f9e5e209894 rsp 7fff702a38d8 error 4
[ 64.961213] gnome-settings-[6738]: segfault at 18 rip 7f26cd34b894 rsp 7fffdf3e7a28 error 4

lsb:

Description: Ubuntu hardy (development branch)
Release: 8.04

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 1 08:44:46 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
NonfreeKernelModules: nvidia
Package: gnome-settings-daemon 2.22.0-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: gnome-settings-daemon
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/sac/sac2c/bin:/usr/java/jre1.5.0_01/bin:/usr/local/papi/bin:/opt/mdyalog/11.0pre/release:/home/username/OSC/bin:.
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 rw_screen_list_outputs ()
 configuration_new_current ()
 configuration_apply_stored ()
 gsd_xrandr_manager_start ()
 ?? ()
Title: gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner src video

Tags: apport-crash
Revision history for this message
Robert Bernecky (bernecky) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:rw_screen_list_outputs (screen=0x65ce70) at randrwrap.c:483
configuration_new_current (screen=0x65ce70) at monitor-db.c:343
configuration_apply_stored (screen=0x65ce70) at monitor-db.c:790
gsd_xrandr_manager_start (manager=<value optimized out>,
impl_activate (plugin=0x653d90) at gsd-xrandr-plugin.c:78

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-settings-daemon:
importance: Undecided → Medium
Changed in gnome-settings-daemon:
assignee: nobody → bryceharrington
milestone: none → ubuntu-8.04
Revision history for this message
Pedro Villavicencio (pedro) wrote :

setting as confirmed due to dups.

Changed in gnome-settings-daemon:
status: New → Confirmed
Revision history for this message
Robert Bernecky (bernecky) wrote :

Still fails as of 2008-04-06, with this day's upgrades.

rbe@rattler:~$ uname -a
Linux rattler 2.6.24-15-generic #1 SMP Fri Apr 4 03:10:59 UTC 2008 x86_64 GNU/Linux

I've observed the following:

1. Some upgrades disable the nvidia graphics driver, dropping me back into 680x480 land.
    The way I fixed these was to use the command-line apt-get to reinstall the nvidia drivers
    again, then do (I think...) nvidia-install again, then configure them.

2. The system doesn't properly sense Samsung SyncMaster 191T settings, although
    it is claimed to be Plug'n'Play. I'm confused at the moment about the LG 226WA,
    but I think it does better.

   At any rate, some updates seem to lose either monitor characteristics, or nvidia driver,
   or both.

3. Built-in table for above monitors don't seem to exist. I have to pick generic
TFT size setting, but that looks to work ok, despite being a nuisance.

[The following is probably unrelated bug, but just in case it's relevant...]:

4. After soft reboot (from shutdown menu), and sometimes on system power-on,
    the system never completes booting. It drops into initramfs(?) after thinking
    over the root file system stuff during bootup.

    It says "ata_id[4091] main: HDIO_GET_ID... {can't read my handwriting...} failed for
   /dev/.tmp/8-16.

Hard reboot via reset button has fixed this boot failure, thus far.

Revision history for this message
Bryce Harrington (bryce) wrote :

I've uploaded a patch with some better error checking in it. Please re-test against current Hardy and reopen if it is still crashing. (It is possible I merely shifted the crash to another spot, but I'll be optimistic...)

Changed in gnome-settings-daemon:
status: Confirmed → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

gnome-desktop (1:2.22.1-0ubuntu4) hardy; urgency=low

  * debian/patches/105_gd-randr-null-ptrs.patch:
    - Add null pointer checks throughout the code (LP: #210226).
    - This prevents us from crashing deep in the code due to various
      invalid situations that cause NULL ptrs, by passing the failure
      back up to the caller. If there are still crashes, this lets us
      handle them at a higher level.

 -- Bryce Harrington <email address hidden> Wed, 09 Apr 2008 14:46:48 -0700

Revision history for this message
Robert Bernecky (bernecky) wrote :

2008-04-10

Just installed a brazillion Hardy patches. Now seeing several sorts
of failures:

- repeated gnome-settings-daemon failures (attached)
- gnome-power-manager failure (See Bug #99505 attachment)
- applet.py failure (See Bug #153610).

Bob

Revision history for this message
James Westby (james-w) wrote :

Hi Robert,

I appears as though you forgot to attach the errors
you were seeing to the bug report, could you
try again please?

Thanks,

James

Revision history for this message
Robert Bernecky (bernecky) wrote :

Oops. I thought they got attached automagically. Lemme see
if I can find out where they went...

Bob

Revision history for this message
Robert Bernecky (bernecky) wrote :

Hi, James,

I looked around, hoping that there would be error log files in /tmp or
somewhere else obvious, but I don't see anything.

There were several logs generated and sent along, if I believe the
crash button stuff on the gnome menu bar...

If you can tell me where they were sent, I'll dig them up.
Sorry for the confusion...

Robert

Revision history for this message
James Westby (james-w) wrote : Re: [Bug 210226] Re: gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()

On Thu, 2008-04-10 at 17:46 +0000, Robert Bernecky wrote:
> Hi, James,
>
> I looked around, hoping that there would be error log files in /tmp or
> somewhere else obvious, but I don't see anything.
>
> There were several logs generated and sent along, if I believe the
> crash button stuff on the gnome menu bar...
>
> If you can tell me where they were sent, I'll dig them up.
> Sorry for the confusion...
>

Ah,

If it's the automatic crash reporting tool you first need to click
on the icon and tell it to report the bug.

Then it will check a few things and report the bug, did it get that
far?

Did it in fact file a new bug? If so can you search for it and post
a link here?

You can get it to report another bug by opening the file manager
and going to /var/crash, and then double clicking on the crash report
with "gnome_settings_daemon" in the name.

Thanks,

James

Revision history for this message
Robert Bernecky (bernecky) wrote :

Hi, James,

Here are a few crash logs from earlier today. Thanks for pointing me at /var/crash!

Revision history for this message
Robert Bernecky (bernecky) wrote :
Revision history for this message
James Westby (james-w) wrote :

On Thu, 2008-04-10 at 20:32 +0000, Robert Bernecky wrote:
> Hi, James,
>
> Here are a few crash logs from earlier today. Thanks for pointing me at
> /var/crash!
>
>
> ** Attachment added: "_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1000.crash"
> http://launchpadlibrarian.net/13342069/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1000.crash
>

Hi Robert,

These crash reports aren't too useful like that. If you double click on
one of them in the file manager the crash reporting tool will pop
up and allow you to report a new bug. Could you do that and drop a
link to the new bug here please?

Thanks,

James

Revision history for this message
Robert Bernecky (bernecky) wrote :

Hi, James.

Per your request, I've submitted new bugs:

# 215751 gnome-settings-daemon
# 153610 system-config-printer
# 217758 gnome-power-manager

Hope this helps...
Robert

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.