Written by cenora the 16 Mar 09 at 21:56.

To unmount the actual device and not only each individual partition.

To unmount the actual device and not only each individual partition.

Written by cenora the 18 Mar 09 at 21:18.

From what I understand, ext3 waits to write files to a device.

If you try to eject the device, there could be files waiting to be written or deleted.

System should say: "Program X is using the device" [Wait] [Force Eject]

From what I understand, ext3 waits to write files to a device. If you try to eject the device, there could be files waiting to be written or deleted. System should say: "Program X is using the device" [Wait] [Force Eject]

Written by elias1884 the 20 Mar 09 at 00:00.

I am regularly told, that an application is blocking device removal. It would be great if I was also told, which app that is.

We can't expect users to user lsof to find out, how to get their USB pendrive released. The greatest solution I could imagine would be, if the notification app asks me, if I want to be taken to the blocking application, so I can close it or whatever. Taken in the sense of switching desktops and bringing the app to the front, if it is a GUI app.

I am regularly told, that an application is blocking device removal. It would be great if I was also told, which app that is. We can't expect users to user lsof to find out, how to get their USB pendrive released. The greatest solution I could imagine would be, if the notification app asks me, if I want to be taken to the blocking application, so I can close it or whatever. Taken in the sense of switching desktops and bringing the app to the front, if it is a GUI app.

Written by Lachu the 21 Mar 09 at 14:35.

Add to device icon menu "device information dialog". We can display on it all partition on this device(name and size). We can allows to unmount whole device. Another feature is to display all programs, which are using that device.

Add to device icon menu "device information dialog". We can display on it all partition on this device(name and size). We can allows to unmount whole device. Another feature is to display all programs, which are using that device.

Written by mattmyers83 the 8 Aug 09 at 16:20.

Maybe you could add more functionality to the administration/hardware drivers application to include a centralized point for all hardware related configuration / information.

You could view all of the hardware for the system and see what drivers are installed for that device. whether it be proprietary drivers provided by the current hardware drivers application or a built in driver.

You could have all information including detected chipset, IRQ, etc.

Maybe you could add more functionality to the administration/hardware drivers application to include a centralized point for all hardware related configuration / information. You could view all of the hardware for the system and see what drivers are installed for that device. whether it be proprietary drivers provided by the current hardware drivers application or a built in driver. You could have all information including detected chipset, IRQ, etc.

Written by corq the 28 Feb 09 at 14:10.

I suggest a small wizard or prompt, after detecting the insertion of the usb speakers or headset, "USB Audio detected; Would you like this device to be your primary audio speakers? With, perhaps a checkbox for "Only this session" for folks who might just be using a headset for Skype meetings and such.

I suggest a small wizard or prompt, after detecting the insertion of the usb speakers or headset, "USB Audio detected; Would you like this device to be your primary audio speakers? With, perhaps a checkbox for "Only this session" for folks who might just be using a headset for Skype meetings and such.

Written by Cé the 1 Mar 09 at 09:24.

This is a problem for everybody with multiple soundcards, Create a gui to set wich soundcard is primary, secondary and so on.

Best regards,
Cedric

This is a problem for everybody with multiple soundcards, Create a gui to set wich soundcard is primary, secondary and so on. Best regards, Cedric

Written by Seph_VII the 6 Mar 09 at 18:12.

My USB-speakers(Logitech Z-10) are detected and work perfectly in Jaunty, so I assume the problem has been fixed.

My USB-speakers(Logitech Z-10) are detected and work perfectly in Jaunty, so I assume the problem has been fixed.

Written by tiede the 9 Apr 09 at 18:23.

Nautilus could send such a request to gnome-device-manager or even hal, if needed, and that program (preferrably gnome-device-manager) could then call on mtools, e2label, or other such program, to accomplish the task.

Nautilus could send such a request to gnome-device-manager or even hal, if needed, and that program (preferrably gnome-device-manager) could then call on mtools, e2label, or other such program, to accomplish the task.

Written by jamesisin the 10 Apr 09 at 07:44.

I used a much easier method for changing drive labels than the one the op links to above. It is found in the first segment of this blog post:

http://www.soundunreason.com/InkWell/?p=918

What could be improved in this method is making it easier to remount an unmouted drive using GParted.

I used a much easier method for changing drive labels than the one the op links to above. It is found in the first segment of this blog post: http://www.soundunreason.com/InkWell/?p=918 What could be improved in this method is making it easier to remount an unmouted drive using GParted.

Written by sighK the 22 Apr 09 at 18:55.

read man zenity --list
parse the mount command for block devices
show these in the zenity list
then use parted with the return of zenity with gksudo to write the device label.

read man zenity --list parse the mount command for block devices show these in the zenity list then use parted with the return of zenity with gksudo to write the device label.

Written by antalar the 3 Dec 08 at 08:21.

Ubuntu Brainstorm was updated in January 2009. Since the idea #16169 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #16169 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by Silvercircle the 21 Mar 09 at 18:11.

The solution for the problem (mountcommand with the -o force option) also is pointed out under details, but most users don't bother to click on details, so why don't you just create a buttion "Use Force" which runs the mount command for you?

Soultion=> Add a forcemount button to the errordialogue

The solution for the problem (mountcommand with the -o force option) also is pointed out under details, but most users don't bother to click on details, so why don't you just create a buttion "Use Force" which runs the mount command for you? Soultion=> Add a forcemount button to the errordialogue

Written by shawe_ewahs the 20 Sep 09 at 11:51.

Can be possible do a better work with checkbox-gtk, if it proposes to users of Ubuntu do a Checkbox-gtk test in here first run, Ubuntu can have a database of existing hardware in use, and people can contribute to have a better configuration of it.

A lot of people have problems with here graphical card, bluetooth devices, sound cards, ... and a lot of times, the reason that it don't work correctly are stupid things, like this:

* Add on "/etc/rc.local" this line "hciconfig hci0 reset"
* Add on "/etc/modprobe.d/nano alsa-base.conf" this line "options snd-hda-intel model=vaio". These occure with a lot of laptops and different soundcards.

And also can be solution for more complex problems with hardware that don't work well or need patches for the moment. Like my graphic card, that can control brightness by default, but exists differents ways to try to do a partial solution, that almost "work", it hasn't the best way, but almost "work".

Can be possible do a better work with checkbox-gtk, if it proposes to users of Ubuntu do a Checkbox-gtk test in here first run, Ubuntu can have a database of existing hardware in use, and people can contribute to have a better configuration of it. A lot of people have problems with here graphical card, bluetooth devices, sound cards, ... and a lot of times, the reason that it don't work correctly are stupid things, like this: * Add on "/etc/rc.local" this line "hciconfig hci0 reset" * Add on "/etc/modprobe.d/nano alsa-base.conf" this line "options snd-hda-intel model=vaio". These occure with a lot of laptops and different soundcards. And also can be solution for more complex problems with hardware that don't work well or need patches for the moment. Like my graphic card, that can control brightness by default, but exists differents ways to try to do a partial solution, that almost "work", it hasn't the best way, but almost "work".

Written by kevinp93 the 21 Feb 09 at 21:39.

At the moment, I am thinking of seeing a user-friendly device manager. Click on the hardware, and change the settings, without even using any commands.

At the moment, I am thinking of seeing a user-friendly device manager. Click on the hardware, and change the settings, without even using any commands.

Written by wouter215 the 22 Feb 09 at 21:12.

a device manager like this:
http://i.zdnet.com/gallery/249310-480-360.jpg
this makes it easy to oversee all devices that are connected.

a device manager like this: http://i.zdnet.com/gallery/249310-480-360.jpg this makes it easy to oversee all devices that are connected.

Written by dhillonv the 20 Oct 09 at 00:11.

I think this can be solved if we make a classifier in Java. This classifier would modify existing drivers and mold them to fit the new device by trail/error. The success rate of this classifier would increase based on training and also the quality of the code. Increasing both give us a classifier capable of making good device drivers :)

I think this can be solved if we make a classifier in Java. This classifier would modify existing drivers and mold them to fit the new device by trail/error. The success rate of this classifier would increase based on training and also the quality of the code. Increasing both give us a classifier capable of making good device drivers :)

Written by Lachu the 24 Oct 09 at 14:06.

It's great idea, but should be restricted only to USB devices. USB port are cross platform port, but we don't have cross platform drivers.

It's great idea, but should be restricted only to USB devices. USB port are cross platform port, but we don't have cross platform drivers.

Written by milanchez the 12 Oct 09 at 21:16.

Side by side versions of packages which are activated/deactivated (after reboot).

Side by side versions of packages which are activated/deactivated (after reboot).

Written by Lachu the 14 Oct 09 at 08:41.

Create DBus API to support switching of VT. It can work in simple way. Deamon loads X driver and only switching screen. X Window System will load driver for new DBus API. It could allow to use newest drivers by older X Servers and prevent to X Window System problem, which causes older architecture. I know it's hard, but it can be great.

Create DBus API to support switching of VT. It can work in simple way. Deamon loads X driver and only switching screen. X Window System will load driver for new DBus API. It could allow to use newest drivers by older X Servers and prevent to X Window System problem, which causes older architecture. I know it's hard, but it can be great.