[00:26] kklimonda - thanks - i will have a look at those traces in the morning if that's ok [00:26] i need to get some sleep soon too:) [06:58] good morning === dholbach_ is now known as dholbach [09:47] <_Ripp3r_> hello [09:47] <_Ripp3r_> does anyone using alfa500mw wireless adapter under ubuntu , im having problem it dont work as it should... [09:48] <_Ripp3r_> signal strengh is around 15-20% ,should be normal strengh up to 100% [09:49] <_Ripp3r_> nvm [10:00] :) === johe|work is now known as johe === nixternal is now known as Guest88294 [12:40] hello [12:42] hi alourie [12:43] thekorn: is this the place to get help when my bug triagers canned reponses greasemonkey addons do not work? [12:44] alourie: I think so, best to get in contact with bdmurray when he is awake [12:45] thekorn: right, thanks [12:45] which timezone he is in? [12:46] alourie: yanky timezone +8 iirc [12:46] ha [12:47] ok === marjomercado is now known as marjo [15:37] Is there a response for somebody that took a bug that was marked fix released in two packages and changed it to new with no explanation? [15:39] MTecknology, not really, you can point they to the HowToTriage and Bug/Status documentation though [16:29] m weird [16:30] is anybody able to edit a bug description with edge? [16:32] oh [16:35] I'm getting a Entity-body was not a well-formed JSON document. on some bugs [16:35] i'll better ask on #launchpad [16:39] alourie: hi! what's going on? [16:40] bdmurray: hi! [16:40] bdmurray: I was trying to use canned responses in Firefox with lp-stockreplies script, but it doesn't do anything... [16:41] does it work with Ff 3.5 [16:41] alourie: how did you install them? from the PPA (a firefox extension) or just stockreplies w/ greasemonkey? [16:46] on this machine (Windows) it's just strockreplies with greasemonkey, at home it was PPA [16:46] bdmurray: ^^ [16:47] hmm, I haven't tried it on Windows (not that it should necessarily matter) but it does work for me on Karmic with Firefox 3.5 [16:47] Do you even see the replies? [16:48] bdmurray: that's the issue - no [16:48] tags work, karma works, but replies do not show anything [16:49] each script has a debug = 0 bit. you could flip that to 1 and then use the error console to look for messages from the script [16:50] bdmurray: oh [16:50] ok, I'll try that... [16:50] bdmurray: now have to run home, talk to you later. Thanks for the help :-) [17:53] chrisccoulson: I can't get anything interesting from devkit-power --verbose --monitor-detail.. [17:53] does it not output anything at all? [17:54] (i haven't actually tried it yet) [17:54] chrisccoulson: It seems that every few times absolutely nothing is logged when I plug in my mouse and after I plug it out crash occurs [17:55] chrisccoulson: the log http://pastebin.com/f7fedcc83 [17:56] hmmmm, i need to have a bit more of a think about it. i'm just going through my e-mails first though [17:56] chrisccoulson: I have connected usb twice but only one try was logged - second one was crash. It's consistent in this that when I plug in and get no log devkit-power crashes after plug out [17:57] kklimonda - could you try running "dbus-monitor --system" and triggering the crash? [17:58] http://pastebin.com/f3d767795 [17:58] chrisccoulson: btw, not that I am in xterm session I'm not logged out [17:59] it's faster to work on it this way but it may be that something is different. should I try from normal gnome? [17:59] well, devkit-power crashes the same, with the same g_critical() message [18:00] kklimonda - yeah, i was just wondering that [18:00] "signal sender=org.freedesktop.DBus -> dest=(null destination) serial=8 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged" [18:01] "string "org.freedesktop.DeviceKit.Power"" [18:01] oh, are you saying the devkit-power utility crashes, or the daemon? [18:02] something wierd happens with the daemon because there is a NameOwnerChanged signal there [18:02] hmm.. from what I can say there is no daemon running at this moment.. [18:03] it has probably crashed already. Let me try this with a fresh session then [18:06] chrisccoulson: ok, I have a better dbus-monitor log now [18:06] http://pastebin.com/f5dc691b3 [18:07] when I connect my mouse/keyboard for a second time there is no DeviceAdded signal [18:07] but I have both DeviceRemoved signals emitted [18:09] kklimonda - yeah, spotted. so, there is no entry to remove from the hash table on the client side, which is why it crashes [18:10] so, there is a bug in the library, and a bug in the daemon too [18:13] kklimonda - would you mind attaching the output from dbus-monitor to the bug report? [18:19] sure [18:21] done [18:21] thanks [18:26] kklimonda - would you also be able to kill the existing devkit-power-daemon process, and start a new one like "/usr/lib/devicekit-power/devkit-power-daemon --verbose 2>&1 /tmp/dkp.log" to capture what happens to the daemon too? [18:27] you would probably need to do that before starting your session though [18:27] i'm just trying to figure out why you don't see the signal when the device is added a second time [18:29] hmmm, the only time it doesn't emit the DeviceAdded signal is during coldplug, but that shouldn't happen unless it restarts [18:35] chrisccoulson: http://pastebin.com/f31ce7dc6 [18:36] I'm also attaching it to report [18:39] thanks, i'll take a look at that shortly [18:51] bdmurray: hi [18:53] alourie: on a call at the moment [19:00] kklimonda - it seems that your mouse isn't actually removed from the device list in the daemon when you remove it the first time (although it generates the DeviceRemoved signal), so when you add it, it doesn't generate the DeviceAdded signal [19:01] seems there is a missing call to dkp_device_list_remove === thekorn_ is now known as thekorn [19:20] alourie: back now === micahg1 is now known as micahg [19:31] bdmurray: hi, I'm looking at the script, and there's no "debug" param. Am I missing it? === billybigrigger_ is now known as billybigrigger1 [20:48] can someone confirm a bug in karmic for me? you need to be able to share your desktop and vnc in [20:49] hey ppl of the buggy world [20:50] looks like it's just me and you haha [20:58] bdmurray: well, I'll have to catch you tomorrow... [21:18] kklimonda - i forwarded your devkit-power bug upstream now. it has enough info [22:41] How do you use apport to add information to a bug report? [22:42] apport-collect bug# [22:43] bdmurray: will it pick up on the package name [22:44] yes, it looks at the bug report for the package affected and then runs the appropriate hook === Mez__ is now known as Mez