Which file extension are you?
Another day, another meme. This one just happens to fit me like a glove:
Another day, another meme. This one just happens to fit me like a glove:
I installed Ubuntu’s latest alpha release, the Feisty Fawn Herd 3, this morning on my development machine. Herd 2 had a bug that wouldn’t install, but Herd 3 installed like a champ.
I’m not going to put up any screenshots – since the release on Thursday, there are plenty of sites that have screenshots up.
Some random thoughts and first impressions:
I installed Compiz from the Ubuntu repositories instead of Beryl, which I’m running on my Edgy Eft / main desktop. I wanted to give Compiz a try and see how it’s different. The best way I can explain it, after only using it for an hour or two now, and not knowing the in’s and out’s of Compiz, is that it seems more vanilla than Beryl. With Beryl being actively developed by the community (not that Compiz isn’t) Beryl seems to have much more eye candy and bells and whistles. I don’t have the stability problem or resources issues others have complained about on Edgy, and Compiz seems to do fine on my Feisty box using the Nvidia binary drivers in the Ubuntu repository. However, installing Compiz out of the box, including the packages compiz, compiz-gnome, and desktop-effects, along with the required dependencies, I had no window borders. The first thread on the Feisty Fawn forums on Ubuntuforums.org didn’t fix it, nor did a post 3 pages in. One post did link to the Compiz forums, and doing the following got it to work:
sudo nvidia-xconfig --composite<br /> sudo nvidia-xconfig --render-accel<br /> sudo nvidia-xconfig --allow-glx-with-composite<br /> sudo nvidia-xconfig --add-argb-glx-visuals
Banshee’s latest release, 0.11.5, is included and feels quite snappy.
Since I built my new computer a few months back, and installed Ubuntu 6.10 Edgy Eft, I have only been able to burn using sudo. My old machine burned fine without sudo, so I was guessing it was because I’m using a SATA DVD-RW drive.
I found this tip on the Ubuntu forums and it fixed my burning problem – Gnomebaker has no problem working as a normal user after applying this fix.
Step 1:
As root (or in a terminal type: sudo gedit /etc/udev/rules.d/15-local.rules This will create a new file called 15-local.rules. Add a new rule in the file:
# SCSI devices<br />
BUS=="scsi", KERNEL=="sg[0-9]", NAME="%k", GROUP="cdrom"
Step 2:
Reboot.
Step 3:
In a terminal type the following (hit enter after each):
sudo chmod 4755 /usr/bin/cdrecord<br />
sudo chmod 4755 /usr/bin/cdrecord.mmap<br />
sudo chmod 4755 /usr/bin/X11/cdrecord.mmap<br />
sudo chmod 4755 /usr/bin/cdrdao<br />
sudo chmod 4755 /usr/bin/X11/cdrdao
That should fix it, especially if you’re running Gnomebaker. If you’re running K3B, run K3Bsetup and hit the above link for more if you’re a KDE user.
Thanks to wilko on the Ubuntu Forums for posting this fix.