[Bug 252023] Re: configure display applet crashes X in intrepid

2008-12-21 Thread Stephen Cradock
Thanks - I understand the position. In retrospect I could have saved the relevant log files after the crash and been more helpful, but that didn't happen. From my position, that could have been avoided if the delay in asking for the files had been shorter - two months (09-01 to 11-12) is a long tim

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-12-21 Thread Martin Mai
I made a misstake in my comment. We are not closing this because you said it is fixed, but because this bug report because it lacks the information we need to investigate the problem.Please reopen it if you can give us the missing information. -- configure display applet crashes X in intrepid htt

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-12-21 Thread Martin Mai
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more a

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-11-12 Thread Stephen Cradock
Sorry, don't have them any more. I haven't used the applet again, and don't want to. The applet appeared, I tried it, it failed as described above. Many changes have happened since, and I have a happily running Intrepid system. -- configure display applet crashes X in intrepid https://bugs.launch

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-11-12 Thread Sebastien Bacher
could you attach your syslog and Xorg.0.log and xorg.conf to the bug? ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low Status: New => Incomplete ** Changed in: gnome-control-center Status: New => Incomplete -- configure display applet crashes X in intr

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-09-04 Thread Timo Aaltonen
to me it seems more like a client problem if xrandr works. ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- configure display applet crashes X in intrepid https://bugs.launchpad.net/bugs/252023 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-09-01 Thread Stephen Cradock
any ideas on why the rotation is handled correctly when initiated by xrandr, but not when initiated by the new applet? -- configure display applet crashes X in intrepid https://bugs.launchpad.net/bugs/252023 You received this bug notification because you are a member of Ubuntu Bugs, which is subs

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-09-01 Thread Sebastien Bacher
the error indicates xorg is not handling correctly the rotation, likely a driver or xorg server issue ** Changed in: xorg-server (Ubuntu) Sourcepackagename: gnome-settings-daemon => xorg-server -- configure display applet crashes X in intrepid https://bugs.launchpad.net/bugs/252023 You received

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-08-08 Thread bascule
** Changed in: xorg (Ubuntu) Sourcepackagename: None => xorg ** Changed in: gnome-settings-daemon (Ubuntu) Sourcepackagename: xorg => gnome-settings-daemon -- configure display applet crashes X in intrepid https://bugs.launchpad.net/bugs/252023 You received this bug notification because you are

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-07-26 Thread Stephen Cradock
Further information: the relevant plugin calls xrandr to set screen and display properties. I have checked xrandr itself on my Intrepid system, and it works correctly to set the display inverted, normal, left, normal in sequence. The bug reported above involves the "new" applet that calls the xran

[Bug 252023] Re: configure display applet crashes X in intrepid

2008-07-25 Thread Stephen Cradock
The "new" applet apparently simply calls the Screen Resolution capplet of gnome-control-center. This means that the crash is caused by a gnome component. Can someone at least push this upstream, please? ** Also affects: gnome-control-center Importance: Undecided Status: New -- configur