[00:27] <mrooney> so let's say I tried to log out for the first time, and it displayed some text and then brought me to a black screen, which didn't respond to ctrl alt delete or ctrl backspace. what logs should I check and what should I report?
[00:30] <sectech> When you logout are you trying to go back to the gdm login screen?
[00:30] <sectech> or just a console
[00:31] <mrooney> sectech: the gdm login, I just pressed the power button and then clicked logout
[00:32] <sectech> hmm..
[00:34] <sectech> try checking /var/log/Xorg.0.log
[00:34] <sectech> What kind of video card do you have/
[00:34] <sectech> ?
[00:44] <mrooney> sectech: sorry for my delay, an ati 350
[00:46] <sectech> mrooney,  On a fresh boot does your login screen come up okay?
[00:47] <mrooney> sectech: yeah, indeed, just fine
[00:49] <sectech> I'm sorry but I don't have a lot of time this evening,  but you might want to check to see if gdm is crashing... maybe try and run a backtrace on that to see if it comes up with anything... That's where I would start if I was having that problem
[00:50] <mrooney> okay thanks
[02:36] <greg-g> bdmurray: would it be wise to add links to BugSquad/KnowledgeBase under the Bug Tools section to the greasemonkey scripts (the karma, add tag, and responses which are in bzr and the latest one you posted to the list)?
[02:59] <mrooney> there are greasemonkey scripts for launchpad?
[02:59] <mrooney> for ubuntu?
[02:59] <greg-g> yep, brian just emailed out one he made to the bugsquad mailing list
[07:03] <savvas> hi, I can't explain this problem properly, i have compiz enabled, and sometimes when i click the upper right button to maximize a window, it doesn't resize the window properly and the window stays the same
[07:04] <savvas> is this problem known? here's a screenshot: http://img238.imageshack.us/my.php?image=noresizemaximizedwindowgh5.png
[08:49] <kijoko> helo
[08:49] <kijoko> i need some help
[08:55] <MightyTweek> kijoko: what kind of help?
[08:55] <kijoko> hardy installed on may laptop
[08:56] <MightyTweek> You probably want to go to #ubuntu
[08:56] <kijoko> but i can't resume ( wake ) from suspend/hibernate
[08:56] <kijoko> no respon from #ubuntu
[08:58] <MightyTweek> this really isn't the right channel, you want to be in #ubuntu, but try https://wiki.ubuntu.com/DebuggingKernelSuspend and http://ubuntuforums.org/showthread.php?p=3066404
[09:31] <savvas> do you think bug #227644 related to compiz or metacity?
[09:31] <savvas> *is related
[09:40] <Hewus> savvas: can you reproduce the issue with metacity?
[09:42] <savvas> hm..
[09:42] <savvas> it doesn't happen always i'm afraid
[09:42] <savvas> let me disable it and try again
[09:44] <savvas> Hewus: i don't think so, in compiz after the 5th or 6th retry I got it happening
[09:45] <savvas> 'ere we go.. most probably compiz related
[09:46] <Hewus> savvas: if it only occurs with compiz, then mark it as compiz :-)
[09:47] <savvas> well that was easy, thanks :P
[09:48] <Hewus> savvas: no worries :-)
[09:52] <lesshaste> hi
[09:52] <techno_freak> hi
[09:54] <lesshaste> I can't seem to work out how to read bug reports .. e.g. https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/165093 has two "Affects" lines marked as Invalid
[09:54] <lesshaste> what does this mean?
[09:54] <techno_freak> lesshaste, it might have affected two different packages
[09:55] <techno_freak> lesshaste, for example firefox is different from firefox-3.0
[09:56] <techno_freak> lesshaste, it looks like you can remove the 'Ubuntu' and 'linux-restricted..'
[09:59] <techno_freak> lesshaste, err.. i meant the two is not related to the bug and hence marked invalid
[10:00] <lesshaste> techno_freak: ok that's odd
[10:01] <techno_freak> lesshaste, the orig. reporter might have added all the 3 because he wasn't sure, 'Ubuntu' is the default option
[10:02] <lesshaste> techno_freak: ok.. I assume it's a driver problem so restricted-drivers looks correct
[10:04] <lesshaste> but what do I know :)
[10:04] <techno_freak> lesshaste, if you want to make it restricted-drivers bug then you have to reason out, afaics people have dealt with it as a Xorg bug
[10:05] <lesshaste> techno_freak: ok.. I'll leave it to the experts.. .it is a bit sad to have an X crash bug at this point. I am not sure I have had one in the 15 years I have been using linux for :)
[10:05] <techno_freak> lesshaste, :)
[10:05] <lesshaste> techno_freak: by the way.. what is this channel for? :)
[10:06] <techno_freak> lesshaste, for the bug squad, to deal with bug triage. its more like a discussion channel for triagers
[10:06] <lesshaste> the triagers allocate bugs to people/teams?
[10:07] <norsetto> lesshaste: no
[10:07] <lesshaste> my bug at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/224561 was supposedley allocated to the kernel team but I see no evidence of it on the bug (I tried to do it myself but didn't have permission)
[10:07] <lesshaste> norsetto: oh.. what do triagers do?
[10:07] <techno_freak> lesshaste, we help making the bug as informative as possible for the people to work on fixing it
[10:08] <lesshaste> techno_freak: cool
[10:08] <lesshaste> sounds like a really worthwhile job
[10:08] <techno_freak> :)
[10:09] <techno_freak> s/bug/bug report/
[10:09] <lesshaste> techno_freak: well is there any more info needed for my bug above for example? :)
[10:10] <techno_freak> lesshaste, https://wiki.ubuntu.com/Bugs/HowToTriage
[10:11] <lesshaste> techno_freak: so has 224561 actually been assigned to kernel? I seem to have problems reading the bug report metainformation
[10:13] <techno_freak> lesshaste, it is assigned to linux source package and handled by the ubuntu kernel team
[10:13] <lesshaste> ok.. sorry I will get used to how this works
[10:13] <lesshaste> I promise :)
[10:13] <lesshaste> Hardy is seriously buggy :)
[10:14] <techno_freak> eh
[10:15] <techno_freak> if there are no bugs, then there are really serious problems
[10:18] <lesshaste> techno_freak: :) there is quite a large margin between no bugs and too many bugs
[10:18] <lesshaste> I am sure it will all clear up slightly in the next month or so
[10:18] <techno_freak> lesshaste, i hardly encountered any bugs with hardy
[10:19] <lesshaste> techno_freak: ok.. on my system which is about 5 years old networking broke, X wouldn't start at all and the dvd drives spews errors on dmesg
[10:19] <lesshaste> :)
[10:19] <lesshaste> this was a simple upgrade from gutsy where everything worked perfectly
[10:20] <lesshaste> I could have waited a few months after hardy was released of course so I only have myself to blame :)
[10:25]  * ogra wonders why you have hda there at all
[10:26] <ogra> we dont have any ide naming in the distro by default anymore, update manager should have taken care for the transition to sdX
[10:27] <savvas> udev package?
[10:27] <savvas> lesshaste: apt-cache policy udev | grep Installed
[10:28] <ogra> lesshaste, do you have added anything to /etc/modules to forcefully load ide drivers ?
[10:29] <ogra> (or something else along these lines)
[10:29] <jeromeg> could an archive admin take care of bug #227225 ?
[10:29] <jeromeg> a package is not installable at the moment because of a partial backport
[10:33] <lesshaste> savvas: ?
[10:33] <lesshaste> ogra: was that for me?
[10:33] <ogra> lesshaste, thats why i prefixed it with your nick, yes :)
[10:34] <lesshaste> ogra: what was it in reply to ? :)
[10:34] <ogra> lesshaste, in reply to reading your bug report
[10:34] <lesshaste> ogra: the DVD drive problem?
[10:34] <lesshaste> ogra: I have more than one :)
[10:34] <ogra> i see ide in your dmseg, that shouldnt be there
[10:34] <ogra> libata is used in hardy that remaps drives to scsi devices
[10:35] <lesshaste> ogra: aha.. http://pastebin.com/f740c0c48 is  /etc//modules
[10:35] <ogra> thats why i asked if you have added any ide drivers to something like /etc/modules
[10:39] <lesshaste> sorry ogra .. hard freeze so had to reboot :)
[10:40] <lesshaste> did you see anything in my /etc/modules file?
[10:42] <ogra> only the lm sensors stuff
[10:42] <ogra> a default one looks the same otherwise
[10:42] <lesshaste> right
[10:43] <ogra> but the hda and ide in your dmesg defiately looks wrong
[10:43] <ogra> err, wait
[10:44] <lesshaste> ogra: I have the full dmesg from the 2.6.22 boot if that helps
[10:44] <lesshaste> where there are no errors
[10:44] <ogra> could be that i2c-piix4 pulls in the wrong stuff
[10:44] <lesshaste> (except for fglrx but that is a different story)
[10:45] <thekorn> hello bugsquad!
[10:45] <ogra> can you comment the lm-sensors part in there, run: sudo update-initramfs -u and try a reboot ?
[10:45] <ogra> (especialy i2c-piix4)
[10:46] <lesshaste> rebooting
[10:48] <savvas> need someone to test the following: 1) open a terminal and run this: /usr/lib/gvfs/gvfsd -r 2) open another terminal and do this: nautilus ftp://viper.sh3lls.net 3) if you get an error without a login prompt, post to http://bugzilla.gnome.org/show_bug.cgi?id=525283 with the output from gvfsd and the error
[10:48] <lesshaste> ogra: still get loads of [  103.668329] hda: status error: error=0x00 { }
[10:48] <lesshaste> [  103.668330] ide: failed opcode was: unknown
[10:49] <lesshaste> do you want to see dmesg?
[10:49] <ogra> did you cemmoent everything below line 11 in http://pastebin.com/f740c0c48 ?
[10:50] <lesshaste> http://pastebin.com/fcec1a27
[10:50] <ogra> hmm
[10:50] <ogra> hats not it then
[10:50] <ogra> *thats
[10:50] <lesshaste> http://pastebin.com/f24d63784  <-- dmesg
[10:50] <ogra> in any case you need to get rid of hda
[10:51] <lesshaste> hwo do I do that? :)
[10:52] <ogra> ask in #ubuntu-kernel i think
[10:52] <lesshaste> to be clear.. what should the dvd drive be if not hda?
[10:52] <ogra> if the drive was recognized by libata and then a ide module is loaded you may have driver clashes that result in such error
[10:52] <ogra> scdX or so
[10:53] <ogra> we have no hdX naming anymore in hardy
[10:53] <lesshaste> aha
[10:53] <lesshaste> I see
[10:53] <ogra> and the device name indicates ts using a wrong driver here
[10:53] <ogra> i migh be wrong but i think thats one of your probs, the kernel guys can confirm or decline
[10:55] <lesshaste> ok I asked in #ubuntu-kernel
[10:55] <lesshaste> although it doesn't look like anyone is in
[10:55] <lesshaste> thanks
[10:55] <lesshaste> although the X crashes are much more annoying :)
[10:56] <savvas> lesshaste can i see your udev version? apt-cache policy udev | grep Installed
[10:56] <lesshaste>  Installed: 117-8
[10:57] <savvas> hm
[10:58] <savvas> dir /dev/h*
[10:58] <savvas> lesshaste: dir /dev/h*
[10:58] <lesshaste> /dev/hda  /dev/hidraw0	/dev/hpet
[11:00] <savvas> might a rules.d problem?
[11:01] <ogra> probably
[11:01] <ogra> lets see what -kernel replies, many of them are in the US
[11:01] <ogra> so will get up later
[11:02] <lesshaste> ogra: did you say nothing should be called /dev/hdX in hardy?
[11:03] <lesshaste> there are plenty of hdX lines in rules.d
[11:04] <savvas> well we can fix it by recreating the files
[11:04] <savvas> but the bug will be broken i guess
[11:05] <savvas> lesshaste: zip -r $HOME/Desktop/etc_udev_rules.d.zip /etc/udev/rules.d/
[11:07] <lesshaste> ok
[11:07] <ogra> lesshaste, btw, which kernel version are you running ? -16 or -17 ?
[11:08] <lesshaste> 2.6.24-16
[11:08] <lesshaste> I didn't know -17 was out
[11:09] <savvas> lesshaste: after that: sudo rm -rf /etc/udev/rules.d/*; sudo aptitude reinstall udev
[11:09] <ogra> its in hardy-proposed ... waiting for promotion to hardy-updates
[11:09] <lesshaste> oh ok
[11:10] <savvas> lesshaste: give it a reboot to use the new rules afterwards, let's see if that helps out
[11:11] <lesshaste> savvas: how do I create new rules? Doesn't zip -r $HOME/Desktop/etc_udev_rules.d.zip /etc/udev/rules.d/ just zip up the old ones?
[11:11] <savvas> 12:09:12 < savvas> lesshaste: after that: sudo rm -rf /etc/udev/rules.d/*; sudo aptitude reinstall udev
[11:11] <savvas> reinstalling udev should recreate them
[11:11] <lesshaste> oh I never saw that?!
[11:12] <savvas> !
[11:12] <lesshaste> rebooting
[11:12] <savvas> ok :)
[11:13] <savvas> weird, ogra did you that command i gave previously?
[11:13] <savvas> did you see* :)
[11:20] <savvas> hm.. i wonder what happened to him
[11:21] <savvas> it took him 2 minutes before to reboot :\
[12:17] <lesshaste> hi :)
[12:17] <lesshaste> that was an absolute catastrophe
[12:17] <lesshaste> savvas, are you still about?
[12:19] <lesshaste> or ogra ?
[12:22] <savvas> lesshaste: a bit busy but yeah
[12:22] <savvas> it didn't work? :\
[12:22] <lesshaste> savvas, much much worse than that
[12:22] <lesshaste> savvas, the system wouldn't boot at all with the new rules.d
[12:22] <savvas> good we kept a back up then
[12:23] <lesshaste> savvas, well not really as I couldn't boot into linux at all
[12:23] <savvas> it's working again with the old rules?
[12:23] <savvas> ouch
[12:23] <savvas> not even with the live cd or the recovery option in grub?
[12:23] <lesshaste> savvas, I eventually booted into windows,mounted the linux partition and overwrote the old rules
[12:23] <lesshaste> not 2.6.22 will boot but 2.6.24 will not
[12:24] <savvas> hm.. better wait for -kernel as ogra proposed then
[12:24] <lesshaste> and I have no networking in 2.6.22 so I have had to find another computer to chat to you :)
[12:24] <savvas> i don't want to break anything else :)
[12:24] <lesshaste> well.. I would really like to boot 2.6.24 to get to where i was
[12:24] <savvas> it's really weird though, i used that here and it worked
[12:24] <lesshaste> it says it can't find the root file system
[12:24] <lesshaste> basically at the moment the computer is broken
[12:24] <lesshaste> either no networking or no booting
[12:25] <lesshaste> now 2.6.22 will boot I meant
[12:25] <lesshaste> if you could help me get back to square one that would be great
[12:26] <lesshaste> savvas, I looked and after doing the aptitude command I ended up with only two rules!
[12:26] <lesshaste> persistent-cd and persistent-net
[12:27] <savvas> hm..
[12:27] <lesshaste> I need to work on this computer today so it's a problem :(
[12:27] <savvas> well i made the booboo, i guess i have to fix it
[12:27] <lesshaste> thanks
[12:28] <savvas> boot up from a live cd and connect to the internet
[12:28] <lesshaste> I have a live usb key
[12:28] <savvas> that would work i guess
[12:28] <lesshaste> can you remind me how to boot form usb?
[12:28] <lesshaste> from
[12:28] <savvas> it depends on your bios i'm afraid
[12:29] <savvas> you stick your usb in and press the Del key several times while booting up
[12:29] <savvas> you have to change the boot sequence
[12:30] <savvas> here you're on your own, i don't know every bios :)
[12:30] <savvas> you choose the usb as the first option, then save your changes and exit
[12:31] <savvas> lesshaste: still there?
[12:31] <lesshaste> yes but I am not sure I  can do your first step
[12:31] <lesshaste> just trying 2.6.24 again
[12:32] <lesshaste> it says "Begin: Waiting for root file system"
[12:32] <lesshaste> before that
[12:32] <lesshaste> "Begin: Running /scripts/local-top"
[12:32] <lesshaste> and before that
[12:32] <lesshaste> "Begin: Mounting root files system...."
[12:33] <lesshaste> so it must just be looking in the wrong place I assume?
[12:34] <lesshaste> I can't see how to boot off the usb device sadly.. I tried "removable" as the first boot device with no luck
[12:35] <lesshaste> I can of course copy whatever is needed over on the usb device if that helps
[12:37] <savvas> lesshaste: don't you have an old ubuntu cd somewhere?
[12:37] <savvas> it doesn't have to be the newest release to do what we have to do
[12:37] <lesshaste> wireless won't work with an old version
[12:38] <lesshaste> but I am looking
[12:38] <savvas> lesshaste: you 're on a second pc there right?
[12:38] <lesshaste> yes
[12:38] <savvas> cool, you could pass on the commands without network then
[12:38] <lesshaste> ok
[12:39] <savvas> basicall, what we will do is to mount your root partition and unzip the old rules back to their place
[12:39] <lesshaste> I did that
[12:39] <lesshaste> that's how I have booted into 2.6.22
[12:39] <savvas> but through windows you don't keep permissions
[12:40] <lesshaste> ok.. but I am in 2.6.22 now.. so I can do the command
[12:40] <savvas> i guess that broke off while you unzipped it
[12:40] <lesshaste> what would you like me to do?
[12:40] <lesshaste> broken pc 1 is in 2.6.22
[12:40] <savvas> load the live cd environment normally
[12:40] <lesshaste> I don't have a live cd
[12:40] <lesshaste> why do I need one?
[12:40] <savvas> oh.. you don't :)
[12:40] <lesshaste> ok
[12:41] <lesshaste> so.. I am all yours :)
[12:41] <savvas> let me see, you booted to an older kernel right?
[12:41] <lesshaste> yes
[12:41] <lesshaste> I also don't understand why permissions will break 2.6.24 but not 2.6.22
[12:41] <savvas> wanna try reinstall the kernel images first?
[12:42] <lesshaste> really?
[12:42] <lesshaste> why would that help?
[12:42] <savvas> it could set up the boot process to recognise the right device
[12:42] <lesshaste> ok
[12:42] <lesshaste> so what do I need to download?
[12:43] <savvas> sudo aptitude reinstall linux-image-2.6.24-16-generic
[12:43] <lesshaste> grr :)
[12:43] <lesshaste> you know I don't have a network connection on the broken pc
[12:44] <lesshaste> so I need to download it on the other one
[12:44] <savvas> i know :\
[12:44] <lesshaste> and move it across on the usb stick
[12:44] <savvas> argh no then
[12:44] <savvas> get a working version first hen
[12:44] <savvas> *then
[12:44] <savvas> wait
[12:45] <savvas> er.. maybe you already have it downloaded
[12:45] <savvas> lesshaste: ls /var/cache/apt/archives/linux-image*
[12:46] <lesshaste> I have
[12:46] <savvas>  /var/cache/apt/archives/linux-image-2.6.24-16-generic_2.6.24-16.30_i386.deb ?
[12:46] <lesshaste> linux-image-2.6.24-16-generic_2.6.24-16/30_i386.deb
[12:46] <lesshaste> and
[12:47] <lesshaste> linux-image-generic_2.6.24.16.18_i386.deb
[12:47] <lesshaste> (excuse typos)
[12:47] <savvas> no probs
[12:47] <savvas> we could could try reinstall that
[12:47] <lesshaste> linux-image-2.6.24-16-generic_2.6.24-16.30_i386.deb
[12:47] <lesshaste> ok
[12:47] <lesshaste> how do I do that?
[12:48] <savvas> sudo dpkg -i /var/cache/apt/archives/linux-image-2.6.24-16-generic_2.6.24-16.30_i386.deb
[12:50] <lesshaste> and you think that might fix something?
[12:50] <lesshaste> what else would the aptitude command you gave me have changed to break the system?
[12:51] <savvas> that, or this command: sudo dpkg-reconfigure linux-image-2.6.24-16-generic
[12:51] <savvas> i must warn you i've never tried the latter one
[12:51] <lesshaste> :)
[12:51] <lesshaste> which one?!
[12:51] <savvas> while you installed with dpkg
[12:51] <savvas> did it say anything about reconfiguring grub?
[12:52] <lesshaste> yes
[12:52] <savvas> and no problems there?
[12:53] <savvas> do: cat /boot/grub/menu.lst | grep -i hd
[12:53] <lesshaste> ok so now 2.6.24 boots :)
[12:54] <savvas> cool
[12:54] <lesshaste> but networking is still broken
[12:54] <lesshaste> going to try to fix that now
[12:54] <savvas> you have a live environment too?
[12:54] <savvas> sorry, gnome*
[12:55] <savvas> lesshaste: this is still with the old rules right?
[12:56] <lesshaste> yes
[12:56] <lesshaste> the networking was killed by reinstalling the kernel probablu
[12:56] <lesshaste> just checking
[12:57] <savvas> you could try recompile the kernel-modules as well :)
[12:57] <savvas> i mean reinstall
[12:57] <savvas> man, it's my typo day today
[12:58] <lesshaste> where do I find them?
[12:59] <savvas>  /var/cache/apt/archives/linux-ubuntu-modules-2.6.24-16-generic_2.6.24-16.23_i386.deb
[12:59] <savvas>  /var/cache/apt/archives/linux-restricted-modules-2.6.24-16-generic_2.6.24.12-16.34_i386.deb
[12:59] <savvas>  /var/cache/apt/archives/linux-restricted-modules-common_2.6.24.12-16.34_all.deb
[12:59] <savvas> you use sudo dpkg -i for each one
[13:01] <savvas> and give it a reboot again
[13:02] <savvas> btw, I can't tell you how sorry I am for breaking it up :(
[13:03] <lesshaste> there are three restricted modules packages
[13:03] <savvas> linux-restricted-modules-generic* ?
[13:03] <lesshaste> modules-common, modules and modules-generic
[13:03] <savvas> ignore that one, it's just a meta-package
[13:03] <savvas> a "shortcut" :)
[13:04] <lesshaste> thanks for the apologising
[13:04] <lesshaste> I should have known better than to follow instructions like that blindly
[13:05] <savvas> the good news is you found your way through.. and i have to stop suggesting stuff that could be dangerous
[13:05] <lesshaste> well.. when I have networking back I will be pleased :)
[13:06] <savvas> i hope we can fix that as well :)
[13:06] <lesshaste> it's quite odd that it's not working
[13:06] <savvas> still not working after a reboot?
[13:06] <lesshaste> the instructions I following originally are https://bugs.launchpad.net/ubuntu/+bug/34902/comments/177
[13:08] <savvas> you can reinstall the headers too if you think that's appropriate
[13:10] <savvas> should be these two: /var/cache/apt/archives/linux-headers-2.6.24-16-generic_2.6.24-16.30_i386.iso  /var/cache/apt/archives/linux-headers-2.6.24-16_2.6.24-16.30_all.deb
[13:15] <lesshaste> ok
[13:15] <lesshaste> the problem seems to be starting wireless.. wlan0 is there
[13:15] <lesshaste> but without an ip address
[13:16] <Iulian> Hey pedro_!
[13:16] <pedro_> hi Iulian
[13:16] <lesshaste> hmm.. what is wlan0:avahi??
[13:17] <savvas> lesshaste: avahi is the avahi-daemon
[13:17] <savvas> but i'm no expert at that
[13:17] <lesshaste> what is that for?
[13:18] <savvas>  This package contains the Avahi Daemon which represents your machine
[13:18] <savvas>  on the network and allows other applications to publish and resolve
[13:18] <savvas>  mDNS/DNS-SD records.
[13:19] <lesshaste> hmm :)
[13:19] <lesshaste> I just want my networking back!
[13:19] <lesshaste> waah!
[13:21] <lesshaste> savvas, any idea why this rules.d thing might have killed my networking?
[13:21] <savvas> lesshaste: wanna try unzip the rules again?
[13:22] <lesshaste> why would that help?
[13:22] <savvas> ls -l /etc/udev/rules.d/
[13:22] <savvas> the files have -rw-r--r-- 1 root   root ?
[13:22] <lesshaste> yep
[13:24] <lesshaste> I'm going to have to give up and go work somewhere else
[13:24] <savvas> hold a sec
[13:24] <savvas> try reinstall udev once more: sudo dpkg -i /var/cache/apt/archives/udev_117-8_i386.deb
[13:25] <savvas> it won't touch the old rules, but might reconfigure the system to use them again (?)
[13:25] <savvas> (i'm speculating)
[13:26] <savvas> then reboot
[13:29] <lesshaste> wlan0 is up
[13:29] <lesshaste> it just doesn't have an ip adress
[13:29] <lesshaste> there must be some simple solution but I can't find it
[13:29] <lesshaste> and I have go get on with work
[13:32] <lesshaste> bye
[13:33] <savvas> he left?
[13:33] <savvas> darn
[15:12] <bddebian> Boo
[15:46] <Iulian> pedro_: Could you please translate bug 227549?
[15:47] <pedro_> Iulian: sure, give me a min
[15:52] <pedro_> Iulian: done
[15:53] <Iulian> pedro_: Thanks
[15:53] <pedro_> you're welcome
[17:52] <pochu> asac: the replytolist Thunderbird extension doesn't seem to work for me. I'm on Hardy, do you have any idea why?
[17:54] <pochu> asac: this page says TB needs a patch and that the Ubuntu maintainer applied it... do you know if it's still there? http://alumnit.ca/wiki/index.php?page=ReplyToListThunderbirdExtension#toc4
[17:54] <pochu> hmm, looks like:
[17:54] <pochu>   * debian/patches/reply-to-list-support: port reply-to-list-support to 2.0
[17:54] <pochu>     branch
[17:56] <seb128> why are people not using evolution which is the default mailer in ubuntu?
[17:56] <ccooke> seb128: they prefer something else?
[17:57] <laga> let's just drop thunderbird if evolution is the default mailer. duh..
[17:57] <seb128> that doesn't reply to the question
[17:57] <seb128> very constructive guys
[17:57] <pochu> seb128: because I started using Thunderbird since I use Windows and haven't needed anything else yet ;)
[17:58] <ccooke> seb128: so what you're *actually* asking is "How could Evolution be improved to draw more users to the default"?
[17:58] <laga> seb128: i'm not using evolution because i don't want to.
[17:58] <pochu> well except a couple of extensions, and one of them doesn't work...
[17:58] <laga> also, i'm using kubuntu and nobody should be forced to use kmail ;)
[17:58] <seb128> ccooke: the question is "what makes user switch to something else", or rather "what should we aim at fixing there"
[17:59] <seb128> ccooke: because if most user switch that's clearly that the default software has issues
[17:59] <pochu> seb128: also Evolution is more than a mail client AFAIK, isn't it? It would be like comparing Outlook with Outlook Express...
[17:59] <seb128> ccooke: and I would like to know which one so we can work on solving those
[17:59] <seb128> pochu: well, nobody force you to use the calendar, tasks, etc
[17:59] <pochu> that's right
[18:00] <ccooke> seb128: I use Evolution - however, I can't use it at work.
[18:00] <pochu> I have never tried it TBH, I guess I'll look at it one day :)
[18:00] <persia> seb128: Speaking for myself, I found evolution significantly slower than claws for my needs.
[18:00] <ccooke> It doesn't work reliably with our Exchange server (I believe because of our use of Enterprise Vault, which is a third party tool)
[18:03] <seb128> ccooke: is there any linux software working correctly with your exchange server?
[18:03] <ccooke> Firefox? :-)
[18:04] <ccooke> I'm currently using OWA directly
[18:04] <seb128> persia: what is slower? network transferts? starting time? rendering?
[18:05] <persia> seb128: Startup and time from pressing "Reply" to having an editing window are the two things I noticed.
[18:05] <ccooke> seb128: Some information here: https://forums.symantec.com/syment/board/message?board.id=106&thread.id=9475
[18:06] <ccooke> seb128: (but I don't have the time to try tinkering at work)
[18:06] <seb128> I guess those are not the reasons most user run rather thunderbird
[18:06] <seb128> and not things easy to change
[18:06] <persia> seb128: Note that my case may be a little odd: I typically have a fair bit of memory pressure, and so am more likely to encounter issues with larger image size than many.
[18:06] <seb128> evolution takes 1 second to open a reply dialog on a 3 year old configuration, that's not perfect but I don't think that's a real issue
[18:08] <persia> claws is ~600 ms on a 4-year old worksation with over 1 MB/s network traffic, full cache, and reported 100% proc usage (mostly iowait).
[18:09] <persia> Mind you, it's not a real issue: depends on use case.  Typically it takes several minutes to type the message anyway.
[18:19] <ogra> we should really switch to balsa
[18:19]  * seb128 slaps ogra
[18:19]  * ogra hides 
[18:20] <ogra> bah, to solw :)
[18:20] <ogra> *slow
[18:24] <seb128> pedro_: bug #227825 == bug #204434?
[18:42] <asac> pochu: we ship that patch iirc
[18:43] <asac> pochu: is the extension properly installed?
[18:49] <pochu> asac: woops, nevermind, works fine!
[18:49] <pochu> asac: my bad, I thought it was 'ctrl+l' instead of 'ctrl+i'
[18:58] <asac> pochu: thanks for confirming ;)
[19:06] <pedro_> seb128: it looks different to me, but looking at Michael comment could be
[20:05] <bdmurray> pedro_: still around?
[20:06] <pedro_> bdmurray: yeap
[20:06] <bdmurray> I'm guessing bug 208181 is a dup of something - do you know what?
[20:07] <bdmurray> They say you need to specify a share name
[20:09] <pedro_> bdmurray: yeah it's a dup, assign it to gvfs in the meantime
[20:10] <bdmurray> pedro_: okay, I'll see if I can find the one if it should be a dup of
[20:10] <pedro_> looks like bug 223372
[20:10] <bdmurray> ogasawara: Have you noticed that the l-r-m package redirects to linux-meta?
[20:11] <ogasawara> bdmurray: I haven't
[20:13] <bdmurray> Yeah, if you don't use the l-r-m-2.6.xyz it gets reassigned to linux-meta which I think is kind of strange
[20:13] <ogasawara> huh
[20:14] <bdmurray> Its interesting that there is a just 'linux' package but not a 'l-r-m' and 'l-u-m' package
[20:17] <secretlondon> yay debian have fixed the libsoundtouch bug, now to patch audacity!
[20:18] <thekorn> hello @all! - what should I do with a report like bug 226221? refering to the CoC and close it as 'Invalid'?
[20:19] <bdmurray> pedro_: maybe more like bug 209520
[20:20] <bdmurray> thekorn: I'll take care of it
[20:20] <thekorn> bdmurray, thanks a lot
[20:25] <thekorn> bdmurray, to be honest: I don't understand your last change to py-lp-bugs,
[20:25] <thekorn> the xpath change for comments
[20:25] <bdmurray> 'boardComment' became 'boardComment ' in the html version
[20:26] <bdmurray> using contains will match either one
[20:26] <thekorn> but unfortunatly now it is totaly broken :(
[20:26] <thekorn> because it now also matches div class="boardCommentDetails" for example
[20:28]  * thekorn hates string changes in lp
[20:28] <bdmurray> hmm, I'd tested it a bit
[20:29] <bdmurray> Do you know how we could make it match either 'boardComment' or 'boardComment    '?
[20:29] <bdmurray> I'd prefer not to have to keep changing it
[20:31] <thekorn> we could use something like    //body//div[@class="boardComment"] | //body//div[@class="boardComment   "]
[20:31]  * thekorn reads the xpath tutorial
[20:34] <thekorn> maybe they accidentally changed this string anyway
[20:35] <bdmurray> Right if it was an accident it might go back to "boardComment" or could become "boardComment  " someday
[20:36] <thekorn> but if they keep on adding whitespaces at the end of attributes, we maybe need an xpath hook function to remove them
[20:37] <thekorn> or change all xpath expressions
[20:37] <thekorn> I'm looking forward the day when launchpad gets a real database API
[20:48] <thekorn> bdmurray, http://paste.ubuntu.com/10791/ fixes parsing of comments for me,
[20:48] <thekorn> tested for some bugreports
[20:49] <bdmurray> cool, I'm looking at another idea at the moment
[20:50] <thekorn> btw, your greasemonkey script is really cool
[20:53] <bdmurray> thekorn: thanks, I've been learning lots of xpath
[20:54] <thekorn> this is even shorter: '//body//div[@class="boardComment" or @class="boardComment "]'
[20:54] <bdmurray> speaking of this seems to work - xmldoc.xpathEval("//body//div[normalize-space(@class)='boardComment']")
[20:54] <thekorn> YAY!!
[20:54] <bdmurray> The normalize-space function returns the argument string with whitespace normalized by stripping leading and trailing whitespace and replacing sequences of whitespace characters by a single space.
[20:55] <thekorn> I was always looking for such a function, but did not find any reference to it
[20:56]  * thekorn needs new glasses
[20:57] <bdmurray> I'll fix the boardComment parsing using that for Hardy and Intrepid
[20:57] <thekorn> super, thanks
[21:01] <james_w> hi secretlondon
[21:01] <secretlondon> hi james_w
[21:01] <james_w> secretlondon: I saw that soundtouch was fixed, are you ok to handle audacity?
[21:02] <secretlondon> james_w yeah, as it's just my patch that didn't work because of soundtouch
[21:02] <secretlondon> I'm just setting up this new machine with all the dev tools, and gonna make an intrepid pbuilder
[21:02] <james_w> secretlondon: cool, are you aiming for an update in hardy? Is that even needed?
[21:02] <secretlondon> james_w it would be nice, but other programs also depend on libsoundtouch
[21:03] <james_w> intrepid pbuilders were broken last I heard, does anyone know whether that is fixed now?
[21:03] <secretlondon> and it's a change in the pc file, which is _bound_ to break stuff
[21:03] <james_w> secretlondon: ah, of course, you needed a new upstream version as well didn't you?
[21:03] <secretlondon> james_ w yes, and a pc file with a different name
[21:03] <secretlondon> so I guess too risky, as we'd have to patch every other music program that depended on libsoundtouch
[21:05] <james_w> yep
[21:05] <james_w> feel free to ping me if you need anything
[21:06] <secretlondon> we'll have to do that for intrepid, but at least we'll have the same pc name as upstream, and all the non-debian based distros
[21:06] <secretlondon> james_w thanks, should I proactively patch the other apps that depend on it? I presume Debian will have the issue firts
[21:07] <james_w> making patches should be straightforward, and Debian would appreciate it as well, so I think it could be worthwhile.
[21:07] <secretlondon> ok
[21:08] <james_w> not everything may use the .pc
[21:08] <james_w> I can grab a list of the packages that may be affected if you like
[21:09] <secretlondon> james_w that would be useful thanks
[21:10] <noelferreira> my keys get stuck sometimes and other times don't work. can anyone help me with this huge bug: http://pastebin.com/m7bc88052
[21:19] <james_w> secretlondon: http://pastebin.com/f3b18ab39
[21:19] <james_w> that's hardy, so there may be some things that sneak in to intrepid, I can't check yet though.
[21:20] <james_w> grep-dctrl -FBuild-Depends -sPackage,Build-Depends -e "soundtouch" < /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_hardy_*_source_Sources if you are interested
[21:21] <secretlondon> james_w thanks, I can't get an intrepid pbuilder E: No such script: /usr/share/debootstrap/scripts/intrepid
[21:21] <secretlondon> so I can't test which is suboptimal
[21:22] <james_w> secretlondon: you need to enable hardy-backports and install the debootstrap from there.
[21:22] <secretlondon> ah! thanks
[21:22] <james_w> it may well fail then as well
[21:22] <james_w> you could test in a hardy pbuilder, at least for now, it would have a reasonable chance of giving the same results.
[21:22] <secretlondon> true
[21:23]  * secretlondon is scared that hardy security wasn't ticked by default
[21:23] <secretlondon> but updates was
[21:23] <bdmurray> thekorn: weren't there some other changes you wanted merged after hardy was out?
[21:23] <jdavies> secretlondon: security.u.c is down at the moment, however you may grab them from archive.u.c
[21:24] <secretlondon> jdavies, thanks, I was more concerned that this is a vanilla install
[21:24] <secretlondon> james_w except that a hardy pbuilder would have the old library
[21:25] <thekorn> bdmurray, https://bugs.edge.launchpad.net/python-launchpad-bugs/+bugs?field.tag=fix-available and there is also an intrepid milestone
[21:25] <james_w> secretlondon: there are tricks you can play to get around that. I can fill you in, or offer to test build your patches.
[21:26] <secretlondon> james_w I'm still setting this machine up, I'll play tonight and let you know
[21:26]  * secretlondon is intending to do more patching and dev work for this release :)
[21:27] <james_w> \o/
[21:27] <thekorn> bdmurray, but maybe I should go throught them, test them and add one by one to the .main branch
[21:28] <james_w> secretlondon: weren't you packaging some tuxpaint snapshots in your ppa?
[21:29] <secretlondon> james_w one thing, I have the new packaging for cinepaint in my ppa, done by sidux, not yet in debian. should I stick on revu?
[21:29] <bdmurray> or maybe we can find some time to work on it at UDS
[21:29] <noelferreira> my keys get stuck sometimes and other times don't work. can anyone help me with this huge bug: http://pastebin.com/m7bc88052
[21:30] <secretlondon> james_w I have the new version of tuxpaint (0.9.19) in my ppa but talking to the dd to share packaging
[21:30] <james_w> secretlondon: yeah, if you want it in intrepid go for it.
[21:30] <james_w> secretlondon: cool, ogra was looking at the merge earlier I think. ogra, did you get the tupaint merge done?
[21:31] <secretlondon> james_w I'd love it in intrepid, but it's not my packaging it's etorix from sidux's. It's still been poor not to have in hardy
[21:31] <thekorn> bdmurray, sounds good!
[21:31] <secretlondon> james_w debian have the same version of tuxpaint that we have currently 0.9.17
[21:31] <secretlondon> I changed the depends/recommends (in consulation with the dd), so we have a later version I suppose
[21:32] <james_w> secretlondon: ah, I must have been mistaken then, sorry.
[21:32] <secretlondon> james_w it would need a merge from debian, but it'd be better to get 0.9.19
[21:32] <james_w> secretlondon: though there has been an upload in debian to -1.1, so a merge is still needed.
[21:32] <secretlondon> I presume we can have my packaging, and if ben from Debian makes a better package we can change
[21:32] <james_w> secretlondon: well, if you get in done in Debian that would be even better.
[21:33] <secretlondon> james_w i'd rather get Ben to make the package and us to sync
[21:34]  * secretlondon notes that these don't all have to be done this evening ;)
[21:35] <james_w> hehe
[21:40] <noelferreira> my keys get stuck sometimes and other times don't work. can anyone help me with this huge bug: http://pastebin.com/m7bc88052
[21:42] <secretlondon> noelferreira, this is a poor place for support - sorry
[22:04] <bdmurray> calc: are you familiar with an openoffice bug where a username and password are required but there is no text entry field for the username when accessing files on an sftp share?
[22:04] <bdmurray> I haven't found one right away
[22:17] <calc> bdmurray: i think there is a sftp bug open already, but not sure if it is that specifically
[22:18] <bdmurray> calc: I saw bug 214275 but they seem to indicate the correct username is filled in while I have no idea what username is used
[22:22] <sectech> Has anyone come through here recently stating there hardy livecd won't boot right... I just bought a new sata drive and I can't get the damn cd to load and recognize the drive.... yet the gusty live cd will work fine
[22:23] <secretlondon> sectech there is/was a hardy bug in development with some cd rom drives
[22:24] <sectech> Hhmm... the install worked fine when I had the ata drive hooked up.... and gusty is installing as I type this...
[22:24] <sectech> I used the latest cd image too
[22:24] <sectech> and yes the md5sums checked out
[22:36] <calc> bdmurray: you scared my electricity away ;-)
[22:38] <bdmurray> that's a new one
[22:49] <sectech> k... It's the kernel version.... Whatever we were using in Alpha 1 reads the hard drive just fine...
[22:49] <sectech> I smell a bug....
[22:50] <sectech> I'll have to install hardy with alpha 1 and then do the updates.
[22:53] <bdmurray> Wouldn't the updates, specifically the new kernel version, break it then?
[22:53] <bdmurray> calc: I've updated bug 214275
[22:53] <bdmurray> Let me know if you need anything else
[22:54] <sectech> that will be the ultimate test won't it
[22:55] <sectech> I'm going to try the alternate cd just for giggles..
[22:55] <sectech> might as well play with the problem while I can
[22:56] <bdmurray> they use the same kernel version
[22:57] <sectech> yeh I know.... like I said, just for giggles....   plus the release cd's wouldn't have the latest kernel version anyway... we had an upgrade after hardy was released.
[22:59] <sectech> I kinda wanted the 64 bit installed, but whatever
[23:03] <sectech> Is there a mirror where we could still get the alpha and beta versions?
[23:03] <bdmurray> not that I know of
[23:04] <sectech> crap
[23:05] <sectech> k... well I am gonna run with the alpha 1 since it's working
[23:05] <sectech> brb
[23:07] <calc> bdmurray: thanks
[23:08] <calc> bdmurray: i'd have to try it again i think it might have broken later
[23:14] <noelferreira> my keys get stuck sometimes and other times don't work. can anyone help me with this huge bug: http://pastebin.com/m7bc88052
[23:41] <secretlondon> james_w I've made my debdiff, but I note that the new lib ftbfs due to lack of intltool
[23:41] <james_w> secretlondon: I think that's a known problem with intrepid at the moment. Or is this hardy?
[23:41] <secretlondon> james_w intrepid
[23:42] <james_w> yeah, I think that's known.
[23:42] <james_w> I think you'll just have to sit tight for a couple of days until this smooths out.
[23:42] <james_w> or you could just get and upload and hope :-)
[23:44] <james_w> secretlondon: your debdiff looks pretty simple though
[23:44] <james_w> are you aware there is a newer version in Debian?
[23:45] <james_w> and we probably want it, as it fixes the build with gcc-4.3, which is what is default in intrepid.
[23:51] <secretlondon> james_w argh, didn't check
[23:51] <secretlondon> my patch is really simple though
[23:52] <james_w> yep, but I don't think it will build without Debian's changes.
[23:52] <secretlondon> ah
[23:52] <james_w> the merge should be straightforward, and you can roll your patch in with that.
[23:52] <secretlondon> sure
[23:53] <james_w> anyway, time for bed I think. Good night.
[23:53] <secretlondon> night! thanks for your help