[08:27] hi my installation was perfect ,using 13.04 a few days but now getting window pop up asking for password to unlock login keyring... [08:28] this is for 13.10 Guest93384 [08:28] try #ubuntu [08:32] like type that in terminal? [08:32] thank you [08:33] Guest93384, /j #ubuntu in your IRC client [08:53] keyboard layout switching and ctrl->caps remapping seems to be broken. Basically, it seems xkbmap options aren't being applied anymore [08:54] anyone knows if a bug has been filed already, or if there is a workaround? I can't find a bug, and I don't know which package to file it under [08:55] it's as if something is resetting the settings, because even when I use setxkbmap with the right -option setting, the settings seem to be reset after a few seconds [10:33] Howdy folks === steveire_ is now known as steveire === SwedMike is now known as SwedeMike === ghostcube_ is now known as ghostcube [13:53] anyone knows of a workaround for https://bugs.launchpad.net/ubuntu/+bug/1215826 ? [13:53] Launchpad bug 1215826 in Ubuntu "Lost ability to remap Caps Lock to Ctrl" [Undecided,Confirmed] [13:54] this is making me crazy === PeTaHuRtZ is now known as GiGaHuRtZ === om26er is now known as om26er|afk === om26er|afk is now known as om26er [21:10] hmm [21:10] [root@enterprise ironhalik]# service ssh restart [21:10] stop: Unknown job: ssh [23:36] on the latest update to 13.10 I see "W: Possible missing firmware /lib/firmware/radeon/KAVERI_pfp.bin for module radeon" It will my 1st restart to the 3.11.0-3 kernel. Is this expected behaviour, or should I stick with 3.10.0-6 ? [23:42] phillw: what version of linux-firmware do you have? https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1183777/comments/6 suggests filing a new bug if that particular firmware is still missing after 1.113 [23:42] Launchpad bug 1183777 in linux-firmware (Ubuntu) "Possible missing firmware /lib/firmware/radeon in mainline 3.10 - 999 ubuntu kernel" [Medium,Fix released] [23:45] trism: I'm just doing a fresh update / dist-upgrade to see if things have settled down in the last 24 hours. (Always a risk of a partial upgrade if I caught up the update at the wrong time). [23:47] If it is still a reported issue, I'll re-open the bug. [23:47] *file a new bug