[00:00] <titi13> Hello i have a problem can anyone help me solve it please ?
[00:03] <titi13> is anybody here ?
[00:09] <ffm> titi13: try #ubuntu
[00:12] <snap-l> titi13: This is for discussing the bug tracking system
[00:12] <snap-l> Which, if you have a bug under Ubuntu can be accessed at http://launchpad.net
[01:32] <mrooney> is there any way to get notified of any bugs that match a certain string/regex?
[01:32] <mrooney> well, obviously there are ways, I mean a current infrastructure that does it already
[01:34] <bdmurray> mrooney: for example?
[01:44] <mrooney> bdmurray: well, I was thinking of adding support to the #ubuntu-bugs-announce for people to PM it regular expressions, and when bug descriptions match it it could PM them the #
[01:45] <mrooney> I was trying to figure out if it would be useful, and if so, if it already existed somewhere, or something similar anyway
[01:45] <mrooney> adding support to the bot in #...., it should have said
[02:23] <bddebian> Boo
[02:34] <wolfger> mrooney: interesting idea!
[02:36] <wolfger> So... on the topic of bugs marked incomplete that maybe ought to be marked as something else... what does anybody think of bug 117232 ?
[02:37] <wolfger> It's not likely to change status anytime soon (if ever)
[02:38] <wolfger> I'm thinking "confirmed, wishlist" is more appropriate
[02:43] <Jafet> When Ubuntu boots I am shown a splash screen; I also remove the "quiet" option in grub so that I get a bit of terminal output in between. Might X be started at any point in this timeframe?
[02:43] <Jafet> (This is the correct channel for investigating bugs, I presume)
[02:44] <greg-g> Jafet: what is the bug? (what do you expect to happen, and what actually happens?)
[02:45] <Jafet> I'm investigating the distressing #194214 (and variants) which seems to have afflicted me.
[02:45] <greg-g> Jafet: and yeah, this is a good channel to figure out what information you should provide when you submit a bug report on launchpad
[02:45] <greg-g> bug 194214
[02:46] <Jafet> Uh, fix released?
[02:46] <Jafet> Funny, I didn't notice...
[02:46] <greg-g> I haven't read that bug, and the comments are long, I don't think I would be of much help :)
[02:47] <Jafet> I don't see any links or any statements on that page hinting at a fix anywhere...
[02:47] <Jafet> Well, you could answer my question, and help me narrow down packages.
[02:47] <greg-g> https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/194214/comments/91
[02:48] <greg-g> the is the message from the "launchpad janitor" which says which changlog the bug was reported to be fixed by
[02:49] <Jafet> Okay.
[02:49] <greg-g> were you experiencing stuck keys?
[02:49] <Jafet> I'm experiencing one stuck key.
[02:50] <Jafet> It's the down arrow key.
[02:50] <Jafet> It's preventing me from using sudo in the terminal, but that's another bug.
[02:51] <Jafet> "xorg-xserver"?
[02:51] <Jafet> I only see a package "xserver-xorg".
[02:51] <Jafet> Wait, the changelog actually said "xorg-server".
[02:53] <Jafet> I have a slightly newer version of xserver-xorg-core (-1ubuntu9), though.
[02:53] <Jafet> Also, does xorg start at that aforementioned point in the boot process?
[02:54] <Jafet> That seems to be a bit early for xorg to start to me.
[02:54] <greg-g> at what point?
 ﻿When Ubuntu boots I am shown a splash screen; I also remove the "quiet" option in grub so that I get a bit of terminal output in between.
[02:55] <greg-g> don't know why I asked, I'm not sure off the top of my head, you could look at syslog
[02:55] <Jafet> I did have a look; I'm no unixbeard but I didn't see anything unusual. No errors or warnings declared.
[02:56] <Jafet> I looked through the user, xorg and syslogs.
[02:57] <greg-g> so, I assume you are running an updated hardy installation correct?
[02:58] <Jafet> Of course.
[03:00] <greg-g> then, you aren't experiencing that specific bug, as many of the people commenting on it said it was fixed with a new version of that package.  So, in that case, you should search Launchpad for similar bugs and see if any are about what you are experiencing, and if not, open a new bug with all the information you can think of that might relate to it (what you tried, what version of packages you are running, attach your xorg.log file, etc)
[03:00] <greg-g> if have any questions about how to report a new bug, feel free to ask
[03:02] <Jafet> How many canned answers do Ubuntu developers have, anyway?
[03:03] <greg-g> what are you referring to?
[03:03] <Jafet> Obviously, the bug isn't fixed.
[03:03] <Jafet> That, is clear enough.
[03:03] <Jafet> The symptoms are identical; the triggers similar.
[03:07] <RAOF> Jafet: What is the actual bug that you are seeing?  It's likely not that bug; I filed it, and it's definitely fixed.
[03:08] <RAOF> That's not to say that you're not seing a bug with similar or identical symptoms but a different cause.
[03:08] <Jafet> I have probably done some unusual mouse-keyboard input combinations this morning.
[03:09] <Jafet> Now the down arrow key is stuck and triggers an event erratically.
[03:09] <Jafet> Xorg is under constant moderate CPU load.
[03:09] <RAOF> Triggers an event 'erratically'?
[03:10] <Jafet> The down arrow event is triggered far more often when Xorg goes into high load.
[03:10] <RAOF> Right.  You're _definitely_ not seeing that bug, then.
[03:10] <RAOF> Because that bug is "this key generates endless keypresses at full speed, all the time".
[03:11] <RAOF> At least 2 other bugs - VMWare doing stupid things, and a kernel bug - were discussed in the comments, but they're filed (or should be filed) seperately.
[03:12] <Jafet> I recall reading these symptoms in another bug report that was filed as a duplicate.
[03:13] <Jafet> Sorry, I should go check what duplicate that bug was filed for.
[03:13] <RAOF> A duplicate of that bug?  Then it was probably mis-duped :)
[03:14] <Jafet> Bleh, can't find that bug...
[03:14] <Jafet> I closed a lot of bug reports pages to reduce system load.
[03:14] <RAOF> Should be in history, right?
[03:14] <Jafet> Yes.
[03:16] <greg-g> Jafet: sorry, coffee shop wireless is flakey
[03:16] <greg-g> back now
[03:16] <greg-g> did you have any other questions?
[03:17] <RAOF> Anyway, it might be a good idea to file a new bug (it's easier to dupe a bug than to split it in two), mentioning the bugs you think this may be a duplicate of.
[03:17]  * greg-g nods
[03:18] <Jafet> Also, this bug persists across reboots, a kernel downgrade to .24-16 (so it's not limited to the kernel, though I think linux is involved), and reinstalls of xserver-xorg and xserver-xorg-core.
[03:18] <Jafet> That is strange enough.
[03:19] <RAOF> Jafet: As in: you don't have to trigger it?  The down button just sends events regardless?
[03:19] <RAOF> This is looking less and less like my bug :)
[03:20] <Jafet> I triggered it this morning, and since then I have rebooted four times.
[03:20] <Jafet> Hmm, it does sound different now that I've said it.
[03:20] <RAOF> Does this occur in a virtual terminal?  (Ctrl+Alt+F1-F6?)
[03:21] <Jafet> I suspect race conditions in the kernel or other core components underlying all these problems...
 ﻿When Ubuntu boots I am shown a splash screen; I also remove the "quiet" option in grub so that I get a bit of terminal output in between. Might X be started at any point in this timeframe?
[03:22] <Jafet> Because I'm getting ]]Bs in the terminal screen at that time!
[03:23] <Jafet> Er, "^[[B"
[03:24] <RAOF> Jafet: _No_.  X isn't started then (we're not Fedora ;))
[03:24] <RAOF> Does this start in grub?  Or do you need to start Ubutu.  Either way, its not an X problem, and may even be a hardware problem.
[03:25] <Jafet> And yes, it occurs in tty1.
[03:25] <Jafet> Not in grub.
[03:26] <RAOF> Right.  So, probably a kernel problem.
[03:28] <Jafet> So much for my plan B of moving to Debian...
[03:29] <RAOF> Debian has a newer kernel, which may or may not have this already fixed.  Or, it may be worse :).
[03:30] <Jafet> How does the computer remember which key to screw me with, though?
[03:30] <Jafet> Might be, as you said, the hardware.
[03:30] <Jafet> I'll boot into Windows and see.
[03:31] <RAOF> Not a bad plan.
[03:31] <Jafet> Thanks for the help so far.
[03:51] <greg-g> hmmm, windows does take forever to load :)
[04:17] <Jafet> Hi RAOF.
[04:17] <Jafet> The error is entirely reproducible in Windows, and in grub.
[04:18] <Jafet> Sorry for bothering you.
[04:18] <Jafet> Still, this is a weird bug indeed, if it is affected by CPU load.
[04:19] <Jafet> Yet remembers to trigger one key consistently...
[04:19] <RAOF> Jafet: Hardware is really weird.
[04:19] <RAOF> :)
[04:19] <Jafet> I'll need to bug my parents to replace this laptop, I think.
[04:20] <Jafet> And no more Sony products for me.
[04:20] <RAOF> So, CPU load may well be correlated to any number of things; heat, power draw, fan speed, etc.  These things can have obvious or not-so-obvious effects on your hardware :)
[04:20] <Jafet> I realize that.
[04:20] <RAOF> But, yes.  Very, very strange.  Bad Sony :)
[04:20] <Jafet> I tried to cool it with an ice pack this morning, to no avail...
[04:24] <RAOF> Hm.  I've never tried _that_ :)
[04:25] <RAOF> I did recently take my laptop apart and re-apply thermal paste and de-dust the heatsink-fan system.  It didn't much like idling at ~80C.
[04:41] <Jafet> My parents would have a fit to see me taking this laptop apart.
[06:52] <LimCore> hello
[06:52] <LimCore> https://bugs.launchpad.net/ubuntu/+source/scponly/+bug/122715
[06:52] <LimCore> this program doesnt work at all
[06:52] <LimCore> what importance would be good? important?
[07:25] <RAOF> LimCore: It's in Universe, so Medium is pretty much the cap.
[09:50] <mpt> seb128, a while ago you were concerned about the name of the "Incomplete status", saying "I would not be surprised if some go 'why the heck are you closing my bug because I didn't specifiy the version I'm using'".
[09:50] <mpt> Did that turn out to be a problem?
[09:51] <mpt> or do reporters mostly understand what it means?
[09:51] <seb128> mpt: I don't think we got complain about it
[09:51] <seb128> mpt: the bug submitters seem to understand what it means
[09:52] <mpt> ok, cool
[14:18] <bddebian> Boo
[14:32] <hggdh> bdmurray: ping
[15:41] <ruiboon> Hi. Can i get the to triage a bluetooth bug? Using a particular bluetooth dongle,2 applications that uses pybluez gives some error. however other bluetooth applications are fine. User tries another dongle, and all application works. Dmesg output does not seems to suggest anything. What should i do next?
[15:55] <bdmurray> hggdh: pong
[16:06] <bdmurray> mvo: ping
[16:06] <mvo> bdmurray: pong
[16:07] <bdmurray> mvo: I ran across bug 230832 and it might have a patch in it if you could check it out
[16:08] <mvo> bdmurray: thanks, that looks interessting, I will give it a go
[16:09] <bdmurray> mvo: Additionally, I subscribed you to bug 197015 can you pull my change(s)?
[16:10] <mvo> sure, thanks bdmurray
[16:20] <hggdh> bdmurray: can you please renew my subscription to ubuntu-bugcontrol?
[16:33] <bdmurray> hggdh: done
[16:44] <hggdh> bdmurray: thank you, sir
[19:52] <Iulian> Heya pedro
[19:55] <pedro_> hey Iulian!
[21:25] <pochu> jwendell: hi :) out of curiosity, do you think you will be able to fix GNOME #517527 for 2.24?
[22:19] <jdenhaer> I need technical support - but rather complex concerning binary package for kernels: 2.6.24-17-generic
[22:24] <|DuReX|> https://bugs.launchpad.net/ubuntu/+bug/235889
[22:25] <|DuReX|> I can help fixxing it :)
[22:46] <mattik> Hello, I have had very stange bugs every time I have used Hardy Heron
[22:47] <mattik> If I enable restricted drivers and I use kdm or kdm-kde4 screen will be halted and I have to press ctrl-alt-del for rebooting
[22:48] <mattik> The second bug
[22:49] <mattik> If I disable wireless network I cannot get it back any way. The only way is install ubuntu or kubuntu again
[22:49] <mattik> applet is disappeared after this
[22:50] <mattik> I have reported these bugs but anybody doesn't care it. I hope the second release is better
[22:51] <bdmurray> what are the bug numbers mattik?
[22:51] <mattik> I think they are closed
[22:52] <bdmurray> It'd still be possible to look at them
[22:52] <mattik> ok I try to find
[22:58] <mattik> https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/200624
[22:59] <mattik> I'm not sure is it duplicate
[23:01] <mattik> https://bugs.launchpad.net/ubuntu/+bug/210294
[23:02] <mattik> It worked after I disabled it
[23:02] <mattik> before no after
[23:02] <mattik> enabling doesn't work and doesn't bring applet back
[23:06] <mattik> The second point, when I installed Hardy to my desktop computer I cannot log in gnome without safe mode. When I try to report this some put it question and it became old. I think this guy was some ms spy >:
[23:10] <bdmurray> mattik: in bug 210294 you say it works, what happened?
[23:13] <mattik> I disabled wireless network in xp side and I rebooted to kubuntu-kde4. After this applet what shows wireless state was disappeared and I don't get it back. This problem came allways when I tested alpha and beta and I did big upgrade by apt. I installed ubuntu back many times
[23:14] <bdmurray> Have you tried reenabling it on the XP side?
[23:14] <mattik> yes
[23:15] <bdmurray> It'd be good to update your bug report with you findings
[23:15] <mattik> ok
[23:16] <mattik> I am very glad that I can help :) I hope I could speak better english that I can help better. Thank you bdmurray :)
[23:18] <mattik> so how is it digital camera support now?
[23:18] <mattik> My camera didn't work when I tested last time
[23:18] <mattik> No transfer
[23:19] <mattik> I think it was in kde4
[23:19] <mattik> in ubuntu I think it works
[23:20] <bdmurray> kde4 is very young
[23:20] <mattik> ok, we need time
[23:23] <mattik> bdmurray, I close computer now, but if you need confirming or you have question, you allways can mail me address matti.kukkola@gmail.com :) see you