After a night out I was about to go to bed when I saw the news that ATI has released a new version of ATI Catalyst™ 9.8 Proprietary Linux x86 Display Driver, its proprietary display drivers for Linux. I immediately downloaded the drivers to test with my Fedora 11 as I am getting more and more desperate to watch HD Movies 😐 Installed them on a manually compiled kernel 2.6.27 and the build failed Installed the latest kernel version (for fedora 11) 22.214.171.124.xxx and build failed yet another time. Switched back to 2.6.27 and tried to build again. This time build was successful. Everything worked as expected. I was getting 1500FPS with glxgears and 300FPS with fgl_glxgears. But after sometime display hanged inturn freezing the system. Hard reboot was the only solution and then this happened for a few times in a row. Now, I am back to radeonhd, waiting for yet another release of ATI drivers so that I can try them yet another time to see yet another failure
Well, I was getting bored and just googled my domain name. As I was browsing through the search results, I clicked on a Spanish site containing the word gofedora. I clicked on google’s “Translate this page” and was surprised by the result. Watch it yourself below.
Yesterday, AMD released ATI Catalyst™ 9.7 Proprietary Linux x86/x86_64 Display Drivers. I happened to checkout the website today. Initially I was very excited about it hoping that these drivers will work with 2.6.29+ and I’ll be able to use my ATI Radeon HD 3200 which is lying dead since a fortnight or so. I downloaded the drivers immediately and switched to Fedora 11 default kernel. Installed the drivers and checked the install log located at /usr/share/ati/fglrx-install.log. And I saw a failure. AMD disappointed me, yet another time
In case you happen to screw your graphics display while trying to install ATI drivers, use the following command to uninstall fglrx.
There is a vulnerability in the way Google authentication service works. Whenever you login to any of the Google’s online services like GMail, Orkut, Groups, Docs, Youtube, Calendar etc., you are redirected to an authentication server which authenticates against the entered username and password and redirect back to the required service (GMail, Youtube etc.) setting the session variables.
Now, if you are able to grab the url used to set the session variables, you can login as the user to whom that url belongs from any machine on the Internet (need not be the machine belonging to the same subnet) without entering the username and password of the user.
The proxy servers in the organizations can be used to exploit this vulnerability. Squid is the most popular proxy server used. In the default configuration, squid strips the query terms of a url before logging. So, this vulnerability can’t be exploited. But if you turn off the stripping mechanism by adding the line shown below, then squid will log the complete url.
So, after turning stripping mechanism off, the log will contain urls which will look like this
Replace .co.in with your tld specific to your country. If you paste this url in any browser, it’ll directly log you in and you can do whatever you want to that account. Remember that all such urls remains valid only for two minutes. So, if you use that url after two minutes, it’ll lead nowhere.
At the time of writing this post Orkut, Google Docs, Google Calendar, Google Books and Youtube are vulnerable.
So, make sure your squid has stripping mechanism turned on and your squid server is properly firewalled.
I use knetstats for monitoring my wireless traffic. One fine day my wireless connection was not working as expected. I reloaded the module and reactivated the wifi device. Just to check if there were some traffic, I opened knetstats and guess what happened. I was blown the by the huge traffic on my wifi interface. The upload speed was something around 5.33 ExaBytes/sec ( or 5864061874995MB/sec) for sometime. I almost survived a heart attack. I wonder when we will have Internet connection with that speed. Here is the proof
We (the yum people) are organising Yum Bug Day on May 30, 2008. We try to kill as much bugs as possible. For a list of bugs, check Yum Bugs and Yum-Utils Bugs. If you think you can fix, provide info about one or more or you have any suggestions, just drop in #yum on freenode.net or shoot a mail at yum-devel.
In Seth’s words,
Yum Bug Day!
It’s exciting! It’s Fun! You get to tell people things like: Already
fixed, WONTFIX, CANTFIX, NOTABUG, and ‘ooo yah, that’s pretty broken’.
KDE4 was released on Jan 11, 2008. I noticed the rpms for Fedora on rpmfind.net on Jan 13. It was a big trouble to get packages one by one keeping in mind the dependencies. I tried Yum with rpmfind repo but it didn’t work out. Then I used the server where my domain is hosted. I have 15GB bandwidth per month and the download speed on the server is awesome (average 400kbps). So, I just ftp to rpmfind.net and downloaded all the rpms on the server hosting my site. And then I downloaded the packages from my domain to my local machine ( No effort for searching now and I can do parallel downloading now). So, lets see how to install KDE4 on Fedora.
Enable the fedora development repository. In '/etc/yum.repos.d/fedora-development.repo' file check if enabled is equal to 1 for development repo. If its zero, then change it to 1.
Use yum to install the kde rpms that you have downloaded.
[root@bordeaux KDE4_RPMS]# yum install *.rpm [Enter] (do as root)
Note: After the KDE4 rpms are up in the fedora repos, then you can skip the step 1 and directly install kde by issuing the command
[root@bordeaux saini]# yum install kde* [Enter] (do as root)
I was expecting a lot from KDE4. But a lot of things went wrong. When I logged into KDE4 for the first time, everything was looking awesome and very sharp. But then I faced the first crash while editing the settings for a widget and I realized that its not possible to have a crash free KDE application. After upgrade ( which cost me around 1GB of downloading via yum) and spending a lot of time manually downloading the packages, all I got was a desktop environment which will crash frequently to remind that you just wasted 1GB of bandwidth.
After upgrading, Kopete stopped working due to some conflict in ssl libraries, xchat is also not working due to some other library conflicts, dolphin the new file manager for KDE doesn’t even start and flush all kind of errors and faults when launched from command line. After the first crash the panel disappeared and I couldn’t get it back. Launching kicker returns the kde3 panel.
KDE4 is awesome when you just sit back and look at it. But when you want to work with some apps, its miserable. One of my friend had this status message on gtalk ‘ KDE4 : KDE3.5.8 :: Vista : XP ‘. KDE4 is as good as Vista when it comes to looks but its equally bad as Vista as compared to XP when it comes to work with it.
Conclusion: Don’t upgrade to KDE4 and wait till May, 2008 when KDE4 will be shipped with Fedora 9. I hope that KDE4 will not crash frequently when it’ll be embedded natively.
Here are some screen shots if you wanna have a look
After installing jdk-6u2 for Linux from Sun Microsystems’ site, when I ran javaws it gave strange error that libstdc++.so.5 not found and it aborted. I searched for libstdc++.so.5 and it was not there in /usr/lib/ as expected. That implied something is wrong. As I installed jdk-6u2 from rpms, it should have given dependency error for the particular library, bit it didn’t. After searching for sometime I found that libstdc++.so.5 is provided by compat-libstdc++-33 package, which was not installed on my system. After I installing the particular package, everything worked fine.
It worked fine for Fedora Core 6 because compat-libstdc++-33 is provided by default in Fedora Core 6.
But its kind of strange that if libstdc++.so.5 and hence compat-libstdc++-33 is required for jdk-6u2 then why ‘rpm -ivh’ didn’t give dependency error.