[00:13] hggdh, play a movie in totem ;) [00:13] or video or music... [00:26] hggdh: gnome-screensaver-command --inhibit [00:44] bdmurray, ping [00:45] deuxpi: and this will survive only for the session? and thank you, BTW [00:46] oh, OK, command blocks. So until it is ended/cancelled [00:47] nigel_nb: yes [00:47] bdmurray, I talked to hggdh earlier... about getting a few sessions on how to triage, now that bug squad has moved to a closed team [00:49] okay [00:49] bdmurray, can you teach/ask someone to teach and schedule them ? [00:51] nigel_nb: is there a particular time / date that many students will be available? [00:51] bdmurray, I was hoping we have it at 3 times on 3 dates so that more people from across TZs can participate [00:51] but otherwise, scheduling is up to the instructor [00:52] we can advertise it heavily enough to get people to join us to learn... [01:00] I'd prefer to ensure there are a sufficient number of students to warrant a class before just scheduling 1 or 3 [01:01] bdmurray, you want me to check on mail list for interest? [01:01] nigel_nb: that'd be great! [01:02] bdmurray, I'll do that then :) [02:53] can somebody mark bug 515725 as "Low"? (it's a cosmetic issue with an easy workaround) [02:53] Launchpad bug 515725 in firefox (Ubuntu) (and 1 other project) "Firefox XSL Zoom (affects: 1)" [Undecided,Confirmed] https://launchpad.net/bugs/515725 [02:56] please and thank you [03:14] bcurtiswx, ping [03:14] nigel_nb: pong [03:14] bcurtiswx, Replying to the email ;) I know we have mentorship. But just wanted to offer a lot of interested contributors a session :) [03:16] nigel_nb: not knocking down your idea. I'm sure others will speak up if they feel differently, If you really wanted to do this you'd have to find a willing teacher and enough participants to make it worthwhile [03:16] ddecator: done. I also marked it Triaged, since you linked the upstream bug. Thank you for your work there! [03:16] hggdh, thanks, i appreciate it =) [03:16] bcurtiswx, actually I asked bdmurray__, he wanted to know if there is an interest in participation [03:16] mrburns: hows things going with the reading? [03:16] bcurtiswx, that was the point of the email :) [03:17] nigel_nb: yup i saw. I guess my interpretation of the mentorship was for this purpose. I've been wrong plenty of times before [03:17] hehe :) === kermiac_ is now known as kermiac [03:23] alright i am a little confused by what "new" means cause i see some bugs that are kind of old but yet will marked as "new" [03:24] mrburns, new = not triaged [03:25] mrburns, unless a bug is reproducible, it wont move to confirmed [03:27] mrburns: yeah he's right. New is the default state given to all bugs... it has to be seen by a triager before it will get changed [03:29] so is that what most of you do look at the bug and see if you can reproduce it [03:30] mrburns: not exactly.... [03:31] mrburns: the basic idea of triage is to look at a bug and see if the bug report has the basic requirements needed to be looked at by a dev. [03:32] 1) the steps to reproduce the problem [03:33] 2)if its a crash there's debugging information you should gather from the reporter [03:33] 3) ubuntu version [03:34] if the reporter is using Karmic and past you can have them type "apport-collect " in their terminal and it will gather the necessary information for the bug from their computer [03:34] they may need to install a package, but it informs them after they type that command on what they need to do [03:35] oh interesting i didn't know you could do that [03:36] but in the apport-collect case the steps to reproduce the problem aren't taken from their computer :P [03:36] so you'll still need that most of the time [03:39] mrburns: there are two places a bug is going to need to go, once it has all of the information that I have listed above. [03:40] if the package involved is developed upstream (this being, debian, openoffice, mozilla, [listed at https://wiki.ubuntu.com/Bugs/Upstream]) it need to be forwarded upstream [03:41] if the package is specific to ubuntu it can be marked as triaged as it's already reported against the ubuntu package [03:43] mrburns: are you ready to tackle a bug together? [03:43] so if a bug is in a package like debian, openoffice forwarding upstreams passes the bug onto developers that work on specific packages like debian, openoffice, etc [03:43] yeah sure [03:43] hi bcurtiswx I had a look at the links regarding membership in your reply to the mailing list. The list seems to have grown a lot since I first looked at it a cpl of months ago. [03:44] I have now added my name to the wiki, is there anything else i need to do? [03:44] kermiac: do you mean mentorship? [03:44] yeah, sorry :) [03:44] kermiac: the launcpad page, request membership [03:44] mrburns: https://bugs.edge.launchpad.net/ubuntu/+source/empathy/+bug/517651 [03:44] Launchpad bug 517651 in empathy (Ubuntu) "Could not connect after I changed all my accounts (affects: 1)" [Undecided,New] [03:45] mrburns: the first thing you want to look for in a bug is that it has the correct package assigned to it. What do you think? [03:45] ok, done. Thanks [03:45] kermiac: you are welcome [03:46] is that empathy 2.28.1.1-0ubuntu1 [03:48] mrburns: you want to read through the description to make sure they aren't talking about a different package than the one they reported against.. (reporters can get packages mixed up) [03:49] it's ok if this take a while to get used to. If you question it at all, don't hesitate to bug someone in this room [03:49] or e-mail me if you aren't on IRC [03:50] bcurtiswx, you just conducted a learning session right here :) [03:50] oh so make sure that the bug is related to their description of the problem [03:51] mrburns: yup. Next you want to make sure that the bug has all the information it needs to be handed off to developers. Look through my stufff above and let me know if you believe it has all of the information [03:52] nigel_nb: yup, you wish for more of a session in a group format, instead of individualized like the mentorship offers [03:52] bcurtiswx, exactly! [03:53] less strain on mentors I'd say [03:53] i like that idea. i have a mentor, but him and i operate at different times so it's difficult for him to help me out [03:53] (I myself am being mentored) [03:54] don't you say, nigel_nb :-) [03:54] hggdh, hehe :) [03:54] LOL [03:55] btw, how is the mentorship supposed to work? do mentors walk people through bugs or are they more for just answering questions? [03:55] bcurtiswx: the idea has merit -- it should be as simple as possible, mostly a Q&A-type [03:55] hggdh: i wasn't trying to shoot down the idea, i agree it has merit [03:55] ddecator: it can work both ways. Usually we show you the ropes, and answer questions [03:55] bcurtiswx: i would say yes 1) i think i could reproduce it with the given information 2) there seems to be debugging information like architecture, xsessionerrors, etc 3) ubuntu 9.10 [03:56] bcurtiswx: I know, I follow you [03:56] ddecator: and correct your mistakes ;-) [03:56] of course, 'your' does not mean you personally, but all the mentees [03:57] hggdh, haha, fair enough. pedro is my mentor but he's on early in the morning (my time) and i'm always on at night so we haven't been able to talk on irc, so i wasn't sure what i was supposed to be doing...i can get up earlier to talk to him, but is talking to a mentor on irc really any more beneficial than asking this channel as a whole for advice? [03:58] mrburns: ok, agreed. The next step is to give it an importance. http://wiki.ubuntu.com/Bugs/Importance lists what each importance means.. which do you think applies? [03:59] it is pretty much the same, all in all. Another thing the mentor is expected to do is follow your bug work -- can can be done quite easily, by looking at the email generated when you change a bug [03:59] ah, simple enough...thanks hggdh =) [03:59] ddecator: and, usually, we would rather answer the questions in this channel -- so that all other lurking may benefit [04:00] bcurtiswx: i would say low [04:00] good point...i'm following bcurtiswx right now to see if i learn anything, haha [04:01] ddecator: what do you think the importance should be? [04:03] bcurtiswx, that's difficult...i'm leaning towards medium since it seems to be a "moderate impact on a core application" (since empathy is now a default app) [04:04] ddecator: " So I deleted all my accounts in empathy and reimported the accounts from pidgin. And what should I say. Now I could connect to my accounts with empathy again." [04:05] bcurtiswx, so does the workaround make it low? i'm not sure it's "easy" since you have to launch another app, adjust the settings there, then import them again... [04:05] mrburns: whats your reasoning for low? [04:12] bcurtiswx: there is a work around (use pidgin), it doesn't not effect hardware components, not a new feature [04:15] mrburns, ddecator: a good rule of thumb is that if you are unsure about the status of a bug, it's safe to set it at medium. In this case, since we're not 100% sure, and we're tied between medium and low. We'll set it at medium.. so go ahead and do that mrburns [04:16] um, bug squad can set priority? [04:16] no we can't ;) [04:16] ddecator made a good point, it is a core ubuntu app so medium applies [04:17] doh [04:17] ddecator, nigel_nb: it's been a while, i couldn't remember [04:17] no problem bcurtiswx [04:17] ok, so we've decided it's medium [04:17] :) [04:17] once we're in bugcontrol we can [04:17] mrburns: the last step would be what? [04:19] bcurtiswx: assign it to a developer [04:20] mrburns: we don't ever assign bugs as a triager.. but we have to make sure the bug gets in the right hands.. like I stated earlier. if the package is maintained not in ubuntu it needs to get forwarded, otherwise you're done and you can mark it as triaged [04:22] bcurtiswx: how do we tell if it is maintained in ubuntu [04:22] type apt-cache show empathy in terminal [04:22] read through the output and let me know [04:23] see, now i learned a new command... [04:23] bcurtiswx: Maintainer: Ubuntu Core Developers [04:24] mrburns: nope [04:24] doh [04:24] every package provided in ubuntu has Maintainer: Ubuntu Core Developers [04:24] yes... "Original-maintainer" is more important ;-) [04:25] oh [04:25] but, even then, this may not point to the real upstream [04:25] such as if the "section" suggests something different? [04:25] hggdh: is there a better way to see which packaged need to be pushed upstream? [04:26] you can look at the "Homepage" -- this is usually where upstream can be located [04:27] in this case, as a general rule, all Gnome apps are upstreamed to Gnome [04:27] mrburns, ddecator: this is a hard task to learn at first. Once you work with it for a while you'll understand it better.. once again ask in here if in doubt [04:28] but sometimes it is really difficult to find where is the upstream [04:28] so in this case it is gnome [04:28] mrburns: correct [04:28] i'm kind of starting to figure it out...i've done mostly work with packages that i know are upstream or not [04:29] in these cases, getting the source package may help: (1) there should be a file called ./debian/watch, where the source tarball can be picked; (2) look at the NEWS, README, and other files in the source [04:30] mrburns: now there are two ways you can get this pushed upstream.. if you are going through squashing a lot of bugs you can leave a stock reply [https://wiki.ubuntu.com/Bugs/Responses] asking the user to take care of it.. [04:30] or you can send it upstream yourself [04:31] the latter teaches more =) [04:31] yes. But there is more to upstreaming... [04:31] mrburns: "https://wiki.ubuntu.com/Bugs/Responses#A bug that should be handled upstream" in specific [04:32] mrburns: upstreaming is a lesson in itself and will save for another day [04:32] if you are going to start upstreaming to a particular package -- subscribe to their mailing list; if they are in an IRC channel, get to it; find out *how* they operate, and try to give them what they like to have on their bugs [04:33] mrburns: for now, set the bug to incomplete and leave the reply "Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or t [04:33] he link), so we can add a bugwatch that will inform us about its status. Thanks in advance." [04:34] but upstreaming is a good lesson to learn because it is really appreciated [04:34] it is not only upstreaming that is important, but doing it *right*. And _right_ is how upstream sees it, not necessarily like us see it [04:34] also, did we ever check for a duplicate? [04:35] ddecator: not yet.. it's difficult finding dups.. was gonna save that for another day [04:35] ok, just wanted to mention it [04:36] mrburns: the true "first" thing that you want to do is check for a duplicate. [04:36] ok yeah i guess that would make sense [04:39] mrburns: for a "hw assignment" I think you should pick 3 bugs that you want. Then work through the bugs like we did tonight. Give me an e-mail with links to the three bugs and the different things that you would do to them. Sound fair? [04:39] hggdh, a little help [04:39] ddecator: who is your mentor? [04:39] yeah sounds good [04:40] bcurtiswx, pedro [04:41] ddecator: do my hw assignment for pedro as well [04:41] nigel_nb: same for you and hggdh [04:41] bcurtiswx, I already have plenty :) [04:41] bcurtiswx, i've already started work on 4 bugs today and triaged one, but ok haha [04:41] nigel_nb: awesome :D [04:42] bcurtiswx, I just branched out to small-term patching and packaging [04:42] s/term/time [04:42] ddecator: then pick 3 bugs that you are less comfortable with [04:42] nigel_nb: what can I do for you? [04:42] bcurtiswx: how did you find that bug? just search for "new" or pick something a random [04:42] bcurtiswx, alright -_- [04:43] hggdh, a rant.... [04:43] hggdh, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/503674 [04:43] Launchpad bug 503674 in xserver-xorg-video-openchrome (Ubuntu) "[K8M800]Screen resolution used to be ok in Ubuntu 6, not in 8.04 and later (affects: 1)" [Low,Incomplete] [04:43] mrburns: i focus on empathy bugs http://bugs.edge.launchpad.net/~bcurtiswx [04:43] hggdh, last comment.. suggestions on what I should reply [04:43] nigel_nb: looking [04:44] mrburns: feel free to tackle any bugs that are "new" in https://bugs.edge.launchpad.net/ubuntu/+source/empathy [04:45] just to clarify...is confirming a bug optional for triaging? [04:45] ddecator: yes optional [04:45] bcurtiswx, well that makes things easier for me o_O [04:45] i was searching for bugs i could confirm haha [04:46] nigel_nb: this bug is a mess [04:46] mrburns: feel free to look at bugs i've triaged for reference [04:47] mrburns, just as an aside, i would avoid firefox bugs at first, mozilla has very specific ways they like bugs to be handled [04:48] bcurtiswx: ok sounds good [04:48] nigel_nb: I think the OP has some valid points [04:49] hggdh, the priority to low is wrong? (I donno x team's rules) [04:50] mrburns: one major thing I forgot.. it's mandatory that all bugs you triage you subscribe to.. otherwise you won't get e-mails when someone replies to a bug [04:50] hggdh, while he does have some right points, the comments were for setting priority to low [04:50] nigel_nb: it sounds correct -- one user affected (even if the OP does not agree) [04:52] but the other points are correct. The OP kept on repeating ignorance, and pretty much all suggestions were badly worded in terms of what to do (expecting deep knowledge) [04:52] real bad work by the commenters [04:53] I was about to start replying when the X team took over, so after that I really didn't keep track much [04:53] I dont think we can do much other than ask the X team..can we? [04:54] gnite all [04:55] well, yes, we can ping Bryce, at least [04:55] ah, yes [04:59] can someone pls confirm that bug 517611 should be converted to a question [04:59] Launchpad bug 517611 in sun-java6 (Ubuntu) "Newbie: Error while downloading/installing Java 6 doc using Synaptic Package Manager (affects: 1)" [Undecided,New] https://launchpad.net/bugs/517611 [05:00] bcurtiswx: thanks for your help [05:00] mrburns: yw, we'll continue another day, nite [05:37] My ubuntu lucid vm guest is rolling forward 500+ years. How might I debug what's causing this/ [05:38] mr-russ: If you are running ubuntu as the host OS also, ask in #ubuntu-virt. #ubuntu-bugs is not a support channel. [05:39] Okay, I just suspected a clock change of 500 years was a bug to find a root cause for. [05:40] mr-russ: Sure, feel free to submit it against the virtualization software you are using, especially if it is a replicable bug on multiple physical machines. [05:41] mr-russ: As a data point, I'm running a Ubuntu Lucid guest here (under Virtualbox-ose) and not seeing that kind of behaviour. [05:41] I would like to try and work out how to find the cause. Ubuntu bugs don't just get fixed without knowing what's going on. [05:41] can someone confirm that i should conver bug 517611 to a question as they are asking for terminal commands & a tutorial [05:41] Launchpad bug 517611 in sun-java6 (Ubuntu) "Newbie: Error while downloading/installing Java 6 doc using Synaptic Package Manager (affects: 1)" [Undecided,New] https://launchpad.net/bugs/517611 [05:42] mr-russ: Right. Ask in a support channel for help with the issue. Such as #ubuntu-virt if the host OS is Ubuntu. You've not even said what the virtualization software you are using is, yet, BTW. There are known timing/clock issues with vmware and some kernels with high tick frequencies, or there used to be... [05:42] jmarsden: jaunty host 64bit amd, 64amd lucid guest is what I'm running. I'll just start playing around with different kernels and the like. [05:43] Then #ubuntu-virt is probably a decent place to ask for help. [05:44] kermiac, sounds like a questions to me, but i haven't had experience with that yet [05:45] thanks ddecator :) [05:46] kermiac, no problem =) [07:18] bug 517925 looks like a dupe of bug 160812. I can verify the bug in Karmic, but not in Lucid [07:18] Launchpad bug 517925 in yelp (Ubuntu) "The help files won't print (affects: 1)" [Undecided,New] https://launchpad.net/bugs/517925 [07:18] Launchpad bug 160812 in yelp (Ubuntu) "Yelp does not print images" [Low,Incomplete] https://launchpad.net/bugs/160812 [07:18] should i dupe 517925 & mark as fix released [07:18] seems like it might be SRU worthy [07:26] does anyone know if yelp would be easily backported or if it would require SRU? [09:59] Hello, I've problem with function keys on Asus Eee 1005HA with Lucid. what package should I report against? [10:03] Damascene, wats the problem? [10:04] most of them aren't working [10:06] nigel_nb, [10:06] Damascene, which ones worl? [10:06] work? [10:07] brightness darkness only [10:07] oh, not the f1 to ff12 keys? [10:08] yes [10:08] they are the f1 to f [10:08] f12 [10:09] this is the fn + some icons on key board keys right? [10:09] if you press ctrl f4 your app exits and all that stuff happens? [10:09] yes most of those icons are the f* keys [10:09] ctrl f4 closes the apps, yes. [10:12] so? [10:13] eee has had issues, I'm reading through them... gimme 5 mins? [10:13] ok thank you [10:14] to my surprise most of those keys are working on Karmic [10:18] Damascene, ah well, apparently initially none of the keys worked [10:18] now it has improved [10:18] you can file a bug against udev package [10:20] type "ubuntu-bug udev" without quotes into a terminal [10:21] ok === kermiac_ is now known as kermiac [11:09] qense, pign [11:10] ugh! spell badly with pings too! [11:10] nigel_nb: pong [11:10] :) [11:10] What's the matter? [11:10] qense, have caught up with the mailing list so far? [11:10] nigel_nb: I suppose so. [11:11] qense, I was hoping for a couple of sessions on "how to triage" for new contributors [11:11] so far, the response is good to start one. [11:11] nigel_nb: Ah, that thread. [11:11] It is a good idea, maybe something we could do monthly? [11:12] Probably. something that needs more discussion. [11:13] qense, Right now, I'm looking for someone to actually lead sessions [11:13] qense, most of the mails I get concerns about TZ difference. [11:14] nigel_nb: I wouldn't mind helping out with that, but someone like bdmurray or pedro_ have got more experience with such sessions. [11:14] qense, yes. But you can't have the same people do sessions always [11:15] valid point :) [11:15] I'm looking to more like a group of people who can help with teaching in turns [11:16] Main thing - from different TZ, so more people can actually participate in the class [11:17] nigel_nb: That is true. Maybe two sessions a month, in two different timezones, would be better. [11:17] actually we need 3 [11:18] but yes, on 3 different days is better [11:18] I'd say, create a wiki page, put some details on it and a list where people willing to lead a session can add their names to. [11:18] if we can get individual teams (like audio, x) coming up with some sessions on how to deal with their bugs, we could have a better time [11:18] Good idea, I'll do that [11:19] I'll talk to bdmurray_ and pedro_ again [11:20] ok! [11:20] qense, I've already set things in motion for a monthly Q and A (oriented to reporters) [11:20] so, now another one oriented to bug squad [11:21] nigel_nb: Good! We need people who take initiative! [11:21] :) [11:25] https://bugs.launchpad.net/ubuntu/+source/udev/+bug/518007 [11:25] Launchpad bug 518007 in udev (Ubuntu) "Asus Eee Function Keys are not working with Lucid 10.04 (affects: 1)" [Undecided,New] [11:26] is there something I can do to improve the bug report? [11:45] Can anyone confirm bug 489977? I can't. [11:45] Launchpad bug 489977 in ubuntu (and 2 other projects) "Inaccessible directory has same emblem as read-only directory (affects: 2)" [Low,Incomplete] https://launchpad.net/bugs/489977 [11:46] qense, how do I confirm change write and then read permissions? [11:47] nigel_nb: The list that's shown in the bug description is 'generated' with the command ls -l. [11:54] anyone else getting timeouts on bugs.launchpad.net & edge too? [11:56] qense, I think KDE also gets papercuts [11:56] re: https://wiki.ubuntu.com/MeetingLogs/devweek1001/KDEPaperCuts [11:56] nigel_nb: ah, thanks [11:57] np :) [11:57] #kubuntu-devel seems a better place to ask [11:57] probably, indeed [11:59] kermiac, me too. [11:59] ah, thanks Damascene - glad it's not just me :) [12:00] it seems like it's only when I'm doing a search. clicking on a direct link to a bug is fine [12:00] it was fine earlier tonight === cjohnston is now known as wikipirate [13:19] qense: hi.. Bug #488041 , you didnt assign to ubiquity , any reason for not assigning after mentioning? [13:19] Launchpad bug 488041 in ubuntu (and 1 other project) "multilanguage keyboard layout (affects: 2)" [Wishlist,Confirmed] https://launchpad.net/bugs/488041 [13:19] vish: Ah, thank you. I must have forgotten about that. [13:20] :P [13:20] fixed now [13:20] qense: i thought so :) but just wanted to make sure.. [13:21] thanks [13:21] qense, that needs to be brainstormed? [13:21] nigel_nb: What needs to be brainstormed? [13:21] the ubiquity bug [13:22] pretty big change for wishlist..isn't it? [13:22] Maybe, but it does hinder users, so I reckoned it would be worth the bug report. [13:25] um, just wanted to know the process [13:25] qense, speaking of which, there needs to be a process for Questions => bugs [13:25] when we convert them, it shows up as a bug the converter reported [13:25] nigel_nb: Isn't there already such a thing? [13:26] so when I confirm it, it looks as though I reported and confirmed a bug [13:26] nigel_nb: That doesn't matter. If you name the Question in the bug description it's ok. [13:26] We're not that rigid. ;) [13:26] ah :) [13:26] qense, btw, I loved your membership meeting [13:27] lol, +1 before you even had to introduce yourself [13:27] nigel_nb: Yeah, that was quite something. ;) It was fun. [13:27] hehe [13:27] now I know why they tell people to wait before applying [13:28] Yeah, of the ten people who had applied only three got accepted. [13:28] That's something I wanted to prevent to happen to me, so I waited. [13:29] I orignally wanted to wait a year, you've inspired me to push longer [13:30] qense, btw, do u sign up for new IDS on bug upstream trackers after becoming a member? [13:30] nigel_nb: I'm inspirational! [13:30] nigel_nb: You mean changing your mail address? [13:31] qense, yes you are [13:31] qense, yeah [13:31] I'd reckon they just change their mail address. [13:31] ah [13:32] Which is encouraged, btw. That way upstream knows Ubuntu is contributing and they know you're a Member and thus (more) thrustworthy. [13:34] hm :) [16:22] when i disble bluetooth or wifi by pressing Fn+F5 in my lenovo notebook while using vista ,after rebooting into ubuntu i cannot enable them is there any way to enable it back? [16:23] bhuvi: That would be worth a bug report. However, we aren't a support channel, so for an immediate solution I would advise you to go to #ubuntu or #ubuntu-{CountryCode}. We can help you with reporting a bug, though. [18:21] I am currently dealing with a bug report, and it seems like the issue might be related to gvfs [18:21] any tips on how to collect more information on it? [18:23] WeatherGod: Did you have a look at https://wiki.ubuntu.com/Bugs/Debugging ? [18:23] not lately... [18:23] * WeatherGod takes a look [18:23] excutes [18:23] https://wiki.ubuntu.com/DebuggingProcedures [18:23] that's the right url [18:26] https://wiki.ubuntu.com/DebuggingRemovableDevices seems out of date... [18:26] it still talks about hal [18:28] and DebuggingProcedures seems to have a dead link to DebuggingGNOMESystemTools [18:30] yes, it could indeed use some updates [18:33] I haven't been following kernel/driver development recently... what's hal been replaced with? [18:33] DeviceKit [18:33] and Udev [18:34] Fully correct would be: devicekit-disks, devicekit-power and udev. [18:34] rmunn, take a look at the Halsectomy page [18:34] although the first two were renamed to udisk and upower iirc [18:34] https://wiki.ubuntu.com/Halsectomy [18:34] oh, have they been renamed? [18:35] WeatherGod, Thanks, reading now [18:35] np [18:38] can anyone tell me what is it that gvfs does that automount can't do? [18:39] WeatherGod: like the name says: handling virtual filesystems [18:39] and userspace stuff like network:/// and trash:/// [18:40] Anyone else having trouble reaching Launchpad right now? https://bugs.launchpad.net/ is timing out for me, and I don't think it's my network connection. [18:40] nope, working fine for me [18:41] qense, so it isn't responsible for automounting USB keys and CDs? [18:41] I'll try disabling redirection to the edge server as the timeout page suggests, it's probably just the edge server that's timing out then. [18:41] no, that's devicekit-disks [18:41] iirc [18:41] yes, probably [18:42] so, udev loads the drivers... and devicekit-disks is the userland stuff? [18:43] yes, that's how it works [18:43] ok, and gvfs sets up url protocols then? [18:44] I think gvfs can mount as well, but I think it only does so on request. [18:46] rmunn: Seems to be only the bugs.lp.net page that's affected. [18:46] I would guess it would be like autofs in the sense that when someone makes a request it would figure out what needs to be mounted, maybe [18:46] I still can't get through to https://bugs.launchpad.net/ even when I SOCKS-proxy my request through to a host on a different network... I'll report my bug later. [18:46] jpds, Ah, so it's not just me then. [18:46] rmunn: I can access bug reports though just fine. [18:46] I can't imagine that it would actually do any system mountings [18:47] jpds, Yeah, me too -- when I tried https://bugs.launchpad.net/evince/+bugs I got right through. Okay, I can work with this. [18:48] WeatherGod: I'm not that familiar with disks and mounting and stuff, so I can't give you a decisive answer. [18:49] https://bugs.launchpad.net/ times out with error ID OOPS-1498O1885 by the way, if any LP admins are watching this channel. [18:49] https://lp-oops.canonical.com/oops.py/?oopsid=1498O1885 [18:50] No, wait, it's a different error ID each time... not useful to report here. Sorry. [18:50] rmunn: OOPS IDs are unique and incremented, your OOPS matches the timeout error mine has. [18:52] jpds, If you want the other OOPS IDs I got I can give them to you, but they're almost certainly the exact same thing each time. [18:52] Yeah, probably are. [18:55] qense, that's ok... it is better to not confuse me with incorrect information [18:55] :) [18:56] I did manage to find another bug report in the gvfs package that reported a similar symptom [21:20] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/510571 << How would I go about taking this upstream? [21:20] Launchpad bug 510571 in linux (Ubuntu) "Latest -11 kernel won't boot, -10 works, Lucid (affects: 7)" [Undecided,Confirmed] [21:22] arand: File a bug on bugzilla.kernel.org ? [21:24] jpds: Yes, but is there a good list of things to include on the report, or could I simply link it to this one for all info? [21:24] arand: A summary of the bug and a link would be good. [21:26] arand: I wouldn't jump that far quite yet... since kernel is custom built by ubuntu, something like that that is already receiving attention is likely to be handled by the kernel team itself. [21:27] mrand: I did try the upstream kernel which failed as well... [21:27] arand: super! In that case, yes, carry on! [21:28] About that bug, we are using the -12 kernel now [21:29] Yea, And I I fail on booting the liveCD as well, unless removing acpi from the virtualbox config, all kernels past 10 seems to be affected. [21:30] I can install in vbox using the alternate image, not the liveCD [21:30] Maybe that is the desktop cd failing? [21:30] I am also running lucid as a work machine, on hardware, using the -12 [21:39] can someone please set bug 516154 as "low"? (low because it is an uncommon configuration with an easy work around) and triaged if everything looks good to you (i sent it upstream and updated the title and description) [21:39] Launchpad bug 516154 in firefox (Ubuntu) (and 1 other project) "Firefox becomes inoperable when cookies set to "ask me every time" (affects: 1)" [Undecided,Confirmed] https://launchpad.net/bugs/516154 [21:40] qense: eheh [21:41] BUGabundo: No Empathy for you? [21:41] nope [21:41] aww [21:41]