[09:02]  * BUGabundo_remote says Hi... to the rain :[
[10:34] <xelister> hi, the retty program seems to be missing?  https://launchpad.net/ubuntu/lucid/+package/retty  is it only in i386 but not on amd64 ??
[10:35] <xelister> http://packages.ubuntu.com/lucid/retty
[10:35] <xelister> wtf why just i386
[10:38] <xelister> ok I see part of that tool is written in assembler, not compatible with 64 it seems
[11:00] <xelister> hehe its a hack.. needs 386 assembler
[13:02] <PrototypeX29A> hi
[13:03] <PrototypeX29A> sometimes i just don't get which the Bug invalidators for
[13:03] <PrototypeX29A> ask for
[13:03] <PrototypeX29A> https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/156517
[13:03] <ubot2> Launchpad bug 156517 in evolution (Ubuntu) "New mail doesn't filter anymore, restart doesn't work either" [Low,Invalid]
[13:05] <PrototypeX29A> here reporter are just shut up because they don't know what is left to add
[13:09] <PrototypeX29A> pedro_: you did it!
[13:16] <PrototypeX29A> it is kind of frustrating reporting bugs which are getting closed with no real clue what is missing
[13:16] <PrototypeX29A> even with being a software developer myself
[13:18] <PrototypeX29A> how do i reopen a bug, just change status on 'new'?
[13:27] <pedro_> PrototypeX29A, pardon me?
[13:27] <pedro_> PrototypeX29A, which bug was closed by me ?
[13:27] <PrototypeX29A> https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/156517
[13:27] <ubot2> Launchpad bug 156517 in evolution (Ubuntu) "New mail doesn't filter anymore, restart doesn't work either" [Low,New]
[13:28] <PrototypeX29A> i could figure out what the missing piece of information was
[13:28] <pedro_> PrototypeX29A, please open a new one, that's a really old bug
[13:28] <PrototypeX29A> could not
[13:28] <PrototypeX29A> yes, but it is still the same symptoms
[13:29] <PrototypeX29A> it never was fixed
[13:29] <pedro_> PrototypeX29A, as said, please open a new one that was closed 2 years ago, the code might change there in Evolution
[13:29] <pedro_> PrototypeX29A, also please test it with the Maverick version of Evolution, lot of things changed in that new branch and it's totally worth to give it a try with that
[13:29] <PrototypeX29A> may i just copy and paste the problem description?
[13:30] <PrototypeX29A> maverick?
[13:30] <pedro_> provide a better one if you can actually...
[13:30] <PrototypeX29A> i don't know how to write a better bug report
[13:30] <PrototypeX29A> neither did the original poster
[13:30] <PrototypeX29A> i guess
[13:31] <pedro_> you might find the guide at http://www.chiark.greenend.org.uk/~sgtatham/bugs.html useful for doing that
[13:31] <PrototypeX29A> i think i have read that
[13:34] <PrototypeX29A> without knowing what is the problem with the specific bug report, i cannot write a better one
[13:36] <vish> PrototypeX29A: you should have read the bug and the comments as well ;)  pedro_ has asked "Can you tell us a few steps in order to trigger the bug? thanks."
[13:36] <PrototypeX29A> yes
[13:36] <vish> PrototypeX29A: there are no steps to reproduce hence is not easy to invistigate
[13:36] <PrototypeX29A> but these few steps were already provided
[13:36] <vish> investigate*
[13:37] <PrototypeX29A> so bugs which are not reliably reproducable will be closed?
[13:37] <pedro_> PrototypeX29A, the steps were not provided and people started to comment random things on that report too
[13:38] <pedro_> PrototypeX29A, you're welcome to open the bug upstream at bugzilla.gnome.org if you don't have or don't know how to reproduce the issue though
[13:38] <vish> PrototypeX29A: not really , the bug was experienced by only by a couple of users and then they didnt reply
[13:38] <pedro_> PrototypeX29A, the upstream developers might have a better clue on what's going on there.
[13:38] <PrototypeX29A> vish: i guess because they didn't know what to reply
[13:39] <PrototypeX29A> as the bug is hard to reproduce
[13:39] <vish> PrototypeX29A: or they aernt affected anymore ;)
[13:39] <vish> PrototypeX29A: anyways , opening a new bug is better than re-opening an age old bug
[13:39] <PrototypeX29A> because they switched email clients
[13:39] <PrototypeX29A> vish: i am just afraid reporting a lot of random data just to get closed too
[13:40] <vish> PrototypeX29A: still no harm in reporting , new bugs cost you nothing ;p
[13:41] <PrototypeX29A> launchpad still costs me a lot of energy
[13:43] <PrototypeX29A> vish: it costs me a less more time than it costs you to set it to invalid
[13:45] <PrototypeX29A> when i try to report it it just urges me to check whether it is already reported
[13:45] <vish> PrototypeX29A: actually , a triager thinks a lot more , we spend more time trying to find ways to trigger the bug before closing.. we do really want to get the bugs fixed :)
[13:45] <PrototypeX29A> i want to believe that :)
[13:47] <PrototypeX29A> well i will open a new bug, even if there are already two bugs fitting my problem
[13:51] <PrototypeX29A> https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/585375
[13:51] <ubot2> Launchpad bug 585375 in evolution (Ubuntu) "Mail filters occasionally do not work (affects: 1)" [Undecided,New]
[13:53] <PrototypeX29A> if i had a deterministic way to reproduce it, i would tell you
[13:57] <PrototypeX29A> after all i respect the work the triager does, but often the answers leave me with 'What am I supposed to do?' before i move on to antoher program
[13:58] <vish> PrototypeX29A: since you are experiencing the bug could you also report it upstream?  i'v posted a comment with link how to do that
[14:00] <PrototypeX29A> i give it a try
[14:01] <vish> PrototypeX29A: https://wiki.ubuntu.com/DebuggingEvolution  < this wiki will also be useful for debugging evolution bugs
[14:09] <PrototypeX29A> error messages from evolution always are kind of meaningless
[14:18] <PrototypeX29A> pedro_: i don't know how i do test with the maverick version
[14:19] <PrototypeX29A> without installing maverick
[14:19] <pedro_> PrototypeX29A, i'm afraid that's the only easy way to do that...
[14:20] <micahg> PrototypeX29A: virtualbox?
[14:21] <micahg> PrototypeX29A: testdrive
[14:21] <PrototypeX29A> i was afraid you would say that
[14:23] <PrototypeX29A> as the bug only happens occasionally i would have to use maverick for a productive system, that is not what i am willing todo
[14:23] <micahg> maybe hggdh has another idea?
[14:24] <PrototypeX29A> pedro_: the idea is to see whether the bug already is fixed?
[14:24] <pedro_> PrototypeX29A, yes, evolution changed a lot during the 2.30 cycle, so would be worth to give it a try
[14:24] <vish> PrototypeX29A: what you can also do is , create a new partition and install maverick on the partition , while you can have karmic preserved just in case you need to get back
[14:25] <pedro_> you can set up a jhbuild environment for evolution as well, but that's a bit tricky
[14:29] <PrototypeX29A> vish: i encounter enough bugs with the 'stable' version, i am not gonna go for something 'testing'
[14:30] <PrototypeX29A> linux makes me very anxious
[14:30] <vish> PrototypeX29A: well , you are sure missing out on all the fun ;p
[14:30] <PrototypeX29A> i just want a stable system
[14:31] <PrototypeX29A> without paying money :)
[14:31] <PrototypeX29A> i once had unstable gentoo, that really was fun
[14:47] <hggdh> PrototypeX29A: OK, what can I do to help you?
[14:48] <PrototypeX29A> i don't think you can
[14:48] <hggdh> oh. I see.
[14:48] <PrototypeX29A> i don't know why your name was dropped
[14:49] <hggdh> pedro_: good morning, and could you renew my bugcontrol?
[14:50] <micahg> hggdh: PrototypeX29A has an evolution bug that's occasional, so I thought of you :)
[14:50] <hggdh> PrototypeX29A: oh, BTW, I am running Evolution git, and I do not have problems with filters
[14:51] <hggdh> micahg: yes. But it seems I cannot help him/her
[14:51] <pedro_> hggdh, bom dia, yes one sec
[14:51] <PrototypeX29A> i think a lot of people do not have the problem
[14:52] <micahg> hggdh: is it possible to backport latest evo to Lucid?
[14:52] <PrototypeX29A> i could name a lot of bugs, which most people don't seem to encounter
[14:52] <PrototypeX29A> but i do, it is very annoying, sometimes i think i am insane
[14:52] <vish> micahg: latest evo was too new a code and untested , hence wasnt used for lucid
[14:52] <pedro_> hggdh, renewed
[14:52] <bcurtiswx> pedro_, did you get my email back about -mentorship?
[14:52] <hggdh> latest stable is 2.30, and there are at least 2 PPA offering it
[14:53] <hggdh> micahg: ^
[14:53] <pedro_> bcurtiswx, yes, thank you for answering ;-)
[14:53] <bcurtiswx> pedro_: awesome, thx
[14:53] <pedro_> bcurtiswx, i'm waiting for the other responses to send more info, so stay tune ;-))
[14:53] <micahg> PrototypeX29A: so maybe use the latest stable and see if that helps?
[14:53] <hggdh> Evo 2.31 would require additional backports -- libgdata and gtkhtml, at least
[14:53] <bcurtiswx> pedro_: rgr that
[14:54] <PrototypeX29A> micahg: latest stable as in Lynx?
[14:54] <micahg> PrototypeX29A: no, evo in PPA
[14:54] <hggdh> PrototypeX29A: *also*
[14:54] <PrototypeX29A> what is PPA?
[14:54] <micahg> hggdh: is there a reliable maintainer PPA for it?
[14:54] <micahg> !ppa | PrototypeX29A
[14:54] <ubot2> PrototypeX29A: A Personal Package Archive (PPA) can provide alternate software not normally available in the offical Ubuntu repositories - Looking for a PPA? See https://launchpad.net/ubuntu/+ppas - WARNING: PPAs are unsupported third-party packages, and should be used at your own risk.
[14:54] <hggdh> I have not looked at it in details, micahg. But Maverick has 2.30 already
[14:55] <hggdh> pedro_: muchas gracias
[15:10] <Hamra> seeing that encryption ain't new around, can it really be no one else had a bug like this? bug 584067
[15:10] <ubot2> Launchpad bug 584067 in debian-installer (Ubuntu) "setting up swap encryption from alternate CD uses unstable device nodes (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/584067
[15:48] <Kangarooo> https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/533478 can somebody help with making backtrace? what backtrace does? ive did what is here https://wiki.ubuntu.com/Backtrace and nothing was done while doing backtrace in programm
[15:48] <ubot2> Launchpad bug 533478 in thunar (Ubuntu) "Deleting file and holding enter opens file witch isnt selected. Witch is to the right from deleted file. (affects: 1) (heat: 8)" [Undecided,Incomplete]
[15:49] <Kangarooo> i did exacly what is writen in section Generation exept first step couse i had gdb already installed
[15:50] <Kangarooo> em i mean second i didnt do but also first i didnt do
[15:53] <hggdh> Hamra: devices that get reassigned continuously on boot are not common
[15:54] <Hamra> ahh... i see
[15:55] <hggdh> Hamra: it would be good, also, to have the dmesg showing device allocation
[16:00] <hggdh> Hamra: actually, please run 'ubuntu-bug -p linux 584067'
[16:01] <hggdh> this will collect a lot of data that may help in pinpoint the issue
[16:04] <stenten> hggdh: Do you mind if I ask what the -p flag does in ubuntu-bug? It's not in the man page.
[16:04] <stenten> (I'm assuming it apport-collects the "linux" info even though the bug isn't filed against the kernel?)
[16:11] <BlackZ> stenten: I think it indicates the package
[16:12] <hggdh> stenten: it tells ubuntu-bug to collect data for the package specified in the parameter (-p linux)
[16:12] <stenten> ok thank you.
[16:12] <BlackZ> hggdh: but it's deprecated
[16:13] <hggdh> BlackZ: is it?
[16:14] <BlackZ> hggdh: Warning: The options -p/-P are deprecated, please do not use them.  See /usr/bin/ubuntu-bug --help
[16:15] <BlackZ> hggdh: I think 'ubuntu-bug linux 584067' would be enough
[16:15] <BlackZ> (but I'm not sure)
[16:15] <hggdh> BlackZ: I cannot see this warning anywhere. But yes, you do not need to -p (or --package)
[16:16] <BlackZ> hggdh: try 'ubuntu-bug -p linux' and you will see it
[16:17] <micahg> I thought -p was for apport-collect when the bug was not tasked to that package
[16:17] <BlackZ> micahg: nope, it indicates the package
[16:18] <hggdh> weird.
[16:18] <hggdh> time to dig in the source
[16:18] <BlackZ> heh
[16:18] <micahg> BlackZ: or tasked to multiple packages I guess, if it just has one task, it will just DTRT
[16:18] <hggdh> mostly cuz --help does not say anything
[16:21] <Kangarooo> is there a command that shows all installed packages by date?
[16:22] <Kangarooo> witch i installed thrue terminal with aptitude
[16:22] <BlackZ> Kangarooo: I'd use dpkg -l
[16:23] <BlackZ> for filter them, I'm not sure if it can be possible (?)
[16:24] <Kangarooo> BlackZ: i have programm in Applications->settings called 3d acceleration i want to remove it
[16:24] <BlackZ> Kangarooo: maybe they're the driver for your video card, however the support is in #ubuntu
[16:25] <Kangarooo> its not opening since i put another videocard and installed restricted nvidia driver and i think maybe that programm is cousing all screen to respond slow
[16:25] <xelister> hggdh: want to dig into horryfiing sources? ;) find out why "retty" application is packaged only for 32 bit mode (from sources) =)
[16:26] <BlackZ> s/driver/driver panel settings
[16:26] <hggdh> xelister: without looking I would say because it FTBFS on amd64 ;-)
[16:28] <ddecator> hggdh: will you be on to talk to kermiac and myself at 1300 UTC on Thursday?
[16:28] <hggdh> ddecator: yes, I will
[16:28] <ddecator> hggdh: alright, that's when we plan to both be on :)
[16:29] <hggdh> ddecator: cool, thanks. It will be easy, all we need is a major change in apport
[16:29] <hggdh> :-)
[16:29] <ddecator> no big deal :p
[16:29] <xelister> hggdh: sort of, but its more funny/horryfing. Took me  <1 minute to find out after getting http://archive.ubuntu.com/ubuntu/pool/universe/r/retty/retty_1.0.orig.tar.gz
[16:30] <hggdh> xelister: so I guess you can propose a debdiff to correct it...
[16:31] <hggdh> xelister: but keep in mind that "builds on amd64" is not the same as "works on amd64"
[16:32] <Kangarooo> https://wiki.ubuntu.com/DebuggingProgramCrash what in there means ~i in aptitude search '~i' | fgrep -e '-dbg' ? i run this command and it doesnt give anything
[16:34] <PrototypeX29A> does anybody know what attachments with the ending .eml are supposed to mean?
[16:34] <PrototypeX29A> they seem to correlate with my bug, but i don't know how to test it
[16:35] <hggdh> PrototypeX29A: an RFC822 email message
[16:36] <xelister> hggdh: no, I can't. look into the source for a lol =)
[16:36] <xelister> probably noone cam
[16:36] <xelister> can
[16:38] <hggdh> xelister: heh. There you go...
[16:39] <hggdh> xelister: but retty would be superceeded by byobu (or screen)
[16:40] <xelister> yea but only retty is able to attach TTY to *LOST* processes (that lost tty, and where NOT started inside screen etc
[16:40] <xelister> but.. look how the retty program does that..
[16:40] <xelister> I looked at the source... and..
[16:40] <xelister> oh my dear god.. WTF
[16:40] <xelister> the language.... the way they "attach" it... the NX bit... the architectures.. OH DEAR GOD its so wrong on so many levels =)
[16:42] <hggdh> :-) so... we are back on always running byobu. Or re-wrting retty (and I agree there *is* usage for it)
[16:45] <hggdh> xelister: looked at the code. I very much doubt I would allow retty to be installed on machines I were to be a sysadmin
[16:47] <xelister> yeap. it would not run on any modern system probably =)
[16:47] <xelister> it would be nice if kernel would reimplenet simply real rettry instead of such hackery
[16:48] <PrototypeX29A> what happens to a bug in say karmic, when it turns out that the problem is fixed upstream?
[16:49] <ddecator> PrototypeX29A: wait for it to work its way downstream and hope it does fix the problem :)
[16:49] <micahg> !sru | PrototypeX29A
[16:49] <ubot2> PrototypeX29A: Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[16:49] <PrototypeX29A> ah thx
[16:51] <PrototypeX29A> so if it is not considered a "high-impact bug" i am doomed
[16:53] <hggdh> PrototypeX29A: not necessarily. "high-impact" has many forms; also, you can always build your own (cherry-pick the upstream fix, and add it in)
[16:53] <PrototypeX29A> sounds good
[16:54] <hggdh> also, every so often I do build an Evo with an upstream fix (when upstream asks me to, usually)
[17:53] <xelister> hggdh: I would guess, only clean way to do retty rewrite would be to make nesesary libc function / kernel syscall? to nativly/nicelly do retty'ing of a process, instead of this hackery attempted by current retty ;)
[17:53] <PrototypeX29A> i found some bugs upstream which match my bug, but i am not sure wether everyone would agree that it is the same bug
[17:54] <PrototypeX29A> so is it better to open a new bug upstream?
[17:54] <hggdh> PrototypeX29A: if in doubt, yes, a new bug is better
[17:55] <PrototypeX29A> actually i am not in doubt, but someone may be :)
[17:56] <PrototypeX29A> nobody is trusting my wisdom
[17:57] <hggdh> PrototypeX29A: OK. Give me your UBuntu bug, and some potential matches upstream
[17:58] <PrototypeX29A> https://bugs.launchpad.net/evolution/+bug/585375
[17:58] <ubot2> Launchpad bug 585375 in evolution (Ubuntu) (and 1 other project) "Mail filters occasionally do not work (affects: 1) (heat: 8)" [Low,New]
[17:58] <PrototypeX29A> https://bugzilla.gnome.org/show_bug.cgi?id=350323
[17:58] <ubot2> Gnome bug 350323 in Mailer "Filter by "Mailing list contains" requires "@" symbol" [Minor,Unconfirmed]
[17:59] <PrototypeX29A> no this one is actually better: https://bugzilla.gnome.org/show_bug.cgi?id=346855
[17:59] <ubot2> Gnome bug 346855 in Mailer "mail filtering in evolution is not perfect" [Normal,Unconfirmed]
[18:01] <PrototypeX29A> unconfirmed since 2006
[18:03] <PrototypeX29A> hggdh: with the first bug i really don't get the developer's relpy
[18:04] <hggdh> PrototypeX29A: sounds a match for gnome 346855
[18:05] <ubot2> Gnome bug 346855 in Mailer "mail filtering in evolution is not perfect" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=346855
[18:05] <hggdh> so yes, you can use this one (and update the upstream bug for current version)
[18:05] <PrototypeX29A> ok
[18:06] <hggdh> PrototypeX29A: fejj was stating that this field should be pre-filled, and not manually edited
[18:06]  * hggdh does not remember how it is now... will have to check
[18:14] <PrototypeX29A> this time i have problems reporting it upstream. I click on "Also affects project" in launchpad and get to a form which asks me for the name of the Project (there does not seem to be a relationship to gnome established before)
[18:17] <PrototypeX29A> i then enter 'evolution' and i get the error: A fix for this bug has already been requested for Evolution
[18:18] <PrototypeX29A> i must say, that i don't find LaunchPad easy to use
[18:18] <hggdh> PrototypeX29A: I see an upstream Evolution task there
[18:18] <PrototypeX29A> where?
[18:19] <hggdh> on bug 585375
[18:19] <ubot2> Launchpad bug 585375 in evolution (Ubuntu) (and 1 other project) "Mail filters occasionally do not work (affects: 1) (heat: 8)" [Low,New] https://launchpad.net/bugs/585375
[18:20] <PrototypeX29A> then i am using a wrong link
[18:20] <hggdh> an upstream task had already been added, all you need to do is edit it (the small down triangle on its left) and add the link for the Gnome bug
[18:20] <PrototypeX29A> https://bugs.launchpad.net/evolution/+bug/585375
[18:20] <ubot2> Launchpad bug 585375 in evolution (Ubuntu) (and 1 other project) "Mail filters occasionally do not work (affects: 1) (heat: 8)" [Low,New]
[18:21] <hggdh> PrototypeX29A: see the "(and 1 other project)"? This is the upstream Evo task
[18:21] <PrototypeX29A> i am very confused now, i happen to get different views on this bug
[18:22] <hggdh> ?
[18:22] <PrototypeX29A> sometimes i see two projects, sometimes only one. I don't know
[18:23] <bcurtiswx> pedro_: are you done editing the contacts page?
[18:25] <PrototypeX29A> now i happen to see two entries on being 'Evolution' and one being 'evolution (Ubuntu)', opening the first one i can enter a remote watch URL. Is that meant to get the upstream link?
[18:25] <hggdh> PrototypeX29A: this is indeed weird, given that -- for this bug -- I always see the two projects/tasks
[18:26] <PrototypeX29A> i don't know. I have just provided an upsteam link for another evolution bug, it was completely without any obstacles
[18:26] <hggdh> PrototypeX29A: you are correct. The "Evolution(Ubuntu)" is our task (local to Ubuntu), and "Evolution" is the upstream one
[18:27] <hggdh> PrototypeX29A: most probably because this other bug did not yet have an upstream task opened for it
[18:27] <PrototypeX29A> so i just select URL at Remote Watch and enter the URL of the gnome-bug?
[18:27] <hggdh> correct
[18:28] <PrototypeX29A> i still am confused, but it should be done
[18:28] <hggdh> and then -- to be complete -- you go to the upstream bug and update it with the Ubuntu bug link, and also update the versions affected
[18:28] <PrototypeX29A> ok
[18:28] <hggdh> checking
[18:28] <PrototypeX29A> what do you mean with versions affected?
[18:29] <PrototypeX29A> that is an entry in the upstream tracker?
[18:30] <hggdh> it is, but I am not sure you would have access. I will do it
[18:31] <PrototypeX29A> it seems that i do not
[18:32] <hggdh> PrototypeX29A: done. Please refresh, and look at the right side, near the top. It is now set as Evo 2.28.x. At the bottom you can see it again, together with the Gnome version
[18:32] <hggdh> which I also updated
[18:34] <PrototypeX29A> is 2.28 the same as 2.8?
[18:35] <hggdh> PrototypeX29A: no, it is not. 2.8 is obsolete...
[18:35] <PrototypeX29A> you just changed to version to 2.8.x
[18:35] <hggdh> ARGHHH!
[18:36] <PrototypeX29A> good, i thought this whole bugtracking thing was only driving me insane
[18:37] <hggdh> PrototypeX29A: corrected. Thank you :-)
[18:37] <PrototypeX29A> good thanks
[18:38] <PrototypeX29A> i'll leave for a bottle of mate, cu
[18:38] <hggdh> PrototypeX29A: tahnk you for the patience
[18:39] <PrototypeX29A> i intend to get my bug score much higher
[18:39] <bcurtiswx> PrototypeX29A: it's not a competition, tho
[18:39] <PrototypeX29A> as soon as i have 30 open bugs, i can prove that linux is buggy :)
[18:39] <PrototypeX29A> bcurtiswx: it motivates :)
[18:40] <PrototypeX29A> if i loose and end up with a working system it is a nice solace
[18:40] <PrototypeX29A> lose
[18:42] <skybon> hi all
[18:43] <skybon> why can't I while being a member of BugSquad triage bugs?
[18:43] <hggdh> skybon: I am not sure I follow you
[18:44] <skybon> ?
[18:44] <hggdh> skybon: and, BTW, welcome ;-)
[18:44] <skybon> thanks
[18:44] <hggdh> skybon: "why can't I while being a member of Bugsquad triage bugs?" <- what do you mean?
[18:47] <skybon> I can't set the status of a bug to triaged despite my membership in BugSquad
[18:47] <skybon> as well as Won't Fix
[18:47] <skybon> idk why, maybe a bug?
[18:48] <hggdh> skybon: indeed. These stati require bug-control membership (given they have been abused again and again)
[18:49] <skybon> ermmm well, ok
[18:49] <hggdh> so -- while you acquire experience to apply to bug-control, please ask here for Importance and status change to Triaged
[18:49] <hggdh> and we will be more than happy to do it
[18:49] <skybon> ok, I get it
[18:50] <skybon> thanks again :)
[18:51] <hggdh> for wontfix... a bit more complex, unless you are an upstream developer for the package
[18:55] <hggdh> or, of course, a maintainer for the specific Ubuntu package
[19:13] <pedro_> bcurtiswx, i was editing that yesterday,  the wiki says i'm still doing that?
[19:14] <bcurtiswx> pedro_: i got the e-mail about changes.. looked and didn't see me on there... thought i was supposed to be
[19:15] <bcurtiswx> pedro_: but in case im not, wanted to verify
[19:15] <pedro_> bcurtiswx, you mean https://wiki.ubuntu.com/BugSquad/Contacts/List ? feel free to add yourself there ;-)
[19:16] <pedro_> bcurtiswx, i just moved that from Contacts to Contacts/List and update the list to include that in the Adopt a package one
[19:16] <bcurtiswx> pedro_: Ah ok, thx :D
[19:16] <pedro_> you're welcome ;-)
[19:19] <bilalakhtar> Hi triagers! Whatis the number of bugs one should try to triage before joining bugcontrol?
[19:19] <hggdh> bilalakhtar: it is not really a question of number of bugs, but rather of quality of work
[19:19] <bilalakhtar> hggdh: ok
[19:20] <hggdh> bilalakhtar: usually a month to 2 months of consistent triage is enough
[19:20] <bilalakhtar> hggdh: ok
[19:21] <bilalakhtar> om26er: Hi there! I have recently commented (again) on your bug, see that
[19:25] <om26er> bilalakhtar, the recent upload to totem only contained the patch to avoid it from crashing on start
[19:29] <om26er> a bug should be converted from regression-potential to regression-release what if a bug was found after the release and is a regression?
[19:29] <hggdh> om26er: correct
[19:29] <bilalakhtar> om26er: so this is a bug in totem. fine
[19:30] <om26er> bug 573845
[19:30] <ubot2> Launchpad bug 573845 in telepathy-gabble (Ubuntu) (and 1 other project) "gtalk video calls wont broadcast my video (works in debian) (affects: 4) (dups: 2) (heat: 40)" [Medium,Triaged] https://launchpad.net/bugs/573845
[19:30] <om26er> hggdh, the tag would be 'regression' ?
[19:30] <bilalakhtar> how do I remove a bug "affects <blah blah>" link
[19:31] <hggdh> you don't... but you can set it INVALID (and explain why)
[19:32] <hggdh> I mean -- if this is a task. If it is just an upstream link, delete it
[19:32] <bilalakhtar> om26er: BTW, how are you using maverick? where did you get an experimental build?
[19:33] <om26er> bilalakhtar, used update manager
[19:33] <bilalakhtar> om26er: oh yeah
[19:33] <hggdh> sudo do-release-upadte -d, or equivalent
[19:33] <bilalakhtar> om26er: you are a real tester
[19:33] <bilalakhtar> update-manager -d
[19:34] <om26er> bilalakhtar, http://www.webupd8.org/2010/05/how-to-upgrade-to-ubuntu-1010-maverick.html
[19:34] <PrototypeX29A> re
[19:35] <bilalakhtar> om26er: how much did you have to download to get maverick?
[19:35] <om26er> bilalakhtar, 200mb here
[19:35] <om26er> ~
[19:36] <bilalakhtar> om26er: How much is it different from lucid?
[19:36] <bilalakhtar> right now, barely any difference
[19:37] <hggdh> om26er: regression-release
[19:38] <om26er> hggdh, thanks done :)
[19:38] <chilicuil> hi, I'm working on this bug #519787 someone has suggested me to merge it with the debian package, the bug was fixed in the 0.15.6 version but the last package in the debian repositories is the .15.9 version, should I merge against the .15.6 version or against the .15.9?
[19:38] <ubot2> Launchpad bug 519787 in mpd (Debian) (and 1 other project) "mpd: segfault when trying to play a m4a (AAC-LC) file (affects: 7) (heat: 38)" [Unknown,Unknown] https://launchpad.net/bugs/519787
[19:39] <bilalakhtar> om26er: is maverick stable for you right now?
[19:39] <mvo> om26er: btw, setting "release-upgrades" to "normal" (instead of lts) and update-manager -d should work now too
[19:40] <mvo> (setting that in software-properties-gtk)
[19:40] <om26er> bilalakhtar, not exactly disk usage sometimes becomes crazy
[19:43] <hggdh> chilicuil: which version do we have on Lucid and Maverick?
[19:43] <bilalakhtar> om26er: disk usage means maverick is using a lot of disk space?
[19:44] <om26er> bilalakhtar, no, the disk activity, it makes me kill X every 1hour and we should be in #ubuntu+1 ;)
[19:44] <chilicuil> hggdh, 0.15.4
[19:45] <hggdh> chilicuil: on both Lucid and Maverick?
[19:45] <chilicuil> yep, hggdh
[19:46] <hggdh> OK. depending of which version will be synch-ed from Debian, you would add it there
[19:46] <hggdh> (if not already in -- e.g., if we sync 0.15.9)
[19:46] <hggdh> then you would propose a SRU for Lucid (and port the fix to 0.15.4)
[19:48] <hggdh> bilalakhtar: Maverick is far from stable right now... so caveat emptor
[19:48] <bilalakhtar> hggdh: I meant to ask is maverick stable enough to use? or it crashes like windoes?
[19:49] <hggdh> bilalakhtar: it may, or may not, depending on what changes have been already done *and* on your hardware
[19:49] <hggdh> bilalakhtar: for example, on the Lucid cycle I had 3 critical failures
[19:49] <bilalakhtar> hggdh: Which ones?
[19:50] <hggdh> xserver, disc recognition on boot, and the root FS failing completely
[19:50] <bilalakhtar> hggdh: Ok, I hafta go. cya
[19:50] <chilicuil> I found in MoM that it has been merged automatically ( https://merges.ubuntu.com/m/mpd/ ), so I think I should merge it manually against the 0.15.9 and then add the patch to the lucid one?, am I right?
[19:51] <hggdh> chilicuil: sounds like a plan
[19:51] <chilicuil> ok, hggdh, thx
[19:58] <Kangarooo> i want to try to resolve problem/report a bug about video card driver. where should i post it? to what package? ubuntu:xorg ?
[20:00] <PrototypeX29A> the driver should be part of the kernel i think
[20:06] <Kangarooo> PrototypeX29A: problem is that i put geforce 5500 (its old) but when starting splash screen is in max quality also tty1-6 are high quality/resolution and windows are opening and closing fast on minimize/maximize but when i in System->hardware drivers put latest driver and restarted i get in glxgears even 5000fps but splash screen is in very bad resolution and available resolutions are less and max mhz are less and tty1-6 are in low resolution and minimiz
[20:08] <Kangarooo> very long line.. was i cut somewhere? last word in that line was :"slow" and also not 5000fps but about 2500fps (yeah wow. i dont know how)
[20:09] <stenten> Kangarooo: is it a bug with the open-source driver or nVidia's proprietary driver?
[20:09] <charlie-tca> That is a know issue. nvidia and kms
[20:10] <Kangarooo> i dont know. that what i want to know so i could write bug and that is fixed (or at least that this computer can be usable couse when activated hardware driver then minimize maximize and everything is sloooow)
[20:11] <charlie-tca> https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#Working%20around%20bugs%20in%20the%20new%20kernel%20video%20architecture
[20:11] <Kangarooo> stenten: so since i activated in hardware then its nvidia also here in nvidia i see the same driver version nr 173 http://www.zimagez.com/zimage/screenshot705.php
[20:12] <stenten> charlie-tca: shouldn't KMS already be off because it's using nvidia-current, not nouveau?
[20:13] <charlie-tca> no, it still makes the splash screen look like an old vga screen, and messes with the other stuff depending on the card
[20:13] <charlie-tca> There are at least three bugs for it already
[20:13] <charlie-tca> it is the nvidia hardware driver causing the ugly stuff
[20:14] <Kangarooo> charlie-tca: ive just made about 5 screenshots about what is possible with/without nvidia and fps rates with glx-gears i can post that all but to witch package? and should i do thrue web in LP or with ubuntu-bgug ?
[20:15] <charlie-tca> Please don't. It is a known issue with bugs on file
[20:15] <Kangarooo> ah ok. i thought maybe very interesting would be seeing 2500 fps
[20:15] <Kangarooo> but will this be fixed or should i take olde card?
[20:16] <skybon> someone from bug-control please mark bug #103791 as Triaged
[20:16] <ubot2> Launchpad bug 103791 in debian (and 1 other project) "[needs-packaging] pcsx2 (affects: 5) (dups: 1) (heat: 56)" [Unknown,New] https://launchpad.net/bugs/103791
[20:16] <charlie-tca> I don't know if/when this will be fixed.
[20:17] <charlie-tca> Kangarooo: here is the ugly splash screen bug - https://launchpad.net/bugs/552000
[20:17] <ubot2> Launchpad bug 552000 in xubuntu-artwork (Ubuntu) "xubuntu logo in plymouth splash screen looks like it has spider webs in it (affects: 3) (heat: 18)" [Medium,Triaged]
[20:17] <charlie-tca> There are two more referenced in the release notes that I gave you
[20:48] <Darxus> Can somebody unmark this as a duplicate?  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/582564  I incorrectly marked it, and don't seem to have the ability to undo it.
[20:48] <ubot2> Launchpad bug 582564 in xorg-server (Ubuntu) "X keeps crashing in Lucid (dup-of: 584655)" [Undecided,Confirmed]
[20:48] <ubot2> Launchpad bug 584655 in xorg-server (Ubuntu) "Xorg crashed: Failed to submit batchbuffer: No space left on device (affects: 2) (dups: 1) (heat: 20)" [Undecided,Confirmed]
[20:51] <Kangarooo> Darxus: u cant un dublicate it?
[20:58] <charlie-tca> Darxus: done. All you have to do is click on the little yellow circle with a pencil. that lets you erase the duplicate number
[21:07] <skybon> someone please mark bug #103791 as triaged
[21:07] <ubot2> Launchpad bug 103791 in debian (and 1 other project) "[needs-packaging] pcsx2 (affects: 5) (dups: 1) (heat: 56)" [Unknown,New] https://launchpad.net/bugs/103791
[21:22] <Darxus> charlie-tca: Sweet, thanks.
[21:23] <bcurtiswx> anyone know what an exit status 245 on dpkg means?
[21:23] <bcurtiswx> reference bug #577122
[21:23] <ubot2> Launchpad bug 577122 in empathy (Ubuntu) "can't remove empathy package (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/577122
[21:24] <Darxus> Since firefox and chrome are frequently crashing X, can you recommend a different browser in the ubuntu archives?  Ephiphany?
[21:25] <Darxus> Yeah, that looks like the option.
[21:27] <charlie-tca> On the chance of getting heavily bombed, I recommend 'midori'
[21:28] <hggdh> heh
[21:31] <micahg> did I miss the what's your favorite browser session?
[21:31] <hggdh> guess you did, by a few :-)
[21:34] <Hamra> guess i missed it too.... by what margin did internet explorer beat the rest? :P
[21:39]  * bcurtiswx hugs opera
[21:40] <charlie-tca> and then he runs away!
[21:50] <skybon> someone please mark bugs #103791 and #113183 as triaged
[21:50] <ubot2> Launchpad bug 103791 in debian (and 1 other project) "[needs-packaging] pcsx2 (affects: 5) (dups: 1) (heat: 56)" [Unknown,New] https://launchpad.net/bugs/103791
[21:50] <ubot2> Launchpad bug 113183 in ubuntu (and 2 other projects) "[needs-packaging] QJoyPad (affects: 2) (heat: 14)" [Wishlist,New] https://launchpad.net/bugs/113183
[22:30] <LinuxGuy2009> I was here the other day about an Intel graphics chip that Lucid doesn't work well with and I read here https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes that I can switch this PC to VESA by copying and pasting to /etc/X11/xorg.conf I just looked for that file and it doesn't exist in that folder. Does this mean I need to create it?
[22:32] <Hamra> yes. as of Hardy, ubuntu has been using a "bullet proof X", an X that can auto configure itself even if no xorg.conf exists
[22:32] <LinuxGuy2009> Ok cool. Thank you.
[22:32] <Hamra> but of course, having the file around helps setting the system better, and specifying exactly how we want X to act
[22:33] <LinuxGuy2009> Hamra: Thanks very much i apreciate the advice.
[22:33] <Hamra> you're welcome
[22:37] <LinuxGuy2009> Hamra: I just saved the file and rebooted and it came up to a black screen right off the bat. Any ideas how I can resolve this?
[22:38] <LinuxGuy2009> Suposed to fix 100% of this issue but not so far.
[22:38] <Hamra> hmmm... seems like this xorg.conf file doesn't configure X properly, if you click CTRL+ALT+F1, do you get a console login?
[22:38] <LinuxGuy2009> No
[22:38] <LinuxGuy2009> Oh wait
[22:38] <LinuxGuy2009> 1 sec
[22:38] <wise_crypt> https://bugs.launchpad.net/ubuntu/lucid/+source/mountall/+bug/559582 << how to solve this ?
[22:38] <ubot2> Launchpad bug 559582 in initramfs-tools (Ubuntu Lucid) (and 3 other projects) "Upgrade from karmic to lucid failes with Internal Error, Could not perform immediate configuration (2) on mountall (affects: 18) (dups: 1) (heat: 110)" [Undecided,Fix released]
[22:39] <LinuxGuy2009> Hamra: Nope, no console
[22:40] <Hamra> ok, try rebooting into recovery option
[22:40] <LinuxGuy2009> ok
[22:40] <LinuxGuy2009> Hamra: How do I do that?
[22:40] <Hamra> when the computer starts, do you see a grub menu with options of kernel choices?
[22:41] <LinuxGuy2009> No do i need to press shift to get that first?
[22:41] <LinuxGuy2009> or something like that?
[22:42] <Hamra> after your motherboard logo disappears, you should either see the menu, or a blank screen for a few seconds. if blank screen, click ESC to get the grub menu
[22:42] <LinuxGuy2009> ok
[22:42] <LinuxGuy2009> 1 sec (its in the other room)
[22:44] <LinuxGuy2009> Hamra: Esc didnt bring anything up.
[22:44] <Hamra> the system just went straight into booting?
[22:45] <LinuxGuy2009> Hamra:  Appears that way.
[22:45] <Hamra> do ALT+F1 or ALT+F2 do anything, while in this black screen now?
[22:47] <LinuxGuy2009> Ill try
[22:48] <LinuxGuy2009> Hamra: No nothing. I'm guessing Ill have to use the live CD to erase the xorg.conf and try another solution so my parents have a working machine without the display blacking out every 5 minutes. Jaunty runs fun on there machine.
[22:49] <LinuxGuy2009> Strange
[22:50] <Hamra> does their PC have same graphics controller? intel?
[22:50] <LinuxGuy2009> Hamra: It has an Intel i845
[22:50] <Hamra> and you?
[22:51] <LinuxGuy2009> Im on my custom built machine with nvidia 9800GTX+
[22:52] <LinuxGuy2009> There PC is an IBM.
[22:53] <Hamra> is jaunty still available on the intel machine? or was it removed during the installation of lucid?
[22:54] <LinuxGuy2009> I did a clean lucid install. But I still have the Jaunty live CD to reinstall if I have to.
[22:58] <LinuxGuy2009> Hamra: Do you think I should just reinstall Jaunty and just keep an eye on this bug and maybe retry it on there machine after its been fixed? Perhaps hopefully by 10.04.1.
[22:59] <Hamra> it really is up to you, and if the problem is fixable. i was hoping if jaunty was still installed, to see if it has a xorg.conf file and copy it
[23:00] <Darxus> (WW) Ignoring unrecognized extension "glx" / (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[23:00] <LinuxGuy2009> Hamra: Not sure Ive never really messed with xorg and al that. Never had to till now.
[23:00] <Darxus> This is frustrating.
[23:00] <LinuxGuy2009> I guess Ill just reinstall Jaunty.
[23:00] <Hamra> i have a nvidia geforce 8500 here, and it sure is hell to configure everytime. i've been copying and using same xorg.conf for 2 years now...
[23:00] <Darxus> LinuxGuy2009: I should probably try that.
[23:00] <LinuxGuy2009> Hamra: Really?
[23:01] <LinuxGuy2009> Hamra: Was 8500 an odd model or something?
[23:02] <Hamra> not really, but the constant changing of how ubuntu deals with nvidia is frustrating. from nv, to defaulting on VESA one time, and now nouveau in lucid
[23:02] <Darxus> Yeah ubuntu really has gotten pretty magical about video card configuration in recent years.
[23:02] <Darxus> I'm *very* happy with how ubuntu currently handles nvidia.
[23:02] <LinuxGuy2009> Darxus: Yeah me too. My 9800GTX+ works great
[23:03] <Darxus> The transition from no magic to magic was a bit rough.  But since then it's been great.
[23:04] <Darxus> Conflicts with the third party magic.
[23:04] <LinuxGuy2009> Well I guess Jaunty is going back on and Ill wait for 10.04.1 and hope this Intel graphics issue is fixed.
[23:04] <LinuxGuy2009> Hamra: Thank You!
[23:05] <Darxus> LinuxGuy2009: Oh, you have an intel issue too?
[23:05] <LinuxGuy2009> Darxus: Yeah you too?
[23:05] <Darxus> That's what's currently driving me mad.  Damn thing keeps hanging.
[23:05] <LinuxGuy2009> Darxus: Black screen like every 5 minutes?
[23:05] <Darxus> No, mostly black with graphical... errors.
[23:05] <Darxus> There are two relevant bugs open.
[23:06] <LinuxGuy2009> Darxus: What model card do you have? My parents is a i845
[23:06] <Darxus> 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
[23:07] <LinuxGuy2009> Darxus: Looks like the same card 845
[23:07] <Darxus> LinuxGuy2009: Are you getting hangs, crashes, or occasional black screens?
[23:07] <LinuxGuy2009> Darxus: Black screens
[23:07] <Darxus> Hah.
[23:07] <LinuxGuy2009> Darxus: Non recoverable it seems.
[23:07] <Darxus> Ah, then it's probably the same as mine.
[23:07] <Darxus> Let me get you a url...
[23:08] <LinuxGuy2009> Cool
[23:08] <LinuxGuy2009> Bug #541492 I have
[23:08] <ubot2> Launchpad bug 541492 in xserver-xorg-video-intel (Ubuntu Lucid) (and 2 other projects) "MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) (affects: 41) (dups: 22) (heat: 368)" [High,Triaged] https://launchpad.net/bugs/541492
[23:08] <LinuxGuy2009> Pretty serious bug
[23:09] <Darxus> Bug #582564
[23:09] <ubot2> Launchpad bug 582564 in xorg-server (Ubuntu) "X keeps crashing in Lucid (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/582564
[23:09] <Darxus> LinuxGuy2009: For me it seems to always been when I'm using a web browser, all three I've tried.
[23:10] <Darxus> LinuxGuy2009: Looks like yours has much more useful info, thanks.
[23:10] <LinuxGuy2009>  LinuxGuy2009: Yeah same here. Firefox and Chromium both we have tried. No other apps seem to do it.
[23:10] <LinuxGuy2009>  LinuxGuy2009: Oh cool
[23:10] <Darxus> The other one I tried was Epiphany.
[23:11] <LinuxGuy2009>  LinuxGuy2009: I didnt try that one.
[23:11] <LinuxGuy2009>  LinuxGuy2009: I wonder if opera does it
[23:11] <Darxus> LinuxGuy2009: Did you try the backported package from gomyhr's ppa?
[23:12] <LinuxGuy2009>  LinuxGuy2009: Backported what package?
[23:12] <Darxus> Eh, read the beginning of the page of that bug you mentioned :P
[23:12] <Darxus> "There is now a potential fix upstream. A driver package with the              backported fix is available in the PPA                                        https://launchpad.net/~gomyhr/+archive/standard
[23:12] <Darxus> "
[23:13] <Darxus> "...or fails in a completely new and exciting way."  Awesome.
[23:13] <LinuxGuy2009>  LinuxGuy2009: hehe
[23:15] <LinuxGuy2009> Darxus: I might have tried that the other day. I think that package is older than the current one.
[23:15] <Darxus> (II) intel(0): Integrated Graphics Chipset: Intel(R) 845G
[23:15] <Darxus> LinuxGuy2009: Ah, bummer.
[23:17] <LinuxGuy2009> Darxus: Im just throwing Jaunt back on it. Not even gonna try  Karmic again.
[23:18] <LinuxGuy2009> Darxus: What do you plan to do?
[23:18] <Darxus> LinuxGuy2009: Don't know yet.  Jaunty is tempting.
[23:19] <Darxus> Still need to read up more on the current state of the problem.
[23:19] <Darxus> Yeah, the version in the archives is newer.
[23:19] <Darxus> Than the ppa.
[23:21] <Darxus> LinuxGuy2009: Did you subscribe to the upstream bug?
[23:22] <Darxus> Ugh, links seems to be failing to handle logins.
[23:41] <Darxus> So this video card was blacklisted from acceleration in Jaunty and that's what kept it from crashing?
[23:53] <maco> :((( i cant mark a bug as affecting debian
[23:53] <maco> clicking "also affects project" tells me "debian" doesnt exist in lp (it does: http://launchpad.net/debian) and searching on their for debian says too many results
[23:54] <micahg> maco: also affects distro
[23:54] <maco> and clicking "also affects distro" and choosing debian from the dropdown then giving it the url to the debian bug, it yells at me about not including the optional (!!!) package name. and when i try "wnpp" as the package name, lp tells me no such thing exists. :(
[23:54] <micahg> maco: what bug?
[23:55] <maco> lp 113183  and bts 564503
[23:55] <ubot2> Launchpad bug 113183 in debian (and 3 other projects) "[needs-packaging] QJoyPad (affects: 3) (heat: 20)" [Undecided,New] https://launchpad.net/bugs/113183
[23:55] <maco> wait what
[23:55] <maco> rawr this is confusing!
[23:55] <dado55> can somebody help with ubuntu freezing on install?
[23:55] <maco> so does that mean it worked the time i tried doing it through email but then decided it just wasnt going to update the web interface to reflect that?
[23:55] <micahg> maco: it seems you got the affecting, just add the URL now
[23:56] <micahg> maco: possibly by the time you got to the web interface, the email changes took effect
[23:58] <micahg> maco: I see there's a bug comment 'affects debian'