[00:06] anyone home? [00:24] hello? [00:25] klutzierthanmost: hello [00:25] klutzierthanmost: do you need some help? [00:28] I understand you like input on bugs? [00:31] yes? [00:31] Has anyone reported Brasero not working after ugrading to 9.04? [00:33] klutzierthanmost, I do not know. A search on launchpad for brasero might answer it [00:34] ok.. onward to launchpad. Thanks === savvas_ is now known as savvas [01:54] anyone here use UNR ? [02:04] Hia, I'm considering marking https://bugs.launchpad.net/ubuntu/+source/linux/+bug/299865 as a dube of https://bugs.launchpad.net/ubuntu/+bug/305724, and adding linux and linux (ubuntu) as affecting the latter one, am I right in this procedure? [02:04] Launchpad bug 299865 in linux "sata failed to set xfermode" [Undecided,New] [02:55] Hi all [02:58] Hi all [02:58] I'm new here and want to help [06:33] Can someone look at bug 293362 for me [06:33] Launchpad bug 293362 in firefox-3.0 "ubuntu 8.04 amd64 - Java applet loop: openjdk-6 icedtea6-plugin Firefox" [Undecided,New] https://launchpad.net/bugs/293362 [06:34] I tested with the sun java plugin and did not have an issue [06:35] ugh, neverming [06:35] I have a different version of Java anyways [06:37] here's one, if a person's assigned to a bug, the status shouldn't be new, right? [06:38] micahg, Sometimes that's a valid model. [06:38] persia: can you clarify pleasE? [06:38] For instance, when a bug is mostly irreproducible, but someone is claiming it because they can reproduce (e.g. on specialised hardware), and are collecting additional details. [06:38] so, that's assigned, but new? [06:38] not incomplete === savvas is now known as medigeek [06:39] or in progress? [06:39] Or when someone finds something, and is working on it, but nobody else has yet confirmed the issue (by the don't-confirm-your-own-bugs rule) === medigeek is now known as savvas [06:39] Well, arguably, it ought be "incomplete" or "in-progress". I think you're right. [06:39] ok, but still, shouldn't that be in progress so people know [06:39] here's my bug problem [06:39] bug 294652 [06:39] Launchpad bug 294652 in firefox-3.0 "Default 8.10 homepage searches wrong google" [Undecided,New] https://launchpad.net/bugs/294652 [06:40] the assignee was asked to reclassify the bug [06:40] Oh, I've encountered that bug. [06:40] that shouldn't be in progress? [06:41] No. That's a somewhat special case. [06:41] ok [06:41] The bug is a bug in http://start.ubuntu.com/8.10 rather than in firefox. [06:41] I've only been doing this a week, so I'm still earning [06:41] ah [06:41] it's a problem witht he site [06:41] It's not clear which project hosts that web page, but the person setting the assignment has some information that indicates the assignee might know where it belongs. [06:42] (the assignee probably said "assign that to me" in an IRC chat) [06:42] I've tried to adopt ff as my bug project to triage [06:42] So, the assignee will probably move it, and then it will follow other processes. [06:42] since it's so out of control [06:42] well [06:42] bad wording [06:42] not out of control [06:42] bugs rising beyond ability to triage [06:42] maybe that's better [06:43] Right. It's a special case. It oughtn't be in that state for long, because it should move away from being against "Firefox" and be against whatever actually handles that page. [06:43] I try to go after everything classified as new [06:43] Well, out of control of those working on firefox (or Ubuntu), at least. [06:43] a little at a time [06:43] heh [06:43] I think I've done about 50 in the past week [06:43] It's been in this state for several months: you might want to contact the assignee and ask if the bug will be updated. [06:44] Cool! [06:44] hggdh: can you be my bug mentor? [06:44] micahg: yes, not probs [06:44] ok [06:44] I was wondering [06:44] s/not/no/ [06:44] We're doing bug mentors now? I always preferred the "ask the channel" model. [06:44] what about combining all the compiz/FF problems into one bug [06:44] there seem to be a lot of them [06:45] persia, I guess both are good [06:45] Same scenario over and over, user starts FF and it's maximized [06:45] user needs to hit F11 twice to get the titlebat back [06:45] *titlebar [06:46] micahg: putting all compiz/ff into one master sounds nice, but... we have to be sure they are all the same issue [06:48] anyway. it's almost 0100 now here. Time to fight the pillow. G'night all y'all [06:48] night [06:52] can I mark bug 349970 and bug 329604 as dupes? [06:52] Launchpad bug 349970 in firefox-3.0 "no minimize maximize or exit in ff" [Undecided,New] https://launchpad.net/bugs/349970 [06:52] Launchpad bug 329604 in firefox-3.0 "It will automatically maximize when it open, and the close column can not be find. Required by F11 twice before returning to normal" [Undecided,New] https://launchpad.net/bugs/329604 [06:53] sigh. I am done with pidgin. Cannot stand the beast :-( [06:53] triaging or using? [06:53] using. be back in a few, unde xchat [06:55] ah, much better. [06:55] ok [06:55] can you check the dupes for me? [06:55] who, me? [06:55] yes, sorry [06:56] can it be tomorrow (er, much later today)? [06:56] sure [06:56] Is there a way for me to mark bugs to look at later? [06:57] yes: piece of paper, and a pencil ;-) [06:58] I'll use vim instead :0 [06:59] I also have to go to bed soon [07:00] I used to use a desktop stickies program, and just copy&paste URLs there. This didn't end up scaling well (I have too many bugs), but it was very helpful for keeping track of things when reviewing a couple hundred bugs quickly. [07:01] tried using something like that, but ended up using real stickies instead... [07:03] ah, would you guys find a watch bug feature useful? [07:03] not subscribe so you get e-mails [07:03] but, just a place to collect a list of ones to watch [07:11] actually, no. Subscription meets that need for me. It's rare I want to watch a bug for longer than a week and wouldn't want to be subscribed. [07:15] good morning [07:18] ok [07:18] good night for real === stooj is now known as StooJ|Away [07:59] Feedback on escalating bug #330298 from medium to large? While there is a rather trivial work around, it is still rather nasty suprise to experience when you upgrade. [07:59] Launchpad bug 330298 in mdadm "mdadm software raid breaks on intrepid-jaunty upgrade" [Medium,Confirmed] https://launchpad.net/bugs/330298 [08:00] s/large/high/ [08:31] good morning [08:32] YoBoY: guud morning ATCHIMMM [08:34] constipado BUGabundo ? [08:36] infelizmente, sim === BugMaN1 is now known as BugMaN [10:25] dumb question, but...how do you change a bugs title? [10:25] edit them ? [10:26] ya...which button to I need to click? [10:26] Ryan52: u just need to use the new AJAX green arrow to change [10:26] let me open a link [10:26] #1 [10:26] bug #1 [10:26] Launchpad bug 1 in ubuntu "Microsoft has a majority market share" [Critical,In progress] https://launchpad.net/bugs/1 [10:26] * BUGabundo was about to kick the boy [10:26] *bot [10:28] Ryan52: stupid question: are u logged in? [10:28] yes [10:29] hi, I would like to fill a bug against Jaunty but I've installed Jaunty beta then keep using UpdateManager, is it OK? [10:29] one more stupid question: is my connection that slow or does searching within launchpad takes a whale of time? [10:30] BUGabundo: can you just fix it for me then? :P [10:30] bug #371569 [10:30] Launchpad bug 371569 in ubuntu-dev-tools "mk-sbuild-lvm: debian sid doesn't have security updates" [Undecided,New] https://launchpad.net/bugs/371569 [10:31] should be "mk-sbuild-lv: debian sid doesn't have security updates" [10:31] so 's/mk-sbuild-lvm/mk-sbuild-lv/' [10:31] * Ryan52 sucks at using web interfaces, as you can probably tell :) [10:32] Ryan52: dont u see a yellow togle after the description? [10:32] it looks like a pensil! [10:32] zee: should be fine [10:32] oh! [10:32] thanks :P [10:33] between "u just need to use the new AJAX green arrow to change" (which was incorrect) and the "pencil" that doesn't look like a pencil...ya. [10:33] Ryan52: u already fixed it! [10:33] Morning everybody.... Looks like I've been away from bug triage too long. When did we stop allowing people to edit a bug's status unless they are the asignee or a member of the package's group? [10:33] Ryan52: im on edge version of LP, so stuff tends to change a lot [10:34] wolfger: anyone can change bugs! [10:34] I thought I was too. [10:34] they just cant change some prio levels (those are left for bugcotrol team) [10:34] isn't everybody in bug control on it? [10:34] (edge) [10:34] BUGabundo, I'm getting a message "You are not the bug assignee nor the maintainer of kpackagekit (Ubuntu), and therefore cannot edit this bug's status. " when I try to confirm bug 354140 [10:34] Launchpad bug 354140 in kpackagekit "Installation problem with installation of digikam under Kubuntu Jaunty Beta" [Undecided,New] https://launchpad.net/bugs/354140 [10:34] Ryan52: dont think its a requirement [10:35] oh, hang on a minute [10:35] wolfger: done [10:35] looks like I got logged out of my LP account [10:35] no prob at all [10:35] eh, it's 2:35 AM, I don't know what I'm thinking. [10:35] wolfger: LOLOLOL [10:36] Yep, that was the problem. Maybe I should wake up more before triaging... :-p [10:36] eheh [10:43] kees: can you please look at 371572 and 371569 when you get some spare time? tia. [10:57] BUGabundo: thx [11:26] Netbook Remix uses the standard Ubuntu kernels, right? [11:27] maxb: i386 yes [11:28] * maxb closes spurious UNR bugtask on a kernel bug, then [11:56] need a bug confirmation: change your to be the same pass but add a few NUMBERs to the end! [12:00] BUGabundo: Steps to reproduce? Bug #? [12:01] Hew: no bug yet! just trying to reproduce [12:01] Hew: open terminal; type passwd [12:01] enter current pass; enter current pass + some NUMBERs [12:01] pass fails to accept new password [12:02] i guess its a security feature [12:03] yes, because its the old PW just with something added [12:03] ogra: still its a diff pass, isnt it? [12:03] you should see the asme if you just add letters [12:03] *same [12:03] it cause confusion on users, and even using GUI (via About Me) [12:03] it silently fails [12:04] it should throw out a proper error message [12:04] thats the bug then [12:04] yea, perhaps there should be a better notification, the word "similar" should be used to describe the new password. [12:04] no error AFAICS [12:04] and CLI also not very helpfull [12:04] at least choosing a pass '1111111111111', warns about a palendoric pass [12:05] Bad: new password must be different than the old one [12:05] thats what i get here on the cmdline [12:05] which is imho a proper error message [12:05] but if the GUI doesnt show this it is indeed a bug [12:06] can u file it? i'm a tad busy nw [12:06] *now [12:06] please sub me to it, if u open it [12:06] not really [12:06] ogra: no? hew you ? [12:06] * ogra has about 400 open bugs to care for [12:07] (i'm cautious about any i add to that list, sorry, and i havent seen it since i never used the gui) [12:09] me neither [12:09] just helping an user, and he stated he couldnt change it [12:09] so i debuged it and saw this behaviour [12:10] so tell *him* to file it :) [12:10] and to attach his auth.log to the bug [12:10] okay [12:10] $ ubuntu-bug to the rescue [12:11] ogra: against what package, by the way? [12:11] no idea :) [12:11] seb128: ping [12:12] what package handles About Me and password? === mrpouit is now known as mr_pouit [12:13] BUGabundo, might be gnome-c-c [12:13] but i'm not sure [12:14] ogra: gnome what? [12:14] control center? [12:14] yes [12:21] Hi, I would like to know how I can change status to triaged? I have not such option at launchpad [12:22] arteek: only bugcontrol members have that option [12:22] aha, I knew it:-) [12:23] But I hoped that each launchpad user can [12:25] BUGabundo: what is the issue exactly? [12:27] seb128: h. if user changes password to the same pass plus a few numbers, its refused [12:27] both on CLI (passwd with a message just stating it failed) and GUI (via About Me with no message) [12:30] seb128: any idea what package that would be? [12:33] seb128: gnome-control-center I think [12:33] ok arteek [12:35] no [12:35] BUGabundo: if passwd fails too it's not a GNOME bug but rather a passwd one [12:36] bug 371615 [12:36] Launchpad bug 371615 in gnome-control-center "changing password by addind digits to current one fails" [Undecided,New] https://launchpad.net/bugs/371615 [12:36] grrr [12:36] ok passwd added [12:36] grrrrrr [12:36] seb128: calm down!!! [12:37] when you open a new task rather than reassigning you bug flood for ever whoever is not concerned [12:37] ie g-c-c subscribers will be bug mail for every comment now [12:37] i'll try to set it to NULL [12:38] I'm setting it to ubuntu and invalid [12:38] and sorry about the ranting but we get way to many bugs right now, always like that after stable [12:38] it's really stressing work [12:38] seb128: sorry... i guess its a LP bug... actualy it really is [12:38] but no fix yet [12:39] i know some lp admins set it to NULL [12:39] right, that's a known one [12:39] but i cant [12:39] I've reassigned to ubuntu and closed [12:39] wgrant: isnt that so? [12:39] not a lot of people are subscribed to the whole ubuntu ;-) [12:39] i was once [12:39] and those who are can handle a few extra emails [12:39] for 2 weeks [12:40] impressive ;-) [12:46] BUGabundo: 'null' is a project, not a package. [12:47] BUGabundo: You can't transform a package task into a project one. [12:47] seb128, passwd does handle it fine [12:47] wgrant: so we can change the proj from Ubutnu to null ? [12:48] BUGabundo: Ubuntu is a distribution, not a project. [12:48] ogra: not fine... it just says the pass is the same, when its not [12:48] seb128, it properly says "Bad: new password must be different than the old one" if you just append chars to the old one ... BUGabundo said the GUI dies silently without error msg in that case, so its a gui bug [12:48] ogra: there is already bugs about the GUI not making messages clear [12:49] ogra: the fact that it thinks that's the same password is a passwd bug [12:50] * ogra doest nee that as a bug ... it essentially *is* the same passwd [12:50] *see [12:51] ubuntu and ubuntujaunty are the same word? [12:51] seb128: ahh?? [12:51] no, it could be more explicit in the error, but from a security POV where a cracker works from first to last letter through the PW they are the same up to a certain point [12:51] BUGabundo: what "ahh??" [12:53] seb128: "ubuntu and ubuntujaunty are the same word?" [12:53] BUGabundo: that was a question for ogra, if he things those are identic [12:53] the proper error would be "Bad: new password to similar to the old one" [12:53] why should that be an error? [12:53] I might decide to have a new password starting with the same letters than the previous one but being different [12:54] because our passwd is set up to deny it [12:55] ask the security team why [12:55] prefix10 prefix11 etc lol [12:55] if we enforce that its surely ok to throw an error, the only issue here is the not correct wording of the error [12:55] which is a bug still [12:56] tyring it in g-about-me leaves the gui sit there eternally though [12:56] * ogra just checked [12:56] right [12:56] May 4 13:06:29 osiris passwd[12842]: pam_unix(passwd:chauthtok): new password not acceptable [12:56] bug #338976 [12:56] Launchpad bug 338976 in gnome-control-center "gnome-about-me hang when changing passwords with libpam-cracklib" [Medium,Incomplete] https://launchpad.net/bugs/338976 [12:56] auth log has a proper message it seems [12:57] bug #358161 [12:57] Launchpad bug 358161 in gnome-control-center "Changing password from "about me" hangs" [Medium,Incomplete] https://launchpad.net/bugs/358161 [12:57] we don't need yet another duplicate [12:57] ah, good [12:57] that's why I recycle the new bug as a bug about the passwd wording [12:57] you can as well close it if you want [12:57] no, it should just use the same wording it sends to logger [12:58] ok, that's what the new bug is about then [12:58] good [12:58] * ogra hands seb128 a candy bar [12:58] lol [12:59] thanks ;-) [12:59] :) [12:59] ogra: Gnome-c-c freezing has 7 bugs open! needs a few mark as dupe [13:00] BUGabundo: how come you didn't check before opening yours? [13:01] seb128: i did! diff bug! mine was no clear messag on GUI and CLI [13:01] all other were about freezes [13:01] i didnt get a freeze [13:02] lunch [13:02] bye [13:14] bug 363787 [13:14] Launchpad bug 363787 in ubuntu "laptop locks up, appears to be at random" [Undecided,Incomplete] https://launchpad.net/bugs/363787 [13:15] reporter says on bug 363787 upgrade from 2.6.28.-11.42 to 2.6.28-12.43 cures his problem wants to close bug, how are bugs closed [13:16] Launchpad bug 363787 in ubuntu "laptop locks up, appears to be at random" [Undecided,Incomplete] https://launchpad.net/bugs/363787 [13:17] jtholmes: you can mark the task as fix released and paste [13:18] the response teaching the user to do that by himself next time [13:18] ok will give it a try thx [13:25] great [15:10] Boo [15:11] hi bddebian [15:14] Hi thekorn [15:33] dtchen: Do you think the fix in -43 for the crackling could trigger the pulseaudio exiting at 100% CPU bug ? [16:02] * penguin42 returns in 2.6.28-11 #42 [16:20] with the debian sync, new packages come in also, right? [16:22] micahg, Mostly. Just about all of them end up in the NEW queue, and there's always a couple on which the sync script fails. Check https://launchpad.net/ubuntu/karmic/+queue before getting too worried about things not appearing. [16:24] the reason I ask is because I invalidated my own bug about syncing rt 3.8 since it exists in debian [16:25] but if it requires a manual step to make sure it syncs, then maybe I should have left it open [16:29] I'd recommend leaving it invalid for a bit. If nothing shows either in the repos or in the +queue in a couple weeks, reopen. [16:30] persia:done means imported? [16:30] oops [16:30] *done [16:30] Hrm? [16:31] on the queue page, does done mean imported? [16:31] It's more complicated than that, but sorta. [16:31] well, it's in teh done section [16:31] For source or binary? [16:31] source [16:32] THen the binaries probably have to go through NEW again. [16:32] ok [16:32] but it doesn't have any crazy deps so I'm not worried [16:32] I'm actually running the sid packages on jaunty [16:32] I haven't learned how to recompile stuff yet [16:35] micahg, Popular methods include: [16:35] !pbuilder [16:36] pbuilder is a system to easily build packages in a clean chroot environment. To get started with PBuilder, see http://wiki.ubuntu.com/PbuilderHowto [16:36] !sbuild [16:36] sbuild is a system to easily build packages in a clean schroot environment. To get started with SBuild, see https://help.ubuntu.com/community/SbuildLVMHowto [16:37] yep, I just haven't had a chance yet [16:37] I actually want to learn hwo to have LP build stuff for me too [16:38] !ppa [16:38] With Launchpad's Personal Package Archives (PPA), you can build and publish binary Ubuntu packages for multiple architectures simply by uploading an Ubuntu source package to Launchpad. See https://help.launchpad.net/PPAQuickStart. [16:38] easy [16:50] hggdh, being a little to the bug squad I was wondering if it would be out of bounds to suggest to someone reporting the freeze bug to try and use the proposed kernel 2.6.28-12-43 since someone else reported that kernel fixed their random desktop freeze ups [16:51] s/little/little new [16:55] jtholmes, yes, it can be done. Do you have a reference for this? [16:57] jtholmes, the user would have to enable jaunty-proposed, and cherry-pick the kernel, though [17:03] hggdh, i was thinking about having them get the kernel straight from here https://launchpad.net/ubuntu/jaunty/+source/linux/ and give them a ref as to how to compile which someone named Peter from Ubuntu has a good write up i am testing now [17:03] jtholmes, compile/build the kernel? [17:04] hggdh, too much to a qualified user to do? [17:04] to ask [17:04] jtholmes: which bug is this for? [17:04] this limits the usage to experienced user... and will require a lot of knwoledge on installing local packages [17:05] bdmurray, hold on let me tell you [17:05] bdmurray, it all started with 363787 that user upgraded [17:05] bug 363787 [17:06] hggdh: Error: Could not parse data returned by Launchpad: The read operation timed out [17:06] ah LP will timeout again [17:06] *did* [17:06] * Pici pokes ubot4` [17:06] bug 363787 [17:06] Launchpad bug 363787 in ubuntu "laptop locks up, appears to be at random" [Undecided,Fix released] https://launchpad.net/bugs/363787 [17:06] thanks, Pici [17:06] ;-) [17:08] hggdh, yes a few of the users that responded seemed to have the savvy to do such [17:08] jtholmes, this was about a soft lockup on the kernel; it would really apply on users having the same/similar kernel backtrace, not (necessarily) for the generic freezes we have seen [17:09] jtholmes, but there is no need to build the kernel, it is already built on jaunty-proposed [17:09] hggdh, and were is the built one url pls [17:10] you have to enable jaunty-proposed on synaptic (easiest way) [17:10] ok good to know [17:11] on synaptic, click on Settings/Repositories, select the "Updates" tab, and enable it there [17:11] right [17:11] thx [17:11] then reload, and cherry-pick the kernel (otherwise all -proposed will be added) [17:12] yeah, getting everything could be a problem, thx [17:13] it is not really *bad*, since most of -proposed will, hopefully, end up in -updates. But it may confuse the issue (when checking for a fix, the ideal is to only update what is *required* to check) [17:14] alright I will procede with caution [17:14] thx [17:14] welcome, and thanks for helping === amarillion is now known as amarAWAY [18:15] bdmurray, ping [18:15] ogra_: pong [18:34] Hi all, can anyone help me get a full backtrace for libgl1-mesa-dri? I've followed the wiki but it seems that -dbg pkg doesen't have all the debugging symbols for r300_dri.so [18:35] gdb says: #0 0xa53a3a5f in _mesa_update_texture () from /usr/lib/dri/r300_dri.so No symbol table info available. === amarAWAY is now known as amarillion [18:54] weird, this library belongs to libgl1-mesa-dri itself. And you have loaded the -dbg or -dbgsym for it? [18:58] 22 [20:25] Having a couple of (unrelated?) problems... [20:25] Can anyone help me pin down where they are? [20:28] hello epastor, what's the problem? [20:28] Specifically, experiencing what looks like Bug 193709... haven't tested the proposed fix yet, plan to soon. Also, having some odd problems associated with either a USB hard drive or sound... that's the one I can't pin down. [20:28] Launchpad bug 193709 in gnome-power-manager "While working screen-monitor goes blank & doesn't respond to keyboard or/and mouse" [Undecided,Invalid] https://launchpad.net/bugs/193709 [20:29] First problem: the sound stutters irregularly (at times, every 10 seconds - at others, it'll go for a song or two before stuttering), no apparent association with CPU activity [20:30] epastor: what version of ubuntu are you using? [20:30] I can't tell if it's a Rhythmbox, audio, or USB hard disk problem, since the trouble seems to be related to the drive spinning down. [20:30] Sorry - Jaunty. [20:31] have you tried moving the audio file to the internal drive to rule out USB hard disk problem? [20:32] pace_t_zulu: *looks sheepish* Haven't tried that yet. Problem is that it seems to take some time before happening, as mentioned... no apparent pattern. [20:33] epastor: i would try moving several files to the internal drive and playing them on repeat... if you continue experiencing the problem you can rule out the USB hard disk [20:33] pace_t_zulu: Will do. The reason I suspect the disk or Rhythmbox is that I can hear (and see, via its activity light) it spinning up just /after/ the stuttering hits [20:34] epastor: your suspicion sounds reasonable... the step i suggested would prove/disprove it [20:34] pace_t_zulu: I'll check. [20:34] epastor: let us know [20:42] pace_t_zulu: Huh... still stuttering [20:43] epastor: now you know it isn't a USB hard drive issue [20:43] epastor: what format are these files? [20:43] epastor: mp3? m4a? [20:44] pace_t_zulu: FLAC, actually [20:44] epastor: are you familiar with lauchpad? [20:44] !launchpad [20:44] Launchpad is a collection of development services for Open Source projects. It's Ubuntu's bug tracker, and much more; see https://launchpad.net/ [20:45] pace_t_zulu: reasonably, yes [20:47] epastor: did you experience this problem w/ intrepid? [20:47] pace_t_zulu: Certainly not as severely, if at all [20:47] pace_t_zulu: Just did a quick test - I see stuttering in Totem as well. [20:47] epastor: it could be the flac codex [20:47] codec [20:48] pace_t_zulu: Seems possible, now. Should I test with some MP3s as well to isolate? [20:49] epastor: i reckon that would be a good idea [20:51] pace_t_zulu: Hm. Duplicated with MP3s in Rhythmbox. [20:52]