/srv/irclogs.ubuntu.com/2008/05/14/#ubuntu-bugs.txt

Fallenouasac < you see ? it's what it should be :p00:03
asacyeah ... maybe a bios thing?00:04
asaci have the same ethernet driver here and it works like a charm00:04
Fallenouhum but how do you explain that it works well on windows XP and gutsy ?00:05
Fallenouwithout touching the bios meanwhile00:05
asachard to say ;)00:05
Fallenou=)00:05
Fallenouis it possible ? ^^00:05
asaceverything is possible :)00:06
asacFallenou: when did you upgrade to hardy?00:06
Fallenouon monday00:07
Fallenoubut when i saw that it didn't work well (for the network) i installed from scratch with Hardy ISO CD00:07
Fallenouthe same day00:07
Fallenouso it's not anymore an upgrade00:07
asacFallenou: do you get any process with ps -eaf | grep dhcdbd00:11
asac?00:11
Fallenouyes00:13
Fallenouone00:13
Fallenouroot 5443 1 0 00:31 ? 00:00:00 /usr/sbin/dhcdbd --system00:14
Fallenouis it normal asac ?00:15
asacyes00:17
asaci assigned your bug to kernel package now00:17
asaci'd try to update bios and hope that its that.00:17
asacbut that is just me ;)00:17
Fallenouok thank :)00:18
Fallenoudo you think i should remove/change/add some more information/file on the bug page ?00:18
asacno. if they need more information, they will probably ask00:19
Fallenouok i will check the page everyday00:19
Fallenouthank you for your help and your time :)00:19
Fallenou'im gonna borrow some network card tomorrow ^^00:19
asacmaybe a good idea ;)00:20
Fallenou:)00:20
Fallenouthanks a lot, really00:20
asacnp. sorry for being not more helpful ;)00:20
Fallenouyou gimme your time that's the best you could do :)00:21
Fallenougood evening/night/morning00:21
Fallenoui'm going to bed =)00:21
=== secretlondo is now known as secretlondon
=== jjesse_ is now known as jjesse
Deniz_OgutHello is there anyone who can help me to decide what to do related with a vedy important bug related with xubuntu, Turkish locale. There's a report in launchpad written bya non-Turkish friend but some other people marked it as a duplicate of another bug; for me this is not the case. Would you please mentor me what to do?04:09
JohnPhysanyone having issues with the update to openssh-server on gutsy?04:12
RAOFJohnPhys: What sort of issues?04:12
Savago@all: anyone out there playing with bluetooth services? It seems that SDP is lacking somethings... it breaks with most of clients using serial port profile (ID list 0x1101).04:12
RAOFYour (stupidly compromised) SSH public key being denied?04:12
RAOFDeniz_Ogut: If you believe the bugs are not the same you can unmark it as a duplicate.  At the same time, you should provide information on the bug (which you are removing the duplicate status of) as to why you believe it to not be a duplicate.04:13
Deniz_Ogut@RAOF: Thank you. I'll do so.04:14
JohnPhysRAOF:  http://paste.ubuntu.com/11965/04:14
RAOFJohnPhys: Hm.  I haven't seen that; it's possible that the update is broken.  Have you checked launchpad?04:17
JohnPhysRAOF:  closest I can find is Bug #230147, but that bug is for hardy, which worked for me this morning.  I'm having issues with the gutsy package.04:20
ubottuLaunchpad bug 230147 in openssh "package openssh-server 1:4.7p1-8ubuntu1.1 failed to install/upgrade: " [Undecided,New] https://launchpad.net/bugs/23014704:20
RAOFJohnPhys: Hardy works for me, too.  I'd suggest filing a new bug, with /var/log/dpkg* and other such goodies.04:22
JohnPhysShould I mark it at as a security issue, since the update is a security-related one I think?  Or not?04:22
SavagoI just found the bug (#227429). Is anyone working on this?04:30
JohnPhysRAOF:  Looks like the fix is already up ( Bug #230003 )  Odd that that didn't show up when I searched "openssh-server" but showed up in the bug report.  I guess I have to wait for the fix to trickle over to the mirror I use.04:30
ubottuLaunchpad bug 230003 in openssh "gutsy: openssh-server won't install or upgrade: debconf error - /var/lib/dpkg/tmp.ci/templates has a duplicate field "template"" [Undecided,Fix released] https://launchpad.net/bugs/23000304:30
RAOFJohnPhys: Maybe your mirror hasn't sync'd the new version yet?04:33
RAOFJohnPhys: Gah.  EWRONGCONTEXT.  Sorry.04:34
JohnPhysRAOF:  It's all right, they'll get it soon enough, I can wait for the update.04:41
JohnPhysRAOF:  as far as the ssh security vulnerability, I'm a little confused on the announcement:  https://lists.ubuntu.com/archives/ubuntu-security-announce/2008-May/000705.html  Is there anything I have to do besides upgrade the package?  Will that automatically re-generate the keys that are generated upon installation of openssh?04:48
JohnPhysRAOF:  I understand that if I manually generated any key pairs, those need to be regenerated, but what about automatically generated ones?04:48
RAOFInstalling the package will automatically regenerate your server's host key.04:49
RAOFEverything else is up to you.04:49
techno_freakJohnPhys, it automatically regenrates the keys, but it's better to do it manually again04:49
RAOFtechno_freak: Which keys?  AIUI, it's just the host key it'll touch?04:50
JohnPhysRAOF:  Ok.  I already removed my public ssh keys from the various servers I had them on.04:50
techno_freakRAOF, when it regenerates and again i test it with the dowkd.pl, it reports it to be weak04:50
techno_freakRAOF, i meant the user keys04:50
RAOFtechno_freak: The package won't regenerate user's ssh keys; it can't.04:51
techno_freakRAOF, ah ok04:51
RAOF_Only_ the server's host key will be regenerated.  Any keypairs you've got need manual intervention.04:52
JohnPhysRAOF, techno_freak:  Thanks for the clarification.  Good thing I only have one set of user keys.04:57
techno_freak:)04:58
=== dabaR__ is now known as dabaR
gnomefreakgeser: yes i do i have already fixed my ssh key05:43
LimCorehow to report a general bug that ubuntu fails06:48
LimCorehow to see bug number 2?06:48
=== doko_ is now known as doko
LimCorecommunity needs reality check07:17
LimCoresome people from ubuntu/debian call "trolldot" and gentoo trolls07:17
LimCorewhile ssh bug was introduced solely by debian team (afaik right?)07:17
techno_freakLimCore, what is your problem?07:28
LimCoretechno_freak: X crashes easly07:29
LimCorelet me check will it crash now as well after disabling compiz totally (uninstall)07:29
techno_freakLimCore, file a bug for us to help it get solved07:29
LimCoresigh07:34
LimCoretechno_freak: ok.07:34
james_wLimCore: is there something you are doing to make it crash?07:34
LimCorejames_w: one sec.07:34
LimCoreyes, go to http://tech.slashdot.org/tech/08/04/30/1822237.shtml07:35
LimCoreclick on  "One post"07:35
LimCorethere is this really long pidgin page.  scroll around up and down a bit07:36
LimCoreworks on nvidia (glx-new) amd64 bit07:36
LimCore"One comment"07:36
techno_freakis it your X crash or Firefox crash? neither for me07:36
james_wLimCore: Firefox 3?07:37
LimCorejames_w: yes07:38
LimCoreentire X crashes07:38
techno_freakLimCore, you mean it freezes up?07:38
LimCoreno, it crashes (resets)07:38
LimCoreIm back at login screen07:38
LimCoreIm a devel, I know difference crash vs freez =)07:39
techno_freakhmm, i saw a similar bug07:39
LimCorehttps://bugs.launchpad.net/ubuntu/+source/firefox/+bug/23018307:43
ubottuLaunchpad bug 230183 in firefox "crashes, and resets X (back to login screen)" [Undecided,New]07:43
LimCoredo you also often find important bugs in ubuntu?07:46
Yur1hello08:06
Yur1could anybody help me with understanding of acpi-handling in hardy?08:07
LimCorecan anyone comment on https://bugs.launchpad.net/ubuntu/+bug/230180 please08:08
ubottuLaunchpad bug 230180 in ubuntu "ubuntu needs better QA since major components have big number of serious bugs" [Undecided,New]08:08
RAOFLimCore: I'd comment that it's probably going to be marked invalid.08:09
RAOFBy the title, but I'll read it first.08:09
RAOFLimCore: Basically, that's not very useful.08:10
LimCorewhat other way to confince ubuntu to put more effor in qa?08:10
LimCoreI reported or confirmed number of such critical yet important bugs... I can link to them there08:11
LimCorethe point08:11
LimCoreis to look for systemic, strategic solution.08:12
RAOFAny suggestions?08:12
LimCoreas I written there08:12
LimCorePerhaps it would be nice to create teams dedicated solely to08:12
LimCore1. fixing in any way bugs in critical components. Workaround, older version, patch - no matter what but it really should Just Work08:12
LimCore2. and a team reviewing security related code, especially in main systems like openssh08:12
RAOFWe _already_ fix things when we can.08:13
LimCoreI know.  therefore: "Since Ubuntu is backed up by real company, perhaps it would be possible to invest more into increasing such teams."08:13
RAOFBasically, your suggestion boils down to "do what you have been doing, except better".08:13
LimCoreright08:14
RAOFAnd "make Canonical hire more Ubuntu devs" is not a bug in Ubuntu :)08:14
HobbseeLimCore: find more people.  do it.08:15
HobbseeLimCore: simple, no?08:16
LimCoreHobbsee: no08:16
LimCoreHobbsee: but I like RAOF's way08:16
LimCorehire more devels08:17
HobbseeLimCore: then don't complain, unless you're either going to a) contribute useful effort to the project, or b) contribute money.08:17
LimCoreb)08:17
Hobbseego on, then.08:17
LimCore:)08:17
LimCorecan someone uninvalid my bug report, when I post interesting idea for a solution there?08:18
LimCore(I dont want to univalid my own bug)08:18
Hobbseeis it actually a bug?08:18
Hobbseesounds like something for the idea storm, or a mailing list, or something.08:19
LimCoreany www gate to mailing list for this purpose?08:19
RAOFI don't believe so, no.08:20
Hobbseewww.hotmail.com / www.gmail.com ....08:21
Hobbseewebmail.isp.com ...08:21
techno_freakLimCore, try brainstorm for it rather than launchpad ;)09:12
LimCoretechno_freak: url?09:12
techno_freakLimCore, http://brainstorm.ubuntu.com/09:13
LimCorenice09:13
LimCoreit doenst share login with lunchpad?09:13
stgraberLimCore: nope, not yet09:15
LimCoreafter bootup,  VT-1 contains trash  "kernel alive"  "kernel direct mapping" text.   anyone knows that bug?09:44
LimCorehow to report it, against what package? kernel?09:44
* LimCore reported it in kernel, https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/23020409:49
ubottuLaunchpad bug 230204 in linux-source-2.6.22 "after bootup, VT-1 virtual terminal contains trash "kernel alive" text" [Undecided,New]09:49
=== gnomefre1k is now known as gnomefreak
copyofjohan#20591911:49
copyofjohanhi, I hope I dont disturbe you to much, but I really need a workaround for this bug 205919. Do you have an idea?11:51
ubottuLaunchpad bug 205919 in brasero "Brasero and nautilus-cd-burner cannot burn 4GiB file to DVD" [Undecided,Confirmed] https://launchpad.net/bugs/20591911:51
=== _neversfelde is now known as neversfelde
asacbdmurray: can you please extend bugcontrol-membership of fta?13:09
asacmail doesnt provide that option for him ... or he lost that mail13:09
LimCoresince ubuntu have so many epic failures, like kformula (unusable in 8.04)13:12
LimCorehow about providing easy way to install&use previous version of given program13:13
LimCoreor perhaps this should be done by QA teams... if given appl is too buggy, then put the downgraded version as officiall one (so on aptitute upgrade clients will install the older but usable version)13:13
Hobbseeapt-get install foo=1.3.413:13
* Hobbsee suggests reading before advocating solutions, and also dropping the "people are incompetent" mentality.13:14
LimCorethe point is to allow both versions at once on one box13:14
LimCorefoo-1.3.4  foo-2.0  and foo is a symlink to one of them13:14
seb128what about fix the issues which make the thing unusable rather?13:14
Hobbseeseb128: that requires work, rather than just throwing other people's money at the problem, so LimCore doesn't want to do that.13:15
LimCoreseb128: that will take months at avarage13:15
LimCore"throwing other people's money at the problem" ?13:15
Hobbseesure.  you were talking about it earlier13:16
seb128there is no reason new versions should be that broken13:16
Hobbsee"just get canonical to hire more developers and qa people"13:16
LimCoreHobbsee: using MY money13:16
seb128downgrading is not a real solution13:16
HobbseeLimCore: oh good.13:16
LimCoreseb128: kformula. I used it for 10 seconds and found 2 ciricail bugs13:16
LimCoreseb128: can't export to SVG, and can't read own native format .kfo13:17
LimCoreHobbsee: does the above entitle a bit "people are incompetent" mentality13:17
seb128seems to be a crappy software if they roll new version without testing if it can open things13:17
LimCoreseb128: I just want to export one simple mathml into svg :'(  and it seems impossible in ubuntu... any other appl does that?  other seem to export only to gif and pdf13:18
Hobbseeinterestingly, there don't appear to be any bugs for it on launchpad.13:18
LimCoreHobbsee: that is indeed interesting, as ~10 bugs showed up while I was reporting mine as possible duplicates13:19
Hobbseenothing open, anyway13:19
Hobbseehttps://bugs.edge.launchpad.net/ubuntu/+source/koffice?field.searchtext=kforumla&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_13:19
Hobbseepackage=13:19
Hobbseeyay, launchpad.13:19
LimCorekformulas is part of koffice13:19
LimCorekformula is part of koffice13:19
Hobbseeyes, it is.13:20
LimCorehttps://bugs.launchpad.net/ubuntu/+source/koffice/+bug/6118913:20
ubottuLimCore: Error: Could not parse data returned by Launchpad: The read operation timed out13:20
=== fdd-0 is now known as fdd
Hobbseeah, drat, i can't spell.13:21
LimCoreactually, can someone please confirm my bug?13:21
LimCoreformula is simple:  1. start kformula  2. type in "2+2"   3. file-export test.svg13:21
* LimCore 8.04 amd6413:21
LimCoremy bug is https://bugs.launchpad.net/ubuntu/+source/koffice/+bug/23024313:22
ubottuLaunchpad bug 230243 in koffice "export to svg fails" [Undecided,New]13:22
Hobbsee1.6.5....that's the kde3 branch, isn't it?13:22
LimCoreyes13:22
LimCoreI will test -kde4 in a moment13:23
Hobbseethat's probably why it's not getting much attention from upstream.13:23
LimCoreit is a rare occasion that one application can be trivially installed in 2 versions at once.   My idea was to allow that always easly, not just for kde3/4 transition13:23
seb128LimCore: there is no easy way to do that and that would be lot of extra work for few win13:25
seb128little win rather13:25
HobbseeO.O13:26
* Hobbsee marks an upstream bug. without pain!13:26
LimCoreHobbsee: related to kformula or other topic?13:26
LimCorekformula-kde4 doesnt work as well.. they simple removed the export to SVG.........13:27
HobbseeLimCore: added an upstream bug to one of your kformula13:27
LimCore\o/13:27
HobbseeLimCore: interestingly, http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&product=kformula&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&bug_id=&votes=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&13:27
Hobbseeorder=Importance&cmdtype=doit is the only stuff filed for kformula, that's open.13:27
LimCoreI'm a happy when without any reading and with people are incopetent mentallity I still manage to report meaningfull bugs.13:27
LimCoreok seriously.  Can I at all export mathML file to SVG using ubuntu?13:28
LimCoreHobbsee: I dont understant what you ment by last statement13:29
Hobbseedunno.  check google.13:29
HobbseeLimCore: that query is all the stuff in the kde bugtracker that's open, for kformula13:29
LimCorehttp://tinyurl.com/6377xh13:30
seb128LimCore: try asking on #ubuntu, there is lot of softwares in universe and some people might use mathml there13:30
LimCoreseb128: I ask on serveral channels and searched in synaptic13:31
LimCoreit seems that no.13:31
HobbseeLimCore: no one does kde questions, btw.13:32
seb128you can try abiword, it seems abiword-plugins uses libgtkmathview13:32
LimCoreseb128: good idea13:32
seb128otherwise libgtkmathview-bin might have some tools to do that13:32
HobbseeLimCore: and it's not an area, so far, that canonical has wanted to invest in further, and doesn't seem like it will in future.13:32
LimCoreyou are saying this in reference to what? to investing into say kde bugfixes?13:33
Hobbseeyour open question on kdebase, about compiz.13:33
Hobbseeoh13:33
LimCoreoh right13:33
Hobbseeyes.13:33
Hobbseeeffectively13:34
LimCoreI was thinking13:34
LimCoreyou know vim model?13:34
LimCorepay for vim to vote what to fix13:34
LimCore(or develop)13:34
Hobbseei'm sure you could contract someone to work on kde for you, if you wished.13:35
LimCoreI can just donate myself, but without organized action its ineffective13:35
LimCoreexacly.  one person with 100 usd  -vs- 100000 ubuntu users * 10 usd13:35
Hobbseeso, organise it.13:36
LimCorewhat do you think about this idea13:36
Hobbseesounds good, if someone actually does it.13:36
LimCoreexample: in 2012 5.000.000 linux users payed 5*5.000.000 usd annual license. 15% goes to KDE 5% to kernel 5% to compiz/xgl/etc  [...] 0.004% to kformula   etc13:37
Hobbseego ahead and organise it, then :)13:37
LimCoreok13:37
LimCorein the meantime, do you think its justified that I think that kformula ubuntu developer REALLY did a bad, bad job?13:38
LimCoreU are a devel right? can you set importance of this bug?13:38
seb128you assume that there is a kformula ubuntu developer which might not be the case13:38
LimCoreLatest release:  1:1.6.3-5ubuntu213:39
LimCoreUploaded By:  Jonathan Riddell13:39
seb128upstream did a bad job rolling a buggy new version13:39
LimCoreMaintainer:Maintainer:  Ubuntu Core Developers  Ubuntu Core Developers13:39
* LimCore stupid mouse button13:39
seb128welcome to the kde world, koffice is not only kformula I guess13:39
jdaviesLimCore: doesn't mean he wrote it13:39
HobbseeLimCore: you don't get it.  for the most part, the ubuntu developers don't work on the individual apps.13:39
LimCoreHobbsee: I really do know that13:39
Hobbseeseb128: and neither is kde koffice :)13:39
seb128updating the source package doesn't mean working on all the softwares is ships13:39
jdaviesLimCore: look under Help -> About KFormula for the dev names13:39
* LimCore makes a bitter joke what happens when distro devels apply own patches for dsa (well ok, thats debian)13:40
* Hobbsee makes a bitter joke about users who try to manage everything from their armchairs, and are very happy to throw blame around, seeing as they pay money, so zomg everyhting should be fixed for me, right now.13:40
Hobbseehmmm.  i wonder if i can add a filter on listadmin.13:41
LimCoreHobbsee: if in this case user is not entitled to complain, then when?13:41
seb128complaining is not really constructive13:42
HobbseeLimCore: sure, you can complain.  whether people help you is an interesting question.  especially if you're blaming everyone.13:42
seb128make sure to report issues that's constructive13:42
LimCorebut I see your point Hobbsee. and I dont know what can I realistically do to fix things.. I'm not rich to sponsor entire team to fix all buggs I find13:42
Hobbseeor at least, people who's fault it isn't.13:42
seb128well, complaining that other people don't do that either will not fix those issues13:42
seb128report the issues you find and try to provide require details13:43
LimCoreI do all the time13:43
seb128and try writting a patch if you really want to contribute13:43
askandHi, what are the chanses that bug 147883 will get into hardy-proposed?13:43
ubottuLaunchpad bug 147883 in rhythmbox "Songs that have a space in their path are not imported automatically from watched music folders" [Unknown,Confirmed] https://launchpad.net/bugs/14788313:43
LimCorethen I wait... and wait, and....13:43
seb128askand: I've a hardy update on my disk, I'm just waiting for upstream feedback for the patch I attached to bugzilla13:44
Hobbsee100 / 700 done!13:44
askand seb128: nice, thanks13:44
seb128you are welcome13:44
LimCorekformula-kde4 seem to not have at all SVG export. am I doing something wrong?  perhaps I should report that too?13:44
HobbseeLimCore: do us all a favour, and report it on bugs.kde.org13:45
Hobbseethe developers are there, who actually code the app13:46
LimCoreok13:46
LimCoreok I tried abiword13:54
LimCorehttps://bugs.launchpad.net/ubuntu/+source/abiword/+bug/18703413:56
ubottuLaunchpad bug 187034 in gtkmathview "AbiWord-2.4 crashes when inserting LaTeX" [Undecided,New]13:56
=== dabaR_ is now known as dabaR
bddebianBoo14:31
geserfoo14:33
ograbee14:33
bddebian:)14:33
Hobbseebdmurray: ping15:35
Hobbseebdmurray: you may want to get https://launchpad.net/~sebastian-ro to do something more useful - looks like he's deciding to mark sync and merge bugs as wishlist.  i'm sure you can find other bugs which are far more useful for him to look at, which no one else has seen.15:36
Hobbseepeople wasting their time is never a good idea :\15:37
pck-chemHe's probably doing it out of ignorance, I had no idea dev's used launchpad to track their work until the recent email exchange on the mailing list :/15:39
Hobbseelikely.15:39
Hobbseeof course, the way to stop people being ignorant is to write documentation warning them what not to touch.15:39
pck-chemWe'll, I15:40
Hobbseepck-chem: that's the thing.  we've had 3 contributors in the past couple of weeks who have been repeatedly changing those types of bugs.  yet out of all the bugs, they're only a small part.15:40
Hobbseepck-chem: i'm starting to think that they're going out and looking for them, because, as you rightly point out, most people don't know about them, and most people don't touch them15:41
Hobbseethe chances of multiple people managing to find a whole chunk of bugs that they should be ignoring, which are only a small subset of the reported bugs is quite low.  yet multiple people manage.15:41
Hobbseeand there are still stacks of bugs that people aren't seeing.15:42
pck-chemHobbsee:  Well, I understand, but I'm not getting into it anymore than the emails have already. My personal opinion is that people shouldn't even bother with that kind of stuff when there are hundred of unpackaged/totally untriaged bugs but I can see both sides of the issue here.15:42
Hobbseeexactly!15:42
thekornHobbsee, out of curiosity: can you please give me a bug number of a bug this guy messed up15:49
Hobbseenorsetto: ^15:49
Hobbseelaunchpad isn't letting me see the exact ones.15:49
thekornall bugs he marked as wishlist have none of these dev-teams subscribed15:50
norsetto[16:16] <norsetto> seems like somebody had the great idea to mass-create needs-packaging bugs for all lp hosted projects15:51
norsetto[16:27] <norsetto> scottk: and there is already somebody busy filing them all as wishlist ... so much so for bug triaging15:51
james_wHobbsee: you said sync/merge bugs, but this time the discussion started with needs-packaging, did he move on to others?15:51
Hobbseejames_w: oh, even better.15:52
Hobbseethat's the one category i didn't put in.15:52
* Hobbsee can see all the importance-only changes, but not bugs that they were added to.15:53
Hobbseesilly advanced search.15:53
Hobbseeoh well.  i'm sure that if he wants to create bugs for every piece of software on launchpad that's not in the archives, he can.15:54
Hobbseei'm sure there's more useful stuff for him to be doing, though.15:54
Hobbseeas long as he closes them when the software packages get added to ubuntu, whether those be syncs, etc, or whatever.15:54
Hobbseeso he's not adding to bug cruft, instead of triaging it.15:54
james_wHobbsee: there are two people here, one is adding the bugs, the other is wishlisting them and adding the needs-packaging tag.15:55
Hobbseefun.15:56
Hobbseethe first is wasting his time, effectively, and the second could find more productive things to do, if the first stopped.15:56
hggdhthekorn: see bug 230234 for an example of what Hobbsee is talking about15:58
ubottuLaunchpad bug 230234 in ubuntu "[needs-packaging] stompboxes" [Wishlist,New] https://launchpad.net/bugs/23023415:58
norsettoand apparently none of the two checks for dupes, I can see at least two ....15:59
Hobbseenorsetto: which means that any doc probably wouldn't have helped, as they clearly didn't read it anyway.16:00
hggdhHobbsee: ^^ agree :-(16:01
Hobbseein which case, does something get done about them, before they become more kmos-like?16:01
hggdhthis, I guess, is a question for bdmurray and ogasawara_. I do not have ways of reaching them (none that I have seen publishes email addresses).16:02
hggdhbut I have a bug Seb Rode subscribed to -- I can add a comment asking him to come here16:03
pck-chemSHIT16:06
pck-chemhttps://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=New&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=on16:06
pck-chemsorry for the curse16:06
pck-chemcheck that out16:06
hggdhwell, the good part is only a few got set to wishlist ;-)16:07
pck-chemWhat are those bugs doing on my "These need triaged" search16:08
Hobbseepck-chem: close them, with "if you want to package them, feel free, else you're just creating needless cruft"16:08
Hobbsee:P16:08
hggdhHobbsee: now a question for you -- please do not get me wrong: how can bug triagers decide what is a legitimate needs-packaging, and what is not?16:09
qensehello16:09
Hobbseehggdh: they're all "legitimate"16:10
pck-chemqense: Hi16:10
Hobbseehggdh: however, creating bugs for them, when they're mostly synced from debian, etc, anyway, and when relatively get in thru ubuntu, just adds to ubuntu bug cruft, as no ubuntu people are actually looking to package them, and to close those bugs.16:10
Hobbseehggdh: so, is there any point in filing them, and/or keeping them open?16:10
Hobbseehggdh: particularly when there's no rationale for why we might want them there, etc.16:11
Hobbseehggdh: also, filing needs-packaging bugs for everything in the FOSS world will never scale.16:11
Hobbsee(in terms of everything getting packaged)16:11
Hobbseehggdh: and as was said above, they're not even checking for dupes now - are they planning to coem back every release, and see if we've gotten the package from debian?16:12
Hobbseehggdh: the new packages from debian are on an autosync.16:12
pck-chemWould anyone seriously mind if I "Invalidated" them all because this is not what launchpad is for?16:13
Hobbseepck-chem: not at all.16:13
Hobbseepck-chem: if you do it by mail, you should be able to kill them all in one hit.16:13
pck-chemHows that?16:13
Hobbseesuggest that the guy follows <insert docs here> and works on <random list of bugs>16:13
Hobbseepck-chem: help.launchpad.net/UsingMaloneInterface or something.16:14
Hobbseepck-chem: https://help.launchpad.net/BugTrackerEmailInterface16:14
Hobbseeit changed names.16:14
pck-chemJust making sure we're on the same topic, you want me to close bugs like #230281 because they have no place in launchpad right?16:15
pck-chem23028116:15
Hobbseebug 23028116:15
ubottuLaunchpad bug 230281 in ubuntu "[needs-packaging] dynamite-game" [Undecided,New] https://launchpad.net/bugs/23028116:15
Hobbseepck-chem: because there are other ways to track them, it's unfeasible to file that everything needs packaging, and that these bugs don't get automatically closed if someone in debian packages them, which is often the case, yes.16:16
pck-chemThats what I was thinking, I just wanted to make sure not to massively piss someone off because I closed 30 of their "bugs"16:17
Hobbseeoh, i'm sure you'll annoy him.16:17
hggdhHobbsee: I understand the rationale, and I agree with it -- but I am (was) a developer also16:17
Hobbseebut, if he's going to proceed on a useless path like that, the only real option is that he gets frustrated :)16:17
Hobbseethe more he does of it, the more he gets frustrated.16:18
pck-chemWe'll like I said I think it needs to happen I just wanted to make sure someone would have my back if crap hit the fan.16:18
Hobbseehggdh: true.16:18
Hobbseepck-chem: yeah, we will.16:18
hggdhbut I think we need a a bit more of documenting on the "filling [needs-packaging] bugs16:18
Hobbseepck-chem: mind you, if he hasn't read bugsquad docs, he likely wouldn't be able to read or use enough thought to know how to complain :)16:19
Hobbseehggdh: true.  MOTU has some on it.  However, bugsquad and documentation.....16:19
Hobbseehggdh: you have to get them to agree to it at UDS, else they'll just revert it.16:19
Hobbseelike they did with my edit.16:20
hggdhHobbsee: it is not only bugsquad, but the whole process that will have to be revisited. I think this is partially due to the success we had on Ubuntu16:20
Hobbseelikely16:21
pck-chemhggdh: Agreed16:21
Hobbseethere were discussions in sevilla about it.  unfortunately, little fo it came out16:21
pck-chemI see this as a problem with a non-traditional use of launchpad, not a problem with bugsquad.16:21
Hobbseeyet no one's actually proposed a better solution.16:22
Hobbseeit would be nice if launchpad grows a workflow thing, and we can convert bugs to workflows, etc.16:22
hggdhpck-chem: I agree... and perhaps this was why Hobbsee's edit was reverted16:22
pck-chemand I understand, which is why I said before I see both sides :)16:22
HobbseeOTOH, that wouldn't happen for at least a couple of years.16:22
Hobbseeso finding a solution *now* is a good idea.16:22
hggdhHobbsee: 100% with you16:23
hggdhHobbsee: unfortunately I will not participate in UDS16:23
Hobbseehggdh: why?16:23
pck-chemCouldn't we just make "ubuntu-workflow" a "package" and just report all workflows against that instead of Ubuntu?16:24
hggdhHobbsee: (1) far from me; (2) business conflicts; (3) remember, I am an "incognito" ;-)16:24
pck-chemIts another non-traditional use, but it would keep devs and bugs from mixing in the Ubuntu package.16:25
pck-chem*project not package excuse me16:26
hggdhpck-chem: LP *can* be used this way, all we need is rules and -- perhaps -- a new status (and corresponding finite-machine changes)16:26
james_wpck-chem: it's an interesting idea.16:26
pck-chemhggdb: True but canonical would have to dig into launchpad's internals do you think that could happen on a timely basis?16:27
Hobbseehggdh: pity.  although i doubt that tehy'd insist on real names.16:28
Hobbseepck-chem: giving devs 2 places to check when doing anything.  great.16:28
Hobbseepck-chem: (they check for existing bugs, too)16:28
hggdhpck-chem: it can -- after all, that's the whole idea on having Lp in the first place16:28
Hobbseeit's also an abuse of packages16:28
hggdhHobbsee: yes... given my experience on both sides of the fence, I think I could help16:29
pck-chemHobbsee: Like I said <--lowley triager. Just throwing out ideas.16:29
hggdhHobbsee: it is indeed an abuse of packages, but the current dev usage is also an abuse of bugs ;-) we need to find a common ground16:30
pck-chemhggdh: Thanks, what I was attempting to express.16:31
hggdhHobbsee: in fact -- *where* is the next UDS? I cannot find it online...16:38
james_whggdh: Prague16:41
james_wif you mean the one next week.16:41
hggdhjames_w: thanks. Indeed, quite far from Dallas, TX :-) and I am back from Paris for good :-(16:42
hggdh(darn! I *was in Prague last November!)16:42
james_whggdh: when we were all in Boston, MA? :-)16:44
pck-chemanyone know what to report bad iso's against? I've always just passed these over. bug 230189 for example16:52
ubottuLaunchpad bug 230189 in ubuntu "Ubuntu 8.04 amd64 image file distrubuted is currupted" [Undecided,New] https://launchpad.net/bugs/23018916:53
bdmurraypck-chem: I'm looking at the bug but it seems unlikely16:54
stgraberthe images are ok, so I would blame the user's burning software16:54
bdmurrayThey should check the md5sum of the iso they downloaded16:55
stgraberlooks like the problem here is Roxio giving errors, so clearly not an Ubuntu bug16:55
bdmurrayAnd it'd be helpful if you found out the url that used to download it16:55
pck-chemThey said three different sites, three different softwares failed. Thats why I felt this was possibly legitimate16:56
ffmpck-chem: They have a bad burner.16:57
bdmurrayffm: They said 3 different systems16:58
ffmbdmurray: Ah.16:58
stgraberbdmurray: packing your stuff for Prague ? :)16:59
pck-chemAgain my question, should I report it against a certain package? or just leave it Ubuntu?16:59
ograstgraber, who is not :)16:59
bdmurraystgraber: yep16:59
stgraberogra: those not coming to FOSSCamp :)17:00
ograah, well, they can package later :)17:00
ogra*pack17:00
ogra.oO(to much work in my head)17:00
bdmurraypck-chem: just leave it to Ubuntu but it'd be good to get some more information out of the reporter17:01
pck-chembdmurray: roger. Quick question I've been meaning to apply for bugcontrol can you handle that now or should I send the email?17:02
bdmurraypck-chem: Could you e-mail it to me?  I should be packing now.17:04
pck-chembdmurray: Sure, have fun in prague.17:04
greg-gneed assitance on bug 198292 , specifically, should I mark this as an intrepid milestone so it gets looked at/fixed before that round of dist-upgrading?17:07
ubottuLaunchpad bug 198292 in motion "Hardy upgrade - motion halts upgrade" [Medium,Confirmed] https://launchpad.net/bugs/19829217:07
bdmurraygreg-g: This is affects gutsy2hardy too right?17:08
greg-gbdmurray: correct17:10
greg-gand I just took a look at all bugs reported against motion, there are at least 3 other dupes there17:10
bdmurraySo it might be good to have it looked at for 8.04.117:10
greg-gah, yeah, forgot about that release17:11
greg-gso should I milestone it?17:11
bdmurraySo you could nominate it for Hardy, and I'll approve it.17:11
greg-gwill do17:12
greg-gand done17:12
bdmurraythen you could milestone the Hardy task or I'll do it17:13
LucidFoxseb128: reuploaded f-spot debdiff17:13
greg-gto 8.04.1 correct?17:13
seb128LucidFox: thanks17:13
pck-chemHow long does it normally take malone to respond to email commands? I've waited about 15 minutes now and received neither a failure or success message.17:14
bdmurraygreg-g: right and it seems status and importance aren't inheriteed17:14
bdmurraypck-chem: did you gpg sign the e-mail?17:14
pck-chembdmurray: Yessir. The help said if I didn't I would at least receive a failure email.17:15
bdmurraypck-chem: if you pastebin the e-mail I could look at it.  15 minutes should be enough17:16
greg-gbdmurray: done17:17
pck-chembdmurray: Pastebin ?17:17
greg-gbdmurray: thanks for taking the time, I know you're busy17:17
greg-g!paste17:17
ubottupastebin is a service to post multiple-lined texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu.com (make sure you give us the URL for your paste - see also the channel topic)17:17
greg-gpck-chem: ^17:18
pck-chemhttp://paste.ubuntu.com/12076/17:18
bdmurraypck-chem: What e-mail address did you send it to?17:19
pck-chem230127@bugs.launchpad.net17:19
pck-chembug 23012717:20
ubottuLaunchpad bug 230127 in sound-recorder "Sound recorder doesn't work" [Undecided,New] https://launchpad.net/bugs/23012717:20
pck-chemwhoops17:20
pck-chembug 23027117:20
ubottuLaunchpad bug 230271 in ubuntu "[needs-packaging] dbp" [Undecided,New] https://launchpad.net/bugs/23027117:20
pck-chemwent dsylexic there.17:21
bdmurraywhat is your launchpad username?17:21
pck-chemPatrick Kilgore17:21
bdmurraypck-chem: is the gpg key you signed your mail with the same one in launchpad?17:24
pck-chembdmurrary: Yes sir.17:25
LimCorebtw, are all developers needed to create new ssh keys?17:25
ffmLimCore: Yepper.17:26
ffmLimCore: Assuming you were affected.17:26
LimCoreI ment ubuntu developers17:26
LimCorewill they all create new keys17:27
ffmLimCore: Yeah, assuming _they_ were affected.17:27
LimCorefor themselves when managing ubuntu repository17:27
ffmLimCore: Packages are signed with gpg, so no compromise there.17:27
PiciLP removed the ssh keys.17:27
ffmLimCore: Repos are intergrated with lp's ssh key manager.17:27
ffmIt's very nice actually.17:27
bdmurraypck-chem: hmm, I'm not sure then17:28
pck-chembdmurray: Old fashioned way I guess. Thanks for trying.17:29
bdmurraypck-chem: I'm not certain marking that bug as Invalid is the best idea17:33
pck-chembdmurray: What should happen then? We had about a half hour discussion earlier. This guy is cluttering up launchpad.17:34
hggdhpck-chem: this bug 230127 is interesting... needs-packaging for something that does not even have code available17:35
ubottuLaunchpad bug 230127 in sound-recorder "Sound recorder doesn't work" [Undecided,New] https://launchpad.net/bugs/23012717:35
hggdhdarn it! now it is _my_ time to go dyslexic17:35
pck-chemlol17:35
bdmurrayMy concern is there is a lot of documentation in the wiki that says filing a needs-packaging bug is the right thing to do17:36
pck-chemAll of these submissions are confusing, unpackage, and taking up a lot of real estate on https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=New&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=on17:36
bdmurrayhttps://wiki.ubuntu.com/UbuntuDevelopment/NewPackages17:36
pck-chemWhich is the primary link for finding unpacked/new bugs17:36
hggdhbdmurray: how can we package something that does not even been written yet?17:36
hggdhs/does/has/17:36
bdmurrayMy point was more the idea of closing needs-packaging bugs as Invalid17:37
hggdhyes, I agree, and I asked Hobbsee the same -- how can bug-triagers mess with dev stuff?17:38
bdmurraypck-chem: If you added importance not wishlist to your query would that help.17:38
bdmurrayI could wishlist the needs-packaging bugs fairly quickly17:39
pck-chembdmurray: I got this link from the wiki, should I update it there as well?17:39
pck-chemand should I set needs-packaging to wishlist in the future?17:39
bdmurraypck-chem: regarding the wiki url that'd be great17:40
hggdhpck-chem: how to deal with [needs-packaging] is what is going to be discussed at UDS17:41
bdmurrayhggdh: cool, I missed that in the backscroll then17:41
hggdhI would recommend to wait until UDS is done (and -- hopefully -- an agreement has been reached on how to deal with dev bugs)17:42
pck-chemHmm found another report about bad amd64 8.04 image...17:43
hggdhbdmurray: do you have a way of contacting the triagers that are changing the dev bugs?17:43
bdmurraytheir e-mail address is in the bug mail they send17:44
bdmurraySo, yes17:44
* hggdh does not subscribe to all bugs updates anymore... got buried in them...17:45
* thekorn waves17:45
hggdhbdmurray: just went to lists.ubuntu.com, and looked up the archives of ubuntu-bugs: no archive after March 2007!!17:47
bdmurrayhggdh: only the mboxes are available17:47
hggdhbdmurray: where are they?17:48
bdmurrayadditionally gmane carries the ubuntu-bugs mailing list17:48
hggdhshould we then update  https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs to point to gmane for archives?17:49
bdmurrayI'll add that to my todo list17:49
hggdhI guess I do not have authorisation  to change it?17:50
bdmurrayI think only the mailing list admin would17:50
hggdhah well.17:51
hggdhmdz, I guess17:51
thekornwow, is bug 230234 really the reason for 2 hours of a "don't touch workflow bugs"-discussion?17:51
ubottuLaunchpad bug 230234 in ubuntu "[needs-packaging] stompboxes" [Wishlist,New] https://launchpad.net/bugs/23023417:51
hggdhthekorn: I think it is just one of a sequence17:51
thekornIMO, the triager did nothing wrong17:53
hggdhseb128: hello, and are you aware of any problems with evo and gnome-keyring?17:54
mmm4m5mhi all. I think I found a bug. Does someone want to check it? This is not working:  dialog --editbox "file_name" 20 20 >/dev/tty17:54
thekornno chance for him to know if this is a packaging bug or not, such a report looks more like invalid for me17:54
mmm4m5merror message is: 'Segmentation fault (core dumped)'17:54
hggdhthekorn: I do not completely disagree, but it just shows that we really, really need to get some sort of agreement done at UDS17:55
* pck-chem can't wait until they figure out workflow bugs because god knows we've talked about it enough.... 17:55
mmm4m5mI am using ubuntu gutsy17:55
seb128hey hggdh, what kind?17:55
seb128hggdh: we have "evolution can't store different password for different protocols on the same server"17:55
seb128hggdh: is, smtp and pop on the same server using different password17:56
hggdhseb128: k, not this, so it is probably new: sometimes my evo hangs17:56
seb128hggdh: and we have "evolution forget the passwords when using gpg"17:56
hggdhI have been running under gdb, and a bt on the hang shows gnome-keyring driven, but in wait17:56
hggdhguess its brand new, then :-(17:57
hggdhseb128: is the gnome-keyring a Ubuntu change, or was it done upstream?17:57
seb128hggdh: upstream, we just switched recently to it though17:59
thekornhggdh, but the agreement can not be to add 100 exceptions to the howtotriage wiki-page, like dont't touch bugs with subscribers ..., with tags ..., with titles like ...17:59
seb128hggdh: I didn't want to ask users to re-enter their passwords17:59
seb128hggdh: but mbarnes added passwords migration code to the gnome-keyring in 2.22.1.117:59
thekornhggdh, it's more the devs who have to think about their workflow and usage of LP17:59
hggdhseb128: I agree, and I saw the dialogs. I wil dig into the bt18:00
seb128ok18:00
hggdhthekorn: I would humbly suggest we need to collaborate -- a common solution would benefit all18:00
thekornhggdh, I agree18:01
hggdhthekorn: for better or worse, dev uses LP bugs, possibly because this is the only thing they could get that would "work"18:01
hggdhso methinks a meet-in-the-middle would benefit all. I think bdmurray or ogasawara_ will drive this at UDS, and hopefully we will all be set18:03
thekornhggdh, IMO it would really help if they could point us to messed up bugs and a percentage of workflow-bugs and wrong triaged ones18:03
hggdhseb128: one think I noticed after upgrading to 2.22.1.1 is that every so often, on a new run of evo, I would be asked to deny/one/always authorise evo to look in the g-k storage. I would expect that this would be done just once, the first time evo came up with g-k integration. This is weird, and I cannot account for it18:05
seb128hggdh: well, on the first keyring use in your session you need to unblock the keyring if you use autologin18:06
hggdhthekorn: I agree. So far I only saw one bug that scottk blasted the triager.18:06
hggdhseb128: yes, but I got the prompts for all my emails, and on _multiple_ evo sessions (one different email per session)18:07
seb128hggdh: are you sure those are keyring prompts?18:07
seb128hggdh: do you have a screenshot showing one of those?18:07
hggdhseb128: sure -- no. The dialog does not state who is asking for it. But it was asking to allow/deny access to the email account password. And, no, unfortunately I did not screenshoot it18:08
* hggdh is rather slow lately18:09
seb128ok, deny or allow access seems a keyring thing18:09
seb128otherwise you would get the password text entry and the checkbox to store the password18:09
hggdhyes, this is why I thought of keyring18:09
seb128I start thinking we should revert the keyring use18:09
seb128though have passwords not encrypted is not optimal either18:09
hggdhclear-text (or xor-ed) passwords is really not cool18:10
hggdhbut I agree with you: I wonder if this is the moment for g-k integration18:10
hggdhbut I have not seen anybody else complaining about this hang I got, so... there is still a chance18:11
hggdhbut I saved the core on the last hang, so I can gdb back into it. I will try it, and see what I find18:12
thekornbdmurray, if you have a minute, can you please renew my u-bugcontrol membership18:13
geseranyone an idea what to do with bug 230350 till LP gets fixed? ignore?18:21
ubottugeser: Error: Could not parse data returned by Launchpad: The read operation timed out18:21
james_wgeser: what's the bug, lp is timing out for me?18:32
james_wor is that what you mean?18:32
sectechAnyone know gnome-system-monitor well?  I am triaging an issue that claims the free diskspace is being reported incorrectly... I was just wondering how they calculated it... 1MB = 1024K or 1000K?18:47
sectechdf claims I have 30.0GB free and system monitor says 2918:47
sectechbug #23037918:47
ubottuLaunchpad bug 230379 in gnome-system-monitor "System Monitor shows wrong available disk space." [Undecided,New] https://launchpad.net/bugs/23037918:47
CarlFKBug #2230118:52
ubottuLaunchpad bug 22301 in partman-md "Install -- Raid setup cannot see all of my RAID partitions" [Medium,Confirmed] https://launchpad.net/bugs/2230118:52
CarlFKbg #2230118:52
CarlFKbug #2230118:53
CarlFKcookie.18:53
geserjames_w: exactly, someone added so many tasks that LP can't handle the bug anymore :(18:54
james_wah, ok.18:54
james_wIs that the Original-Maintainer bug?18:54
CarlFKanyone want to poke at a 3 year old bug?18:55
ogrageser, please invalidate many of these packages listed there are not even in debian18:56
* ogra points to ubuntu-calendar-*18:56
ograthat script is missing checks first place18:57
geserogra: I hope the email interface still work on this bug18:57
hggdhCarlFK: which bug?19:02
CarlFKBug #2230119:04
sectechgnomefreak, you around?19:04
ubottuLaunchpad bug 22301 in partman-md "Install -- Raid setup cannot see all of my RAID partitions" [Medium,Confirmed] https://launchpad.net/bugs/2230119:04
hggdhCarlFK: I see no updates since 2007. Are you suffering from it?19:06
CarlFKhggdh: yes19:07
CarlFKhggdh: I dumped all my config stuff here http://dev.personnelware.com/carl/temp/May14/b/dhcp11/19:07
CarlFKand did the ln workaround19:07
hggdhdid it work?19:07
CarlFKyup19:08
hggdhwhat Ubuntu version you are running?19:08
CarlFKhardy19:08
hggdhCarlFK: thanks. Can you please update the bug with your experience? It is indeed good to know it is still present in Hardy.19:09
CarlFKwill do19:09
hggdhCarlFK: and I will set it to triaged -- all we can do here19:10
sectechhggdh,  you wouldn't know how they calculate the free diskpace in gnome-system-monitor would you? :P19:15
greg-gsectech: I'm not sure how they calculate it, but it looks like it would be in the disks.cpp file in the source19:24
hggdhsectech: sorry, no. But I guess looking at the code should give us it19:25
* greg-g is looking right now, but it looks like they are calling some premade function, not sure yet19:26
sectechI could dig through the source code...  29GB is pretty close to 30GB though...  I'm not sure if they consider some hd space reserved or not19:26
sectechAt least I'm doing better then the reporters "0MB free"19:27
hggdhsectech: on the source, if the disk being looked at is not a real device, it is all set to zero19:33
sectechAhhh I see19:34
hggdhCarlFK: please tar/zip your config, and attach it to the bug -- this way it will survive more than 2 weeks19:35
hggdhsectech: what is the bug #?19:36
sectechhggdh,  23037919:36
sectechIt looks like this guy has a laptop...   I don't have any hardware info added with the bug though19:37
sectech(just going by the screen shot)19:37
hggdhsectech: it might be interesting to find out what the filesystem tab shows19:39
hggdhsectech: but this difference does not really sound like being a MiB vs MB19:40
sectechSee I didn't know that if gnome doesn't see the device as real it will set it to 0..(like you said)...I bet you that's what's happening19:41
sectechI'll ask for the output of pci -vvv and a screensnap of the filesystem tab19:42
sectech.... might help if I had the laptop make/model as well... it might be an existing bug19:42
sectechMy battery is running low, time to head home... bb later19:45
\shg'day20:30
jderemerhello20:30
jderemer:)20:30
greg-gello20:31
\shguys, a bug report with a stack trace of a stable package and no .crash report != "invalid bug report"20:31
\shplease ask people for the steps of reproducing it...but don't "invalid" the report, because it's just like a "close and get rid of the crap report"20:32
\shthe "stack trace" is more valuable for us...to determine what we have to ask in future...or what you "bug triagers" should ask the customer :)20:33
hggdh\sh: which bug?20:36
\shbug #23043920:36
ubottuLaunchpad bug 230439 in yelp "yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document))" [Undecided,Incomplete] https://launchpad.net/bugs/23043920:36
\shhggdh: greg-g is involved20:36
greg-gI took care of the situation on the LP side of them (reopened, asked for information)20:37
hggdhthanks, \sh, greg-g. Let me look at it anyways20:37
greg-gnp20:38
\shgreg-g: read -motu...don't let me be misunderstood20:38
hggdh\sh: there is no stack trace there20:39
hggdhand, it seems, no .dbgsym or dbg20:39
\shhggdh: stacktrace hmm...backtrace with less debug symbols...20:39
hggdh\sh: backtrace with *no* debug symbold :-)20:40
seb128\sh: the reply on this bug was correct20:40
seb128\sh: and that's duplicate20:40
\shseb128: TBH, no...20:40
greg-gseb128: there are others like it, but I couldn't find a duplicate20:41
\shseb128: ** Yelp:ERROR:(yelp-document.c:217):yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document)) is more then "no debugging symbols"20:41
seb128\sh: we don't care, we get too much bugs, crashes should be send using apport so they are in the autoduplication database20:41
greg-gthere are others with the same amount of information that were forwarded upstream and set at triaged20:41
seb128greg-g: that was a mistake then20:42
\shseb128: hardy is no apport without manual intervention...please..20:42
greg-gsee bug 22014220:42
ubottuLaunchpad bug 220142 in yelp "Yelp:ERROR:(yelp-document.c:275):yelp_document_cancel_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document))" [Medium,Triaged] https://launchpad.net/bugs/22014220:42
hggdhseb128: isn't apport disabled on hardy nowadays?20:42
seb128did you guys read the stock replied used to close the bug?20:42
seb128it's mentioned there20:42
greg-gyes, apport is disbaled by default, and this reporter enabled apport and reproduced the crash but no .crash file was created20:42
jderemeryes i enable apport20:43
greg-gjderemer == the reporter20:43
seb128I still don't care, he should use file an apport bug or attach a debug stacktrace20:43
jderemerand i just dis a valgrind log20:43
\shseb128: the reporter is in here...and we hopefully file another bug report against apport20:43
seb128we get a zillion bug a week20:43
jderemerseb128: hey ...20:43
seb128and having useless stacktrace is of no use there20:43
jderemerseb128: then tell me what you want20:43
seb128jderemer: hi ;-) nothing personal, but this bug bring no useful informations and create extra work20:43
jderemerSeb128: saying you dont care doesnt help... just fustrates me20:43
greg-gso instead of closing it and being done, we should ask him to do a valgrind no?20:44
seb128no20:44
hggdhjderemer, greg-g we need to have the debug symbols20:44
seb128jderemer: open an apport bug, figure why it's not working and then open the bug using apport20:44
greg-gthen if A) the application crashes but B) no .crash file is created the what should I ask him to do?20:44
hggdha bt/stacktrace without debug symbols is not worth the virtual paper20:44
seb128jderemer: or install libglib2.0-0-dbgsym libgtk2.0-0-dbgsym yelp-dbgsym and get a new stacktrace20:44
jderemerwhat do i need to do to get the symbols20:44
jderemerok20:44
jderemerwill do20:45
seb128greg-g: to file a bug against apport, fix his installation and then open a decent crash bug using apport20:45
greg-g"fix his installation" meaning what?20:45
seb128or to get a debug stacktrace installing the required dbgsym packages which depends of the stacktrace20:45
\shseb128: that's I'm sorry to say "bullshit"...having a bug in apport is not the fault of a user...the bug report is valid and usable20:45
seb128greg-g: whatever the apport maintainer will figure is buggy and make apport not work for him20:46
hggdhjderemer: please also see https://wiki.ubuntu.com/DebuggingProgramCrash20:46
seb128\sh: no it's not usuable, it has no debug information20:46
jderemerhggdh: im there now :)20:46
\shseb128: it has more debug reports in it then a stupid glibc crash..20:46
jderemerhggdh: this part will take a minute20:46
hggdhjderemer: take your time20:46
greg-gif it has no debug information then why go around the issue and start with apport instead of asking to install the -dbg packages? (or am I missing something)20:46
seb128\sh:20:47
seb128"Program received signal SIGABRT, Aborted.20:47
seb128[Switching to Thread 0xb6d08940 (LWP 6817)]20:47
seb1280xb7f9e410 in __kernel_vsyscall ()"20:47
hggdhjderemer: also install yelp.dbgsym20:47
jderemerya.20:47
seb128\sh: do you read consider that an useful stacktrace?20:47
\shseb128: yes...having the reporter the say of how reproducing it20:47
seb128\sh: you should teach me how to track bug from a such stacktrace then20:47
LaserJockthe guy wrote steps to reproduce, it should at least be looked at before marked Invalid out of hand20:47
seb128\sh: do you get the issue doing "going back to the first page opened in yelp"?20:47
seb128LaserJock: no20:48
seb128we have too many bugs to spend hours getting the details for submitter20:48
LaserJockthat's just crap20:48
seb128we accept detailled desktop bugs or not20:48
seb128well, have to handle several hundred bugs a week and we will talk about it again20:48
\shseb128: question: how do you get bugs fixed in server environments?20:48
greg-gI was willing to do the work to get this report up to snuff20:48
LaserJockthen don't provide the tools to do so!20:48
LaserJockif you can't handle the volume remove apport20:49
seb128the other alternative is that we just stop to care, declare that bugs are useless and stop reading those20:49
greg-gfalse dichotomy20:49
seb128LaserJock: it's not enable in stable, that bug has not been filed using apport20:49
LaserJockseb128: it should *be* there if you don't want people using it20:49
seb128LaserJock: ? that's not coherent20:50
LaserJockeverybody is told to use apport, so the user enables it and then get's rejected for doing so20:50
\shreally...I have bug reports with less info then this to bugfix apps...which are written in flash crap...this info in the bug report is more worth then bug #120:50
ubottuLaunchpad bug 1 in ubuntu "Microsoft has a majority market share" [Critical,Confirmed] https://launchpad.net/bugs/120:50
seb128LaserJock: where did you get somebody sending an apport bug rejected?20:50
seb128LaserJock: this bug has not been sent using apport20:50
jderemerim running into an issue with the install of libgtk2.0-0-dbgsym and libglib2.0-0-dbgsym20:50
LaserJockseb128: this guy sent the bug via apport20:50
seb128no he doesn't20:50
hggdhjderemer: what is the issue?20:50
seb128or the bug would have the distribution and packages version20:51
jderemerwants versions that arent in the repository yet..20:51
seb128and the environment20:51
hggdhLaserJock: it was not filled via apport20:51
seb128and the stacktrace20:51
jderemerhggdh:   libglib2.0-0-dbgsym: Depends: libglib2.0-0 (= 2.16.3-1ubuntu1) but 2.16.3-1 is to be installed20:51
jderemer  libgtk2.0-0-dbgsym: Depends: libgtk2.0-0 (= 2.12.9-3ubuntu4) but 2.12.9-3ubuntu3 is to be installed20:51
LaserJockjderemer: did you use apport or not?20:51
greg-glets try to help him work through his present problem first20:51
jderemerlaserjock: apport did not give me any files20:51
hggdhjderemer: look for the .dbg packages20:51
hggdhit seems dbgsym generation is running behind20:52
LaserJockwe should at least ask for information rather than rejecting it out of hand20:52
jderemerhggdh: yea.. the yelp one installed find20:52
hggdhLaserJock: look at bug 23043920:52
seb128jderemer: stable update candidates might not have the dbgsym available yet20:52
ubottuLaunchpad bug 230439 in yelp "yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document))" [Undecided,Incomplete] https://launchpad.net/bugs/23043920:52
LaserJockhggdh: I have been20:52
hggdhLaserJock: this is not an apport bug20:52
seb128LaserJock: the bug has been rejected asking to send a new one using apport and giving explanations on how to do so20:52
seb128and explaining why it has been rejected20:53
LaserJockbut why should it be rejected?20:53
seb128because it's useless20:53
seb128it has no debug information20:53
LaserJockbut it can be made better20:53
LaserJockbut rather than do any work we just Invalidate it20:53
seb128well, apport will open a new bug20:53
jderemerseb128:  i dont agree. it makes the user feel useless20:53
seb128yes, because apport doesn't attach to new bugs20:54
jderemerseb128:  expanding information is easy20:54
\shseb128: "If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart." is the explanation of "how do I enable bloody apport on a stable release" when it gives me enough knowledge about a null pointer assignment and crash?20:54
seb128jderemer: sorry to do that but you are filling a duplicate without debug information, that creates extra work for everybody for no win20:54
jderemerseb128: i spent 20 minutes looking at bug20:54
seb128jderemer: not your fault but that's the case and that's why we ask for apport bugs which are decently handled20:54
jderemerseb128: didnt see any dups20:54
\shhey...if I can't grep or vi the stupid source...I'm not a dev...I'm a stupid working horse...and should really retire20:55
greg-gseb128: which is the duplicate? (have to ask)20:55
\shthe error report comes from the (let's say it kde/qt wise) qdebug line..and tells me where it crashed20:55
seb128\sh: what null pointer assignment?20:56
\shthe reason WHY it crashed needs to come from the reporter...and it's obviously missing...whereas the triages needs to ask "how did you bloody do it?"20:56
seb128\sh: no, we need a bug open using apport, that's the only way we manage to duplicates handling20:57
seb128if everybody file non debug crasher manually the retracer don't register the stacktraces and we have to do the work20:57
seb128that doesn't scale20:57
seb128that might suck but that's the best we can do desktop wise with the ressources we have20:57
\shseb128: read the stupid error message..this warning is a NULL POINTER ASSIGNMENT warning...there is something wrong, and it stupidly throwas a debug message on STDERR...20:58
seb128and that's why we ask people to use apport20:58
\shseb128: as long apport is not enabled by _default_ for stable releases...we need to use more brain instead of closing and throwing away bugreports20:58
\shseb128: I do agree with you for devel releases.20:59
hggdh\sh: then we need more physical bodies to add up20:59
seb128\sh: read the report, the reply just ask to enable apport, and report the bug again using it, what is wrong there?20:59
greg-gbecause he did and no .crash file was created20:59
* ogra shudders imagining seb128 stuffing bodies into LP20:59
seb128\sh: we are not really interested by stable crashers to be honest, 98% of those are duplicates from crashes which have been sent during the unstable cycle21:00
\shIf you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.21:00
\shIf you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.21:00
\shIf you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.21:00
\shplease..do read the lines and tell me I'm not stupid...21:00
jderemerhggdh: its uploaded21:00
\shwhat should I bloody do : touch "/etc/default/apport" and "/sbin/reboot"21:00
seb128\sh: read https://wiki.ubuntu.com/Bugs/Responses maybe?21:00
\shseb128: really...I don't care about wrong docs21:01
seb128\sh: and suggest improving the wiki page rather than blame people for using the stock reply21:01
\shseb128: many of the docs are doomed and not trying to reach reality..really21:01
seb128\sh: you are not trying to reach reality either21:01
seb128\sh: it's not possible to deal with the hundred of useless stacktrace we get every week without asking some efforts from submitter21:02
seb128\sh: those efforts being to use apport21:02
seb128it's not too much to ask21:02
hggdhjderemer: we are still missing some data21:02
seb128and it gives lot of extra informations21:02
jderemerseb128: once again this effort21:02
seb128and make everybody's work easier21:02
jderemerseb128:  your as ass if you say im not trying21:02
hggdhjderemer: after you get the SIGABRT, please type in the GDB session 'bt full'21:02
jderemerhggdh: ok21:03
hggdhand then type in 'thread apply all bt'21:03
hggdhjderemer then please upload the output21:03
seb128jderemer: I don't say that, as said before it's nothing personal, we just get hundred of bugs every week and there is a bunch of us triaging those, it's just not possible to do the efforts for the submitters21:04
jderemerhggdh:  that help at all?21:04
jderemerhggdh: didnt seem to spit out much info..21:05
seb128jderemer: so either we do energetic triaging and ask submitter to use apport or we give up and stop reading bugs because that's too much things and it's not workable21:05
hggdhjderemer: let me refresh it21:05
\shseb128: do you really know how many false positives we have and dealing with? if we would close all those bugs with "invalid, please use this tool...if you can't go away"...I do trust people who reply in time (let's say 1 or two 2 days) but closing them randomly because "it doesn't in my workflow" just doesn't work21:05
hggdhwow21:05
jderemerseb128: im not saying you get a lot, im saying im here... im putting the effort..  just help21:05
hggdhthat is cool... \sh, there you go21:05
seb128jderemer: if you comment here on the bug saying apport doesn't work we will tell you how to get a stacktrace or fix apport21:06
hggdhhuh... I am referring to the bug21:06
seb128jderemer: marking the bug "invalid" is just a way to tell that it is of no use for us right now, it can be reopen21:06
jderemerif invalid, i doubt youll ever look at it again21:06
jderemer:(21:06
jderemeror few ppl do21:07
hggdhjderemer: it is invalid until you (for example) reopen it with more data21:07
\shseb128: marking "invalid" is the only way for LP to mark it as "this bug report is closed"21:07
seb128\sh: not sure who you call "we", but I don't think you can tell we are doing a bad job on desktop bugs21:07
seb128\sh: and that's why we use it ;-) because we close things which are of no use21:07
\shseb128: bug is bug, no need to divide it into desktop server or whatever bug21:07
seb128\sh: and we reopen when they are of interest again21:07
seb128\sh: well, I'll not speak for packages you maintainer but it works fine for desktop bugs, we close the bug because apport will open a new bug and not attach to an existant one and that the new one will have extra informations21:08
hggdh\sh please look at the bug, and see if there is enough data for you21:08
jderemerhggdh: didnt think i could reopen. thought one of you guys had to do it21:08
seb128\sh: it's efficient to do it this way rather than mark the bug incomplete, ask the submitter to mention the duplicate number and then close the bug21:08
\shhggdh: I already greped the source...no need for something else...I just need the info how to reproduce it properly.21:09
hggdhjderemer: I *think* you can21:09
greg-g\sh: yeah, I cna't reproduce it unfortunately21:09
hggdhjderemer: \sh needs you to explain how to reproduce21:09
* hggdh cannot reproduce either21:09
greg-gyes, anyone can change a bug from "invalid" to "new" or "imcomplete"21:09
seb128this bug is bug #218537 anyway21:10
ubottuseb128: Error: Could not parse data returned by Launchpad: The read operation timed out21:10
seb128why do you guy insist so much on reopening a duplice?21:10
seb128duplicat21:10
seb128bug #21853721:10
ubottuLaunchpad bug 218537 in yelp "yelp crashes silently in GNU-Info Pages" [Medium,New] https://launchpad.net/bugs/21853721:10
greg-gbecause I missed that duplicate21:11
LaserJockseb128: I'm more concerned with upsetting reporters by just off-hand invalidating with a canned response21:11
seb128LaserJock: well it's either that or we give up on dealing with the bug load21:12
greg-gwant me to change the topic to something more meaningful, like the error message?21:12
jderemeri dont see how its a bug if its a different situation21:12
seb128LaserJock: asking to use apport as several advantage21:12
jderemerdup bug*21:12
seb128- the bug is registered in the stacktrace database for autoduplication21:12
greg-gs/topic/title/21:12
seb128- it has details on the system21:12
seb128- it gives a detailled stacktrace21:12
LaserJocksure21:13
seb128jderemer: "** Yelp:ERROR:(yelp-document.c:217):yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document))"21:13
LaserJockbut that doesn't change the fact that it looks like people are just rejecting user's problems21:13
seb128jderemer: that's the same error and source code line21:13
greg-gI'm going to change the title of that bug to the error message to more closely conform to how apport titles bugs and to make it more useful, any -1's?21:13
seb128LaserJock: the stock reply should be clear "closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding."21:14
seb128LaserJock: you are welcome to suggest a better stock reply thoguh21:14
LaserJockI suggest that apport figure out how to add to the bug rather than having people closing bugs21:14
seb128LaserJock: I'm not sure it would be clear to have some useless comments and then the useful informations rather than a new stock useful bug21:15
seb128LaserJock: but I think there is an apport bug about that and once it's fixed we can discuss it again21:15
\shseb128: the problem is not apport, even it's not running, but the human intervention...nothing more nothing less..21:16
seb128but for now we do with what we have, apport always open a new bug and that's why we close the current one21:16
seb128\sh: what is your issue exactly there? you want to keep useless bugs open to make submitter happy or something?21:16
\shseb128: people closing bugs, because they don't understand the reason why the bug was opened...mostly because of not reading, or if the text was read, not understanding...21:18
seb128\sh: that's clear, crash bug -> use apport21:19
jjesse\sh: are you then trying to prevent people from mistakes somehow? or people who are closing bugs that should know better21:19
seb128that's the only way the retracer will know about the duplicates and do its work21:19
\shseb128: nope...crash bug, use something which gives me more knowledge21:19
marnanelsometimes people do show a surprising inability to read the rest of a bug21:19
seb128\sh: welcome to the real world but you way is not manageable, we make use of the tools we have to handle the bug load21:20
jderemerall i can say is this is getting way to hard21:20
seb128\sh: duplicating bugs manually because submitter don't want to use apport is not an option21:20
seb128jderemer: that's why we ask to use apport too, it's too hard when the user has to figure what to install and how to get the informations21:21
jderemereverything is installed21:21
seb128jderemer: the issue is that apport is not working in your case21:21
greg-gto bring it back to productive discussion, what things should jderemer / I put in an apport bug about this issue (apport not working in his case)?21:23
CarlFKhggdh: will do21:23
\shseb128: the real world don't use public bug reports (adobe)...and don't have this problem...being a community guy, and opensource facist, thinking about people not having the knowledge I have makes more sense...we do have the tools, which are not really in place here...marking as "yes, we know already about it, marking it as dup #xyz" or "guy, thanks for the bugreport, I know it's bugging you, but heck, how did you do it" or "thanks, I read the bug,21:24
\shI know it's a patch file of 1MB, I see dev Y is assigned to it, so I leave it alone"...the discussion we have, right here right now is about sense, not tools or pre-defined answers21:24
seb128greg-g: that's a duplicate of bug #21853721:24
ubottuLaunchpad bug 218537 in yelp "yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document)) Aborted (core dumped)" [Medium,New] https://launchpad.net/bugs/21853721:24
seb128I'm not sure why gdb is not working though21:24
seb128but there is no real need of extra details21:24
greg-gseb128: yeah, I mean, you suggested to report a bug against apport as it wasn't working correctly, wondering what information I should have jderemer give for that bug21:25
seb128\sh: the stock reply describe the issue clearly, we need to have the bug reported using apport to be able to deal with it efficiently, what is offencive for users there?21:25
seb128greg-g: well, the issue there is that it SIGABRT and I'm not sure apport catch those21:26
\shseb128: machines vs. people -> stock replies vs. people not knowing our business but using our software....the whole market around linux.21:26
greg-gseb128: ok, so then no apport bug then21:26
hggdhgreg-g: state apport was not kicked on this bug (provide the link to the bug), and ask why, and what can be done21:26
seb128\sh: how the submitter knows it's a stock reply?21:26
\shseb128: the bug about apport and eventually "SIGABRT" is out problem...not the reports21:27
\shreporters21:27
hggdhgreg-g: this will probably end up with pitti, anyway21:27
greg-ghggdh: ok21:27
seb128\sh: I'm happy to open bugs about apport when it doesn't work for me, but that's not the case there21:27
* hggdh thinks we live in interesting times21:28
seb128\sh: anyway that's not really constructive, as said either we keep thousand of useless bug open because the user might have apport not working or we explain them that we close the bug because if they use apport then the bug can be better handled and suggest them to do that21:28
\shseb128: apport actually is a bug tool for the devs*(ubuntu)...no user has to take care about it...21:28
seb128no, it's not21:29
seb128it's the way for user to report issues21:29
jderemerA WAY21:29
jderemernot the ONLY way21:29
seb128I don't use apport and  don't care about it21:29
jderemerso if it doesnt work21:29
seb128I use gdb and valgrind when I've issues21:29
jderemerand someone asks21:29
seb128apport is a way for users to report issues without having to care about those details21:29
jderemerseb128: both of those reports are there though21:29
hggdhjderemer: the beauty of apport is it takes cares of collecting the necessary data from your system, and you (the user) do not need to worry about details like what happened with the dbgsyms21:30
hggdhjderemer: yes, they are, and \sh said it is enough for him to work on it21:31
jderemerhggdh: ya, but the #ubuntu-bugs channel should help and not just complain when a user is trying to get information21:31
seb128jderemer: in 90% of the case apport work, so between keeping 90% of the bugs open for nothing or reopening 10% because apport doesn't work we pick the second option, it's not ideal but that's the only way we can deal witht he bug load21:31
hggdhjderemer: we do help. It just happens you got in while we were discussing work flow21:31
jderemerhggdh: yep... i want to make my point thought.  When this method is learned, more ppl learn.  if some one asks how to do something dont tell them to bad21:31
jderemerer didnt mean that toward hggdh..21:32
seb128jderemer: there is no complain, but the discussion turned in a disagrement between people doing distribution work21:32
jderemerment it in geeneral21:32
seb128and you are in the middle now21:32
* \sh goes to his wife now, cries a lot, goes to work later and fixes yelp21:32
seb128sorry about that ;-)21:32
jderemerits fine21:32
jderemerim not an idiot though21:32
jderemerso when i learn somethign new i can use it in the future21:32
jderemer:)21:32
seb128;-)21:32
hggdhjderemer: I understand -- *we* understand21:33
seb128ok, so to be back to your bug21:33
jderemerlearned a lot today, and hope to give better ones in the future21:33
jderemerand i still dont think its a dup21:33
seb128I've marked as duplicate of bug #218537 which has the same exception on the same line21:33
ubottuLaunchpad bug 218537 in yelp "yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document)) Aborted (core dumped)" [Medium,New] https://launchpad.net/bugs/21853721:33
hggdhthe whole thing -- and it might explain a bit -- Ubuntu is community effort. We need help21:33
jderemerits a differnt use21:33
jderemeri read that bug21:33
hggdhjderemer: but it is the same error, same place21:33
jderemerits nothing like what i was doing.21:33
hggdhchances are it is the same issue21:33
seb128jderemer: exact same message on the exact same code = same bug in 99.9% of the cases21:34
seb128jderemer: buggy code paths can be trigger by different ways often21:34
hggdhjderemer: the developer/maintainer working on this bug should look through the duplicates21:34
jderemerone sec21:34
seb128jderemer: see bug #223918, the description is similar to yours21:36
ubottuLaunchpad bug 223918 in yelp "'Back' button crashes Documentation Browser (Help 2.22.1) (dup-of: 218537)" [Medium,Invalid] https://launchpad.net/bugs/22391821:36
ubottuLaunchpad bug 218537 in yelp "yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document)) Aborted (core dumped)" [Medium,New] https://launchpad.net/bugs/21853721:36
jderemerok now 223918 i did NOT see21:37
hggdhand if they decide one issue is not the exact scenario, they should unduplicate (sorry) it21:37
jderemeryeppie for crappie launchpad search21:38
jderemerol21:38
jderemerhggdh: thanks for the help21:39
seb128jderemer: this one was already closed as duplicate of the other one ;-)21:40
jderemerand the courtesy21:40
hggdhjderemer: welcome. We will be here, and -- one way or the other -- we will get it done :-)21:40
seb128jderemer: and the default search doesn't list duplicates21:40
seb128jderemer: you are welcome and sorry again about the discussion about how bugs should be handled21:40
seb128any enough bug discussion for now21:42
seb128I've some things to do before uds ;-)21:42
jderemerum21:43
jderemersuggestion21:43
jderemernext time21:43
jderemermark it as duplicate21:43
jderemernot invalid... lol21:43
greg-gjderemer: don't worry, that bug that yours was marked a duplicate of had a bad title, I just changed it to what it is now21:43
jderemeri saw :021:43
greg-g:)21:43
greg-gjderemer: have a good one, and again, don't be afraid to come back :)21:44
jderemeri dunno21:45
jderemerthis place is scary :-P21:45
greg-gheh, this is true, but you must be brave :)21:45
jderemerhaha21:45
jderemerim a little mad all that work did nothing21:45
jderemer:(21:45
jderemerbut o well21:45
jderemertheres always next time21:45
greg-gjderemer: well, you confirmed that the bug is still present, at least :)21:46
hggdhjderemer: welcome to the fringe... ;-)21:47
jderemerhahaha21:48
jderemerso true21:48
jderemerboth statements :)21:48
=== sdh_ is now known as sdh
wolfgerany suggestions how to treat bug 162855 ?23:01
ubottuLaunchpad bug 162855 in gnome-app-install "add/remove help integration" [Undecided,Incomplete] https://launchpad.net/bugs/16285523:01
ffmwolfger: It should be {blueprint, brainstorm idea}23:19
ffm(one of)23:19

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!