Written by msriram the 5 Sep 12 at 18:54.

Enabling it from the GUI is the way to go in the long run. It could be the default desktop application, or Nvidia / AMD driver application.

Enabling it from the GUI is the way to go in the long run. It could be the default desktop application, or Nvidia / AMD driver application.

Written by diegoj the 26 Nov 08 at 02:14.

Ubuntu Brainstorm was updated in January 2009. Since the idea #15971 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 #15971 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 gruntzen the 22 Mar 12 at 13:49.

A lightweight, simple calendar application for GNOME with integration to the indicator and NotifyOSD seems like the sort of small detail that would add a lot of polish to Ubuntu. Something like the elementary project's "Maya" (could it be adopted and used in Ubuntu?), or iCal on OSX.

Preferably, the calendar would sync to Google Calendar and iCloud (and various other calendar services).

A lightweight, simple calendar application for GNOME with integration to the indicator and NotifyOSD seems like the sort of small detail that would add a lot of polish to Ubuntu. Something like the elementary project's "Maya" (could it be adopted and used in Ubuntu?), or iCal on OSX. Preferably, the calendar would sync to Google Calendar and iCloud (and various other calendar services).

Written by MsG the 28 Mar 12 at 20:54.

Make a generic calendar API in Ubuntu and a seperate application which can talk to services like Google Agenda, this application then can hook into the API. The API can also be used by desktop email applications for people who DO use a desktop email or calendar client. This will suit both.

Make a generic calendar API in Ubuntu and a seperate application which can talk to services like Google Agenda, this application then can hook into the API. The API can also be used by desktop email applications for people who DO use a desktop email or calendar client. This will suit both.

Written by RobinJ1995 the 9 Apr 12 at 08:06.

Provide integration with services like Remember The Milk and Google Calendar.

Provide integration with services like Remember The Milk and Google Calendar.

Written by stevenroose the 28 Sep 12 at 09:53.

My suggestion is to start development of a simple calendar application, mostly mimicking iCal, that has some basic, but essential, functionality. I think about managing multiple calendars, syncing with Google Calendar / Exchange / iCloud and (auto-)importing ical files.

My suggestion is to start development of a simple calendar application, mostly mimicking iCal, that has some basic, but essential, functionality. I think about managing multiple calendars, syncing with Google Calendar / Exchange / iCloud and (auto-)importing ical files.

Written by gruntzen the 2 Oct 12 at 14:58.

Elementary's Maya ( https://launchpad.net/maya ) shows promise, but development is slow to the point of being nearly nonexistent. If additional support could be given to the project (or a fork of the project), it could become a great application (at the moment, it is missing cloud syncing and other important features).

Elementary's Maya ( https://launchpad.net/maya ) shows promise, but development is slow to the point of being nearly nonexistent. If additional support could be given to the project (or a fork of the project), it could become a great application (at the moment, it is missing cloud syncing and other important features).

Written by Porky the 4 Oct 12 at 05:34.

Sunbird may no longer be maintained, but its still a handy FOSS calendar. It can be customized with add-ons just like any other mozilla project and can come in quite handy. Since the code is open, it can be retailored to match the specific needs of the average Ubuntu user.

Sunbird may no longer be maintained, but its still a handy FOSS calendar. It can be customized with add-ons just like any other mozilla project and can come in quite handy. Since the code is open, it can be retailored to match the specific needs of the average Ubuntu user.

Written by eugene2k the 15 Jan 09 at 13:30.

This will allow the users to install 32bit packages if there aren't any 64bit ones.

This will allow the users to install 32bit packages if there aren't any 64bit ones.

Written by Warbo the 17 Jan 09 at 07:49.

I'm not a fan of special-cases, so I thought about making this more generic, and applicable to other situations. I propose that architectures can declare support for each other, for example amd64 can support i386, i686, etc. which implements the above solution, allowing its own packages as well as its supported packages to be installed.

It could also be applied to other situations, like Loongson 3 MIPS processors from China which also support x86 code. In this case a new architecture loongson3 could be made which supports mips and i386.

This would be built into dpkg and apt.

Very little mirror overhead would be needed, since such architectures wouldn't need their own packages, they could use any which they support (which are already sitting on the mirrors as I write this).

Perhaps there should be a priority, for example with loongson3 it would be better to have mips than i386, but this could simply be done by having them in a config file, and checking each one listed in turn until a match is found, and putting mips ahead of i386.

I'm not a fan of special-cases, so I thought about making this more generic, and applicable to other situations. I propose that architectures can declare support for each other, for example amd64 can support i386, i686, etc. which implements the above solution, allowing its own packages as well as its supported packages to be installed. It could also be applied to other situations, like Loongson 3 MIPS processors from China which also support x86 code. In this case a new architecture loongson3 could be made which supports mips and i386. This would be built into dpkg and apt. Very little mirror overhead would be needed, since such architectures wouldn't need their own packages, they could use any which they support (which are already sitting on the mirrors as I write this). Perhaps there should be a priority, for example with loongson3 it would be better to have mips than i386, but this could simply be done by having them in a config file, and checking each one listed in turn until a match is found, and putting mips ahead of i386.

Written by maticmatija the 3 Nov 08 at 12:29.

Ubuntu Brainstorm was updated in January 2009. Since the idea #15190 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 #15190 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 Endolith the 13 Oct 08 at 18:31.

It would be nice if we could see at a glance that a directory contains nothing, or contains only other directories.

It would be nice if we could see at a glance that a directory contains nothing, or contains only other directories.

Written by Living-FOSS-iL the 19 May 09 at 07:45.

Nautilus is already aware of disks that are unmounted or ejected. Why not extended its range of actions to closing the window of the unavailable disk.

Nautilus is already aware of disks that are unmounted or ejected. Why not extended its range of actions to closing the window of the unavailable disk.

Written by Ssdg the 19 May 09 at 15:46.

If you use tabs to browse your media, if the window closes, you loose all tabs. so juste close one tab and if it's the last one close the window.

If you use tabs to browse your media, if the window closes, you loose all tabs. so juste close one tab and if it's the last one close the window.

Written by mitkaese the 22 May 09 at 00:58.

I'm not sure auto-closing windows on the user is the best idea. I can imagine times when when the user needs to know what was just removed, e.g. to compare with those on another drive.

It seems a much more robust solution to visually/sonically signify that the drive is no longer mounted, perhaps by graying out the window or adding an "[Ejected]" to the title bar.

Additionally, the Ubuntu's system notification could let the user know the drive has been removed and *ask* if the correspondent windows should be closed.

I'm not sure auto-closing windows on the user is the best idea. I can imagine times when when the user needs to know what was just removed, e.g. to compare with those on another drive. It seems a much more robust solution to visually/sonically signify that the drive is no longer mounted, perhaps by graying out the window or adding an "[Ejected]" to the title bar. Additionally, the Ubuntu's system notification could let the user know the drive has been removed and *ask* if the correspondent windows should be closed.

Written by Clorox the 23 May 09 at 01:25.

#4 is a great idea, but if the user is asked whether the window should be closed, then there should be a "do not ask again" option.

#4 is a great idea, but if the user is asked whether the window should be closed, then there should be a "do not ask again" option.

Written by LiraNuna the 23 May 09 at 06:56.

Ubuntu Jaunty (9.04) have a new marvelous notification system. Use it to report that the media is now safe to remove.

Ubuntu Jaunty (9.04) have a new marvelous notification system. Use it to report that the media is now safe to remove.

Written by Kver the 25 May 09 at 00:40.

Instead of closing the tab, move the current location to either the /media folder, or the parent folder of the mount point.

Instead of closing the tab, move the current location to either the /media folder, or the parent folder of the mount point.

Written by Endolith the 10 Nov 08 at 03:04.

There should be a "Guest session" button on the Locked screen for friends to open the Guest session, so they can check their email or whatever without knowing anything else about Gnome or Linux or user accounts.

Currently the locked screen has:

Password: [_______________]
[Leave Message] [Switch User] [Cancel] [Unlock]

I'd say change it to:

Password: [_______________]
[Leave Message] [Guest Session] [Switch User] [Cancel] [Unlock]

There should be a "Guest session" button on the Locked screen for friends to open the Guest session, so they can check their email or whatever without knowing anything else about Gnome or Linux or user accounts. Currently the locked screen has: Password: [_______________] [Leave Message] [Switch User] [Cancel] [Unlock] I'd say change it to: Password: [_______________] [Leave Message] [Guest Session] [Switch User] [Cancel] [Unlock]

Written by Eldmannen the 29 Oct 08 at 01:14.

Ubuntu Brainstorm was updated in January 2009. Since the idea #14938 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 #14938 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 radioxid the 22 Apr 10 at 22:08.

Because the inconvenience is that the copy can break at any advanced or random time.

The best is to stop the copy at the beginning or at least to offer to avoid the files too large during the copy.

Because the inconvenience is that the copy can break at any advanced or random time. The best is to stop the copy at the beginning or at least to offer to avoid the files too large during the copy.

Written by Lachu the 24 Apr 10 at 07:42.

System should first try to reserve space for file, when may be copied to removable device. It will reduces IO operations and resolves this matter.

System should first try to reserve space for file, when may be copied to removable device. It will reduces IO operations and resolves this matter.

Written by rnerwein the 28 Apr 10 at 06:15.

if the warning will be implemented then there should also be
a posibilty to swicht this of by user account.

if the warning will be implemented then there should also be a posibilty to swicht this of by user account.

Written by thiagomoraesp the 28 Apr 10 at 14:01.

We need to explain to the user that this is a filesystem limitation and not a ubuntu limitation :)

We need to explain to the user that this is a filesystem limitation and not a ubuntu limitation :)

Written by gumshore the 28 Apr 10 at 23:23.

If the OS told the user that there is a limitation, thats fine, but chances are, the user still wants to copy the file. If we could display a dialog that offered to use file-roller or gzip or whatever to make an uncompressed archive of the file, and split it up, a user on a M$ computer could un-archive it with either WinR@R or 7-zip.

If the OS told the user that there is a limitation, thats fine, but chances are, the user still wants to copy the file. If we could display a dialog that offered to use file-roller or gzip or whatever to make an uncompressed archive of the file, and split it up, a user on a M$ computer could un-archive it with either WinR@R or 7-zip.

Written by robheus the 29 Apr 10 at 06:46.

The problem does not just show up when copying, since also when dowloading a file to a FAT file system, this could happen. Also, somewhat unrelated, on file systems which DO facilitate large files, the writing or copying of a file onto such a filesystem might break, because of a device (external USB harddisk) might be too slow.
Also a warning against that (having to wait an hour for a copy which still fails feels miserable) should be issued.

The solution would require two parts:
1. The tools that do such kind of copying (including file download) should warn against the breaking of the copy due to characteristics of the device and/or filesystem, and direct the user to utilize in that case another, better equipped tool.

2. Create a utility that can both split a file in (user definable, but with a good default value that depends on the filesystem in question) chunks/parts, and later join them together when doing the reverse transaction (for example: split with the option -j to join, and the option -s to split). As a command line option, offer also compression of the file to be written. Have the tool also resumable, so that it can resume a broken partial write, and/or have it check for the actual amount of the file written, and delay as necessary the copying if the device to write on is too slow to keep up.

3. Implement this also in other copy tools, like download managers, FTP, etc.

The problem does not just show up when copying, since also when dowloading a file to a FAT file system, this could happen. Also, somewhat unrelated, on file systems which DO facilitate large files, the writing or copying of a file onto such a filesystem might break, because of a device (external USB harddisk) might be too slow. Also a warning against that (having to wait an hour for a copy which still fails feels miserable) should be issued. The solution would require two parts: 1. The tools that do such kind of copying (including file download) should warn against the breaking of the copy due to characteristics of the device and/or filesystem, and direct the user to utilize in that case another, better equipped tool. 2. Create a utility that can both split a file in (user definable, but with a good default value that depends on the filesystem in question) chunks/parts, and later join them together when doing the reverse transaction (for example: split with the option -j to join, and the option -s <size> to split). As a command line option, offer also compression of the file to be written. Have the tool also resumable, so that it can resume a broken partial write, and/or have it check for the actual amount of the file written, and delay as necessary the copying if the device to write on is too slow to keep up. 3. Implement this also in other copy tools, like download managers, FTP, etc.

Written by DaVince the 14 May 10 at 22:57.

This means the Linux filesystem driver for FAT32 will handle the split files differently by showing, and reading, the split parts of the file as a single "normal" file.

Users of other OSes (like Windows) would see the split files instead.

This means the Linux filesystem driver for FAT32 will handle the split files differently by showing, and reading, the split parts of the file as a single "normal" file. Users of other OSes (like Windows) would see the split files instead.

Written by elypter the 27 May 10 at 18:51.

of cause with a warning and with an option to convert files.
Depending on the device a warning that most mp3players or cameras only work with fat

of cause with a warning and with an option to convert files. Depending on the device a warning that most mp3players or cameras only work with fat

Written by mitzampt the 14 Feb 11 at 13:20.

Offer as solution packing into smaller archives if the user only needs to store the file

Offer as solution packing into smaller archives if the user only needs to store the file