[00:02] <yuriy> bdmurray: i guess i'm wondering if it's appropriate to have a knetworkmanager page if the bugs on the hug day page are for network-manager and not network-manager-applet
[00:05] <yuriy> and each network-manager-applet and knetworkmanager cover almost 100 bugs in addition to the 100+ for network-manager
[00:05] <bdmurray> I think not having network-manager-applet on there may have been an oversight on our part
[00:10] <yuriy> bdmurray: yeah i was thinking adding it would be good until i noticed how many more bugs that is
[00:12] <bdmurray> sometimes I sort the list using "-nr" and just cut it off after 50 or so
[00:12] <bdmurray> So those would be the 50 newest knetworkmanager bugs
[00:13] <bdmurray> because we really want to get the Hardy bugs triaged / fixed in time
[00:16] <bdmurray> yuriy: Does that help / make sense at all?
[00:20] <jlparise> hey hows it going
[00:21] <jlparise> I'm interested in helping out, wanted more info
[00:25] <bdmurray> jlparise: What kind of info bug triaging is a large topic.
[00:25] <jlparise> well basically I want to help with Ubuntu in some way
[00:25] <jlparise> and I am trying to figure out how
[00:26] <jlparise> I've been using it since Dapper, currently on Gutsy
[00:26] <bdmurray> Today we are looking at bug reports related to update-manager and we have a list of ubgs at https://wiki.ubuntu.com/UbuntuBugDay/20080318
[00:26] <jlparise> I see
[00:27] <bdmurray> Frequently bug reports come in without enough information so we work with reporters to gather that info
[00:27] <jlparise> I see
[00:27] <jlparise> So how can I help?  Just going through the list here?
[00:27] <bdmurray> We have a series of debugging procedure wiki pages at https://wiki.ubuntu.com/DebuggingProcedures
[00:28] <bdmurray> right! we could look at a bug together if you'd like.
[00:29] <jlparise> That would be fine
[00:30] <bdmurray> greg-g: are you still around?
[00:31] <bdmurray> jlparise: lets look at bug 195790 then
[00:31] <ubotu> Launchpad bug 195790 in update-manager "do-release-upgrade failed on gusty -> hardy" [Undecided,New] https://launchpad.net/bugs/195790
[00:32] <jlparise> ok, let me pull that one up here
[00:33] <jlparise> ok I have it up now
[00:33] <greg-g> bdmurray: yeah
[00:33] <bdmurray> greg-g: would you mind helping jlparise out I have to run for a bit.
[00:33] <greg-g> sure
[00:34] <greg-g> ok, I'm looking at that bug now
[00:34] <jlparise> ok later bdmurray
[00:34] <bdmurray> sorry about running off.  thanks greg-g!
[00:34] <greg-g> np, take care bdmurray
[00:34] <jlparise> no problem
[00:35] <jlparise> ok greg-g I have the bug opened up
[00:36] <jlparise> I am not sure what langauge it is written in though...
[00:37] <greg-g> neither am I, luckily most of the error message is in english
[00:38] <jlparise> yeh I see that
[00:38] <greg-g> so, I'm trying to figure it out before I walk you through it since I am not sure as to what the problem is right now, don't want to start you down the wrong path
[00:39] <jlparise> It looks eastern european perhaps
[00:41] <greg-g> jlparise: well, since I couldn't find anything obvious, here is how we can start
[00:41] <jlparise> ok
[00:41] <jlparise> I tried some online translations for czech, polish, danish, no luck
[00:41] <greg-g> since, looking at the wiki page about debugging update-manager ( https://wiki.ubuntu.com/DebuggingUpdateManager ) asks for all the logs which are already provided, that is good
[00:42] <greg-g> by the way, debugging procedures for many packages can be found here: https://wiki.ubuntu.com/DebuggingProcedures
[00:43] <jlparise> Yeh i see them all attached to the posts
[00:43] <greg-g> and this is the general knowledge base for triaging: https://wiki.ubuntu.com/BugSquad/KnowledgeBase
[00:44] <greg-g> ok, so...  all the information is there that is needed by the developers to start diagnosing the problem.  Are job is not to tell them how to fix it, but just making sure that the information is available so they can.
[00:44] <jlparise> oh ok
[00:44] <jlparise> I did notice something at the end of the apt.log
[00:44] <greg-g> but, we also want to make sure that this bug has not been reported already, to do that we can try to search update-manager bugs for some keywords which we think would pull of duplicates
[00:45] <jlparise> refering to mybuntu
[00:45] <jlparise> ok I'll look around
[00:45] <greg-g> yeah, I saw that
[00:46] <greg-g> so, we could reply and ask the reporter to try "sudo apt-get reinstall mythbuntu-desktop"
[00:46] <greg-g> and in this case, we would try to phrase that in the most clear english we can, since they might not be native/secondary/tertiary speakers of it
[00:47] <jlparise> I see
[00:47] <jlparise> it seems like they are not
[00:48] <greg-g> so, if you want to reply with something to the effect of "Thanks for your report.  Please try reinstalling mythbuntu by typing this in the terminal: "sudo apt-get reinstall mythbuntu-desktop"  Reply with the output of that command.  Thanks!"
[00:49] <jlparise> done
[00:50] <greg-g> ok, good comment.  one note, in the future try to imply that you are awaiting a response from them
[00:50] <jlparise> I replied before you send that message
[00:50] <jlparise> sent
[00:50] <jlparise> so I added another
[00:50] <greg-g> no worries
[00:50] <greg-g> no, that is ok
[00:50] <greg-g> you can leave it as is.
[00:50] <jlparise> ok
[00:50] <jlparise> that was pretty easy
[00:51] <greg-g> but, now that we have effectively asked for more information (having them try something) we should set the Status to "Incomplete" indicating that the information required to work on fixing the bug is not all available yet.
[00:51] <greg-g> you do that by clicking the down-arrow next to the word New in the yellow bar
[00:51] <jlparise> ok, how do I do that
[00:51] <jlparise> I am logged in
[00:52] <jlparise> ok should i assign it to me? or no one?
[00:52] <greg-g> do you see the down arrow next to the word "New" in that yellow bar at the top of the page?
[00:52] <jlparise> got it
[00:52] <greg-g> no, leave it unassigned, assignment is to indicate who is working on _fixing_ the issue, as in a developer
[00:52] <greg-g> but, check the box that says "subscribe me to emails for this bug report"
[00:53] <jlparise> oh ok
[00:53] <greg-g> or, if you have already changed the status, click on the "Subscribe" link on the left
[00:54] <jlparise> ok I subscribed when I changed the status
[00:54] <greg-g> that way, when they reply with more info, you will be notified and can then act accordingly (setting to confirmed if more information is provided, invalidating if it is not reproducible, etc)
[00:54] <greg-g> now, lets search for duplicates, just to be safe
[00:54] <jlparise> ok
[00:54] <greg-g> some good keyterms for that one would be stuff like "mythbuntu-desktop
[00:55] <greg-g> and "x11-apps" since that was mentioned in the body of the report
[00:55] <greg-g> you can search update-manager bugs at this link: https://bugs.launchpad.net/ubuntu/+source/update-manager
[00:55] <jlparise> ok, now to find the search box...
[00:56] <greg-g> you can get to that page by clicking on the package in the yellow bar "update-manager" (I usually open a new tab)
[00:56] <greg-g> or, if there is no package assigned (which sometimes happens) you can search all Ubuntu bugs by going here: https://bugs.launchpad.net/ubuntu
[00:57] <jlparise> I didnt turn up much
[00:57] <jlparise> just oen bug that seems unrelated
[00:57] <jlparise> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/180032
[00:57] <ubotu> Launchpad bug 180032 in update-manager "Update removes vital media codex." [Undecided,In progress]
[00:58] <greg-g> yeah, so, we can fairly safely assuming that this is not a duplicate
[00:58] <jlparise> ok
[00:58] <jlparise> that seems logical to me
[00:58] <jlparise> what would we havedone if it was a dupe?
[00:59] <greg-g> so, quick steps: 1) make sure it is a real bug (not a support request) 2) check for duplicates 3) if no duplicates, ask for more information 4) subscribe to bug 5) wait for reply
[00:59] <ubotu> Launchpad bug 5 in rosetta "Plone Placeless Translation Service metadata missing from po files" [Wishlist,Fix released] https://launchpad.net/bugs/5
[00:59] <jlparise> whats step 5 in more detail?
[01:00] <greg-g> if it was a duplicate: the bug that is newer/has less information you would click on "mark as duplicate" then enter the bug number of the real bug
[01:00] <jlparise> ok
[01:01] <greg-g> literally wait for them to provide the requested information, and if they gave you enough that the developers can now start working on the bug you can set it to "Triaged" and ask someone in here to set the Importance accordingly
[01:01] <yuriy> it's like a mini triaging class in here :)
[01:01] <jlparise> cool
[01:01] <greg-g> yuriy: ツ
[01:01] <jlparise> yeh I am just learnin the ropes
[01:02] <greg-g> unfortunately, I need to start on some other work now... I'll be around to answer quick questions, but no more lecturing ;)
[01:02] <jlparise> well thanks for showing me the ropes
[01:02] <jlparise> now I can finally help out with Ubuntu a bit
[01:02] <greg-g> jlparise: be sure to read these pages: https://wiki.ubuntu.com/BugSquad/KnowledgeBase  and  https://wiki.ubuntu.com/Bugs/HowToTriage
[01:03] <greg-g> there is a wealth of information there, helped me a lot when I first started
[01:03] <jlparise> Oh man homework from professor greg-g....
[01:03] <jlparise> I'll read it over
[01:03] <greg-g> thanks for taking interest
[01:03] <jlparise> have a good night
[01:03] <greg-g> and I expect a 5 page, single spaced report :)
[01:03] <jlparise> :-O
[01:04] <greg-g> take care
[01:04] <jlparise> you too
[01:04]  * greg-g is away
[01:57]  * hefe_bia takes "participate in a BugDay" off the "things not done yet" list and heads for sleep... It was fun. C ya.
[02:18] <jlparise> well I did 5 of them, thats enough for today
[02:20] <jlparise> night all
[02:42] <damian> auto-identify
[04:39] <bdmurray> yuriy: I've started graphing knetworkmanager for you. Let me know if graphs don't show up in a bit.
[05:30]  * calc likes the way his openoffice graphs look now :)
[05:31] <calc> only ~ 37 new bugs
[10:33] <james_w> does anyone know which package provides the cd boot menu?
[10:33] <james_w> 1 Try Ubuntu without any change to your computer
[10:33] <james_w> 2. Install Ubuntu
[10:33] <ogra_cmpc> james_w, thats a mix ...
[10:33] <james_w> etc.
[10:33] <ogra_cmpc> gfxboot-theme is one part
[10:34] <james_w> I'm seeing a problem in the help text.
[10:34] <ogra_cmpc> debian-cd another
[10:34] <james_w> ah, it's probably the former, thanks.
[10:34] <ogra_cmpc> the text likely comes from debian-cd
[10:34] <ogra_cmpc> its  tad confusing :)
[10:34] <ogra_cmpc> * a tad
[10:35] <james_w> ah, ok, thanks.
[10:39] <ogra_cmpc> james_w, usually cjwatson is the best person to ask about gfxboot
[10:40] <james_w> yeah, I'm guessing he's a tad busy though :-)
[10:40] <james_w> I can't find this text in debian-cd or gfxboot-theme-ubuntu either
[10:41] <james_w> let's try gfxboot
[13:26] <gregory> hello is pedro v. in this channel?
[13:27] <james_w> gregory: it's probably still a little early for him, but he will be around later.
[13:27] <pedro_> gregory: that's me
[13:27]  * james_w feels silly
[13:28] <gregory> james_w: thank you nevertheless
[13:29] <gregory> pedro_: i have submitted #203676. its an useless stacktrace, though i have installed all dbg-sym packages via  dpkg-query -W -f='${package;-50}\n' | xargs sudo apt-get install
[13:29] <pedro_> gregory: let me have a look to it
[13:29] <gregory> why is it useless. its not possible to catch crashes even with *dbgsym?
[13:30] <pedro_> gregory: that's not your side, the apport service was unable to get a backtrace of it
[13:32] <gregory> ah is there already a RFE for it? btw. i could not file it since i dont have enough knowledge, but would like to subscribe to the issue
[13:32] <pedro_> gregory: It'd be nice if you can submit a complete backtrace, we have some instructions on how to do it at https://wiki.ubuntu.com/Backtrace
[13:32] <pedro_> since you have installed all the dbgsym package it'd be easy to do
[13:32] <pedro_> s/package/packages
[13:34] <gregory> are stacktraces "valid", if i run gdb with firefox every time i browse (the crashes appear randomly). i would end with a huge log file of course, but it still be valid?
[13:34] <qense> hello!
[13:37] <james_w> gregory: when it crashes rub
[13:38] <pedro_> gregory: not all the stacktraces are good enough to determine where's the problem for example http://launchpadlibrarian.net/12726996/Stacktrace.txt
[13:38] <james_w> run "bt full" then "thread apply all bt"
[13:38] <pedro_> just compare that one with http://launchpadlibrarian.net/11669528/Stacktrace.txt
[13:38] <james_w> those are the important bit usually.
[13:39] <Iulian> Hey
[13:40] <pedro_> yep, follow what james_w is saying. And if you want to save that log to a file you can use "set logging on file.txt" inside gdb  for saving the output to a file that you can submit later to a bug report
[13:40] <gregory> james_w: ok
[13:40] <pedro_> hey Iulian!
[13:40] <gregory> pedro_: ok
[13:40] <Iulian> Hello pedro_ ;)
[13:44] <gregory> sorry, me again: "/usr/bin/firefox": not in executable format: File format not recognized  ?
[13:44] <gregory> ah
[13:44] <gregory> script, not "exe"
[13:45] <james_w> /usr/lib/firefox/firefox-bin I think
[13:46] <james_w> Any suggestion on how I can work out why nautilus fails to start f-spot on the latest hardy live cd?
[13:46] <james_w> It thinks for a while but doesn't start, it starts ok from the menu.
[13:46] <james_w> strace isn't telling me much.
[13:52] <gregory> ok or not ok? http://paste.ubuntu-nl.org/60149/
[13:53] <james_w> gregory: it doesn't look like you ran firefox? Did it start?
[13:53] <seb128> james_w: how do you try to open it?
[13:54] <james_w> seb128: I open my CF card and it says "The media contains digital photos" and gives a button to start f-spot at the top.
[13:55] <gregory> james_w: it doesnt start from within gdb. if i use the same command without the gdb it starts.
[13:55] <gregory> james_w: one moment
[13:55] <seb128> james_w: ok, no idea bout that, I've no CF there
[13:56] <james_w> seb128: I've got the source now, I'm trying to find how it does it.
[13:56] <james_w> gregory: run gdb on it's own.
[13:57] <james_w> gregory: then type "file /usr/lib/firefox/firefox-bin"
[13:57] <james_w> gregory: and then "run"
[13:57] <gregory> james_w: i made a mistake, sorry, i didnt "run" inside gdb
[13:58] <gregory> my question about the paste is: is it ok that no debug symbols are found at the beginning?
[13:59] <bddebian> Boo
[14:00] <james_w> gregory: that seems odd, can you confirm that you have firefox-2-dbgsym or firefox-3.0-dbgsym installed, depending on which version you are running?
[14:00] <james_w> hi bddebian
[14:00] <bddebian> Hi james_w
[14:04] <gregory> james_w: status: install ok installed
[14:04] <james_w> gregory: ok, that's strange then
[14:05] <james_w> aha, it's not passing a needed option to f-spot
[14:06] <gregory> thats the status quo: http://paste.ubuntu-nl.org/60152/
[14:08] <james_w> so, it should be using the f-spot-view.desktop, but it appears to use f-spot.desktop.
[14:13] <seb128> james_w: that seems to be correct, f-spot is the application, -view is the viewer, no?
[14:14] <james_w> seb128: well, .xsession-errors has the usage message
[14:15] <seb128> james_w: what message is that exactly?
[14:15] <james_w> I presume it is trying to open it as "f-spot folder"
[14:15] <james_w> when you need to do "f-spot --view folder"
[14:16] <james_w> which is what the f-spot-view.desktop has as its Exec
[14:16] <james_w> I'm looking in gio as to why it chooses f-spot over f-spot-view
[14:16] <gregory> gregory: about the missing symbols i have submitted #203913, will be back when i have more news
[14:17] <james_w> ah, default_app = g_app_info_get_default_for_type (x_content_type, FALSE); in nautilus
[14:18] <james_w> so it's saying that the .desktop doesn't need to support URIs.
[14:18] <seb128> james_w: it's likely just using the one having x-content/image-dcf in his mimetype list
[14:19] <james_w> ah yes, fspot-view doesn't list that.
[14:19] <james_w> I guess this is f-spot's problem then.
[14:19] <seb128> yes
[14:20] <james_w> https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/202998
[14:20] <ubotu> Launchpad bug 202998 in f-spot "f-spot doesn't want to open with the nautilus new shortcut bar" [Undecided,Confirmed]
[14:20] <seb128> we have a distro patch from a contributor which added the change
[14:20] <james_w> I should look more closely at existing reports.
[14:20] <james_w> seb128: the change to f-spot's .desktop?
[14:20] <seb128> james_w: bug #191475
[14:20] <ubotu> Launchpad bug 191475 in rhythmbox "[hardy] media tab in file management preferences missing applications" [Low,Fix released] https://launchpad.net/bugs/191475
[14:22] <seb128> james_w: maybe we should have used the contributor version, ie using --import
[14:24] <james_w> seb128: yeah, that seems to be the most appropriate flag.
[14:25] <james_w> so, to get this straight in my head, we need to drop the mime type from f-spot.desktop, and then create f-spot-import.desktop with it.
[14:25] <seb128> james_w: yeah, basically drop the patch we have and use the contributor version
[14:26] <james_w> seb128: great, thanks, I'll come up with a patch to that bug report and reference the original, or re-open the original?
[14:26] <james_w> also, should I propose the bug for hardy? Is that the correct protocol?
[14:26] <seb128> james_w: reopen
[14:27] <seb128> james_w: milestone it for hardy if you want, if you can let me know I'll do it
[14:27] <seb128> I'm not sure about the target for hardy thing
[14:27] <seb128> I don't use it
[14:27] <james_w> I can only propose I think, so it needs someone with more power to make it visible.
[14:27] <james_w> I haven't worked out all the different lists yet.
[14:29] <james_w> also, what do you think about nautilus changing the flag that I pointed out to require that applications launched that way support URIs? (i.e. have %u or %U in their Exec)
[14:29] <james_w> will that break on a lot of things that accept it, but don't specify so?
[14:36] <seb128> james_w: I'm not sure to understand the nautilus change you want to do
[14:37] <james_w> so the function call I posted above has FALSE as the second parameter.
[14:38] <james_w> If that parameter is TRUE it means "whatever application you pass back must support URIs", which translates to having %u or %U in the Exec line.
[14:38] <james_w> and if nautilus is going to pass it a URI then it should ask for an application that allows it to do that.
[14:39] <james_w> however, what I am not clear on is whether there will be applications that allow you to do that but don't have %U, and so nautilus wouldn't be able to use them.
[14:39] <seb128> ideally nautilus should be clever
[14:39] <seb128> and call the applications with a path or uri corresponding to what it can handle
[14:41] <elmargol> iwl3945 really sucks :(
[15:09] <james_w> https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/191475
[15:09] <ubotu> Launchpad bug 191475 in f-spot "[hardy] media tab in file management preferences missing applications" [Low,In progress]
[15:10] <james_w> should I subscribe u-main-sponsors?
[15:10] <seb128> james_w: yes please
[15:11] <james_w> done.
[15:12] <james_w> thanks for your help seb128
[15:13] <seb128> james_w: you are welcome, thanks for the work on it
[15:14] <james_w> no problem.
[15:14] <james_w> is this the best use of time during pre-beta testing?
[15:15] <james_w> would it have been better to just file it and add it as a todo for post-beta?
[15:16] <seb128> james_w: we need to get those bugs fixed, now is a good time for that
[15:24] <james_w> seb128: cool.
[15:39] <james_w> so, I still can't find the location of the problematic text in the boot menu of the cd, can anyone else give a hint?
[15:40] <james_w> It's in the F2 or F3 help text, I can't remember which.
[15:41] <seb128> james_w: ask on #ubuntu-installer maybe?
[15:42] <bdmurray> james_w: what text?
[15:48] <james_w> "Ubuntu" may be replaced by the name of any other distribution. This help text is generic.
[15:48] <james_w> or something similar, I don't think it's meant to be there.
[15:48] <james_w> seb128: thanks, I didn't know about this channel.
[17:52] <qense> can bug 203677 be set as confirmed or does it need more information?
[17:52] <ubotu> Launchpad bug 203677 in gnome-power-manager "gnome-power-manager cpufreq problem" [Undecided,Incomplete] https://launchpad.net/bugs/203677
[17:54] <pedro_> qense: confirmed is ok since the reported submitted the info you requested, if the maintainer needs more info he'll ask for it
[17:58] <qense> ok, thx
[18:08] <nxvl> can some put the importance on Bug #203449
[18:08] <ubotu> Launchpad bug 203449 in dovecot "[dovecot] [CVE-2008-1199, CVE-2008-1218] privilege escalation" [Undecided,Confirmed] https://launchpad.net/bugs/203449
[18:08] <james_w> hi nxvl
[18:08] <nxvl> james_w: :D
[18:09] <james_w> nxvl: you get everywhere don't you :)
[18:10] <nxvl> james_w: i'm a virus :D
[18:16] <pedro_> nxvl: done :-)
[18:22] <bdmurray> pedro_: hello!
[18:22] <pedro_> hey bdmurray
[18:24] <bdmurray> tomorrow KDE seems to be looking at knetworkmanager should we add some network-manager-applet bugs for tomorrow?
[18:24] <bdmurray> s/KDE/Kubuntu
[18:27] <pedro_> yeah totally, it seems to have a lot of new bugs too
[18:31] <pedro_> ok, I've already added them
[18:31] <bdmurray> awesome!  thanks pedro_
[18:31] <pedro_> sure, thanks you for the reminder
[18:33] <nxvl> pedro_: thanks
[18:34] <pedro_> nxvl: de nada :-)
[18:37] <nxvl> bdmurray: did you check the mail i send you with my appliance?
[18:39] <bdmurray> nxvl: I've seen your e-mail but not had a chance to review it yet
[18:40] <qense> How's the designing of the new application procedure going?
[18:45] <nxvl> bdmurray: oh! ok, let me know when you check it please
[18:45]  * nxvl HUGS bdmurray 
[19:21] <qense> What is the upstream bug tracker for GDM, GNOME?
[19:22] <pedro_> qense: yes
[19:22] <pedro_> qense: http://bugzilla.gnome.org
[19:23] <qense> ok, thx
[19:23] <qense> (ah, of course :P GNOME Display Manager. I forgot)
[19:41] <qense> I go, bye
[19:50] <gregory> hello, i am stuck with https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/203913
[19:50] <ubotu> Launchpad bug 203913 in firefox-3.0 "debug symbols?" [Undecided,New]
[20:22] <hefe_bia_> Hi, can somebody set the Importance for bug #192204 (Wishlist, I think)?
[20:22] <ubotu> Launchpad bug 192204 in update-manager "Error message on unmet dependencies during update should be improved" [Undecided,Confirmed] https://launchpad.net/bugs/192204
[20:25] <hefe_bia_> Also: Might this be a duplicate of bug #63659 ? I'm not sure.
[20:25] <ubotu> Launchpad bug 63659 in update-manager "dist-upgrade should give better error-message when it can't upgrade because of transient archive issues" [Wishlist,Confirmed] https://launchpad.net/bugs/63659
[21:08] <Arby> for bug 194186 what is the appropriate log to ask for, dpkg.log?
[21:08] <ubotu> Launchpad bug 194186 in update-manager "update with adept manager failed" [Undecided,New] https://launchpad.net/bugs/194186
[21:09] <Arby> also, should it be reassigned to adept-manager rather than update manager?
[21:14] <mvo> please reassign adept bugs to adept :)
[21:18] <Arby> thought so
[21:19] <Arby> am I right asking for dpkg.log?
[21:19] <Arby> mvo^
[21:19]  * mvo checks
[21:19] <mvo> yes, that sounds good
[21:20] <Arby> thanks
[21:20] <mvo> its a bit unfortunate that adept has its own way when it comes to running dpkg, this means that it does not write a termianl log like apt or synaptic
[21:20] <mvo> usually we have nowdays good debug information in /var/log/apt/term.log
[21:20] <mvo> and during the dist-upgrade of course in /var/log/dist-upgrade/term.log
[21:21] <mvo> thanks Arby!
[21:21] <Arby> mvo: happy to help
[21:22] <Arby> mvo is there anything else I can do to help with update-manager?
[21:22] <Arby> besides keep whacking the bug list of course :)
[21:25] <mvo> helping with the buglist is a wonderful help already, that is really really appreciated :)
[21:30] <Arby> what else would be needed for bug 191834 to be considered complete?
[21:30] <ubotu> Launchpad bug 191834 in update-manager "Update-manager could not calculate the upgrade from feisty to gutsy" [Undecided,New] https://launchpad.net/bugs/191834
[21:30] <Arby> the logs are all there but there's nothing obviousl useful there
[21:34] <bdmurray> Arby: the dbus errors sound familiar I'd look around for a duplicate
[21:34] <mvo> Arby: I think we have enough, it looks (from apt.log) like this is a issue with nfs-common and libnfsidmap2 - there should be a master for this already. IIRC the workaround was to remove nfs-common for the upgrade
[21:34] <Arby> OK I'll go digging
[21:41] <Arby> bug 157763 looks similar, is that it?
[21:41] <ubotu> Launchpad bug 157763 in update-manager "[master] nfs-common makes upgrade calculation impossible (was: Could not calculate the upgrade)" [High,New] https://launchpad.net/bugs/157763
[21:42] <mvo> Arby: yeah, I think that is the one
[21:43] <Arby> thanks
[22:13] <Arby> mvo: any known bugs for update-manager and either udev or upstart
[22:13] <Arby> bug 191418 reports broken dependencies for both udev and upstart
[22:13] <ubotu> Launchpad bug 191418 in update-manager "Upgrade failed" [Undecided,New] https://launchpad.net/bugs/191418
[22:14] <Arby> 203765 looks possible
[22:14] <Arby> oops 203756
[22:18] <Arby> also 76840 looks like a similar upstart error
[22:37] <mvo> Arby: 191418 should be fixed now, it was a apt bug - I also added a workaround in my latest udev upload, so hopefully this one is gone now
[22:38] <mvo> But I will ask for what upgrade it happend