=== thumper is now known as thumper-afk [02:06] I want to get the Unity 8/Ubuntu Desktop Next session running on an armhf device (RPi 2). Sadly, this means I can not install Unity 8 via the LXC container instructions because there is no armhf iso. If I install the "ubuntu-desktop-next" package, should I assume I might be able to use the Unity 8 session? === Bl4ckD34Th is now known as zz_Bl4ckD34Th === thumper-afk is now known as thumper [06:30] Noskcaj: yes; apt is rather resistant when it comes to uninstalling a package; there must be several new dependencies to the new one, and the new one must at least Provides: the old one, but that's not the case here [06:30] as I said, it might be that apt became more clever in the last year or so, but an upgrade needs to be tested [06:40] good morning desktopers [06:41] bonjour seb128 [06:41] hey pitti :-) [06:42] so I got up late (we had a concert last night), you got up early, almost the same time now :) [06:42] convergence! [06:46] hehe [06:48] so pitti can plug seb128 into the TV and get Ubuntu desktop then ;) [06:49] hi all, btw [07:25] good morning [07:27] hey didrocks [07:27] hey seb128 [07:58] bonjour didrocks [07:59] guten morgen pitti [07:59] hi pitti! [07:59] larsu: moin moin! === \b is now known as benonsoftware [08:24] morning [08:26] hey mlankhorst [08:29] hey [08:30] hey mlankhorst [08:59] Hey willcooke. :) [08:59] morning [09:04] yo [09:05] hey TheMuso Laney willcooke [09:05] hi all [09:06] oh, I just remembered - I'm on holiday tomorrow [09:06] and in London on Monday [09:06] larsu, cancelled our meeting tomorrow ^^^ [09:06] let me know if you need anything [09:07] willcooke: morning & thanks, will do [09:07] willcooke: and enjoy you day off ;) [09:08] \o/ looking forward to it [09:08] ooh London, glamorous [09:09] I'll send you a postcard of a telephone box Laney [09:09] tell us if Doctor Who is around :) [09:09] go check out Cereal Killer [09:11] Laney: we are all Cereal Killers otherwise they wouldn't sell it in boxes [09:42] darkxst: thx for uploading [09:43] seb128: can you check grilo-plugins in vivid new when you've got some minutes today please? [09:43] (then try totem 3.14 if you have a few more :p) [09:43] Laney, sure can [09:43] what should I try on totem exactly? [09:43] random use [10:02] desrt: thx, saw it, replied on the list [10:02] I should filter that one out of my main inbox [10:09] Laney, totem looks fine to me [10:09] cool [10:10] thanks to darkxst and Noskcaj for doing most of the work [10:12] Noskcaj, darkxst, good work! [10:12] it's a bit weird that the Videos tab is empty by default [10:13] would be nice if is was listing the content of XDG_VIDEOS_DIR [10:13] also the plugins list in preference is empty [10:13] is that normal? [10:19] has some here [10:19] is totem-plugins installed? [10:22] ups, that got uninstalled [10:22] Laney, thanks ;-) [10:22] Laney: I can't install it because it wants grilo-plugins-0.2-base, which isn't available [10:23] Laney, thanks [10:23] they're coming soon, or you can grab from https://launchpad.net/ubuntu/+source/grilo-plugins/0.2.13-3ubuntu3 [10:23] thanks [10:23] larsu, I just NEWed those binaries, should be available after the next publisher run [10:23] Laney, ^ [10:23] will need to wangle through proposed [10:23] thanks! [10:24] seb128: thanks! I'll just wait a bit then [10:24] hum [10:24] can't connect to people.canonical.com? [10:25] some kind of maintenance [10:26] yeah, saw that in the #is topic [10:26] I wanted to look at why glib didn't migrate out of proposed yet [10:27] gnome-photos failure [10:27] should indeed be retryable with this NEWing [10:28] to do with https://launchpad.net/ubuntu/+source/gnome-online-miners/3.14.0-2ubuntu1 [10:29] that doesn't seem related to glib? [10:29] why do we block on it rather than overriding? [10:30] was fixing it [10:31] k, the logic still feels weird to me, but as long as it's fixed it's all good :-) [10:32] I always prefer to fix tests if reasonably possible even if they're not directly caused by the thing they are blocking [10:32] well that's orthogonal [10:32] you can unblock and still fix the test :-) [10:51] Morning. There has been a recent release of GTK2 which fixes a nasty bug. Is this where the right channel to progress the fix in Ubuntu? [10:53] Yeah, we're going to get that soon [10:57] flexiondotorg: rly? what bug? [10:59] ochosi, https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1351890 [10:59] Launchpad bug 1351890 in ubuntu-mate "Changing external screen resolution with dual monitors" [Medium,Triaged] [10:59] ah that one, ok [10:59] ochosi, Although our motivation to prepare the patch was to fix a segfault in MATE, other GTK2 applications are affected. [10:59] ochosi, Upstream release now. [11:00] Laney, Excellent. Thanks. === MacSlow is now known as MacSlow|lunch [12:12] seb128: hi, do you have time to look at https://code.launchpad.net/~attente/unity-settings-daemon/fcitx-transition/+merge/230289 and https://code.launchpad.net/~attente/unity-control-center/fcitx-transition/+merge/249523 === alan_g is now known as alan_g|lunch [12:46] attente_, I can try to have a look today yes [12:47] seb128: thanks! [12:47] yw! [12:48] attente_, btw I did follow up that work recently, did anything change compared to previous cycle? should still be a no-op for ibus users riht? [12:49] seb128: yes, should only improve our situation with fcitx [12:56] attente_, my ibus is not working, I think it's still like the ubuntu-keyboard thing, do we have a bug open about that? [12:57] seb128: yeah, it's because of this: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1245925 [12:57] Launchpad bug 1245925 in maliit-framework (Ubuntu) "Troublesome export in /etc/profile.d/maliit-framework.sh" [Undecided,Confirmed] [12:58] the workaround for now is to comment out the export of QT_IM_MODULES, or remove maliit-framework [12:58] sorry, QT_IM_MODULE [12:59] purge [12:59] ah, right. purge, sorry :) [12:59] Laney, ? [12:59] oh [12:59] that's not a solution [12:59] he called it a workaround [12:59] yeah, I'm not interested in a workaround [13:00] I was talking about fixing that issue [13:00] in the distro [13:01] yes indeed [13:02] one thing we can do is make im-config still set GTK_IM_MODULE and XMODIFIERS, but it doesn't fix the fact that we need QT_IM_MODULES to have both maliitphablet and ibus/fcitx [13:02] can it have multiple modules? [13:02] (does stuff work right then?) [13:03] don't think so. GTK_IM_MODULES can, but even then, it's just like going through a list of fallbacks until it picks one [13:04] how does maliit get used for gtk apps? [13:05] could we kill this file and teach im-config about maliit, then get $phone_place to call it? [13:06] i guess we could probably do that without teaching im-config about maliit [13:06] * Laney doesn't know how it works [13:07] but it needs to set the environment variable across the session [13:09] ye, some upstart job [13:10] well anyway, just throwing out ideas :) [13:15] well, I'm not even sure what should happen [13:16] is there a way to know when we change from having a physical keyboard to not having one? [13:16] it feels like the osk shouldn't be by session [13:16] but by input device [13:16] like usng a touch screen should display one [13:16] can the toolkits do that? [13:16] if you connect a bt keyboard to your phone it shouldn't display the osk then [13:16] not sure [13:17] I've feeling we are not going to resolve those usecases under xorg/unity7 though [13:17] so meanwhile having a way to turn osk on or off, like we do with onboard, would be something [13:19] perhaps we just say that we don't use maliit on unity 7 or something :| [13:22] that wfm [13:22] well, until we figure how we deal better with that [13:22] I'm not even sure ubuntu-keyboard works fine on unity7 [13:23] the upstream one did at least work when I packaged it ages ago [13:26] seb128: do we do "= unity8-* || = ubuntu-touch" or "!= ubuntu"? [13:26] attente_: ^ [13:26] something is wrong in any case, because it if was taking over ibus, it should display its UI when trying to im? [13:26] if you fix it like this, it would be good to also make that file a noop if maliit isn't installed [13:27] Laney, I would say unity8 | ubuntu-touch [13:28] yeah [13:29] ok, attente_ are you happy to do that? [13:29] Laney: sure [13:29] can review after that [13:29] sweet [13:29] lemme know [13:30] attente_, can you get desrt to look again to your indicator-keyboard changes and approve it if it's fine, if he is I can do a landing [13:30] seb128: sure [13:30] thanks [13:44] * Laney pulls ze totem trigger [13:44] chuk-chuk boom [13:51] this script doesn't even seem to run when i start a unity 8 session... [13:53] likely some Xsession.d hackery [13:53] or X hacks don't apply to Mir [13:53] so how does maliit currently work on the phone? [13:55] the phone runs the profile.d scripts but the desktop doesn't? [13:56] correct [13:56] http://bazaar.launchpad.net/~phablet-team/ubuntu-touch-session/trunk/view/head:/ubuntu-touch-session [13:56] that the ubuntu-touch-session script [13:56] which is some hackery used on the device [13:57] unity8 desktop doesn't have those hacks [13:57] the script sources profile.d [13:57] maybe this is what we need to disable in u7 [13:57] that's one of those things we should deprecate by integrating what it does in the proper packages [13:57] you mean? [13:58] we are not going to install that script on unity7 if that's what you suggest :-) [13:58] it does things like forcing the qt qpa to mir [13:58] or has android bits [13:58] we should do it the other way around, move things out of this script to the proper packages instead [13:59] yeah [14:01] but the script is running on u7 right now... [14:04] no. i'm wrong, something else is running the /etc/profile.d scripts under u7 [14:05] well, profile.d scripts are run through Xsession.d [14:05] oh, ok === MacSlow|lunch is now known as MacSlow [14:06] hum, in fact I don't have that package/script [14:07] I wonder why my ibus is not working [14:10] cyphermox, hey, can you get https://code.launchpad.net/~mathieu-tl/mtp/lp1421664/+merge/249669 landed? [14:10] sure [14:10] thanks [14:10] happy new year btw ;) [14:10] cyphermox, I would try to write you that in chinese but my ibus is not working :p [14:11] ahahha [14:11] I could write it in vietnamese but for the same reasons [14:12] seb128: what does your ~/.xinputrc say [14:12] there's a bit fewer special accents to add that need ibus [14:12] attente_, I deleted that file like 10 minutes ago, but it was empty [14:12] can you try 'im-config -n ibus' and restart the session? [14:12] why is that needed? [14:12] how does it work with new users/installs? [14:13] yeah, you're right, it shouldn't be needed [14:13] let me restart session in case anyway [14:13] seb128: i really can't ACK those changes [14:13] desrt, why not? [14:14] because i don't know anything about input methods or indicators :) [14:14] are you happy with the code? [14:15] i can review that part of it again :) [14:15] thanks [14:15] I can test the IM/indicator side [14:15] i can look for another reviewer [14:16] or happyaron, do you know someone else? ^ [14:18] 你好 [14:19] :D [14:19] attente_, works after deleting that .xinput rc which had comments only [14:19] maybe that was preventing im-config to do his init or something [14:19] ah, maybe [14:23] larsu, Can you look at https://code.launchpad.net/~ted/indicator-messages/lp1385331-unescape-message-ids/+merge/250235 [14:25] Laney, seb128, can you guys test https://code.launchpad.net/~attente/maliit/1245925/+merge/250311 on the device? [14:25] to make sure osk still works [14:25] i can't test it since the behaviour is different on the desktop [14:25] attente_, I can do that [14:31] pitti: Hi Martin! Saw that https://translations.launchpad.net/ubuntu/trusty/+language-packs seems to be ready. Do you have time to get it into -proposed today? [14:33] tedg: sure, give a few mins [14:33] *me [14:37] GunnarHj: yes, it's on my list; I have to wait for the currently running vivid langpack build to finish, though [14:37] GunnarHj: I'm watching it on a foreground terminal :) [14:37] pitti: Ok, great! :) [14:46] hum [14:46] so my desktop doesn't boot anymore [14:47] stucked on the plymouth logo [14:47] it boots fine if I remove quiet splash though [14:47] didrocks, pitti, ^ know of any issue with recent systemd updates? [14:48] seb128: didn't upgdate since yesterday, can do if you want [14:48] update* [14:49] seb128: actually, I'm running latest systemd already, no issue at boot [14:49] (did reboot just after latest upgrade) [14:50] GunnarHj: I'm asking in #ubuntu-release about when to upload them; I figure having them in trusty-proposed should be fine, but I'll double-check [14:50] seb128: I'm not aware of regressions; could you boot with systemd.debug-shell, and once it's hanging switch to VT9 and check systemctl list-jobs? [14:50] pitti, k [14:50] looking to the journal those boots have different fails [14:51] pitti, http://people.canonical.com/~seb128/log [14:51] pitti: ok [14:51] fÃ©vr. 19 15:45:12 seb-e6410 systemd[1]: Starting Network Manager... [14:51] fÃ©vr. 19 15:46:02 seb-e6410 systemd[1]: Started Console System Startup Logging. [14:51] why that lag? [14:52] I guess I need debug as well [14:56] n conjugating directly for voice, English uses the past participle form of the verb plus an auxiliary verb, either be or get, to indicate passive voice. [14:56] * larsu accidentally pasted. Sorry [14:56] darn, I missed the start of the English lesson [14:56] * larsu hates middle-click paste [14:56] pitti: reading wikipedia about passive voice :) [14:57] o_O middle click paste == ♥ [14:57] +1 [14:58] pitti, no vt, including the vt9 one :/ [14:58] meh [14:59] the 45 s lag is certainly odd, but it doesn't say anything in that log at that time [14:59] fÃ©vr. 19 15:46:27 seb-e6410 dbus[774]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out [14:59] fÃ©vr. 19 15:46:27 seb-e6410 dbus[774]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out [14:59] fÃ©vr. 19 15:46:27 seb-e6410 dbus[774]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out [14:59] right, well it boots in 10s without quiet [15:00] seb128_: that's also weird -- after that it shuts down, did you request that manually, or does it happen automatically? [15:00] I try one with debug to see if it has more [15:00] I do ctrl-alt-f1 and ctrl-alt-del [15:03] ah, so manual shutdown [15:03] yes [15:04] pitti, hum [15:04] févr. 19 15:59:09 seb-e6410 systemd[1]: Starting Run Click system-level hooks... [15:04] févr. 19 15:59:59 seb-e6410 systemd[1]: Received SIGINT. [15:05] seb128: urk :) you might not want to install weird stuff [15:05] that runs on non debug runs as well and doesn't hang the boot [15:05] I'm unsure how to debug that :-/ [15:06] systemd.debug-shell doesn't give me a vt9 [15:06] seb128: so with plymouth is it just taking "long" or actually hanging forever? does it get far enough to ssh in and see what's happening? [15:06] it seems to hang forever [15:06] but I didn't wait for more than 3 minutes [15:06] attente_: this patch is pretty great [15:06] seb128: you mean VT switching doesn't work? or it doesn't even boot far enough after the initramfs? [15:06] but a boot without quiet takes 15 seconds [15:07] step 1) attente copy/pastes something from one part of the code to another part [15:07] pitti, ctrl-alt-fn display empty screens [15:07] step 2) desrt flags in review "this is not necessary" [15:07] no command line [15:07] step 3) attente fixes all of the other instances of same [15:07] it just switches away from the plymouth logo [15:07] step 4) massive net-negative diff [15:07] seb128: yeah, 90s is the standard timeout, so anything which takes longer can safely count as "forever" [15:07] desrt: sounds like step 5) hug attente ? [15:07] srsly. [15:08] Sweet5hark1, quick easy way to reset LO settings to default? Deleting something from .config perhaps? [15:08] * Sweet5hark1 is in call [15:08] nw [15:08] ./.config/libreoffice ? [15:08] willcooke: "rm -rf ~/.config/libreoffice" should reset your user profile [15:08] thanks pitti Sweet5hark1 [15:09] pitti, I could try to boot with systemd-bootchart I guess [15:09] seb128: yeah, good first step [15:09] seb128: also, do you have plymouth in the initramfs? [15:09] zcat /initrd.img | cpio -t|grep ply [15:09] pitti, how do I tell? [15:09] yes [15:10] seb128: ok, so you have cryptsetup installed probably? [15:10] yes [15:10] seb128: if you don't have encrypted internal partitions, you could try removing it, to compare [15:10] but I don't use it [15:10] k [15:10] let me try [15:10] (cryptsetup-bin is enough for encrypted USB etc.) [15:10] seb128: if you still see plymouth, that at least means that it gets far enough into the root system to at least boot [15:11] seb128: another strategy: [15:11] - enable persistant journal: sudo mkdir /var/lib/journal [15:11] reboot with plymouth, wait two mins, reboot [15:11] - reboot without plymouth, journalctl -b -1 [15:11] pitti, I do have persistant journal, that's how I got you the boot log before [15:11] ah [15:12] seb128_: ah, so you boot with bootchart by default? [15:12] pitti, ok, withoyt cryptsetup, stucked on plymouth with animated dots [15:12] seb128_: so exactly the same? [15:12] pitti, not voluntarily [15:12] yes [15:13] seb128_: voluntarily> you mean it accidentally boots with bootchart? [15:13] I'm not using bootchart that I know* [15:13] I use init=/lib/systemd [15:13] sorry /bin [15:13] fÃ©vr. 19 15:46:34 seb-e6410 umount[1458]: umount: /dev/.bootchart/proc: target is busy [15:14] ah, perhaps this is normal then, but it looks odd for sure [15:14] I've the bootchart package installed [15:14] seb128_: oh, you have an /etc/init.d/bootchart [15:14] seb128_: I don't think I ever tested that with systemd [15:14] guess so [15:14] but that could very plausibly be the cause [15:14] but that's not new [15:14] ok [15:15] pitti, after 2 minutes the plymouth logo went away [15:15] seb128_: does that actually work? (or rather, did?) [15:15] I've only an empty screen now [15:15] hm, so why no VTs and debug shell; darn [15:15] ohh [15:15] I've a vt1 [15:15] shrug [15:15] trying to log in displayed some logind not starting error [15:16] and bounced me to xfailsafe [15:16] ah [15:16] got my vt [15:16] systemctl status hangs :-/ [15:16] systemd is NOT happty [15:16] ah, bootchart depends: upstart [15:17] sounds like missing dbus [15:17] "Failed to read server status: ... timeout" [15:17] *nod* (no dbus) [15:18] * pitti installs bootchart and upstart, uninstalls systemd-sysv, and boots with init=/bin/systemd [15:18] hm, that works [15:18] I've virtualbox installed [15:19] the line before the hangs on that box is virtualbox-guest-utils [15:20] * pitti installs that, too [15:21] I don't understand why it would work without "quiet" though :/ [15:21] yeah [15:22] seb128_: the main plymouth related change in 219 was the addition of didrocks's fsckd which tries to connect to plymouth [15:22] bleh, my system just hard locked [15:23] Laney, one of those days!! [15:23] seb128_: for experimentation, could you try sudo systemctl mask systemd-fsckd ? [15:23] can be the plymouth spam? [15:23] "spam"? [15:23] seb128_: if plymouth goes down, it tried to reconnect [15:23] pitti, I purge virtualbox-utils, was not it [15:23] tries* [15:24] but yeah, masking systemd-fsckd can help as pitti told [15:24] back on plymouth stucked animating dots [15:24] can I do that without dbus? [15:24] "rolex replica now cheap - contact your plymouth daemon !! " [15:24] or is that going to fail like systemctl status? [15:24] wait [15:24] "your plymouth won the lottery !!" [15:25] * Laney sinbins ogra_ [15:25] :) [15:25] seb128_: sudo ln -s /dev/null /etc/systemd/system/systemd-fsckd.service [15:25] you can mask the unit manually with the null symlink [15:25] yeah [15:25] seb128_: also, do you mind checking if fsck runs? [15:25] didrocks, how? I can't access to a vt [15:25] well, not before the timeout that makes plymouth go away [15:26] where did you type systemctl then? [15:26] ah ok [15:26] I doubt fsck would though run at every boot [15:26] (and so systemd-fsck should exits without contacting systemd-fsckd) [15:26] and thus plymouth [15:27] didrocks: that might be it [15:27] when plymouth timeout, going to vt7 I've [15:27] didrocks: I do have it running after a clean boot in my VM [15:28] pitti: oh? [15:28] [*** ] (3 of 4) A Start job is running for Wait for Plymouth Boot Screen to quit (2min 43s / no limit) [15:28] where the * are red [15:28] didrocks: it's still running actually [15:28] the message was there on vt1 and changing [15:28] before I tries to log in [15:28] pitti: but only first boot, right? [15:28] hum, weird [15:28] fsck did run? [15:28] didrocks: no, I rebooted like 10 times [15:28] no fsck running [15:28] * didrocks is puzzled [15:28] seb128_: systemd-fsckd was running? [15:28] (if you didn't mask) [15:29] oops, I just rebooted to systemd for the lolz [15:29] didrocks, yes, didn't try to mask yet [15:29] doing that now [15:29] Feb 19 16:27:13 pid1 systemd[1]: Listening on fsck to fsckd communication Socket. [15:29] Feb 19 16:27:13 pid1 systemd[1]: Starting fsck to fsckd communication Socket. [15:29] Feb 19 16:27:13 pid1 systemd-fsck[172]: /dev/vda1: clean, 188260/1179648 files, 1021730/4718592 blocks [15:29] lots of stuff is taking ages to start [15:30] pitti: do you still have some systemd-fsck instances running? [15:31] fscanf on the fsck pipe should return != 4 [15:31] and thus, systemd-fsck closes after the connection [15:31] $ sudo systemctl --all|grep fsck [15:31] [sudo] password for martin: [15:31] systemd-fsck-root.service loaded active exited File System Check on Root Device [15:31] and systemd-fsckd doesn't even try to connect to plymouth [15:31]