gnome-display-properties gives an error after applying changes

Bug #397455 reported by Jamie Jackson
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.

Description: Ubuntu 9.04
Release: 9.04

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.

gnome-settings-daemon:
  Installed: 2.26.1-0ubuntu2
  Candidate: 2.26.1-0ubuntu2
  Version table:
 *** 2.26.1-0ubuntu2 0
        500 http://us.archive.ubuntu.com jaunty-updates/main Packages
        100 /var/lib/dpkg/status
     2.26.0-0ubuntu4 0
        500 http://us.archive.ubuntu.com jaunty/main Packages

3) What you expected to happen

(I'm describing the simplest failing use-case, though all "useful" use-cases fail as well.)

User Actions:
A. Open System > Preference > Display
B. Change nothing
C. Click "Apply"

Expectation:
Something along the lines of: "Do you want to keep this configuration? etc."

4) What happened instead

User Actions:
A. Open System > Preference > Display
B. Change nothing
C. Click "Apply"

Result:
Error Popup Dialog:
Could not apply the selected configuration
Method "ApplyConfiguration" with signature "" on interface "org.gnome.SettingsDaemon.XRANDR" doesn't exist

Extra Details:
*This just started happening this week, and I happened to apply all automatic updates that came in over the weekend. Among the updates was an update to the kernel, I believe.
*I'm running dual head (TDMS-1 and VGA, at the moment, with a disabled LVDS built-in display of the docked laptop)
*This bug seems very similar to Bug 387391, though that one applies to Karmic (not Jaunty). Members of #gnome advised that this belongs in its own ticket, based on the version difference.
*grep "xrandr" .xsession-errors (recommended by #gnome members, yields nothing)
*The problem is intermittent. I've booted thrice since this weekend. The first yielded this problem. The second, the GUI worked fine, the third (my present boot), it fails again.
*A #gnome user suggested that I post my .config/monitors.xml, which I will do next.
*I'll also post my xorg.config and Xorg.0.log FWIW

Let me know if there's any other info I can provide.

Revision history for this message
Jamie Jackson (jamiejackson) wrote :
Revision history for this message
Jamie Jackson (jamiejackson) wrote :

*FWIW: Linux mercury 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009 i686 GNU/Linux

Revision history for this message
Jamie Jackson (jamiejackson) wrote :
Revision history for this message
Nanley Chery (nanoman) wrote :

Running 9.04 on a single display, Inspiron 1525, I also get an error message:
"""Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."""

* Although the messages are different, it looks like there's a shared problem with the policykit configuration for the display settings manager.

-------

As you can see from the screenshot above, the dialog appears behind the display manager when compiz is enabled. It appears on the upper left of the screen when compiz is disabled, but still does not have _focus_.

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
summary: - Gnome Display Settings GUI: Applying Changes Causes Error
+ gnome-display-properties gives an error after applying changes
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Nanley - your issue is not related, and is probably just a timeout presumably due to not responding to the "Does the Display look OK?" dialog. I'm not saying it's not a bug, but it isn't related to this.

Jamie - what is the output of:

killall gnome-settings-daemon
gnome-settings-daemon --debug --no-daemon

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
tags: removed: applyconfiguration jaunty
Revision history for this message
Jamie Jackson (jamiejackson) wrote :

@Chris Coulson:

That set of commands killed my session. I wasn't expecting that. Were you? (If so, was I supposed to redirect output to a file, or something?)

Anyway, now what? :-)

Also, I see you've removed my tags. For good reason, presumably, so I'll look up the tags documentation and see why you did so.

Revision history for this message
Josef Andersson (northar) wrote :

can confirm posted bug

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Jamie - killing gnome-settings-daemon shouldn't kill your session. Are you sure you didn't kill gnome-session?

Revision history for this message
Jamie Jackson (jamiejackson) wrote :

@Chris: I'm pretty sure I killed gnome-settings-daemon, but it's long-gone out of my history now, so I can't confirm.

BTW, although the problem was intermittent in the first place, I don't think I've seen it for a while.

Revision history for this message
Alexandre Derumier (aderumier-odiso) wrote :
Download full text (25.7 KiB)

Same problem for me (fglrx drivers), xrandr plugin load fine

** (gnome-settings-daemon:16400): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin
** (gnome-settings-daemon:16400): DEBUG: GnomeSettingsPluginInfo: name='XRandR' file='/usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin' location='xrandr'

* (gnome-settings-daemon:16400): DEBUG: Successfully connected to D-Bus
** (gnome-settings-daemon:16400): DEBUG: Starting settings manager
** (gnome-settings-daemon:16400): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-2.0/
** (gnome-settings-daemon:16400): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin
** (gnome-settings-daemon:16400): DEBUG: GnomeSettingsPluginInfo: name='Accessibilité du clavier' file='/usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin' location='a11y-keyboard'
** (gnome-settings-daemon:16400): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin
** (gnome-settings-daemon:16400): DEBUG: GnomeSettingsPluginInfo: name='Arrière-plan' file='/usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin' location='background'
** (gnome-settings-daemon:16400): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin
** (gnome-settings-daemon:16400): DEBUG: GnomeSettingsPluginInfo: name='Presse-papiers' file='/usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin' location='clipboard'
** (gnome-settings-daemon:16400): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin
** (gnome-settings-daemon:16400): DEBUG: GnomeSettingsPluginInfo: name='Factice' file='/usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin' location='dummy'
** (gnome-settings-daemon:16400): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin
** (gnome-settings-daemon:16400): DEBUG: GnomeSettingsPluginInfo: name='Polices' file='/usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin' location='font'
** (gnome-settings-daemon:16400): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/housekeeping.gnome-settings-plugin
** (gnome-settings-daemon:16400): DEBUG: GnomeSettingsPluginInfo: name='Housekeeping' file='/usr/lib/gnome-settings-daemon-2.0/housekeeping.gnome-settings-plugin' location='housekeeping'
** (gnome-settings-daemon:16400): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin ...

Revision history for this message
Garrri4 (excomnu) wrote :

Confirm. Nothing happend when change resolution, don't see applet-monitors.
It's was start when my computer shutting down by power off/

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → Expired
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.