=== arand_ is now known as arand
=== micahg_ is now known as micahg
[02:01] <balthus> hi, could someone from UBC have a look to bug #768127? My guess in that it deserves the "won't fix" status.
[02:01] <ubot4`> Launchpad bug 768127 in starttls (Ubuntu) "starttls not available in Natty (affects: 1) (heat: 330)" [Undecided,Confirmed] https://launchpad.net/bugs/768127
[02:02] <micahg> balthus: invalid was fine
=== ZNC is now known as KDE-ZNC
[02:06] <balthus> micahg: ok, tx, i mark it invalid then
[02:06] <micahg> balthus: the only time you
[02:07] <micahg> need "won't fix" vs invalid is when there's an argument about whether or not to do something and the developers say no
[02:10] <balthus> ok i see, in this case there is indeed no doubt we will give satisfaction to the initial bug report
[02:13] <balthus> (well satisfaction was still given to the reporter, cause he got a solution to workaround his issue)
[02:14] <balthus> i wonder now if i should have turned this bug report into a question?
[02:14] <balthus> (cause it may be come back one day or another)
=== yofel_ is now known as yofel
[09:32] <bkerensa> night
[09:50] <antoIT> Hi I'm Antonio, I found a bug in Ubuntu 11.04 but with ubuntu-bug application I cannot send a bug info because the application doesn't collect any kind of bug info, while I found those by hand in kernel log file. I wrote in launchpad ubuntu ask, but I received in answer that that isn't a right place to send a bug. Can I send here info?
[10:07] <thekorn> antoIT: hi antonio, can you use apport to file the bug, and then add additional informtion to the bugreport in a comment
[10:07] <thekorn> or by changing the description afterwards
[10:07] <thekorn> ups, that was not supposed to be a question ;)
[10:54] <antoIT> thekorn: thanks about your answer. I changed question in a bug. I hope that this can help to solve problem. I cannot use 11.04 because of radeon driver crash. In any case my bug is https://bugs.launchpad.net/ubuntu/+bug/775439
[10:54] <ubot4`> Launchpad bug 775439 in ubuntu "ubuntu 11.04 ati open driver bug. Crash during boot (affects: 1) (heat: 6)" [Undecided,New]
[12:06] <jibel> mr_pouit, mvo , Hi, can you look at bug 775411, I don't know where a fix should be provided xubuntu or update-manager ?
[12:06] <ubot4`> Launchpad bug 775411 in xubuntu-meta (Ubuntu) (and 1 other project) "Unable to upgrade to 11.04 when both ubuntu-desktop and xubuntu-desktop are installed: conflict on notification-daemon (affects: 1) (heat: 8)" [Medium,Triaged] https://launchpad.net/bugs/775411
[12:11] <mvo> jibel: thanks, looking now
[13:47] <kamusin> hggdh, Eeebotu is shocked and doesn't speak anymore
[13:47] <hggdh> oh darn!
[13:49] <pedro_> Eeebotu is fighting on IRak
[13:51] <hggdh> yep. *THIS* time it was not eeebotu, but the network...
[13:51] <hggdh> kamusin: thank you for the heads up
[13:51] <kamusin> pedro_, Haha is twitting about that..
[13:51] <pedro_> heh
[13:52] <kamusin> twitting/tweeting he
[13:52] <kamusin> hggdh, you are welcome ;)
=== seb128_ is now known as seb128
[15:18] <jibel> RedSingularity, hi, for bug 772409 there's no need to file a new report, the error is "gzip: stdout: No space left on device", the advice is to free some space and try again.
[15:18] <ubot4`> Launchpad bug 772409 in update-manager (Ubuntu) "Kubuntu 10.10 to 11.04 "Could not calculate the upgrade" (affects: 1) (heat: 8)" [Undecided,Invalid] https://launchpad.net/bugs/772409
[15:20] <RedSingularity> jibel: Hey. Any specific directory or no?
[15:22] <RedSingularity> jibel: hmmm and why is there no notification in the main.log about space?
[15:25] <RedSingularity> It seems he only gets the space error when running the install command for linux-image-2.6.38-8-generic.  I would have thought there would be an error notification in the main.log as well
[15:26] <jibel> RedSingularity, in main.log you'll only find the result of the dpkg command:
[15:26] <jibel> 2011-04-28 16:13:17,403 ERROR got an error from dpkg for pkg: 'linux-image-2.6.38-8-generic': 'subprocess installed post-installation script returned error exit status 2'
[15:26] <jibel> the actual error is in apt-term.log
[15:27] <jibel> RedSingularity, in apt-term.log the error is line 33379
[15:27] <RedSingularity> jibel: well there it is!  See it now  ;)
[15:27] <RedSingularity> forgot all about term.log :(
[15:29] <jibel> RedSingularity, for dist-upgrades, first check main.log if it's a resolver issue (failed to calculate the upgrade), then read apt.log, if it's a package installation error (ERROR: dpkg ...) then search the error in apt-term.log
[15:30] <jibel> I mean release upgrades of course
[15:30] <bcurtiswx> wow, empathy bug reports flooding my inbox
[15:31] <RedSingularity> jibel: thats usually the sequence I follow but i have not checked a term.log in a while.  Thats why i forgot all about it ;)  Thanks for bringing it to my attention.  Much appreciated as usual buddy :)
[15:32] <jibel> RedSingularity, my pleasure :)
[16:39] <shanttu> Hi. I'm having a problem with my ati-card. I have searched a lot about this specific problem and asked guys @ #ati without a solution. OK to report to launchpad?
[16:40] <shanttu> Problem is the same on both open and proprietary drivers.
[16:41] <ChrisGagnon> shanttu: Yes. report it on launchpad, if you can't find a dupe there.
[16:42] <shanttu> ChrisCagnon: Thanks, I'll do that.
[19:23] <njin> hello fellows, the lagpack italian for gnome-orca contain an error, but the upstream translation is correct, what i can do ? thanks
=== zyga is now known as zyga-afk
[23:21] <micahg> hggdh: I thought moving from Fix Released and Won't FIx was restricted
[23:22] <bdmurray> micahg: nope
[23:22] <hggdh> micahg: I thought so, but Brian corrected me
[23:22] <hggdh> and not even moving to fix released seems to be locked
[23:22] <micahg> bdmurray: won't fix is locked, right?
[23:22] <micahg> hggdh: moving to never was AFAIK
[23:22] <bdmurray> to won't fix is
[23:23] <micahg> bdmurray: from won't fix also, right?
[23:23] <bdmurray> micahg: no, don't thinks so but trying to find bug number
[23:23]  * hggdh laughs seeing micahg repeating pretty much the same questions, the same order...
[23:23] <micahg> if won't fix is changeable by anyone, the LP team broke the ACL
[23:24] <hggdh> no, it should not
[23:24] <micahg> unless there was some decision that I missed
[23:25] <bdmurray> bug 655385
[23:26] <ubot4`> Launchpad bug 655385 in launchpad "Allow bug status change from Triaged only for bug supervisor (affects: 2) (dups: 1) (heat: 10)" [High,Opinion] https://launchpad.net/bugs/655385
[23:27] <bdmurray> well, that's just from Triaged I guess
[23:28] <micahg> bdmurray: right
[23:28] <bdmurray> I've a non bug control account and could confirm from won't fix
[23:29] <bdmurray> "Having a look now, it seems we only check WONTFIX to prevent someone other than bug supervisor unsetting it."
[23:29] <bdmurray> from comment 3 so ...
[23:30] <bdmurray> to Triaged and to Won't Fix are restricted
[23:30] <bdmurray> from Won't Fix is too
[23:30] <bdmurray> but that's it
[23:30] <micahg> k
[23:31] <hggdh> and nothing about fix released...
[23:31]  * hggdh goes editing again
[23:35] <bdmurray> thanks