=== micahg1 is now known as micahg
=== asac_ is now known as asac
=== bibinou_ is now known as bibinou
=== bibinou is now known as cappert
=== cappert is now known as bibinou
[03:29] <bibinou> hi
[03:30] <bibinou> IIRC there was a list of "easy-to-fix" bugs of some sort
[03:30] <bibinou> or was it ?
[03:40] <micahg1> bibinou: there is a bitesize tag iirc
[03:40] <greg-g> bibinou: the "bitesize" bugs: https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=bitesize
[03:40] <bibinou> thanks !
[03:40] <greg-g> no problem :)
[03:43] <JanC> actually, I doubt those bugs are bite-size  ;)
[03:44] <JanC> at least some of them
[03:49] <greg-g> JanC: true, all depends on who tagged them bitesize :)
[03:50] <JanC> some of them will require a flamewar to implement, so hardly "bite-size"  ;)
[03:50] <JanC> greg-g: ^^^
[03:57] <greg-g> JanC: hah!
=== plars_ is now known as plars
[06:41] <mac_v> hmmm,... a notification area bug is the gnome-applets project... right?
[06:58] <mac_v> micahg: around? ^ is that right?
[06:58] <mac_v> and the upstream task would be gnome-panel right?
[06:59] <micahg> mac_v: idk
[06:59] <micahg> what is the issue?
[06:59] <mac_v> micahg: Bug #476170 was filed for humanity when it is actually a panel bug > https://bugzilla.gnome.org/show_bug.cgi?id=583115
[06:59] <ubot4> Gnome bug 583115 in notification area "make location of status icons more predictable" [Normal,Unconfirmed]
[06:59] <ubot4> Launchpad bug 476170 in humanity-icon-theme "Panel looks inconsistent when not all monochrome icons load earlier than the others" [Undecided,New] https://launchpad.net/bugs/476170
[07:01] <micahg> mac_v: if upstream it's gnome-panel, it should probably be gnome-panel in LP
[07:01] <mac_v> so i'm a bit confused as to which is the right component to add the also affects to
[07:01] <mac_v> micahg: ah , ok thanks
[07:01] <mac_v> :)
[07:01] <micahg> if that's the same bug
=== maco__ is now known as maco
[07:14] <mantiena> mrand: hi, still online ? ;)
[07:31] <indus> hi
[08:36] <lstep> hello, I've got a bug in a package from a "MOTU", so I can't report it using ubuntu-bugs. And I don't see any related info on the HelpingWithBugs page. How should I report it?
[08:39] <lstep> Could anyone tell me where should I report this bug (https://bugs.launchpad.net/ubuntu/+source/x264/+bug/475933 ). Should I write a mail on the MOTU mailing list (ubuntu-motu@lists.ubuntu.com)?
[08:39] <ubot4> Launchpad bug 475933 in x264 "The library included in the libx264-67 package is libx264.so.68 but should be libx264.so.67" [Undecided,Invalid]
[08:45] <thekorn> lstep, I think you have installed this package from a PPA, correct?
[08:45] <thekorn> lstep, looks like this one https://edge.launchpad.net/~kow/+archive/ppa
[08:45] <lstep> thekorn: hmm, how do I know that? in aptitude show, I don't see any such info :-(
[08:46] <thekorn> hmm, good question
[08:47] <lstep> thekorn: In the package source, there's just the library file and a copyright
[08:47] <lstep> thekorn: packae content I mean
[08:48] <thekorn> lstep, don't know, maybe you have downloaded the package frome somewhere and installed it manually?
[08:49] <lstep> hmm, I don't usually do that
[08:49] <thekorn> lstep, anyway, there is a "contact this user" link on https://edge.launchpad.net/~kow
[08:49] <lstep> thekorn: yes, thanks, I'll do that
[08:49] <thekorn> lstep, I think this is the best way to get in contact with him
[12:32] <bibinou> triage is Hard
[12:38] <matti> ;]
=== _stink__ is now known as _stink_
[14:28] <bibinou> what is the "policy" on offensive comments in bugs ?
[14:28] <bibinou> like this one : https://bugs.launchpad.net/ubuntu/+source/totem/+bug/476512
[14:28] <ubot4> Launchpad bug 476512 in totem "its gay and its horrible" [Undecided,New]
[14:29] <pedro_> bibinou, close the report and point the user to the code of conduct, there's an stock response on wiki.ubuntu.com/Bugs/Responses for that
[14:30] <bibinou> pedro_: status -> invalid ?
[14:30] <mac_v> argh! how can users even title bugs like that and expect a good response :(
[14:30] <ikt> rofl!
[14:30] <pedro_> bibinou, yes
[14:30] <bibinou> thanks
[14:30] <pedro_> bibinou, thank you for helping out
[14:31] <ikt> I have no idea what that particular user would be expecting
[14:31] <bibinou> i'm not fond of those "robotic" responses
[14:31] <bibinou> but i see where they can be useful
[14:32] <pedro_> bibinou, https://wiki.ubuntu.com/Bugs/Responses#Reported%20by%20someone%20not%20respecting%20the%20Code%20of%20Conduct
[14:32] <bibinou> pedro_: done, thanks ! :)
[14:32] <pedro_> np :-)
[14:35] <caolin> I have been trying for 4 days now to convert bug 254130 from a bug to a question but it always times out and does not do the conversion. Could someone else please try this and post the result to bug 438116? Also if it cannot be converted, any suggestions as to workarounds? The only thing I can think of is to treat the bug as if it were a question, provide the reporter wth a final answer and then mark it as invalid.
[14:35] <ubot4> Launchpad bug 254130 in ubuntu "smtp problems, zoneminder? cause of games crashing?" [Undecided,New] https://launchpad.net/bugs/254130
[14:35] <ubot4> Launchpad bug 438116 in launchpad "Timeout Error (OOPS-1367EC560) When Converting Bug into Question" [Undecided,New] https://launchpad.net/bugs/438116
[14:35] <caolin> yes
[14:37] <Pici> caolin: Probably best to ask about that in #launchpad.... although I just clicked on 'convert to a question' and it worked.
[14:37] <Pici> Then again, I'm on edge.lp
[14:38] <caolin> ok, thanks. I wanted to know if the problem was user specific or not.
[14:38] <caolin> I am as well.
=== _stink__ is now known as _stink_
[18:43] <balachmar> Hi, could someone help me to triage a bug?
[18:44] <balachmar> Or should I be @motu for that?
[18:46] <micahg> no, here is the place for triage balachmar
[18:46] <micahg> what's the issue?
[18:47] <balachmar> ok, I am experiencing a bug on my other laptop. It boots, the gdm shows and I can login. But after login it freezes after some time.
[18:48] <balachmar> I am now searching in the logs for the time that still shows on the desktop (which does not add up anymore), but I cannot really find anything
[18:48] <balachmar> I am able to log into the machine using ssh by the way
[18:48] <micahg> which graphics card?
[18:48] <balachmar> intel 855
[18:52] <micahg1> There's a page here on how to troubleshoot X issues: https://wiki.ubuntu.com/X/Troubleshooting
=== micahg1 is now known as micahg
[18:52] <micahg> balachmar: and here's the one on how to report a bug: https://wiki.ubuntu.com/X/Reporting
[18:54] <balachmar> micahg: thanks I will read through the troubleshooting first :)
[18:54] <micahg> great, if you need more help, please come back balachmar
[19:00] <balachmar> I try to run sudo INTEL_DEBUG=batch /etc/init.d/gdm restart, however GDM does not restart, how should I try to get a debug log from the freeze then?
[19:01] <micahg> did you install the intel-gpu-tools?
[19:02] <balachmar> yes
[19:02] <micahg> is this before or after it froze?
[19:02] <balachmar> after
[19:02] <micahg> ok, you need to do this before and then make it freeze
[19:02] <micahg> BTW, are you on karmic?
[19:03] <balachmar> yes, but it freezes quite soon, so I might not be able to enter that info (yeah it started with karmic)
[19:04] <balachmar> I will try booting in recovery mode and start gdm manually
[19:04] <micahg> well, you don't need to wait for gdm to start all the way, you can hit CTRL+ALT+F1 and get to a terminal
[19:07] <balachmar> ok, weird. gdm does not start from recovery mode
[19:07] <micahg> yeah, I'd try regular mode and get to a terminal as soon as X starts to appear
[19:10] <balachmar> ok gdm restarted, now just login and hope for a freeze right?
[19:12] <micahg> yep
[19:26] <balachmar> ok, got the stuff. Bug report is here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/476817
[19:27] <ubot4> Launchpad bug 476817 in xorg "[karmic] X freezes with intel 855GM videocard" [Undecided,New]
[19:31] <balachmar> How should I turn some options off, because I have heard that karmic doesn't user much of the xorg.conf
[19:33] <micahg> balachmar: if you upgraded with a custom xorg.conf, I suggest making a backup and regenerating it
[19:33] <balachmar> I have a backup, but how do I regenerate, because the last time I tried it just removed the xorg.conf (at least it seemd so)
[19:34] <balachmar> mmm, with compiz turned off, the gdm doesn't load...
[19:35] <micahg>  sudo dpkg-reconfigure -phigh xserver-xorg
[19:37] <balachmar> ok, now it also freezes at the gdm with compiz on...
[19:40] <balachmar> Could this "conflicts with ACPI region SMB0" cause a freeze?
[19:42] <micahg> balachmar: did you start with a new xorg.conf yet?
[19:43] <balachmar> no, not yet. It is now checking the HD. And I let it do that because of the few hard power off lately.
[19:45] <balachmar> But now it seemed to have finished the file system check and there is no hdd action anymore, but I can hear me cpu fan spinning loadly. (So probably the cpu is doing something)
[19:49] <kklimonda> any idea why isn't xorg.conf generated by jockey when nvidia drivers are installed? how to debug it?
[19:51] <balachmar> dpkg-reconfigure -phigh xserver-xorg doesn't create an xorg.conf
[19:51] <micahg> weird
[19:51] <micahg> it should
[19:51] <micahg> it should create a new /etc/X11/xorg.conf
[19:52] <balachmar> it doesn't do that on my machine...
[19:53] <micahg> did you use sudo?
[19:53] <kklimonda> it always just worked for me so I don't know how to debug it and I don't even have working computer with nvidia anymore :/
[19:54] <balachmar> micahg: yeah I used sudo
[20:00] <balachmar> micahg: seems that it shouldn't do that anymore: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551082
[20:00] <ubot4> Debian bug 551082 in xserver-xorg "dpkg-reconfigure -phigh xserver-xorg does not create xorg.conf anymore" [Normal,Open]
[20:01] <kklimonda> balachmar: but jockey-gtk doesn't use it afair
[20:01] <hggdh> IIRC, xorg.conf is not really needed anymore
[20:01] <svz90> Hello. I had a quick question. If I see a bug that has "Affects" set to "ubuntu, when it could be made more specific, should I change it, even if I'm not the one who reported it
[20:01] <kklimonda> hggdh: it's needed when you want to use closed driverse
[20:01] <kklimonda> drivers*
[20:01] <balachmar> kklimonda: the remark was not meant as a reply to your question
[20:02] <kklimonda> balachmar: ach, I see - you have a similar discussion :D
[20:02] <kklimonda> sorry
[20:02] <balachmar> no worry
[20:02] <hggdh> kklimonda: let me rephrase: is not needed anymore unless you want out of the defaults ;-)
[20:02] <balachmar> hggdh: Then How do I specify the options of the intel video driver for X
[20:02] <hggdh> svz90: in this case you *do* need it
[20:03] <hggdh> svz90: you should set the affects to the correct package, indeed
[20:03] <svz90> bug doesn't affect me directly. It's a bluetooth bug, I though it might be better off being set to bluez
[20:03] <svz90> instead of gnome
[20:03] <svz90> that's why I wasn't sure if it was correct to change someone else's bug
[20:04] <hggdh> svz90: if bluez is the affected package, yes. Usually "Ubuntu" is a placeholder meaning "I do not know what is the package"
[20:04] <hggdh> or "I do not know, nor I care"
[20:04] <svz90> hggdh: it
[20:05] <svz90> it's that file transfers are corrupt, so I'm guessing that's a problem with the stack.
[20:05] <hggdh> svz90: do you have the bug #?
[20:05] <svz90> 474397
[20:05] <hggdh> bug 474397
[20:05] <ubot4> Launchpad bug 474397 in ubuntu "bluetooth file transfer data inconsistency" [Undecided,New] https://launchpad.net/bugs/474397
[20:05] <svz90> yep
[20:06] <svz90> hggdh: I was googling for info on something else about the stack, and came across it.
[20:09] <hggdh> svz90: I am not sure *which* of the blue* packages it would be -- I do not use bluetooth
[20:09] <hggdh> but certainly it is not Ubuntu
[20:09] <kklimonda> "dlopen: /usr/lib/xorg/modules/drivers//nvidia_drv.so: invalid ELF header" - huh
[20:09] <hggdh> kklimonda: cool
[20:09] <balachmar> ok, you can regenerate the xorg.conf with sudo Xorg -configure
=== micahg1 is now known as micahg
[20:11] <svz90> hggdh: alright, so it's okay to change it? (and for future reference, it's okay to do this in the future with other bugs)?
[20:13] <hggdh> svz90: yes, it is OK. Please also always add a comment on what you change
[20:13] <hggdh> there are some "default" answers that you can copy & paste & adjust for that
[20:14] <svz90> hggdh: Alright. Just wanted to make sure. Thanks for the help.
[20:14] <hggdh> see https://wiki.ubuntu.com/Bugs/Responses (and, more generically, see https://wiki.ubuntu.com/BugSquad/KnowledgeBase)
[20:14] <hggdh> svz90: and thank you for helping
[20:15] <svz90> hggdh: my pleasure.
[20:41] <jcastro> Do we still use regression tags after release?
[20:41] <jcastro> like, if something worked in jaunty but not karmic do we put "regression-potential"
[20:42] <jcastro> https://wiki.ubuntu.com/QATeam/RegressionTracking feels like it's more of a dev release thing
[20:42] <hggdh> jcastro: yes, regression tags are still used
[20:42] <jcastro> ok thanks!
[20:44] <greg-g> jcastro: fwiw: I saw Chris Coulson change one bug's tag from "regression-potential" to "regression-release"
[20:45] <jcastro> yeah I just figured out after reading the page
[20:46]  * jcastro doesn't use them enough to know off the top of his head
[20:49] <greg-g> jcastro: me neither, I just saw that bug update email and thought "oh, neat, that makes sense"
[20:49]  * jcastro nods
=== YDdraigGoch is now known as WelshDragon
[21:39] <balachmar> Could I tempt someone to look at this: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/476817 and maybe tell me if there is something missing?
[21:39] <ubot4> Launchpad bug 476817 in xorg "[karmic] X freezes with intel 855GM videocard" [Undecided,New]
[23:05] <ref_0_> Hello. I have a problem with kubuntu 9.10 (upgraded from 9.04) and I want to report it as a bug in launchpad but I don't know how do that, I do not know which files and info attach.
[23:05] <ref_0_> The problem is that when I copy files (up to 50MB and tested from konsole or dolphin), the system becomes slow and unusable until the task is complete.
[23:11] <ref_0_> kswapd0 and pdflush process appear as "disk sleeping" in system monitor while file is copying.