/srv/irclogs.ubuntu.com/2017/02/17/#xubuntu-devel.txt

bluesabreThat's fair, I'd say02:04
Unit193Presumably nobody has been testing sessions with GDK_CORE_DEVICE_EVENTS=1?04:44
flocculantknome: but Super+S is synaptic and repo reload07:19
* flocculant is used to Xubuntu being listed last - thought we weren't on the 16.04.2 release announcement 07:40
flocculantbluesabre Unit193 - now we've got thunar 1.6.11 how do we go about getting it to 16.04 ? and will it happen before April? 08:31
Unit193!sru08:32
ubottuStable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates08:32
* Unit193 shrugs.08:32
knomeflocculant, noo ;)09:33
=== Justanick1 is now known as Justanick
pleia2btw http://ubucon.org/en/events/ubucon-summit-us/schedule/15:55
pleia2"10 Years of Xubuntu"15:55
pleia2I guess I have a talk to write15:55
flocculantknome: so run how to start Xubuntu 17.04 on w.x.o ? 17:56
flocculants/run how/run how to by me again ...17:57
SwissBotfeed xfce4-announce had 5 updates, showing the latest 318:01
-SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: thunar 1.6.11 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-thunar-1-6-11-released-tp48891.html (by Simon Steinbeiss)18:01
-SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-notifyd 0.3.5 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-notifyd-0-3-5-released-tp48893.html (by Simon Steinbeiss)18:01
-SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfce4-weather-plugin 0.8.9 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-weather-plugin-0-8-9-released-tp48895.html (by Harald Judt)18:01
knomepleia2, congrats ;)18:47
flocculantUnit193 ochosi - now getting thunar crash when properties on a file - both with master from git or 1.6.11 from repos19:27
ali1234xfce4-display-settings is consistently segfaulting again19:33
flocculantbug 166575019:33
ubottubug 1665750 in thunar (Ubuntu) "Thunar crashes when calling Properties" [Undecided,New] https://launchpad.net/bugs/166575019:33
flocculantdid upstream at 1336119:34
ali1234backtrace has no debug symbols :(19:34
flocculantali1234: well thunar-dbg is installed - perhaps I just do it wrong19:35
flocculanteasy enough to redo - unfortunately ...19:35
ali1234how do i get 1.6.11?19:35
ali1234on 17.0419:35
flocculanthttps://wiki.ubuntu.com/Backtrace19:35
ali1234you can try "apport-retrace -s -S system /var/crash/..."19:36
ali1234but for me even that is not currently working19:36
flocculantali1234: update for 1.6.11 - version in repo now19:36
ali1234i just did "apt upgrade" and i still have 1.6.1019:37
flocculantmmm19:37
ali1234maybe the mirrors are not synced yet19:37
flocculantali1234: assuming you are uk ?19:37
ali1234yes19:37
flocculantI tend to use main server here19:37
flocculantassuming still uk that is :p19:38
flocculantpretty sure it's not coming from a ppa19:38
flocculant(uk too)19:38
ali1234i'll switch to the main archive19:38
ali1234in the mean time19:39
flocculantso *how* do I get debug symbols in a backtrace?19:39
ali1234have debug symbols installed for all libraries19:39
ali1234or use apport to do a retrace19:39
ali1234"apt upgrade" still says nothing to update19:40
flocculantexcept /var/crash is empty19:40
ali1234do you have access to errors.ubuntu.com?19:40
acheronukno crash here. though I am running KDE on this machine19:40
flocculantali1234: yea19:40
ali1234sometimes yoou can get backtraces from there, although it's hard to find the one you want19:40
flocculantali1234: I might purge the gtk3 ppa's first and retry 19:41
flocculantand seems it only crashes out Properties on a file - not a folder19:41
ali1234did you do "ubuntu-bug thunar" to report that bug?19:42
ali1234that normally doesn't work if there's any ppa stuff involved19:42
flocculantali1234: so - errors.u.c for 17.04 for thunar for the past day "No data to display"19:44
flocculantali1234: and yea ack on if ppa involved19:44
ali1234hmm19:44
ali1234can you see private bugs?19:44
flocculantnope19:45
ali1234me neither :(19:45
ali123417.04 being unreleased sends bugs to launchpad, where they get marked private19:45
ali1234instead of e.u.c19:45
flocculantseems the only thunar-debug package is thunar-dbg 19:45
ali1234yeah but you need debug symbols for eg libgio19:45
ali1234libgtk19:45
ali1234etc ...19:45
flocculantmmm19:46
flocculantwouldn't it be nice if thunar-dbg included things it *might possibly* need :p19:47
ali1234-dbg packages have never really worked properly19:47
flocculantor if even there was a 'xubuntu-debug-symbols' or the like19:48
ali1234they're usually several days behind the repos19:48
flocculant;)19:48
ali1234and they only exist for use by apport19:48
flocculantright19:48
ali1234which currently is broken for some reason19:49
flocculant:D19:49
ali1234your best bet is probably to get apport to send a backtrace to launchpad19:49
ali1234then wait for it to retrace19:49
ali1234but if anyone already did that your bug gets marked as private19:49
flocculantI managed to ubuntu-bug just before I posted the link19:49
ali1234then you have to go and ask it to be made public19:49
flocculantyea - been there more than once19:50
ali1234yeah but you have no crash report for apport to attach for some reason19:50
flocculantnope 19:50
ali1234i don't know why. maybe because it crashed too many times before19:50
flocculantpretty sure I didn't do the 'oh ffs just ignore this please' 19:50
ali1234i think it does that automatically after three or four crashes19:51
ali1234i cant get it to touch my crash because i reported it on launchpad19:51
ali1234(xfce4-display-settings:8733): xfce4-display-settings-CRITICAL **: xfce_randr_mode_width: assertion 'mode != NULL' failed19:53
flocculantI don't appear to be able to get that to fall over19:54
ali1234only happens in virtualbox19:54
ali1234https://www.bountysource.com/issues/34695319-display-settings-pops-up-and-then-disappearers19:54
ali1234apparently it doesn't only happen in virtualbox19:55
ali1234https://bugzilla.xfce.org/show_bug.cgi?id=12607 is true bug link19:55
ubottubugzilla.xfce.org bug 12607 in Display Settings "Display Settings pops up and then disappearers" [Major,New]19:55
flocculantali1234: \o/ 19:59
flocculantok so default/apport was set to 19:59
flocculant019:59
flocculantreset it to 1 - restarted - now have a crash report20:00
ali1234okay, now try "apport-retrace -s -S system /var/crash/..."20:00
flocculantseems to be trying - I assume it's going to fall down like you've been seeing20:02
ali1234no if it takes a long time it will probably work20:02
ali1234when it fails for me it fails instantly - because i already reported the bug20:02
ali1234i just unlinked the duplicate bug report on launchpad and now apport wants to report it again20:03
flocculantali1234: well - ubuntu-bug reported it too with a 'some' stacktraces - I assume that's what we needed? 20:04
ali1234did it?20:04
ali1234i dont see any20:04
flocculantali1234: the apport retrace is still going - I'd already re-reported it 20:05
flocculantcurrently private - going to un-private it - dupe my original to the new one20:05
flocculantbug 166576120:08
ubottubug 1665761 in thunar (Ubuntu) "thunar crashed with signal 7 in g_resource_new_from_data()" [Undecided,New] https://launchpad.net/bugs/166576120:08
flocculanthopefully then - that new one has debuig symbols - no idea, don't knwo what they look like20:09
ali1234sorry i lost internet there20:11
ali1234flocculant: i dont see any backtrace on your lp bug20:12
ali1234oh right duplicate20:12
flocculanthope that's got what's needed20:14
flocculantbiab20:15
ali1234it doesn't really tell anything useful20:15
ali1234it crashed inside gio20:15
flocculantftr - when we were testing thunar master+ patches last couple of weeks - Unit193 saw this in the ppa one atm, I couldn't replicate it with master and patches20:17
ali1234its probably random corruption (agan)20:17
ali1234it certainly looks like that, from the stack trace20:17
ali1234based on the stacktrace it looks like what happened is thunar tried to call a method on a gobject20:19
ali1234gio tried to look up the object in the giant hash table of objects it keeps20:19
ali1234but the hash table is completely corrupted, so the whole thing crashed20:19
ali1234so basically the usual random memory corruption caused by use-after-free somewhere completely different20:20
knomeslickymaster, let's continue here...20:30
slickymastersure20:30
slickymastermerge it knome 20:30
knomeanother thing too20:30
slickymasterI just got home from Lisbon and I still want to eat something before the meeting20:30
knomeoh, ok20:31
knomethen go have dinner20:31
knomei can catch up with that other thing later20:31
slickymasterI just have to warm the plate so we can do it now20:31
knomeok, so regarding documentation teams20:31
knomemostly non-xubuntu20:31
slickymasteryes20:31
knomesince we now have our branch under ~xubuntu-doc, there's no real reason for us to keep certain team memberships20:32
slickymastermakes sense20:32
knomelike ubuntu documentation committers - i will not be pushing anything to any other docs branch really20:32
knomeand same for contributors - i don't think there is any synergy or technical reason why we should be members there20:33
slickymasterright, but will that tahes completely off the ubuntu documentation umbrella?20:33
knomethe only direct implication of this is that unless you are a member of ubuntu bug control via other teams (or directly), you'll lose that20:33
knomeslickymaster, in the social sense - we've already been separated technically for a long time (even more during the zesty cycle)20:34
slickymasteryeah, but we won't be a member of Ubuntu Documentation Project Team anymore, right?20:35
knomeand there is https://launchpad.net/~ubuntu-doc20:35
knomexubuntu documentation is20:35
knomebut tbh, i'm not sure if we need to be20:35
knomei only see mainbuntu, edubuntu and us there20:35
knomeanything in the team description actually even applies to us20:36
slickymasterno objections from me reagrding tis20:36
slickymaster+h20:36
knomebut this is why i wanted to talk with you about this20:36
knometo see if you think there is any (social) reason to belong to something like that20:36
slickymastersince we'll be managing our own branch we really don't need to be under their umbrella just for social sake20:37
flocculantali1234: that all sounds like it makes sense to me from just words - but that's it :)20:37
flocculantevening knome slickymaster 20:37
slickymasterevening flocculant 20:37
knomeslickymaster, yes, and there hasn't really been any benefits or any cooperation between different doc teams20:37
knomeso i don't feel like there is any obligation to stay with the rest20:38
slickymasterthat's true, an absolut sero20:38
slickymasterwill that have to be submit to s vote, knome 20:38
slickymaster?20:38
knomei'll take this to the meeting as well (mostly informational) and then do the changes20:38
knomemeh, i don't think so20:38
slickymasterok20:38
knomei'll ask if people think it should be voted on20:39
slickymastereven better20:39
knomebut personally i don't think there's much to vote20:39
slickymasteranyone I'm officially +1 it20:39
knomeheh :)20:39
flocculantali1234: so on a xubuntu updated - but just vanilla, thunar works as expected21:21
ali1234if it's random memory corruption that doesn't mean much unfortunately21:24
ali1234can you make it crash again?21:24
-SwissBot:#xubuntu-devel- ::xubuntu-docs:: [zesty] r628 Merge flocculant's improvements for the contributor document... (by Pasi Lallinaho)21:25
Unit193Debian #85539821:35
ubottuDebian bug 855398 in release.debian.org "unblock: thunar/1.6.11-1" [Normal,Open] http://bugs.debian.org/85539821:35
Unit193flocculant: Do you have thunar-gtkhash installed?21:50
Unit193#6  0x00007f995c550ea6 in ?? () from /usr/lib/x86_64-linux-gnu/thunarx-2/libgtkhash-properties-thunar.so   so yes.21:54
flocculantUnit193: oh yea ...21:55
Unit193Try removing that plugin first.21:55
flocculantUnit193: yup21:56
flocculantI totally forgot about that bit - blaming irssi cos it's easy to look back in hexchat 21:57
flocculantUnit193: thanks for reminding me - I was completely lost on why it was failing now21:58
Unit193Sure thing.21:58
flocculantI guess the bug should be for thunar-gtkhash :)21:58
Unit193Trying something real quick.21:59
Unit193Or not, meeting time.21:59
Unit193#startmeeting Xubuntu community meeting22:00
Unit193Howdy and welcome to the Xubuntu community meeting.  Agenda: https://wiki.ubuntu.com/Xubuntu/Meetings22:00
meetingologyMeeting started Fri Feb 17 22:00:00 2017 UTC.  The chair is Unit193. Information about MeetBot at http://wiki.ubuntu.com/meetingology.22:00
meetingologyAvailable commands: action commands idea info link nick22:00
knomeo/22:00
krytarik\o22:00
Unit193Well I'm here of course.22:00
knomekrytarik, you missed the high-five. you're one row too low.22:00
slickymastero/22:01
Unit193#topic Open action items22:01
Unit193I don't see any.22:01
Unit193#topic Updates and Announcements22:02
flocculantthat's good for 3 months then :)22:02
Unit193We've already hit feature freeze.22:02
flocculant#info - Beta 1 due next week22:03
Unit193Any more, slickymaster, knome?22:04
knomenope22:04
Unit193#topic Discussion items22:04
Unit193#subtopic Thunar - 16.04/16.10 (flocculant)22:04
slickymasternothing here22:05
Unit193flocculant: You have the floor.22:06
flocculantsimply put- what are we going to do about thunar? 14.04 is EOL soon and we'll be expecting people to be upgraded to 16.04 or 16.1022:06
Unit193We have a fixed thunar now in the repos, so likely going to do an SRU.22:07
flocculantright22:07
flocculantthe question is will that be done before EOL of 14.04 22:07
flocculantbecause if it's not22:07
knomeas i mentioned before, since the 14.04 core is supported for 5 years, we can extend our promised 3 years to make sure it does22:08
flocculantthen can we really expect people to care about EOL? 22:08
flocculantknome: yes - but do we just say 'foo' on our media?22:08
knomei don't think there is much more to be done22:09
knomeanyway, we should totally be able to land the SRU before - we still have time22:09
flocculantso then we need to action that22:09
knomeyes22:09
knomeUnit193, want to help with the SRU?22:10
flocculantI know this all sounds obvious - just wanted it minuted :p22:10
Unit193knome: I'd hope bluesabre would.22:10
knomethat works22:10
knome#action knome to work with bluesabre in order to get thunar SRU out ASAP22:10
meetingologyACTION: knome to work with bluesabre in order to get thunar SRU out ASAP22:10
Unit193flocculant: I believe it'll land close enough to the EOL, but we still have to get it in there either way.22:10
knome#nick bluesabre 22:10
flocculantUnit193: yup22:11
Unit193flocculant: So good?22:12
flocculantyea for sure22:12
Unit193#subtopic Documentation team reorganization (knome)22:12
Unit193knome: You have the floor.22:12
knomeso as you might know, the xubuntu docs branch now live under ~xubuntu-doc22:12
flocculantsort of22:13
knomeso in the same direction of progress, we were thinking that since there is no specific reason to belong to any of those ubuntu documentation LP teams, we might just as well do that22:13
knomeobviously individuals are free to stay on any general documentation teams they want to 22:14
knomethe biggest "change" (technically, this is purely social) is that the xubuntu documentation team would not be a member of https://launchpad.net/~ubuntu-doc any more22:15
slickymasterknome is right, since we now manage our own branch we really don't need to be under the ubuntu documentation umbrella just for social sake22:15
Unit193Thus wouldn't get loads of bugreports for other packages, that's why I let myself expire.22:15
knomebut even that is justified; none of the text in the description applies to us, since this is not the way to get contributions to the xubuntu documentation even now22:15
knomeand yes, there is this thought of not having the doc people get that load of mail22:16
slickymaster:)22:16
knomedoes anybody think we should have a vote on this, or should we simply proceed with the actions?22:16
slickymasterIMO we should just proceed with it22:17
krytarik+122:17
knome(again, anything isn't affected, except getting unrelated mail will stop :))22:17
flocculantI'm +1 to us doing whatever suits us22:18
knomeoki, then i guess we're fine22:18
slickymasterUnit193?22:18
knome#action knome and slickymaster to proceed with leaving some general ubuntu documentation teams22:18
meetingologyACTION: knome and slickymaster to proceed with leaving some general ubuntu documentation teams22:18
Unit193There seems to be no opposition or questions, so yeah.22:18
knomeUnit193, sorry for not waiting for the reply, but i was pretty sure you'd be for it :P22:19
slickymasterlol22:19
Unit193Yep, fine.22:19
knomeand i'm good with this, we can continue with the meeting22:19
Unit193#topic Announcements22:19
* Unit193 scratches head.22:19
Unit193OK.22:19
flocculantthought we did that22:19
knomeyes!22:19
Unit193For some reason, it's on the agenda.22:20
knome#info ~xubuntu-doc left ~ubuntu-doc22:20
Unit193slickymaster to schedule next meeting22:20
flocculantyou can have some updates if you want :p22:20
flocculant#info - QA testing of 16.04.2 done and dusted, mostly internally to qa22:20
flocculant#info - testing of xfce components for ochosi:xfce4-notifyd and taskmanager22:20
flocculant#info - testing Setting Manager gtk3 for regressions - 3 bugs reported to bugzilla> xfce 13316, xfce 13317, xfce 1331822:20
flocculant#info - testing of thunar master plus 2 sets of patches (interminably it seemed ...) - response from 1 person via m/l (thanks Pjotr)22:20
ubottubugzilla.xfce.org bug 13316 in General "Search box padding" [Normal,New] https://bugzilla.xfce.org/show_bug.cgi?id=1331622:20
flocculant#info - review Contributor Docs - removed mention of Trello22:20
ubottubugzilla.xfce.org bug 13317 in General "Regressions between 4.12.1 and 4.13.0" [Normal,New] https://bugzilla.xfce.org/show_bug.cgi?id=1331722:20
ubottubugzilla.xfce.org bug 13318 in General "Setting Manager oddities" [Normal,New] https://bugzilla.xfce.org/show_bug.cgi?id=1331822:20
flocculantoh - meant to lose the xfce from those :p22:20
knomelol :)22:21
Unit193Anything else for this meeting?22:22
knomehmm, well22:22
knomelet's do this22:22
flocculantyou might want to action slickymaster or he'll leave it for months :p22:22
slickymasterbah22:23
Unit193#action slickymaster to schedule next meeting.22:23
meetingologyACTION: slickymaster to schedule next meeting.22:23
knome#info The Xubuntu council is hanging in #xubuntu-council if anbyody has any issues they want to take up for the council. Please note that the channel has a no-idling policy, so please do not populate the channel without anything to say - or you will be booted22:23
knomethere we go22:23
Unit193Thanks.22:24
Unit193#endmeeting22:24
meetingologyMeeting ended Fri Feb 17 22:24:17 2017 UTC.  22:24
meetingologyMinutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2017/xubuntu-devel.2017-02-17-22.00.moin.txt22:24
slickymasterthanks Unit193 22:24
flocculantUnit193: thanks :)22:24
Unit193Thanks all for being here.22:25
knomethanks Unit193 22:25
Unit193And the song just ended.22:25
flocculantThe Song Remains The Same too22:25
knomehuh22:26
knomei just noticed ~xubuntu-council is a member of ~xubuntu-bugs22:26
knomethere's no specific reason that is so, it's the owner of that team too22:26
* knome silently presses a few buttons22:26
pleia2now no one sees bugs \o/22:27
knome(for fairness' sake, this has been done with other subteams a long time ago)22:27
knomepleia2, at least not the council members ;)22:27
flocculantpleia2: \o/22:27
knomepleia2, unless they are members of that team directly, like sean22:27
slickymasterhi pleia2 22:27
flocculantknome: you hope22:27
knomei don't - he is :)22:28
knomebesides i could add him if i wanted... O:)22:28
knomehttps://launchpad.net/~xubuntu-bugs/+members22:28
flocculantyou read his mail? 22:28
* flocculant leaves22:28
knomelol22:28
knomei don't... except those that are sent to both of us :)22:29
knomewell i also read the mail he sends that is sent to me... considering you consider that "his mail" ;)22:29
bluesabreevening all22:36
bluesabremissed the meeting :(22:36
flocculanthi bluesabre :)22:36
Unit193...On purpose, but we still gave you a treat.22:37
Unit193bluesabre: I don't have to care about xfce4-mount-plugin or xfce4-sensors-plugin right? :(22:37
* flocculant saves not marking b1 for release next week - till next week :p22:38
knomebluesabre, so, thunar SRU... do you need assistance with it, and what would that be?22:40
bluesabreUnit193, yeah, not important22:43
Unit193They released, I saw it, I put it on a list, I never touched them to put them in the PPA. :322:43
Unit193https://mail.xfce.org/pipermail/xfce/2017-February/035454.html looks important.22:44
bluesabreknome, will be going by https://wiki.ubuntu.com/StableReleaseUpdates#Procedure22:44
* flocculant was just reading that22:44
bluesabreprobably don't need help with it yet, will need some "me toos" later22:44
Unit193Thanks so much for doing the SRU.22:45
bluesabreSRU's aren't so bad22:45
knomeoki, thanks - if there is any paperwork you need me to do anyway, feel free to poke22:45
bluesabreSRU verification is the worst22:45
bluesabreusually goes: 6 people say it's fixed, 1 person tests it wrong perpetually and keeps commenting that it broke and sold their dog22:45
knome:D22:46
flocculant:)22:46
bluesabrethanks knome22:46
Unit193"Oh I didn't enable proposed, nevermind" after 3 months.22:46
bluesabre:D22:47
bluesabreso glad to have thunar back... nautilus is quite a bit slower22:53
bluesabrenicer to look at22:53
bluesabrebut slow22:53
flocculantbluesabre: yea 22:53
-SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r491 Add preliminary support for the dark theme variant... (by Simon Steinbeiß)23:18
-SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r492 Try to get the square buttons in headerbars right (Fixes #17... (by Simon Steinbeiß)23:18
-SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r493 Fix the sidebar color in the dark variant (#168)... (by Simon Steinbeiß)23:18
Unit193Silly ochosi, hiding.23:20
knomeindeed23:21
bluesabre:o23:23
bluesabredark theme variant, that sounds neat23:23
flocculantbut dark23:23
bluesabrexfwm still doesn't support that, I think23:23
flocculantvery very dark23:23
flocculantXubuntu goes over to the dark side - \o/ 23:23
bluesabrelike ochosi's soul23:23
flocculantha 23:24

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!