When working with multiple monitors of different resolutions, and when not working with panels above/below the smaller of the monitors, the desktop icons can spill into areas of the desktop not visible to the user. It is also possible to lose the mouse in this area because the mouse boundaries are specified by the desktop, not the screens.

When in multi-head mode on Windows using different resolutions, Windows restricts the movement of the mouse to stay within the area of the desktop, which may be non-rectangular. Gnome (or even X) needs to do something like this.

It has come to my attention ( so called blockers can be found at http://pastebin.com/m39042b41 ) that there are plans to move from Rhythmbox to Banshee in either "Karmic Koala" or "Lame Llama"

Let me show strong opposition. Regardless of the arguable yet significant issues both legal and practical with the mere inclusion of Mono apps in the default (I personally think the best path is to get rid of these apps from the default, not to add more) There's also another issue... I like Rhythmbox .

It is not just for technical issues such as "Banshee uses twice as much memory as Rhythmbox" It is also because of the cleaner interface and that in many ways it follows the ubuntu philosophy much better. Regardless, I do not think I a am alone, as noticeable in Idea #18932 There's strong opposition to switching from this app. Instead, what the community wants is that ubuntu sticks to rhythmbox and keep improving it.

It is a little frightening that these decisions are being taken out of artificial advantages such as theorically saving 6.1 MB, The Mono runtime itself adds to much heavier space requirements than Rhythmbox.

PS: What's the message Canonical would be giving to the world if we need MS technology even for basic apps such as music libraries? I mean, really...

Trying karmic I've seen that it warns you about low disk space on any partition. The problem is that it uses a dialog window and you must press a key to get rid of it. The warning itself it's a good idea but that method it's not convenient at all; it's very annoying.

At the moment, if I plug in a webcam or a USB mouse, there is nothing visual to say that Ubuntu has correctly detected the new hardware, to see if it's been properly detected, I have to actually start using it.

(wasn't sure what related project to put)

Currently when a program falls into an infinite loop and hangs, grabbing nearly all the cpu cycles when it does, what's the current procedure for the end user? The computer will most certainly be painfully slow to user input (assuming it's responsive at all.) We need to kill the offending process ASAP. This can be daunting for new users, and frustrating even for seasoned users. Currently the options include xkill, killing from the System Monitor, ps then kill, or (one of my current favorites) pkill. Sometimes X is so slowed down, I even Clt-Alt-F1 into a fresh tty. In the 21st century can't we do better?

What about this instead: When a runnaway process grabs nearly all the CPU cycles, 3 seconds later a 'ballon' notification should appear in the taskbar informing you that the system suspects this, and offering you the option to 'click here to kill the program'. Offer this functionality as an option that can be turned of if the user so choses.

Why not have the system realize what's going on, 'quaranteen' the damage by automatically renicing processes, and provide a notification with option to terminate the offending process?

In the new way I have suggested, the system monitors it's processes. If a process belonging to a currently logged-in user suddenly grabs 95% (just for example) or more CPU and keeps hold of it for more than, say 3 seconds, a few things happen. First, the offending process is automaticallly re-niced to the highest nice value. Second, a freedesktop.org - compliant singal is sent. Third, GNOME, KDE, XFCE, or whatever window manager / desktop enviro is running picks up the signal and creates an alert to the user. The processes for sending the signal, receiving it and displaying the alert have all been re-niced to the lowest nice value, effectively clearing the way.

Maybe the alert will take the form of a 'balloon' from the taskbar? Maybe a nice compiz fade-in popup? Maybe something like mumbles-project.org uses? Whatever method is used, the alert notification must supply a 'one click' to terminate the offending process.

What we're doing here is changing the paradigm. The question isn't 'How do we allow users to terminate a misbehaving program?' Intead its 'How do we ensure users's systems will remain responsive to input.'

[....]

The Gnome Power Manager Manual preferences screen (specifically section 5.2)
would be significantly improved by language that would distinguish between
suspend and hibernate (APCI S3 and ACPI S4. A lot of newbies don't know how
they differ functionally.

The developers of GNOME are thinking about changing their interface. They want to replace the current interface (top panel and bottom panel) with something they call GNOME Shell. This new interface will have a bar on the top called "Activities". The old menu called "Applications" will be gone and you'll have to type the name of the application to start this application.

Screenshots:
http://live.gnome.org/GnomeShell/Screenshots

I really don't like this new interface and I've seen many other people complaining about this new interface.

Right now dragging and dropping items is fickle and inconsistent. It is unclear what exactly will happen when an item is dropped somewhere. Sometimes the expected action happens, sometimes nothing happens, and worse still, sometimes the wrong action ensues.

One can switch to the Guest Account from inside a logged-in GNOME account (using the menu item) or logged-in to another WM (by running the script), but if the screen is locked (with gnome-screensaver or xscreensaver) or logged out (GDM) there is no way to get to the guest session.

Currently no matter what wallpaper you have the font is always white and you have to change it manually in the gnome colour chooser.