This bug is closed; it's better to open a new bug (with fresh backtrace
and logs) than to comment on this one.
** Changed in: gnome-desktop (Ubuntu)
Assignee: Bryce Harrington (bryce) = (unassigned)
** Changed in: gnome-control-center (Ubuntu)
Assignee: Bryce Harrington (bryce) =
In investigating further it appears that something (apport?) is linking
people to this bug report. However, this bug was fixed four years ago.
It's likely the logic in whatever is linking to this is faulty in some
fashion, rather than that this ancient crash has come back.
In any case, like I
Bryce, note that apport is now implementing client-side dupe checking
which may be to blame here for bugs being considered duplicates. People
are going to have a hard time filing a new bug report if that's the
case. At any rate, if apport thinks they're duplicates, that implies
the signature of
Up-to-date Quantal Alpha-1 with Fallback No Effects on ASUS eeePC900 +
ext mon. Still producing these at random.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197153
Title:
gnome-settings-daemon
6 June Quantal daily build install all up to date 3.4.0-5 likely near
Alpha 1 level still occurring on widescreen notebook.
Jerry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197153
Title:
Every time I boot quantal 12.10 daily image I get one or more of these
errors on netbook, notebook, tower. My daily image is up to date as of
yesterday 1 June.
Jerry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Occurred again on quantal daily build just now, 2 June, on booting
startup-disk
At least apport is working now, for the last days and days it didn't
follow through to launchpad.
Jerry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Eh, just trying the new LTS - looking to get the text instead of icons - One of
those who reads not looks.
This error just popped up when I was looking at Settings - running form live CD
- maybe after 2 minutes after booting.
EDITORIAL: Oh my, looks like a fun time ahead... Ugh!
MRK
--
You
12.04 Beta 2 booted ran a few minutes and got this bug.
Jerry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197153
Title:
gnome-settings-daemon crashed with SIGSEGV
To manage notifications about
This bug has been reported on the Ubuntu localized ISO testing tracker.
A list of all reports related to this bug can be found here:
http://localized-iso.qa.ubuntu.com/qatracker/reports/bugs/197153
** Tags added: iso-testing localized-iso
--
You received this bug notification because you are a
I still have this issue (nvidia driver) and cannot start gnome-settings-
daemon with xrandr enabled (8.04 fully updated). So either i am
experiencing another bug or this issue is still there.
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in
Longsleep, this is a different bug. please see Bug #199960
Thanks
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi
On Wed, Mar 19, 2008 at 05:31:19PM -, Sebastien Bacher wrote:
Simone, this bug has been fixed, if you still have an issue that's a
different one so open a new bug
Latest update and this is fixed for me, xrandr on,
gnome-settings-daemon starts, intel driver.
great.
Jan
--
.~.
Same here but I have an Nvidia GF7300...
Disabling xrandr in gconf-editor seems to fix it, at least I can login.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
After the latest updates everything seems to work fine for me; the
xrandr module in gnome-settings-daemon as well as the gnome-display-
properties utility. This is on 855GM hardware, using the intel driver.
Cheers!
--
gnome-settings-daemon crashed with SIGSEGV
Simone, this bug has been fixed, if you still have an issue that's a
different one so open a new bug
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm the same on an Intel 855GM card. After implementing fixes from
this bug (where you'll see my other comments) and disabling xrandr in
gconf-editor I am able to use the intel driver, at the correct resolution and
DPI without xrandr crashing.
I'm experiencing this bug on an intel 855 based laptop but it has NOT been
fixed as of Mar 16 CST 5:27 (DST).
This is after implementing some fixes I've described on a seemingly adjacent
bug report concering the intel driver w/ Xorg.
--
gnome-settings-daemon crashed with SIGSEGV
I can confirm that disabling xrandr with gconf-editor fixes this issue,
along with a related crash-on logoff issue.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have the same problems and unfortunately posted all my information to
Bug #83152 as it was the first one I found with the summary I was
searching for.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a
I'm still getting this with an update hardy, though the bug says fix released.
[EMAIL PROTECTED]:~$lspci|grep Graph
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated
Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics
The bug reappeared on my intel 855 based laptop (FSC P7120) too (it was
fixed with some intermediate release)
Albrecht
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: gnome-control-center (Ubuntu)
Target: ubuntu-8.04-beta = None
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I worked a bit on the dialog Friday, but unfortunately I found that the
way the gui and daemon work, the settings are applied and *then* tested,
rather than vice versa as the old Screen Resolution tool did, so it's
not 100% obvious how to implement a revert capability. I've asked
upstream for
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, March 9, 2008 3:35:21 PM
Subject: [Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
reporting bugs is useful but sending several comments on different
bugs
is not, just using the new opened one would be enough
Btw, for those not yet subscribed to bug 198951:
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,
After installing those debs, I only get this in the terminal when
running it:
[EMAIL PROTECTED]:~$ gnome-display-properties
Resource Timestamp: 59462
Resource Configuration Timestamp: 59462
CRTC 41 Timestamp: 59462
CRTC 42 Timestamp: 59462
Output 43 Timestamp: 59462
Segmentation fault (core
Arthur, these are fixes to gnome-settings-daemon, not gnome-display-
properties. For the gnome-display-properties issue, you'll need to
install the .deb posted to bug 198951.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification
I confirm this problem has reemerged. Gnome-Settings-Daemon crashes
during IPL sequence when xrandr 1.2 is active. The video driver is
radeonhd (latest from git).
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you
This seem to have recurred as bug 199960, can somebody take a look?
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
could you stop adding comments? today is sunday and not every is
working, don't use an unstable version if you don't want issues
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Sun, 2008-03-09 at 18:51 +, Sebastien Bacher wrote:
could you stop adding comments? today is sunday and not every is
working, don't use an unstable version if you don't want issues
Am I supposed to not report problems? I thought the whole purpose of
testing the unstable version was to
reporting bugs is useful but sending several comments on different bugs
is not, just using the new opened one would be enough and the comment
was rather about the other requests which were the same question repeted
and doesn't bring anything constructive there
--
gnome-settings-daemon crashed
This one seems to have recurred in 2.21.92-0ubuntu1, please review bug
199960
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
@Florent and rbmorse: Thanks for confirming that the crash is gone on
855, that's a relief. So technically this bug is solved - system start
up is no longer prevented. I'm dropping the priority and milestone.
For the separate gnome-display-properties crash, unfortunately that
means this tool
Bryce Harrington schrieb:
@Florent and rbmorse: Thanks for confirming that the crash is gone on
855, that's a relief. So technically this bug is solved - system start
up is no longer prevented. ...
same here, crash gone (855GM in FSC lifebook P7010), I also tried
meanwhile two other machines,
Bryce Harrington a écrit :
@Florent and rbmorse: Thanks for confirming that the crash is gone on
855, that's a relief. So technically this bug is solved - system start
up is no longer prevented. I'm dropping the priority and milestone.
For the separate gnome-display-properties crash,
This bug was fixed in the package gnome-desktop - 1:2.21.92-0ubuntu3
---
gnome-desktop (1:2.21.92-0ubuntu3) hardy; urgency=low
* debian/patches/102_gd-xrandr-null-pointer-check.patch:
- Adds a null pointer check to prevent an assertion at a later point
in the code, which
the change fixes the crash when using radeonhd, I've uploaded the new
revision
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
On Tue, 2008-03-04 at 07:44 +, Bryce Harrington wrote:
I've posted some packages to http://people.ubuntu.com/~bryce/Uploads/
for testing, including debs.
These include checks for if xrandr is available (which should help
Xinerama users), if the xrandr version is 1.2 (which should help
Excellent news that the gnome-desktop changed fixed the problems on
radeonhd. I'll forward the fix upstream.
I'd like to hear from the folks on intel with this problem, to see if it
solves the issue there as well.
Rick, Xinerama and Xrandr are sort of ying and yang; Xinerama being the
old,
Some results with an intel 855 GM :
With gnome-settings-daemon 2.21.91-0ubuntu6 and gnome-desktop 2:21.92-ubuntu3
gnome-settings-daemon don't crash anymore at startup.
However, gnome-display-properties still crash with a sligthly different
backtrace :
#0 rw_output_by_id (info=0x1af28, id=77)
Let me confirm what Florent reported.
I'm using the radeonhd driver (latest from git).
I previously indicated the gnome-setting-
daemon_2.21.91-0ubuntu6-i386.deb package had fixed the problem, but
further poking around reveals that only the crash on startup symptom was
fixed.
Selecting
@Bryce: that's good to hear there's a new tool being developed. You
don't actually seem to mention its name anywhere though - are you
referring to the individual per-driver proprietary settings tools (like
nvidia-settings) as the successor to displayconfig-gtk ? or is there
something else.
For
Another confirmation running nvidia-glx-new. I have two video cards set
up in dual head mode, similar to that described in bug #197354.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs,
From the confirmations, it sounds like all the reporters are using
drivers or hardware without proper xrandr 1.2 support. I would imagine
fglrx users would have the same problem.
This will require adding some checks to verify 1.2 capabilities of the
drivers in g-s-d I suppose. I'll work on it
@Bryce: Not true, I mentioned I'm using the intel driver which indeed
has proper xrandr 1.2 support. Do you want me to post my xorg.conf?
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
2008/3/3, Bryce Harrington [EMAIL PROTECTED]:
From the confirmations, it sounds like all the reporters are using
drivers or hardware without proper xrandr 1.2 support. I would imagine
fglrx users would have the same problem.
Do you mean that the intel driver with an intel 855 card is not
I have this problem on my system as well. I use the radeonhd driver. It
goes away if I set /apps/gnome-settings-daemon/plugins/xrandr/active and
/apps/gnome_settings_daemon/plugins/xrandr/active both to false (perhaps
one of the might have been enough).
Based on Bryce's instructions on IRC, I
I don't believe Bug #197665 is a duplicate of this one, in my case it
doesn't seem to segfault.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Tested bug's workaround and disabling xrandr pluggin does
gnome_setting_deamon stop crashing.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Tags added: need-i386-retrace
** Tags removed: apport-failed-retrace
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Tags removed: need-i386-retrace
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided = Critical
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
could somebody not getting the crash but a xorg bad request install
llibgtk2.0-0-dbgsym libgnome-desktop-2-dbgsym gnome-settings-daemon-
dbgsym, run it under gdb, break on gdk_x_error and get a stacktrace?
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You
On Mon, Mar 03, 2008 at 09:09:54PM -, Sebastien Bacher wrote:
could somebody not getting the crash but a xorg bad request install
llibgtk2.0-0-dbgsym libgnome-desktop-2-dbgsym gnome-settings-daemon-
dbgsym, run it under gdb, break on gdk_x_error and get a stacktrace?
Those packages don't
Hi Ryan,
Please see
https://wiki.ubuntu.com/DebuggingProgramCrash
for information on getting those packages.
Thanks,
James
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which
Those packages don't seem to exist under hardy.
Use this repo :
deb http://ddebs.ubuntu.com hardy main universe
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Looking at all the bug reports, the issue is identical - in gnome-
desktop, the output_initialize() routine, output-info is not getting
checked for a NULL pointer.
** Changed in: gnome-desktop (Ubuntu)
Importance: Undecided = Critical
Status: New = Confirmed
Target: None =
Here's a trivial patch to add a check for the aforementioned null
pointer. It doesn't address the underlying issue of why the pointer is
null in the first place (likely lack of xrandr 1.2 support); I'll
investigate that further.
** Attachment added: null_pointer_check.patch
In looking further, I notice that the new code dropped an #ifdef
HAVE_RANDR which actually we probably still need. Attached is a patch
to resolve that.
This probably only addresses cases where Xrandr is not used at all -
like Xinerama configs or drivers with absolutely no xrandr support.
I also
(likely lack of xrandr 1.2 support)
Just for the record, Bryce, I'm sure using xrandr 1.2. I switch between,
external, internal and dual screen setups all the time using randr and xrandr
1.2.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this
I've posted some packages to http://people.ubuntu.com/~bryce/Uploads/
for testing, including debs.
These include checks for if xrandr is available (which should help
Xinerama users), if the xrandr version is 1.2 (which should help nvidia
and fglrx users, and maybe others), and the null pointer
I see the same problem with the radeonhd driver (latest from git).
My xorg.conf is Hardy default except for adding the line
Driver radeonhd
to the device section.
System behaves normally when using the vesa driver.
--
gnome-settings-daemon crashed with SIGSEGV
The workaround works for me, I used gconf-editor to disable the plugin.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I also see this behavior. I'm using the nvidia driver on i386 on a
machine that I recently upgraded from gutsy to hardy. I have
(==) RandR enabled
in my X log, but
$ xrandr -q
X Error of failed request: BadRequest (invalid request code or no such
operation)
Major opcode of failed request:
** Changed in: gnome-settings-daemon (Ubuntu)
Target: None = hardy-alpha-6
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Appear to have same problem with AMD64 on a MSI MS-7093 motherboard and
NVIDIA GeForce 7300 GS running nvidia-glx-new 169.12+2.6.24.10-11.29
(NVIDIA 169.12 driver). I've attached my xorg.conf file.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/12357650/xorg.conf
--
Another confirmation with newest update on March 2. Using radeonhd
driver.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Same here.
I also noticed that I have two subtrees for gnome-settings-daemon in
gconf: gnome-settings-daemon and gnome_settings_daemon. I had to disable
the xrandr in the latter one to get things back to work.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
A backtrace :
--- stack trace ---
#0 rw_output_by_id (info=0x0, id=77) at randrwrap.c:122
output = value optimized out
#1 0xb6dc9990 in screen_info_new (screen=value optimized out) at
randrwrap.c:606
info = (ScreenInfo *) 0x80a4e50
#2 0xb6dc9f3b in rw_screen_new
StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: Stacktrace.txt (retraced)
http://launchpadlibrarian.net/12340874/Stacktrace.txt
--
gnome-settings-daemon crashed with SIGSEGV
thank you for your bug report. That's due to the new xrandr changes
** Changed in: gnome-desktop (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification
what video driver and xorg configuration are you using?
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
graphic card : intel 855 GM
Attached is my xorg.conf
** Attachment added: xorg.conf
http://launchpadlibrarian.net/12341101/xorg.conf
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Tried this with the fglrx and the radeonhd driver. Both give same problem.
Attached is my xorg.conf
On 01-03-08 15:26, Sebastien Bacher wrote:
what video driver and xorg configuration are you using?
--
Regards,
Jacco van Koll
[EMAIL PROTECTED]
# xorg.conf (xorg X Window System
No problem with the i810 driver, but i guess it's because it don't
support randr 1.2
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Not sure if I'm allowed to mark this as confirmed, but I would like to.
1. I installed Gutsy
2. I applied all updates as of March,2008
3. I upgrade to Hardy, on March 1, 2008
4. Upon logging in gnome-settings-daemon error occured
5. Apport launched, and brought me here, where I found this error.
Hi Arthur,
I think that there may be enough information already, so the
apport files are not needed.
Could you please confirm your video card type and the driver
you use, and attach your xorg.conf please?
Thanks,
James
--
gnome-settings-daemon crashed with SIGSEGV
I'm stumbling upon the same problem, using the intel driver. Should I
attach any information or is there enough now to debug this issue?
By the way, what exactly does it mean that gnome-settings-daemon has
xrandr to capabilities?
--
gnome-settings-daemon crashed with SIGSEGV
James Westby wrote:
Hi Arthur,
I think that there may be enough information already, so the
apport files are not needed.
Could you please confirm your video card type and the driver
you use, and attach your xorg.conf please?
Thanks,
James
Dear James,
Here is output of lspci | grep
I'm affected by that problem and that force to use the default gnome theme.
My video card is: Intel 82855GME
And now my xorg.conf below:
** Attachment added: xorg.conf
http://launchpadlibrarian.net/12347334/xorg.conf
--
gnome-settings-daemon crashed with SIGSEGV
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/12336918/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12336919/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/12336920/Disassembly.txt
** Attachment
I confirm that disabling the xrandr plugin make gnome-settings-daemon
work
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
84 matches
Mail list logo
