Bug 29202 - Segfault at xrandr screen switching(?)
Summary: Segfault at xrandr screen switching(?)
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nVidia (proprietary) (show other bugs)
Version: 7.5 (2009.10)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Martin Stjernholm
QA Contact: Aaron Plattner
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2010-07-21 13:06 UTC by Martin Stjernholm
Modified: 2018-06-12 19:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg log from crash (19.13 KB, application/x-trash)
2010-07-21 13:06 UTC, Martin Stjernholm
no flags Details

Description Martin Stjernholm 2010-07-21 13:06:12 UTC
Created attachment 37279 [details]
Xorg log from crash

I got this segfault:

  Backtrace:
  0: /usr/bin/X (xorg_backtrace+0x28) [0x4a3248]
  1: /usr/bin/X (0x400000+0x655ad) [0x4655ad]
  2: /lib/libpthread.so.0 (0x7fedaf34e000+0xf8f0) [0x7fedaf35d8f0]
  3: /usr/bin/X (0x400000+0x13d20e) [0x53d20e]
  4: /usr/bin/X (0x400000+0x13d5c2) [0x53d5c2]
  5: /usr/bin/X (0x400000+0x81abf) [0x481abf]
  6: /usr/bin/X (0x400000+0x81c95) [0x481c95]
  7: /usr/bin/X (RRCrtcSet+0x162) [0x4c1892]
  8: /usr/bin/X (ProcRRSetScreenConfig+0x508) [0x4c72b8]
  9: /usr/bin/X (0x400000+0x30c3c) [0x430c3c]
  10: /usr/bin/X (0x400000+0x261aa) [0x4261aa]
  11: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7fedae046c4d]
  12: /usr/bin/X (0x400000+0x25d59) [0x425d59]
  Segmentation fault at address 0x18

  Caught signal 11 (Segmentation fault). Server aborting

It happened after watching a video using xine through its Xv driver. I quit xine normally in a script like this:

  xine --geometry 720x480+1920+0 -f "$@"
  xrandr -s 0
  gnome-settings-daemon

The server crashed at the instant I quit xine (so I rather suspect the xrandr command). The crash is intermittent - this is the first time I've seen it. Attaching the Xorg log.
Comment 1 Julien Cristau 2010-07-21 14:17:52 UTC
Looks like you're using a closed driver.  You need to report your issue to nvidia (or, if you can reproduce with a free driver, file a bug with the corresponding log).
Comment 2 Aaron Plattner 2010-07-21 16:01:37 UTC
There's no indication in the backtrace that the NVIDIA driver is involved in the crash at all.  Could you please get a backtrace using GDB?
Comment 3 Martin Stjernholm 2010-07-21 16:33:15 UTC
Unfortunately this happened in a normal non-debug session, so no coredump was produced. If the problem repeats itself I'll get a better backtrace.
Comment 4 Adam Jackson 2018-06-12 19:09:37 UTC
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.