[00:06] <Lupine> This should be a WishList: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/311615
[00:06] <Lupine> As well as this one: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/311503
[00:10] <Rocket2DMn> Lupine, wishlisted the second one
[00:10] <Rocket2DMn> that first one seems more like a regression
[00:12] <Lupine> but it's not really a bug though, right?  true it's annoying, and I do agree with the reporter...so how should I typically handle these?
[00:12] <Rocket2DMn> the reporter said it behaved as expected before
[00:12] <Rocket2DMn> then with an update it stopped
[00:13] <Rocket2DMn> so the user is complaining about a change in behavior, not a new feature
[00:15] <Lupine> agreed, and I read over the pidgin developer ticket: http://developer.pidgin.im/ticket/7172
[00:15] <Lupine> so....maybe I should do this
[00:15] <Lupine> re-assign the bug to the specific window manager the user is using?
[00:16] <Lupine> in this case, metacity
[00:16] <Lupine> this is one of those more confusing bugs, but I would like to learn from this one, so I'll know next time
[00:16] <Rocket2DMn> its possible its a WM problem
[00:18] <Lupine> I think so, I will reassign and post an explanation to the user.  thanks for the feedback
[00:19] <Rocket2DMn> np
[01:56] <Hobbsee> bug 316174
[01:57] <Rocket2DMn> thats weird
[01:58] <Rocket2DMn> intrepid-updates has a newer version than jaunty, lol
[02:55] <ToHellWithGA> Hobbsee: @lart 34
[03:00] <ToHellWithGA> later gators
[03:58] <jedex> hi
[07:04] <dholbach> good morning
[07:16] <jedex> morning
[15:55] <StevePearce> Hello all, I would like to ask a question about recording/changing a Jaunty bug.
[15:55] <StevePearce> First time bug reporting. So im doing my research before tinkering in Launchpad.
[15:55] <StevePearce> The issue I am having is with Jaunty's partitioning tool in Ubiquity (GTK).
[15:56] <StevePearce> I am trying to achieve the following: Create a new partition table, create a 20gb / (primary), 10gb /home (logical), 6gb swap (logical) and then allocate the rest to a /data (logical) partition.
[15:56] <StevePearce> Ubiquity fails at creating the swap partition and instead creates a /var or /usr. I am able to repeat the issue.
[15:56] <StevePearce> Hunting through launchpad (to see if developers were aware of the issue) I noticed this post https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/311799 with a "new" status.
[15:56] <StevePearce> My question is essentially this: what do I change? Do I confirm this report? Again, this is my first time reporting/altering a bug.
[16:01] <andresmujica> ok,
[16:01] <andresmujica> that's nice
[16:01] <andresmujica> i believe you should confirm this bug
[16:01] <StevePearce> ok, thanks
[16:01] <andresmujica> reporting you're case, and reporting what to do to repeat it.
[16:01] <StevePearce> ok
[16:02] <andresmujica> an we can change the description to extend it to other fs like /var or /usr
[16:02] <andresmujica> reporting your case (sorry)
[16:18] <andresmujica> StevePearce did you already comment to the bug?
[16:19] <StevePearce> i have literally just posted the changes.
[16:20] <andresmujica> ok
[16:20] <andresmujica> perfect!
[16:20] <andresmujica> let me check
[16:20] <StevePearce> thankyou for the help
[16:20] <StevePearce> I now feel more comfortable checking out bug reports
[16:21] <andresmujica> great!!
[16:21] <andresmujica> thanks to you for reporting the issue
[16:24] <andresmujica> Steve, check if you've got this file /var/log/installer/partman and attach it to the report
[16:25] <andresmujica> also add this /var/log/installer/syslog
[16:25] <andresmujica> and if you've got the time it would be great if you can add
[16:26] <andresmujica> the file /var/log/installer/debug  created by running  ubiquity --debug
[16:26] <StevePearce> ok
[16:39] <StevePearce> andresmujica, i haven't got a "syslog" or "partman" in the /var/log/installer directory
[16:39] <StevePearce> "debug" however is there, with a few thousand lines
[16:39] <StevePearce> should i pop it in a pastebin? or will it be fine to include in a comment?
[16:40] <andresmujica> i'm not really familiar with ubiquity but add the debug one, it may include useful information.
[16:40] <apw> would this be the right place to ask whether i am about to use launchpad correctly, specifically i we are working on a change which affects multiple packages, i am presuming (and want to confirm) it would be appropriate to use one bug with multiple tasks one per package affected?
[16:40] <andresmujica> add it as attachment
[16:40] <StevePearce> ok, thanks
[16:41] <student022> Hi! I have installed Ubuntu8.04 on server B and run the gnome desktop on B, accessing it with nxclient from A. When I open a gnome-terminal from within the desktop on B, I get an error "There was an error creating the child process for this terminal". How to avoid this?
[16:41] <student022> I found reports on /etc/fstab or udev errors that prevent the /dev/pts directory from having the right settings. But /dev/pts/0 exits, so its probably something else.
[16:41] <student022> When logging in to B from A using ssh -X, I can open gnome-terminal without problems. It only happens under Gnome (or KDE with konsole, respectively.)
[16:43] <persia> StevePearce, syslog and partman are found in /var/log/ directly
[16:43] <afflux> apw: yes, it most probably is appropriate
[16:43] <apw> thanks
[16:43] <StevePearce> ok persia
[16:43] <StevePearce> thanks
[16:43] <persia> apw, How many tasks are you considering?  Generally it becomes unwieldy for more than about 10, due to an outstanding bug with implicit subscriptions.
[16:44] <andresmujica> hmm, i'm gonna edit the wiki then, it says they're located at /var/log/installer
[16:44] <apw> persia, three
[16:44] <bdmurray> andresmujica: which wiki page is wrong?
[16:44] <persia> apw, Then almost certainly as tasks against a single bug, yes.
[16:45] <andresmujica> hmm.. i'm re-reading maybe i misunderstood ??  https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs
[16:45] <apw> persia, thanks thats great
[16:46] <andresmujica> it seems that while the installation is in progress the files are located at /var/log .. then they move to /var/log/installer.. right?
[16:46] <bdmurray> Yes, that's correct
[16:46] <persia> Not quite.  Different logs go in different places.
[16:46] <persia> Oh, post-install?
[16:46] <bdmurray> https://edge.launchpad.net/ubuntu/+source/ubiquity/+filebug-advanced
[16:48] <bdmurray> andresmujica: so that wiki page could use some clarification it seems
[16:48] <persia> Oh nifty: I think I never got that far when having installer issues.
[16:48] <andresmujica> yeap, i'm working on it..
[16:56] <andresmujica> ok. done
[17:45] <andresmujica> if a bug is solved by a package uploaded to Jaunty, which would be the right path ? a backport or a SRU?.  The bug affects hw and just installing the Jaunty package would it be solved.. bug #262853
[17:46] <james_w> andresmujica: SRU probably
[17:47] <andresmujica> ok, i'll fill it like SRU then. thks
[17:49] <james_w> andresmujica: yeah, the new upstream is a targeted patch. It would be up to the SRU team exactly how to proceed, but the work of updating the package would be easy
[17:50] <andresmujica> ok, i believe that too.
[19:59] <james_w> pedro_: you know a new network manager hit Jaunty today? Does that affect the bug day at all?
[20:01] <pedro_> james_w: don't think it could affect the hug day but i can update the bug list let's say Wednesday to include some of those new bugs (in case they're)
[20:01] <pedro_> or regenerate the list if needed
[20:01] <MrKanister> I think it's good to have a very latest version in Jaunty for tests
[20:02] <pedro_> indeed, having the latest version is always good ;-)
[20:03] <MrKanister> having Jaunty on a test machine helps so much :)
[20:07] <petski> Hi, I'm looking for a way to trace all system calls: "strace" can only trace one (actually 32) process/command at the time. Any other way then just wrap a shell script for this functionality? (LTTng seems overkill)
[20:20] <maco> thekorn: what is error 104? the 5aday applet just said "could not add bug #.... error 104"
[20:23] <thekorn> maco, don't know, let me check the code
[20:23] <maco> thekorn: when i did it from the cli right after it said that the bug had been added though. i keep having that happen lately. kinda confusing :-/
[20:24] <thekorn> hmm, #104: error while committing changes
[20:24] <maco> so why does the cli say it's already been added?
[20:25] <maco> i havent used 5aday much in the last few months...the last 3 or 4 times i tried, i got errors from the applet and the cli claimed that it had already been added
[20:25] <thekorn> maco, don't know, can you please file a bug and subscribe me, I will have a look at it tomorrow morning, can't look at it right now
[20:26] <thekorn> yeah, this looks wired
[20:26] <pedro_> bbl
[20:27] <maco> er... i dont think i have enough info for a proper bug report
[20:28] <andresmujica> maco: from time to time i've got the same issue... normally is beacuse a commit get stucked
[20:28] <andresmujica> maco: gimme a sec i'll look the commands i use to solve it...
[20:29] <maco> well bzr says there's nothing uncommitted
[20:32] <andresmujica> take a look via web into the last commit to check if the latest bug added to 5-a-day is there...
[22:10] <torkiano> Can someone  confirm bug 299869 ?
[22:10] <torkiano> (I'm the reporter)
[22:17] <milos_> i don't remember when I last lol'd on bug report since this one https://bugs.launchpad.net/ubuntu/+bug/316547
[22:17] <milos_> :)