every now and again window decorations disappear in ubuntu 12.04. this happened in 11.04 and 11.10 as well. here is the fix for that.
# press alt + f2 to open the run command dialog
and viola, your window decorations have returned!
# install open ssh server
sudo apt-get install openssh-server
# backup the default ssh config to the home directory
sudo cp /etc/ssh/sshd_config ~
# edit the config file using vi (gedit works as well if your in a gui)
sudo vi /etc/ssh/sshd_config
# change the following lines – you dont want root to be able log in, change the default port from 22 and allow users – so change the ones listed below
AllowUsers user1 user2
# restart the ssh server to commit the changes
sudo restart ssh
dont forget to setup the port forwarding on the router for external access!
i am really looking forward to the new expansion for world of warcraft called mists of pandaria. all new talents and skill trees (you can check out the new talent calculator here) and the new monk class looks awesome. one of the other things i am really looking forward to is the pet battle system, now your vanity pets are for more than just looks and for showing off!
here is the trailer for the new expansion (yeah, its been out for awhile, i just have not been posting about wow much lately)
when installing the dotnet packages in wine, i got this error -
user@darkstar:~/.wine$ ./winetricks dotnet11
Executing w_do_call dotnet11
Executing w_do_call fontfix
Please uninstall the Samyak/Oriya font, e.g. 'sudo dpkg -r ttf-oriya-fonts', then log out and log in again. That font causes strange crashes in .net programs.
to remove the font package
# its a part of the
ttf-indic-fonts package, so we need to remove it
# there are other references to them – using a handy
sed command you can find them and then edit the file to remove.
# i ran the following commands in the
grep -nr samy . | sed 's@\(Samyak\)@@'
grep -nr oriy . | sed 's@\(Oriya\)@@'
after the oriya and samyak fonts and all mentions of them are removed, log out and log back in and you should be all set to move forward with the dotnet11 install
here is a fast and dirty how to for recompiling your kernel in slackware -
download the kernel source
cd over to the directory we are building the kernel in
move the tarball over to the directory we are building the kernel in
mv /home/michael/linux-3.3.1.tar.bz2 .
unpack the tarball
tar -xvjf linux-3.3.1.tar.bz2
remove the sym link to the old kernel
create a new sym link to the new kernel
ln -s linux-3.3.1/ linux
move into the new folder
copy the old config over to use for the recompile
cp /boot/config .config
there are a few different options to use here – make menuconfig which is a ncurses based tool to configure the kernel. for this how to i used make xconfig which is a X based tool. there is also make config which is just awful and i would not recommend using it unless you have a lot of time.
compile the kernel – i used the -j3 because i have a dual core. use -jN where N is the number of cores you have +1
compile the modules
make -j3 modules
install the modules
make -j3 modules_install
remove the sym link for the old System.map, config and kernel
now copy the new System.map, config and kernel over to /boot
cp arch/i386/boot/bzImage /boot/vmlinuz-3.3.1
cp System.map /boot/System.map-3.3.1
cp .config /boot/config-3.3.1
create the sym links for the new kernel
ln -s /boot/vmlinuz-3.3.1 vmlinuz
ln -s /boot/System.map System.map
ln -s /boot/config-3.3.1 config
now to modify your
lilo.conf to show the new kernel on boot
here is what my section of lilo looks like – make sure you change the
/dev/ points to your partitions
# Windows bootable partition config begins
other = /dev/sda1
label = windows
table = /dev/sda
# Windows bootable partition config ends
# 126.96.36.199 start
image = /boot/vmlinuz-huge-smp-188.8.131.52-smp
root = /dev/sda6
label = 184.108.40.206
# 220.127.116.11 end
# 3.3.31 start
image = /boot/vmlinuz-3.3.1
root = /dev/sda6
label = 3.3.31
# 3.3.31 end
then run lilo to update the config
after the kernel has been added reboot
and when you load into the new kernel, assuming you dont get a kernel panic error, run
uname -a and you will see the new kernel. for example, mine looks like this -
Linux quotidian 3.3.1-map-3-4-12 #1 SMP Tue Apr 3 13:15:09 EDT 2012 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ AuthenticAMD GNU/Linux