[00:15] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 18.10 - i386 - i386 built.
[00:41] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 18.10 - amd64 - amd64 built.
[08:04] <ochosi> hey everyone, just fyi i'll be afk until mid of next week (hoooolidays!)
[08:21] <knome> hf!
[09:01] <brainwash> bluesabre: do reports like this one have to forwarded upstream now? or do you check launchpad too?
[09:01] <brainwash> bluesabre: bug 1783887
[09:04] <brainwash> The question is: should xfpanel-switch check if 'output-name' and 'position' can be applied to the new system, or should xfce4-panel not crash/disappear when given a invalid config
[10:27] <bluesabre> brainwash: it's best to forward to upstream. The ones fixing those bugs are often not in the Xubuntu team
[10:32] <brainwash> bluesabre: isn't xfpanel-switch your domain?
[10:33] <brainwash> aka Xfce4-panel-profiles
[10:50] <bluesabre> brainwash: it is, but most folks wouldn't know that :)
[10:51] <bluesabre> I'll work on resolving that bug soon. Ideally, it would check for those displays and a) fail gracefully, or b) swap them out with the current configuration
[11:02] <brainwash> bluesabre: so, xfce4-panel does not require any patching? I mean this bug could be fixed in both components, or just in either of them
[11:03] <brainwash> it's a bit confusing
[11:15] <bluesabre> Yeah, I'd imagine they both need fixes. Fixing just xfpanel-switch would for the most part hide the issue
[11:29] <bluesabre> ugh, https://bugs.launchpad.net/ubuntu/+source/catfish/+bug/1782735/comments/6
[20:13] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 18.10 - i386 - i386 built.
[20:38] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 18.10 - amd64 - amd64 built.