The people that have been around here for long may remember me. I was at some point in the past quite active here, if only because I wanted to give back some of what I got from this forum. The truth is, I only went to this forum looking for solutions to issues I had with KUbuntu, which happened usually after a version upgrade.
So far it has been mostly a smooth sailing. But the latest upgrade has left me with a bitter feeling. After all these years, we still get upgrades with issues, both know and unknown. This has to improve. Listen Canonical, we can wait a few weeks, even months. Your reputation is much more damaged by releasing non working software than by releasing less than the latest version of everything. We can wait. You're already way ahead of the pack in terms of updating, perhaps only Google with Chrome is releasing updates faster than you. But releasing buggy updates does not create the loyal following that you're looking for to create the momentum to reach your target of 200 million users.
Back to the topic: it has been a long time since I visited this forum, which is a good sign of the degree of stability and lack of issues with KUbuntu. But this afternoon, after upgrading to Natty, I had to log in again. Incidentally, I did not found the solutions I was looking for, so I thought I better post them here.
- Konsole crashes when resizing with NVidia driver: change the properties of the Konsole icon to use the --notransparency argument.
- Virtualbox-ose-dkms driver not installing: install the package, and you'll see the error and the end of apt-get install. Then issue the command: sudo dkms install -m virtualbox-ose-dkms -v 4.0.4
Shame on you, Canonical, for releasing an update that crashes one of the basic components (Konsole) of the distro when half of the users (NVidia) resize a window. Shame on you NVidia for not releasing a patch for this quickly.
Shame on you, Oracle and Canonical, for not fixing what is apparently a trivial bug in one of the most popular (VirtualBox) free virtualization packages around.
So yeah, grub is now blue and the color theme is great. But it's sad, and makes me think of switching to Fedora or -heaven forbids- Suse.
So far it has been mostly a smooth sailing. But the latest upgrade has left me with a bitter feeling. After all these years, we still get upgrades with issues, both know and unknown. This has to improve. Listen Canonical, we can wait a few weeks, even months. Your reputation is much more damaged by releasing non working software than by releasing less than the latest version of everything. We can wait. You're already way ahead of the pack in terms of updating, perhaps only Google with Chrome is releasing updates faster than you. But releasing buggy updates does not create the loyal following that you're looking for to create the momentum to reach your target of 200 million users.
Back to the topic: it has been a long time since I visited this forum, which is a good sign of the degree of stability and lack of issues with KUbuntu. But this afternoon, after upgrading to Natty, I had to log in again. Incidentally, I did not found the solutions I was looking for, so I thought I better post them here.
- Konsole crashes when resizing with NVidia driver: change the properties of the Konsole icon to use the --notransparency argument.
- Virtualbox-ose-dkms driver not installing: install the package, and you'll see the error and the end of apt-get install. Then issue the command: sudo dkms install -m virtualbox-ose-dkms -v 4.0.4
Shame on you, Canonical, for releasing an update that crashes one of the basic components (Konsole) of the distro when half of the users (NVidia) resize a window. Shame on you NVidia for not releasing a patch for this quickly.
Shame on you, Oracle and Canonical, for not fixing what is apparently a trivial bug in one of the most popular (VirtualBox) free virtualization packages around.
So yeah, grub is now blue and the color theme is great. But it's sad, and makes me think of switching to Fedora or -heaven forbids- Suse.
Comment