=== maclin1 is now known as maclin === jamesh_ is now known as jamesh [05:19] morning [05:20] cyphermox, guided [05:35] good morning! [05:40] good morning desktoppers [05:47] hey oSoMoN [05:47] how are you? [05:58] salut didrocks [05:58] I'm good [05:58] you? [05:59] I'm great! Getting bearable temperatures, finally [06:06] it's rainy here today, dropped from 32°C yesterday to a forecast of 23°C today [06:09] good morning desktopers [06:09] lut oSoMoN didrocks [06:10] salut seb128, ça va? [06:10] lut, nickel, et toi ? [06:10] ça va :) [07:51] Morning desktopers [07:52] Or should I say, morning France. [07:54] bonjour flexiondotorg! [07:54] (from Spain) [07:54] hey flexiondotorg [07:55] oSoMoN: What part of Spain? [07:55] near Barcelona [07:56] Catalonia, my favourite part of Spain. [07:57] Used to live and work in Tossa De Mar. [07:57] cool [07:58] was the company located there, or did you work remotely? [07:59] I was a chef ☺️ [07:59] My first career. [07:59] oh wow [08:00] flexiondotorg is cooking for us in NYC! [08:01] didrocks, do you happen to have nvidia hw handy? I could use some help in understanding and fixing https://forum.snapcraft.io/t/gl-applications-using-desktop-helpers-dont-work-on-nvidia/1825 [08:01] No one cooks in NYC 😉 [08:01] oSoMoN: no, only Intel here, sorry [08:01] oSoMoN: my old nvidia laptop is RIP since 2012 :p [08:01] I have nvidia. [08:02] flexiondotorg, would you have a bit of time to help me debug that issue? [08:03] I can. [08:03] iirc popey said it's not just the chromium snap, others are affected too [08:03] awesome [08:03] ahoy [08:03] I have a meeting this morning. Then I can help. [08:03] hey Laney [08:03] Morning Laney [08:04] flexiondotorg, excellent, in the meantime I’ll try to come up with ideas to give you things to try [08:04] oSoMoN: I think this issue affects other snaps so I'm keen to figure out the issue. [08:05] I wonder if it's missing pieces (stage packages) inside the snap, or if really the desktop helpers magic is to blame [08:05] hey Laney [08:05] well I guess if the former then it's also something that can be fixed by the desktop helpers [08:06] it would be interesting to compare that chromium snap to another one that is known to work with hw acceleration on nvidia [08:06] popey, do you know of any snap that works with hw acceleration on nvidia? [08:07] (preferably one that uses the desktop helpers) [08:08] oSoMoN: chromium isn't a classic snap, correct? [08:08] correct, it's strictly confined [08:08] ok, not what I thought of (missing export of LD_LIBRARY_PATH as snapcraft doesn't do it for you) === Guest90399 is now known as fredp === fredp is now known as Guest95606 [08:14] hey oSoMoN didrocks flexiondotorg [08:14] what up [08:16] didrocks, salut, how do I force a wayland session without the option in gdm? [08:18] jibel: salut ! Maybe changing the session in account-services? That's the part I'm not terribly familiar with and don't have the time to look at, that's why seb128 asked Robert to have a look at all those session selection bug (I didn't find any code in gdm for this, hence I think it's account-services) [08:19] Trevinho: apparently, the new indicator extension has some "double click" behavior (to activate some menus), can you look at disabling this or putting an option? It's not really cohesive with the rest of the Shell UI [08:19] (double-clicking on the dropbox icon to activate it) [08:19] didrocks, I changed the session in /var/lib/AccountsService/ and apparently it worked. Thanks [08:20] hmmm, and now gdm proposes a selection of sessions .... [08:20] * jibel reinstalls again [08:20] didrocks: yeah... [08:20] All in my list [08:21] jibel: there is still the question of selecting a default session [08:21] (gdm hardcodes "gnome") [08:31] and now I cannot log into X anymore, meh :( [08:33] hey Laney [08:34] jibel, didrocks, I didn't have slots to spend on that gdm/accountsservice issue, is there a bug registered? [08:34] sessions are correctly listed here [08:38] seb128, bug 1712287 and bug 1712504 [08:38] bug 1712287 in gdm (Ubuntu) "Wayland is not the default session after installation" [Undecided,New] https://launchpad.net/bugs/1712287 [08:38] bug 1712504 in gdm (Ubuntu) "No 'Ubuntu' session after an upgrade from Zesty" [High,Confirmed] https://launchpad.net/bugs/1712504 [08:38] seb128, let me do another install with today's iso [08:38] seb128, and now I've a new bug, I'm logged into wayland whichever session I select [08:39] stuck in wayland and cannot use VMs [08:39] ... [08:41] thanks [08:42] hey seb128 [08:42] seb128, I'll file another one for the default install, I cannot find it [08:47] thx [09:02] seb128, after an upgrade from Z should I expect ubuntu, ubuntu on xorg and unity? or just ubuntu and ubuntu on xorg? [09:02] in gdm that is [09:02] IIRC, I wrote that in the trello cards at the time, you should expect the 3 session, with "ubuntu" being the default [09:04] k, found your comment [09:05] didrocks, but it is not clear. THere is "maybe a wayland/Xorg choice, but that's it" [09:05] didrocks, is it still a maybe? [09:08] jibel: it's not anymore, it should be wayland by default, and xorg as optional [09:09] (basically it's "default install" + unity on upgrade) [09:09] didrocks, okay, so after an upgrade I'm expecting: "ubuntu", "ubuntu on xorg", "unity" correct? [09:10] correct [09:10] and "ubuntu" being the default which should start a wayland session [09:10] exactly [09:10] good [09:19] seb128, bug 1714203 [09:19] bug 1714203 in gnome-session (Ubuntu) "Cannot select a session after a fresh installation - No selection is available in gdm" [Undecided,New] https://launchpad.net/bugs/1714203 === Guest95606 is now known as fredp === fredp is now known as Guest13695 [09:46] jibel, thanks [09:48] O_O [09:48] I upgraded to gnome-shell from proposed and ended up in Classic [09:48] probably some session selection thing too [09:59] for the theme, I'm puzzled about the best strategy [10:00] I was first doing a lot of sed regexp, but there are a lot of special case, in context (yes, we can do this with more complex regexp expressions) [10:00] also, the issue with regexp is that if one entry becomes invalidated (because like upstream changed one source color), we won't notice it [10:00] as "not applying is ok" [10:00] hey desktopers! [10:00] the other solution would be to make a python script [10:01] but meh [10:01] chrisccoulson, hi, please see PM [10:01] another one is to make a patch [10:01] however, new version of the Shell, hard to rebase, hard to look at new entries [10:01] another idea is just to ship a copy of the theme and rely on a 3 way merge at each Shell update to look at the diff of upstream css [10:02] any thoughts? [10:11] jbicha: that concerns you as well I think ^ [10:14] didrocks: you didn't do your theme work last week with GNOME Shell 3.25.90? [10:14] jbicha: did we have GNOME Shell 3.25.90 in the archive? how could we test it? [10:15] didrocks: can't you make an ubuntu.scss which includes the gnome one and overrides the modified bits? [10:15] GNOME3 Staging PPA [10:15] jbicha: as told, if you didn't update it, we had to do with 3.24 [10:15] * Laney doesn't know much about sass / scss but that sounds more maintainable than sedding or patching (patching the output at least) [10:15] jbicha: but no, and not really the current topic (as the css diff is minimal anyway) [10:15] didrocks: I mean I could have crammed it into artful-proposed but it wasn't going to go to artful until gjs/armhf was fixed [10:15] Laney: not really possible, most of the colors are hardcoded and not in sass [10:16] where do they come from? [10:16] it just seems like you made more work for yourself… [10:16] Laney: I meant, they are not "in context", like it's not just replace all colors from X to Y [10:16] or we need to remove some stenzas as well [10:16] jbicha: rebasing again is easy [10:16] the question is: how do we make that maintainable? [10:17] (which was why I wanted to raise this here ^) [10:18] I think a separate css file is maybe the best approach first, rather than patch/sedding and doing a 3-way merge on shell update? [10:18] then, if it's not sustainable, we can revisit (I hope to make the Shell more customizable upstream in the meantime) [10:18] GNOME Classic uses a separate css file and it sounds like it's easy for us to make more changes that way [10:18] of course, we might not want *too* many changes :/ [10:19] yeah, it just asks when we do update to download the old css to compare the changes [10:19] which, I think, is fine for a first approach [10:19] jbicha: the main issue is that a lot of colors are "blue grey" and it's a mismatch [10:19] we need "orange grey" [10:19] so, same changes on multiple colors all over the place [10:21] show what you've got maybe? [10:21] you want the diff against 3.24? [10:21] http://paste.ubuntu.com/25437780/ [10:21] here you go ^ [10:23] k, and where do those values come from? [10:23] ? the hackfest ? [10:23] you made them up? [10:23] some from unity [10:23] or they are the output of some algorithm or? [10:23] some from our ubuntu keys [10:23] some, we had to made them up, in the hackfest [10:24] hi, qq... running 17.10, fully up to date, using ubuntu session, used to have 'dash to dock' extension which i've uninstalled and can't get the new ubuntu dock to show - in https://extensions.gnome.org/local/ it says "ERROR" against ubuntu dock - can anyone please point me to how/where can i find logs to find what's going on so i can submit a bug report? [10:25] roger-roger: "journactl /usr/bin/gnome-shell" should have this output [10:25] Laney: how does it impact the diff? [10:25] roger-roger: one way is to run [10:25] gsettings get org.gnome.shell enabled-extensions [10:25] then [10:25] gsettings reset org.gnome.shell enabled-extensions [10:25] and go back and enable the extensions you want after that [10:26] but please file a bug report too [10:27] ok found it - "Extension "ubuntu-dock@ubuntu.com" had error: TypeError: dockManager is undefined" [10:27] interesting [10:27] if i submit bug report, any other useful bits to include other than the gsettings get and journalctl output? [10:27] just put that in ^ [10:28] that should be enough [10:28] ok cool, thanks [10:28] didrocks: what I'm getting at is that these are generated files from upstream, and in particular the colours you're replacing are generated using functions [10:28] I think any approach that is working on the generated code is going to be difficult [10:29] Laney: indeed, but look at the diff again [10:29] Laney: it's not a one to one mapping [10:29] some values are different in context [10:29] (and that's because they actually corresponds to other pieces of UIs) [10:29] where one value in the upstream theme makes sense, less in other case [10:30] same for instance in the border removals [10:30] so the upstream in those cases could define a new variable but give it the same content [10:30] exactly [10:30] and ubuntu.scss would give it different content [10:30] and that's what we want to do for next cycle [10:30] get it better themeable [10:30] upstream [10:30] I thought that's what you were asking about now [10:31] no, right now, I'm trying to figure out what would work for you guys for this cycle [10:31] as the maintaince burden will be for everyone updating G-S (hopefully, we won't have huge css change thus) [10:31] that's why I'm about shipping a css file as they do for GNOME classic [10:32] ok then, I understood 'strategy' to mean a long term thing [10:32] and have the maintainer updating doing a 3 way merge [10:32] W 65 [10:32] oops [10:32] 65 buffers? crazy ;) [10:32] this is a low day [10:33] didrocks: for this cycle, GNOME Shell is supposed to be at UI Freeze with Hard Code Freeze on Monday… [10:33] yeah, we will supposively have the transparency change [10:33] but apart from that, I think it's safe to ship the css [10:34] just to whoever update it, remember to at least diff old gnome-shell.css to new one [10:34] I guess it's the sanest for now [10:35] right, I don't envisage big reworking for 3.26 at this point [10:35] just checking it should be ok [10:35] let's do this [10:35] need to update to g-s 3.25.9x first [10:36] but mutter doesn't want to… hum, /me looks [10:38] didrocks: oh, it's silly Debian-packaged gnome-shell extensions with a max gnome-shell version, I'll do some uploads for it [10:38] jbicha: yeah, saw that, thanks! :) [10:38] ubuntu dock bug report --> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714219 [10:38] Ubuntu bug 1714219 in gnome-shell (Ubuntu) "Extension "