X11 connection rejected because of wrong authentication.
kate: cannot connect to X server localhost:10.0


I know I’m not the only Kubuntu user, and there is proof I am not the only user encountering this error. I’ve been getting around it by using gksu which has no problems with my authentication. I suppose I could just alias kdesu and kdesudo (i tried it with no luck too!) to gksu, but I’d like to see an update fix this in the upcoming months. The nice fade effect of gksu is a welcome change sometimes.

Here’s the good news about it for me. If I use the keyboard to switch to a tty login, the monitor wakes back up. I can then use the keyboard to switch back to my KDM.

I have not tested it with suspend to disk yet. Let me know if this works on your laptop (comment on the bug report).

I don’t think it’s a problem. However, you kind of have to wonder how it affects the users who install using Ubuntu 8.04 and then add the kubuntu-desktop package, or will it be disabled?

Others have noted that there’s been a lack of reports from users with their experience regarding Hardy Heron. I noticed the torrent activity was kind of slacking. This is an excellent time for us to step up the testing on this. I suggest testing the .ISO image from a LiveCD and from some sort of virtualization application, such as VMWare or VirtualBox. If you’ve got the resources, it’s definitely appreciated for a full install and all the reports that you get from that experience.

I’ve encountered a few bugs that I’ve reported at Launchpad. Here I found other users reporting the same kind of problems I experienced. I wasn’t able to find the bug reports doing a simple search, instead it found them for me when I attempted to report the bugs, so go ahead and just attempt to report the bug you encounter. If it doesn’t find it for you, someone will catch it in triage. So, to re-iterate. If you haven’t tried it yet, go ahead and take the time. This is one of the easiest ways to contribute to the community.

Now… first things first. I setup the notebook using Vista and made sure that everything worked. Fortunately, everything worked… and worked perfectly.

Next, I moved into using GParted/CloneZilla from their LiveCD so that I can resize the NTFS partition. At first when I opened it, I noticed that it had a couple of partitions, including a recovery partition, the OS partition, and two others that I was uncertain of their purpose. It’s my first Dell, so I left those alone for now.

I resized the largest partition, the one used by Windows, so that I would have enough free room to support Ubuntu and all my desired files. I rebooted and attempted to let Vista load. Windows Vista noticed something had changed and spent the next 25 minutes checking integrity. It then allowed me to proceed to log in and everything again worked as expected.

I rebooted to use the GParted LiveCD again, this time with the intention of creating my desired partitions and this is where the problem began. I was unable to create any additional partitions because Dell had created all 4 partitions as Primary partitions, and that’s the limit. I opted to delete the last partition on the drive for convenience. The unallocated space was before this partition, so it just made the most since and required the least amount of data to be moved. I later found out this partition held the wonderful MediaDirect 3.0 software, that must be reinstalled prior to any OS.

I put the Hardy Heron Alpha1 disk in the tray, rebooted, and allowed it to install. I could not let it use a guided setup because I wanted /home on a separate partition. I also chose to put /etc on it’s own separate partition, and the Install program let me do it.

After rebooting, on the Ubuntu loading screen with the sliding orange progress bar, my caps lock and scroll lock lights begin to blink/flash. I rebooted and chose the Recovery mode from GRUB. This time, I see where it stops and it shows this error:

init: error parsing configuartions no such file or directory.

After searching the internet for reports of bugs with the flashing lights, I found a bunch of irrelevant stuff. Searching for the specific error message, I found the problem in a this bug report on Launchpad.

I re-installed and put /etc on the same partition as / and it now boots properly into Hardy Heron.

It seems that /etc can’t be on it’s own partition. Who knew? Not me. Not the install program. To me, it’s a bug that it wasn’t able to tell me : DO NOT install /etc on a separate partition.

Now that it boots, my next step is to get the wireless and audio working.