Often I'll login in to Ubuntu to discover I have updates that need to be installed. I've got a lot of work to do so I decide to install the updates after I completed my work.
The issue is at this point I install the updates and walk away from the machine to go to sleep, go out to eat, etc. The updates will have installed while I was gone but the machine will have been on potentially for hours just wasting electricity
Written by brk0_0 the 16 May 12 at 18:33.
Global category: Usability.
Duplicate
Many useful options are still missing, like natural-scroll. The main today's features are not easily accessible from these menus and user may be frustrated when trying to use it.
I think it will be better if people can edit their comments in Ubuntu Brainstorm. When comments are edited, there should be a timestamp showing the time it is edited like those in Ubuntu Forums. Also, there could be a time limit for editing comments like an hour or two.
Since start using Ubuntu, i started to got curious on how can i make my own .deb files.
Well, i can imagine most of you when reading this seems to be about on sticking here some Debian or Ubuntu tutorial links about it, but mostly are too complicated or messy, specially when the process of making .deb files is not much more than packaging some non-executable documents.
The easier ways i found on making .deb were:
1. using alien over .tar.gz tarballs (but it lacks on very important 'control' information for the databases, like dependencies, description, etc.)
2. using a .sh with plenty of 'echo' and 'ar' commands, but it can create corrupt .deb files, and so incompatible with gdebi, dpkg and so on...
My idea would be being able to create a .deb file from a tool like FileRoller, but of course all suggestions and reccomendations of new tools i may not know are hugelly welcome! =)
(in meanwhile, i'm getting stuck into creating tarballs, and expanding them with 'tar -zxvf tarball.tar.gz -C /')
By doing this, transition from Grub to GDM (or KDM or whatever) would be done almost instantly. Plymouth will use a graphical boot mode with a fallback method to text for those computers that don't have hardware support.
It would be good if we could optionally vote a specific reason why a brainstorm idea is being voted down. Maybe add a drop-down box next to the "See the 1 comments". Otherwise, perfectly good ideas may be voted down without comments on a minor technically, and the process isn't an optimising submission process (we want average ideas to be actively improved to be good).
The dropdown box may contain:
- Security Concerns
- Technically not possible
- Poor solution to the problem
- Duplicate of another idea
- Incorrect
- Spam
- No reason (same effect as clicking down arrow)
That way people can get an idea of why their idea sucks, and address them, or improve them. This would be optional but may improve the quality of ideas, so people don't keep getting caught in the same mistakes. Also, easy to implement, and the old method is still possible.