=== Pici` is now known as Pici
=== snap-l is now known as snap-l_
=== snap-l_ is now known as snap-l
[03:04] <snadge> whats this latest kernel update about?
[03:04] <snadge> theres no USN for it
[03:05] <snadge> god damn im sick of this changelog problem ;)
[03:05] <snadge> and im sick of kernel updates
[03:05] <snadge> i have to rebuild some modules etc
[03:24] <Hobbsee> snadge: that's a different bug to the one you're usually complaining about
[03:24]  * Hobbsee reported that one a while ago, but no one's felt so far inclined to fix it
[03:24] <Hobbsee> feel free to
[03:26] <Hobbsee>   * Fix broadcom Makefile to get correct objects from split-module.
[03:26] <Hobbsee>     LP: #243930
[03:26] <Hobbsee> is the change
[03:44] <LimCore> hi
[03:45] <LimCore> where one should report general epic failures of ubuntu, hard to pinpoint to exact package?  in example "when moving windows - my entire mplayer/totem/kaffeine skips/losses frame... on 2x2GHz box (wt..)"?  So bugs based on functionality, not given application (it also seems to not be unique to one X DE/manager"
[03:51] <Hobbsee> LimCore: do you think you could drop the comments about hte failures of ubuntu?
[03:51] <Hobbsee> it gets really boring when you do it *every time*
[03:51] <Hobbsee> and will probably just get you completely ignored
[03:51] <LimCore> well ok, this is just annoyance, not like i.e. totall lack of working desktop recording program we discussed previously
[03:52] <LimCore> anyway, where to report such system-wide problems
[03:52] <Hobbsee> depends on what causes them.
[03:52] <LimCore> X problem... drivers problem... wrong scheduling policy...
[03:52] <Hobbsee> that one, i'd guess, is compiz not redrawing properly or something.  could be something to do with X.  may well have something to do with the binary driver that you're running.
[03:52] <LimCore> I dont think Im using compiz. how to check
[03:53] <Hobbsee> does it happen on your intel card?
[03:53]  * LimCore wonders why Hobbsee still thinks LimCore uses intel card O_o
[03:53] <LimCore> intells have open driver btw dont they, i915
[03:53] <LimCore> but  Im on nv
[03:53] <Hobbsee> because you said you'd used both drivers yesterday, and the bug yesterday occurred with them.
[03:53] <Hobbsee> er, had both drivers.
[03:54] <Hobbsee> if you're with the binary driver, and it doesn't happen with non-binary drivers, tehn you'll have to contact nvidia.
[03:54] <LimCore> I tihnk I said I use nvidia,  but that other person commenting my bug about recordmydesktop not working at all, confirmed it on his intell
[03:54] <LimCore> well ok I will check... but Im 99% sure its not driver itself, since otheriwse and for harder tasks (i.e. 3d games) it works perfectly
[03:55] <LimCore> bug reporting tool schould be more user friendly and allow general systems, dont you think?
[03:55] <LimCore> "My screen blinks all the time. No I dont know what pacage.. what is
[03:55] <Hobbsee> not really
[03:55] <LimCore> "My screen blinks all the time. No I dont know what pacage.. what is 'package' anyway" <-- typical user
[03:55] <Hobbsee> because most of the time, others have no idea either, and have no system to test on
[03:56] <Hobbsee> and you can report a bug with saying you don't know the package.
[03:56] <Hobbsee> xine, stop misbehaving.
[03:57] <LimCore> what would create a /success/ for ubuntu, would be a QA teams oriented on given areas, from user perspective
[03:57] <Hobbsee> i'd seriously suggest you'd try the forums.
[03:57] <LimCore> or: Ubuntu needs a good way to flexibly allow mounting of pluggable storages. (kde's current version sucks, because 1) 2) 3)"
[03:57]  * Hobbsee sighs
[03:57] <Hobbsee> rants --> forums.
[03:58] <LimCore> forums -> /dev/null
[03:58] <LimCore> how this helps
[03:58] <Hobbsee> your random rants about how ubuntu sucks, etc, don't help either.
[03:58] <LimCore> did you triagged/whatever new version of recordmydesktop to have it in ubuntu repos?
[03:58] <Hobbsee> and in fact, are worse in places where people are attempting to do something productive.
[03:59] <Hobbsee> i requested a backport in irc, but didn't file a bug.
[03:59] <Hobbsee> !backports
[03:59] <ubottu> If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging
[03:59] <LimCore> seems like it worked
[03:59] <LimCore> devels are rather here or in forums?
[03:59] <Hobbsee> yeah, mostly.
[04:00] <Hobbsee> it worked?  what'd you do?  use teh intrepid version?
[04:00] <LimCore> hm? Not sure.. but if it will be faster in rep, the better for all
[04:00] <Hobbsee> well, then, file a backport request for it
[04:00] <Hobbsee> the link gives you the required info.
[04:01] <Hobbsee> it can give you something productive to do, instead of ranting.
[04:01] <LimCore> you are talking to the gay thanks to whom ubuntu doesnt provide totally broken sshfs in 8.04
[04:01] <LimCore> hah
[04:01] <LimCore> guy.
[04:01] <LimCore> ...which I think is very usefull tool as ssh based "nfs"
[04:02]  * Hobbsee raises an eyebrow
[04:02] <LimCore> dont look at the typo
[04:02]  * LimCore ^H
[04:02] <Hobbsee> if you're thinking you deserve instant respect, and others to be your slave, for getting one bug fix in....
[04:02] <LimCore> Hobbsee: I refer to the totally ***** version of sshfs that segfaulted each few minutes, and thanks to my persistance was fixed 2 dayss before 8.04 was out
[04:03] <Hobbsee> yes, i saw you ranting about it repeatedly.
[04:03] <Hobbsee> well done, you fixed something.
[04:03] <LimCore> if I would be quiet, all ubuntu users would use broken sshfs
[04:03] <Hobbsee> do you want a medal?
[04:03] <LimCore> it is not as hilarious as ssh dsa bug, but still
[04:03] <LimCore> sure
[04:04] <Hobbsee> too bad.  i don't have any spare ones.
[04:04] <Hobbsee> oh good, mesa got through on intrepid.
[04:04] <Hobbsee> maybe X will work now
[04:04] <LimCore> how to check that version of recordmydesktop that yo uare refering to?
[04:05] <Hobbsee> the one in intrepid?  install it.
[04:05] <Hobbsee> i'm sure you cna figure out how to
[04:26] <LimCore> Hobbsee: intrepid version works excelent for me
[04:27] <LimCore> this warning seems to be harmless, X Error: BadWindow (invalid Window parameter) BadWindow on XGetWindowAttributes.
[04:28] <Hobbsee> correct
[04:31] <LimCore> well, is there any need to actually do  https://bugs.launchpad.net/ubuntu/hardy/+source/recordmydesktop/+bug/244261/+nominate  ?
[04:31] <ubottu> Launchpad bug 244261 in recordmydesktop "Locking assertion failure libxcb-xlib.so.0 xcb_xlib_unlock" [Undecided,Confirmed]
[04:32] <Hobbsee> no, i already nominated the important ones.
[04:33] <LimCore> in best case, when regular ubuntu users will be able to use again recordmydesktop?
[04:33] <Hobbsee> after it gets backported, like i told you earlier.
[04:33] <Hobbsee> did you file the backports request yet?
[04:34] <LimCore> well you have the experience - how much time it is, days, months?
[04:34] <Hobbsee> depends how long it takes the fix to be found, and how soon people act on it
[04:35] <LimCore> well, cool
[04:36] <LimCore> but still, for enders - they simple could not record their desktop for months now... I wonder can this be avoided
[04:36] <Hobbsee> by people testing the prereleases of ubuntu, filing bugs, and getting them fixed, mainly.
[04:36] <Hobbsee> and actually doing productive stuff
[04:37] <Hobbsee> RAOF: hm.  is it worht reporting a bug that the SHM stuff for touchpads doesn't get detected automatically?
[04:37] <Hobbsee> RAOF: or has someone already reported it?
[05:02] <Grantbow> Is this the right channel for "ubuntu bug control" as described https://wiki.ubuntu.com/Bugs/Status under triaged
[05:02] <Grantbow> ?
[05:04] <LaserJock> I believe so
[05:04] <Grantbow> I think bug #201388 is a medium - I confirmed it but I don't know the next step so I thought I would ask.
[05:04] <ubottu> Launchpad bug 201388 in gnome-system-tools "[users-admin] Group list is not complete" [Undecided,Confirmed] https://launchpad.net/bugs/201388
[05:18] <Grantbow> anyone?
[05:23] <hggdh> Grantbow, can you reproduce the issue?
[05:24] <hggdh> Grantbow, if you could, I do not see any indication in the bug comments
[05:25] <hggdh> for example, what did you try, how did you try, what did you find?
[05:25] <Grantbow> hggdh: did you look at the bug?  Yes, I confirmed the problem first reported by someone else and I wrote down the steps to reproduce it.
[05:26] <Grantbow> and the package name and version
[05:26]  * hggdh is again hit by the irc name vs LP name thingie
[05:26] <hggdh> Grantbow, sorry
[05:26] <hggdh> but...
[05:26] <hggdh> what version?
[05:27] <hggdh> (although, in retrospect, grantbow sounds suspiciously like the name in the bug ;-)
[05:27] <Grantbow> I didn't report it at first.
[05:27] <Grantbow> gnome-system-tools 2.22.0-0ubuntu9 hardy heron 8.04.1
[05:28] <Grantbow> Ioannis Ramfos is the original reporter
[05:28] <hggdh> Please add the version you tested as a comment, and please ask the reporter for their version
[05:29] <hggdh> but I can confirm on Intrepid also, so... it is worthy of a Triaged status
[05:29] <hggdh> (but we still need to know the reporter's version_
[05:29] <Grantbow> hggdh: did you look at https://launchpad.net/bugs/201388?  it is in the comment already - I just added it.
[05:29] <ubottu> Launchpad bug 201388 in gnome-system-tools "[users-admin] Group list is not complete" [Undecided,Confirmed]
[05:29] <Grantbow> since two of us can confirm it - how much value is there in waiting for Ioannis response?
[05:32] <hggdh> we know it is valid at hardy and Intrepid, but we do not know if the reporter's version is still maintained
[05:32] <hggdh> we do not wait for the reporter's answer, but if this will be fixed for him/her or not is still open
[05:33] <Grantbow> aha!  That makes sense, good point.
[05:33] <hggdh> Grantbow, anyway, good work, and thanks for helping
[05:34] <Grantbow> I am new to working with Ubuntu bugs but I've done QA professionally.  Do you want to ask the reporter or can you tell me know to do it?
[05:34] <LimCore> it seems 8.04 didnt worked after installation (Gnome problems) for one of my users (no more details as for now) - anyone knows this one?
[05:35] <hggdh> Grantbow, either of us can do it -- all we need is to add a comment asking for it.
[05:35] <hggdh> but, in order to prevent a race condition... do you want me to do it?
[05:36] <Grantbow> Ok, yes please - I'll watch and do the next one myself.  Thanks.
[05:38] <hggdh> Grantbow, done, again thank you for your help
[05:39]  * hggdh hits the pillow (too much work, too much pain, too much alcohol)
[05:42] <Grantbow> hggdh: great, thanks for your assistance.
[06:34] <Somerandomname> have an issue with the Wubi installer
[06:34] <Somerandomname> Apparently if you run a windows cleaning utility it clears the location of the wubi install
[06:34] <Somerandomname> meaning your left with a ubuntu boot option but no ubuntu to load.
[06:55] <Grantbow> Somerandomname: that sounds quite bad - which cleaning utility?
[07:31] <Somerandomname> Grantbow Theres two that seem to affect the installer, Ccleaner and NCleaner (both by the same makers)
[07:33] <Grantbow> who makes it?
[07:36] <Somerandomname> ill grab that info
[07:36] <Somerandomname> http://www.ccleaner.com/
[07:36] <Somerandomname> Piriform Ltd.
[07:37] <Somerandomname> the reason i can verify this is from those programs is because i have installed the same method on 3 boxes
[07:37] <Somerandomname> each running diffirent versions of windows.
[07:38] <Somerandomname> Vista/MCE/XP all 3 develop the same issues after a system clean.
[07:38] <Grantbow> so ccleaner will wipe out a wubi install?  that's worth reporting :-)
[07:38] <Somerandomname> It technically doesnt wipe the install, it corrupts the install.
[07:39] <Grantbow> ok, but I bet a report here and maybe to ccleaner.com would be appreciated.
[07:39] <Somerandomname> but once you then try to unistall, you can but with the remnant of the loading option for ubuntu (which never goes away)
[07:39] <Grantbow> aha, interesting
[07:39] <Somerandomname> I am not sure how to go about this? directly to ubuntu bugs?
[07:40] <Grantbow> I'll try to find the right place, one sec
[07:41] <Grantbow> https://bugs.launchpad.net/wubi
[07:41] <Somerandomname> thanks
[07:41] <Grantbow> include as much info as possible
[07:41] <Grantbow> np
[07:41] <greg-g> it isn't really a wubi bug though, you should report it to that software's developers
[07:41] <greg-g> we can't fix
[07:42] <Grantbow> a warning might be useful in our documentation
[07:42] <Grantbow> or something
[07:42] <greg-g> or in theres! :)
[07:42] <Grantbow> especially their's
[07:43] <Grantbow> but when wubi fails who will get blamed?  :-(
[07:43] <Grantbow> users may not make the association
[07:43] <greg-g> in that case, that software manufacturer
[07:43] <greg-g> true
[07:44] <Grantbow> wubi failed so it's our fault - they were just doing "what they usually do" to take care of their system and never had any problems before, lol.
[07:44] <greg-g> Somerandomname: please report to those developers and put what you find out in the bug report you file for wubi
[07:44] <greg-g> Grantbow: yep
[07:44] <greg-g> :)
[07:44] <Grantbow> unfortunately.  There's a way to push a report here upstream - would that be appropriate in this situation?
[07:44] <Somerandomname> In the process of reporting this now.
[07:45] <greg-g> Somerandomname: paste the bug number here when you are done
[07:45] <Grantbow> at least the data about the problem needs to be collected in a public place
[07:45] <greg-g> please
[07:45] <greg-g> Grantbow: upstream is ccleaner, no? And they don't appear to have a public bug tracker
[07:45] <Grantbow> it may go into a bit-bucket if you send it to the ccleaner.com reporting locations - I doubt they have a public bug system.
[07:46] <Grantbow> haven't checked yet.
[07:46] <greg-g> http://www.ccleaner.com/help just a forum
[07:46] <Grantbow> maybe Somerandomname would know if they do or not
[07:46] <Grantbow> I've never used it
[07:47]  * greg-g nods
[07:47] <Grantbow> that's the only publically available support option?  uh oh.
[07:48] <greg-g> just a warning to everyone, the bug report will probably be closed as invalid due to it being caused by a 3rd party closed source application (ie: "we can't do anything about it, they are the ones that messed up, sorry")
[07:48] <Grantbow> a note should be placed in our docs to warn users this will happen
[07:49] <greg-g> its a wiki :) https://wiki.ubuntu.com/WubiGuide
[07:50] <Grantbow> hmm, http://www.piriform.com/ is the company that owns that product
[07:50] <Grantbow> good idea greg-g
[07:50] <Grantbow> lol!  http://www.piriform.com/about  "The future of software is free software!"
[07:51] <greg-g> lowercase free
[07:51] <greg-g> they have lost my respect :)
[07:51] <Grantbow> after the report is fleshed out they do have an email submission form.  http://www.piriform.com/contact
[07:52] <Grantbow> depends on how they respond, they may not know of this bug yet.
[07:52] <greg-g> they probably don't.
[07:53] <Grantbow> From a very high level I can see why a huge multi-gig file might be removed if you are trying to clean up a machine's hard disk.
[07:54] <Grantbow> but without a warning?
[07:54] <Grantbow> not good
[07:54] <greg-g> or a reason?
[07:54] <greg-g> good rule of thumb is "if you don't know what it is, don't touch it"
[07:55] <Grantbow> yeah, it should somehow be able to identify what it deletes before doing os
[07:55] <Grantbow> so
[07:55]  * greg-g nods
[08:01] <Somerandomname> Sorry for the delay but heres the bug report #
[08:01] <Somerandomname> Bug 248915
[08:01] <ubottu> Launchpad bug 248915 in wubi "Corrupt File System When CCLEANER/NCLEANER Are run" [Undecided,New] https://launchpad.net/bugs/248915
[08:02] <Somerandomname> Hope its helpful.
[08:04] <greg-g> I added paragraphs to make it readable
[08:05] <Somerandomname> Sorry about that im lingusitlicly challanged.
[08:06] <greg-g> :) no problem
[08:08] <Somerandomname> linguistically* ( i better look like a fool that can correct himself.)
[08:34] <Grantbow> Somerandomname: thanks for reporting this
[09:56] <snadge> so let me get this straight.. ubuntu pushes out an "important security update" for the kernel
[09:56] <snadge> because:   * Fixed hppa FTBS by adding ABI files from -19.33.
[09:56] <snadge> WOW! thats so worth millions of people downloading a new kernel
[09:56] <snadge> all 5 hppa users will be extremely overjoyed
[10:05] <pwnguin> snark levels approaching fatal
[10:15]  * LimCore starts usng hppa to feel the joy too
=== emgent_ is now known as emgent
[13:04] <Hew> Hey guys, I'm reproducing a segmentation fault, but apport doesn't seem to be picking it up. I have set enabled=1 already. Any ideas?
[13:05] <RAOF> There's alwoys GDB.
[13:05] <RAOF> But I'm off, so I won't be able to hand-hold you through  it.
[13:05] <Hew> no worries, thanks anyway
[13:07] <Hew> just wondering why apport isn't catching it since it's the easy option for reporting the bug. The crash report has been requested (bug #248868)
[13:07] <ubottu> Launchpad bug 248868 in file-roller "File-Roller is unable to open gzip-compressed files like pci.ids if they are missing an .gz extension" [Low,New] https://launchpad.net/bugs/248868
[13:12] <Hew> fyi, just found that the .crash file was sitting in /var/crash but for some reason didn't pop up like it usually does. Problem solved.
[13:29] <mouz> Hew there are reports of apport itself crashing.
[13:29] <mouz> For example bug 248788
[13:29] <ubottu> Launchpad bug 248788 in gnome-system-monitor "gnome-system-monitor crashes at startup" [Undecided,Invalid] https://launchpad.net/bugs/248788
[13:29] <Hew> mouz: I figured something like that was happening, thanks for the bug #
[13:30] <mouz> That person attaches his crash dumps directly. Can those be used at all?
[13:31] <Hew> I believe so, yes. I don't really have much experience with dealing with apport data though.
[13:32] <Hew> I haven't received any apport "crashes" though, just it wasn't doing what I expected it to.
[13:33] <Hew> ah, actually it looks like they shouldn't be attached to the bug report itself
[13:33] <Hew> mouz: the user double clicking the .crash file should take care of things
[13:37] <mouz> Hew: not if apport itself crashes :)
[13:38] <Hew> true, but the user in that bug seems to have posted a .crash for it somehow :P
=== bddebian2 is now known as bddebian
[15:34] <geser> thekorn: Hi, do you know when there will be a new python-lp-bugs in intrepid which works with current LP?
[15:35] <Hobbsee> geser: they're still messing with the ui for the next couple of days, apparently
[15:35] <Hobbsee> no point rewriting it yet :)
[15:36] <geser> so anything using python-lp-bugs is broken currently?
[15:37] <Hobbsee> probably
=== james_w_ is now known as james_w
[15:38] <geser> crap :( so I need to file sync request through the ui
[15:38]  * geser wishes they would finish the LP API before doing more UI changes
[15:39] <Hobbsee> geser: requestsync doesn't work?
[15:39] <Hobbsee> geser: or use mail.
[15:40] <geser> true, I usually use requestsync with --lp
[15:53] <thekorn> geser: sorry, as Hobbsee said, there are currently changes on lp every day, so it is a bit hard to release a working version for intrepid,
[15:53] <thekorn> but the bzr branch should be up-to-date
[15:53] <thekorn> and working
=== fenris_ is now known as e-jat_
=== e-jat_ is now known as e-jat
=== LaserJoc1 is now known as LaserJock
=== thekorn_ is now known as thekorn
=== chuck_ is now known as zul
[19:15] <runemaste644> is there a place to report bugs besides launchpad?
[19:16] <runemaste644> I was just about to submit a bug report and launchpad stopped responding.
[19:17] <Pici> runemaste644: Nope, thats it.
[19:18] <runemaste644> somebody obviously does not want me to submit a bug report because im not even getting the slightest chance to submit a bug report.
[19:18] <runemaste644> First firefox wasnt working, now launchpad is down, whats next?
[19:20] <greg-g> launchpad is working for me right now
[19:21] <runemaste644> oh, and before either of those, i found a bug in the bug report tool
[19:21] <runemaste644> Yes! Now's my chance!
[19:26] <runemaste644> turns out it was already submitted, i subscribed and commented on it
[19:30] <greg-g> runemaste644: good deal
[19:30] <greg-g> thanks for looking into the issue
[19:36] <runemaste644> oh, and how come a bug that i submitted about a half a year ago is still marked new?
[19:37] <jjesse> runemaste644: because it hasn't moved to any of the other bug statuses?
[19:37] <runemaste644> yes, but how come nobody has even looked at it
[19:39] <runemaste644> it is a bug that prevents th screen from automatically locking
[19:39] <runemaste644> *the
[19:39] <jjesse> runemaste644: because we are busy?
[19:40] <runemaste644> fair enough
[19:43] <runemaste644> its just i thought it might be important for system admins to know
[19:44] <charlie-tca> Does someone need to triage Bug #186794 for me? I marked it as invalid since it is against the theme itself.
[19:44] <ubottu> Launchpad bug 186794 in gtk2-engines-murrine "Running VMware Server Console with Murrine as GTK engine doesn't look right" [Undecided,Invalid] https://launchpad.net/bugs/186794
[20:22] <charlie-tca> Can anyone let me know if an invalid bug needs to be triaged?
[21:22] <mouz> charlie-tca: an invalid bug will probably not be triaged. Can you set it back to new?
[21:24] <mouz> charlie-tca: maybe i do not completely understand your question...
[21:27] <greg-g> charlie-tca: what is the bug number?
[21:30] <mouz> charlie-tca: invalid bugs need not be triaged :)
[21:38] <charlie-tca> Thank you. It's bug #186794
[21:38] <ubottu> Launchpad bug 186794 in gtk2-engines-murrine "Running VMware Server Console with Murrine as GTK engine doesn't look right" [Undecided,Invalid] https://launchpad.net/bugs/186794
=== mcas is now known as mcas_away
[22:20] <hggdh> charlie-tca, invalid is a final state for bugs.
[22:22] <hggdh> charlie-tca, the bug is invalid actually because the reporter is using a non-packaged-by-us vmware, so your response & status setting seem correct
[22:38] <charlie-tca> Thanks. I appreciate you taking the time.
[23:59] <chrisccoulson> hi, would somebody mind setting this bug to 'wishlist' please? https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/249237
[23:59] <ubottu> Launchpad bug 249237 in gnome-system-monitor "Process Properties dialog" [Undecided,New]