BitmapCake!

Note: This issue has been fixed in DBeaver 4.1 :)




I've been using DBeaver for a while to work on some Postgres databases (because PgAdmin 4 sucks!) and I found this tool to be really awesome so far. However, as we know, not everything is perfect, and I found a little bug in DBeaver which is, that you cannot add a new record by clicking on the small plus (+) sign on the grid view. This is not working only on new / empty tables. If the table has at least one record, this works.

However, you are not left alone helpless in this case. There's a small workaround to overcome the issue. This is how to insert data into a new empty table without writing a sql query.

All you have to do it press and hold the "Shift" key while cliking on that green plus sign. Then DBeaver will add a new row as usual :) That's simple, isn't it?

I hope this will be useful to someone. Please don't forget to leave a comment if you know any other work around to this :)

Hello guys, here is another issue I faced today with Ubuntu 16.04. I have a laptop which runs Windows 10 and Ubuntu 16.04 on dual boot. Sometimes I have to switch between the two systems depending on the project I work. So it's very usual that I switch between them a few times in some days.

If you do the same, you may have already got this error, or at some point you will get this error when you try to mount a partition that you use with Windows and Ubuntu both. I'll show you how to fix this easily.

Error Details:

Error mounting /dev/sda2 at /media/nimeshka/6E86FACC86FA93B5: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sda2" "/media/nimeshka/6E86FACC86FA93B5"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sda2': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
You get this error and you are unable to mount the partition. However, Ubuntu lets you mount the partition in a read-only mode which may be enough sometimes, but it's not a real solution to this. Before diving into fixing the problem, let's look closely at the error message once again. If you read it carefully, you will see that Ubuntu reports the error in a clear and a concise way. Towards the end of the error message, you can see it states "Please resume and shutdown Windows fully (no hibernation or fast restarting)". That basically gives you a hint on the solution. It says that Windows has not been fully shutdown, hence Ubuntu is unable to mount it. So the problem is really in Windows, not in Ubuntu.

You may wonder that you didn't hibernate Windows, then how could this happen? Yeah, it happens because with recent versions of Windows, they have introduced some new features to speed up the booting process, known as "Fast Startup" in Windows 10 and "Fast Boot" in Windows 8. It's something very similar to (or almost same as) hibernate option you had with previous Windows versions.

To fix this problem, you need to login back to your Windows OS and shutdown it properly. To do that, please follow these steps.

1. open a command prompt with administration privileges. (To open command prompt with admin privileges, right click command prompt in the start menu and choose "Run as administrator" option).
2.  Run the following command:

 shutdown /s 

1. Now login back to Ubuntu to see that you can mount your drives back :)

That's it guys. I hope this wll help you. Please share this with your friends in G+, Facebook and Twitter if you think this will be helpful to them as well! Also leave a comment to give any feedback.