[09:53] hi all :) [10:49] amigamagic: hey, this is the bug report which addresses the lightdm cursor problem -> bug 1024482 [10:49] bug 1024482 in unity-greeter (Ubuntu) "Mouse cursor theme does not change from default after login" [Undecided,Confirmed] https://launchpad.net/bugs/1024482 [10:54] <[1]amigamagic> brainwash, are you sure is that the right bug report? [10:55] yes and no === [1]amigamagic is now known as amigamagic [10:55] check the linked debian reports [10:55] maybe it's related but it's not exactly the same problem I think... [10:56] it should be the same issue just described differently [10:57] it talks about the mouse that doesn't change shape everywhere, but to me it's only the busy cursor that doesn't work [10:58] it's very likely that this is still the same issue [10:58] "When using LightDM to login to a GNOME Shell session" [10:59] lightdm (+greeter) and gdm do things differently [10:59] so there is some sort of incompatibility [10:59] I tried xdm and the busy cursor works with that [11:48] bluesabre: can we set this env var in the greeter code? https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1024482/comments/18 [11:48] Launchpad bug 1024482 in unity-greeter (Ubuntu) "Mouse cursor theme does not change from default after login" [Undecided,Confirmed] [11:50] I've tested it and apps like abiword, libreoffice, software-center,.. now trigger the busy cursor on startup [13:42] hi everyone [13:43] sry, i was busy/away travelling [13:45] thanks for doing the tests elfy [13:46] guess we can move on to the sophisticated patch then if this one works in principle [13:46] woooho [13:46] ochosi is back! [13:47] * sidi-valencia pokes brainwash, bluesabre, knome, ali1234 and Unit193 all at once. [13:47] heh [13:47] hey sidi-valencia [13:47] hi [13:48] didn't know you were hanging out in this channel too :) [13:48] im everywhere D: [13:48] does that mean you're just one step away from contributing to xubuntu again? ;) [13:48] it's funny how the place changed in 5 years though [13:48] so many more people [13:48] and some people gone, too [13:48] ochosi, yes [13:48] awesome [13:48] as soon as you guys drop the Ubuntu part I'll join again [13:48] harhar [13:49] yeah, luckily there are a few more ppl here now than there were [13:49] still not too many though [13:49] is ubuntulog_ a logging daemon? [13:49] should be, yeah [13:49] this channel is logged [15:03] Unit193: could you please add the next team meeting (Friday, May 16th at 10:00am UTC) to the google-cal? === qwebirc73586 is now known as slickymasterWork [15:45] ochosi: I hope that you'll have the mailing lists in place before the next meeting for us :) [15:46] elfy: knome was assigned to send a proposal for that to the ML [15:46] so i'll wait for that [15:47] that was actually decided at the last meeting, when i wasn't around, so it's not even my fault :) [15:47] next meeting will be Friday, May 16th at 10:00am UTC, right elfy, ochosi? [15:48] yup [15:48] thanks, ochosi [15:49] though I might make that [15:50] good [15:50] i hope many will make it [15:50] as i said, it's a bid of an experiment [15:51] depends if I'm working - I believe not [15:53] I'll make it, but probably will be fighting with my connectivity (as usual at work) :P [15:53] :) [15:54] you laugh elfy, I despair [15:54] I can usually feel you despairing from over here ;) [15:55] lol [15:57] ochosi, added it to the calendar [15:57] hi knome [15:58] hey elfy [15:59] bbiab [17:24] ochosi: 1 report that the xfpm fix doesn't work [18:20] elfy: thanks, i saw it and replied [18:20] dinner time... [18:37] heh [18:39] did anyone test with xscreensaver or other screen lockers? we surely don't want to fix one thing and break another [18:39] amigamagic: hey [18:39] hi brainwash [18:40] amigamagic: https://launchpad.net/~thad-fisch/+archive/lightdm-gtk-greeter [18:40] busy cursor with lightdm(-gtk-greeter) [18:41] the report I've linked earlier today was the correct one [18:41] it's a fix for the busy cursor problem? [18:42] more like a workaround [18:42] see https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1024482/comments/18 [18:42] Launchpad bug 1024482 in unity-greeter (Ubuntu) "Mouse cursor theme does not change from default after login" [Undecided,Confirmed] [18:43] I've only added the env var to the greeter code [18:43] and it works fine for me [18:44] the question is, what could setting this env var possibly break (in the future)? :) [18:44] I have to try that... [18:46] for that really I don't know... We should check what the GDK_CORE_DEVICE_EVENTS var does... [18:48] I wonder if we you could include this change for the next bug fix release [18:48] after a discussion ofc [18:51] I found this on a forum thread from 2012 (http://forums.gentoo.org/viewtopic-t-925138-start-0.html): "If you export GDK_CORE_DEVICE_EVENTS=1, GDK will stop using XInput and use old-school X11 events" [18:51] yes [18:52] it shouldn't break anything [18:52] anything related to xubuntu :) [18:53] I think we should try it for a while and check if we see anomalies in the behaviour of gdk applications [18:54] xfce itself I think uses gdk for some plugins [18:55] gdk is used by gtk [18:57] so we need to look out for cursor anomalies [18:57] yes [18:58] after the var change, I have to logout and login to check if it works? [19:04] ok, now the busy cursor works [19:05] the system looks all right. The mouse changes shape when you go to the corners of the windows or in an a text field, etc... [19:09] I tried some classic apps (gimp, libreoffice, firefox, chrome, etc.) and it looks all ok. I don't think this var could do troubles in the system, but let's check for a while. [19:11] you should check mainly gtk3 apps like gedit [19:12] I don't know if I have gtk3 apps [19:12] the editor I use are mousepad and geany [19:12] then just enjoy the busy cursor :) [19:13] yeah, of course! Thanks for the help! [19:14] Is there already some list with the new features for the 14.10 release? For example, there are some little improvements and bugfixes for xfdesktop and tasklist plugin that could already be included in the 14.10. [19:14] roadmap? [19:15] usually upstream fixes will land automatically in the new release (synced from debian) [19:15] or manually by someone from the team [19:15] per request [19:16] but this requires a new upstream release [19:17] like xfdesktop 4.11.7 [19:17] yes, honestly I don't think those fixes and improvements are already in the mainstream [19:18] but it's very likely that they will be before 3-4 months [19:22] these fixes could be tested via the team ppa [19:29] for example there is these: https://bugzilla.xfce.org/show_bug.cgi?id=10813 https://bugzilla.xfce.org/show_bug.cgi?id=10846 https://bugzilla.xfce.org/show_bug.cgi?id=10862 [19:29] bugzilla.xfce.org bug 10813 in General "xfdesktop doesn't save the arrangement of desktop icons after a resolution change" [Minor,Resolved: fixed] [19:29] bugzilla.xfce.org bug 10846 in Window Buttons "Grouped icons sometimes are wrongly rendered as a mini-icon" [Minor,New] [19:29] bugzilla.xfce.org bug 10862 in Window Buttons "Grouped icons are not rendered with transparent effect when their child are all minimized." [Minor,New] [19:32] they are all fixed albeit only the first has been checked and marked as fixed by an xfce developer. I think there are some developers in the XFCE team that are no more active. No one checked my last 2 fixes from 25 April and 2 May [19:33] evening all [19:33] hi elfy [19:34] hi amigamagic [19:36] hey elfy [19:38] hey brainwash :) [19:38] amigamagic: the Xfce project needs more helping hands and active developers/maintainers, especially for the near future (gtk3 + wayland + systemd) [19:40] yeah [19:41] but it's so imperative to switch to gtk3 ? (note that I don't know much of these libraries, being that I've only fixed some xfce bug here and there) [19:45] gtk2 is old, deprecated and hardly maintained anymore [19:45] gtk3 is also a requirement for wayland support [19:53] is gtk3 totally incompatible with gtk2? [19:59] I mean, if you have to rewrite all from scratch (xfdesktop, thunar, panels, plugins, etc.), I wouldn't like to be in the shoes of the developers... :D [20:00] gtk3 isn't the problem and systemd isn't the problem [20:01] porting it to those will be trivial [20:01] wayland is the problem [20:01] porting to wayland will require a from-scratch rewrite of almost every component [20:03] ouch [20:05] and the end result would be as different from xfce as gnome 3 is from gnome 2 [20:08] why that? will coders get bored of writing it from scratch and start messing around with the design? :D [20:08] no, it's basically because wayland implements only the functions needed to implement gnome shell [20:08] in xfce and in gnome panel, the panel and window manager are separate, yeah? [20:09] it's built around gnome3 =S [20:09] and you can use xfce panel with metacity, or gnome panel with xfwm? [20:09] in gnome shell, the window manager and panel are one big monolithic binary [20:09] and so in wayland, that's the only way you're allowed to make a shell [20:09] like unity [20:09] yes, exactly like unity [20:09] unity8 + mir won't be different [20:10] mir is almost exactly the same as wayland in every way [20:10] hooray [20:10] I hate gnome 3 (the UI, I mean) [20:10] there is really no reason for both of them to exist [20:10] except the gnome and wayland are red hat, and unity and mir are canonical [20:10] they're really both equally bad in exactly the same ways [20:11] and the constant fighting between them is kind of annoying, since they both all do the same things they accuse the other of doing [20:11] it's not a case that they look similar in many aspects [20:11] oh, systemd also fits in this category [20:11] i'm not talking about the visual design [20:11] bloated piece of software [20:11] i'm talking about the APIs [20:11] systemd is almost the exact opposite [20:11] it is? [20:12] wayland replaces X which does everything, with a tiny library that can only just run a single piece of software [20:12] systemd replaces tiny shell scripts with a massive tool that does everything [20:12] ah [20:12] wayland as protocol [20:13] but the implementations are bloated [20:13] yes, X is a protocol too [20:13] like gnome [20:13] with mutter [20:13] in a sense [20:13] wayland pushes all responsibilty into the compositor shell, which means that instead of getting rid of the old X code, you've just created multiple different broken re-implementations of it [20:14] systemd sucks in responsibilities from other programs, so it's at least standardizing things [20:14] they really are completely opposite in design [20:16] so, we wait and see what happens :) [20:16] no, we continue to complain about the lack of standardization in wayland until they fix it [20:17] why not provide patches? [20:17] patches have already been provided [20:17] the last time sometime tried to do something about this, the wayland devs kicked him off the team [20:18] and then Mir was born? :D [20:18] mmh [20:18] no, northfield was created [20:18] mir has identical design goals to wayland [20:18] and they also have no interest in standardizing anything [20:19] northfield already dead? [20:19] not dead, just resting [20:19] apparently [20:19] i spoke to the developer recently [20:19] pining for the fjords, eh? [20:20] well yeah, it's unlikely that northfield will ever take over the world === drc is now known as Slartibartfast === Slartibartfast is now known as drc [20:21] so it's not easy to change/adjust the vision of the main wayland devs [20:22] well the problem is that they don't want to take on any extra responsibilities [20:22] it's not easy to change/adjust the vision of anybody [20:22] what wayland does, it does well [20:22] Sometimes small pieces of software that do small things are better than a monolithic big one that tries to do everything. And you can easily replace the small piece with another one (maybe a better implementation), without break anything. [20:22] "vision" [20:22] the problem is it's not enough, and there's no standard way of implementing the extra things that are needed, and this is largely because gnome shell doesn't need them [20:23] I see [20:23] and exactly the same applies to mir/unity [20:24] ali1234, one of these missing implementations maybe is related to panels (like in gnome2/xfce) ? [20:24] right, wnck can't work in wayland [20:24] or mir [20:25] a program running in wayland cannot know what other programs are running, which means it is impossible to write a panel in wayland [20:26] wayland also does not support window reparenting at all, so external decorations are impossible [20:26] and programs cannot position their own windows, which breaks xfdesktop [20:26] you can implement all these things in the compositor [20:26] but then your program will only work in one compositor, and it work work in gnome or kde or weston [20:27] doesn't cinnamon uses gnome3 ? How they did that? [20:27] it has nothing to do with gnome 3 [20:28] they run gnome 3 in X11 [20:28] but they have panels, I think... [20:28] so these problems do not apply [20:28] so you can use gnome3 in X11 too? [20:28] they will be forced to rewrite their panels when they switch to wayland, just like gnome did [20:29] and it's really necessary to switch to wayland? [20:29] actually cinnamon is a fork of gnome 3, so that has already happened [20:29] no, it's not necessary to switch at all [20:36] so, maybe it would be better to follow the cinnamon way [21:29] ochosi: http://goo.gl/Gy3XVV [21:30] knome: Oh right. It keeps sending me stuff, but I have to login to do something, but I am not aware what password and it doesn't appear to be my own that I need to moderate the list. [21:30] yyyah. [21:30] * elfy has same issue with the -users list ... [21:31] elfy can prod you with the -devel pass [21:31] i don't have it here right now [21:31] except that the -devel pass fails for the -user list :) [21:31] yeah, that i don't have anywhere [21:31] oh - Unit193 wants the dev pass? [21:31] we most probably want to refresh that [21:31] elfy, yep. [21:32] what do you think of my proposal then? [21:32] done [21:32] I've seen no proposal [21:33] -devel mailing list, a minute ago. [21:33] orite - not seen it yet [21:33] I say I disagree with it ... [21:33] :p [21:36] elfy, great, now please argument ;) [21:36] I'll not - I'll not be able to post my stuff to the -devel list as I need to get people actually talking back to me :) [21:37] ;) [21:37] * Unit193 doesn't think there's anything important he has to go to any list. [21:38] that's because not enough people in QA send things to the list :p [21:38] Hey! I trello'd, what more do you need? ;) [21:40] :) [21:40] to trello on a board I'm subscribed to so I know lol [21:41] or to do one of the checklist things in the only Doing 14.10 card :) [21:41] anyway - I'm off now - cya tomorrow peeps [22:39] my only concern about a moderated list is that the moderators will get bored and forget to moderate posts [22:39] this is basically the situation on ubuntu-devel now [22:39] they'll get daily emails about moderating [22:39] if you're not whitelisted you can't post, and you won't get a rejection either [22:39] just silence [22:39] i think we might be able to set a message for "pending" [22:39] if the moderators get bored... well, then the team won't be very active [22:39] yes, you can [22:40] ubuntu-devel is *very* active [22:40] just not the moderators [23:22] brainwash: we can possibly include it, but I'd be interested in what regressions it causes