Contributor sandoz

Adding a "Secure Delete" feature to shred files in the trash can beyond recovery.

People around the globe that are using/concidering using Ubuntu are afraid that some of their hardware won't work for them. And some are frustrated to buy additional add-on cards to work around unsupportad onboard chips. All this could be avoided with a lookup in an ubuntu Hardware Database Website.

Some problematic hardware can be used with more or less work if helping information is available together with the hardware compatabillity data.

The hardware database can be found at http://hwdb.ubuntu.com/

From idea #47: The data should then be available in a format that is simple for users to browse on-line when considering new hardware.

I'm a big fan of Images like .iso. However it is not very easy to mount these Images.

I feel there should be a Tool in Nautilus and Dolphin which allows mounting Images by double Click or something similar. (This feature exists int MacOS). Or with a right click on the I think that would be a very useful Tool for every one.
A good example for this is CDemu.

I know there are some other good programs, but I think that would be the easiest way

Replace initscripts with upstart events. Our boot sequence is currently slow, full of race conditions and poor interactions, especially with competition between the series of tasks run by sysv-rc, udev and sometimes just with the kernel. We developed upstart so that we could have a truly event driven boot sequence that would be fast, reliable and flexible; we should take advantage of it.

I guess everybody has experienced the rather long boot up times in Ubuntu (particularly with laptops). I know they are already working on it, but the change from feisty to gutsy was a pain in the ass in terms of boot up speed.
A default WinXP installation beats Ubuntu's boot up time by far!! That shouldn't be allowed fellas!!

I therefore propose to the development team (both Ubuntu and by extension Gnome)to work on the improvement of boot up times in Ubuntu systems.

Ubuntu needs to go green. Powertop, Lesswatts and other tools have finally hit the Linux scene to pave the way for better power management. It needs to be said, "if you want your battery to last longest, or have your energy bill be the lowest, you better use Ubuntu Linux."

At the moment it's possible to manage traditional wired and WiFi connections using Network Manager. To connect via a modem, a 3G/GPRS card, over bluetooth to a cell phone or via USB to another device requires that the user installs extra packages, and does a fair amount of configuration that isn't found in Network Manager.

A single unified tool should be provided which allows the user to connect to a network (or internet) via any supported method. It would also be useful to provide an extension to this tool to manage firewall rules and network connection sharing.

If we really want to make (K/X)Ubuntu for the layperson, than we need to be able to set up more than one user account during the installation.

Families won't like (K/X)Ubuntu if they can't make all their own personal user accounts from the get-go.

Right now, to install (K/X)Ubuntu for multiple users, you have to set one up, then log in, add a new user, and go through the process of setting of group permissions mirroring that of the first user. This is NOT intuitive.

This is what the setup looks like (KDE-wise),
http://www.flickr.com/photos/lunarcloud_88/2879394590/
http://farm4.static.flickr.com/3085/2879394590_d72d2664d7.jpg

Here is an acceptable mock-up, feel free to post your mock-ups:
http://www.flickr.com/photos/lunarcloud_88/2879462152/
http://farm4.static.flickr.com/3163/2879462152_585c12d986.jpg?v=0

There should be a guest user in there to show that it will exist (possibly disabled).
The user icon can be selected (gdm/kdm should set icon source to "user,admin")
You can add a user, and the computer name is a seperated entity, automatically defined by the FIRST user's name, but obviously changeable as before.

One of the things included in Hardy was ufw (Uncomplicated firewall wall), but everything has to be done via CLI. There is a very nice GUI frontend being developed for it and it would be nice if it is bundled as a default package.

Links to the project:
https://launchpad.net/gui-ufw
http://gufw.tuxfamily.org/index.html

When you use quite often USB key, you always have to unmount them correctly to keep your data safe. When you're copying a file on a USB key, you must wait to empty the copy buffer.

I would propose to link the USB key icon to the state of the transfer :
- If there's a transfer, we can see clearly that we can not take the USB key away.
- When transfer is finished and the buffer emptied, the icon can show that the USB key can be safely removed

and thus it's not yet useful to click on "unmount", because the unmount management is totally transparent, and treated by the system. We can simply pick the USB key away because transfer is already finish and correctly closed. This will be a great innovation to simplify unmount such usual disks.

edit : Maybe the icon can stay like the same, but w can add some little sub-icon to inform of the state.

(see also ideas 1373 and 10032)

Warn users if they try to use a weak password. In the style of google account creation.

I originally thought that this would be good for the users login password. However, possibly this could be implemented for all passwords system wide.