** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Chris Coulson (chrisccoulson) = Joey Utin (josephutin2001)
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Joey Utin (josephutin2001) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
I can confirm that this is still a problem.
I've just upgraded from 12.04 to 12.10, and am trying to get my dual
monitor setup working again (worked fine under 12.04). I have gnome-
settings-daemon 3.4.2-0ubuntu15, but still get the same 'No such
interface' error as Maraschin.
Should this be
I just got this problem!
I can't enable the second monitor as a separete monitor.
I only get it as a mirror... :-/
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface
`org.gnome.SettingsDaemon.XRANDR_2' on object at path
/org/gnome/SettingsDaemon/XRANDR
--
You received this
setting the bug to verified, the change is trivial and obviously correct
and there is no visible issue after running the new version for a week
here
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package gnome-settings-daemon -
3.4.2-0ubuntu0.2
---
gnome-settings-daemon (3.4.2-0ubuntu0.2) precise-proposed; urgency=low
* Upload to precise-proposed
[ Chris Coulson ]
* debian/patches/10_smaller_syndaemon_timeout.patch: Update to increase
the
Hello jerrylamos, or anyone else affected,
Accepted gnome-settings-daemon into precise-proposed. The package will
build now and be available in a few hours. Please help us by testing
this new package. See https://wiki.ubuntu.com/Testing/EnableProposed
for documentation how to enable and use
Ok, after discussion on IRC we figured that there is an obvious error in
10_smaller_syndaemon_timeout.patch: we add an extra argument to *args[]
without changing the allocation (i.e we write NULL out of the arrays),
not sure how that turns out in corrupting ebx but Chris is looking at it
;-)
--
The registed corruption occurs when the function returns, where it
restores the register states from the stack. At least this is an easy
fix :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
This bug was fixed in the package gnome-settings-daemon - 3.4.2-0ubuntu5
---
gnome-settings-daemon (3.4.2-0ubuntu5) quantal; urgency=low
* debian/patches/10_smaller_syndaemon_timeout.patch: Update to increase
the size of the stack allocated array for the extra argument passed
** Also affects: gnome-settings-daemon (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Importance: Undecided = High
--
You received
** Description changed:
- External monitor on notebook Acer Aspire 5253 System Settings Displays
- attempt to set resolution:
+ [Impact]
- Failed to apply configuration: %s
+ One of the patch we ship is obviously buggy and lead to stack corruption
+ issues which turned to segfault on quantal,
Updated 12 noon EST and Systems Settings Displays works, so the bug is
fixed. Anyone know how to mark the bug solved?
Thanks much!
One funny, pull down menus now have a white stripe with black lettering
for each line, example Systems Settings from the applet on the top right
of the screen. I
The bug is marked fix released so no need to change anything, the
rendering issues are side effects of the new GTK uploads and being
worked, today updates have some fixes already even if it's not perfect
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Yes, touchpad, disabled while typing. Unticking that checkbox indeed
makes g-s-d not crash. Attached is the valgrind output from when I
reenabled that setting and ran g-s-d again.
** Attachment added: Valgrind output
(And now the real valgrind log, following instructions from the wiki)
** Attachment added: valgrind.log
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1007588/+attachment/3192961/+files/valgrind.log
--
You received this bug notification because you are a member of
Disconnected external monitor. Widescreen laptop monitor came up with
1366x768 the max res. Any attempt to change that with Systems Settings
Displays including just 1360x768 causes same crash as soon as apply is
selected. The touchpad is turned on. For that matter, don't have to
change
** Also affects: gnome-settings-daemon (Ubuntu Quantal)
Importance: High
Status: Confirmed
** Changed in: gnome-settings-daemon (Ubuntu Quantal)
Assignee: (unassigned) = Chris Coulson (chrisccoulson)
--
You received this bug notification because you are a member of Ubuntu
Desktop
Ok, with some help from mterry who is able to reproduce this quite
easily, it looks like we've determined that what happens is something in
set_disable_w_typing() writes 0x0 to the %ebx register and doesn't
restore its original contents (%ebx must be preserved by the callee as
per the SysV i386
Note, you can observe that %ebx still contains 0x0 when it crashes in
the PLT.
As a workaround, you can turn off disable touchpad whilst typing, as
it is something specific to the codepath which enables this
functionality. I guess everyone experiencing this does actually have a
touchpad? (I hope
Yes I do have a touchpad on my lenovo T61 and I did have the Disable
touchpad flag set. I have now unchecked the box and see how I go. thanks
for tracking this down.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I always have touchpad turned off since I touch type and my hands are all over
the keyboard and the touchpad goes nuts. Right now I'm using an external
keyboard so I could try turning touchpad back on.
Tried simply turning touchpad on and doing Systems Settings Displays, got
Rebooted, touchpad is on, tried Systems Settings Display Apply and got
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface
`org.gnome.SettingsDaemon.XRANDR_2' on object at path
/org/gnome/SettingsDaemon/XRANDR
The external minitor did come up 1280x1024 as it was, so some
Hi,
The information here doesn't yet rule out it being something other than
a toolchain issue (this type of crash can be caused by overwriting the
GOT). Whilst I set up an i386 environment to debug this in, could
someone please try running gnome-settings-daemon in valgrind and
recreate the issue
** Attachment added: valgrind.log
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1007588/+attachment/3189382/+files/valgrind.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
This happens to me as well with gnome-settings-daemon 3.4.2-0ubuntu1 or
3.4.2-0ubuntu4. Downgrading to 3.4.1-ubuntu1 works around the problem
but is no longer an option. Backtrace:
#0 0xaedeaf00 in gdk_device_manager_list_devices@plt ()
from /usr/lib/gnome-settings-daemon-3.0/libmouse.so
#1
Backtrace after installing the glib dbgsym:
#0 0xaedeaf00 in gdk_device_manager_list_devices@plt ()
from /usr/lib/gnome-settings-daemon-3.0/libmouse.so
#1 0xaededec5 in gsd_mouse_manager_idle_cb (manager=manager@entry=0x813e620)
at gsd-mouse-manager.c:1124
#2 0xb7860570 in
Further evidence towards Michael Terry's suspicion about this possibly
being a toolchain issue: 3.4.1 also segfaults in the same location when
I rebuild it on quantal.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
And commenting out that part of gsd_mouse_manager_idle_cb makes it
segfault in another part of the plt:
0xaedf0200 in g_settings_get_boolean@plt () from
/usr/lib/gnome-settings-daemon-3.0/libmouse.so
(gdb) bt
#0 0xaedf0200 in g_settings_get_boolean@plt () from
Another point:
between 3.4.1 and 3.4.2 the mouse plugin received no related changes,
which also indicates a build/toolchain problem.
Removing the mouse plugin at leaset makes g-s-d stable for me, so I've done
that for now. I'll keep testing updates.
--
You received this bug notification
Another finger pointing to gcc: setting CC=gcc-4.6 in debian/rules makes
the resulting binary not fail this way.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1007588
** Summary changed:
- cannot set displays on dual monitor: No such interface
`org.gnome.SettingsDaemon.XRANDR_2
+ [mouse]: gnome-settings-daemon SIGSEGV in
gdk_device_manager_list_devices@plt()
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
It's interesting that the stack is crashing in the @plt version of the
function. See http://stackoverflow.com/questions/5469274/what-does-plt-
mean-here for an explanation of the plt (procedure linkage table).
So it's not even hitting libgdk. And neither gtk/gdk or gnome-settings-
daemon
32 matches
Mail list logo
