[00:10] <kcj> penguin42: bug #665734 I followed the instructions at https://help.ubuntu.com/community/ReportingBugs . Hopefully I included enough information.
[00:10] <ubot2> Launchpad bug 665734 in xorg (Ubuntu) "Xorg freezes when viewing website in Firefox. (affects: 1) (heat: 258)" [Undecided,New] https://launchpad.net/bugs/665734
[00:11] <penguin42> kcj: Was it a particular web site - or one too embarrassing to mention?
[00:12] <penguin42> kcj: Can you add to the bug one of the backtraces that you linked to earlier - it hasn't got it at the moment
[00:12] <kcj> penguin42: Lol. Yes it is a particular website but it is a bit controversial. It's littered with strong political views.
[00:12] <penguin42> haha ok, so put the backtrace in at least
[00:13] <kcj> penguin42: No porn or anything though. disinfo.com
[00:13] <kcj> penguin42: What do you mean by backtrace?
[00:14] <penguin42> kcj: You posted a link to a kernel message you got before?
[00:15] <penguin42> (That page uses a font that is identical for i and l - and has the word ill - quite surreal rendering)
[00:20] <kcj> penguin42: I don't know what you mean, I can't view the website without my system crashing. :(
[00:20] <penguin42> kcj: About an hour ago you gave us a link to a pastebin that had the kernel messages in
[00:21] <kcj> penguin42: this http://paste.ubuntu.com/518962/ ?
[00:21] <penguin42> kcj: Yes!  Include that text in the bug report
[00:21] <penguin42> kcj: Also include the URL
[00:21] <kcj> penguin42: How long are pastes valid?
[00:21] <penguin42> kcj: I don't know, I'd include the full text
[00:21] <kcj> penguin42: should I just include /var/log/messages?
[00:21] <penguin42> kcj: If it's a /var/log/messages that actually includes that, yes
[00:22] <kcj> penguin42: Yes it is.
[00:22] <penguin42> kcj: Incidentally I don't think your bug is that unusual having seen some of them
[00:22] <kcj> penguin42: Am I correct to mark it as a security vulnerability?
[00:22] <penguin42> no
[00:22] <kcj> oh
[00:22] <kcj> I thought it might be because if I was redirected to a website that causes the crash it could.. well.. cause a crash.
[00:23] <penguin42> yeh, although it just looks more like a driver screw up than anything that could do anything nastier than a crash - but heck who knows
[00:23] <kcj> penguin42: How do I unmark it as a security vulnerability?
[00:23] <penguin42> not sure, never done that
[00:24] <kcj> does it matter?
[00:24] <penguin42> I guess the security guys will look  at it, and go nah, not for us and unset it anyway
[00:25] <kcj> lol
[00:29] <kcj> penguin42: I have included var/log/messages
[00:30] <penguin42> great
[00:31] <kcj> I hope this gets fixed soon.
[00:31] <penguin42> kcj: It's certianly worth asking the #radeon, and #ubuntu-x guys - I know you're not the only person to have a bug like that
[00:31] <kcj> Although I know how hard finding bugs can be. :(
[00:32] <kcj> penguin42: What would I ask them?
[00:33] <penguin42> kcj: Well I'm not sure I guess; but I bet they'll ask you to try xorg-edgers and also the daily kernels - so you may as well try them if you know how to get out of a mess if it made it worse
[00:34] <kcj> penguin42: That sounds like a path I'd rather not travel.
[00:34] <penguin42> kcj: OK, fair enough - then just sit back, but be rest assured that lots of people have similar problems so it should get fixed
[00:35] <kcj> penguin42: If only I knew how to fix it myself. :)
[00:36] <penguin42> kcj: I've fixed one or two Radeon kernel bugs - but that's too deep without knowing that Radeon code properly
[00:36] <kcj> penguin42: That almost sounds like fun.
[00:41] <kcj> penguin42: I have only gotten into programming over about the last 9 months.
[01:02] <kcj> penguin42: Thanks for your help.
[01:02] <penguin42> no problem
[01:03] <kcj> penguin42: Please feel free to /msg me.
=== andreas_ is now known as anoteng
[03:15] <andersk> Can someone mark bug 665471 as importance critical?
[03:15] <ubot2> andersk: Bug 665471 on http://launchpad.net/bugs/665471 is private
[03:16] <andersk> ubot2: No it isn’t.
[03:16] <ubot2> Factoid 'No it isn\xe2\x80\x99t.' not found
[03:16] <andersk> Thanks.  Anyway, it’s [natty] GRUB no longer finds kernel with separate /boot partition
[04:12] <RedSingularity> Need some help tagging a bug the proper package.  bug 664265  I think it can go under Intel drivers package.  Any advise?
[04:12] <ubot2> Launchpad bug 664265 in firefox (Ubuntu) "Can't play flash videos full screen on firefox and google chrome (affects: 2) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/664265
[04:24] <micahg> RedSingularity: when other people come along like that and say oh I'm having the same issue, when it's probably not, it's best to ask them to file a new bug
[04:24] <micahg> RedSingularity: and I don't think you ever answered my question from the other day
[04:25] <RedSingularity> micahg:  i did.  Stand by a moment.
[04:26] <RedSingularity> micahg:  There was a corruption in their folder so i had them remove the whole folder.  I warned it would delete all their preferences though.  He didnt seem to mind.....
[04:26] <RedSingularity> micahg:  after further investigation it turned out not to be a corrupption though
[04:26] <micahg> RedSingularity: yes, but that's a big hammer for a small nail, if the corruption was caused by firefox, we can no longer test a fix
[04:27] <RedSingularity> micahg: ahhhh i see
[04:27] <micahg> RedSingularity: you never want to have someone delete a potential test case
[04:27] <RedSingularity> micahg:  what if that folder tho was causing the problem?
[04:28] <micahg> RedSingularity: suggest moving it, not deleting it
[04:28] <micahg> RedSingularity: but generally it won't be the folder, worse case scenario WRT the folder is if they ran as root in which case the solution is to chown the folder appropriately back tot he user
[04:29] <RedSingularity> micahg:  WRT?  I am drawing a blank......
[04:29] <micahg> RedSingularity: that user should file a new bug against the intel driver
[04:29] <micahg> RedSingularity: with regard to
[04:30] <RedSingularity> micahg:  Do you think it is the intel driver?
[04:30] <micahg> RedSingularity: idk, I don't use compiz
[04:31] <RedSingularity> micahg:  should it be filed against compiz or intel you think?
[04:32] <micahg> RedSingularity: it's a newer chipset, so I'd say the intel driver
[04:32] <RedSingularity> micahg:  thats what I thought at first but the issue only occurs when using compiz window manager
[04:33] <RedSingularity> micahg:  seems like compiz needs to edit thir code to accept that card
[04:34] <micahg> RedSingularity: if you're aware that compiz works like that, then fine, idk how compiz works
[04:34] <RedSingularity> micahg....I am not sure myself honestly
[04:36] <RedSingularity> micahg but since fullscreen will work with metacity obviously it isnt intels fault for not displaying the flash video properly......
[04:37] <micahg> hi Amaranth, we're looking a bug 664265, the tangent towards the bottom about compiz and are wondering if a bug should be filed against the driver or compiz
[04:37] <ubot2> micahg: Bug 664265 on http://launchpad.net/bugs/664265 is private
[04:37] <Amaranth> I think you'll have to subscribe me, pretty sure my ubuntu-bug-control membership expired
[04:37] <micahg> Amaranth: it's not privare
[04:37] <micahg> *private
[04:38] <RedSingularity> micahg:  If it were intels fault fullscreen would not work with matacity either i think
[04:38] <micahg> it seems ubot2 is a slightly broken ATM
[04:38] <micahg> RedSingularity: not necessarily true
[04:38] <micahg> I actually have to run out for a bit, but I'll check back here later
[04:38] <micahg> thanks Amaranth
[04:38] <RedSingularity> micahg:  later then :)
[04:39] <Amaranth> Well, I have intel too and sometimes run in to the same problem
[04:39] <RedSingularity> Amaranth:  What do you think??
[04:39] <Amaranth> But only with flash videos
[04:39] <Amaranth> I think I don't remember how to get the information to know for sure :)
[04:40] <RedSingularity> Amaranth: lol
[04:40] <Amaranth> See if someone can reproduce with another driver, only way to be sure
[04:40] <RedSingularity> Amaranth:  another intel driver?
[04:40] <Amaranth> No, nvidia, nouveau, fglrx, radeon, etc
[04:41] <RedSingularity> Amaranth:  well i tested with my Nvidia and its fine
[04:41] <RedSingularity> using compiz as well
[04:41] <Amaranth> That would point to the driver
[04:42] <Amaranth> Although compiz has other issues with flash as well so I'm not sure
[04:42] <Amaranth> Well, rather, flash has issues with compiz ;)
[04:43] <RedSingularity> Hmmmmm now i am really not sure what package to give it.
[04:43] <RedSingularity> What do you think??
[04:44] <RedSingularity> I mean the intel driver was the first thing i thought of so i guess i would have to agree if you say intel
[04:45] <Amaranth> I'd go with intel
[04:45] <Amaranth> worst case bryce reassigns
[04:45] <Amaranth> If it goes to compiz it'll probably sit for some time
[04:46] <RedSingularity> ok.  And what should i mark it?  Confirmed?
[04:48] <Amaranth> Yeah
[04:48] <RedSingularity> Amaranth:  ok and thanks for the help :)
[04:51] <RedSingularity> Amaranth:  one more thing.....what do you think of the importance??
[04:51] <Amaranth> RedSingularity: Leave it alone for now
[04:51] <RedSingularity> Amaranth:  will do
[05:21] <micahg> RedSingularity: you should close that bug and ask the user to file a new one against the intel driver with ubuntu bug
[05:21] <micahg> ubuntu-bug I mean
[05:49] <RedSingularity> micahg:  No good to just change the package?  That report has all our correspondents in it.
[05:51] <micahg> RedSingularity: yes, but it's missing apport information
[05:51] <micahg> RedSingularity: and it ahs nothing to do with the original reporter's issue
[05:52] <micahg> RedSingularity: so, have the user file a new bug with ubuntu-bug and reference the other bug #
[05:52] <RedSingularity> Hmmmm so if he makes a new one can it be marked "confirmed" right away since we did all the questioning?
[05:52] <micahg> RedSingularity: no
[05:53] <micahg> RedSingularity: why should this be confirmed?  can anyone else confirm it?
[05:54] <RedSingularity> micahg: I havent asked anyone to......but wont the user get mad?  I mean it is a real issue on his machine even with a fresh install.
[05:54] <micahg> RedSingularity: oh, nm it's the same user
[05:54] <micahg> RedSingularity: a user cannot confirm his own issue
[05:55] <RedSingularity> micahg:  whats the same user?
[05:55] <micahg> RedSingularity: there's only 1 user in the bug, I thought there were 2
[05:55] <RedSingularity> micahg....there were.  I have a feeling it was him under another name tho :/
[05:56] <micahg> that jazz guy needs to file a new bug
[05:56] <micahg> RedSingularity: take a look at this: https://wiki.ubuntu.com/X/Triaging and make sure all the required information is there
[05:56] <micahg> there are guidelines to confirm there
[05:59] <RedSingularity> micahg:  The original filer should make a "new" report though using apport?
[06:00] <micahg> RedSingularity: no, the user an just run apport-collect
[06:00] <RedSingularity> micahg:  ok
[06:02] <RedSingularity> apport-collect bug #
[06:02] <RedSingularity> ?
[06:03] <micahg> RedSingularity: yes
[06:03] <RedSingularity> ok
[06:04] <RedSingularity> And as for leaving it confirmed??  No good?
[06:05] <micahg> RedSingularity: not unless it meets the X requirements for the status
[06:06] <RedSingularity> can i edit the description and put the necessary details in or is that the users job?
[06:10] <micahg> RedSingularity: no, you can do it
[06:14] <RedSingularity> micahg:  in the reproduce steps should I mention you need the intel driver in use?
[06:14] <micahg> RedSingularity: whatever is relavent
[06:16] <RedSingularity> And how about the original apport info about firefox?  Delete that?
[06:20] <micahg> RedSingularity: you don't have to
[06:20] <RedSingularity> micahg: when the user adds the apport collect info do I put it into the description?
[06:21] <micahg> RedSingularity: no
[06:23] <RedSingularity> micahg: how does it look?  Acceptable?  bug 664265
[06:23] <ubot2> Launchpad bug 664265 in xserver-xorg-video-intel (Ubuntu) "Can't play flash videos full screen on firefox and google chrome with intel driver and compiz (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/664265
[06:25] <micahg> RedSingularity: no "bug"
[06:25] <micahg> it should be apport-collect XXXXXX
[06:26] <RedSingularity> whoops i thought is was apport collect bug number-here.  Making a note to him now.
[06:27] <RedSingularity> Done
[06:32] <RedSingularity> micahg:  How can this ever be marked "triaged" though?  Wouldn't i need another person to test and confirm the problem with their machine?
[06:33] <micahg> RedSingularity: that's a question for the X team
[06:33] <micahg> RedSingularity: there are guidelines on the wiki
[06:34] <RedSingularity> micahg:  So we have no right to mark it triaged then not being a part of the X team?
[06:35] <RedSingularity> micahg:  sorry for the endless questions btw :)
[06:35] <micahg> RedSingularity: there are guidelines on teh wiki for what qualifiees as triaged, I haven't studied it yet
[06:36] <RedSingularity> micahg:  If I were able to reproduce does that make a difference?
[06:37] <micahg> RedSingularity: not unless you have the exact same hardware
[06:40] <RedSingularity> micahg:  Is this what you would consider an easy bug?  It seems like there are a lot of things to take into account for this report.
[06:41] <micahg> RedSingularity: no, not at all
[06:41]  * micahg stays away from X and kernel bugs
[06:42] <RedSingularity> ohh i see.  What do you do though in this case.  I mean i took it because I thought it was a firefox bug.
[06:43] <RedSingularity> obviously it evolved into something else
[06:43] <micahg> RedSingularity: I move it to the appropriate package and move on
[06:44] <RedSingularity> micahg:  Alright.  Good idea.  What else can I do with it now?  Leave it to the intel driver guys?
[06:45] <micahg> RedSingularity: yes
[06:45] <micahg> RedSingularity: you can follow the X triaging guidelines if you like
[06:45] <micahg> I gave you the link
[06:45] <micahg> I just can't help with that
[06:45] <RedSingularity> yes i have it here
[06:49] <RedSingularity> micahg: Obviously it is good to take bugs in a package you are familiar with.  I like working with update-manager but how could I go about leaning more about the package to be of more help?
[06:51] <micahg> RedSingularity: find a mentor familiar with it
[07:11] <geekosopher> need help with bug 664968...
[07:11] <ubot2> Launchpad bug 664968 in ubuntu "Maverick 10.10 Desktop i386 installer fails to boot from USB on Dell Mini 9 (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/664968
[07:13] <geekosopher> the reporter is able to boot the laptop from the usb stick, but not able to boot his netbook from it
[07:14] <geekosopher> should it be marked against grub or linux
=== andreas_ is now known as anoteng
[13:02] <njin> Hello to all, can someone take a lopok at this that seems a security issue https://bugs.launchpad.net/ubuntu/+bug/664960 Thanks
[13:02] <ubot2> Launchpad bug 664960 in ubuntu "Shared object Crash on Unload (Multiple Module Audit) (affects: 1) (heat: 6)" [Undecided,New]
[13:06] <njin> yofel: sorry if disturb ^^^^^
=== blueyed_ is now known as blueyed
[13:47] <penguin42> hmm, fun bug
[13:51]  * penguin42 wonders why he's found it in the stuff in /usr/lib/debug though
[13:57] <jpds> penguin42: I like how his IsKnownToCrash() function has everything hard-coded.
[13:58] <penguin42> oh, I hadn't followed the actual code
[13:59] <njin> penguin42. hello, can you pleae give the link to control that a wishlist respond to our standards? thanks
[14:00] <penguin42> ? sorry, I don't quite understand your question, (and I don't think I know the answer )
[14:01] <njin> penguin42: i've to control that a bug report is well done, so I can ask someone to triage as wishlist
[14:01] <njin> https://bugs.launchpad.net/ubuntu/+bug/664553
[14:02] <ubot2> njin: Error: Bug #664553 is private.
[14:02] <penguin42> jpds: Heck that code is hard to follow - DoLoadUnload loads teh library explicitly but unloses it using the destruction of AutoLib
[14:03] <njin> ubot miss his glasses
[14:07] <penguin42> njin: SO on bug 664553   I see arduino already in the package list
[14:07] <ubot2> Launchpad bug 664553 in ubuntu "Arduino should be in ubuntu software center (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/664553
[14:08] <njin> pebguin42: so i mark as invalid ?
[14:09] <njin> penguin42: so i mark as invalid ?
[14:09] <penguin42> njin: Hang on a sec, I'm just trying installing it
[14:10] <penguin42> njin: Just check, on your system do you see it in Ubuntu Software Centre under Get Software->Science & Engineering->Electronics->Arduino IDE ?
[14:12] <njin> penguin42: yes is present
[14:13] <penguin42> njin: Yeh so tell him it's already packaged, and point him at it
[14:13] <penguin42> (It does look like the version we have is the debian Java free version - and I don't know how much that causes problems)
[14:14] <njin> penguin42: ok thanks i refer to reporter
[14:15] <zeroseven0183> Hi anyone here had their screen brightness problem fixed? I'm using HP Pavilion dv3 on a Lucid Lynx. I'd like to try the PPA but would like to test it first on a live Maverick USB
[14:22] <BUGabundo> Boa tarde o/
[15:46] <mreiter> Hi, I filed a bug about failing hibernation on Thinkpads after upgrading from 10.04 to 10.10. I also did test an upstream kernel and I think the report is ready to be triaged. Could some Bug Control member maybe have a look? Here's the bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/661711
[15:46] <ubot2> Launchpad bug 661711 in linux (Ubuntu) "Hibernate fails on Thinkpad X60 (affects: 8) (heat: 48)" [Undecided,Confirmed]
[16:03] <pmvalente> Hi, I have an asus ul30A notebook, when I upgrade to 10.10 (clean install) the touchpad sometimes doesn't work well, it get a little bit laggy. Some ideas. Thanks
[18:14] <dev001> hi.  i've a but to post re: openssl (upstream) source build issues on Ubuntu.  iiuc, @ launchpad says bugs go to OpenSSL-RT -- seems no Ubuntu-specific place to post the bug.  Atm, I can't seem to get my bug posted to OpenSSL-RT -- tried twice, isn't showing up.
[18:14] <dev001> That said, is there a better/different place in "Ubuntu-land" to post the bug?
[18:29] <cousteau> is there a way to report a bug _without_ having apport installed?
[18:33] <cousteau> and without having firefox installed? how am I supposed to report a bug on a system that doesn't have any browser installed (and that is running on a virtual machine)
[18:35] <joumetal> https://help.ubuntu.com/community/ReportingBugs has some instructions
[18:36] <cousteau> joumetal: all of them involving the usage of apport
[18:36] <cousteau> my bug is about installing ubuntu from a minimal install and then installing ubuntu-desktop with the --no-recommends option
[18:37] <joumetal> check tips and tricks
[18:37] <cousteau> ...never mond, found the instructions, thanks
[18:37] <cousteau> *mind
[19:03] <AbhiJit> hi
[19:03] <AbhiJit> i dont think this is a 'bug'
[19:03] <AbhiJit> https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/665983
[19:03] <ubot2> Launchpad bug 665983 in postgresql-8.4 (Ubuntu) "package postgresql-8.4 8.4.5-0ubuntu10.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (affects: 1) (heat: 6)" [Undecided,New]
[19:04] <AbhiJit> but some type of error or wrong thing
[19:04] <AbhiJit> what to do?
[19:08]  * penguin42 looks at the DpkgTerminal.log
[19:10] <penguin42> AbhiJit: Well it looks like it's that bit about not being able to create the shared memory segment - probably need someone who knows postgresql to know whether thats likely a screwed up value in the guys config or if it's the default one that's a problem
[19:10] <AbhiJit> penguin42, should i ask in to take the issue to #postgres?
[19:10] <AbhiJit> and mark as incomplete?
[19:10] <penguin42> AbhiJit: I wouldn't mark as incomplete
[19:11] <AbhiJit> ok
[19:11] <penguin42> AbhiJit: Well not without understanding if there is something you need; mark it incomplete once you identify something you need from the reporter
[19:11] <AbhiJit> yah
[19:11] <AbhiJit> penguin42, so i just commnet that he try asking in #postgres?
[19:13] <penguin42> AbhiJit: What I would do would be to look through the log for the actual error that failed (that WIT FATAL, detail and hint line) and copy that into a comment saying that that was the error that caused it to fail
[19:13] <penguin42> AbhiJit: It might help someone who does know PostgreSQL triage it better
[19:13] <AbhiJit> oh ok
[19:15] <penguin42> It might help the original reporter to look it up on some postgres docs as well
[19:15] <AbhiJit> hm
[19:15] <penguin42> (I wish packages weren't so fussy - if they've managed to install but couldn't start a service should they actually fail to install?)
[19:22] <AbhiJit> bye
=== Dr_Who is now known as tgall_foo