[05:46] I have installed Ubuntu 9.04 and have notice the slowness of graphics!!! Xorg is taking up 30% of my cpu and beagle-helper is taking up 15% to 20% of my cpu... thats on avarage 50% of my cpu!!! can anyone please help me before i have to back to vista witch ran just fine.... I am a nuwbie to linux and have liked it so far but now I am stuck with this problem. [06:43] Good morning [07:35] hi pitti [07:38] hey didrocks [07:38] pitti: still reviewing SRUs? :) [07:38] every day after a release :) [07:39] good luck ;) [07:39] I spent the morning packaging the new g-p-m, though [07:39] still has some rough edges, though, so I'd like to get some more work onto that [07:39] is it working great? [07:39] oki [07:39] robert_ancell: oh, FYI, in case you are interested in g-p-m, I have a branch with 2.26.1 (to avoid double work) [07:40] didrocks: yay devicekit :) [07:40] pitti: oh, didn't know they integrated devicekit. I will have a look to it :) [07:41] didrocks: I blogged about it a while ago [07:42] found http://martinpitt.wordpress.com/2009/03/11/wanna-touch-devicekit/, remember now :) [07:42] pitti: g-p-m = gnome-power-manager? Don't think I've ever looked at it... [07:43] pitti: I will try it when you will make it available. I'm bored that my suspend to ram works so well :) [07:46] Who is the local Firefox expert? I've been looking at bug 368252 and I don't have the know-how to trace how the totem plugin is invoked. Clues are making it look like Firefox+javascript may be causing the problem.. [07:46] Launchpad bug 368252 in totem "Totem firefox plugin can't launch apple HD trailers" [Low,New] https://launchpad.net/bugs/368252 [07:47] ok, I'm off for an hour or two for a doctor appointment [07:47] see you [07:47] later [07:47] robert_ancell: asac IIRC [07:48] didrocks: cheers [07:48] y/w === tkamppeter_ is now known as tkamppeter [08:43] re [08:43] re pitti [08:47] hello pitti didrocks [08:47] hey seb128 [08:48] Hi seb128 [08:48] seb128: hey seb [08:48] hello robert_ancell [08:49] robert_ancell: how was your day? did you manage to squash some bugs? ;-) [08:51] seb128: hard going today. I worked on the totem-mozilla bug but I think it's a firefox issue? Some more work on the SSH bug, I can repeat it but I don't get what is going on [08:51] * robert_ancell has been pushing all his work upstream today :) [08:51] robert_ancell: could be for totem, it's weird that the non-hd things are working and firefox is calling totem by looking to .xsession-errors [08:52] hm, this U1 thing doesn't really seem to like me :/ [08:52] seb128: well it seems to be due to the way the page is crafted. I was hacking it apart to find what HTML/JS code is making the difference [08:52] hello [08:52] hey crevette [08:52] robert_ancell: I see [08:53] lut crevette [08:53] robert_ancell: don't spend too much time on it, reassign to firefox if the bug is there [08:53] pitti: I was wondering if it didn't work 'cause it was shut down when I was awake - it hardly never works! [08:53] hello frenchies [08:54] well, I set it up, and I see my files again which I uploaded two months ago [08:54] but it never syncs [08:54] seb128: that's my guess - I'll do that and they can reassign it back if they can say why its invoking the plugin in different ways [08:54] * crevette is interested by what is this U1 project [08:54] :) [08:54] I guess today we just know mere mortal [08:54] +s [08:54] crevette: wait until May 7 :) then the public beta will start [08:54] ECHANNEL, sorry [08:55] but well, we talked about it in the meeting yesterday [08:55] crevette: can you see http://ubuntuone.com ? [08:55] robert_ancell: ? [08:55] robert_ancell: what have you found so far? [08:55] pitti, no, I don't permission to see it :) [08:56] asac: can you look at bug 368252 - I'm a bit lost on the divide between firefox and the totem plugin [08:56] Launchpad bug 368252 in totem "Totem firefox plugin can't launch apple HD trailers" [Low,New] https://launchpad.net/bugs/368252 [08:57] robert_ancell: the rhythmbox issue, are you waiting on an another example? [08:57] robert_ancell: I think the current case is already worth fixing, what do you think [08:58] seb128: I agree. I was diving into the source but I got lost. I'm not sure if it's a gstreamer or rhythmbox issue. I was looking at the diffs but couldn't see anything. [08:59] robert_ancell: I would expect rather a gstreamer one [08:59] but I'm not sure either [08:59] it's just a random guess ;-) [08:59] seb128: I also tried the Intrepid rb but it occurs for that too - this is why I think it is probably in gstreamer [09:00] robert_ancell: what is supposed to happen when you left click? [09:01] It should open the video in fullscreen afaik [09:01] (it's just a standard link) [09:02] asac: the interesting thing that stood out in the log is "width 1" and "height 1" for the failed cases [09:10] robert_ancell: onclick="s_objectID="http://movies.apple.com/movies/paramount/star_trek/startrek-clip_480p.mov_1";return this.s_oc?this.s_oc(e):true" [09:10] thats what happens "on click" [09:10] doesnt look right [09:11] asac: yeah, do you think they've changed the page? [09:12] asac: how did you get that? I was playing around with the web developer plugin but couldn't find out how to get what a link would resolve to [09:12] robert_ancell: can you check what "this.s_oc function does? [09:12] robert_ancell: install firefox-3.0-dom-inspector [09:13] robert_ancell: then you can click on elements and see the HTML element in the inspector [09:15] tseliot: hi, did you read the xrandr capplet bug about virtual settings questions? [09:15] seb128: what bug? [09:15] * seb128 grrr at people not reading their bug emails [09:16] let me get the number, I assigned the bug to you [09:16] tseliot: bug #365210 [09:16] Launchpad bug 365210 in gnome-control-center "gnome-display-properties mistakenly requires logout to increase resolution" [Low,Confirmed] https://launchpad.net/bugs/365210 [09:16] seb128: I might have read that but I would like to know what bug you're referring to [09:16] robert_ancell: it seems to do something ... so figure out what this.s_oc function does [09:16] robert_ancell: and so on [09:16] have to get coffee now ;) [09:17] asac: ok, cheers [09:17] tseliot: I get it every time on several boxes [09:17] tseliot: it's quite annoying and would be nice to fix in a sru [09:18] seb128: I think I missed this report. I'll try to reproduce the problem here and work on a fix [09:18] tseliot: thanks [09:18] np [09:19] tseliot: it's easy, start the capplet, try a lower resolution and back to your normal one [09:19] it will not go back until you restart the capplet [09:19] and it wants to add virtual settings when not required [09:19] ie just to go back to the normal value you were using for example [09:19] seb128: and does this happen when the virtual resolution is already set in xorg.conf? [09:19] pitti: how do you deal with sync-source -a errors? [09:20] seb128: one by one, I'm afraid [09:20] tseliot: I've not tried, I'm using one screen [09:20] seb128: often we need to remove packages first, because they got renamed [09:20] pitti: is there a way to skip the broken entry or resume from there instead of redoing the whole -a ? [09:20] seb128: or binaries moved around (then -F helps) [09:20] seb128: or different orig [09:20] seb128: ah, ok, so in your case it wasn't set [09:21] pitti: could you look to the libdca error and tell me what you would do? [09:21] seb128: resuming isn't possible, I'm afraid [09:21] seb128: you have to temporarily blacklist it, -a again, rinse and repeat until it succeeds [09:21] and then resolve the temporary blacklisted ones [09:21] tseliot: I'm using one screen on ati and no, I've no virtual on this box [09:21] seb128: looking [09:21] ok [09:22] tseliot: but virtual is not required since that the normal resolution [09:22] I just start the capplet [09:22] change to 800x600 for example [09:22] ack the choice [09:22] and then try to change back to the normal value [09:22] I get the error [09:22] restart the capplet and it works [09:22] ok, thanks for the info [09:22] you're welcome, thanks for looking into it! [09:23] pitti: thanks [09:23] pitti: I've been fixing some overwritte issues yesterday by using -f for those [09:23] seb128: right, what I said; our current libdts-dev is built from the libdts source [09:23] binaries which are built by new sources [09:23] seb128: so this one should just be --force'd, I think [09:23] ok, so -f, flush, wait for publishing and -a again? [09:24] pitti: ok, can you do it while you have it locally? thanks! [09:24] seb128: or just skil flush and publisher, and immediately run -a again [09:24] pitti: oh, no need to wait for publisher? [09:24] seb128: no, just don't flush [09:24] and let it sync all over again [09:24] pitti: I was not sure where it was getting versions to compare [09:24] that should be faster [09:24] pitti: it breaks again on the same case then [09:25] even if I -f ed it [09:25] seb128: not if you temporarily blacklist it [09:25] ah ok [09:25] ok, makes sense [09:25] I will do that next time, thanks! [09:25] seb128: oh, hang on [09:25] seb128: no, I won't sync that [09:25] seb128: our libtds-dev is ubuntu modified [09:25] it won't scribble over that [09:25] it needs to be merged [09:26] (or at least checked if the changes can go) [09:26] pitti: so just blacklist it for now? [09:26] seb128: yes [09:26] I'm off, see you guys tomorrow [09:26] robert_ancell: have a nice evening see you tomorrow [09:26] robert_ancell: good night! [09:26] pitti: can you do that while you are at it? [09:26] bye [09:26] well, I'm not "at it", but *shrug* [09:26] pitti: I'll continue on sync when I'm done with what I'm doing right now [09:26] sure [09:26] pitti: ok don't bother, I though you were already sshing on the box [09:27] I will do that in a bit [09:27] seb128: doing now, don't worry [09:27] I stopped on that this night and didn't resume yet [09:27] I just kept the question for this morning ;-) [09:27] * seb128 hugs pitti [09:28] seb128: ah, that's an ancient package (gutsy) [09:28] seb128: I'll just remove the libdts source, then it should just sync [09:29] is anyone intereted in taking bug 337441 for karmic? [09:29] Launchpad bug 337441 in gnome-settings-daemon "Low disk space warning "Cancel" and "OK" buttons do the same thing" [Low,Confirmed] https://launchpad.net/bugs/337441 [09:29] chrisccoulson: you? ;-) [09:29] seb128: it'd probably be better to do a full process-removals run, I'll do that one [09:29] pitti: you rock! [09:29] seb128 - i was going to offer if noone else wanted to do it already:) [09:30] chrisccoulson: go for it, I expect we will find enough to do to not get bored without that one ;-) [09:30] i'll take that one then. thanks [09:30] thank you [09:30] seb128: right, process-removals duefully caught it [09:31] pitti - did you see my response in bug 360399? I don't think we're going to get an SRU-worthy fix to resolve this issue [09:31] Launchpad bug 360399 in tracker "Tracker Evolution Eplug missing" [Medium,Triaged] https://launchpad.net/bugs/360399 [09:32] upstream identified some issues with the plugin but when they fixed it it caused a big regression, and so they've just disabled it completely in 0.6.9x which we have in jaunty [09:32] and they're not planning any more work on that [09:33] chrisccoulson: right, I saw it; nevermind about it [09:33] you can probably unsubscribe the sponsors team and ubuntu-sru team from that if you like [09:33] at least the sponsors, yes [09:34] chrisccoulson: thanks [09:34] thanks:) [09:41] * pitti finally removes gtk+1.2 [09:42] pitti: waouh! [09:42] seems that nobody ran process-removals for some time [09:44] seb128: hmm, eel2 got removed in Debian [09:45] ROM; obsolete, no rdeps, now in nautilus [09:45] pitti: right, we got it off the CD in jaunty [09:45] still being used by g-c-c and libnautilus-burn [09:45] g-c-c ?! [09:45] and three universe packages [09:45] -- karmic/main build deps on libeel2-dev: [09:45] gnome-control-center [09:45] that's a mistake [09:46] seb128: anyway, I'll keep it for now [09:46] rdpends lists n-c-b too but that's a mistake too [09:46] we'll do another process-removal run [09:46] ok [09:46] seb128: or want me to kill it now as a kind of reminder? :-) [09:47] I would not mind you doing that [09:47] "oops", it's gone :) [09:47] I've karmic sources there and there is only 3 rdepends [09:47] yay cruft cleanup [09:47] and I expect 2 of those to be fixed when syncing the second half of the archive [09:47] absolutely [09:47] they must have fixed it in debian [09:48] let's create some breakage [09:48] and g-c-c is just a cruft left in the build-depends [09:48] karmic works waaaaay too well right now [09:48] yeah, karmic is boring [09:48] well, new kernel+uxa is quite nice, though :) [09:49] seb128: okay, process-removals done; I suggest to let that publish (12:00 CEST) and then do a sync run [09:49] should get a little further now [09:49] pitti: ok thanks [09:50] pitti: no hurry I expect the buildds are busy for the day [09:50] hehe [09:50] the first sync runs yesterday did quite some work [09:50] it also cut quite a dent into MoM main.html [09:50] ok, so I'll get back to fixing g-p-m 2.26.1 [09:51] and then I'll look into DK-disks and gnome-disk-tool [09:51] * pitti is in crack & breakage mood today [09:52] yeah [09:52] we're getting g-p-m 2.26.1 this cycle are we? [09:53] * crevette wants to have a broken distro [09:53] * chrisccoulson gives crevette a large hammer [09:53] crevette: that's my plan anyway [09:53] :) [09:53] crevette: likewise, gnome-mount/hal -> gnome-disk-tool/dk-disks [09:53] I didn't switch to karmic yet [09:54] gnome-mount is superseded by gnome-disk-tool [09:54] erm, chrisccoulson: that's my plan anyway [09:54] pitti - nice:) [09:54] * crevette is lagging behind for new gnome technology [09:54] I'm running gpm/dk-power here, but it has some small problems [09:55] what sort of problems? i know the newer g-p-m has proper consolekit support so doesn't try to do actions on the inactive VT [09:55] should fix an annoying bug i have where i press the power button on my machine and the shutdown dialog appears on all user sessions [09:57] chrisccoulson: it doesn't suspend when I close the lid [09:57] other than that, it seems to work fine [09:57] chrisccoulson: weird, I thought that problem was gone ages ago [09:58] pitti: gnome bug #573826 [09:58] pitti - my power button produces a HAL event on the system bus rather than going through X, so all running instances of g-p-m get the event and respond to it [09:58] Gnome bug 573826 in general "gdu volume monitor" [Normal,Assigned] http://bugzilla.gnome.org/show_bug.cgi?id=573826 [09:58] too [09:58] pitti: I expect they will land it upstream in 2.27 [09:58] pitti - what sort of event does your lid button produce? [09:58] seb128: you are a bug machine [09:58] lol [09:59] I spend too much time working on bugs indeed ;-) [09:59] seb128: ah, for that; thanks (I thought you referred to the lid issue) [09:59] chrisccoulson: what kind of events? I'll watch g-p-m in debug mode [09:59] pitti: no, sorry for the confusion [10:00] seb128: your's is for gvfs hal->dk, isn't it? [10:00] pitti: yes, it was a reply to your dk-disks comment [10:04] pitti - if your lid button produces a hal event, then it won't work in g-p-m 2.26.x unless you built it with --enable-legacy-buttons [10:07] chrisccoulson: indeed, pressing the power button doesn't do anything either [10:08] chrisccoulson: I just get hal events, but nothing in g-p-m [10:26] pitti - i just get HAL events too. the new g-p-m doesn't support those unless you enable the support explicitly. that should probably be enabled in karmic until all hotkey support has gone from HAL [10:31] chrisccoulson: ah, I'll have a look at this [10:32] pitti - the stuff you're interested in is in src/gpm-button.c [10:33] all the hal stuff is conditionally compiled with #ifdef HAVE_LEGACY_BUTTONS [10:33] chrisccoulson: right, so that would require a DK-acpi or something such [10:34] so to understand the big picture hal is being deprecated to DeviceKit? [10:34] the comments in there suggest that hotkey support is being removed from HAL and they will all produce keypress events through X [10:35] pitti: CEST is european time right? [10:35] pitti: ie still half an hour to wait for this publisher run? [10:36] seb128: right [10:36] thanks [10:36] chrisccoulson: many thanks, testing now [10:39] CEST is our time [10:39] mere frenchies [10:40] and all the countries around (to not appear selfish) [10:40] :) [10:42] crevette: right, what I though and has been confirmed, "european time" [10:43] sorry I'm lagging [10:44] chrisccoulson: hm, doesn't seem to help :/ [10:44] mvo: ok, I've update-notifier buggy again [10:44] mvo: it opens update-manager every time I do an apt-get install [10:46] seb128: please keep it in that state [10:46] mvo: ok [10:46] seb128: I need to for for lunch, after afterwards I would love to diagnose it [10:46] mvo: ok, I'm not touching the box until after lunch [10:46] or rather letting that in state ;-) [10:46] I will do bug triage now [10:49] chrisccoulson: ah, nevermind, working perfectly; was just my docking station going mad at me [10:49] pitti: I know you already did SRU yesterday but it would be nice if you could review libical today [10:49] pitti: we have quite some users annoyed by evolution hanging or crashing [10:50] the change should be easy enough to review [10:50] seb128: I will (I need to do SRU daily these times anyway) [10:50] thanks! [10:50] well, I do it right now; g-p-m isn't that urgent [10:55] seb128: can you please dupe some real bug reports to bug 368508, to get some affected users subscribed, and to underline the necessity for SRU? [10:55] Launchpad bug 368508 in libical "don't crash on incorrect values or errors" [Wishlist,Confirmed] https://launchpad.net/bugs/368508 [10:56] pitti: I plan to add comments on the stack of evo bugs when it's accepted [10:56] to ask people to try this change [10:56] okay [10:56] I don't want to dup since the other ones a still bugs [10:56] they will not lead to crashes but should still be fixed [10:56] a -> are [10:56] if you ask them to give feedback on this one, that's okay [10:57] (accepted) [10:58] ok, commenting now [10:58] seb128: since bug 363169 is not a regression, I'm nervous about it for SRU; it might uncover other bugs in the new functionality [10:58] Launchpad bug 363169 in libxklavier "libxklavier is built without XInput support" [Low,Confirmed] https://launchpad.net/bugs/363169 [10:58] pitti: the bug submitter is upstream and the code path different is some 7-8 lines [10:59] pitti: it's just a callback called on new device detection [10:59] right, but that hasn't been tested properly? [10:59] pitti: and it has been tested in other distros [10:59] pitti: well, I don't feel strongly about it, just upstream has been pushy to get it sru-ed [11:00] well, it's not a regression, and not at all a major bug, so it needs some more convincing to become an SRU [11:00] and we have some user complaining about keyboard settings being dropped after suspend etc [11:00] it's a "annoying bug" [11:00] it reset your keyboard settings in some cases where xorg redetect the device [11:00] but I'm fine waiting a bit to have karmic feedback or debian one [11:01] pitti - it's good that works now:) [11:03] chrisccoulson: now I just need to find out how to repair the notify-osd patch, then it's all good [11:03] i've not seen that patch. is it quite big? [11:03] it's in the bzr tree [11:04] shouldn't be too hard to port [11:05] re [11:06] pitti: I would not have sru-ed to fix the issue only since I think it's a minor one too, I'm trying to not make manage upstream there but if want to put it on hold fine with me too [11:35] mvo: lots of people still have trouble in bug 257639 [11:35] Launchpad bug 257639 in packagekit "E: The package cache file is corrupted E: _cache->open() failed, please report." [High,In progress] https://launchpad.net/bugs/257639 [11:40] servus pitti and mvo, as a work around we could disable the update cache of packagekit [11:40] this would require a backport of f876a76737e504fca161f075bd0d1b8ba386cb75 and setting the corresponding configuration option [11:41] if we disable the internal update cache of packagekit there would be no need for the apt post-update script anymore [11:42] hey glatzor, wie gehts? [11:43] pitti, oh, work time consumes a lot of my life currently - so could be better. and yourself? [11:43] glatzor: pretty good, thanks; looking forward to karmic breakage :) [11:50] mvo: are "restart required" notifications still done in tray or by a pop up in jaunty? [11:51] asac: dialog auto opening [11:51] ah ... so thats why users complain about getting that without seeing the in-firefox notification [11:55] asac: if I have an empty .mozilla/extensions/\{ec8030f7-c20a-464f-9b0e-13a3a9e97384\}/ does that mean ubufox is disabled? [11:55] mvo: i have http://paste.ubuntu.com/160607/ in /var/lib/update-notifier/user.d/firefox-3.0-restart-required ... nothing happens at all [11:55] james_w: check in tools -> addons ... search for "Ubuntu Firefox ..." [11:55] pitti, mvo: sorry for not thinking about this. but we could delay the packagekit statehaschanged action quite easily [11:55] asac: that's my old profile [11:55] * pitti merges the 73177 line diff of g-p-m dk branch to the ubuntu branch, *ugh* [11:56] asac: going back to that might lose my tabs again :-) [11:56] glatzor: do you have a diff to look at? [11:57] pitti, mvo: we could raise PK_ENGINE_STATE_CHANGED_PRIORITY_TIMEOUT in src/pk-engine.c [11:57] asac: have yu touched /var/lib/update-notifier/dpkg-run-stamp ? [11:57] james_w: not sure that i get what you mean ;) [11:57] asac: it claims to be enabled [11:57] james_w: and touching the file doesnt display the in-firefox notification ? [11:58] mvo: since when do i need to do that? [11:58] asac: its done automatically by apt if you install the package [11:58] asac: but if you just do local testing, then its needed [11:58] mvo: i just raun --reinstall firefox-3.0 [11:58] asac: it does this time [11:58] asac: hm, that should work, give me a sec to check [11:59] mvo: touched both a few times ... nothing changes. [11:59] james_w: so maybe you didnt see that when it happened? [12:00] asac: what happened was that I installed today's upgrades, and firefox stopped working properly in the middle as usual. After a while I noticed the update-notifier dialog, closed that, went to firefox, and there was no banner. So I just hit the X in the top right and then started firefox again. [12:00] james_w: anyway. there are still bugs with upgrading even with this in-firefox notification ... so with some bad luck you might loose tabs on upgrade - unfortunately [12:00] asac: hm, seems to work for me, could you please run "update-notifier --debug-hooks" ? it will spit out quite a bit of output [12:00] omg [12:00] lol [12:00] mvo: update-notifier --debug-hooks [12:00] The program 'update-notifier' can be found in the following packages: * update-notifier [12:01] glatzor: if that is not used for other stuff, I'm fine with changing that timeout. but I wonder why the other fix does not help, it should have the same effect [12:01] asac: ;) [12:02] seb128: could it be that you have pending security updates? [12:02] mvo: how do I check that? [12:03] seb128: u-m should display those on top of the updates list [12:03] mvo: no I don't then [12:04] oh goodness. thats really bad (popping up the window :)) [12:04] pitti: sorry if that is a stupid question, but if I sru compiz-fusion-plugins-unsupported to jaunty-proposed, will it be poket copied or something like this? [12:04] asac: talk to mpt but I think some people complained already ;-) [12:04] asac: ... [12:04] asac: you are just not the target user [12:04] maybe that was the reason i didnt have update-notifier installed anymore ;)? [12:05] damn [12:05] there is a gconf key to get the previous behavior back [12:05] well. we have a notification in firefox if you have ubufox [12:05] so that shouldnt be displayed at all on default installs [12:05] guess i have to make the DisplayIf: smarter [12:06] mvo: how is the kapturl going? i still cannot require kubuntu to install ubufox due to that dependency ;) [12:06] seb128: hm, hm. what is the value of /apps/update-manager/launch-time for you (in gconf)? [12:06] asac: I don't know :) hacking a bit qt would be fun I guess [12:06] mvo: [12:06] $ LC_ALL=C gconftool -g /apps/update-manager/launch-time [12:07] No value set for `/apps/update-manager/launch-time' [12:07] asac: the code is nicely seperated now [12:07] launch_time (sorry) [12:07] mvo: the idea would be to not use synaptic [12:07] mvo: launch_time = 1241003015 [12:07] if that's what you meant [12:07] mvo: could apturl just not use synaptic? [12:07] asac: it does, but it still needs a little bit of frontend cod [12:07] e [12:08] mvo: well. if thats just gtk it would be ok i guess [12:08] firefox requires gtk anyway [12:09] gnome-app-install, [12:09] gnome-icon-theme [12:09] why does apturl depend on that icon theme? [12:09] synaptic [12:11] seb128: hm, that time looks very valid [12:12] ** (update-notifier:4981): DEBUG: /usr/lib/update-notifier/apt-check returned 116 (security: 2) [12:12] (update-notifier:4981): update-DEBUG: is_package_system_locked: 0 [12:12] (update-notifier:4981): update-DEBUG: update_apt_is_running: 0 [12:12] (update-notifier:4981): inotify-DEBUG: apt_get_running=TRUE [12:12] (update-notifier:4981): inotify-DEBUG: apt_get_running=TRUE [12:12] (update-notifier:4981): inotify-DEBUG: dpkg_was_run=TRUE [12:12] (update-notifier:4981): inotify-DEBUG: dpkg_was_run=TRUE [12:12]