[00:22] <blkperl> can someone set bug 870874 to triaged please
[00:22] <ubot2> Launchpad bug 870874 in at-spi2-core "LDAP user with automounted nfs homedir cannot login" [Undecided,Confirmed] https://launchpad.net/bugs/870874
[00:27] <penguin42> blkperl: Is it? I mean reading the comment set, does anyone really understand where the problem is?
[00:29] <blkperl> penguin42: ok maybe your right, can you add an importance at least
[00:32] <penguin42> blkperl: Done, marked it high
[00:32] <blkperl> penguin42: thank you
[00:33] <penguin42> blkperl: I mean why the heck does assistive technology interact with nfs homedirs?
[00:40] <blkperl> penguin42: no clue... o.O
[08:14] <Conradzz> what sup
[08:15] <Conradzz> anyone there?
[08:16] <elgaton> Conradzz: yes?
[08:17] <Conradzz> messing with linux again and sure enough problems
[08:17] <Conradzz> full system freezes now on a fresh 12.04, 64 bit
[08:17] <Conradzz> was running fine earlier
[08:18] <Conradzz> reading bug reports, and I'm guessing its pretty common
[08:19] <Conradzz> I swear lol, every few months I come back and give linux a try and I'm always met with resistance, I'm beginning to think I'm just not meant to use it
[08:20] <elgaton> Conradzz: Don't know. Anyway, do you mind if we switch to the #ubuntu channel, as that is the most targeted?
[08:20] <Conradzz> sure
[11:15] <alo21> hi all
[11:16] <alo21> where can I find easy bug to fix in Ubuntu?
[11:58] <rokr1> Hi guys
[11:58] <rokr1> I have a problem
[11:59] <rokr1> with indicator-datetime-service memory leak
[11:59] <penguin42> would you like to tell us what the problem is?
[11:59] <rokr1> any solution available ?
[12:00] <penguin42> hmm seems to be bug 772340
[12:00] <ubot2> Launchpad bug 772340 in indicator-datetime "e-calendar-fact and indicator-datet consumes 2,6GB Memory" [High,Fix released] https://launchpad.net/bugs/772340
[12:00] <penguin42> rokr1: Can you confirm what version you have of package indicator-datetime ?
[12:02] <rokr1> I am on 64 bit got my system unconfigured due this bug since its a  server x64 running kernel 3.3.4
[12:02] <rokr1> unfortunately I uninstalled all the ubuntu components
[12:02] <rokr1> and it seems that my apt went missing
[12:03] <penguin42> rokr1: Can you tell me the package version - dpkg -l indicator-datetime   I think
[12:03] <rokr1> oh okay a minute please
[12:04] <rokr1> oops my system is broken now
[12:07] <rokr1> I removed all ubuntu component that removed my apt and damaged dpkg
[12:08] <rokr1> I also had issues with geoip opening unwanted outbound connections to ubuntu server
[12:08] <rokr1> that was my major concern
[12:08] <rokr1> penguin42
[12:08] <rokr1> any advise
[12:09] <penguin42> if your dpkg is that broken then it sounds like you need a reinstall
[12:09] <rokr1> I did apt-get purge ubuntu*
[12:09] <rokr1> so did it removed all ubuntu plugins
[12:09] <rokr1> ?
[12:10] <rokr1> I still have aptitude functional
[12:10] <penguin42> well you can reinstall what you removed if you know, but if you don't then it's probably easier to reinstall
[12:14] <rokr1> resolvconf and libgdk-pixbuf2.0-0 are missing dependencies
[12:14] <rokr1> to get apt to work
[12:36] <uxq> How do I attach an ubuntu-bug report (i.e., all the files) to an existing bug report using ubuntu-bug
[12:37] <jtaylor> apport-collect
[12:38] <uxq> hmm, only works if I am the originator
[12:41] <penguin42> when I did that yesterday it gave me a warning if I wasn't the originator but let me do it if I clicked yes
[12:44] <rokr1> I got apt working now
[12:44] <rokr1> manually installed the package
[12:45] <uxq> it only gives me the option of clicking "Close"
[12:47] <uxq> You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed
[12:47] <penguin42> uxq: Interesting, the KDE frontend yesterday had 3 options, one of which was a Yes I really want to
[12:48] <uxq> I marked a bunch of bugs as duplicates, but the original bug doesn't have the backtrace
[12:48] <uxq> will devs actually look at the duplicates?
[12:49] <penguin42> uxq: Possibly not unless you point them to it
[12:49] <rokr1> is the bug for geoip unity solved ? like it opens an unwanted outbound connection
[12:49] <penguin42> uxq: While you generally dupe to the earliest number, if actually one of the others has a much better report it's best to dupe to that
[12:50] <penguin42> uxq: Add a comment that says something like 'there are more interesting back traces in ....'
[12:51] <uxq> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/980519
[12:51] <ubot2> Launchpad bug 980519 in xorg "Random log off in Ubuntu 12.04 LTS" [Undecided,Confirmed]
[12:52] <uxq> I did, can you mark the important as "High" ?
[12:52] <uxq> this is unreal how many people are affected
[12:54] <rokr1> penguin42: I am installing the gnome-shell
[12:54] <uxq> darn, I linked the dupe to the later one
[12:55] <rokr1> penguin42: with lightdm, installin them right now
[12:55] <uxq> maybe some bug admins will clean it up for me, my bad
[12:57] <uxq> Is there a way to use apport to collect all info about my system, then I can create an attachment?  I'm not using kde
[12:57] <uxq> or is there a way I can use the KDE apport?
[12:57] <uxq> (without installing KDE)
[12:58] <rokr1> what does the indicator-datetime-service do ?
[12:59] <jtaylor> uxq: see man apport-cli
[12:59] <jtaylor> some of the options might do what you want
[12:59] <jtaylor> --save looks goo
[13:05] <rokr1> ??
[13:05] <rokr1> anyone
[14:07] <alo21> hi all
[14:07] <alo21> could you tell an easy package?
[14:18] <alo21> Flannel: hi
[14:18] <alo21> can you help me?
[14:18] <alo21> please
[14:20] <alo21> done...
[14:20] <alo21> do not worry
[14:46] <alo21> epikvision: hi
[14:47] <alo21> epikvision: can you help me?
[14:47] <epikvision> hello
[14:47] <Resistance> alo21:  whats up?
[14:47] <alo21> Resistance: I would like to fix bugs
[14:47] <epikvision> alo21: yeah, Resistance is the better one to talk to
[14:48] <epikvision> but I could get you started
[14:48] <Resistance> actually, on a day like today, one of the more senior bugsquad peoples or the MOTUs would be better to talk with
[14:48]  * Resistance yawns
[14:48]  * epikvision sighs
[14:48] <epikvision> that is true.
[14:48] <epikvision> be prepared, alo21, to do lots of reading
[14:49] <Resistance> but that's because i've only been up for an hour xD
[14:49]  * Resistance hasnt had his coffee yet
[14:50] <alo21> epikvision: Resistance I am reading at harvest.ubuntu
[14:50] <alo21> to find an easy bug... and it is ok
[14:50] <txomon|home> I have asked this in #ubuntu-server and #ubuntu-testing, and hope someone can give any idea. When using mini.iso or netboot (i use the last one) which is the aim of putting the "Manual package installation" if it crashes the install?
[14:50] <Resistance> ugh, why didn't i copy my mozilla and firefox folders from my old drive >.>
[14:51]  * Resistance is still getting his systems back online
[14:51] <alo21> epikvision: Resistance in the meanwhile i am reading this guide https://wiki.ubuntu.com/Bugs/HowToFix
[14:53] <epikvision> alo21: are you very familiar with the command line?
[14:53] <alo21> epikvision: Resistance a little bit
[14:53] <epikvision> https://help.ubuntu.com/community/UsingTheTerminal
[14:53] <epikvision> better master the terminal before you get started
[14:54] <Resistance> i strongly agree
[14:54] <epikvision> Let me quote philipballew for you
[14:54] <Resistance> the terminal and CLI is one of a developer's most utilized, and most intimidating, tools
[14:54] <epikvision> "to know linux is to know the command line."
[14:55] <epikvision> Resistance: can the tasks of the command line be accomplished in an IDE like Eclipse or Geanie?
[14:55] <epikvision> or that just isn't possible; one must embrace the command line for these tasks?
[14:56] <epikvision> tasks = bug reporting, packaging, etc.
[14:56] <Resistance> epikvision:  it can, but only for code, when you get into packaging and debdiffs, you should do that via command line only
[14:56] <Resistance> bug reporting is done on launchpad, packaging is done via CLI
[14:56] <epikvision> ahh
[14:56] <Resistance> code fixing is done by [editor of your choice]
[14:56] <epikvision> I c
[14:56] <Resistance> personally, i use GEdit or Kate for when fixing code, but that's because I don't like most IDEs
[14:57] <Resistance> (GEdit is the text editor in Ubuntu, Kate's the advanced text editor in Kubuntu)
[14:57] <Resistance> speaking of which...
[14:57]  * Resistance forgot to install Kate for his KDE environment
[14:57] <Resistance> oops
[14:57] <alo21> epikvision: my main question is: Can I really edit source coude whatever I want to fix the bug?
[14:57] <epikvision> of course
[14:58] <Resistance> you should do targetted editing to fix bugs
[14:58] <Resistance> and then submit diffs to the bug for review
[14:58] <alo21> epikvision: directly from the source or via a patch?
[14:58] <Resistance> alo21:  via a diff / patch
[14:58] <Resistance> alo21:  and then you submit that to the bug, and a team will review it
[14:58] <Resistance> it is of course possible bugs arent fixed by patches, in which case patches can be rejected, so unless you're certain your patch fixes a bug, don't submit it (my advice)
[14:58] <Resistance> or have someone else test it before submitting
[14:59] <Resistance> (that's my tactics)
[14:59] <epikvision> sounds sweet
[14:59] <alo21> Resistance: why wiki suggests me thhe command to join a patch "patch -p1 < ../bugfix.patch"
[14:59] <alo21> if I edit directrly from the source?
[14:59] <Resistance> to include a patch in code, yes.  but that's for testing
[15:00] <Resistance> when you work on Ubuntu packages, you can do stuff that method, or you can include it in a patch in a package, but that's advanced stuff
[15:00] <Resistance> for your testing, you should do that, yes.
[15:00] <Resistance> but when you submit the patch, it may be included in the package as a patch so that at build-time for the package it will apply the patch
[15:00]  * Resistance sees this more often than not
[15:01]  * epikvision raises his hand
[15:02] <epikvision> Resistance: should the developer's environment have the next upcoming release in his computer?
[15:02] <Resistance> epikvision:  in some way shape or form, yes.
[15:02] <epikvision> like the testiso thing?
[15:02] <Resistance> lemme give you an overview of where bugs get fixed:
[15:02] <Resistance> When a new bug is filed, and a fix released, it is a candidate to be included/synced/updated in the latest development release, in this case Quantal
[15:03] <Resistance> The exception are upstream bugs, such as the one you ran into a few days ago epikvision
[15:03] <epikvision> ahh
[15:03] <Resistance> in which case those are fixed in the upstream program itself
[15:03] <Resistance> and are included whenever that version shows up for Ubuntu
[15:04] <Resistance> When testing programs to confirm bugs, and then fix bugs, you should test with the latest development release (because if the bug exists in Precise, it probably exists in Quantal)
[15:05] <Resistance> whoopsies, i forgot to upload a patch for a bug...
[15:05] <epikvision> well, that was good stuff, Resistance
[15:05] <epikvision> thanks.
[15:06] <alo21> epikvision: Resistance https://bugs.launchpad.net/ubuntu/+source/xine-lib/+bug/810407
[15:06] <ubot2> Launchpad bug 810407 in xine-lib "small typo in src/audio_out/audio_directx2_out.c:392" [Undecided,Confirmed]
[15:06] <alo21> here a bug
[15:07] <alo21> should I work in xine-lib (ubuntu) rigth
[15:07] <alo21> right*
[15:08] <alo21> ?
[15:08] <Resistance> this was upstreamed, it seems, and its sat there for almost a year upstream
[15:09] <Resistance> https://bugs.xine-project.org/show_bug.cgi?id=422
[15:09] <ubot2> bugs.xine-project.org bug 422 in Plugins / Audio Output "Typo in translatable string in directx audio output code." [Normal,Unconfirmed]
[15:11] <Resistance> a lot of bugs are upstreamed :P
[15:11]  * Resistance yawns as he finally gets up to get a cup of coffee
[15:12] <epikvision> upstreamed means the bug doesn't need to be touched.
[15:12] <epikvision> ?
[15:12] <epikvision> Resistance: 'cuz it's taken care of.
[15:12] <Resistance> it might need poked upstream, but usually means that it doesnt need immediate fixing in  ubuntu and needs fixing upstream (with the program developers, an dnot just Ubuntu)
[15:13] <epikvision> ahh, so it's the program developers who are more in charge
[15:13] <Resistance> for example: say you found a bug in a webserver package, lets say nginx.  The bug is a critical bug, and exists on all versions of the program, including that built from source not in Ubuntu.
[15:13] <Resistance> you would file that bug against the package in ubuntu, but that would then be upstreamed to their bugtrackers for their devs to fix
[15:14] <Resistance> and if you submitted a patch that fixed it, that'd go upstream as well
[15:14] <Resistance> but that's just an example :P:
[15:15] <Resistance> there's a whole bunch of guidelines for what needs upstreaming and what doesnt
[15:15] <Resistance> and frankly, i'm not even sure 100% of which cases require upstreaming :P
[15:15] <Resistance> okay, seriously, i need my coffee now
[15:15]  * Resistance shall return
[15:17]  * epikvision winks. 
[15:18] <epikvision> Resistance: I'll have to read a lot then.  There is much to learn.
[15:19] <txomon|home> can anyone have a look on this: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/924959
[15:19] <ubot2> Launchpad bug 924959 in chromium-browser "chromium browser not working in guest account" [Undecided,New]
[15:20] <txomon|home> and this one: https://bugs.launchpad.net/ubuntu/+source/update-inetd/+bug/919660
[15:20] <ubot2> Launchpad bug 919660 in update-inetd "bootp doesn't have an updated man/xinetd boot script" [Undecided,New]
[15:20] <txomon|home> and this one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/975197
[15:20] <ubot2> Launchpad bug 975197 in linux "Can't avoid mounting in boot time" [Medium,Confirmed]
[15:49] <Resistance> txomon|home:  what do you want us to look at it for?  in what context if i might ask
[15:50] <txomon|home> Resistance, what is to be done with them, 2 of them are Undecided, and the other, just confirmed
[15:50] <Resistance> txomon|home:  the chromium browser one is filed against 11.10, i'd like them to test it in Precise, and I commented as such
[15:51] <Resistance> i'm checking the other two
[15:51] <txomon|home> oki
[15:51] <txomon|home> I am going to test in 12.04
[15:51] <Resistance> i've asked them to confirm in 12.04  too, i'd like more than one test ;p
[15:52] <Resistance> txomon|home:  are these bugs you're filing?
[15:52] <txomon|home> Resistance, doesn't
[15:52] <Resistance> txomon|home:  please answer my question ;P
[15:52] <txomon|home> ?
[15:52] <Resistance> are these bugs that you are filing?
[15:52] <Resistance> i.e. did you file these bugs you're referencing
[15:53] <txomon|home> this are the bug I have filled, and I would like to be able to move them
[15:53] <Resistance> ah
[15:53] <Resistance> post on that chromium browser bug the issue does not occur in Precise
[15:53] <txomon|home> Resistance, does
[15:54] <Resistance> it does?
[15:54] <Resistance> does it or does it not occur in Precise?
[15:54] <Resistance> you cant have it both ways :p
[15:55] <txomon|home> Sorry, I meant that it doesn't work in precise, and that it does occur in precise xD
[15:55] <Resistance> doesn't work, or doesn't occur?
[15:55] <Resistance> there's a difference
[15:55] <Resistance> if chromium doesnt work in precise that's a different bug
[15:56] <txomon|home> in guest account
[15:56] <Resistance> if the same issue as you had in 11.10 is still occuring, where it does not load in the guest account, i'll test once i'm back on 12.04
[15:56] <txomon|home> due to "Failed to move to ... PID " or sth like that
[15:56] <Resistance> (backing up my data right now)
[15:56] <Resistance> i'll check once i'm done backing up my 12.04 data
[15:56] <txomon|home> oki
[15:56] <Resistance> post on your bug that the same issue still occurs in Precise
[15:57] <txomon|home> oki
[15:58] <txomon|home> I am doing an apport-collect with the just installed lubuntu-core computer
[15:58] <Resistance> you dont really need a ton of apport bug stuff
[15:59] <Resistance> the 'linux' one i dont think is valid against the 'linux' package
[15:59] <Resistance> might be a samba problem
[15:59] <txomon|home> Resistance, it is a linux bug, because it doesn't skip mounting
[15:59] <Resistance> txomon|home:  its not supposed to skip mounting, when in fstab
[15:59] <txomon|home> true sry
[16:00] <Resistance> fstab will always try to mount
[16:00] <txomon|home> Resistance, but it gives the option
[16:00] <Resistance> if you dont want it to do that, remove it from fstab
[16:00] <Resistance> then the bug is in handling mounting of samba shares
[16:00] <Resistance> and not 'linux' because 'linux' is a package that contains a kernel (or rather is probably a metapackage that depends on the latest kernel)
[16:00] <Resistance> so against 'linux' it's invalid
[16:00] <txomon|home> if I put it in fstab, but the path is not /var but /mnt another guy told me it allowed to be skipped
[16:01] <Resistance> it's marked as "confirmed" but i'm not sure
[16:01] <txomon|home> Resistance, linux package is not valid, I agree
[16:02] <txomon|home> the idea is that in boot screen, it tells you it is waiting for network storage system, and if you want to skip it, you may press S (or G or whatever)
[16:02] <txomon|home> and the problem is that it doesn't work
[16:02] <Resistance> txomon|home:  its marked as confirmed, so i'll set it as Opinion
[16:02] <Resistance> or get it set rather
[16:03] <txomon|home> dont know if that option shouldn't be there or not (as you said fstab is mandatory) but if you give the option to choose, the decision should be effective
[16:06] <Resistance> i'm going to forward that to the BugSquad mailing list
[16:06] <Resistance> because i want additional opinions
[16:08] <penguin42> I know things like swap (which are speicified in fstab) will display the skip message if it's not available and it works, so IMHO that's just the same and therefore it's just a bug if the skip doesn't work
[16:11] <Resistance> agreed, but is it valid against the 'linux' package?
[16:11] <Resistance> having siad this i just sent this to the mailing list
[16:12] <txomon|home> Resistance, which is the package that mounts things specified in fstab?
[16:13] <Resistance> txomon|home:  that's why i emailed the mailing list :P
[16:13]  * Resistance isnt sure
[16:13] <Resistance> also, i'm wanting additional opinions on the Validity of that bug
[16:13] <penguin42> is that mountall ?
[16:13] <txomon|home> This  man  page is part of the util-linux package and is available from   ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
[16:13] <Resistance> ?
[16:13] <txomon|home> man fstab
[16:14] <txomon|home> so the package is util-linux instead of linux?
[16:14] <Resistance> i'd... wait on that one
[16:15] <penguin42> Resistance: 'linux' isn't that bad a bet - I don't know how the skip stuff is done; the actual mounting is done by the kernel so if the kernel isn't letting it be cancelled that's reasonable - so even if it's wrong it's not a bad guess
[16:15] <Resistance> indeed
[16:15] <Resistance> hence, though, why i'd be looking for a secondary opinion anywyas ;P
[16:15] <Resistance> anyways*
[16:17] <txomon|home> and the bootp one, is it an opinion, bug or... how is that classified?
[16:22] <penguin42> looks like a bug from your description
[16:25] <txomon|home> I have another bug that is making me crazy, it randomly comes/goes.
[16:25] <txomon|home> but just sometimes (like 3 months intervals between apparitions)
[16:27] <penguin42> txomon|home: I assume there is some ubuntu policy of how to treat inetd/xinetd - and I'm not sure what it is, so I'm not sure what the right thing to do with that bootp one is
[16:48] <Resistance> penguin42:  i'd forward em to the mailing list, or just leave the bugs
[16:48] <Resistance> i did confirm chromium-browser's bug though, not sure though if its 100% against chromium, or something else
[16:48] <penguin42> yeh I just left it
[16:49] <Resistance> (sorry i had to swap drives again)
[20:26] <blkperl> can someone set the importance of bug 932064 to high
[20:26] <ubot2> Launchpad bug 932064 in amanda "amtape crash" [Undecided,Confirmed] https://launchpad.net/bugs/932064
[20:54] <alo21> hi all
[21:25] <alo21> mrand: hi.. can you help me please?
[21:25] <Resistance> alo21:  with?
[21:25] <Resistance> oh getting started on bugs?
[21:26] <alo21> Resistance: hi...
[21:26] <alo21> Resistance: some had reported a typo bugs
[21:26] <alo21> bug*
[21:26] <Resistance> where?
[21:26] <alo21> https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/807861
[21:26] <ubot2> Launchpad bug 807861 in inkscape "typo in ../src/widgets/toolbox.cpp:4685" [Low,Fix committed]
[21:27] <alo21> Resistance: some one has committed a fix yet
[21:27] <Resistance> !info inkscape precise
[21:27] <alo21> but not for both
[21:27] <Resistance> bleh, it doesnt listen here
[21:27]  * Resistance forgot
[21:27] <Resistance> alo21:  its committed upstream
[21:28] <Resistance> once inkscape 0.49 is included in Ubuntu the "traiged" in ubuntu becomes fix released
[21:28] <Resistance> i am probably assuming that inkscape hasnt been released as 0.49 stable
[21:28]  * Resistance should check
[21:28] <Resistance> yeah, 0.49 isnt released yet
[21:29] <Resistance> and therefore does not yet exist in Ubuntu
[21:29] <Resistance> so if/when 0.49 gets included in Ubuntu, that will become Fix Released
[21:29] <Resistance> and since its triaged, there's nothing you can do
[21:29] <alo21> Resistance: ok, thanks
[21:29] <Resistance> (because its an upstream-handled bug)
[21:30] <alo21> Resistance: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/923932 here
[21:30] <ubot2> Launchpad bug 923932 in libreoffice "LibreOffice icons classic" [Undecided,Confirmed]
[21:30] <alo21> there is a bug that reguards two package
[21:31] <alo21> packages*
[21:31] <Resistance> there's a lot of bugs that are connected to multiple packages
[21:31] <Resistance> :P
[21:31] <Resistance> heck, i've even handled a few
[21:31] <alo21> and how does it work?
[21:32] <alo21> Should I check in wich package is the bug?
[21:32] <Resistance> nope, if it says 'confirmed' then its apparent in both, but i dont know enough about the packages to fix it
[21:33] <Resistance> if you're unsure how to help debug packages, I suggest you ask in #ubuntu-motu on how to get started in locating bugs in programs
[21:35] <alo21> Resistance: thank you :)
[21:36] <Resistance> because even though these're bite-sized bugs, some of em can be tricky to find solutions for
[21:36] <Resistance> heck, the PHP5 bug i worked on which really was a feature request took me a while to locate the file to change :P
[21:36] <Resistance> and that's a pretty decent-sized package/program
[21:38] <alo21> is very difficult for me finding new bugs without a fix commitee, which is assigned to nobody
[21:38] <Resistance> well the key is to see whether its upstream or not
[21:38] <alo21> Resistance: how=
[21:38] <alo21> ?
[21:39] <Resistance> if its got something else tied to it and its *not* a package (i.e. not "something (ubuntu)") then its probably been forwarded upstream
[21:40] <alo21> Resistance: I should check all bugs to find the one which is not in upstream
[21:41] <Resistance> i'd recommend just sticking to the bitesized ones
[21:41] <Resistance> look for ones that arent upstream
[21:41] <Resistance> or ones that are not committed upstream
[21:41] <Resistance> (because you can still provide a patch to the upstream)
[21:41] <alo21> Resistance: ok... I have to go... bye