Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=436702.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Changed in: gnome-desktop (Fedora)
Status: Confirmed = Fix Released
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: backtrace-gnome-display-properties.log
http://launchpadlibrarian.net/12738112/backtrace-gnome-display-properties.log
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this
Sorry Seb, but it doesn't seem like it was fixed on my box.
[EMAIL PROTECTED]:~/svn/systems/scripts/misc$ dpkg -l | grep gnome-desktop
ii gnome-desktop-data 1:2.22.0-0ubuntu2
Common files for GNOME 2 desktop apps
ii libgnome-desktop-2
Looking at that strace and a bit of poking around on this box...
gnome-display-properties opens a socket and assigns it fd 3 for x.
It writes some data and RANDR to that socket. After another read on
that same socket, it drops core.
[EMAIL PROTECTED]:~/svn/systems/scripts$ xrandr
Xlib:
this crasher is a different one, see bug #199878
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hello, the gnome-settings-daemon is not crashing anymore after the
latest updates.On Wed, 19 Mar 2008 13:13:34 - Bug 198951 wrote
Sorry Seb, but it doesn't seem like it was fixed on my box.
[EMAIL PROTECTED]:~/svn/systems/scripts/misc$ dpkg -l | grep gnome-
desktop ii gnome-desktop-data
valgrind log showing the issue
==24278== Use of uninitialised value of size 4
==24278==at 0x5609ECA: output_initialize (randrwrap.c:606)
==24278==by 0x56095E8: fill_out_screen_info (randrwrap.c:267)
==24278==by 0x56096F7: screen_info_new (randrwrap.c:297)
==24278==by 0x5609771:
** Changed in: gnome-desktop (Fedora)
Status: Unknown = Confirmed
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Alright, I've figured the issue and will upload a fix soon
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) = Sebastien Bacher (seb128)
Status: In Progress = Fix Committed
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx,
** Changed in: gnome-desktop (Ubuntu)
Sourcepackagename: gnome-control-center = gnome-desktop
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of
The issue was due to RWOutput *output = rw_output_by_id (output-info,
info-clones[i]);, the same variable name is used for the new rwoutput
and as function parameter which creates a conflict and breaks the
argument used there
The new upload fixes the gnome-settings-daemon issue, testing on an
This bug was fixed in the package gnome-desktop - 1:2.22.0-0ubuntu2
---
gnome-desktop (1:2.22.0-0ubuntu2) hardy; urgency=low
* debian/patches/100_gd-add-randr-12.patch:
- don't use conflicting variable name, fix the gnome-settings-daemon
and gnome-display-properties
Sebastien you are my hero !
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Bryce, the bug has a detailled backtrace, valgrinds shows an incorrect
read there and build libgnome-desktop-2 using -O0 seems to workaround
the issue
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You
Redhat has a bug about that on
https://bugzilla.redhat.com/show_bug.cgi?id=436702
** Also affects: gnome-desktop (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=436702
Importance: Unknown
Status: Unknown
--
gnome-display-properties crashed with SIGSEGV in screen_info_new()
I'll have a look at getting informations but I'm not the one who added
those changes and I'm not responsive for the issue
** Changed in: gnome-control-center (Ubuntu)
Assignee: Sebastien Bacher (seb128) = (unassigned)
Target: None = ubuntu-8.04-beta
--
gnome-display-properties
Like many others, I experience the crash with an 855 and the intel driver.
Let me add that I can use xrandr 1.2 features using the command line tool, i.e.
$ xrandr --output VGA --pos 0x200
extends the screen downwards to my external display. I have mostly used it for
a clone configuration, but
Assigning to seb128 since he needs to either accept the gnome-settings-
daemon patch I sent, or propose an alternate patch, or provide
additional troubleshooting information including detailed backtraces
before I can do anything more.
** Changed in: gnome-control-center (Ubuntu)
Assignee:
Try replacing default with whatever your default output is (e.g.
VGA-1, DVI0, etc.) You can run xrandr with no args to see a list of
what outputs are available.
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
I replaced default with LVDS, and it successfully changed the
resolution with no error messages.
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of
On Wed, 2008-03-12 at 06:43 +, Bryce Harrington wrote:
Try replacing default with whatever your default output is (e.g.
VGA-1, DVI0, etc.) You can run xrandr with no args to see a list of
what outputs are available.
Bryce, same result when specifying output (DVI-I_1/digital). No error,
I replaced default with LVDS, and it successfully changed the
resolution with no error messages.
I'm using an Intel btw.
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification
[EMAIL PROTECTED]:~$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 768, maximum 1280 x 1280
VGA_1 disconnected
PANEL connected 1280x768+0+0 0mm x 0mm
1280x768 60.0*+
[EMAIL PROTECTED]:~$ xrandr --output PANEL --mode 1024x768
xrandr: cannot find mode 1024x768
[EMAIL PROTECTED]:~$
Thanks, although unfortunately it's inconclusive whether xrandr 1.2 is
supported.
So... I decided to code up a big workaround (disable the daemon on
drivers that won't support it). This won't fix the gnome-display-
properties crash, but if you are experiencing the daemon crash, please
see bug
I tried installing the latest test deb, and it does not install, citing
dependancy issues. It claims to depend on libgnome-window-setting1 (=
1:2.21.92-0ubuntu3), but I only have libgnome-window-setting1 (=
1:2.21.92-0ubuntu2). My system is up to date (it can find no more
updates to apply from the
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Invalid
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Tue, 2008-03-11 at 03:30 +, Bryce Harrington wrote:
Darn. Well, could you please install and test this deb, which includes
a test for xrandr 1.2, and let me know if it still crashes or not.
http://people.ubuntu.com/~bryce/Testing/XrandrGui/gnome-control-
Ah, sorry missed that:
http://people.ubuntu.com/~bryce/Testing/XrandrGui/libgnome-window-settings-dev_2.21.92-0ubuntu3_all.deb
http://people.ubuntu.com/~bryce/Testing/XrandrGui/libgnome-window-settings1_2.21.92-0ubuntu3_i386.deb
--
gnome-display-properties crashed with SIGSEGV in
On Tue, 2008-03-11 at 18:37 +, Bryce Harrington wrote:
Ah, sorry missed that:
http://people.ubuntu.com/~bryce/Testing/XrandrGui/libgnome-window-settings-dev_2.21.92-0ubuntu3_all.deb
http://people.ubuntu.com/~bryce/Testing/XrandrGui/libgnome-window-settings1_2.21.92-0ubuntu3_i386.deb
Hi
rbmorse, the gnome-settings-daemon crash you're experiencing is covered
in bug 199960. Sorry for the confusion.
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are
rbmorse, those gnome-control-center debs are only intended for
addressing the crash in gnome-display-properties, *not* the crash in
gnome-settings-daemon.
** Description changed:
Binary package hint: gnome-control-center
Starting gnome-display-properties crash at startup.
I got this
I'll second what rbmorse said. Dependencies are cleared up, but things
will still not work.
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
On Tue, 2008-03-11 at 20:21 +, Bryce Harrington wrote:
rbmorse, those gnome-control-center debs are only intended for
addressing the crash in gnome-display-properties, *not* the crash in
gnome-settings-daemon.
Maybe I'm confused, too. In any case, gnome-display-properties still
crashes,
Let me clarify: I still cannot start-up gnome-display-properties.
Didn't read all of what rbmorse said.
I still get:
Resource Timestamp: 59462
Resource Configuration Timestamp: 59462
CRTC 41 Timestamp: 59462
CRTC 42 Timestamp: 59462
Output 43 Timestamp: 59462
Segmentation fault (core dumped)
--
Hey, by any chance are you guys running Xgl?
(You can check by running xvinfo | grep Xgl )
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of
I tried running the xvinfo command:
[EMAIL PROTECTED]:~$ xvinfo | grep Xgl
[EMAIL PROTECTED]:~$
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of
On Tue, 2008-03-11 at 23:30 +, Bryce Harrington wrote:
Hey, by any chance are you guys running Xgl?
(You can check by running xvinfo | grep Xgl )
xvinfo returns:
[EMAIL PROTECTED]:~$ xvinfo
X-Video Extension version 2.2
screen #0
no adaptors present
[EMAIL PROTECTED]:~$
--
I am using radeonHD drivers, so nope, I'm not using XGL or anything of
the sort.
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
Bugs, which
Okay, thanks, that rules that out.
Next thing to test - run `xrandr --output default --mode 1024x768`.
a. Does it change the resolution properly?
b. Do you get an X Error message about BadMatch (major opcode 158, minor 7)?
Or a different X Error?
--
gnome-display-properties crashed with
As my laptop is already running at 1024x768, I tried it with 800x600 and
640x480, neither of which had any effect - the resolution stayed the
same
[EMAIL PROTECTED]:~$ xrandr --output default --mode 800x600
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$ xrandr --output default --mode 640x480
[EMAIL
On Wed, 2008-03-12 at 01:25 +, Bryce Harrington wrote:
Okay, thanks, that rules that out.
Next thing to test - run `xrandr --output default --mode 1024x768`.
a. Does it change the resolution properly?
b. Do you get an X Error message about BadMatch (major opcode 158, minor 7)?
Or a
I also get no errors (or any other output), but it doesn't change the
resolution at all.
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- [intel 855GM] gnome-display-properties crashed with SIGSEGV in
screen_info_new()
+ gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
** Description changed:
Binary package hint: gnome-control-center
Starting
I believe this issue is due to bugs in xrandr rather than an issue in
gnome-settings-daemon itself. I've backported several bug fixes from
upstream that look relevant to making xrandr work properly - these are
from one of the radeonhd developers, so will be especially relevant for
radeonhd users
Hi Bryce,
X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu5~b
wh1)
Current Operating System: Linux flo-laptop 2.6.24-12-generic #1 SMP Mon Mar 10 1
5:32:00 UTC 2008 i686
Build
On Tue, 2008-03-11 at 01:01 +, Bryce Harrington wrote:
I believe this issue is due to bugs in xrandr rather than an issue in
gnome-settings-daemon itself. I've backported several bug fixes from
upstream that look relevant to making xrandr work properly - these are
from one of the radeonhd
** Changed in: gnome-control-center (Ubuntu)
Sourcepackagename: gnome-settings-daemon = gnome-control-center
--
gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855,
fglrx, radeonhd
https://bugs.launchpad.net/bugs/198951
You received this bug notification because you are a
Darn. Well, could you please install and test this deb, which includes
a test for xrandr 1.2, and let me know if it still crashes or not.
http://people.ubuntu.com/~bryce/Testing/XrandrGui/gnome-control-
center_2.21.92-0ubuntu3_i386.deb
--
gnome-display-properties crashed with SIGSEGV in
49 matches
Mail list logo
