[09:05] <baskak> hi, i'd like to file a bug about oneiric hanging after the computer is left running overnight. no idea what package and if there's any similar bug - don't really know what keywords use to search to make it sensible
[09:12] <drussell> baskak: hmm do you have another machine you can use?
[09:12] <drussell> baskak: if so, ssh into the crashing one, and tail a few of the logs
[09:12] <drussell> baskak: that way when it crashes you'll have something that might give you an idea as to what's happening
[09:47] <baskak> drussell: thanks, i have another, but it's win xp. can you direct me to some guide how to do it? and, is it meant to monitor the state of the crashing machine all the time?
[09:48] <drussell> baskak: you can use "putty" which is a ssh terminal for windows
[09:48] <drussell> baskak: and then run something like "tail -f /var/log/syslog"
[09:49] <baskak> drussell: thanks. i will check it.
[09:50] <drussell> baskak: you probably want to monitor /var/log/dmesg and /var/log/Xorg.0.log
[09:50] <baskak> drussell: will it give more than it is logged there now after "elephants" reset?
[09:51] <drussell> baskak: no, but it'll allow you to see whats happening at the moment that it crashes/locks up
[09:52] <drussell> baskak: but if you're logged in you may find that it's only the display that's frozen, not the whole machine for example
[09:52] <baskak> drussell: by "see" you mean observing it live? i can't really do it. it's a question of many hours
[09:53] <drussell> baskak: you'll also be able to look at the putty terminal in the morning after the machine has crashed
[09:54] <baskak> drussell: i suspect it might be display only. i will try it.
[09:54] <drussell> baskak: best of luck
[09:55] <drussell> baskak: if it's just the display, take a look at  /var/log/Xorg.0.log
[09:55] <drussell> baskak: or rather Xorg.0.log.old for the previous session (probably the one that crashed)
[11:14] <baskak> drussell: i had to reboot the computer, so i lost the log. however, it might be that the reason i hhad to reboot, general slowing down and choppy display, is related. does the current log tell you something? the previous one seemed to end similarly, at the line similar to 1072. http://paste.ubuntu.com/689904/
[11:21] <drussell> baskak: hmm, not really, or at least not to me... how about the other logs? syslog (or possibly syslog.1)
[11:22] <drussell> baskak: and dmesg (or dmesg.0)
[15:04] <bdmurray> mvo: could you look at bug 839584 with me?
[15:04] <ubot4> Launchpad bug 839584 in ubuntu-meta (Ubuntu) "package ubuntu-desktop 1.242 failed to install/upgrade: ErrorMessage: dependency problems with unity-2d (affects: 4) (dups: 1) (heat: 14)" [High,Confirmed] https://launchpad.net/bugs/839584
[15:06] <mvo> bdmurray: that one looks like a ordering bug :/ I hope I will be able to reproduce, there is some code in apt-experimental that should fix those once and for all
[15:07] <bdmurray> mvo: okay how can you tell it is an ordering bug?  I also found bug 850049
[15:07] <ubot4> Launchpad bug 850049 in ubuntu-meta (Ubuntu) "package ubuntu-desktop 1.242 failed to install/upgrade: ErrorMessage: dependency problems libatk-adaptor (affects: 5) (dups: 4) (heat: 38)" [High,Confirmed] https://launchpad.net/bugs/850049
[15:08] <mvo> bdmurray: if dpkg complains and there is no other issue (that seems to be the case) then I don't see what else it could be, we can ask for the /var/log/dpkg.log file to be certain
[15:13] <bdmurray> Okay, thanks
[15:18] <baskak> drussell: http://paste.ubuntu.com/690065/ syslog.1 that ends on 8:15 am today, therefore after the previous Xord.0.log (ca. 1:30 am) but before i approached the computer in the morning. ps. sorry for gaps in correspondence.
[15:22] <drussell> baskak: ahh that's bad....
[15:23] <drussell> baskak: the out of memory killer is firing, and killing stuff off to try and save the system
[15:25] <drussell> baskak: the most I can suggest for now is raising a bug explaining what's going on, and attaching that log file
[15:41] <baskak> drussell: actually it's *not* oneiric-specific
[15:43] <baskak> drussell: but it's ubuntu-specific since some time ago. there's not much memory, 1gb, but it should work on swap, shouldn't it
[15:46] <AlanBell> hi all
[15:46] <AlanBell> debian bug #626790
[15:46] <ubot4> Debian bug 626790 in openswan-modules-dkms "openswan-modules-dkms: Kernel modules doesn't compile" [Grave,Open] http://bugs.debian.org/626790
[15:46] <bdmurray> cyphermox: I'ved updated bug 799937
[15:46] <ubot4> Launchpad bug 799937 in network-manager (Ubuntu) "unable to connect to a WPA PSK network (affects: 2) (heat: 10)" [High,Incomplete] https://launchpad.net/bugs/799937
[15:46] <AlanBell> that affects Ubuntu natty and Oneiric, openswan-modules-dkms just doesn't work
[15:47] <AlanBell> there is a patch on the debian bug, can we do something with it to make it work or do we have to wait for someone to do something in debian first?
[15:57] <baskak> drussell: what package should be pointed out? kernel?
[16:00] <cyphermox> bdmurray: oh, very interesting, thanks
[16:01] <cyphermox> this I have a setup I can test with
[16:01] <bdmurray> cyphermox: okay cool
[16:07] <baskak> drussell: i filed as kernel=related. and btw.: what should i do if bugs i submitted get no follow-up at all?
[17:44] <ksknightmare> can someone look at bug 850923
[17:44] <ubot4> Launchpad bug 850923 in xserver-xorg-input-synaptics (Ubuntu) "Two-finger scrolling is off by default (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/850923
[17:44] <ksknightmare> i feel like this shouldnt be an actual bug, its just loading the default action