=== tmpRAOF is now known as RAOF [06:51] good morning === ara is now known as Guest58945 [07:51] hey didrocks, good morning desktopers [07:52] re seb128 [07:52] Saviq: hi! Now the unity8 indicators show up in the Ideapad s10-3t, but not much else: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436203 [07:52] Ubuntu bug 1436203 in unity8 (Ubuntu) "[Dash] unity8-dash crashed with SIGABRT in QMessageLogger::fatail()" [Undecided,New] [08:36] ahoy ship mates. [08:36] morning capitains [08:50] hey willcooke [08:50] larsu, if you want some easy review karma, https://code.launchpad.net/~seb128/unity-settings-daemon/wrap-label-mount-dialog/+merge/253988 [08:51] done [08:51] larsu, danke [09:06] Folks, do you need anything from design in the next three months? I've already made a list for them longer term, but just want to make sure I haven't missed any urgent requirements. [09:07] Actually, I'll email this round too [09:10] willcooke, would be good to have a status update on the desktop theme refresh, and maybe converging a bit the icon theme (like using the touch indicator icons on desktop) [09:11] great [09:12] FJKong, You're still at NUDT right? === dbarth_ is now known as dbarth-afk === duflu_ is now known as duflu === strycore is now known as ed8 === ed8 is now known as strycore [10:54] it's like some people in the UK wrote this article: http://www.buzzfeed.com/marietelling/42-reasons-to-never-visit-france [10:54] and btw… [10:54] 28. Lyon is like an ugly wart in the middle of France. [10:54] see, it's written "middle" [10:54] :p [10:55] lol [10:55] (funny that on this photo, you can see my engineering school) [10:58] ahah, in the comments "zlatan agrees" [11:14] larsu: most of hamburg (at least from what I see) would agree with the berlin consensus. seems like after elbphilharmonie and BER airport, its Hamburgs turn again to have an opportunity to waste tax money into corruption ... [11:15] Sweet5hark1: yay! Gotta alternate wasting money ;) [11:16] larsu: otoh its understandable: nobody knows if berlin will even have an airport finished in only 10 more years, so better not risk to have olympics there ... [11:17] clearly we won't [11:17] it's pretty hard to build an airport [11:17] not sure if _anyone_ has ever done that successfully [11:20] larsu: if PAX are getting handed parachutes on final approach, requirements on the ground are easier to fulfill, I hear. [11:20] :D [11:20] * larsu <-- lunch [11:23] "may the guys with beards, glasses and latte come to the front now please ? We start disembarquing over x-hain ..." [11:25] seb128: whats your take on doing an libreoffice upload for kde themeing? the patch seems innocent enough to me ... [11:25] Sweet5hark1, should be ok I think [11:25] but I'm going to for lunch [11:25] bbiab [11:25] seb128: k [11:30] Sweet5hark1: nudge nudge :) https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1435764 [11:30] Ubuntu bug 1435764 in libreoffice (Ubuntu) "FFe UI exception for LibreOffice Breeze Icons" [Undecided,Incomplete] [11:31] Riddell: hehe. annoying if one just joins a channel and misses a backlog, isnt it? ;) [11:32] Riddell: bug just updated: its just about that patch for vivid, right? [11:36] Sweet5hark1: there's a breeze icons tar too, commenting.. [11:42] Sweet5hark1: commented === dbarth-afk is now known as dbarth [13:09] rawr [13:09] hey desrt [13:09] morning desrt [13:09] good morning [13:10] * desrt faces his uphill battle for the day: freebsd file monitoring fixes [13:12] morning desrt [13:13] bon matin [13:14] willcooke: hey Will, I am back from NUDT this afternoon [13:20] hey FJKong - hope you had a good trip. [13:20] FJKong, My afternoon is fully loaded, can we try and catch up tomorrow? [13:20] tedg: any update on your indicator-power silo? [13:20] willcooke: no problem [13:22] mdeslaur, I realized I'm going to have to redo it because the testing changes are going to be too big for beta freeze. [13:22] Sweet5hark1, congrats on Online docs! Very exciting [13:22] tedg: ah :( [13:22] Sweet5hark1: what willcooke said [13:26] willcooke: ahh, its just yet another platform ;P [13:29] MOAR PLATFORMS [13:30] willcooke: someone needs to bring back LibreOffice on Solaris with the Sun compiler. You volunteer? [13:31] * Sweet5hark1 remembers that was so much fun back in the days ... [13:31] * didrocks would prefer irix [13:31] Sure why not. What's a compiler? [13:32] willcooke, It's a computer program that teaches you new swear words [13:32] tedg, oh! Awesome. I need one of those. [13:33] willcooke: a partner for shouting matches. Usually you throw four-letter words at it and it replies with page-long error messages -- at least for C++ ... [13:33] well, if you use it, you will then lose at cards against humanity [14:20] man. i missed the obscure-platforms mini-chat [14:20] that's like my favourite thing [14:21] did everyone know that minix is back in fashion? [14:32] cyphermox, hey there [14:33] seb128: hey! [14:33] good morning, how are you doing? [14:34] cyphermox, I'm good thanks, how are you? [14:34] cyphermox, do you know about bug #1421249 and who would be the right person to look at the issue? [14:34] bug 1421249 in urfkill (Ubuntu) "bluetooth can not be enabled sometimes (when booting with flight mode on being one case)" [Undecided,Confirmed] https://launchpad.net/bugs/1421249 [14:35] cyphermox, basically if you boot touch with flight mode on, it's impossible to enable bluetooth, even after disabling flight mode [14:37] yeah [14:37] happyaron, attente_, seb128: Should I go on with a l-s fix to handle bug #1435311? [14:37] bug 1435311 in ubuntu-meta (Ubuntu) "fcitx (the framework) should be seeded in desktop" [High,New] https://launchpad.net/bugs/1435311 [14:37] the bluetooth touch upstart jobs need some more work [14:38] cyphermox, why is that related to upstart? [14:38] the flight mode is not an init thing, is it? [14:39] seb128: one of the issues is that in some cases you absolutely need to do some bluetooth firmware changes early on boot, perhaps even before urfkill starts [14:39] seb128: but you also need to ensure bluetooth is never started when flight mode is enabled, otherwise you're technically doing something illegal [14:39] there probably is some tweaking that needs to happen to satisfy both these conditions [14:39] hum, I see [14:40] do you think that's something you could look at? ;-) [14:40] since it's also dependent on whether the firmware changes need to happen before bluez is started or not [14:40] yeah, eventually :) [14:40] GunnarHj: i don't really understand why adding the Depends isn't enough. isn't fcitx already prioritized over ibus by im-config? [14:41] I think maybe we're safe from the "needs to happen before bluez starts" now, except maybe on nexus 7 [14:41] like if the user has 'auto' in their .xinputrc, it should choose fcitx if fcitx-bin is installed, no? [14:44] attente_: The problem is the timing. 1) l-s lists what should be installed, and since fcitx(-bin) is not there, nothing fcitx-* is included in the list. 2) Then the listed packages are installed, and only now fcitx-bin is pulled due to the depend. The other fcitx-* stuff is not installed, though, since it was never in the list to begin with. [14:45] attente_: im-config only deals with already installed IM frameworks. [14:47] GunnarHj: are you talking about the "Keyboard input method system" combo? [14:47] attente_: Well, the latter is not quite true with the latest changes... But the timing of the fcitx-bin install is still a problem. [14:48] if it's the combo it seems like it should be something fixed in l-s to refresh after an install [14:48] attente_: At first hand I'm talking about which files are installed at the moment when you install a Chinese language. [14:49] ok, but a session restart is necessary to see the effects of the language change anyways, right? [14:49] what other fcitx-* stuff is needed besides fcitx-bin and fcitx-pinyin? [14:50] attente_: If the user is changing the display language, so yes. But s/he may be installing a Chinese language only to get access to the IM stuff. [14:50] and that needs a session restart to take effect too, no? [14:50] attente_: The whole approach with letting the display language determine the IM framework is rather fragile. [14:51] attente_: Well, yes, in order for u-c-c to recognize the new stuff, you need to relogin. [14:51] right [14:51] attente_: But you shouldn't need to open Language Support again. [14:52] attente_: And redo it... [14:52] you mean re-open Language Support to switch from IBus to Fcitx? [14:53] i was saying if that's the problem, the combo widget in l-s should be refreshed after an install (if it doesn't it's a bug) [14:53] attente_: To have the fcitx engines installed at first hand. [14:53] sorry if i'm misunderstanding, but i'm genuinely confused [14:54] attente_: Please reread the bug description. [14:55] GunnarHj: i did. and i'm not sure why a language-pack-zh-hans(-base) Depends on fcitx-pinyin wouldn't work in this case [14:56] attente_: Again, it is the timing. ^ [14:56] GunnarHj: are we expecting it to install all chinese fcitx im engines? [14:57] attente_: I'm assuming we want to install the Chinese IM engines which are listed in pkg_depends. And that will not happen with the language-pack-* depend you mentioned. [14:59] GunnarHj: ok, so this is some incongruity between the list that's displayed to the user and what is actually installed? [15:00] attente_: The list is not shown to the user - it's created behind the scenes. And it does not include the fcitx IM engines unless fcitx (should be changed to fcitx-bin) is installed at that spot of time. [15:02] attente_: That's why I suggest a l-s hack. [15:03] attente_: If you start gnome-language-selector from terminal, and install a language, you'll see the list, though. [15:07] attente_: I just thought of another possibility... Maybe we should simply remove the fcitx condition in the Chinese entries in pkg_depends. Then your depend idea would probably work. [15:08] attente_: OTOH I'm not sure how you edit the language-packs. I think they are created automatically via langpack-o-matic or something... [15:09] GunnarHj: ok, so it sounds like a l-s hack is probably unavoidable then... [15:10] attente_: Ok, I'll take a look. It's probably a pretty easy thing. I'll let you know if I need help. See you later (maybe tomorrow). [15:11] GunnarHj: ok, thanks [15:13] attente_: Btw, the IM combo you mentioned is a separate story. Currently ~/.xinputrc is created automatically the first time a user opens gnome-language-selector, so a later install of a Chinese language won't automatically switch the IM framework to fcitx, but the user needs to do it manually. [15:15] attente_: Personally I think we should keep it that way. It makes not sense at all to me that the IM framework is automatically changed only because the user changes display language. [15:19] GunnarHj: yeah, i'm not sure. if they never explicitly set it (i.e. auto), is it safe to assume they'd be ok with switching... [15:23] attente_: I don't think it would be safe. Let's take the simplest example: A Chinese install. The user starts using fcitix IM, and then for some reason changes the display language to English (without touching the combo). It's reasonable to assume that s/he wants to keep using fcitix for IM things even if the display language is English. [15:29] Hi guys, my Xorg server crashes like this http://pastebin.com/qXATtm4s any idea? [15:36] larsu, are you still looking at this nautilus zooming issue? I've an upload I want to do, wondering if I should wait on an eventual fix or just go with what I have and do another one later if needed [15:37] seb128: I didn't get to it yet sorry. Please go with what you have for now [15:38] larsu, k, thanks [16:13] larsu, opened https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1436428 and added to your queue, hope it's ok ;-) [16:13] Ubuntu bug 1436428 in gedit (Ubuntu) "highlight spelling mistakes not working with the default theme" [Low,New] [16:13] not sure if that's a theme issue [16:15] * larsu nods silently [16:29] seb128: hey, I'm looking into UI scaling work that was done for unity - where you could scale up/down UIs on each screen [16:30] there's a dconf setting: con.canonical.user-interface.scale-factor being used [16:30] greyback, hey [16:30] I'm trying to find the gtk code that reads and monitors that value, any idea where it is? [16:30] there is none [16:31] gtk knows only of one scale factor and it's in org.gnome.desktop.interface scaling-factor [16:31] which is read by gnome/unity-settings-daemon which set the corresponding xsettings [16:31] that's not a by monitor value though [16:32] so I've 2 monitors set up here, one with different scale to the other. gedit (mostly) rescales when I move it from one monitor to the other [16:34] it does? [16:34] yeah [16:34] what change? [16:35] if I manually edit com.canonical.user-interface.scale-factor, gedit rescales [16:35] right [16:35] but that's not by monitor [16:35] it is [16:35] it should apply the same scale factor to gtk independently of the monitor [16:35] well the key is [16:35] and unity has different scaling by monitor [16:35] which applies to decoration, launcher, etc [16:36] it also tweak the gtk scaling behind the scene [16:36] but I though that the gtk factor was not by monitor... [16:36] I might be wrong though [16:36] larsu, Trevinho^ ? [16:36] lemme test more, perhaps I'm not interpretting "scaling" correctly [16:37] ah, font sizes are being changed [16:38] it's not scaling anything [16:38] for anyone playing along at home, I have a typo above, it is: "com.ubuntu.user-interface.scale-factor" [16:40] greyback, if you want to see scaling do "gsettings set com.canonical.user-interface.scale-factor 2" [16:40] greyback, or use e.g GDK_SCALE=2 gedit [16:42] seb128: yeah I see it (for a microsecond, before something reverts it back to 1) [16:42] seb128: thanks, I see what's happening now [16:42] greyback, oh, right, unity tries to be smart, doing GDK_SCALE=... gedit [16:43] seb128: yeah that's nice [17:08] seb128: no clue, that's a Trevinho/bregma question [17:08] larsu, the question was whether the gtk scaling factor was per monitor, I though it was not [17:10] seb128: it is [17:10] at least according to the API [17:10] larsu, how does that work with the xsettings/gsettings key? [17:10] not sure if it dynamically changes it [17:10] dunno [17:11] it used to be one single value system-wide [17:11] larsu, I only know of com.canonical.user-interface.scale-factor [17:11] which is one number [17:11] int [17:11] there's also the text-scale-factor which is independent [17:11] but also one value? [17:11] there's gdk_screen_get_monitor_scale_factor() [17:12] not sure if that ever returns different values though [17:13] ya, it always returns the same value on x [17:20] larsu, thanks [17:38] attente_: see my reply at bug #1435311 [17:38] bug 1435311 in language-selector (Ubuntu) "Make sure fcitx-bin is installed when installing a Chinese language" [High,In progress] https://launchpad.net/bugs/1435311 [17:53] seb128: yeah, what you said to greyback is right [17:53] greyback: the thing is that gtk doesn't support real scaling factor values, but only integers [17:54] greyback: so... to workaround that if you set something such as 1.8, then we use the font-scaling factor + the ui scaling factor to get the proper value [17:55] and, the gtk scaling factor is actually global... I mean, although every screen can have a difrenent one, the apps doesn't update automatically afaik === alan_g is now known as alan_g|EOD [18:19] * willcooke -> EOD. g'night all [18:35] Has someone already tried Vivid on a virtual machine (Utopic as host). For me it does not work at all. It stops booting after the first update. [18:36] tkamppeter: are you by chance using ext3? [18:36] ext3 as the hosts file system? [18:36] tkamppeter: yeah [18:37] No, I am using ext4 [18:37] ahh, looks like the bug I'm thinking of can also happen if your ext4 fs doesn't use extents, https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1292234 [18:37] Ubuntu bug 1292234 in linux (Ubuntu) "qcow2 image corruption on non-extent filesystems (ext3)" [High,Fix released] [18:39] sarnold, what do I have to do to fix it? [18:39] tkamppeter: if this specific bug is the one you hit, you can either turn on extents or use saucy's qemu/kvm/etc [18:40] sarnold, and how do I turn on extents? [18:41] tkamppeter: tune2fs can do that [18:46] sarnold, I did sudo tune2fs -O extent /dev/sda1 now and after rebooting the host I can boot Vivid in the VM again. Thank you very much. extents should be made default. [19:07] Does anyone else use internet connections who catch bad hostnames, in order to redirect you to their own web servers? [19:08] (In tech jibberjabber, id est, NXDOMAIN hijacking.) [19:09] Fortunately my ISP at least allows that stupidity to be turned off [19:48] Ah well. I don't like nxdomain hijacking. I'm technical enough to fix it, but our users aren't. I just made a networkmanager/ifupdown plugin to fix it automatically. I'm hoping for feedback. [19:50] qengho: I see nxdomain hijacking all the time [19:50] qengho: nice [19:59] happyaron: dui4buqi3, install "dns-veracity" from ppa:cmiller/ppa ? This is the only file installed: http://bazaar.launchpad.net/~cmiller/+junk/dns-veracity/view/head:/etc-network-ifup-script [20:00] looks handy [21:41] qengho: if someone returns ipv6 addrs instead of ipv4 headers, this script appears to ignore them [21:45] sarnold: that's right. I only ask for A records, and I filter anything not \d and . . I could test for AAAA and : later, I guess. [21:46] qengho: probably not a huge deal today :) but perhaps some mobile operator has ipv6-only or something similar.. [21:54] sarnold: $ host -t aaaa ipv6.test-ipv6.com. #-> ipv6.test-ipv6.com has no AAAA record # any idea the problem? [21:56] -t ANY works. [21:56] qengho: do your resolvers used for the query ignore ipv6 responses? I got back an AAAA from that.. [21:57] Hrm. Could be. [21:57] qengho: I can't recall if there's a handy switch for the resolver interface to ignore AAAA responses.. I could have sworn I've seen one somewhere but I didn't spot it in the manpages I thuoght to check [23:07] sarnold: http://bazaar.launchpad.net/~cmiller/+junk/dns-veracity/view/head:/etc-network-ifup-script ??? [23:28] qengho: looks great