[00:20] So has anyone else noticed the bug where when you mouse over System > Preferences, and then (or immediately) mouse over Administration, it pauses for a second or so? [00:20] Really weird, but seems like it might be a bug. ^^ [00:21] It's been doing that in Gnome for as long as I can remember [00:21] Yfrwlf: sounds strange. [00:21] and it only does it the first time, like it's a menu loading problem, no clue [00:22] unless it's building an index the very first time, i've no idea. [00:22] I'd be really surprised if I'm the only one who has seen it happen. :P [00:23] is it just on first install, or the first time it gets done after boot? [00:23] maybe it's the menu freezing until all the icons in Preferences have loaded, before it will display the Administration menu. [00:24] i would expect that's the case [00:24] I think it's when ever the menu isn't in RAM or something, it's after every login or after a while of not using that menu maybe? Would have to experiment with it. Very minor thing, but I've actually seen it freak out new users and such, it's just a cosmetic thing. ^^ [00:24] how much ram do you actually have in that machine? [00:24] (that you're seeing it on?) [00:25] it happens on all different machines on all different Gnome versions that I've used for the past several years [00:25] though I'm sure it's less noticeable on faster machines obviously [00:25] very strange. [00:26] my machine's likely too high specced to see it, then. [00:26] wow, I can easily reproduce it on the fly, too. [00:26] you could probably try reporting it to gnome directly, as it sounds like a gnome 'bug' that it's not optimised fully. [00:27] yeah, alright. ^^ [00:27] under metacity, presumably? or compiz? [00:28] I created another user, test, and then logged onto test, (on this same computer), and was able to reproduce it. After the first time though like I said, it doesn't happen anymore until you log out or possibly unless it leaves RAM. [00:28] I don't *think* it's the window manager, but let me check. [00:32] Great, now I'm just finding other bugs >.< [00:34] After switching to Metacity and logging in as test again, the menu bug isn't there, but maybe it's like saved in memory already or something...when I went in as test, it was Metacity. Then I switched back to my user, switched to Compiz, and logged in as test again to find that Metacity was running. When I then tried to turn on Compiz as test, it said desktop effects couldn't be enabled. Oiy =P [00:34] fun stuff ^^ [00:37] hrm. that wasn't friendly. [00:37] oh wow, even after disabling Compiz on my user, and logging into test and trying to enable it there, it won't let me. [00:37] What wasn't friendly? [00:38] locking my screen on jaunty wouldn't let me unlock it again. [00:38] That's what I'm using too btw. [00:38] I haven't had that problem before though, how did you manage to do that? [00:41] not sure. it's probably transient, as i hadn't rebooted after some updates which it was telling me to [00:41] that may have been it then, I remember when you could keep on using programs even if they had been updated, but I notice some problems with doing that sometimes. [00:42] yup [00:43] but, just restart X at the very least, and that should fix the screen locking problem you're having, if that's the cause of it. [00:43] should be using the new versions of everything at that point [00:43] to my knowledge [00:44] i thought i'd done so, from the last time it locked up, but then it happened again [00:44] ah well, will look again later === r0bby_ is now known as r0bby === bddebian2 is now known as bddebian [01:32] Bug #319393 to wishlist please [01:32] Launchpad bug 319393 in user-setup "Hardcodes ubuntu username" [Undecided,New] https://launchpad.net/bugs/319393 [01:48] Bug #319776 to the lovely wishlist please [01:48] Launchpad bug 319776 in gnome-session "don't allow shut down if there are other user with opened sessions" [Undecided,New] https://launchpad.net/bugs/319776 [01:49] * Hobbsee doesn't think the first one is a wishlist item. [01:49] and i'm surethat second one is a dupe. [01:50] in fact, the guest account already accounts for that. [01:52] k, Hobbsee, could you please leave that note on the bug as it'll be better for you to note it [01:53] sigh, he's left. [01:53] heh [01:53] shoot & run [01:54] he could have actually *tested* it, to see that the bug reporter was mostly wrong, but no... [01:54] lets just smack it with a 'wishlist' status, and be done with it. [01:54] all one needs is to read and mis-interpret, I guess [01:55] there is also one thing -- a lot of the new folks are worried of doing something wrng, and would rather somebody else did it [01:56] weird. I thought the second one would be a question of capabilities [01:57] presumably because they don't actually know what htey're doing, and suspect they're not being so helpful anyway, and don't want to get jumped on when it's wrong. [01:58] but the first is the classic "original reporter is known competent, so please don't put rubbish (ie, it's not a bug. BRAINSTORM IT!) on their bugs" [01:58] which i don't think there's a solution for yet [02:00] * Hobbsee invalidates it, and claims it for 5-a-day [02:11] heh === hggdh is now known as hggdh|away [07:18] good morning [07:27] good morning [07:36] hi dholbach [07:36] hiya thekorn === BugMaN1 is now known as BugMaN === ara_ is now known as ara === asac_ is now known as asac === shiyee_ is now known as shiyee [11:28] folks don't forget that today we have a hug day : https://wiki.ubuntu.com/UbuntuBugDay/20090122 [11:29] there's still a lot of bugs to be triaged, feel free to grab anyone and squash it === LucidFox_ is now known as LucidFox [13:11] I found a bug concerning powersaved, is it oky to discuss this here? [13:55] there's still a lot of bugs to squash, join the fun : https://wiki.ubuntu.com/UbuntuBugDay/20090122 [13:55] good day MrKanister [13:56] hello pedro_ [13:59] pedro_: Sorry, I have to deliver some magazines. Will be back in about two hours. [13:59] pedro_: Then I will join the fun ;). Bye [13:59] MrKanister: see you later! === hggdh|away is now known as hggdh [15:21] Boo [15:41] https://wiki.ubuntu.com/UbuntuDeveloperWeek - Day 4 to kick off in #ubuntu-classroom in 19m. :-) [16:13] hI EVERYONE. [16:13] hi steve555 [16:14] Hi BUGabundo.What is the progress of triarging Firefox3.0? [16:15] I have no idea! [16:15] just logon [16:15] I haven't got it installed yet,but I have done in the past.I personally use Opera10.0 Alppha [16:15] aint even got the courage to look into my inbox [16:16] I thought this was the channel to help out if we can.Which one is it? [16:16] ask dholbach [16:17] BUGabundo: about what? [16:17] dholbach: please refer to steve555 ^^^^^^^^ [16:18] I have no idea about Firefox [16:18] asac is the mastermind there :) [16:18] Where can I reach him?I have treid to get on a hug day and a even a Ubuntu classroom,but I seem to miss them,as I live in the U.K G.M.T [16:20] I'm curently using Kubuntu Jaunty Jackalope Alpha3. [16:20] he's in here :) [16:21] Ok,I'll ask him. [16:21] asac,do you need help with Firefox3.0? [16:23] steve555: please visit #ubuntu-mozillateam [16:23] Ok,thanks BUGabundo. [16:24] steve555: The firefox hugday is today. https://wiki.ubuntu.com/UbuntuBugDay/20090122 [16:25] Yeah I know,am I in time?it's Greenwich Mean Time where I live. [16:27] yes, it's only 4:27pm there [16:28] And, the bugs can be triaged anytime :-) [16:51] Before I go,I'm have a bit of trouble importing some keys from Launchpad.When I refrseh my repositoires with Synaptic,I get this error:: GPG error: http://ppa.launchpad.net jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7D2C7A23BF810CD5 [17:02] omg the graphs for the hug day are looking amazing! [17:02] http://people.ubuntu.com/~brian/complete-graphs/firefox-3.0/plots/firefox-3.0-week-new.png <- wow [17:04] pedro_: see http://status.qa.ubuntu.com/qapkgstatus/firefox-3.0 for more details [17:08] -300 WOW [17:26] here [17:27] does Martin Mai hang out here sometimes? [17:27] pedro_: ? [17:27] ffox 3 got 300 new bugs eliminated from yesterday to today [17:27] asac: yes Mrkanister is his nickname [17:27] thats really awesome [17:28] https://wiki.ubuntu.com/MozillaTeam/Bugs/TriagersHandbook [17:28] asac: yeah that's pretty awesome, did you looked at the graphs today? [17:28] pedro_: the graph is not up-to-date ... NEw count is now 420 [17:28] ;) [17:29] woohoo ;-) [17:29] we can reduce them to less to 400, right charlie-tca, chrisccoulson ? ;-) [17:29] pedro_: i would stick the triagers handbook in topic ... would be much more efficient if folks would remember those few points [17:30] asac: alright, i'm editing the hug day page with that information [17:30] pedro_: i will update topic... you can just stick the same info there too [17:31] pedro_: i cannot do that [17:31] not an op [17:31] /topic Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | Firefox NEW/Incomplete processing: https://wiki.ubuntu.com/MozillaTeam/Bugs/TriagersHandbook | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu [17:32] thats what i wanted to do [17:32] bdmurray: ^ [17:32] on it [17:32] hi there [17:32] bdmurray: wait a sec ;) [17:32] (from the ubuntu berlin bug jam) [17:32] /topic Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | FFox New/Incomplete processing: https://wiki.ubuntu.com/MozillaTeam/Bugs/TriagersHandbook | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu [17:32] bdmurray: ^^ [17:32] shortened and adjusted case [17:33] thanks [17:33] ccm: hello there === bdmurray changed the topic of #ubuntu-bugs to: Ubuntu BugSquad | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | FFox New/Incomplete processing: https://wiki.ubuntu.com/MozillaTeam/Bugs/TriagersHandbook | If you have been triaging bugs for a while, please apply to https://launchpad.net/~ubuntu-bugcontrol/ | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu [17:34] asac: Could we get some package bug guidelines setup for firefox? [17:36] bdmurray: just the triagers handbook should be enough [17:36] a link [17:36] bdmurray: and maybe a direct reference to https://wiki.ubuntu.com/MozillaTeam/NormalizedBugFormat [17:36] asac: I meant information to show when people report a bug about firefx [17:36] bdmurray: for that lets just use the NormalizedBugFormat page ;) [17:36] Maybe a link to https://wiki.ubuntu.com/MozillaTeam/Bugs ? [17:37] would be helpful if folks file directly in that format [17:37] so we can foward [17:37] yes. lets use that and the normalized format thing [17:38] bdmurray: how do we get those instructions there? [17:39] asac: https://lists.ubuntu.com/archives/ubuntu-devel/2009-January/027206.html [17:39] ok so not me ;) [17:39] so lets state: [17:40] Well, you could stick a firefox file in the package-bug-guidelines folder and I'd update the instructions for it / them. [17:40] bdmurray: package-bug-guidlines? is that abranch? [17:40] its a folder in ubuntu-qa-tools branch [18:04] Hi guys. Do you think I can list these 2 bugreports together? https://bugs.launchpad.net/ubuntu/+bug/320105 and https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/319553 the last one happens to be mine. [18:04] Launchpad bug 320105 in ubuntu "Intrepid Ibex (8.10) loses Internet connectivity after installation" [Undecided,New] [18:20] pedro_: I'll grab some bugs in a bit; got my 3-month old grandson right now [18:23] How often are is the status of packages updated at http://status.qa.ubuntu.com/qapkgstatus/ ? [18:23] the graphs are updated hourly [18:25] bdmurray: Thanks. And the information on the left of a package page (for example http://status.qa.ubuntu.com/qapkgstatus/firefox-3.0) ? [18:25] ogasawara: that's ^ hourly too right? [18:26] bdmurray, MrKanister: yup I believe it is hourly [18:26] bdmurray: Maybe. If yes it gets updated in 14 minutes. Was just curious :) [18:27] thanks ogasawara [18:27] MrKanister: although I'm not positive if it on the hour or half past [18:29] ogasawara: hm. ok [18:29] MrKanister: ah, every 30min - or at least that's what it used to be [18:30] ogasawara: Don't think so because the last update was at 17:42 UTC (so more than half an hour back) [18:31] the raw data comes from http://people.ubuntu.com/~brian/complete-graphs/firefox-3.0/firefox-3.0-changes.html [18:32] bdmurray: Thanks. Maybe the data is then updated once a day [18:33] MrKanister: is there a specific stat you're noticing is not updating [18:35] ogasawara: No. As I said, I was just curious about it. [18:36] ogasawara: uh, you were right with the half an hour update. Now it reads: "Last updated at 18:10 UTC" === apachelogger is now known as apachelogger_ [18:59] wow...thats what I call a BugDay [18:59] Hi guys. Do you think I can list these 2 bugreports together? https://bugs.launchpad.net/ubuntu/+bug/320105 and https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/319553 the last one happens to be mine. [18:59] Launchpad bug 320105 in ubuntu "Intrepid Ibex (8.10) loses Internet connectivity after installation" [Undecided,New] [18:59] * MrKanister huggs pedro_ and charlie-tca [19:00] * pedro_ hugs the hug day hero MrKanister [19:02] * MrKanister wishes more people would start on BugDays because everyone is able to [19:02] CrownAmbassador: it's hard to tell without hardware information for bug 320105 [19:02] Launchpad bug 320105 in ubuntu "Intrepid Ibex (8.10) loses Internet connectivity after installation" [Undecided,New] https://launchpad.net/bugs/320105 [19:02] bdmurray: Thanks, I'll ask for hardware info then. [19:13] MrKanister: hi. i added a link for ffox triaging to topic ... please take a look ;) [19:13] and thanks for all the work :) ... i definitly owe you a few beers ;) [19:13] asac: Thank you. This is a very useful site [19:14] Unfortunately the fun is nearly over ;) [19:14] MrKanister: most important for the further upstream triage is to get the description in the normalized format mentioned there [19:14] MrKanister: how comes? [19:14] asac: No problem. I like to work with nice people :) [19:15] asac: No worries. I mean for the bug day this week [19:15] heh [19:15] sure [19:15] but i think i saw your mails outside of hug days ;) [19:15] asac: What do you mean? (maybe my english is to bad) [19:16] oh..you mean nromal bugs? [19:16] *normal [19:16] MrKanister: yeah ;) [19:16] https://wiki.ubuntu.com/MozillaTeam/NormalizedBugFormat [19:17] hm...with that information I think we should do another BugDay on firefox [19:18] we nearly halved the number of "new" bugs [19:19] MrKanister: true. there will surely be more new bugs. [19:20] asac: Oh, yes. I very much hope more people will participate on BugDays because it is not difficult. Everyone can do it [19:21] thats why i tried to keep the handbook as simple as possible. New/Incomplete bugs can all be processed really easily [19:21] and Confirmed too most of the time [19:22] at least for firefox i cannot really forward bugs wher ei have to digg the important info out of the lengthy discussion. [19:22] asac: yup, the handbook is really awesome ;) [19:23] MrKanister: how do you reach the triagers? just the hug day announce mail? [19:23] asac: Yes, via some mailing-lists -> https://wiki.ubuntu.com/UbuntuBugDay/Organizing#Announcement%20E-mail [19:24] asac: I hate the bug tracker of mozilla, too [19:24] asac: The gnome but tracker is soo much more user friendly [19:25] MrKanister: what exactly is more user friendly? [19:25] asac: *the gnome bug tracker [19:25] asac: (sorry, typo) [19:25] MrKanister: yes, but makes that more user friendly? [19:25] personally, i think processing bugs for gnome is easier because you have lots of small apps [19:25] with a small number of bugs [19:26] so you can usually see everything on one or a few patges [19:26] asac: I mean it is easier to use, so it's "user friendly" [19:26] the tricky thing about firefox is that you have to find the right component in bugzilla to get any sensible search results [19:26] (or doesn't that phrase exist in English?) [19:26] MrKanister: yes, but both is bugzilla ... so my question is: why is it easier to use? [19:27] my guess is that its easier to use because of the reasons i gave above [19:27] asac: Oh, your are right, it's because of a better overview over the packages [19:28] MrKanister: sure. thats hard to do for a huge app like firefox. if you want to triage bugs upstream and wonder about which component to file against/look just ask [19:28] at best in #ubuntu-mozillateam [19:29] asac: Thanks. Will bookmark that === apachelogger_ is now known as apachelogger [19:29] thanks [19:29] cu then ;) [19:30] asac: See you [19:32] Hi guys,I'm having trouble uploading traces produced by Apport-qt to Launchpad.It comes up with this error: [19:32] Could not upload report data to crash database: [19:32] [19:36] asac: I wonder if https://wiki.ubuntu.com/MozillaTeam/Bugs/TriagersHandbook should replace https://wiki.ubuntu.com/MozillaTeam/Bugs/Procedures which is linked on https://wiki.ubuntu.com/MozillaTeam/ [19:36] steve555: apport hasnt worked since jaunty started [19:36] steve555: just file the bug manually and attach a retrace [19:37] Is there another package I could use to upload? [19:37] your web browser [19:39] Hmmm,I'll give it a go,is it ok to attach the .crash to the bug report that apport created? [19:39] steve555: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/314212 ; even better, add to this one [19:39] Launchpad bug 314212 in apport "Apport unable to report crash - urlopen error timed out" [Undecided,Confirmed] [19:39] use apport-retrace to get just a stack trace [19:40] (that's what i was told to do when i asked a couple days ago) [19:43] so it is still broken? [19:43] yes [19:44] sigh [19:44] I'll look at it today [19:44] yay, just ran it. At least now I do not get a file://... URL, but the (common) url error [19:44] hggdh: which one? [19:45] urlopen timed out [19:47] hggdh: when uploading? [19:47] the last comment in bug 314212 has a workaround that might be worth trying [19:47] Launchpad bug 314212 in apport "Apport unable to report crash - urlopen error timed out" [Undecided,Confirmed] https://launchpad.net/bugs/314212 [19:48] let me run it again [19:48] MrKanister: not sure. procedures is definitly work-in-stalled-progress ... but is suppsoed to be more complete than handbook [19:49] but we should definitly link the handbook from there [19:49] asac: ok, a link would be good [19:50] darn! now I am back to file:// on the FFox call [19:51] hggdh: its still an improvement though ;) [19:51] bdmurray, heh. At least the blob was uploaded [19:57] hey mrkanister, are there any more firefox bugs left to triage ;) [19:57] chrisccoulson: hehe, hundreds :) [19:58] chrisccoulson: But we managed to halve the new bugs [19:58] thats good. sorry i haven't helped out much - been busy doing some other stuff [19:59] chrisccoulson: no problem. I think many also preferred the UbuntuDeveloperWeek to triaging bugs :D [20:00] i'd completely forgotten about that. i wouldn't have minded getting involved [20:01] chrisccoulson: You forgot the DeveloperWeek? That's sad, I was a great event and I learned alot [20:01] *it was [20:01] which sessions did you go along too? [20:02] MrKanister: check https://wiki.ubuntu.com/MozillaTeam/Bugs/Procedures please [20:02] chrisccoulson: The Launchpad API, Baazar for packaging, Boot performance, etc [20:02] i forgot too, what with the couple million people converging on every spare bit of sidewalk and empty chair in every restaurant/cafe around my apartment [20:03] asac: Looks great. That way we don't have a page without content ;) Thanks [20:04] 3 guesses where maco lives [20:04] lol [20:05] ^_^ [20:05] i lack internets in my apartment, so those cafes are somewhat necessary for me to get online [20:07] that's not good. i couldn't live without my internet connection :( [20:07] my old roommate moved out and took the internet with her. i get new internet tomorrow. [20:07] thats good then. i bet you're looking forward to that! [20:07] yes [20:15] Is anyone interested in looking at the one-line patch in bug 296925? [20:15] Launchpad bug 296925 in linux "linux-image postinst script ignores warn_reboot in /etc/kernel-img.conf" [Undecided,Confirmed] https://launchpad.net/bugs/296925 [20:16] bug 319204 was just mentioned in #ubuntu-motu - IIUC it doesn't make sense to say "Please sync from DEHS". Is there a standard phrasing for a "Please update to newer upstream" bug? [20:16] Launchpad bug 319204 in flumotion "Please sync flumotion (universe) with the scoop of the Debian External Health Status" [Undecided,New] https://launchpad.net/bugs/319204 [20:30] Is the needs-packaging tag appropriate for a "please package new upstream version" bug? [20:35] i think needs-packaging is just for new (not in the archive at all) packages [20:37] maxb: bug number? [20:38] bug 319204 was just mentioned in #ubuntu-motu - IIUC it doesn't make sense to say "Please sync from DEHS". Is there a standard phrasing for a "Please update to newer upstream" bug? [20:38] Launchpad bug 319204 in flumotion "Please sync flumotion (universe) with the scoop of the Debian External Health Status" [Undecided,New] https://launchpad.net/bugs/319204 [20:38] https://wiki.ubuntu.com/SyncRequestProcess [20:40] 0.5.3 ? [20:45] maxb: I linked it to the debian new upstream request [20:46] maxb: I'll try and see if it's easy to upgrade [20:46] You make a good point, linking it makes sense, but I was wondering what to do to the bugtitle, since it's falsely masquerading as a sync request at present [20:48] well there's no upstream debian package yet :P [20:49] Can you change it to something appropriate and set the needs-packaging tag? [20:49] I think it's ok to use it in this case [20:53] hm.. lool.. [20:55] maxb: I the user with nickname lool in freenode is the maintainer of flumotion. In #ubuntu-devel or #ubuntu-motu probably [20:55] -I [21:10] maxb: let me know if you talk with the maintainer [21:11] I don't really mind, actually my interest in this is mainly limited to not having a non-sync bug masquerading as a sync bug [21:11] :-) [21:13] ok, but it happened to me twice to upgrade new packages and then the maintainer comes and says "Oh, I've had this packaged all along, I just forgot/been busy/some excuse here" [21:39] bdmurray, what do you think, should we workaround bug 314212 and temporary increase the timeout in storeblob.py? [21:39] Launchpad bug 314212 in apport "Apport unable to report crash - urlopen error timed out" [Undecided,Confirmed] https://launchpad.net/bugs/314212 [21:43] thekorn_: yes, it seems like the fastest solution [21:44] bdmurray, ok, let me prepare a patch [21:59] bdmurray, I think this is the best solution: http://paste.ubuntu.com/108389/ [22:00] but it is untested on jaunty [22:01] thekorn_, no timeout is dangerous [22:01] hggdh, why, that's the default [22:01] this is then a bad default. Never to timeout can cause some other problems [22:02] instead set it -- say -- to 180 seconds. [22:02] never timeout -> leads to hanging [22:02] hggdh, so this need to be fixed in python itself [22:02] probably, I agree. But, right now, I like your approach, at least it bypasses the issue [22:03] a very low timeout is as bad as a very large timeout [22:03] hey guys, when youre finished with your current debate, can you have a quick look at bug 319825 and let me know if you think its a kernel issue or a problem with NM (see daemon.log). No rush. [22:03] Launchpad bug 319825 in linux "acer_wmi in Jaunty on Aspire One exposes non-functional (always disabled) rfkill device" [Medium,New] https://launchpad.net/bugs/319825 [22:03] thekorn_, it is just my opinion [22:04] hggdh, yeah, I totally agree with you, [22:05] but since launchpad is "a bit slow" sometimes, I'm unable to judge which is the best timeout === Afwas__ is now known as Afwas [22:05] Rocket2DMn - it would be nice to see the output of "lshal" for that bug report [22:05] alright chrisccoulson , ill ask for that, what specifically are we looking for in that? [22:07] i haven't checked the whole report yet, but any object with the capability "killswitch" [22:07] just to get a more complete picture of the hardware [22:08] i think from the description that its not a nm bug [22:08] bdmurray, I'm going to sleep now, I would be nice if you could apply the patch, otherwise I will do it tomorrow morning, [22:08] feel free to adjust the timeout [22:09] thekorn_: okay, I think using something other than none would be best [22:09] if you think it makes more sense [22:09] * hggdh has had some very bad experiences with no TCP timeouts [22:10] chrisccoulson, based on how the user gets around the behavior by removing a module, it seems that it is kernel. However, daemon.log has problems with NM which had me thinking that maybe NM isn't communicating well with the correct driver/module [22:10] thekorn_: thanks for the patch [22:10] np, no big deal [22:12] chrisccoulson, there is also a link to a bug in daemon.log that is still Confirmed against NM, whereas everything else seems to be fixed in intrepid. [22:12] im not sure what to make of that [23:13] hi Rocket2DMn - sorry, i had to disappear somewhere [23:13] thats ok [23:13] i'll take another look in a second [23:14] ok, theres really no rush [23:14] ill be here [23:14] someone set the bug #319204 as triaged please, I'm sending a new upstream package to debian as we speak [23:14] Launchpad bug 319204 in flumotion "Please package new upstream version of flumotion (universe)" [Undecided,New] https://launchpad.net/bugs/319204 [23:16] savvas: wishlist? [23:16] charlie-tca: yes, thanks :) [23:17] You are welcome. done [23:17] a really weird package [23:17] Yeah, it happens [23:18] It probably needs some adjustments, but at least I made it a bit easier for the maintainer :) [23:19] My thought is every bit helps :-) [23:21] Rocket2DMn - the bug report number referenced in that reporters daemon.log is just displayed because NM found an unmanaged device (a device specified in /etc/network/interfaces). the "state CONNECTED forced" bit just means that NM will tell any application which asks that the particular connection is connected, regardless of the actual state of the connection [23:21] it seems that the killswitch state from HAL doesn't get updated [23:22] it would probably be good also to run "lshal -m", then toggle the killswitch and see if anything changes state [23:22] chrisccoulson: hi [23:22] hi seb128 [23:22] chrisccoulson: is the new mixer applet working now for you? [23:23] not entirely [23:23] chrisccoulson: and are your session dialog correctly themed since the gnome-session update? [23:23] chrisccoulson: is it starting correctly rather [23:23] 1 second - i'll try that in a moment [23:23] the volume control actually appears to be suffering a race with pulseaudio [23:23] the status icon doesn't update when pulseaudio comes on and off-line [23:24] if the applet starts before pulseaudio, no icon displays [23:24] theres a report upstream somewhere [23:24] ok, so there is probably a race during session start there [23:24] it seems so. the applet and pulseaudio start in the same phase [23:24] I get an error in .xsession-errors which seems to indicate that the applet is started before the sound server there [23:25] yeah, i get that too. i tried writing a patch, but i cant get it to work [23:26] gnome bug 564311 is the applet problem [23:26] Gnome bug 564311 in gnome-volume-control ""Connection failed" when PA drops off" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=564311 [23:27] right, the new comment seems to be the issue [23:27] pulseaudio started before gnome-session in intrepid, but that's not a good solution [23:28] chadwik, what should the reporter do when monitoring in order to trigger the killswitch? is that a keyboard function key, or removal of the module, or something else? [23:28] chrisccoulson, ** ^ [23:29] Rocket2DMn - they can run "lshal -m" in a terminal and then physically move the killswitch. if it changes state, then the reporter will see some output on the terminal [23:29] if he doesn't, then it's almost certainly a kernel bug [23:29] seb128 - i see the problem with gnome-session dialog too [23:29] chrisccoulson: ok, good, I need to ping vuntz about it [23:30] the dialog is a distro patch, I need to try if the upstream dialog get the same issue [23:30] yeah, thats a good idea [23:30] i might try building it without in a bit [23:31] what do you mean physically move the killswitch? i guess i dont fully understand what a killswitch is then. i thought this was like a power switch, though laptops dont typically have an actually switch, they use a key combo or a dedicated button i guess [23:31] ah, you might be correct [23:32] Rocket2DMn: sometimes they're slidey things [23:32] i got the impression that whatever button or switch he was using actually physically turned the RF off. he seems to suggest that [23:32] hey maco, i dont think ive ever seen a laptop with a slide power switch for wireless [23:32] i suppose they are out there ethough [23:32] my old company dell had a slider [23:33] nice [23:33] rfkill switches are increasing massively in popularity [23:33] i don't have a laptop anymore to know:( [23:33] new company won't give me one! [23:33] cheapskates [23:34] so we want the user to toggle with killswitch while the acer_wmi module is loaded then right? [23:34] i think so [23:35] ok, what if something shows when he does it then? [23:35] it depends what shows i suppose [23:35] if the state of the killswitch changes then it might be a NM problem. but i think thats unlikely having read the description [23:36] when i toggle on my laptop, it doesnt say anything about a killswitch, but it shows something else about ButtonPressed = wlan [23:36] chrisccoulson: http://bugzilla.gnome.org/show_bug.cgi?id=567958 [23:36] Gnome bug 567958 in general "Shutdown and Logout dialogs not themed" [Normal,Unconfirmed] [23:37] chrisccoulson: were you referring to bug 319443 earlier? [23:37] Launchpad bug 319443 in pulseaudio "[jaunty] no volume applet because pulse gets started too late" [Low,Confirmed] https://launchpad.net/bugs/319443 [23:37] seb128 - that makes sense. so, it seems like it's definately an upstream issue unless the reporter is a jaunty user [23:38] chrisccoulson: there is a screenshot and that's the upstream dialog [23:38]