[03:57] <^Gecko^> anyone have any luck with the Asus Xonar DX soundcard and the optical output? surround sound?
[03:58] <^Gecko^> or surround sound from optical at all?
[06:36] <Zladnyl> Anyone here not afk? I'm lost at this point and need help with something involving linux...
[06:37] <Zladnyl> Here is a better question if anyone here is reading. Anyone got a Dell Alienware PC? Specifically one with Alienware Command Center on it. And even more specific, the Alienware X51 R3...
[06:38] <Zladnyl> Anyone?
[06:39] <Zladnyl> Anyone at all got a PC like the one I just described? And is anyone not afk?
[06:40] <Zladnyl> (╯°□°）╯︵ ┻━┻
[06:40] <krytarik> \o/
[07:09] <lordievader> Good morning
[07:49] <OOPMan> Hello. Has anyone who upgraded from 17.04 to 17.10 noticed KDE taking much longer to login than before. Not only does it sit on the splash screen for much longer but it also takes much longer to load the panels. I have a fresh 17.10 install on another machine (which worse specs) and it doesn't seem to be affected by this problem.
[07:50] <OOPMan> Is there maybe some stray KDE config that could be causing issues?
[08:04] <hateball> OOPMan: I havent noticed it myself. Simple enough to test with a new user
[08:07] <OOPMan> hateball: Good point, will try that
[08:15] <hay207> Hi, i got an issue with a specific font in kde menu [above size 9], is that letters at end of words sometimes are cut as in link below, Is this a font issue or a kdemenu bug ?
[08:16] <hay207> https://uploads.disquscdn.com/images/506ebcaf53af6d95787cf8f986ce2fd48317df4c887178cd451666d56838426e.png
[08:19] <hateball> feels like a kicker bug
[08:20] <hateball> hay207: is that kubuntu 14.04 ?
[08:20] <hay207> yes
[08:20] <hateball> looks like KDE 4.x
[08:21] <hateball> well, I dunno what to advice really. while kubuntu itself is still supported, upstream kde has dropped support for 4.x
[08:21] <hateball> so... I'd consider upgrading to 16.04
[08:21] <hateball> and 14.04 -> 16.04 is not a supported upgrade path (even if it works for the most part) so there might be some breakage
[08:22] <hay207> Should i report the bug to kde ?
[08:24] <hateball> hay207: Like I said, upstream will only tell you upgrade. But you can file a Kubuntu bug and maybe there's a fix that can be backported
[08:24] <hateball> !bug
[08:26] <hay207> Ok, thanks
[08:31] <hateball> hay207: but really you should consider upgrading to 16.04, so you can smoothly upgrade to 18.04 in a few months
[08:32] <hay207> i guesss when 18.04 comes, i do a clean install on an empty partition rather than upgrade
[12:39] <batteronizer> And of course, I want to continue using plasma search
[12:41] <batteronizer> Oops, mixed up messages
[12:41] <batteronizer> Hi, I'm on Kubuntu 16.04. mysql constantly consumes 15-20% CPU.
[12:41] <batteronizer> The only solution I've found so far is $ akonadictl stop
[12:41] <batteronizer> Is there a way to fix the high CPU consumption? My computer runs very slow otherwise.
[12:43] <hateball> batteronizer: is this a fresh install?
[12:43] <batteronizer> hateball: yes
[12:43] <BluesKaj> Hi folks
[12:44] <hateball> batteronizer: do you use the akonadi stuff? otherwise it is fine to leave it stopped
[12:44] <batteronizer> I want to use plasma search
[12:44] <hateball> batteronizer: you mean krunner? alt+f2 or alt+space
[12:44] <batteronizer> And calendar etc might be useful too
[12:44] <hateball> batteronizer: that's not dependant on akonadi but rather baloo. calendar is akonadi tho
[12:45] <batteronizer> Yeah krunner and the Alt+F1 menu as well
[12:45] <hateball> batteronizer: if it is a fresh install I suggest you add this PPA and upgrade https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports
[12:45] <hateball> stock 16.04 is a little more buggy than desirable
[12:46] <batteronizer> Ah cool
[12:46] <batteronizer> The high CPU issue used to be there in 15.10 and earlier as well
[12:47] <batteronizer> hateball: btw, when I perform a file search from dolphin, it never gives me any results
[12:48] <batteronizer> Even krunner only gives results from recent documents
[13:03] <hateball> batteronizer: try "balooctl stop" reboot and "balooctl start" to restart the indexing
[13:05] <batteronizer> Alright, I'll give it a try in some time
[16:40] <Prototype> ello
[16:41] <Prototype> well, i did come here to discuss python3 and my update process hogging 25% of my CPU,  but it seems to have settled down now
[16:42] <Prototype> but since im here now....
[16:46] <BluesKaj> hi Prototype the python process updates right after the unattended upgrades which upgrade by default in the background about a minute after logging in to the ps
[16:46] <BluesKaj> pc
[16:46] <Prototype> ah ok,  thats will be why rebooting didnt solve it
[16:46] <BluesKaj> yup
[16:47] <Prototype> thanks
[16:47] <BluesKaj> np
[16:48] <Prototype> might upgrade to 17.10 this weekend,  was going to wait until 18.04 comes out and i get my new SSD
[16:49] <Prototype> gonna go over to offtopic
[17:40] <Rammelbieber> Hello, I have a question to Kubuntu Log In Proglems. I started Kubuntu (Cynthos <IP_ADDRESS> on x86_64) and I could not login - kinda freeze screen or login. After press ESC while booting, I switched to the recovery mode and tried to remove unnecessary stuff on disk. It removes a lot of old kernel data and after reboot, it started without any problems. For sure, I googled for that kind of problem, but after 20 minutes
[17:40] <Rammelbieber> of search, I did not find anything. So, anyone of you guys have a glue, what the problem maybe was?
[17:42] <BluesKaj> Cynthos ?
[17:44] <BluesKaj> Rammelbieber,^
[17:45] <Rammelbieber> forget this information ^^
[17:46] <Rammelbieber> But back to my question. I can't figure it out, what triggered my login problems (screen freeze)
[17:47] <BluesKaj> Rammelbieber, when did ti freeze ?
[17:48] <BluesKaj> it
[17:48] <Rammelbieber> In the login screen, right after I typed my password and press return
[17:51] <BluesKaj> ok , which graphics card/chip ?
[17:55] <Rammelbieber> Intel Corp 3rd Gen Core processor Graph. Controller (rev 09) - command bash: lspci | grep VGA
[17:59] <Rammelbieber> Can it be possible that some old linux kernel versions get in the newest one's way ?
[18:00] <BluesKaj> hmm, that  kernel module driver is installed by default
[18:00] <BluesKaj> or should be
[18:01] <BluesKaj> sorry , but I have to leave...my vehicle has an appt to be winterized
[18:09]  * genii sips


[05:11] <mborzecki> morning
[06:26] <zyga> good morning
[06:30] <mup> PR snapd#9198 closed: features: add HiddenSnapFolder feature flag <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/9198>
[06:36] <mborzecki> zyga: hey
[06:36] <zyga> hey :)
[06:36] <zyga> finally some cold air, eh?
[06:36] <mborzecki> yeah, much cooler (and nicer)
[06:37] <mborzecki> later summer/early autumn, cold mornings/evening, warm during the day
[06:37] <mborzecki> s/later/late/
[06:39] <mborzecki> errand, back ~11
[06:39] <mborzecki> mvo: hey
[06:39] <zyga> irc, eh,...
[06:39] <mvo> good morning mborzecki and zyga
[06:40] <mborzecki> need to run an errand, back ~11 hopefully
[06:40] <zyga> good morning mvo
[06:40] <zyga> mborzecki o/
[06:40]  * zyga waits for Lucy to wake up
[06:41]  * zyga goes to squash merge https://github.com/snapcore/snapd/pull/7825
[06:41] <mup> PR #7825: many: use transient scope for tracking apps and hooks <Security-High> <Squash-merge> <Created by zyga> <https://github.com/snapcore/snapd/pull/7825>
[06:41] <zyga> just need to think of a proper commit message
[06:43] <zyga> is anyone else using "git reflog" like the recent call lists on pre-smartphones?
[06:45] <mup> PR snapd#9204 opened: sandbox: track applications unconditionally <Created by zyga> <https://github.com/snapcore/snapd/pull/9204>
[06:46] <zyga> ^ this is not yet ready for review
[06:46] <zyga> I want to see how it affects our tests
[06:57] <zyga> I'll go do some reviews
[06:57] <zyga> and then break to handle lucy being awake
[06:57] <zyga> and should then return for 1:1 and remaining work
[07:00] <mup> PR snapd#7825 closed: many: use transient scope for tracking apps and hooks <Security-High> <Squash-merge> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/7825>
[07:03] <pstolowski> morning
[07:03] <zyga> good morning Pawel
[07:41] <mvo> good morning pstolowski
[07:42] <pstolowski> o/
[07:48] <mvo> just fyi (all) 8982 needs reviews, samuele is happy with it on a high level but did not do a full review (not urgent though)
[08:12] <pstolowski> ack
[08:36] <pstolowski> mborzecki: hey, i've updated selinux profile in #9084, can you take a look (last commit)?
[08:36] <mup> PR #9084: o/snapstate: check disk space before creating automatic snapshot on remove (3/N) <Disk space awareness> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9084>
[08:53] <zyga> In the office
[09:08] <zyga> mborzecki hey
[09:08] <zyga> mborzecki I've proposed a draft that attempts systemd-based app tracking by default
[09:08] <zyga> and I got a few denials for selinux
[09:08] <zyga> 1) type=AVC msg=audit(08/24/20 07:27:34.527:12644) : avc:  denied  { getattr } for  pid=78926 comm=snap path=/run/user/0/bus dev="tmpfs" ino=22956 scontext=system_u:system_r:snappy_cli_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=sock_file permissive=1
[09:09] <zyga> 2) type=AVC msg=audit(08/24/20 07:27:34.528:12645) : avc:  denied  { write } for  pid=78926 comm=snap name=bus dev="tmpfs" ino=22956 scontext=system_u:system_r:snappy_cli_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=sock_file permissive=1
[09:09] <zyga> 3) type=AVC msg=audit(08/24/20 07:27:34.529:12646) : avc:  denied  { connectto } for  pid=78926 comm=snap path=/run/user/0/bus scontext=system_u:system_r:snappy_cli_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_dbusd_t:s0-s0:c0.c1023 tclass=unix_stream_socket permissive=1
[09:09] <zyga> I would appreciate some ideas on how to tackle that
[09:10] <zyga> those are from fedora 32
[09:12] <zyga> mborzecki I've added a comment on https://github.com/snapcore/snapd/pull/9204 with the same information
[09:12] <mup> PR #9204: sandbox: track applications unconditionally <Created by zyga> <https://github.com/snapcore/snapd/pull/9204>
[09:23] <mborzecki> re
[09:27] <pedronis> mborzecki: hi, I did a pass on #9201
[09:27] <mup> PR #9201: [RFC] boot: observe update & rollback of trusted assets <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9201>
[09:31] <mborzecki> pedronis: thanks, would have some time for a chat later?
[09:31] <pedronis> mborzecki: before the standup
[09:31] <mborzecki> pedronis: sounds good
[09:31] <mborzecki> let me add something
[09:35] <mborzecki> zyga: looks like this should be covered by dbus chat interfaces
[09:35] <mborzecki> zyga: let me see if there's something for chattign with systemd specifically
[09:35] <zyga> thank you!
[09:40] <mborzecki> zyga: there's a bunch of systemd_dbus_chat in refpolicy but those seem to cover logind, timedated, machined, resolved
[09:40] <zyga> do we need a new interface or is there a better way out?
[09:43] <mborzecki> zyga: hm but it's user_tmp_t, can you try adding userdom_write_user_tmp_sockets(snappy_cli_t) to the policy, reload and see what happens?
[09:45] <zyga> mborzecki sure, I'll try
[09:49] <pstolowski> mborzecki: heh, my selinux fix worked everywhere except for centos 8. although there i see "type=AVC msg=audit(1598261418.464:4691): avc:  denied  { getattr } for  pid=133098 comm="snapd" path="/var/snap/lxd/common/ns/shmounts"
[09:50] <mborzecki> pstolowski: why is snapd looking there?
[09:50] <zyga> mborzecki: probably because "du"
[09:50] <zyga> to estimate size of the data
[09:50] <pstolowski> yes exactly
[09:50] <zyga> in a way we need one-file-system that really means ignore-magic-filesystems
[09:53] <mborzecki> pstolowski: zyga: there's --one-file-system switch to du
[09:53] <zyga> but we don't really want that
[09:53] <zyga> we want to allow people to have other file systems mounted on /var/snap/blargh
[09:53] <zyga> what we want is to filter out nsfs
[09:54] <zyga> or procfs
[09:54] <mborzecki> zyga: should those other filesystems count towards snapshot size?
[09:54] <pstolowski> that's interesting. i wonder what happens when we do actual snapshot
[09:55] <zyga> it probably archives an empty file
[09:55] <zyga> it's a permissive profile
[09:56] <zyga> it's a bind mount of /proc/PID/ns/mnt to an empty file
[09:56] <zyga> so the archiver will just see the empty file
[10:03] <pstolowski> yeah but what about the rest of proc\
[10:03] <zyga> pstolowski is all of proc mounted in SNAP_DATA?
[10:03] <pstolowski> zyga: i don't know, re-running to see what happens (it's a lxd snap_
[10:03] <pstolowski> )
[10:03] <zyga> pstolowski I think you will only find nsfs
[10:04] <zyga> the rest of the filesystems are mounted inside that thing
[10:04] <zyga> it's like a chest for more mounts
[10:07] <zyga> mborzecki I have one deny left
[10:07] <zyga> mborzecki I have one deny left
[10:08] <zyga> type=AVC msg=audit(08/24/20 10:05:41.032:928) : avc:  denied  { connectto } for  pid=29450 comm=snap path=/run/user/0/bus scontext=system_u:system_r:snappy_cli_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_dbusd_t:s0-s0:c0.c1023 tclass=unix_stream_socket permissive=1
[10:09] <zyga> brb
[10:09] <mborzecki> zyga: ok, so you probably need unconfined_dbus_chat(snappy_cli_t) now
[10:09] <ijohnson> morning folks
[10:09] <zyga> hey ijohnson :)
[10:09] <zyga> mborzecki trying
[10:09] <mvo> good morning ijohnson
[10:09] <ijohnson> o/
[10:09] <ijohnson> mmm have we not had a new snapd edge since 8-22 ?
[10:09] <mborzecki> zyga: and maybe unconfined_dbus_connect(snappy_clit_t) too
[10:09] <mborzecki> ijohnson: hey
[10:10] <ijohnson> or 22-8 for y'all europeans :-)
[10:10] <pstolowski> hi ijohnson !
[10:10] <ijohnson> hey pstolowski
[10:10] <zyga> ijohnson looking
[10:10] <zyga> yeah
[10:10] <zyga> it seems so
[10:11] <ijohnson> smells odd
[10:11] <zyga> ijohnson snapd had a long weekend? :D
[10:11] <ijohnson> haha maybe
[10:11] <zyga> either stuck in moderation or the publish pipeline got blocked somewhere
[10:15] <mvo> ijohnson: probably no changes in edge since 22 ?
[10:16] <ijohnson> mvo: ah actually you're right there were a couple commits this morning but nothing over the weekend
[10:16] <ijohnson> I'm just so used to seeing the snapd snap update every day
[10:22] <zyga> re
[10:24] <zyga> ha, does it mean we had a long weekend instead?
[10:24] <zyga> as in two days without patches
[10:25] <zyga> ijohnson https://listed.zygoon.pl/17659/introduction-to-bashunit-unit-testing-for-bash-scripts :)
[10:39] <ijohnson> do we hijack the post-refresh hook for the core* snaps as well as the configure hook ?
[10:42] <ijohnson> zyga: very cool stuff! that's really nice to see it all come together like that, one thing I wonder though is that in the failure output you have for bashunit you don't see what the actual output of `hello_world` function is before the grep fails, so it's a bit difficult to debug
[10:43] <ijohnson> zyga: that's probably intristic to using bash however so probably not worth looking into, but I wonder if it would be helpful to have some kind of test util command you can use in the unit test file that saves the output inside pipes only to be displayed on test failure
[10:43] <ijohnson> zyga: something like `hello_world | echo_on_fail | grep -qFx 'Hello world'`
[10:43] <ijohnson> just a thought
[10:44] <ijohnson> I've wanted something like that _so_ many times when looking at spread failures
[10:48]  * zyga-x240 switches devices
[10:51] <zyga-x240> mvo: 2.46 branches are red, do you want to merge master or cherry pick all the fixes back>
[10:51] <mvo> zyga-x240: will merge master to it today
[10:52] <zyga-x240> ok
[10:52] <zyga-x240> do 2.46 jamie branches make sense to review then?
[10:56] <mvo> zyga-x240: no, please not
[10:56] <mvo> zyga-x240: in a meeting now
[10:56] <zyga-x240> ok
[10:56] <mvo> zyga-x240: we can close them
[11:16] <zyga-x240> mvo: ack, doing that now
[11:16] <mvo> ta
[11:21] <mup> PR # closed: snapd#9192, snapd#9193, snapd#9194, snapd#9195
[11:25] <ijohnson> real simple uc20 PR: https://github.com/snapcore/snapd/pull/9205
[11:25] <mup> PR #9205: boot/initramfs_test.go: reset boot vars on the bootloader for each iteration <Simple 😃> <Test Robustness> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9205>
[11:26] <mup> PR snapd#9205 opened: boot/initramfs_test.go: reset boot vars on the bootloader for each iteration <Simple 😃> <Test Robustness> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9205>
[11:26] <zyga-x240> is shell surprising? https://paste.ubuntu.com/p/FGYyvVXmm8/
[11:28] <zyga-x240> our || true pattern is dangerous
[11:28] <ijohnson> wow just wow
[11:28] <ijohnson> how can such fundamental things in bash be so broken
[11:28] <zyga-x240> ijohnson: it's documented :)
[11:28] <zyga-x240> it's a feature
[11:28] <zyga-x240> just ill-designed IMO
[11:28] <zyga-x240> I think we can do something like "not"
[11:29] <ijohnson> didn't we have a NOT in spread ?
[11:29] <zyga-x240> we have "not" in snapd
[11:29] <zyga-x240> it's really exactly the same feature in bash that requires it
[11:30] <diddledan> yes. it's surprising :-) (not what I expect with `set -e`)
[11:30] <zyga-x240> diddledan: it's just another case of https://listed.zygoon.pl/17629/broken-composition-or-the-tale-of-bash-and-set-e
[11:30] <diddledan> I guess you need to add set -e inside the function?
[11:31] <zyga-x240> diddledan: but just seeing the code behave this way is shocking
[11:31] <zyga-x240> diddledan: no :)
[11:31] <zyga-x240> diddledan: try that
[11:31] <zyga-x240> it's ignored
[11:31] <diddledan> gah
[11:31] <zyga-x240> the link I referenced explains why
[11:31]  * diddledan reads it
[11:31]  * zyga-x240 reviews nested.sh
[11:32] <diddledan> it's the same with /bin/sh (which in Ubuntu 20.04 is dash, right?)
[11:32] <zyga-x240> yes
[11:32] <zyga-x240> it's a very old feature
[11:33] <diddledan> the `do-something && do-something-on-success || do-something-on-fail` is a common pattern that I've seen all over the interweb
[11:35] <zyga-x240> diddledan: it all depends on what those are
[11:35] <zyga-x240> diddledan: also, remove the echo that says "surprising" and it's well, also documented but more surprising
[11:37] <diddledan> gosh, there's a lot of strange interactions you've highlighted
[11:42] <zyga-x240> mvo: shellcheck issue (reported in early 2019) https://github.com/koalaman/shellcheck/issues/1484
[11:44] <zyga-x240> cachio: how much work would it take to make nested.sh a non-sourced script?
[11:44] <ijohnson> morning cachio
[11:45] <cachio> zyga-x240, hi, I already did something like that a time ago
[11:45] <cachio> ijohnson, hi
[11:45] <zyga-x240> cachio: oh? where?
[11:45] <cachio> good morning
[11:45] <cachio> zyga-x240, I closed that a time ago
[11:45] <zyga-x240> why?
[11:45] <cachio> I need to open it again
[11:46] <cachio> because there were too many changes
[11:46] <zyga-x240> I'm reading https://github.com/snapcore/snapd/pull/9098 and I'm very worried about bugs
[11:46] <mup> PR #9098: tests: new organization for nested tests <Run nested> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9098>
[11:46] <zyga-x240> well, we can start small
[11:46] <cachio> Iand I decided to create a new change to address that
[11:46] <zyga-x240> but I think we must go that way
[11:47] <cachio> I could make it again
[11:47] <zyga-x240> please start small
[11:47] <cachio> it could be a tool
[11:47] <zyga-x240> prepare/restore + execute
[11:47] <zyga-x240> yeah, I think sourcing is a no-go
[11:48] <zyga-x240> port a single test (keep nested.sh as-is)
[11:48] <zyga-x240> over time it will replace the other
[11:49] <cachio> zyga-x240, ok, makes sense
[11:49] <zyga-x240> cachio: why is execute remote using "$*"?
[11:49] <zyga-x240> https://github.com/snapcore/snapd/pull/9098/files#diff-3af5dfa44ec70d885e9485dbb117f52fR844
[11:49] <mup> PR #9098: tests: new organization for nested tests <Run nested> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9098>
[11:51] <cachio> zyga-x240, it is very old
[11:51] <cachio> zyga-x240, I think federico created that
[11:51] <zyga-x240> I think that's wrong
[11:51] <cachio> and nobody updated that
[11:51] <zyga-x240> and I suspect it's broken with regards to quoting
[11:52] <zyga-x240> cachio: I did a quick pass over https://github.com/snapcore/snapd/pull/9098#pullrequestreview-473374133
[11:52] <mup> PR #9098: tests: new organization for nested tests <Run nested> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/9098>
[11:52] <cachio> zyga-x240, nice, thanks
[11:52] <cachio> I'll take a look
[11:53] <zyga-x240> cachio: let me know if anything I said there is unreasonable please
[11:54] <zyga-x240> cachio: please look through all the functions, they should not create new globals unless that's exactly desired
[11:54] <zyga-x240> e.g. start_nested_classic_vm defines a dozen or so new globals
[11:55] <cachio> zyga-x240, ok, np, I'll update that
[11:55] <zyga-x240> cachio: wait_for_ssh defines retry as a global
[11:55] <zyga-x240> please go through the entire file
[11:56] <cachio> zyga-x240, ok, I'ldd
[11:56] <cachio> I'll do
[11:57] <zyga-x240> thanks,
[11:57] <zyga-x240> the more we learn about shell the more we need to be careful
[11:58] <cachio> zyga-x240, yes hehehe
[12:25] <pstolowski> mborzecki: pondering what to do about that second denial on centos8 only; is "allow snappy_t unconfined_service_t:file getattr;" too terrible?
[12:25] <mborzecki> pstolowski: wouldn't that only mask the issue?
[12:27] <pstolowski> mborzecki: fwtw these files appear empty, and are included in actual snapshot
[12:30] <zyga-x240> pstolowski: they are empty
[12:31] <zyga-x240> pstolowski: they are mount points to contain nsfs objects
[12:32] <mup> PR snapcraft#3260 opened: tools: update setuptools in environment-setup <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/3260>
[12:34]  * zyga-x240 -> lunch
[12:46] <mup> PR snapd#9160 closed: boot, o/devicestate: observe existing recovery bootloader trusted boot assets <UC20> <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/9160>
[12:50] <pstolowski> degville: hi, welcome back! it seems you made a nice shot of milky way but unfortunately for some reason i see very pixelated/blurry pictures, something wrong with google photos here i suspect
[12:52] <ijohnson> zyga-x240: what's your take on passing function names to a bash function? I want to inject any function to be called during the execution of another function, but only sometimes, something like passing a func() as a param in Go
[12:52] <ijohnson> zyga-x240: does my idea seem terrible given your current experiences ?
[12:53] <ijohnson> I could just add all the functions I need inside the main function and just use a silly named option/switch to the function when I call it
[12:55] <zyga-x240> ijohnson: re
[12:55] <zyga-x240> ijohnson: let me read backlog
[12:55] <ijohnson> zyga-x240: sure no rush
[12:55] <zyga-x240> ijohnson: no, not really
[12:55] <zyga-x240> ijohnson: there's even a way to do "pointers" in bash if you need to
[12:56] <zyga-x240> ijohnson: the more important detail is exactly how is the function called
[12:56] <zyga-x240> ijohnson: I think that disabling set -e, calling the function, recording $? and re-enabling set -e is probably correct, to the best of my understanding
[12:56] <zyga-x240> ijohnson: some simpler functions are also correct in more generic cases, those that involve a single command
[12:57] <ijohnson> zyga-x240: the function I need to call is very simple, but it needs to be called at a very specific point in time
[12:58] <zyga-x240> ijohnson: I'm happy to review and suggest improvements
[12:58] <ijohnson> but actually I think I can get away with just a single implementation, thinking about it I don't know that I need multiple different functions to be called so I think I'll just use a special optional argument to the original function I need to call
[13:15] <degville> pstolowski: thanks for letting me know (and the welcome back!) - I'll check, but it's pretty low quality anyway as it was just a long exposure shot taken with my phone. I do have a RAW version, so I may try and play with it in Darktable.
[13:23] <mup> PR snapcraft#3261 opened: requirements: pin setuptools devel requirement <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/3261>
[13:29] <mborzecki> zyga-x240: there's no way to set the 'script' interpreter in spread, or is there?
[13:29] <zyga-x240> mborzecki: no and in addition, spread joins many separate task together
[13:29] <zyga-x240> IIRC
[13:32] <ijohnson> let's all switch to julia instead of bash
[13:32] <ijohnson> alternative to julia would be the good ol lisp
[13:34] <zyga-x240> ijohnson: I think js is the most realistic alternative
[13:34]  * ijohnson really doesn't wanna write js tho
[13:34] <zyga-x240> it's not great but has arguably the best tooling
[13:34] <ijohnson> I see your clojures in js and raise you an offer of erlang
[13:35] <zyga-x240> I think it's not something we should pick in a rush
[13:35] <zyga-x240> maybe figuring out how to transition to anything is more relevant
[13:35] <zyga-x240> then we can consider alternatives
[13:37] <cachio> zyga-x240, I see this error https://github.com/snapcore/snapd/runs/1021534236#step:5:1744
[13:38] <cachio> todya the image has been updated
[13:38] <cachio> did you already see that?
[13:40] <zyga> cachio strange, is that image changing from efi to legacy boot?
[13:42] <cachio> no
[13:42] <cachio> zyga, it shouldn't
[13:42] <cachio> I am trying to reproduce
[13:44] <zyga> ok
[14:11] <mup> PR snapd#9206 opened: boot: complain about reused asset name during initial install <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9206>
[14:31] <zyga> snap wait --help panics
[14:32] <zyga> pstolowski snap save on f32 says "broken: invalid snapshot"
[14:33] <zyga> https://pastebin.ubuntu.com/p/cxHqJ9MZQn/
[14:34] <mborzecki> zyga: backtrace goes to go-flags
[14:34] <zyga> maybe go-flags is old
[14:35] <mborzecki> zyga: maybe a particular version is broken
[14:35] <zyga> the beauty of maintaining packages
[14:36] <pstolowski> zyga: ? is this my PR?
[14:36] <zyga> nope
[14:36] <zyga> mborzecki it creshes on
[14:36] <zyga>                                         descPadding := strings.Repeat(" ", descStart-len(argPrefix))
[14:36] <zyga> afk
[14:37] <zyga> dog needs to go out
[14:41] <pstolowski> we run snapshot-basic spread test everywhere, are you sure it's not some local issue on your f32?
[14:48] <pedronis> pstolowski: I did a pass on #9199
[14:48] <mup> PR #9199: snapstate: installSizeInfo helper that calculates total size of snaps and their prerequisites <Disk space awareness> <Needs Samuele review> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9199>
[14:49] <pstolowski> pedronis: just saw it, thanks
[14:51] <pstolowski> mborzecki: does the selinux workaround in #9084 look fine to you? it passed now (except for unrelated test failure on centos8 and suse)
[14:51] <mup> PR #9084: o/snapstate: check disk space before creating automatic snapshot on remove (3/N) <Disk space awareness> <Created by stolowski> <https://github.com/snapcore/snapd/pull/9084>
[14:55] <mborzecki> pstolowski: yeah, i don't think we have any other options at this point
[14:56] <pstolowski> mborzecki: ok thanks, i'll land this
[15:01] <mup> PR snapd#9084 closed: o/snapstate: check disk space before creating automatic snapshot on remove (3/N) <Disk space awareness> <Created by stolowski> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/9084>
[15:03] <mborzecki> pstolowski: still, it'd be nice to maybe ask the lxd team what that ns/shmounts contains, my rough guess it's some bit of /proc/self/ns/.. of the lxd process, hence the unconfined_t label (and nsfs fstype)
[15:07] <pstolowski> pedronis: interesting, so the idea is to essentially exclude snaps that could have been installed in the meantime when computing total?
[15:07]  * cachio lunch
[15:23] <pedronis> pstolowski: yes, as I said, it doesn't cover all cases, but it get us closer to the kind of code that we would need for that
[15:26] <pstolowski> pedronis: right, got it, thanks
[15:34]  * zyga-x240 goes for PT
[15:38] <mvo> pstolowski: I updated 8982
[15:38] <mvo> pstolowski: thanks for your review, the misgging BadRequest test highlighted a bad error message
[15:38] <pstolowski> mvo: yes, i looked briefly, thanks for the changes
[15:39] <pstolowski> 👍
[15:53] <pstolowski> +1
[16:15] <mvo> yay now 8982 just needs a second review
[16:17] <mup> PR snapd#9207 opened: boot/bootstate20: reboot to rollback to previous kernel <Bug> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9207>
[18:01] <zyga-x240> re
[18:02] <zyga-x240> today's exercise was *intense*
[18:02] <zyga-x240> I'm genuinely tired
[18:02]  * zyga-x240 needs water
[18:18]  * zyga-x240 is rehydrated
[18:18] <zyga-x240> let's write some ocd
[18:18] <zyga-x240> *code
[18:32]  * zyga-x240 goes upstairs
[18:53] <mup> PR core20#82 opened: [RFC] hooks: mv docker user/group definition to extrausers <Created by anonymouse64> <https://github.com/snapcore/core20/pull/82>
[19:22] <mup> PR snapd#9208 opened: tests/nested/core20/kernel-failover: add test for failed refresh of uc20 kernel <Run nested> <Test Robustness> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/9208>
[19:25]  * ijohnson EODs


[08:42] <eliasps> Hello, any launchpad administrators here to have a look at this when convenient? https://answers.launchpad.net/launchpad/+question/293510. It's about renaming a team and it's mailing list, and downloading some launchpad teams' mailing list archives. Thank you.


[04:32] <frickler> there's a regression in the latest apache2 updates at least for focal and impish. a request for e.g. /path/xyz gets passed to an uwsgi backend as /pat//xyz
[05:02] <frickler> or to be more precise, I get SCRIPT_NAME="/pat" instead of "/path" and PATH_INFO="//abc" instead of "/abc"
[05:13] <frickler> I hope this is enough to reproduce https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1945274
[05:20] <sbeattie> frickler: thanks.
[05:31] <frickler> so the culprit seems to be CVE-2021-36160.patch , if I build the focal version without that patch, the issue is resolved
[05:45] <sbeattie> yeah, that was the likely candidate.
[06:09] <frickler> so ... we are using this ProxyPass statement: ProxyPass "/placement" "unix:/var/run/uwsgi/placement-api.socket|uwsgi://uwsgi-uds-placement-api/" retry=0
[06:10] <frickler> if I remove the trailing / in the uwsgi:// path, things get back to work. not sure if that's actually a bug in our deployment that was just uncovered by the CVE fix
[06:10] <frickler> it also only affects some apps, not everything
[06:18] <amurray> since there is no trailing / on "/placement" then I don't think there should be one on the uwsgi:// URI either
[06:21] <amurray> see https://httpd.apache.org/docs/trunk/mod/mod_proxy.html#proxypass -  "If the first argument ends with a trailing /, the second argument should also end with a trailing /, and vice versa. Otherwise, the resulting requests to the backend may miss some needed slashes and do not deliver the expected results."


[15:05] <Mouxon> Hi! I just upgraded to Zesty (from Yakkety) and now, I have a lot of problems with gtk applications. I tried to execute gedit or gtk3-demo, but nothing happened and there is no error. Any idea to show the log ?
 @Mouxon, Run it in the terminal.
[15:27] <Mouxon> @tsimonq2, I tried but I successed to have an error with 'gedit --wait': "Failed to register: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying".
[15:27] <meetingology> Mouxon: Error: "tsimonq2," is not a valid command.
[15:27] <Mouxon> tsimonq2, I tried but I successed to have an error with 'gedit --wait': "Failed to register: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying".
[15:28] <Mouxon> I also tried to execute vim-gtk and vim-gtk3 and it seems that only gtk3 doesn't work
 @wxl23 ^^
 Mouxon: try emailing the Lubuntu-users list
[15:31] <Mouxon> Ok, thanks tsimonq2
[16:39] <wxl> Mouxon: still around?
[17:26] <Mouxon> Yes
[17:27] <wxl> what about gtk3-demo? same issue?\
[17:28] <Mouxon> Yes
[17:29] <wxl> k i'm going to explore more. your mailing list message will remind me to do so :)
[17:29] <Mouxon> I watched to dbus-monitor but I don't understand the output :D
[17:29] <wxl> you can include that in the message
[17:30] <Mouxon>  What is the mailing list email ?
[17:30] <wxl><EMAIL_ADDRESS>[17:30] <Mouxon> Thanks


[00:30] <Unit193> Well I know, but I can't tell him now..
[00:46] <knome> Unit193, tell who?
[00:52] <Unit193> I had a ping.
[10:09] <dkessel> Good morning.
[10:11] <dkessel> Has anybody else gotten two battery indicators? I have the unity power indicator plus xfce4-power-manager. This did not happen on Friday...
[10:13] <brainwash> dkessel: hey, the power manager one should be hidden
[10:15] <brainwash> but I think that the updated xubuntu-default-settings package still needs to be uploaded
[10:15] <dkessel> brainwash: ok , that should change it?
[10:20] <brainwash> I hope so
[10:21] <dkessel> I'll keep an eye on it
[10:23] <brainwash> bluesabre0: why did you remove xubuntu-default-settings from the affects list? bug 1281323
[10:35] <brainwash> dkessel: you can check bug 1295864 for status updates
[10:36] <elfy> brainwash: appears that the odd deleting bug I had has gone
[10:38] <brainwash> elfy: mark it as incomplete and remove it from the -bugs blueprint?
[10:38] <elfy> not yet - it only appears to have gone :)
[10:39] <knome> anybody can come up with a reason why we need https://launchpad.net/xubuntu-desktop
[10:39] <knome> it doesn't have bugs traker, support issues tracked, translations tracker, branches specified, it has no announcements, it specifies no exact license...
[10:39] <knome> it basically only points people to the home page, wiki, screenshots and the downloads page
[10:40] <elfy> ask cody somerville why he set it up?
[10:40] <brainwash> I like that page
[10:40] <elfy> certainly appears to be a nothingness
[10:41] <knome> it appears to be user-facing communication in a developer platform
[10:41] <knome> ...which can be good
[10:41] <knome> but not if it says the development focus is natty series
[10:41] <knome> brainwash, why do you specifically like that page?
[10:42] <brainwash> it's like a minimal version of the actual xubuntu homepage
[10:43] <knome> like, a very minimal
[10:43] <brainwash> with informative text and links
[10:43] <knome> it only has the description text that can be useful
[10:43] <knome> and the links
[10:43] <knome> the rest of the page is useless information
[10:43] <knome> which can most definitely confuse people
[10:44] <brainwash> other flavors don't have this page (-desktop)
[10:44] <knome> apparently it is the "upstream" project for xubuntu-meta and xubuntu-system-tools packages
[10:44] <knome> but that's not a useful thing
[10:45] <elfy> don't tell ali then - or there will be 500 u-gnome ones by the end of the day :p
[10:51] <brainwash> xubuntu-system-tools? o.o
[10:52] <knome_> 12:46  knome: yeah, i don't know
[10:52] <knome_> some ancient package from 2009 i guess
[10:53] <brainwash> so no one will miss that page
[10:53] <brainwash> if it is redundant
[10:53] <knome> if not else, i'm cleaning it up now
[10:54] <knome> "top contributors"
[10:54] <knome> ehh....
[10:54] <knome> who *is* jeb. e? :)
[10:54] <knome> or petar sredojevic?
[10:54] <knome> i know who gunnar is, but he's not involved with xubuntu
[10:59] <knome> mhm, xubuntu-meta is actually at lp:ubuntu/xubuntu-meta
[10:59] <knome> the page is a bit cleaner now
[11:00] <knome> will continue investigations later
[11:07] <bluesabre0> brainwash: poke
[11:07] <brainwash> bluesabre0: hey
[11:08] <bluesabre0> hey, I removed it from affecting xubuntu because we fixed it in xubuntu
[11:08] <bluesabre0> we removed light-locker from autostart by shipping an empty autostart entry on live
[11:09] <brainwash> why not leave it there and change the status to "fix released"?
[11:09] <brainwash> yes, the lubuntu guys need the exact same fix
[11:10] <knome> can agree marking as "fix released" would be better than marking unaffected ;)
[11:10] <bluesabre0> good question, I feel like I had a good reason back then :\
[11:12] <bluesabre0> maybe because the issue was with xubuntu-live-settings or something
[11:12] <knome> bluesabre0, retarget?
[11:12] <bluesabre0> yeah, I'll do so now
[11:12] <knome> Unit193, do we still try to get the translator attribution in for trusty, or should we postpone it for a point release?
[11:13] <knome> Unit193, looks like there are other things for that as well, so...
[11:13] <brainwash> bluesabre0: -default-settings builds -live-settings
[11:13]  * bluesabre0 doesn't like those packages
[11:14] <bluesabre0> xubuntu-meta -> xubuntu-default-settings -> xubuntu-live-settings
[11:15] <knome> :P
[11:15] <knome> guests coming any minute now, bbl
[11:16] <bluesabre0> there
[11:41] <brainwash> dkessel: I've checked again and the change already has landed in trusty, but it won't take effect if you have a custom power manager config file
[11:42] <dkessel> brainwash: oh OK that might have been the case.
[11:42] <brainwash> ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml
[11:42] <dkessel> bbl lunch...
[11:42] <brainwash> rename the config file and restart the session
[11:42] <brainwash> ok
[13:51] <dkessel> Yup, that worked
[13:53] <brainwash> dkessel: thanks for testing, sadly this little problem will affect users who upgrade from a previous release
[13:54] <brainwash> not all of them, but the ones who already have a user config file for the power-manager (which overrides the global config)
[14:00] <dkessel> brainwash: what was the general idea here? To replace xfce's power manager icon with the ubuntu default? Is there no way of globally disabling xfce's pm on upgrade? Or is it still required for something?
[14:02] <brainwash> dkessel: xfce4-power-manager is still running in the background, but we decided to use unity's indicator instead (which now also opens xfpm if running)
[14:04] <brainwash> and xfpm checks for a user config file first
[14:04] <brainwash> but we can only adjust the global config file
[14:04] <dkessel> Ah OK... So we only switched that part of the UI. Hm patch xfpm to not start the tray icon anymore if indicator-power is installed?
[14:05] <brainwash> adding some hack to xfpm could resolve this
[14:06] <brainwash> file a bug report and maybe we'll address this issue
[14:08] <brainwash> however, the problem is that hacks are usually not easily accepted
[14:09] <brainwash> and altering files in the user folder via the package install routine is a no-go too
[14:53] <pleia2> 95 xubuntu-devel moderator request(s) waiting
[14:53] <pleia2> gah
[14:53] <pleia2> usually there are like.. 2
[14:58] <elfy> ...
[14:58] <elfy> I'll turn off thunderbird then :p
[14:59] <elfy> the fc list gets about 40 a week
[15:30] <ochosi> hey everyone
[15:33] <brainwash> ochosi: hello
[15:34] <elfy> hi ochosi
[15:45] <brainwash> elfy: any news regarding the ibus keyboard layout mess?
[15:46] <brainwash> telling people to simply delete ibus is a bad solution
[15:46] <elfy> only that it seems to be a regression
[15:46] <brainwash> so there is hope for a fix :)
[15:46] <elfy> I know it is not a good solution - but then installing something that breaks this isn't good either :p
[15:46] <elfy> I hope so brainwash
[15:49] <ochosi> yeah, i'm wondering whether we should consider dropping it form our seed...
[15:50] <elfy> ochosi: mmm - trouble is can we add it back when it's fixed?
[15:50] <elfy> I don't know the answer to that
[15:50] <ochosi> i dunno whether it's really needed by default
[15:50] <brainwash> only problem is, many people rely on it
[15:50] <ochosi> i've personally never used this (this doesn't mean it's not needed, but that i don't know)
[15:51] <elfy> brainwash: then they'd want one that's not broken :)
[15:52] <brainwash> it's not broken if you configure it, or?
[15:52] <ochosi> has anyone gotten in touch with the ibus maintainers?
[15:52] <elfy> ochosi: I've not
[15:52] <elfy> brainwash: why should you have to configure it?
[15:53] <elfy> in my opinion - I set up the system when I install with a suitable keyboard layout - I shouldn't have to do anymore than that
[15:53] <brainwash> I mean if you need to switch between different kb layouts, you could configure it, so that it works
[15:54] <ochosi> yeah, but there are alternatives to that
[15:54] <brainwash> so we should deactivate the autostart entry
[15:54] <ochosi> e.g. the xfce4-keyboard-plugin
[15:54] <brainwash> yes
[15:54] <ochosi> yeah, deactivating the autostart entry would be a workaround i could live with
[15:54] <ochosi> but in the long run it'd be nice to re-consider whether we really need it on a default install
[15:54] <brainwash> does the panel plugin allow switching via kb shortcut?
[15:55] <ochosi> or whether there are even better solutions for it
[15:55] <ochosi> yeah, i think you can set it up to do that
[15:55] <ochosi> to the worst you can bind an xfconf-query command ;)
[15:55] <ochosi> (also: is this a functionality you consider essential to layout-switching?)
[15:56] <brainwash> yes
[15:56] <brainwash> switching via kb shortcut is widely used
[15:56] <brainwash> when chatting for example
[15:57] <ochosi> what do you base that "widely used" on? :)
[15:57] <brainwash> just my observations
[15:57] <brainwash> asian people for example
[15:58] <brainwash> or russian ones
[15:58] <ochosi> could you point these folks to translating light-locker?
[15:58] <brainwash> :D
[15:59] <brainwash> light-locker needs translation?
[15:59] <ochosi> yup
[15:59] <ochosi> and chinese and russian are still not complete/up-to-date
[15:59] <brainwash> ah, the lock screen
[15:59] <brainwash> with the big lock icon
[15:59] <ochosi> nah, it's more than that
[15:59] <ochosi> commandline-options etc
[15:59] <ochosi> ~12strings
[16:00] <brainwash> we could use google translate
[16:01] <ochosi> no
[16:01] <ochosi> that just creates a mess
[16:02] <brainwash> sadly I don't know anyone I could ask
[16:03] <ochosi> so who are those misterious asians and russians you quoted earlier? :)
[16:04] <brainwash> gaming related, so they don't actually use ubuntu
[16:06] <brainwash> what about asking in the local ubuntu channels, like #ubuntu-ru ?
[16:06] <elfy> ochosi: I could live with us deactivating autostart for it
[17:47] <ochosi> micahg: reminder about the merge-requests
[17:57] <ochosi> knome: what do you thnk about disabling ibus autostart by default in 14.04? from what i can tell it seems to have a regression (changes kb-layout on login) that causes the bug elfy reported a longer while ago already
[17:57] <ochosi> i'm mostly asking cause this would most likely also go in x-d-s
[17:58] <ochosi> (i guess elfy can tell you more about it if necessary as i'm running out now)
[19:37] <starrats> hello folks I just sent in another bug report, didn't want too but this one warranted it.  Problems with start up cursor is still freezing at password window, it's been real good for me until gthe last two days and all of a sudden it is freezing again. the cursor.
[19:48] <brainwash> starrats: hey
[19:48] <brainwash> little 'lightdm' window?
[19:49] <brainwash> you mean the login box on the login screen, correct?
[19:50] <starrats> yes the logon /password window
[19:50] <starrats> not the little 'lightdm' window
[19:50] <starrats> sorry
[19:51] <brainwash> does the keyboard also stop responding?
[19:51] <starrats> yes
[19:51] <brainwash> can you switch to a virtual console (ctrl + alt + F1)?
[19:52] <starrats> I move my finger on the touchpad/mousepad and sometimes I have a 'free' cursor and sometimes nothing and no keys will operate to unfreeze the cursor
[19:52] <starrats> never tried that combo of keys
[19:53] <brainwash> you can switch back with ctrl + alt + F7
[19:53] <starrats> did not know that combo of keys
[19:54] <brainwash> it is a simple test to check, if the whole system is frozen
[19:54] <starrats> ah okay next time I'll try these two combo's
[19:56] <starrats> thanks brainwash
[19:56] <starrats> if the system is frozen?
[19:56] <starrats> hard crash/ turn off
[19:56] <starrats> I mean hard shutdown
[19:59] <brainwash> starrats: try to reboot your system in a cleaner way, see http://fosswire.com/post/2007/09/fix-a-frozen-system-with-the-magic-sysrq-keys/
[20:06] <starrats> thank you brainwash, I know a hardshut down is not good.  i read and copied the info concerning alt + SYSRQ keys and then typing in REISUB, question does that have to be in caps?
[20:07] <starrats> the reason I ask is that the link you shared showed that 'word' in caps.
[20:08] <brainwash> no caps needed
[20:08] <starrats> ah okay cool
[20:09] <brainwash> you can also skip the first 3 letter, because they are ignored on ubuntu systems
[20:09] <brainwash> but that's not important
[20:09] <starrats> so just sub?
[20:09] <brainwash> nah, use reisub
[20:09] <starrats> ah okay
[20:10] <starrats> thank you again for all your help
[20:10] <brainwash> you're welcome
[20:11] <brainwash> one more thing, you should attach log files to your report
[20:11] <starrats> log files in the bug report?
[20:12] <brainwash> yes, for example /var/log/syslog and /var/log/Xorg.0.log + /var/log/Xorg.0.log.old
[20:12] <starrats> ah okay
[20:13] <brainwash> after your system has frozen again and you have performed a reboot
[20:14] <starrats> those didn't 'pop-up on term when I was finally able to type my password to get on I went to the term and typed in 'ubuntu'bug' and prceeded from there.
[20:14] <starrats> ah okay
[20:16] <starrats> though when i did type in 'ubuntu-bug in term I did get an output that startedcv with WARNING...
[20:16] <brainwash> so your frozen system recovers without reboot?
[20:17] <starrats> no I do the hard shutdown and try to logon on again, that was 4 times today, I hate hard shutdowns
[20:17] <starrats> to reboot
[20:17] <brainwash> alright
[20:17] <starrats> the 4 times were back to back
[21:41] <olbi> hi guys, why daily iso doesnt have actually lang files from launchpad? and why translation from transifex isn't updated for Xfce? :/
[21:42] <olbi> I want to check and fix this but can't :/
[21:42] <knome> for which package specifically?
[21:42] <olbi> xubuntu installer slideshow
[21:43] <knome> that's pending a new release
[21:43] <knome> translations will land on the non-language-pack freeze day at latest
[21:43] <knome> for what comes to transifex... i doubt there are automatical imports
[21:45] <olbi> that isn't cause I do changes 7 days ago and it doesn't go to update files in 14.04, for example Thunar 1.6.3
[21:45] <knome> it is...
[21:46] <knome> translations made in launchpad or transifex do not magically get moved to the archive
[21:46] <knome> the bzr branches in launchpad are updated automatically, but packages aren't build from them automatically
[23:33] <ochosi> hm, we should still set some sane defaults for the X11 screensaver timeouts in xubuntu...
[23:33] <ochosi> (currently 10mins)
[23:34] <brainwash> 10mins is not sane?
[23:35] <ochosi> seems a bit short
[23:35] <ochosi> well otoh now that we have l-l-s by default it's easily configurable
[23:35] <brainwash> but it's the widely used default value
[23:35] <ochosi> so less of a headache
[23:35] <brainwash> exactly


[05:37] <omairqazi> hi
[05:38] <omairqazi> there is a problem in lubuntu 18.04
 @vaibhavsingh, o/
 have you guys seen this?
[11:44] <Guest64987> Hey, guys. I've noticed that the magnet link for the LTS version if for the 14.04.2 instead of 14.04.3, which is the release that is displayed on the download page
[11:44] <Guest64987> *is for the 14.04.2
 @Guest64987, What architecture? If it's wrong i must fix it 😏
 Some 14.04.3 ISOs are not available, only 14.04.2
 But I'll have a look. Thanks for noticing.
 All links seem fine to me. Can you, please, point which one you think is wrong?
 @VikingRedwolf Ooh, he could be talking about Lubuntu.net
 LOL
[12:55] <redwolf> he's offline anyways
[16:08] <wxl> m4sk1n: what did you do to make things so darn pretty? :) https://i.m4sk.in/image/Z9U
[16:11] <m4sk1n> wxl: just adapta theme, paper icons, roboto font and default compton configuration
[16:11] <wxl> cuz that's pretty
[16:12] <wxl> @VikingRedwolf ^^^ look at what m4sk1n did
[16:12] <wxl> i like the wallpaper a lot, too. reminds me of recent kubuntu stuff.
[16:13] <m4sk1n> it’s generic material design wallpaper from adapta-backgrounds
 Meh
 Not a fan of material design personally :)
 I see, wxl. but I see some problems there:
[16:27] <wxl> well, *I* think it's pretty so blah
 It seems flat themes are "the thing" right now
 Right. It's a trendy thing. In a few years, or even months, we'll see an old screenshot and we'll say "eeewwww"
 Look at this:
 (Document) http://vps.tsimonq2.net:8080//file_3302.gif
 Flat enough, isn't it? It's olvwm, one of the best window managers ever invented. It's 20 years old.
 for sure, i remember that time where all the screenshots or videos was full of ultra conkys, cube 3D, tron decorations with flames woobly windows and moving icons.
 Right XD
 That gtk1 with wooden texture
[17:14] <wxl> new designs are often easily appreciated, but whether or not they'll stand the test of time is the question
 @Wolfenprey, I still love Tron :|
 i like something balanced, all functionality
 @VikingRedwolf, (me too... but ssshhh)
[17:15] <wxl> do not be embarassed about tron
[17:15] <wxl> now if you're going to tell me you like the look of STTNG GUIs, i'm going to freaking hit you.
 @wxl, well, first i have to know what is, XD
[17:19] <wxl> @Wolfenprey http://www.forestfriend.ca/wp-content/uploads/2012/02/ingr_lcars_sovereign.jpg
[17:20] <wxl> the colors alone make me homicidal
 too much for my senses...
[17:20] <wxl> here's an actual screenshot from the show when they first installed it http://a.fastcompany.net/multisite_files/fastcompany/imagecache/1280/poster/2013/12/3022935-poster-1280-trek.jpg
 XD
[17:21] <wxl> you laugh but i have seen COUNTLESS themes created based on it
 urgh...
[18:20] <m4sk1n> @VikingRedwolf this background isn’t from google, it’s by author of this theme
[18:20] <m4sk1n> but almost every material design wallpaper looks the sams
[18:20] <m4sk1n> s/sams/same/
[18:23] <m4sk1n> XD
 @m4sk1n, It reminds me a sort of mixture between android with Manjaro colors wallpaper.
[18:29] <m4sk1n> It was just my temporary config for vm… :P
 @wxl, I LIKE IT
 .___.
 ...
 i prefer the olvwm look
 :)
 the maximum functionality, speed and performance was, in my opinion, WindowMaker
 1 square = 1 app. perdiod.
 https://3.bp.blogspot.com/-uWpN-R2AEWQ/VUnqCnVlkQI/AAAAAAAAAZQ/Xz2cnK88AWg/s1600/Screenshot%2Bfrom%2B2015-05-01%2B14%3A43%3A50.png
 they called it... """DOCK"""
 .__.
 lol
 but for sure it works
 and dont need a NASA COMPUTER for move a window
 exactly. shadows? naah. composition? naah. effects? naaaaah
 but still I managed to make the Lubuntu compositor to work on WindowMaker. it looked awesome
 i remember i used openbox a lot , cant remember the distro
[19:42] <wxl> ARE YOU GUYS TALKING ABOUT NUHBUNTU????
 also, starting GIMP in WM was like... instant, telepathic
 0.00001 seconds
 @VikingRedwolf, mmm al that on a SSD
 @wxl, NUH!
[19:43] <wxl> XD
 @Wolfenprey, stop!   What have you discovered?
[22:44] <tsimonq2> Ooooooooooooh
[22:44] <tsimonq2> @Schyken ^^^^^^
[22:50] <tsimonq2> wxl: What's your opinion on people failing ISO QA tests because instructions are slightly incorrect?
[22:50] <tsimonq2> wxl: http://iso.qa.ubuntu.com/qatracker/milestones/384/builds/163656/testcases/1689/results for ref
[22:52] <wxl> what do you think my opinion is?
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> T[M
[23:35] <tsimonq2> T[M
[23:35] <tsimonq2> T[M T[M
[23:35] <tsimonq2> T[M
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> U[M
[23:35] <tsimonq2> UGH
[23:35] <tsimonq2> Sorry everyone...
 GUYS - I KNOW WHY I COULD USE UEFI
 So, I've been looking into this Meltdown thing, and ofc checking my CPUs, things like that... My BIOS/UEFI locks LegacyOPROM into an enabled state, even when explicitly told to be disabled.
 Looks like there's an update available for it since October :/
[23:41] <wxl> not exactly. they've been working on it since about october
[23:42] <wxl> here's the announcement for the Linux that includes the fix https://lwn.net/Articles/742449/
 Oh great 😢
[23:43] <wxl> About half the rc6
[23:43] <wxl> work is x86 updates.
[23:43] <wxl> ^^^
[23:43] <wxl> by x86 he means KPTI
 @Alon Ganon, Try browsing through here: https://www.debian.org/doc/packaging-manuals/python-policy/
[23:44] <wxl> you could also try making a snap out of it
[23:44] <wxl> or a flatpak
[23:45] <tsimonq2> Or an AppImage
[23:45] <wxl> oh! you mean a klik!
[23:45] <wxl> you only like that because it's developed by a guy named simon.
[23:47] <tsimonq2> Meh


[23:01] <kendell> I'm a visually impaired user of ubuntu mate 24.04. It is my favorite linux distribution. I'm having a lot of trouble pushing to a git repository of fixes I have created for the espeak-ng speech synthesizer. Git keeps asking me for user name and password but keeps telling me it's the wrong password when it isn't. I have ssh set up, but can't seem to figure out how to use it. Can anyone help?
[23:02] <kendell> I have the following options configured. git configure -global user.name "kendell clark" git config -global user.email<EMAIL_ADDRESS>and still it asks me for authentication. I'm confused.
[23:02] <superkuh> You might have more luck in #git
[23:03] <kendell> I'll try there too.
[23:06] <kendell> just wanted to let everyone know how impressed I am by how accessible ubuntu mate is out of the box. Right off orca comes up and speaks and the installer is accessible. That is not common among linux distros
[23:06] <oerheks> kendell, setup ssh properly too, https://cis106.com/guides/Ubuntu%20Github%20Setup/
[23:50] <kendell> git channel was very helpful thanks. Still love ubuntu mate, so I'll hang out here and try to be helpful. Having issues getting my bluetooth headset to repeatedly pair once paired the first time, the error is a bit cryptic
[23:52] <kendell> the error I get most often is br connection unknown, connection failed. Forgetting and readding it works, once, but fails on subsequent connections
[23:53] <superkuh> What voices do you use with espeak? I prefer niitech HTS voices (nitech_us_awb_arctic_hts) in festival 1.96. It's still a bit robotic but better than anything espeak I've tried and incomparably faster and less resources than neural network speech synth.
[23:54] <superkuh> piper tts would be okay except for the weird noises it makes at the end of utterances.
[23:56] <kendell> I use the max varient with espeak and ibm tts on occasion. Festival I never could get to work well but I never tried thta hard to use it
[23:56] <kendell> I'm getting to where I actually dislike how ibm tts sounds despite the good pronunciation
[23:59] <superkuh> I know what you mean. After a decade of listening to this festival robo voice I almost prefer it too good enunciation.


[08:01] <huats> morning
[13:12] <aday> mgunes, andreasn: hey, meeting time?
[13:13] <godbyk> aday: I assume so. Though it appears that our fearless leader is absent.
[13:14] <aday> godbyk: it would seem so
[13:14] <aday> wers, vish: yo, you here?!
[13:14] <mgunes> and without him and an agenda we're destined for an aimless hour of chit-chat as usual :)
[13:15] <wers-android> I'm having dinner. hehe. wait
[13:15] <vish> yup for a few mins :)
[13:15] <mgunes> aday, your last blog post was a nice summary of design happenings in GNOME; it would be useful if you were to make it periodical, perhaps with some help from us and/or others.
[13:16] <aday> mgunes: that's what's happening. we're going to rotate each week
[13:16] <aday> hbons is supposed to be doing it this week
[13:17] <aday> there's tonnes of design work happening in gnome right now
[13:17] <mgunes> good to know.
[13:18] <aday> the report seems to have gone down well, anyway
[13:27] <aday> anything worth discussing now?
[13:27] <mgunes> aday, I take it that http://live.gnome.org/UsabilityProject/HIG3/ is where the latest HIG-related things go on, correct?
[13:28] <aday> mgunes: that's right. bit quiet at the moment... i need more hours in the day
[13:28] <mgunes> I'm a bit puzzled as to what exactly "porting" an old HIG guideline involves. Could you expand on that a bit?
[13:29] <aday> mgunes: the new hig is a set of ui patterns, which have a template for
[13:29] <aday> porting means pulling out a ui pattern from the existing guidelines, structuring it around the template, and updating where necessary
[13:29] <wers-android> nice. i just thought. does kde have ui patterns?
[13:29] <wers-android> maybe, we can work together. just maybe
[13:30] <aday> some patterns are just sections from the current hig. some have to be pieced together from a few different places
[13:31] <aday> wers-android: there are some links here - http://live.gnome.org/User%20Interface%20Patterns . don't think kde use patterns as such
[13:31] <aday> we really need help with the new hig though - any assistance would be appreciated
[13:34] <wers> yep. that's very important
[13:34] <mgunes> aday, so right now it involves literally lifting existing pieces of the old guidelines and fitting them in the new template; whether the actual content is to change and to what extent is to be discussed and approved later
[13:35] <wers> aday, is this the latest http://library.gnome.org/devel/hig-book/nightly/ ?
[13:36] <aday> mgunes: yes, that's some of it. there are going to be new patterns too of course
[13:36] <mgunes> right
[13:36] <aday> wers: i guess. don't think it's changed that much. i just use the stable version
[13:37] <aday> mpt wrote a new pattern on handling errors that's really good - http://live.gnome.org/UsabilityProject/HIG3/HandlingErrors
[13:38] <wers> aday, I'm not familiar with the work required for the HIG other than the UI Patterns. is there more to it than what mgunes mentioned?
[13:39] <aday> wers: not really. it's pretty straightforward. we have the template, new patterns to write and existing ones to port and update
[13:39] <mgunes> and GtkBuilder files and sample source code to provide (which is particularly a strength of the new HIG)
[13:40] <aday> mgunes: in time, yes
[13:41] <mgunes> aday, I read mpt's pattern; it doesn't seem to conform to the template though
[13:42] <aday> mgunes: no :P
[13:42] <aday> mgunes: we're still playing with the format. we'll have to review at some point soon
[13:42] <aday> the template is a bit overcomplex imo
[13:45] <mgunes> aday, I assume most of the work goes on in #gnome-design, right?
[13:47] <aday> mgunes: indeed
[13:48] <mgunes> I'm hoping to set aside some time in the coming weeks for HIG work
[13:50] <aday> mgunes: that would be so awesome
[14:02] <thorwil> aday: one issue i see is that most there looks like guidelines, not patterns
[14:02] <aday> thorwil: in the HIG3 stuff? yeah, there's a bit of both
[14:03] <thorwil> a pattern should be more concrete and might include a selection and layout of widgets
[14:04] <aday> thorwil: where is that not happening?
[14:05] <thorwil> aday: the handling errors thing? sorry, real life interferes, bbl
[14:06] <mgunes> thorwil, I assume they will be closer to patterns once more of them have GtkBuilder examples and sample code
[14:07] <mgunes> I recall the first few ones Calum Benson worked on had both
[14:08] <aday> i agree about the handling errors page not being very pattern-like. maybe some of it could be disaggregated into other patterns? we still want the central message - that's useful, i think
[14:24] <thorwil> it would be fine to have both a more abstract guidelines part and a pattern library.
[17:35] <Jaikyee> hola, cuando hay reu de nosotros... un evento donde nos reunamos?
[17:36] <czajkowski> !es | Jaikyee
[17:37] <Jaikyee> aloooo
[21:23] <Tito__> Los invito a visitar mi blog donde publico tutoriales que pueden llegar a ser útiles la página es http://titoubuntu.blogspot.com/
[21:24] <czajkowski> !es | Tito__
[21:26] <Tito__> ok gracias


[10:49] <freeflying> Riddell-> ping
[10:50] <freeflying> Riddell-> today's dapper-install-i386.iso can not install to HDD
[11:37] <jpatrick> morning raphink
[11:37] <raphink> morning jpatrick
[11:38] <jpatrick> new upstream release for kcontrol-autostart :)
[11:56] <jpatrick> Riddell: ping - applied kubuntu_01_kdepot.diff to kcontrol-kdmtheme -> http://revu.tauware.de/details.py?upid=1281
[12:05] <Riddell> freeflying_: what's up with todays?
[12:05] <Riddell> jpatrick: cool
[12:05] <freeflying_> like yestoday's
[12:05] <Riddell> will try and find time for revu today
[12:06] <Riddell> freeflying_: yeah :(
[12:06] <freeflying_> Riddell: will you have a try of today's
[02:07] <jjesse> hmm installing dapper flight 2 cd thru qemu and it is taking forever at "perparing to configure oopenoffice.org2-kde"
[02:08] <jjesse> what exactly takes place at this step?
[02:16] <jjesse> should it take an hour+ to take care of this step?
[02:25] <apokryphos> jjesse: definitely not; sounds like a bug
[02:25] <Riddell> jjesse: no, although qemu is exceedingly slow at times
[02:28] <jjesse> i can get the live cd to work fine, was just trying on an install
[02:29] <jjesse> is there a way i can sync my flight2 iso to the daily build or something like that and try it again?
[02:30] <Riddell> yes, see KubuntuFiles for rsync
[02:30] <Riddell> but today's probably won't work, so don't
[02:32] <jjesse> ok
[02:33] <jjesse> should i create a bug on it or chalk it up to problems w/ qemu?
[02:33] <jjesse> tried on a breezy box and windows xp pro box and it hangs at configuring openoffice
[02:35] <Riddell> you could create a bug
[02:35] <Riddell> not sure if anyone would pay attention
[02:43] <jjesse> Riddell: did you have a chacne to look at what i have so far in releasenotes?
[02:45] <Riddell> jjesse: eek, no
[02:45] <Riddell> quite forgot
[02:45] <jjesse> Riddell: no worries, wiill get to desktopguide while im at in-laws
[02:46] <jjesse> https://docteam.ubuntu.com/repos/trunk/kubuntu/releasenotes/C/releasenotes.xml
[02:47] <Riddell> "Kubuntu 5.10 Breezy Badger"  that needs changed :)
[02:47] <jjesse> doh
[02:48] <jjesse> where do you see that?
[02:48] <Riddell> " Kubuntu also provieds security updates for 18 months after each releasea"  this is a long supported release so that should be changed to 3/5 years
[02:48] <Riddell> jjesse: in the html made from  make release-notes-web
[02:48] <jjesse> hmmm
[02:48] <Riddell> hmm, I wonder where that comes from
Kubuntu &kdistro-version; &kdistro-rev;</subtitle>
[02:49] <Riddell> that'll be it
[02:50] <Riddell> Pre-Upgrade section should be changed to use adept
[02:51] <Riddell> FireFox 1.5 isn't on the CD so it should be mentioned as a note at the bottom of the "On the Desktop" section
[02:52] <Riddell> note that as a long term supported release we're focusing on fixing things not new features
[02:52] <jjesse> even though i mention firefox 1.5 is a release canditate?
[02:52] <Riddell> otherwise looking lovely :)
[02:53] <Riddell> well firefox isn't a kubuntu feature so it shouldn't be given the same prominance in the text
[02:54] <jjesse> ok
[02:55] <jjesse> can i ask why when i build the web it goes to trunk/kbuntu/build/kubuntu/release-notes-web isntead of repos/trunk/build/ like the other docs go?
[02:57] <jjesse> also will there be a KubuntuDapperKnownProblems created like the KubuntuBreezyKnownProblems ?
[02:59] <Riddell> yes there will be
[02:59] <Riddell> feel free to start it off
[03:00] <allee> jjesse: relnotes:  typo releasea
[03:08] <jjesse> Riddell: saw it myslef and already changed it
[03:09] <jjesse> Riddell: relnotes: another section i'm changing  "Installer Kubuntu" doesn't sound right, should be installing Kubuntu
[03:09] <Riddell> yes
[03:10] <allee> jjesse: IMHO s/!!!!/!/
[03:10] <allee> jjesse: wiki and bugzilla links  https: instead of http:
[03:10] <jjesse> ok
[03:12] <Riddell> allee: certificates?
[03:12] <allee> jjesse: Dapper Drake is first mention in Update section.  A bit too late?
[03:15] <allee> Riddell: the browswers 'complain' that the issuer is unknown
[03:15] <Riddell> allee: well it's self signed so they would :)
[03:16] <Riddell> there was a plan to include cacert in the trusted issuers but I don't know if I trust cacert that well
[03:17] <allee> Riddell: really.  Tried lauchpad.  Signed by Thwate.  Don't we trust then since sablf isn't the owner?
[03:17] <Riddell> exactly :)
[03:17] <allee> :)
[03:18] <jjesse> allee: i thought at one time there was going to be a change on going by the numbers instead of the name
[03:18] <jjesse> so 6.04 i think the # is mentioned more
[03:18] <Riddell> we are trying to move towards numbers more
[03:18] <Riddell> people loose track of names
[03:18] <allee> jjesse: just stay consistent (IMHO) either codename or version or both ;)
[03:18] <Riddell> although nobody understand the numbering system either
[03:22] <allee> jjesse: post-upgrade: there will be a new X11 + KDE.  So why don't we suggest to dist-upgrade on console and then /etc/init.d/kdm restart?
[03:22] <allee> pre-upgrade would be alt-ctrl-f1, login, sudo /etc/init.d/kdm stop ...
[03:23] <jjesse> not upgrade through adept?
[03:24] <freeflying_> Riddell: have you coreect th installing error ?
[03:25] <Riddell> freeflying_: it's not mine to correct, it needs someone to promote some packages to main I think, and the people who do that are on holiday
[03:25] <allee> jjesse: good question.  In the past some kde apps crashed on logout after kde.  So _I_ switched to konsole.  But I have not tried a breezy->dapper upgrade in failsafe + adept!
[03:26] <jjesse> allee: i've done an upgrade in adept in normal mode and just restarted X w/o problems
[03:26] <allee> after kde upgrade that is
[03:27] <freeflying_> Riddell:  How to solve the kde error of mine ?
[03:27] <allee> jjesse: how did you restart X11 the usual alt-ctrl-backspace  (sound like windoof alt-control-del.  may awake bad memories ;)
[03:28] <jjesse> allee: yeah through the alt-ctrl-backspace
[03:29] <Riddell> freeflying_: reinstall from flight-2 maybe?
[03:30] <allee> jjesse: I usually use init.d/kdm restart, so new kdm is running too.  But let's stick which what is in relnotes and try how it works with flight 3
[03:30] <jjesse> allee: ok
[03:30] <jjesse> allee: did you get flight2 to run for qemu?
[03:31] <freeflying_> Riddell: fault of flight-2 have been fixed?
[03:32] <jjesse> afk meeting
[03:32] <allee> jjesse: didn't try.  First I want breezy, sarge, sid(for backports & tests & bug verification) flight2 runs without emulation here ;)
[03:33] <jjesse> allee: i didn't want to mess up my work laptop w/ dapper just in case and can't get past configuring openofficeorg-kde
[03:35] <allee> jjesse: I know what you mean ;)  I want into holidays, started the laptop and libcapi was broken -> no internet (no library in pkg ;)  Luckyly apt-proxy had the old version
[03:42] <allee> jjesse: changed apps section add a placeholder so adept/amarok/kopete are not forgoten later, mhmm IMHO listing just some highlights of KDE 3.5 visual guide can't hurt (just to make it more impressive, than just the reference to visual guide))
[04:58] <Riddell> jpatrick: kdepot patch on 1281 fails
[04:59] <Riddell> ok, I'm away for holidays
[05:03] <jpatrick> it's 1285
[08:28] <jjesse> burgwork do you know what time zone jerome is in?


[08:05] <xubuntu56w> Hi! MenuLibre in Xubuntu 19.04 doesn't work. See the bug here: https://bugs.launchpad.net/menulibre/+bug/1826069. Please fix the bug. Thanks.
[08:31] <knome> i thought he said xubuntu, but the bug says pop!_os... hmm...
[08:32] <Unit193> Pop is system76's version of Ubuntu, I thought?
[08:33] <Unit193> So, if it is 19.04 it'd make sense for it to hit both.
[08:33] <knome> i didn't know we were supporting any kind of derivatives here, thoguh
[08:33] <knome> or anywhere :P
[08:52] <Unit193> Menulibre is elsewhere, if the problem is first found elsewhere then reported, that's what may turn up in searches.  Said user could be using Xubuntu, found the bug, that's the one that they hit.  No?
[08:55] <knome> suure...
[08:56] <Unit193> ...This is all long moot though.
[08:57] <knome> yep :P
[14:01] <nokiomanz> Hi all, Question about screen resolution. I have a mini desktop connected to my 4k TV. I set my xubuntu to 1080p. But when I close the television and open it for instance the next day or a few hours later. The desktop switch to 4k resolution. How to make it stick to 1080p?
[14:12] <pmjdebruijn> nokiomanz: is "configure new displays when connected" unchecked?
[14:15] <nokiomanz> pmjdebruijn, I would say it is probably at default value. I am on my laptop right now which run the same xubuntu version(18.04) and it is unchecked. I am not at home to go check that particular desktop right now. But I would believe it is also uncheck.
[14:20] <nokiomanz> It is as if when I open the television, the destop sees it as a new display and try to match default resolution. Would that make sense?
[14:35] <pmjdebruijn> yeah, that would be my guess too
[14:36] <pmjdebruijn> I don't have that much experience with TV screens connected to desktops
[14:36] <pmjdebruijn> i vaguely recall that the HDMI modes are a tad different
[14:36] <pmjdebruijn> but I might be mistaken
[14:38] <pmjdebruijn> http://ubuntuhandbook.org/index.php/2017/04/custom-screen-resolution-ubuntu-desktop/
[14:38] <pmjdebruijn> https://wiki.archlinux.org/index.php/xrandr#Adding_undetected_resolutions
[14:38] <pmjdebruijn> those pages might offers some help
[14:38] <pmjdebruijn> though it seems a bit hacky to use xrandr directly
[14:38] <pmjdebruijn> but it might turn out to at least provide a get-you-by solution
[14:39] <pmjdebruijn> and/or stick around for someone more knowledgable to help
[15:00] <nokiomanz> pmjdebruijn, Thanks for your time. I will try to see for a more "easy" solution. If it was just me it is one thing. The kids are using that setup too and they are too young ahah.
[15:01] <friendlyGoat> any of ya'll know about rsync cause im having a problem with it and im not sure if its cause im stupid or not
[15:01] <friendlyGoat> im trying to write out a path with spaces and an apostrophe but nothings working
[15:03] <friendlyGoat> its host@ip address:/home/pi/SERVER/Jonah's Stuff/Note Backups/ and im at a loss as to what to do since no matter what i do it just goes down to a > line or causes and error or puts it in a new folder i didnt want
[15:04] <diogenes_> friendlyGoat, rsync "/home/pi/SERVER/Jonah's Stuff/Note Backups/" should work.
[15:07] <friendlyGoat> for some reason thats not working, its on my server so i've been doing
[15:07] <friendlyGoat> rsync -av --delete -e ssh /home/jonah/Notes/ pi@insert ip:/home/pi/SERVER/Jonah's Stuff/Note Backups/
[15:17] <friendlyGoat> thank god i fixed it, thanks for trying to help!
[16:40] <pmjdebruijn> nokiomanz: have you checked your Xorg logs yet?
[17:00] <nokiomanz> pmjdebruijn, I must admit I have not. But I can do that over ssh. BRB I will go take a look!
[17:09] <nokiomanz> I don't know what to look for exactly. I do see at some point this line : "...switch to mode<EMAIL_ADDRESS>on HDMI1..."
[18:37] <ChunkzZ> why can't I right click > open terminal and right click a file a delete without it going to the recycle bin? 19.04 does do this and 18.04 doesn't. I prefer 18.04...
[18:40] <brainwash> ChunkzZ: 19.04 has Thunar 1.8, 18.04 has the older version 1.6
[18:41] <brainwash> I'm pretty sure that "open terminal" should work
[18:44] <ChunkzZ> yeah well it doesn't and I liked that.
[18:46] <brainwash> https://git.launchpad.net/xubuntu-default-settings/tree/etc/xdg/xdg-xubuntu/Thunar/uca.xml.in?h=bionic
[18:46] <brainwash> check your ~/.config/Thunar/uca.xml
[18:47] <brainwash> deleting it will restore the default version the next time you relog
[18:48] <ChunkzZ> brainwash, I'm on 18.04 right now and it's fine, it's just 19.04 that's the issue.
[18:48] <brainwash> ah
[18:49] <ChunkzZ> also, pretty sure the minimal .iso is broken when you try and do a minimal install... it breaks when it's installed and doesn't let you open anything; something about missing a helper. idk, weird.
[18:50] <brainwash> in Thunar 1.8 the "Delete" entry is hidden by default. you can enable it via Preferences > Behavior
[18:50] <ChunkzZ> ahhh thanks, know for next time
[18:50] <brainwash> and "Open Terminal" should still work in 19.04
[18:50] <brainwash> I haven't seen any reports about it being broken
[20:06] <Spass> I've noticed that fonts in Firefox behave funky when I'm moving a cursor over the tabs - https://streamable.com/zs0ap
[20:07] <Spass> Firefox is in "CSD mode", seems like the font on the tab and in the address bar looses and gains antialiasing (?)
[20:09] <Spass> currently I'm using 19.04, Materia GTK theme and Noto Sans font, but from what I remember it was also present in 18.10 on Adwaita Dark
[20:09] <Spass> changing the font doesn't help (well, on some other fonts it's less visible, but it's still there)
[20:17] <brainwash> Spass: you will have to contact the mozilla devs
[20:19] <Spass> yeah, need to do that, but I'll try to do some more testing tomorrow on 18.04 and different themes
[20:19] <xubuntu67w> hi just check in to see webchat works cool enjoying xubuntu 18.04.2  cheers for the good work
[22:40] <izpele> Hello, having trouble with monitor geometry at login. How can I configure correct monitor geometry when I log in to Xubuntu 19.04?
[23:12] <xubuntu32w> guys, I have a problem with a program (an IntelliJ IDE) switching workspaces when there are multiple instances of it on different workspaces. Tried tweaking 'Window Manager Tweaks' -> 'Focus' opts, nothing helps. Can the program itself be the problem, or is there some solution?
[23:13] <xubuntu32w> I mean like, I have one window open on workspace 1 and another open on workspace 2, and sometimes the first window jumps to workspace 2 or vice versa
[23:13] <well_laid_lawn> xubuntu32w:  I would think that would be the program itself gathering the windows together
[23:14] <xubuntu32w> it's really chaotic, I have up to 20 or so instances of it running over 8 workspaces, and it's always just two of them merging up


[11:14] <mooa> My text looks blurry, as of today or yesterday
[11:14] <mooa> I noticed it today
[12:56] <mooa> My text looks blurry, as of today or yesterday
[12:56] <mooa> I noticed it today
[12:56] <mooa> whats wrong?
[16:11] <mooa> this channel is so dead x.x
[16:31] <ikonia> it's pretty alive if you have a discussion point
[16:40] <mooa> yeah, but i cant be the only one here using ubuntu+1
[16:40] <mooa> and cant be the only one with blurry fonts
[16:40] <mooa> anyone else notice these blurry fonts?
[16:45] <ikonia> many people in here are using the pre-release
[16:45] <mooa> yeah, and nobody experience these blurry fonts?
[16:45] <ikonia> you need to ahve a little bit of context
[16:45] <ikonia> think about it
[16:46] <mooa> well, yesterday or the day before, they fine, now they're blurry
[16:46] <ikonia> there are many different screens, laptops, displays, many different video cards driving those displays, then a few options of how to drive those video cards
[16:46] <ikonia> there is a reasonable level of diversity that some may see a problem you see, some may not
[16:46] <mooa> 24" desktop LCD, GNOME, Intel Haswell 4770k
[16:46] <mooa> over DisplayPort
[16:46] <ikonia> I'm not asking for your spec
[16:47] <ikonia> I'm asking you to take a step back and try to be aware of how some people may / may not see what you see
[16:47] <mooa> Good point
[16:47] <ikonia> the fact that you're using gnome - when the default desktop will be unity, is a key thing to keep in mind
[17:09] <mooa> Is Python 3.6 coming to zesty?
[19:12] <mooa> zesty doesn't have Python 3.6, PHP 7.1, Ruby 2.4 or Rust 1.14 :(
[20:34] <Logan> mooa: that would be a question for doko
[20:35] <Logan> at least, RC1 is available in the repo
[20:35] <Logan> but I'd be surprised if we didn't get the final release version before Feature Freeze
[20:35] <Logan> whether or not it becomes the default is unclear, though
[22:39] <mooa> who is this doko?
[23:06] <valorie> Doko is Matthias Klose: https://launchpad.net/~doko
[23:06] <valorie> Debian QA among other things