I agree with Paul. As I've stated. I'm trying to help test Jaunty. I'm doing what amounts to black-box testing. I have not added, removed, or otherwise changed any programs that are on my system since i upgraded. One of the packages that I didn't add to my system is reporting an error to me when I try to use it, and its giving me no indication of what the error is caused by other than a cryptic message. It says nothing about installing another package, and I really have no desire to need to install extra packages to get programs that are already in my menu working.
Some how, some way, there is a bug in this situation. On Mon, Mar 23, 2009 at 7:32 PM, Paul Broadhead < pjbr...@twinmoons.clara.co.uk> wrote: > I must admit that I'm not very pleased with this "bug" being marked as > invalid. I know that the menu item needs an extra package before it > will work; it was me that identified the issue. However, as others have > said, why have an icon in your menus that does not work unless it is a > bug? At the very least, the error message should be changed to give > some hint as to what is required before this launcher will function. > > -- > "New Login in a Window" fails > https://bugs.launchpad.net/bugs/283426 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “gdm” source package in Ubuntu: Invalid > > Bug description: > The "Application->system Tools->New Login in a Window" icon failed with the > following error dialogue: > > "Cannot start new display > The X server failed. Perhaps it is not configured well." > > The same occurs if I run "gdmflexiserver --xnest" or just "gdmflexiserver" > from a terminal. The error occurs with visual effects enabled or disabled. > Switching to an alternative login using the fast user switch works fine. > > This is a clean Intrepid install from the last alpha, fully updated as of > today. I have not modified the Xorg.conf file. > -- "New Login in a Window" fails https://bugs.launchpad.net/bugs/283426 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
