If you missed the news yesterday, Ubuntu 10.10 Alpha 3 was released. As of this stage, there are a significant amount of new features in 10.10 compared to 10.04. For an overview, you should look at the list that OMG! Ubuntu! has compiled.
If you’ve been anxiously waiting to test Ubuntu 10.10, but need a stable system then this is not the time to upgrade.
If you’re not worried about a problem here or there on occasion and what to give 10.10 a spin, I would suggest you download the Alpha 3 torrent to install rather than doing a system upgrade from 10.04 to 10.10 (at least until the final is released).
If you’re still longing to upgrade your Ubuntu 10.04 directly, you can do so by the following:
Press Alt+F2 to launch the Run Application dialog.
Type update-manager -d and press enter.
When the Update Manager appears, it should alert you of an upgrade to 10.10. Do so at your own risk!
Also, as always, if you’re already running Ubuntu 10.10 whether its Alpha 1 or Alpha 2, applying all updates via Update Manager will give you all of the changes that are to be found in Alpha 3. Continuing this until the final is released will update you to a final version. There’s always confusion from some about this, but updating does indeed keep your system using the latest and greatest!
As of Alpha 3, we’ve still seen no signs of the Windicators that Mark has promised, but the indicator-applets for the GNOME panels are coming along very nicely and adding a great deal of ease and consistency.
Another discovery of mine has led to the exposure an unmentioned feature in Gwibber that will help you follow your friends’ conversation more closely (or so I assume).
If you’re the ultimate stalker, like my girlfriend, then you’ll most likely find this feature to be very useful. Others may only use it on rare occasions.
New in Gwibber is the ability to expand conversations you’ve directed towards Twitter. With an expand button (currently the somewhat large green plus icon), you’re able to view a conversation you’ve posted to Twitter and (assumingly) the follow up posts from your friends.
At the moment Gwibber only seems to expand your own personal tweets, but it appears to be a feature that will (as a speculated example) help you find out exactly why your friend Kathy agrees with your tweet on the recently hot weather in Raleigh.
Understand that my speculations are just that, speculations, and nothing more. This feature could easily evolve into anything more than I’ve imagined. In the meantime, share your ideas, thoughts and opinions! I’m always excited to hear new speculation and ideas!
With so many people talking about the new Ubuntu Font that’s soon to be released to the public for beta testing, I thought I would take the opportunity to post a quick and easy guide to testing these fonts before everyone else does!
If you’d like to test these fonts, then you need to follow these instructions exactly (since the ppa is “private”). I found other site instructions a bit confusing, so if you follow my directions you should have these installed effortlessly and pain free in no time.
Now open a new tab and navigate to the following link. Once there, you should see the PPA listed as “ppa (ppa:ubuntu-font-beta-testing/ppa)” in your list and it may be the only one. There should be a link labeled “View” to the far right of it, click it. http://launchpad.net/people/+me/+archivesubscriptions
The link that you just opened when clicking view should list software sources for this PPA that are unique to you. Open your software sources list file and copy these two source lines to the bottom, save and close (using the following command to open the sources). sudo gedit /etc/apt/sources.list
Add the PPA key so the package is authenticated properly when you install: sudo apt-key adv –keyserver keyserver.ubuntu.com –recv-keys 42F834EC
Update your software sources. Your new access to the private PPA may take between 5-15 minutes before its processed, so if you see errors for this software source in the terminal, be patient and try updating again in a few minutes.: sudo apt-get update
Install the font: sudo apt-get install ubuntu-private-fonts
Now that the fonts are install, apply them by right clicking on your Desktop -> Change Desktop Background -> Fonts (tab):
You should now have the new font installed. Good luck and enjoy!
The indicator menus have seen some more slight improvements in the latest updates and they’re beginning to take shape nicely!
Messaging Menu Highlights
The new updates to the Messaging Menu have brought highlighted message counts so that new messages can be easily recognized. The updates aren’t final and have caused a slight misalignment (as you can see on the left margin of the menu), but they do look promising!
I was unaware that this change was in the pipeline, but I must say that I fully approve.
I suspect that the next step will be to configure a color change for the bubbles and text for when the menu entry is hovered, as the bubble and text are hardly legible in this instance.
Sound Menu Playlists
You’ve probably seen, in my previous posts regarding the sound menu, that Playlist integration has been planned from the beginning. Only recently have the signs of inclusion seen the light of day.
The new Playlist sub-menu looks to be very promising and a real time saver if you’re the type of person to create mood-lists. 😛
That being said, it looks to be a while longer before your listed Playlists are of any use. The current listed Playlists as seen in the image above are apparently faux placeholders until the real code to embed them in menus is written and committed.
Sound Menu Play Buttons
In the latest updates, I also notice that the selected hot spots for the play buttons (previous, play/pause, next) have changed. Looking through the code last week I found the code behind the buttons and they are temporarily rectangular hot spots rather than shaped to form the visible buttons.
Seeing this, I spent a short bit of time writing a fix and submitted a potential patch for this to LaunchPad. In the latest updates, they’ve not yet included my patch or written their own fix, but the rectangular hot spots have been fine tuned a bit.
If you’re waiting for features to be completed or have found a nagging bug, I encourage you to download the source code, fix it and submit a patch! After all, this is what Open Source is all about! 😉
I just saw this change marked in my updates recently for Rhythmbox in Ubuntu 10.10 and thought I would share whats new so far!
The new “Get a link for the current song to the Ubuntu One Music Store” button is now present and functional in Rhythmbox for Ubuntu 10.10.
When you click on the “Get a link” button, you are prompted with a dialog that scans the online music store for a match and displays the result for you. The address to the song or album is automatically copied into the clipboard and is ready to paste!
This feature can be used to send a link of a favorite song to your friends, where they can purchase the track right away if they choose to. If you want to go even one step further, you can even tweet the link to your friends and followers!
As you can see, this new Tweet feature is built upon the tightly integrated Gwibber application. Though I haven’t tried this yet, it should be possible to post to other services such as Facebook if you have them enabled in Gwibber.
It appears that the whole “Social from the start” idea that was first started with Ubuntu 10.04 is now moving to another level and becoming commonly integrated with deeper parts of the operating system.
Above is an example of Twitter integration in the Ubuntu Software Center that allows you to easily suggest software to your friends.
If you’ve ever noticed your user agent string before, then you may have noticed that Opera identifies as running on a generic Linux platform. This can be a bit bothersome or annoying if you’re a Linux enthusiast like me.
Opera for Windows and Mac both properly identify the platform they are installed on, but Linux is a little more challenging due to the overwhelming number of distributions. You can easily adjust your user agent string to accurately reflect your platform and help promote both Opera and your Linux distribution when you browse and post online.
To change this so that it reflects your specific platform, simply:
Open “opera:config#ISP|Id” in a new tab.
Enter your distribution in the blank box in the format “Distribution/Version”.
Click the Save button and restart your browser.
This should successfully change your user agent from something generic like..
Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.6.30 Version/10.70
..to something a little more specific like..
Opera/9.80 (X11; Linux x86_64; U; Ubuntu/10.10; en) Presto/2.6.30 Version/10.70
Hope that helps! You can test your updated user agent strings in the comments below since they will appear above your comment. Or you can test it out at UserAgentString.com.
I just noticed this change in the sound menu and I’ve very pleased so far with the progress!
The menu is beginning to take shape nicely, but don’t get too excite just yet. While the back, forward and pause/play buttons do indeed work, they don’t currently have any mouse animations. By this I mean that there is no visual change when you click them as you would see in a regular button. The pause button also doesn’t toggle back to the play button.
After the song progress bar and time are inserted, there won’t be much more to look forward to usability-wise other than the playlist sub-menu’s. I’m sure there will be several tweaks and adjustments coming along after these features work their way in, but they seem to be piecing things together in a very orderly fashion!
I’ve been in talks with the GSPCA maintainer for a week now discussing possible issues that the Microsoft LifeCam VX-1000 was having in Linux. In case you don’t know (which I didn’t at first either), GSPCA stands for “Generic Software Package for Camera Adapters.”
This software package contains drivers to a wealth of webcams and other video input devices, the Microsoft LifeCam VX-1000 included. The problem I had was that the built in microphone would stop working as soon as you turned on the camera. If you never used the camera and only opened a sound recording application then the microphone would work perfectly. In the long mailing list discussions that let me to this post, we discovered that the bug was is in setting a GPIO register that instantly breaks communication with the microphone. I’ve worked up a patch that I would like to get tested by others. Basically, the patch just includes conditionals that tell the driver not to apply this GPIO register change if the camera is using the OV7660 sensor. What I would like to test is, does disabling for this sensor affect other OV7660 devices? If not, then this patch will likely go into the main Linux kernel. If you’re using the Microsoft LifeCam VX-1000 or VX-3000 and are having trouble with your microphone, could you please do the following?
Extract the zip file on your Desktop (so you have the folder “gspca-2.9.51-vx1000-patch-20100712”).
Open a terminal window and enter the following commands: cd Desktop/gspca-2.9.51-vx1000-patch-20100712/ make sudo make install
Reboot your computer and test your webcam in an application such as Cheese (which can easily be found in the Ubuntu Software Center).
Make sure that when you start your webcam in Cheese that the microphone continues to work. You can verify this in the Sound Preferences window if you click on the Input tab (make sure you have selected “LifeCam VX-1000” as your input device). Let me know in the comments below or in the Ubuntu thread regarding this issue how it works for you! In case anyone is interested, here is the “diff -uNr” for the original sonixj.c against my modified version:
UPDATE 2010-07-13: As of today this patch is included in GSPCA v2.9.52+! It looks like my hard work paid off after all and now all Linux users, not just Ubuntu users, will be able to enjoy the fruit of my labor since GSPCA is merged into the official Linux Kernel. 😉
If you’re using Ubuntu 10.04 or newer and have installed the proprietary Nvidia or ATI video drivers then you likely know what I’m talking about.
The nice Ubuntu boot screen that you saw during the installation is now a low quality image and the resolution is wrong. Fortunately for you and I, there is a fix for this written by Marius Nestor at Softpedia.
I’ve taken the liberty to implement his steps in a single script that makes the work on your end a much easier task. Only use this script if you have not already attempted to follow Marius Nestor’s tutorial.