[16:54] <jbicha> hmm, I had hoped update-manager would be working again today, but I'm using the still rough 0.9 NetworkManager
[16:54] <jbicha> so changelog checking is broken
[16:56] <mvo> jbicha: if you remind me tomorrow I can add a workaround to u-m to ignore NM
[16:58] <jbicha> mvo: oh ok, I thought I'd have to wait until nm 0.9 made it into Oneiric
[16:59] <mvo> jbicha: I will probably have forgoten by tomorrow but with a gentle reminder tomorrow I can look into it
[19:28] <IdleOne> Don't you just love the feeling of anticipation you get when you run an update and it needs a reboot :-)
[19:28]  * IdleOne is all excited about not knowing if my system is going to become a brick or not
[19:28] <coz_> :)
[19:28] <IdleOne> I'll be back!
[19:32] <coz_> IdleOne,  no brick?
[19:32] <IdleOne> nope
[19:32] <IdleOne> :)
[19:32] <IdleOne> happy to report
[19:35] <nit-wit> kernel update?
[19:37] <IdleOne> no
[19:37] <coz_> driver video?
[19:37] <IdleOne> lots of libs and perl packages
[19:37] <coz_> oh!
[19:38] <coz_> and a reboot was necessary?
[19:38] <IdleOne> I didn't really look to see what was being updated. aptdeamon update-manager-core and others
[19:38] <nit-wit> video driver probably
[19:39] <nit-wit> you brave user not looking .;)
[19:40] <IdleOne> what is the log file to see what was updated?
[19:40] <nit-wit> there is one in home but i look in synaptic history
[19:41] <nit-wit> *in
[19:41] <coz_> somewhere ins var log I believe
[19:41] <coz_> IdleOne,  if you didnt update via synaptic I dont think it will be listed under history,, unless that has changed
[19:41] <nit-wit> there was a kernel update a couple of days ago thats my bet
[19:42] <coz_> yeah  kernel and video drivers  are the two most frequent reasons for reboot
[19:42] <IdleOne> nit-wit: nope
[19:42] <IdleOne> that wasn't it
[19:42] <nit-wit> doesn't matter it will show in that synaptic history afaik
[19:43] <IdleOne> it didn't. I used apt-get update && apt-get upgrade
[19:43] <coz_> IdleOne,  yeah it generally is not registered under synatpic history from apt-get in terminal but I am checking to be sure
[19:44] <coz_> IdleOne,  no just did update via terminal no history listed in synaptic,, been that way for years ;)
[19:49] <IdleOne> found it. /var/log/aptitude
[19:50] <IdleOne> I think
[19:52] <coz_> its somewhere in /var/log for sure
[19:53] <yofel> /var/log/apt/history.log usually
[19:54] <IdleOne> yeah mine are in /var/log/aptitude I aliased update='sudo aptitude update'
[19:55] <yofel> aptitude should still put stuff in history.log, but yeah, aptitudes log file is easier to read
[19:57] <nit-wit> sudo gedit /var/log/apt/term.log or to the log itself
[19:58] <yofel> that's even harder to get the last actions out from ^^
[19:58] <Ampelbein> nit-wit: gksu for graphical applications! ;-)
[19:59] <nit-wit> Amapelbein; I will make sure I watch every post close with the rentetive ego needs thanks.;)
[19:59] <IdleOne> gksudo
[19:59] <nit-wit> *retentive
[20:00] <coz_> logs are not graphical
[20:00] <IdleOne> gedit is
[20:00] <Ampelbein> gedit ist
[20:00] <IdleOne> :P
[20:00] <Ampelbein> nit-wit: it's just a good habit to follow. http://psychocats.net/ubuntu/graphicalsudo has a explanation.
[20:00] <IdleOne> so anyway here are 3 different logs http://paste.ubuntu.com/608584/
[20:01] <IdleOne> history.log appears to be incomplete
[20:01] <IdleOne> term.log is the most complete
[20:01] <nit-wit> Ampelbein, If I need to be preached at I would ask bro I'm more then familiar I'm not a noob
[20:01] <Ampelbein> IdleOne: you cut off history.log, thats why it looks incomplete
[20:02] <Ampelbein> IdleOne: (notice the $ sign at the end)
[20:02] <IdleOne> Ampelbein: hmm
[20:03] <IdleOne> you are correct Sir
[20:03] <IdleOne> my mistake
[20:03] <IdleOne> So what caused a reboot to be needed ?
[20:03] <Ampelbein> IdleOne: personally i use aptitude.log to check WHAT has been done and term.log/dpkg.log if there is an error
[20:08] <Ampelbein> IdleOne: dbus has a call to reboot-required
[20:08] <IdleOne> that splains it :)
[20:14] <jbicha> the dbus update required a reboot for me
[20:16] <Ampelbein> jbicha: yes, in it's postinst it calls /usr/share/update-notifier/notify-reboot-required
[20:17] <jbicha> oops, missed your reply
[20:18] <jbicha> I happened to install that update individually today while troubleshooting
[20:48] <arand> Is there any more videos from the sessions than those up on youtube?
[20:57] <elv> hi guys terrible problem. my keybord (laptop) is no more active. also the mouse does not responds anymore unless i plug it out and then in, but i cannot do the same for the keyboard. i remain on gdm screen...
[20:57] <elv> please help me
[20:57] <elv> maybe any bugged update today?
[20:58] <elv> completely frozen keyboard but it does work whit the live cd so not hardware problem
[20:59] <elv> i upgraded udev, dbus before....
[21:01] <elv> any ideas?
[21:01] <jbicha> elv: are you using Ubuntu 11.04 Natty?
[21:02] <elv> no oneiric
[21:02] <Ampelbein> elv: if you boot from a live-cd can you scan for any relevant output in /var/log/syslog?
[21:02] <Ampelbein> (on the installed system of course)
[21:03] <jbicha> elv: you can help test out Ubuntu's accessibility support with the on-screen keyboard ;-), j/k
[21:04] <elv> what i have to search there? errors?
[21:04] <elv> i don't have orca or similar
[21:04] <jbicha> actually, on second thought, if you're using GDM 3, it doesn't have accessibility in Ubuntu on the login screen
[21:04] <elv> but it strange couse also mouse it's frozen but after unplug and plug it works
[21:05] <jbicha> the old GDM, you just click the accessibility icon and you can enable it
[21:05] <Ampelbein> elv: any messages that look like they have something to do with input devices/usb (if you use a usb keyboard)
[21:05] <elv> no no i'm usign gnome 2.32
[21:05] <jbicha> oh, click the icon that looks like a human silhouette
[21:05] <elv> Ampelbein: it's a laptop not usb
[21:06] <elv> jbicha: i uninstalled accessibility long time ago
[21:07] <elv> i'll scan /var/log/syslog now
[21:07] <jbicha> haha, you never know when you might need it
[21:08] <elv> i tried downgrading udev but nothing changed
[21:09] <elv> what could cause this problem? never happened something similar
[21:09] <yofel> does it work in a tty at least?
[21:10] <elv> i managed to get a recovery tty once before
[21:10] <kurtul> is oneiric already out? where did you find it?
[21:10] <yofel> can't think of anything except udev either though
[21:10] <yofel> kurtul: lol, not before october ^^
[21:10] <yofel> hm, someone should put the schedule in the topic
[21:10] <kurtul> is alpha out?
[21:10] <elv> yofel: but have you upgraded udev today?
[21:11] <yofel> kurtul: nope, https://wiki.ubuntu.com/OneiricReleaseSchedule
[21:11] <elv> yofel: what may i do from a tty?
[21:11] <yofel> elv: yes, but didn't restart yet ^^
[21:12] <kurtul> thanks
[21:12] <yofel> guess I'll do that, brb
[21:13] <elv> yofel: syslog it's hardwork
[21:13] <elv> may i search for some keyword?
[21:14] <Ampelbein> rww: ocaml rebuilds are on now, perl transition is finished
[21:14] <rww> oy
[21:14] <rww> Is "nothing in desktop uses ocaml, I don't care" a valid reaction to that ;P
[21:15] <Ampelbein> ...no? ;-)
[21:15] <rww> ok ;P
[21:15] <yofel> hm, nothing broken ehre
[21:15] <yofel> *here
[21:15] <rww> heh, my tab key's not working >.>
[21:16] <rww> .
[21:16] <elv> gosh guys
[21:16] <elv> syslog make me screw
[21:16] <rww> Pici: get in here and fix the topic, irssi's giving me a headache :(
[21:17] <Pici> What what
[21:17] <Omega> /topic to make it print the topic. :)
[21:18] <elv> do you think that if i install oorca from live session will i manage to log in ?
[21:18] <Pici> rww: How do you want me to fix it?
[21:18] <rww> Pici: Ampelbein says the Perl rebuilds are done and ocaml is up next.
[21:18] <Ampelbein> Pici: s/Perl 5.12/OCaml 3.12.0/
[21:18] <rww> and my autocomplete is being screwy and I don't feel like typing the whole dang thing out
[21:20] <Ampelbein> although the ocaml transition should be much smoother, http://people.canonical.com/~ubuntu-archive/testing/oneiric_probs.html has a friendlier look.
[21:20] <Ampelbein> the only major problem with oneiric for some people will be pidgin being uninstallable and thus holding back a lot of packages.
[21:21] <elv> people i'm getting lost with this keyboard
[21:22] <rww> Pici: thanks
[21:22] <Pici> rww: np
[21:25] <elv> but if it's not udev related what could it be?
[21:37] <IdleOne> !info libunique-1.0-0