[00:02] doko: While you're uploading FTBFS compilers, you've noticed that gcc-4.8 can't migrate because you dropped a library that all the olders ones depend on, right? [00:03] infinity, I know, I should have gone to bed [00:03] doko: Yeah, my late night uploads usually aren't much better. :) [00:05] infinity, feel free to merge the older ones. I wanted to delay that until alioth is up again [00:06] doko: Oh, if you already have the older ones fixed in Debian or a VCS, that's cool. [00:07] infinity, feel free to fix 4.4 [00:07] doko: I'm in no huge rush to see it all fixed migrate, just wanted to make sure it was happening some day. :) [00:07] doko: I can replicate your 4.6/4.7 fix to 4.4 if you haven't, sure. [00:07] doko: (After I fly across an ocean and such, so... Later) [00:08] do you work somtimes too? ;-P [00:08] doko: Every second Thursday. [00:08] (Hey, I worked all day while I was doing laundry!... And most of the long weekend I just had) [00:08] I suck at long weekends. [00:10] slangasek: I'm not sure we are collecting everything we need === _salem is now known as salem_ === salem_ is now known as _salem === freeflying is now known as freeflying_away [04:19] stgraber: 1211514> as the changelog says, version 4 fixes half of the problem, but I just figured out the other half last night (way after uploading the SRU) [04:20] stgraber: but that bug is much less critical than the suspend failure, so I wanted to get this out ASAP [04:20] stgraber: that bug is indeed not yet fixed in trusty [04:20] Good morning === freeflying_away is now known as freeflying === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [06:40] @pilot in === udevbot changed the topic of #ubuntu-devel to: Ubuntu 13.10 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: pitti [06:55] good morning [06:56] hey dholbach [06:56] hey pitti [07:30] Hello guys, I didn't get any feedbacks from the glibc maintainers, I was wanting to add a new language suppport(language package) having iso code ="the" ; please helpme !!! === iahmad_ is now known as iahmad|afk [08:16] dholbach: happier with the sponsoring queue now? :-) [08:16] pitti, a bit, yes ;-) [08:16] * dholbach hugs pitti [08:18] * pitti hugs dholback [08:33] Hello guys, I didn't get any feedbacks from the glibc maintainers, I was wanting to add a new language suppport(language package) having iso code ="the" ; please helpme !!! [08:42] seb128, didrocks: salut mes amis! comment ça va? could you add something to https://wiki.ubuntu.com/TimoJyrinki/DeveloperApplication-PPU when you have time? :) === iahmad|afk is now known as iahmad [08:43] Hello guys, I didn't get any feedbacks from the glibc maintainers, I was wanting to add a new language suppport(language package) having iso code ="the" ; please helpme !!! [08:45] arun_, maybe you bring it up on the mailing list instead? [08:45] ubuntu-devel-discuss@lists.u.c [08:45] dholbach: oh, with great pleasure! [08:45] dholbach, salut, c'était bien l'Inde ? sure, can do, adding to my list for today (in fact it was already in my tomboy todo note) [08:45] arun_, instead of posting this every couple of hour/half hour [08:46] didrocks, seb128: très bien, merci beaucoup [08:46] Mirv: you didn't add qtcore itself and all qt plugins? [08:46] dholbach, nice to have you back ;-) [08:46] seb128, c'était fantastique - j'au aucun idée pourquoi je suis retourné :) [08:46] Mirv: I think you can add what we are upstream for (what's in cu2d) [08:46] dholbach, don't forget to hug Laney for doing sponsoring reminder [08:46] * dholbach hugs Laney [08:47] that's right! :) [08:49] Hello, anyone knows how the package‘s "Task" tag comes, if i want to set a package's "Task" tag, what should i do? [08:52] didrocks: can you be more specific? by qtcore do you mean qtcreator? it rarely needs updating other than new upstream version since now our stuff is separated from there. the qtcreator-plugin-ubuntu includes both plugins we have. [08:53] Mirv: Source: qtbase-opensource-src [08:53] Mirv: I don't see it in the first sentence :) [08:54] (also, we do have way more Qt components than what is listed) [08:55] didrocks: which sentence, and which list. since this is a different channel too, I don't have the context :) the upstream Qt modules are not suitable for daily release as is. [08:55] didrocks: the PPU page! [08:55] didrocks: right, now I understand what on earth you're talking about :) [08:56] didrocks: so... I thought I'd start with those special modules and QtC. I'm part of the pkg-kde team in Debian, so the official Qt modules can be easily added afterwards, while I'd certainly want to go through them with someone else for the next big 5.2 upload still. [08:56] Mirv: that was just 10 lines before I pinged you ;) [08:57] didrocks: yeah, there just wasn't highlight above that and I thought this was some sort of continuation from CI channel :) [08:57] Mirv: I think you are suited to have all Qt modules at least (I would add daily packages, but if you want to do that later on, I'm fine) [08:57] didrocks: ok [08:57] Mirv: you did all the packaging and we just sponsor you, so it's a strong suggestion :) [08:58] Mirv: I trust you to ask us if you have any question anyway [08:58] (which are what the upload rights are really about) [09:09] jodh: is https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/force-reload-configuration-for-broken-inotify/+merge/180690 still relevant? (I'd upload it to trusty instead) [09:17] * Mirv added the rest of the Qt modules and most of cu2d packages that provide Qt modules [09:20] Mirv: great! === pbn_ is now known as pbn [09:28] pitti: yes, it very much is. I believe slangasek is going to merge it when he gets a chance. [09:28] jodh: it looks fine to me, so if you want I can merge it now [09:29] pitti: oh - sorry, wrong branch. one sec... [09:29] jodh: (being patch pilot today) [09:29] penghuan: tasks come from seeds in ubuntu, see http://pad.lv/p/ubuntu-seeds https://wiki.ubuntu.com/SeedManagement . So it's done post-upload, on the archive side. [09:36] pitti: I've commented on the MP. Essentially, it's fine, but we might want to call on system actually using overlayfs. [09:43] dholbach: George Merkel on ubuntu-motu list being a bit non-CoC? [09:43] Riddell, I just replied to the mail [09:44] I wonder what's going on in his head [09:44] (but everybody else could have reminded him of the fact too :)) [09:44] no idea - I assume somebody who signed up for the list at some stage, forgot about it and is now surprised about the traffic happening today === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [10:02] Hello guys, excuse me !!!! I had some questions about the adding of new language having ISO Code = "the" , please help me anyone there !!! [10:09] jodh: is that for the live session? I. e. could we just guard that with 'grep -q '^/cow / overlayfs' /proc/mounts ? [10:10] jodh: (asked the same on the MP) [10:11] pitti: live session, persistent usb, cloud-images with overlayfs. Or any other file system that happens to not support inotify, or have non-notifying inotify support as the case is with overlayfs. [10:11] xnox: right, but that sounds like a rather similar check (just perhaps not with /cow) [10:12] but we shouldn't make it too complicated; if it takes lots of grepping, stat'ing, and guessing, we might just as well do the reload :) [10:13] pitti: similarly session-init is also affected, thus we maybe also should make all session init's reload configs, and that's a few paths /etc/xdg/, /etc/ubuntu-xdg/, /usr/share/upstart/session === Sweetsha1k is now known as Sweetshark [10:21] jodh, xnox: proposed a more generic solution on the MP [10:22] I tested this on a live CD (says "overlayfs") and on my desktop (says "ext4") [10:25] pitti: there is no inotify over NFS, when in root over NFS configuration - is /etc mounted local, or is that remote as well? [10:26] xnox: as I said, I'm not trying to deal with each and every broken configuration, just with overlayfs :) [10:26] i'm guessing in fully disk-less configurations it's remote. [10:26] but then / would be remote, too [10:27] so it could be extended to check for overlayfs or nfs [10:28] xnox: re session init, maybe we should consider adding a ConfigurationReloaded signal that they can all react to. Depends how quickly the kernel team fix the overlayfs issue though :) [10:30] pitti: in a way I agree with you. Polluting each invoke-rc.d call with reload-configuration is expensive and needless. And the actual usability bug in question is "i've installed $daemon package, it didn't start" and most commonly that's on overlayfs (live desktop iso / cloud image). [10:31] @pilot out === udevbot changed the topic of #ubuntu-devel to: Ubuntu 13.10 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: [10:44] cyphermox: i still roam to a 40/70 AP while there is a 61/70 AP available (on trusty) [10:45] cyphermox: you said that NM is the one deciding on such "policy"? [10:49] hallyn_: you've added 2 changes on package syslog-ng (https://launchpad.net/ubuntu/+source/syslog-ng/3.3.1.dfsg-1ubuntu1) but there is no explanation what do these changes. are they still needed? are they Debian-related, as well? === _salem is now known as salem_ [10:59] cyphermox: checking a bit on code there seem to be bgscan_simple and learn ... i only found that NM tweaks the simple parameters for the wpa_eap case, do you know where the "real" defaults used for wpa_psk are? [11:05] Riddell, he apologised in private and I took him off the list [11:05] diwic: I read through bug 1197395 and the corresponding Fedora bug (I linked that now); I'd rather fix this in libpam-systemd, so that we don't have to apply the workaround in ubuntu's pulse, if that's ok with you? [11:05] bug 1197395 in systemd (Ubuntu) "/run/user/$ID/pulse owned by root and not by the user" [High,Triaged] https://launchpad.net/bugs/1197395 [11:05] diwic: it might still make sense to apply it upstream of course, if the pam fix gets rejected upstream [11:06] pitti, sure, go ahead and fix in systemd, I too think that's better [11:06] diwic: we'd otherwise need the same fix in dconf, dbus, and whatnot [11:06] upstart, gvfs too [11:06] dholbach: win :) [11:09] pitti, I was hoping that my "blame systemd developers" patch would persuade Lennart to fix the bug upstream, but so far no response. Only been one day though. [11:36] ev, hey, there is something weird with e.u.c === dholbach_ is now known as dholbach [11:36] infinity: I was looking on the package source-highlight. (http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/source-highlight/trusty/revision/21) debian has adopted similiar patch like yours. however, sequence in debian/rules is reversed. (http://paste.ubuntu.com/6410267/) anyhow package from Debian builds fine (tested only i386). is it OK and can be synced? [11:37] ev, https://errors.ubuntu.com/problem/eac5049914041dcb1e77bd2c6437da8fa9eca096 has a total of 116 reports in that page, but it has more reports than that on the index (e.g https://errors.ubuntu.com/?release=Ubuntu%2013.10) [11:39] didrocks: could you push a button to rebuild qtcreator-plugin-ubuntu 2.8.1-0ubuntu1 on armhf? its build dep was an arch-independent package that depended on arch specific package which hadn't yet built at the time of the first try. [11:40] ev, e.g "https://errors.ubuntu.com/?release=Ubuntu%2013.10&from=2013-11-10&to=2013-11-13" has that report with a count=303 which is > 116 total for the detail view [11:40] Mirv: done [11:42] thanks [11:46] cjwatson: libwebp has moved to main (MIR approved), is ok to upload imagemagick with webp enabled? [11:48] xnox: Any chance of getting Debian to enable it first? It's not something we currently disable in an Ubuntu delta, as far as I can see. [11:48] cjwatson: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1117481/comments/3 [11:48] Ubuntu bug 1117481 in imagemagick (Ubuntu) "Imagemagick lacks support for webp" [Undecided,Opinion] [11:49] xnox: Right - I'd be more comfortable if it had reached the point where Debian was prepared to support it [11:50] xnox: I'm absolutely not going to overrule an "OMG this is a security nightmare" from the Debian maintainer who knows imagemagick much better than I do - persuade *them* :-0 [11:50] :-) [11:51] Hello excuse me guys , please help me add a new language [11:52] cjwatson: not sure where "5" is taken from, given that public CVEs turned up only 3 in 2012 (as part of MIR). Unless it's part of imagemagick's CVEs of which there are more..... [11:52] right, will talk with debain maintainer [11:55] Cimi: ping [11:59] knocte, pong [11:59] Cimi: hey, can you have a look at https://code.launchpad.net/~knocte/ubuntu-themes/fix-Radiance-CSS-precedence-of-state-pseudoclasses/+merge/194678 when you have time? === MacSlow is now known as MacSlow|lunch [12:00] I approved, looks the same [12:01] Cimi: cool thanks! [12:03] knocte: omg! i wonder if that's the root cause behind "continue button is insensitive" if any class is applied to GtkEventBox by the application. [12:03] (thus preventing the user to finish the installation) [12:04] xnox: we're talking about CSS here, it shouldn't change behaviour in any way [12:05] CSS==appearance [12:05] knocte: hm. the button did go from (default, sensitive, active) -> (insensitive). Sure but GTK does hook in functionality to css classes. The button was loosing sensitive css class, and ability to be clickable as well upon CSS change. [12:06] (all of us were mind boggled by it) [12:06] a CSS change cannot cause an element lose its classs, if anything, it can change some atributes that are applied to that class in a rule [12:06] i think ubuntu-themes are missing a few other bug-fixes that were applied in Adwaita (ordering, properties, etc) [12:07] right, styling for some of the new widgets also [12:07] e.g the nautilus cog menu [12:07] probably, I already applied one of the fixes that gtk3 upstream is including [12:08] diwic: http://paste.ubuntu.com/6410377/ does the trick for me [12:09] seb128: knocte: so the GtkEventBox.fancy style and "style.add_class('fancy') had to be reverted in http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6033 because otherwise it was causing https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1240532 [12:09] Ubuntu bug 1240532 in ubiquity (Ubuntu) "side by side install mode had disable back and install buttons" [Critical,Fix released] [12:09] is there anything wrong that you can see with fancy class? [12:10] diwic: doing final build/test now, and then I'll send that to the RH bug [12:10] (it's done in application, so it would be after the theme is loaded) === freeflying is now known as freeflying_away [12:10] pitti, thanks. Feel free to add a pointer to my patch as well if you like (I don't think I have an account on fedora's bug tracker) [12:10] ScottK, i just saw your comment about qreal/double on the blueprint, that seems to have been decided upstream already (there is a discussion on the debian-arm ML about this http://lists.debian.org/debian-arm/2013/11/msg00015.html) [12:10] diwic: already done in my reply from an hour ago [12:10] xnox: does this involve any pseudo-class (states)? [12:11] diwic: https://bugzilla.redhat.com/show_bug.cgi?id=753882#c57 [12:11] bugzilla.redhat.com bug 753882 in systemd "pam_systemd should not use loginuid (at least not when used by su)" [Medium,Assigned] [12:11] we should probably fix bugs like https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1186633 for the LTS [12:11] Ubuntu bug 1186633 in ubuntu-themes (Ubuntu) "gedit find box background should turn red when text is not found" [Undecided,New] [12:11] (if somebody feels like doing some theme hacking/refresh) [12:12] seb128: oh, that reminds me.. [12:13] seb128: we got gnome-icon-theme-symbolic 3.10 autosynced into proposed, but we still have gnome-icon-theme 3.8 in trusty [12:13] seb128: this causes both packages to be uninstallable and e. g. breaks the deja-dup test [12:13] seb128: do we want to merge g-i-t 3.10 as well, or stay at 3.8 and remove the 3.10 -symbolic sync? [12:14] pitti, I've not looked at what change in g-i-t, updating to 3.10 seems fine in principle ... let me have a look [12:14] xnox: by looking at it I don't think it's related, take in account that the Ambiance fix ( http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-themes/trunk/revision/311 ) is only changing affecting elements that have insensitive, selected, focused or backdrop state [12:14] seb128: AFAIR we wanted to by and large stay at 3.8 for trusty, didn't we? [12:15] xnox: but the best way to know is if you test without that change [12:15] pitti, yes, but icons should be on the safe side... [12:15] seb128: certainly safe, yes; and we have our ubuntu icon themes anyway, so probably mostly relevant for ubuntu gnome [12:15] and they certainly want 3.10 [12:16] pitti, 3.8 -> 3.10 is 4 commits [12:17] 2 being a commit and revert [12:17] hah [12:17] pitti, there is actually 1 commit between those [12:17] c'est facile [12:17] oui [12:17] pitti, do you want to do the update? [12:18] knocte: right, so we did button.set_sensitive(false) -> add_class(fancy) to gtk_eventbox elsewhere on the gtkwindow -> button.set_sensitive(true) no longer worked, well it no longer made button sensitive nor made it accept any click / actions / signals [12:18] knocte: with knowledge of subclasses and unbroken glade, let me experiment =) [12:19] seb128: can't do right now (only shoestring/yoghurt can internet in the train), but later [12:19] pitti, ok, thanks [12:27] pitti, i just heard you have a blueprint planned about TRIM support, will you include MMC TRIM too (for arm) ? [12:28] (got an url for me to subscribe ?) [12:28] ogra_: is that any different than just calling fstrim on their mounts? [12:28] ogra_: https://blueprints.launchpad.net/ubuntu/+spec/core-1311-ssd-trimming [12:28] pitti, well, you want the discard option in fstab [12:28] ogra_: if it's any different, can you please make a note in the whiteboard? [12:28] (does fstrim set that) [12:28] ogra_: I don't think we actually want that by default [12:29] ogra_: I personally lean towards calling fstrim from cron instead of adding synchronous delays [12:29] but deciding between discard and cron'ed fstrim is the main meat of that discussion [12:29] well, if it adds the same IO speedup as the fstab option i dont mind [12:30] ogra_: but it sounds like you actually talk about the exact same thing; so yes, it'll be fixed one way or the other [12:30] good [12:30] yeah, there shouldnt be much difference in functionality, but the device naming will be mmc specific [12:30] (/dev/mmcblkXpY and such) [12:31] ogra_: it doesn't care about device name; you run fstrim on mount points [12:31] pitti: i'm also for cron option. Or anacron. [12:31] ogra_: device names come into play if we want to set the discard option by default, though (but then we shouldn't look at device names but their properties, like "SSD?"/"can trim"? [12:32] xnox: I just stuffed into cron.weekly; that should be anacron [12:32] pitti, xnox ... well, the question is, do we want to run cron by default on phones (and preiodically wake them up) [12:33] ogra_: well, one less often deletes many files on the phone [12:33] so perhaps we want discard on phone and cron on desktop/server [12:33] right, i added a topic to the whiteboard [12:33] (and subscribed) [12:34] ogra_: heh, "performance boost" is a nice understatement [12:34] at least on an SSD, not doing any trimming is outright broken [12:35] after a few months my SSD went from 250 to 5 (!) MB/s write speed [12:35] MMCs usually work fine without but get a lot faster if the MMC supports it and you turn it on [12:36] ogra_: do you have such a device at hand by chance? [12:36] ogra_: can you confirm that "sudo hdparm -I /dev/mmcWHATEVER |grep -i trim" gives you something? [12:36] the ac100 has such MMCs [12:36] * ogra_ hasnt booted any ac100 in a year or two though ... [12:37] i'll make sure i have one working for next week [12:37] ogra_: ah, so it's not for Panda/mako/maguro/etc? [12:37] pitti, i havent checked on the phones yet [12:37] ogra_: ok, thanks [12:38] and panda uses SD cards ... that would have to be checked individually for each SD [12:38] my cron job just calls fstrim /mount/point, that'll just fail on devices which don't support it [12:38] well, we should only enable it on devices where we know it works [12:38] calling lots of hdparm/sysfs poking isn't any faster really [12:38] to not waste cycles [12:39] but we need these checks if we want to set the discard option on devices [12:39] (on the phne thats easy to know in advance and just flick a switch) [12:39] (based on the device) [12:39] sure [12:45] knocte, I noticed that we're missing menu separators, when this started happening? [12:46] Cimi: in what theme? [12:46] ambiance [12:46] I don't have them [12:46] I have them, and I have my patch applied, so I don't think my patches are related [12:47] knocte, I have trusty though [12:48] ok, my only change that could have affected Ambiance in trusty is the removal of empty rules, which I consider very unlikely to be the culprit [12:49] ogra_: on a phone, how about doing stuff when (say) the phone is charging and hits 100%? Then there shouldn't be a power issue. I imagine there's other maintenance stuff that might be useful here, too. So no cron, then, but you do get reasonably regular maintenance [12:49] Cimi: I have only requested "safe" patches for now, I was going to start with the risky ones now but I guess I'll wait a bit :) [12:50] I'm sure I read somewhere that dealing with trim works out better if you do it periodically from userspace rather than with discard [12:51] http://opensuse.14.x6.nabble.com/SSD-detection-when-creating-first-time-fstab-td3313048.html and http://en.opensuse.org/SDB:SSD_discard_%28trim%29_support may be useful to read. [12:52] ogra_: Upstream has a view, but we have an option about whether or not to follow the switch or how to do it. I'm aware of the Debian discussion. They are interested in what Ubuntu decides to do. [12:53] rbasak, well, lets discuss it at the vUDS session i'd say ;) [12:53] rbasak, but indeed triggering something on 100% battery would be possible [12:54] ogra_: just a suggestion and fuel for discussion. It's not my area. === pitti is now known as sabdfl === sabdfl is now known as pitti === freeflying_away is now known as freeflying === MacSlow|lunch is now known as MacSlow [13:20] this is the broken commit http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-themes/trunk/revision/315 [13:22] xnox: that is you? ^ [13:26] Cimi: knocte: yeap, also regression spotted on the bug report https://bugs.launchpad.net/ubuntu-themes/+bug/1181661 [13:26] Ubuntu bug 1181661 in ubuntu-themes (Ubuntu) "Ugly separator in toolbar and Nautilus - Ambiance - 13.04" [Medium,Fix released] [13:26] comment 7-8 [13:26] rbasak: "discard" will always keep your drive fast/clean, but it slows down file deletion quite a bit [13:26] xnox, there's also another bug [13:27] xnox, it removes separators [13:27] from the menu [13:28] right, the bogus *v* got later reverted. [13:28] Cimi: horizontal separators that is? [13:29] what's wrong with horizontal menu separators? [13:29] (I have them in saucy/trusty) [13:29] xnox, yes [13:29] pitti, ambiance [13:30] oh, that's the wrong^Wdark theme, right? [13:30] yes [13:30] if it's possible, I'd like to be asked to review all branches we get === d1b_ is now known as d1b [13:30] I know it's my fault I let this one, and many others, pass... [13:31] I worked on unity8 and thought nothing was touched on light-themes [13:31] Cimi: right, so stuff from #1181661 should be reverted as it "blackens" _all_ menuitem separators, not just the vertical ones in inline toolbars. [13:31] pitti: ambiance is the default theme [13:31] Cimi: i'll make a merge proposal and ask you to review. [13:31] xnox, thanks [13:32] xnox, the bug should be fixed differently [13:32] xnox, adding a css rule for menuitems in toolbars [13:32] Cimi: light-themes still have bugs and still need maintenance though to matches changes in gtk+ et.al. =/ e.g. [13:32] xnox, which is bad [13:32] Cimi: yeap, i'm got that now. [13:32] xnox, because gtk should not break [13:33] but apparently gtk doesn't care of that [13:33] Cimi: gtk is also "fixing bugs" =/ [13:33] i know. that's why i can't wait to ditch gtk =) [13:33] every new gtk release something related to theming changes [13:33] it's ridiculous [13:34] also https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1053986 has been "fixed" by patching Adwaita to generate buttons the right way around. And i don't think i've managed to distill those Adwaita patches back for lighting-themes. [13:34] Ubuntu bug 1053986 in ubuntu-themes (Ubuntu) "GtkMenuToolButton looks odd with inline toolbar style" [High,Triaged] [13:34] speaking of annoying bug [13:35] https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1018718 [13:35] Ubuntu bug 1018718 in ubuntu-themes (Ubuntu) "columns width redrawn by multiple events" [Low,Triaged] [13:35] Cimi, ^ could you look at that one, one of the recent comment explain the issue [13:35] with our theme the columns change size on focus in/out [13:36] easy to reproduce, go to e.g /etc with nautilus in list view mode [13:36] and focus/unfocus nautilus [13:36] the name column jump around while doing that [13:37] pitti: right, and AIUI if you do it less often, there shouldn't be any perf degradation unless you actually run out of free blocks, which is unlikely in a week of churn on a normal system. [13:37] rbasak: exactly [13:38] rbasak: and then it's running async in the bg instead of blocking your UI [13:38] rbasak: so we mainly need to define sensible conditions when to run it [13:39] pitti: going from the SuSE pages, I'd go with 1) when power conditions are good (eg. 100% battery and on charge) and 2) if it hasn't been run in a week [13:41] rbasak: mind to add that to the whiteboard of https://blueprints.launchpad.net/ubuntu/+spec/core-1311-ssd-trimming ? [13:41] it's good to collect this kind of links and experiences [13:48] pitti: done [13:59] rbasak: cheers [14:25] arti-tczew is gone, but in case he checks the online logs, the changes are still needed in precise since the libsystemd-daemon-dev pkg does not exist there. [14:25] oh, hm [14:25] i mis-spelled :) [14:26] ari-tczew: syslog-ng change is needed in precise and quantal. in raring, libsystemd-daemon-dev is present so the changes can be undone. === greyback is now known as greyback|away [14:55] hallyn_: ok, so I'm going to sync it in trusty. thank you very much for help! [14:56] ari-tczew: awesome, thanks === corvolino is now known as corvolino[AFK] [15:11] hi there, can I get this meeting scheduled? http://summit.ubuntu.com/uds-1311/meeting/22016/limiting-surveillance/ [15:14] cjwatson, xnox: thanks a bunch! === greyback|away is now known as greyback [16:44] seb128: sometimes the counters over/under count for the front page. The canonical count should be the number of reports you see on the problem page itself. [16:44] guys, is the glibc responsible for the language option ?? [16:45] (counters in Cassandra are not idempotent) [16:45] ev, what does it mean if the report is way off the frontpage index? [16:45] Moving to Acunu Analytics for the front page counts will fix this [16:45] ev, does it mean we can't trust the bucket/trend since it's loosing/not collecting most of the issues? [16:45] this happens rarely, I don't think it means we cannot trust the data [16:45] it's also something we can repair [16:46] well, it makes difficult to trust the datas [16:46] since we just need to count the number of columns in the Bucket Column Family (each column is an instance of the problem) [16:46] since I don't know if we drop is because we fixed the bug [16:46] or because we are failing to collect the reports under the bucket [16:47] seb128: the bucket page itself should give you the confidence that you fixed the bug [16:47] well, the number goes down there [16:47] because it's not appearing in high numbers on the newly released version [16:47] but the summary page disagrees with that [16:47] so what is creating the delta? [16:47] ^ bdmurray would you mind looking into this on your next Errors day? [16:48] ev, bdmurray: thanks [16:49] ev: looking into the bucket count being different on the index page compared to the bucket page? [16:52] bdmurray: yeah, ensuring that seb128 has something he can look at as the canonical source for knowing whether a problem still exists in new versions [16:53] and then why we're seeing discrepancies in the counters in the example he raises - though this one might be best fixed by bringing up Acunu Analytics if it's a problem with the counters themselves [16:53] I suspect it'll be easier now that we have the read-only access :) [16:54] you can just dig at the problemid in the database [16:54] and see what the real count should be [16:55] seb128: do you have an example? [16:57] bdmurray: there's one in the asana task I just created [17:01] brainwash: hey, how are you? would you have some time to test systemd-shim 4 in my PPA? in theory that should work better than the fixed 10 min timeout [17:02] brainwash: I'm now also able to reproduce that bug, with the instructions I put into the bug [17:02] guys, is the glibc responsible for the language option ?? [17:05] bdmurray, http://irclogs.ubuntu.com/2013/11/13/%23ubuntu-devel.html#t11:36 [17:12] pitti: sure, I can test the new package, but it will take some time until I'm able to report back. my system goes into sleep mode much faster at the momment, because I changed my gpu setup [17:12] brainwash: ah, "it doesn't regress" is also worthwhile; but suspend/resume is also way below 1 s for me, I can only reproduce it with the 00break pm-utils script [17:15] pitti: did you test with an artificial delay of 30 or more seconds? [17:16] brainwash: no, so far just with 15 [17:16] 30 seconds to suspend? wow, that sounds really broken [17:17] pitti: in this case the dbus connection did timeout, but the prepareforsleep flag got reset [17:18] hibernation probably [17:19] brainwash: ah, that would be a different spot in the code, though [17:19] but that would explain why some people still see this happening [17:21] pitti: I guess we need to wait for the new test results [17:22] oh wait, the latest comment does not look promising =S [17:22] brainwash: well, neither did the first one after the first version :) [17:22] so here's hope [17:23] :) [17:54] shrug [17:55] jodh, slangasek, xnox, stgraber: hey upstart friends ... "sudo restart networking" seems to take the system dbus bus down, is that a known issue? how would you go about debugging that? (as you can image it makes things really unhappy, including upstart) [17:56] jcastro, ^ (that's looking at the email you sent me) [17:56] seb128: not really a known issue, it's a known consequence [17:56] I thought "restart networking" was a "you get to keep both pieces" kind of thing [17:56] seb128: is "sudo restart networking" at all supported? [17:56] Why is anything doing that? [17:57] seb128: dbus is stop on deconfiguring-networking which is emitted by networking when going down, so that's indeed to be expected [17:57] seb128: you probably want: ifdown -a --exclude=lo && ifup -a --exclude=lo [17:58] though even that one isn't necessarily a good idea on systems that require event based network bring up (systems with complex bridges, bonds, ...) [17:58] couldnt we split networking and loopback-networking ? [17:58] in two separate jobs [17:59] ogra_: we already do. networking is a dummy job, and you have network-interface* job instance per interface. [17:59] ogra_: look at $ sudo initctl list [17:59] stgraber, xnox, cjwatson: I don't know why people to restart networking, but they do [17:59] https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1072518 [17:59] Ubuntu bug 1072518 in gnome-settings-daemon (Ubuntu) "Restarting network crashes (apparently) the desktop manager" [High,Confirmed] [17:59] jcastro, ^ do you know why user do network restart? [18:00] xnox, then dbus should probably depends on the loopback one [18:00] *depend [18:00] why do we ever need to stop dbus? [18:00] ogra_: we could but that still wouldn't solve the other half of the problem (virtual interfaces ordering), so we'd just trade one bug for another. I think the real problem here is people recommending to use restart networking at all [18:00] that should go away on shutdown with the system [18:00] seb128: at shutdown for example =) [18:00] do we need to stop it cleanly? [18:00] rather than just going down? [18:01] seb128: apparently this was made so dbus would be stopped before the loopback interface actually goes away. I'm not sure there was a reason to do that though (like dbus crashing if the loopback interface disappears under its feet) [18:02] guys, is the glibc responsible for the language option ?? [18:02] if we had such a thing as a restart statement in upstart, I think it'd be reasonable to skip emitting that signal and have ifup/ifdown run with --exclude=lo, but since we don't, I think our best option is to make sure people don't do things we don't support [18:02] stgraber, in any case it's not a g-s-d issue, where do you suggest reassigning? [18:03] seb128: to whatever documentation told the user to do that. Or mark it invalid as an unsupported user action. [18:03] stgraber, well, why do we provide a "networking restart" if that's not supported? can't we just make that display a big warning with a type "yes I'm sure"? [18:03] seb128: because it's not possible not to provide it [18:03] Right, we don't deliberately provide it, it's an emergent consequence [18:03] seb128: "restart networking" is just a standard upstart command [18:04] well, can we make the "networking" job to not do what it's asked [18:04] or ask for confirmation? [18:04] upstart jobs can't interact with the console [18:05] The only way to do that would be to break "stop networking", which would break shutdown [18:05] right [18:05] http://askubuntu.com/questions/98201/whats-the-right-way-to-restart-services-in-11-10 [18:05] can we fix the web to stop suggesting stupid commands to users? ;-) [18:05] we sure can try ;) [18:05] restart is just stop then start as far as the job is concerned [18:05] stgraber: cjwatson: well, we can do a pre-stop script, that will check upstart events. If there is none, it means user invoked it directly. And we can bail out. And we can check goal, if goal is to restart, we can again do nothing. [18:06] or indeed execute ifdown / ifup sequences. [18:06] that's true, although there's no such thing as a restart goal [18:06] the goal is set to stop and then to start [18:06] and I'd rather not break "stop networking" since it's at least used in testing (by people who know what's going to happen when they do so) [18:07] stgraber, how is that ever useful for testing? [18:08] I don't want to screw my system, but I tried a bit earlier it took dbus's system bus down [18:08] we specifically need a way to restart networking for enterprises, it's part of how to set up bonded interfaces in the server guide [18:08] which made upstart enable to work properly [18:08] it [18:08] upstart uses a private connection, surely [18:09] e.g I couldn't even use "status" [18:09] seb128: argh don't manually stop networking (i.e., what everyone else said) [18:09] seb128: it's useful when I test a new ifupdown as my test systems are simple containers that don't have anything to bring up/down when networking restarts [18:09] seb128: that lets me make sure all the network-interface instances get properly created/destroy and that all the events are emitted as expected [18:10] seb128: you should have been able to run 'status' still as root [18:10] it's currently completely broken in 12.04; there is a private escalation for it [18:10] if the server guide recommends restarting networking, then it's wrong and needs to be fixed [18:10] status> won't work as a user if dbus is stopped, but should still work as root or with --system [18:11] er, I may not mean --system [18:11] right, upstart as root always uses the private socket and doesn't depend on dbus at all [18:11]