=== maclin1 is now known as maclin
[05:30] <didrocks> good morning
[05:47] <seb128> good morning desktopers
[05:49] <didrocks> hey seb128
[05:51] <seb128> re didrocks
[05:57] <jibel> good morning
[06:04] <seb128> hey jibel
[06:08] <jibel> salut seb128
[06:09] <seb128> jibel, cups should be fixed in artful, let me know if you have the chance to try the update this morning
[06:12] <jibel> seb128, I tried the version in proposed yesterday and it worked fine
[06:12] <seb128> great
[06:12] <seb128> well it migrated 3 hours ago
[06:12] <seb128> so we should be good
[06:13] <oSoMoN> good morning desktoppers
[06:13] <didrocks> salut oSoMoN
[06:13] <oSoMoN> salut jibel, seb128
[06:13] <didrocks> hey jibel
[06:13] <seb128> lut oSoMoN
[06:13] <jibel> although I've a crash of evince when I print a specific document but I don't think it's related
[06:13] <oSoMoN> salut didrocks
[06:13] <seb128> jibel, can you share the document?
[06:13] <seb128> at least privately?
[06:13] <jibel> sure
[06:13] <seb128> thanks
[06:17] <jibel> seb128, in your inbox
[06:21] <seb128> jibel, thanks, I can confirm the segfault
[06:21] <seb128> let me look a bit at the stacktrace/get debug info
[06:36] <seb128> jibel, that nautilus segfault is specific to videos?
[06:37] <jibel> seb128, I couldn't reproduce with other types
[06:37] <seb128> thanks
[06:37] <seb128> indeed I can confirm
[06:37] <jibel> seb128, there is a reference to vaapi in the trace
[06:37] <seb128> well I just did it on a mp3
[06:37] <jibel> didn't crash for me with an mp3
[06:37] <seb128> so I think it's a bug in the totem extension
[06:38] <seb128> ah
[06:38] <seb128> well it does for me
[06:38] <seb128> I'm going to assume it's the same bug in totem
[06:38] <seb128> well at least start from that one and then test with videos
[06:57] <jibel> there is a similar crash in shotwell
[07:07] <seb128> jibel, when doing what?
[07:12] <jibel> seb128, reported in LP
[07:12] <jibel> I didn't try to reproduce it yet
[07:13] <seb128> k
[07:13] <jibel> in a call right now, i'll come back to it later
[07:16] <jibel> seb128, actually I just opened shotwell under wayland and it crashed
[07:18] <seb128> jibel, evince segfault reported upstream as https://bugs.freedesktop.org/show_bug.cgi?id=102922
[07:18] <ubot5> Freedesktop bug 102922 in pdf backend "evince abrt on a double free in cairo_truetype_font_destroy" [Normal,New]
[07:19] <jibel> thanks
[07:31] <seb128> jibel, shotwell works fine under wayland here but I don't have lot of photos on that machine
[07:32] <seb128> oh
[07:32] <seb128> could be videos there as well
[07:32]  * seb128 going to try that a bit later
[07:33] <seb128> but I need to step out for some hours, shifting those to the evening today
[07:33] <jibel> seb128, I uploaded the crash to bug 1718595 lets see if it 's the same trace
[07:33] <ubot5> bug 1718595 in shotwell (Ubuntu) "shotwell crashed with SIGSEGV" [Undecided,New] https://launchpad.net/bugs/1718595
[07:33] <seb128> thanks
[08:01] <Laney> moin
[08:11] <didrocks> hey Laney
=== zhaoqiang1 is now known as zhaoqiang
[08:22] <Laney> sup didrocks
[08:25] <jibel> seb128, shotwell crashes in the video reader
[08:25] <didrocks> Laney: nothing special, and you?
[08:29] <Laney> mmm not much
[08:29] <Laney> the sky is about 10cm off the ground today
[08:31] <didrocks> waow, blue sky here and sun :)
[08:35] <jibel> there used to be a setting to start a vpn automatically when a specific connection comes up. Where is it?
[08:35] <jibel> I cannot find it in the network or vpn settings
[08:42] <Trevinho> seb128: so, Laney suggested to remove the s390x nux/unity build from the archive...
[08:42] <Trevinho> hey by the way :-)
[08:44] <Trevinho> seb128: you can do that or who can?
[08:45]  * didrocks needs to add multiple 'Add printers button' as the g-c-c panel is using a gtkstack
[08:46] <didrocks> waow, system config printer is buggy in term of refresh with our theme
[08:46] <didrocks> drawing artefacts and such
[08:53] <didrocks> ah, the language support button isn't aligned right, let's ensure we align right all additional buttons as I suggested
[08:53]  * didrocks cleans up the .ui patch as well for language support
[08:54] <didrocks> (useless placeholders)
[09:02] <Trevinho> didrocks: hey, you can also help with removal of nux/unity builds for s360x? :)
[09:02] <didrocks> Trevinho: sure, did you check all rdepends?
[09:03] <didrocks> just open a bug and list all binary packages that needs to be removed please :)
[09:03] <Trevinho> didrocks: yeah, it only has unity
[09:03] <Trevinho> well or... unity itself let me see
[09:04] <didrocks> Trevinho: still, list all binaries package, there is libunity-core* and so on, please
[09:05] <Trevinho> didrocks: on what project?
[09:05] <didrocks> Trevinho: whatever, can against unity source package
[09:05] <Trevinho> It was probably just easier to disable the tests :-D
[09:05] <didrocks> and add all binary packages, ensuring there is no rdepends
[09:05] <Trevinho> ehm, less time consusming
[09:06] <didrocks> as you wish, but I need to list them all to remove them
[09:06] <didrocks> so, be nice to the person who is going to remove them :p
[09:06] <Trevinho> ok
[09:14] <Trevinho> didrocks: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1718615
[09:14] <ubot5> Ubuntu bug 1718615 in nux (Ubuntu) "Nux doesn't build proprerly in s390x arch" [Undecided,New]
[09:16] <didrocks> Trevinho: see, asking you was useful, there were the lenses :)
[09:17]  * Trevinho hopes not to have included too much :-D
[09:17] <Trevinho> or to less
[09:19] <didrocks> Trevinho: done!
[09:19] <didrocks> Trevinho: well, if you followed carefully the rdepends, it should be fine :)
[09:30] <oSoMoN> when I upgrade my artful amd64 VM (vbox, was up-to-date yesterday), the VM boots but gdm fails to display the login screen
[09:45] <didrocks> oSoMoN: the french forums report it's since the kernel upgrade to 4.13.0-11-12, maybe try downgrading it?
[09:46] <oSoMoN> didrocks, thanks, trying that
[09:50] <jibel> oSoMoN, try to disable wayland in gdm
[09:51] <Trevinho> didrocks: yes I did but... Some are all
[09:51] <Trevinho> Trevinho: thanks by the way
[09:51] <Trevinho> Lol
[09:51] <oSoMoN> jibel, how do I do that? I don't have a login screen, can't select a session
[09:52] <Trevinho> didrocks: thanks to you :-)
[09:53] <jibel> oSoMoN, boot in recovery and uncomment #WaylandEnable=false in /etc/gdm3/custom.conf
[09:56] <oSoMoN> jibel, ack, trying to downgrade (or rather not upgrade from my previous snapshot) the kernel first, then I'll try that
[09:57] <oSoMoN> didrocks, not upgrading the kernel works
[09:58] <didrocks> I guess you can drop a line on #ubuntu-kernele :p
[09:58] <didrocks> kernel*
[09:59] <Trevinho> sil2100: hey https://bileto.ubuntu.com/#/ticket/2892 needs to be published but it doesn't go through because of missing build in s390x. We removed it from the archive, but still status gives errors
[10:19] <jibel> didrocks, back to the keybindings topic from yesterday ccsm has little to do in the story. I did a fresh zesty install, applied all the updates, upgraded to artful and all the keybindings from unity7 are preserved and considered non-default under gnome-shell
[10:19] <jibel> didrocks, eg ctrl+super+up/down to maximize/restore instead of super+up/down
[10:20] <didrocks> jibel: interesting, can you look if the keys are considered as default before the upgrade (and then after the upgrade?)
[10:20] <didrocks> jibel: there is nothing I know of (maybe Unity/Compiz does?) writing those keys
[10:20] <didrocks> Trevinho: you may know? ^
[10:20] <sil2100> Trevinho: hm, are those really removed from the archive?
[10:22] <sil2100> Trevinho: I don't see any publishing history that would point that either nux or compiz got removed for s390x from artful
[10:25] <didrocks> sil2100: they, were but indeed, no publishing history for the removal, see bug #1718615
[10:25] <ubot5> bug 1718615 in nux (Ubuntu) "Nux doesn't build proprerly in s390x arch" [Undecided,Fix released] https://launchpad.net/bugs/1718615
[10:25] <didrocks> sil2100: archive skew? I can give a retry
[10:25] <didrocks> nope
[10:25] <didrocks> $ ./remove-package -a s390x -b libnux-4.0-0 libnux-4.0-dev libunity-core-6.0-9 libunity-core-6.0-dev unity unity-lens-video unity-lens-music unity-lens-files unity-lens-applications unity-china-music-scope -m "desktop isn't a target for s390x Bug #1718615"
[10:25] <didrocks> Removing packages from artful:
[10:25] <didrocks> Could not find binaries for 'libnux-4.0-0/None' in artful .  Exiting.
[10:25] <didrocks> -> so done for the archive tool
[10:26] <sil2100> hm, I think bileto is taking the info from LP so maybe it's still a bit too soon for Bileto
[10:27] <sil2100> Maybe it'll notice once LP notices
[10:28] <sil2100> Let's give it some more time
[10:28] <sil2100> btw. last time I remember we wanted to remove unity etc. from s390x there was some opposition (can't remember what though)
[11:24] <Gargoyle> Found a sneaky bug. Might be able to fill out a proper bug report later with some guidance, but thought I would see if anyone else can recreate.
[11:25] <Gargoyle> In settings->devices->printers, click the settings icon for a printer and choose "details". The details "modal" opens with virtually no title bar. making it almost impossible to close.
[11:26] <Gargoyle> I was just about able to right click on the 2 or 3 pixels of menu bar and choose close.
[11:27] <Gargoyle> https://www.dropbox.com/s/88wh5vcpvq9e1z9/Screenshot%20from%202017-09-21%2012-26-23.png?dl=0
[11:31] <andyrock> hey seb128 regarding the urgent notification
[11:31] <andyrock> am I free regarding the design?
[11:31] <Gargoyle> 17.10, updates last installed in Tuesday (I think)
[11:33] <seb128> andyrock, hey, what urgent notifications?
[11:35] <seb128> Trevinho, sorry I have shifted hours today, seems like others helped you with the archive bits though?
[11:43] <jbicha> Gargoyle: that's LP: #1712011
[11:43] <ubot5> Launchpad bug 1712011 in gnome-control-center (Ubuntu) "Unable to close Printer properties" [Low,Triaged] https://launchpad.net/bugs/1712011
[11:44] <jbicha> Gargoyle: Esc key is a workaround to close the dialog
[11:45] <andyrock> seb128: the one you get when an app requires attention
[11:45] <andyrock> it's not so used
[11:45] <andyrock> and I don't think it's high priority
[11:45] <jbicha> Gargoyle: it's an unusual bug because it doesn't happen with GNOME's Adwaita theme
[11:45] <andyrock> but I can deliver it by the end of today without problems
[11:56] <jibel> Trevinho, keybindings bug 1718648
[11:56] <ubot5> bug 1718648 in gsettings-desktop-schemas (Ubuntu) "unity7 keybindings are preserved after upgrade and considered as non-default keybindings" [Undecided,New] https://launchpad.net/bugs/1718648
[12:23] <seb128> andyrock, sorry I changed location, yes for that just do whatever looks fine to you, we can change it later if we want
[12:36] <Gargoyle> jbicha, Thanks for the info. I'll see if I can add anything useful to that bug.
[13:11] <Gargoyle> Is there another bug to say that printing just doesn't work full stop?
[13:12] <doko> is there a way to align the workspaces horizontally?
[13:16] <jibel> Gargoyle, it should be working today. Make sure you have the latest version of cups-filters
[13:16] <Gargoyle> jibel, Just spotted that in the pending updates, running apt now! :-)
[13:19] <kenvandine> Trevinho, do you have that in a silo?
[13:43] <oSoMoN> jibel, didrocks: to follow up on my kernel issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718679
[13:43] <ubot5> Ubuntu bug 1718679 in linux (Ubuntu) "Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland" [Undecided,New]
[13:46] <seb128> oSoMoN, did you ask about it on #ubuntu-kernel?
[13:47] <oSoMoN> seb128, I did, sforshee asked me to file a bug and said he would look into it
[13:47] <seb128> good
[13:48] <jbicha> seb128: LP: #1718643 is intentional behavior upstream. It can be disabled by turning off Tweaks>Windows>Attach Modal Dialogs
[13:48] <ubot5> Launchpad bug 1718643 in gnome-shell (Ubuntu) "Inability to move child dialogues separate from parent applicaitons" [Low,New] https://launchpad.net/bugs/1718643
[13:48] <seb128> jbicha, I know
[13:49] <seb128> jbicha, still, if users think it's a buggy behaviour they should tell upstream
[13:49] <seb128> the feedback might lead upstream to think their design has a flaw if that's the case
[13:49] <seb128> which can't happen without feedback
[13:49] <jbicha> I don't think that's very useful here… but ok
[13:50] <seb128> yeah, bug trackers might not be the best place to give feedback on the experience
[13:50] <seb128> but we don't have a better place for that?
[13:50] <seb128> feel free to redirect them to a mailing list if you think it's more appropriate
[13:52] <seb128> jbicha, anyway I don't care much either way, my rational was just to try to provide feedback to upstream when users think there is a problem with how things are designed
[13:53] <jbicha> in this case, I think the behavior is so fundamental to GNOME that it's unlikely to be changed there
[13:53] <seb128> they can't wontfix it, it's fine
[13:53] <seb128> can*
[13:56] <jibel> today my screen is not locked on resume from suspend, anyone else experienced this?
[13:57] <seb128> I don't
[13:57] <jibel> hmm, sept. 21 15:54:56 herm gnome-shell[2358]: Screen lock is locked down, not locking
[13:57] <jibel> from the journal
[13:59] <oSoMoN> seb128, jibel : I'm seeing the LO snap crash when exporting a presentation to pdf, and there's a cairo_surface_destroy assertion failed message in the console just before the crash, wondering if that could be related to the bug you filed earlier this morning?
[14:00] <oSoMoN> I need to debug it further anyway
[14:00] <seb128> oSoMoN, could be, difficult to say without at least a backtrace
[14:01] <oSoMoN> yup, I'll try to get one
[14:01] <jibel> disable-lock-screen is set to false, everything looks normal, weird
[14:01] <seb128> jibel, well the message suggests that it thinks the screen is locked when it's not?
[14:01] <seb128> GNOME 3.26 is a bit of a disaster :-/
[14:02] <jibel> seb128, yes something along the line, or that it is disabled
[14:02] <jibel> which is not the case
[14:02] <seb128> next cycle we should perhaps avoid the new version
[14:02] <jibel> and obviously not locked since I'm typing :)
[14:02] <jbicha> seb128: the biggest problems are gnome-shell and gnome-control-center; unfortunately those are key parts of new GNOME versions :(
[14:02] <seb128> seems like they didn't really ramp up their quality since we switched
[14:03] <seb128> jbicha, right, gnome-shell especially those segfault, resolution changes being dismissed
[14:03] <jbicha> other apps generally are fine
[14:03] <jibel> gnome-shell and gnome-control-center top 2 on errors.u.c in terms of crashes
[14:03] <seb128> it's even over me how they can release a "stable version" with those issues
[14:03] <seb128> especially in a wayland world
[14:04] <seb128> where a g-s segfault takes your session down
[14:04] <seb128> they should really care more about fixing bugs or at least keep on top of what gets reported
[14:04] <seb128> anyway
[14:04] <seb128> </rant>
[14:04] <jibel> yeah, now I switch to a vt first, start byobu, then log in gnome-shell and connect to the terminal, otherwise it brings everything down on crahs
[14:05] <jibel> next cycle we should only focus on stability
[14:05] <seb128> and stay away from gnome-shell updates
[14:06] <seb128> I wonder what would be the right venue to tell them they have a quality problem and that they should get on it
[14:06] <jbicha> GNOME devs hate it when we mix & match GNOME versions but there are good reasons…
[14:07] <seb128> right
[14:12] <jbicha> I wish GNOME did LTS releases
[14:12] <mdeslaur> https://www.sudosatirical.com/articles/local-man-claims-gnome-is-root-cause-of-world-problems/
[14:12] <jbicha> although that can backfire a bit for initial stability as devs rush to cram features in at the last moment
[14:19] <seb128> jibel, did you confirm that "wayland doesn't work in vm with new kernel" issue?
[14:19] <seb128> like is that impacting everyone?
[14:19] <seb128> is that specific to vms?
[14:19] <jbicha> at least GNOME 3.28 will still target mozjs52 so that's one less thing changing
[14:21] <seb128> right
[14:28] <Trevinho> kenvandine: no... I can do it or you can. As you wish
=== JanC is now known as Guest54020
=== JanC_ is now known as JanC
[14:54] <jibel> seb128, no I didn't
[14:54] <jibel> seb128, it works for me. The main problem is one I reported a while ago with qxl driver
[14:54] <seb128> ah
[14:54] <jibel> seb128, it's specific to virtual box
[14:54] <jibel> it works in qemu
[14:56] <jibel> yeah, last image with kernel 4.13 works in qemu
[14:56] <jibel> oSoMoN, did you try to disable wayland in gdm?
[14:56] <jibel> + latest kernel
[14:57] <jibel> to narrow the problme down
[14:59] <oSoMoN> jibel, I did (see bug report), and that "fixed" the issue indeed
[15:00] <jibel> oSoMoN, k, thanks
[15:00] <jibel> another one in the wayland queue
[15:09] <kenvandine> Trevinho, i can create it
=== ricotz_ is now known as ricotz
[15:33] <oSoMoN> https://forum.snapcraft.io/t/call-for-testing-libreoffice-5-4-1/2217
[15:36] <oSoMoN> and https://plus.google.com/+OlivierTilloy/posts/aqMo6c9qrQE
[16:10] <seb128> oSoMoN, well done on the libreoffice snap update!
[16:12] <oSoMoN> thanks
[16:12] <oSoMoN> let's see if the feedback is good enough to promote to stable sometime next week
[16:32] <oSoMoN> chrisccoulson, chromium-browser fails to build in artful because of changes in glibc, I have a patch for those, let me push that to a PPA near you
[16:34] <oSoMoN> actually it's gonna have to be 61.0.3163.91, the latest stable
[17:15] <oSoMoN> chrisccoulson, chromium-browser 61.0.3163.91-0ubuntu1.1374 currently building in https://launchpad.net/~osomon/+archive/ubuntu/chromium-stable/+packages , it should be safe to copy to artful-proposed as I've already tested that patch against the beta and dev branches, and the build is already past the point where it failed
[17:16] <Laney> see you later
[18:11] <Trevinho> sil2100: Laney tried to publish it actually (https://bileto.ubuntu.com/log/2892/publish/2/), but it failed... Should I clearout the silo or are there other tricks?
[18:53] <seb128> Trevinho, we should probably just pocket copy
[18:55] <oSoMoN> g’night all