[00:12] <brainwash> ali1234: what's broken in xfdesktop?
[00:12] <ali1234> what *isn't* broken? :)
[00:12] <ali1234> the whole multiple desktop and workspace thing... doesn't work
[00:12] <ali1234> and when you relog it resets the wallpaper to default
[00:14] <brainwash> only tested it once, set a different wallpaper for every workspace and it worked and was consistent
[00:14] <ali1234> yes, that's the *only* case where it works properly :)
[00:14] <ali1234> where you set a unique wallpaper for every monitor and workspace, without any spanning
[00:15] <brainwash> oh
[00:15] <ali1234> if you have two monitors and you set a wallpaper to spanning it doesn't work properly, and if you set "same on all workspaces" it doesn't work properly
[00:16] <ali1234> when you start it up it tries to get the wallpaper for each workspace and monitor
[00:16] <ali1234> if that fails it looks for legacy settings
[00:17] <ali1234> the new version uses the monitor plug name, legacy uses the number
[00:17] <ali1234> that means that defaults have to be set using legacy, because we can't know the plug name in advance, it's something like "DVI-I-0"
[00:17] <ali1234> but that means that there is always a legacy setting
[00:17] <brainwash> is the monitor naming consistent or does it change?
[00:17] <ali1234> it's consistent on a single machine if you don't even unplug anything
[00:18] <ali1234> so anyway, there are legacy settings in the defaults.xml, which means they can't be deleted
[00:19] <ali1234> that means when you log in and you didn't specify a wallpaper for some monitor or workspace, it tries to load the legacy setting and that resets your whole system to defaults
[00:19] <ali1234> also sometimes it loads up the default wallpaper and then quickly changes to what you asked for
[00:19] <brainwash> wow, so much fun with a multi monitor setup
[00:19] <brainwash> + xfdesktop :)
[00:19] <ali1234> yes
[00:20] <ali1234> and further more i can't even set the wallpaper on all my monitors because some of them overlap
[00:20] <ali1234> setting a wallpaper on those monitors wouldn't even make sense
[00:20] <brainwash> so xfdesktop and lightdm-gtk-greeter really need some multi monitor rework
[00:20] <ali1234> looks like it
[00:20] <ali1234> i guess you've seen what gtk-greeter does when monitors overlap?
[00:21] <brainwash> no, only running single monitor setups here
[00:21] <ali1234> oh... well it draws the wallpaper multiple times
[00:21] <ali1234> it's not pretty
[00:22] <brainwash> did you also test unity-greeter?
[00:22] <ali1234> no
[00:22] <brainwash> maybe we can do some copy&paste
[00:22] <ali1234> maybe
[00:22] <ali1234> probably not though
[00:23] <ali1234> hang on let me try it...
[00:24] <brainwash> at least to get an idea on how to improve it (in case unity-greeter handles it better)
[00:24] <ali1234> heh
[00:24] <ali1234> brb
[00:28] <brainwash> xfce4-session-4.11.0 has been released
[00:32] <Noskcaj> How much of the new 4.11 stuff do we want for 14.04?
[00:33] <Noskcaj> Everything but session is now packaged for debian
[00:34] <brainwash> should we go full 4.11? :)
[00:37] <Noskcaj> If the release team allows it, i want to
[00:37] <Noskcaj> minimum is settings bugfix release, ui bugfix release, garcon
[00:38] <brainwash> I see lots of bugfixes in the various changelogs
[00:40] <brainwash> maybe it's worth to ship the full 4.11 setup
[00:45] <ali1234> how do i change the lightdm greeter?
[00:49] <ali1234> ochosi: accounts service background works in test mode but not in the real login window
[01:19] <ali1234> ok so unity-greeter is even more hilariously broken
[01:19] <ali1234> it doesn't honour the monitor layout at all
[01:19] <ali1234> so by default all the monitors do not overlap (it just uses whatever the xorg default is)
[01:19] <ali1234> that means you have to reconfigure your monitor layout after every login
[01:27] <ali1234> i suspect if it wasn't horribly broken it would show the same thing as gtk-greeter does, which is this: http://imagebin.org/295107
[01:31] <brainwash> ali1234: this would drive me nuts
[01:31] <ali1234> well it's better than what unity-greeter does
[01:31] <ali1234> which is this: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1283615/+attachment/3992319/+files/IMG_20140223_005551.jpg
[01:32] <ali1234> at least it is *functional*
[01:33] <brainwash> mmh, makes me wonder.. was multi monitor support always that bad?
[01:33] <brainwash> or do we see some sort of regression here
[01:34] <brainwash> maybe hardware/driver related?
[01:34] <ali1234> unity greeter used to work properly with xorg.conf
[01:34] <ali1234> it isn't driver related
[01:34] <ali1234> with unity-greeter you get the default layout as if you had no xorg.conf
[01:34] <ali1234> they've obviously decided to ignore it
[01:34] <ali1234> which is pants-on-head retarded, so about right for unity
[01:35] <ali1234> but yeah, multimonitor support has always been terrible. nvidia is the only way to make it work ina reasonable way
[01:35] <ali1234> and they did it by rewriting half the xorg stack
[01:36] <ali1234> that bug does not affect unity-webkit-greeter btw
[01:36] <ali1234> and probably not lightdm-kde-greeter either
[01:36] <brainwash> not at all?
[01:37] <ali1234> the webkit one does something very similar to what the gtk one does with multiple backgrounds
[01:37] <ali1234> but it honours the monitor layout like it should
[01:42] <brainwash> maybe I should extend my laptop screen with another monitor and do some testing
[01:45] <ali1234> that would be cool
[06:44] <Unit193> Oh right, how did the CC catch up go?
[07:58] <forestpiskie> it didn't
[09:12] <elfy> lderan: you managed to get anywhere writing testcase for your app?
[12:10] <lderan> elfy, is this on the right tracks http://paste.ubuntu.com/6981366/ ?
[12:14] <elfy> lderan: yep that looks fine to me - get it in to bzr push lp:~YOURUSERID/ubuntu-manual-tests/YOURBRANCHNAME
[12:14] <elfy> then I'll check/approve and sync it
[12:15] <lderan> \o/ will do so now
[12:15] <elfy> ok :)
[12:17] <lderan> and i think i've just found a bug with thunar
[12:19] <elfy> I bet it's a known issue :p
[12:20] <lderan> bet so
[12:21] <lderan> if you have 2 rename dialog boxes open the first stops working fully :P
[12:23] <elfy> I can't even open 2 rename dialogues from the same instance of thunar - works fine with another thunar opened
[12:24] <lderan> it partially works for me, the apply button on the first one opens doesn't close the box, but the apply button on the 2nd closes both
[12:24] <elfy> can't confirm that as I can't even get that far :)
[12:24] <lderan> :P
[12:26] <elfy> lderan: when you've done that testcase and I've synced the tracker - I'll do a call for testing - but I don't remember the PPA
[12:26] <lderan> shall try to find it for you
[12:26] <elfy> thanks
[12:26] <elfy> biab
[12:29] <lderan> elfy: https://launchpad.net/~light-locker-settings-team/+archive/stable , trust at the moment
[12:41] <elfy> lderan: in future when you do a mr for testcases - don't number them :)
[12:41] <elfy> someone might be syncing one and the number will be wrong ;)
[12:41] <lderan> oh sorry
[12:44] <elfy> lderan: you sure you've finished it? the first 2 tests look decidedly odd and the <dd><dd> won't work :)
[12:45] <elfy> off for a few hours now
[12:45] <lderan> shall check it :)
[12:46] <elfy> can you check spelling too please :)
[12:46] <elfy> cya later
[12:46] <lderan> cheerio
[12:46] <elfy> minuter - must have then copy pasted the same word elsewhere lol
[12:47] <lderan> gah apologies
[12:48] <elfy> ochosi: will get this testcase synced and then called for later today
[12:48] <ochosi> elfy: which one?
[12:48] <elfy> light-locker-settings
[12:49] <ochosi> oh great
[12:49] <ochosi> ty
[13:03] <lderan> elfy, have redone it :P hopefully all okay now
[13:31] <ochosi> elfy: shouldn't it be "sudo apt-get update" instead of "upgrade"?
[13:34] <ochosi> (re: ML test-case announcement)
[14:39] <jjfrv8> ochosi, you still here?
[15:02] <elfy> lderan: thanks - all done
[15:02] <elfy> ochosi: yep ...
[15:08] <jjfrv8> ochosi, I can't stick around but wanted to ask something about light-locker...
[15:08] <jjfrv8> after testing the light-locker-settings ppa, I tried the light-locker testcase...
[15:09] <jjfrv8> when I click Suspend and go to resume, it brings up the old, flaming xScreensaver dialog. That's not right, is it?
[15:09] <elfy> jjfrv8: purge xscreensaver
[15:10] <jjfrv8> alright, let me try that.
[15:11] <jjfrv8> elfy, that's better. Thanks. Can't keep all the stuff I read in the logs in my head :(
[15:12] <elfy> I did have a note in the testcase to make sure that was done - was sure that the seed had been fixed to not include xscreensaver
[15:13] <jjfrv8> apparently not, this was on a fresh install from today's daily
[15:13] <elfy> mmm
[15:16] <Unit193> Fix Committed, not Fix Released.
[15:16] <elfy> thanks Unit193
[15:17] <jjfrv8> ochosi, also wanted to make sure you had seen that xfesktop Prefs is ready for review.
[15:17] <jjfrv8> bbl
[18:51] <ochosi> thanks jjfrv8
[18:51] <ochosi> will review tomorrow
[18:58] <knome> http://open.knome.fi/2014/02/23/logging-in-with-ubuntu-one/
[18:59] <knome> ochosi, you feeling better today?
[19:01] <Noskcaj> Anyone know where micahg went? He's usually online in some form
[19:03]  * knome wonders how the liquid micah types
[19:03] <knome> or the gas-form micah
[19:06] <elfy> very very carefully in both cases
[19:07] <Noskcaj> :)
[19:08] <knome> compressed air then i guess
[19:09] <brainwash_> Noskcaj: bug 1282509 has been fixed upstream, what is the next step now? normal merge request in ubuntu, debdiff or fix it in debian and sync?
[19:10] <Noskcaj> I'll ask corsac. The sponsor queue is pretty big currently
[19:11] <brainwash_> ok, I'm a bit lost, not sure what the best move would be
[19:13] <ali1234> why did thunar get SRU'd in 13.10?
[19:13] <Noskcaj> it did?
[19:14] <ali1234> the update is crashing all over the place
[19:14] <ali1234> apparently
[19:15] <ali1234> Noskcaj: can you see error reports on errors.ubuntu.com?
[19:15] <ali1234> https://errors.ubuntu.com/problem/cb0629c4765654432162e73197d145eea640134a
[19:16] <Noskcaj> ali1234, No i can't
[19:16] <Noskcaj> although it doesn't look SRUed
[19:16] <ali1234> hmm... maybe i'm reading it wrong
[19:17] <ali1234> https://launchpad.net/ubuntu/saucy/i386/thunar
[19:17] <ali1234> ah, uploaded two months before release
[19:17] <ali1234> anyway, there's 17000 reports of that problem ^
[19:18] <ali1234> it's the old magazing_chain_pop_head nonsense again, crashing deep inside glib
[19:23] <Noskcaj> I thought  that was fixed in saucy
[19:24] <ali1234> still crashing in trusty
[19:24] <ali1234> it's on the top 100 most common bugs
[19:24] <Noskcaj> wow. Is there an upstream bugfix?
[19:25] <brainwash_> I did not notice any thunar crashes in trusty so far
[19:25] <ali1234> there is a bug report on launchpad but i can't see that
[19:25] <ali1234> bug 1203296
[19:26] <ali1234> 65th most common bug in ubuntu in the past day
[19:27] <ali1234> the xfdesktop bug was 48th
[19:28] <brainwash_> all marked as private?
[19:30] <Noskcaj> public now
[19:30] <Noskcaj> bug 1203296
[19:32] <Noskcaj> the xfdesktop fix is done in debian.
[19:39] <brainwash_> that's great, so it will be ready for ubuntu B1, right :)
[19:40] <ali1234> hmm... so of the top 10 most frequent crashers in xubuntu, thunar is number 2, 3, 4, 5, 6, 7, 8, and 10
[19:40] <Noskcaj> brainwash_, Provided corsac uploads it
[19:40] <ali1234> and it looks like most of that is magazine_chain_pop_head - which means memory corruption
[19:41] <Noskcaj> ali1234, wow
[19:41] <brainwash_> in trusty?
[19:41] <ali1234> in all versions, past 24 hours
[19:42] <brainwash_> how is that even possible?! =S
[19:45] <brainwash_> ah, I recall reading about this
[19:45] <brainwash_> something related to "Pane Side -> Tree is enabled."
[19:45] <brainwash_> the tree view
[19:49] <ali1234> it does look like the bug was introduced between 1.6.2. and 1.6.3
[19:50] <ali1234> or maybe not
[19:51] <ali1234> there are like 3 reports of it with 1.6.2 and 20000 with 1.6.3
[19:55] <ali1234> hmm i see some changes to g_list code... that's the same thing that crashed xfce-terminal
[19:55] <ali1234> argh... yeah, this is it
[19:55] <ali1234> http://git.xfce.org/xfce/thunar/commit/?id=d5b6768a104786b44542522768d6263cff07a886
[19:56] <ali1234> bad commit...
[19:56] <Noskcaj> it was terminal that we patched to stop magazine_pop_chain, maybe the patch can be modified to thunar
[19:57] <ali1234> magazine_chain_pop_head crashes are very generic
[19:57] <ali1234> it just means the program did a double free or something
[19:57] <ali1234> that commit is suspicious but it might not be it
[19:57] <ali1234> any g_list code would be a place to look though
[19:57] <ali1234> especially when using prepend
[19:57] <Noskcaj> ok
[19:58] <ali1234> basically it means memory was corrupted... it could have happened anywhere in the program, backtraces are not useful :(
[20:01] <ali1234> some more g_list stuff here: http://git.xfce.org/xfce/thunar/commit/?id=58fa477fb20aa2ac8eaea8d81d7e4d8c00180600
[20:03] <ali1234> of course it could even be in a plugin...
[20:03] <brainwash_> how do you trigger the memory corruption? with the tree view?
[20:04] <Noskcaj> Do we want dev-tool or libxfce4util 4.11? both just got uploaded
[20:05] <Noskcaj> util is probably too big a package to do this late, but dev-tools is probably safe to sync
[20:05] <ali1234> brainwash_: i don't know
[20:06] <ali1234> brainwash_: opening the tree view takes a suspiciously long time
[20:09] <brainwash_> ali1234: not here, 2sec
[20:09] <ali1234> 2 sec is too long
[20:09] <brainwash_> not for a very slow HDD
[20:09] <brainwash_> but still.. nothing crashes
[20:24] <ali1234> Noskcaj: can you see this page? https://errors.ubuntu.com/?user=a-j-buxton&period=day
[20:25] <ali1234> (or anyone else for that matter)
[20:27] <Noskcaj> yep. Turns out i wasn't logged in
[20:27] <ali1234> that page should be visible to anyone i think
[20:29] <Unit193> It is.
[21:12] <ali1234> Noskcaj: watch out when making bug reports public, that thunar one has a torrent download filename in it
[21:13] <Noskcaj> My one?
[21:13] <ali1234> 1203296
[21:14] <Noskcaj> Oops, must have missed that
[21:14] <ali1234> that guy likes his torrents, lots on the dupes too
[21:15] <Noskcaj> Is it private info though?
[21:15] <ali1234> i dunno
[21:15] <brainwash_> not the usual linux distro torrents? :D
[21:15] <ali1234> it's evidence of illegal activity though
[21:16] <bluesabre> quick, append "-parody" to each of them
[21:16] <ali1234> lots of the dupes were made public by apport
[21:16] <ali1234> this is on ProcCmdLine: field btw
[21:17] <ali1234> hmm
[21:18] <ali1234> "This incident occurred when closing Thunar after moving a file from my  PC hard drive to my external drive. The cut/paste operation was  complete, I clicked the "X" to close Thunar and got the "Ubuntu  experienced an error" message."
[21:18] <ali1234> "Thunar crashed after pressing the close button"
[21:19] <ali1234> "I closed thunar, this error happened"
[21:19] <ali1234> well, that's a pattern if i ever saw one
[21:19] <Noskcaj> thunar has a heap of different errors when it closes. I just made a bug for another one
[21:19] <ali1234> "I closed Thunar, and got this error. Pane Side -> Tree is enabled."
[21:20] <ali1234> it has all different errors because memory is getting randomly corrupted somewhere
[21:20] <ali1234> that can cause many different symptoms, but the root cause is almost certainly the same
[21:20] <ali1234> if you can find a way to reliably reproduce it...
[21:21] <ali1234> something is overwriting random bits of memory
[21:21] <ali1234> probably an uninitialized pointer somewhere
[22:48] <ali1234> it's particularly telling that all the bugs have roughly the same frequency except for the top one or two
[22:49] <ali1234> well, most happened only once
[23:01] <brainwash_> I'm not affected, because I don't move big torrent downloads from A to B :)
[23:04] <brainwash_> but thunar needs some cosmetic fixes, 1) use correct icon for "open with" menu entry 2) sort "open with..." sub menu 3) use theme color for selection rectangle
[23:04] <brainwash_> I'll put it on my todo list
[23:06] <ali1234> which versions of thunar have shipped in xubuntu releases?
[23:07] <ali1234> !info thunar precise
[23:07] <ali1234> !info thunar quantal
[23:07] <ali1234> !thunar raring
[23:07] <ali1234> !info thunar raring
[23:07] <ali1234> hmmmmmmmmmm
[23:08] <brainwash_> ?!
[23:08] <ali1234> this bug has never been reported with raring as far as i can tell
[23:08] <ali1234> so it may be a bug in some library
[23:08] <brainwash_> glib?
[23:08] <ali1234> no
[23:08] <ali1234> some xfce library that only thunar uses
[23:08] <ali1234> !info thunar saucy
[23:09] <ali1234> 1.6.2 showed the bug in saucy but not raring, and that was during development
[23:10] <ali1234> although actually, it *could* be due to glib changes... same thing happened with xfce-terminal
[23:10] <brainwash_> shouldn't there be reports outside of the ubuntu universe too?
[23:33] <ali1234> yes, but frankly... where?
[23:33] <Noskcaj> arch, debian, suse, mint?
[23:34] <ali1234> the only reason i'm seeing these reports is because of automatic error reporting
[23:34] <ali1234> i think people tend not to report one-off unreproducable crashes
[23:34] <ali1234> mainly because triagers just close the bugs if they can't be reproduced
[23:35] <ali1234> i think the only option here is to go through the code and audit it by hand :(
[23:36] <ali1234> cppcheck didn't find anything obvious, valgrind isn't showing any corruption... i don't know what else to try
[23:37] <ali1234> i'm actually impressed we even got on the top 100 bugs... must be a lot of users out there
[23:38] <ali1234> especially since it seems pretty hard to reproduce
[23:52] <knome> humm, i'm seeing a debian wallpaper on the installer...
[23:52] <knome> :)
[23:55] <Noskcaj> ali1234, yay?


[00:25] <shaybox> Anyone know how i would go about starting a second X session thats blank, starting openbox then running a command / opening a program? "xinit (ex. terminator) -- :1 vt8" then i need openbox somehow
[01:17] <schnoodles> If I am running kde-backports is the upgrade process to 16.10 a tiny bit different?
[01:20] <valorie> backports PPA in 16.04
[01:20] <valorie> ?
[01:20] <valorie> if so, no
[01:20] <valorie> it will disappear during the upgrade though
[05:20] <user|37353> Hello there ! After a update Form Kubuntu 16.10 I Trier to reboot the laptop, but it just wohnt Boot
[08:14] <barq> Is it worth upgrading to 16.10 or should I stick with LTS?
[08:24] <hateball> barq: depends what you value
[08:26] <barq> A stable OS
[08:27] <hateball> imo the current state is that plasma in 16.10 is more stable than that of 16.04+backports
[08:27] <hateball> but that's just one part of the OS
[08:30] <barq> I am on 5.6.5 plasma
[08:30] <barq> via backports
[09:13] <yossarianuk> on kubuntu 16.10 I have a really annoying issue - Every login mangles by dual monitor config! Primary monitor unusable on login (black screen unable to right click on it until I disable/renable)
[09:13] <yossarianuk> https://bugs.kde.org/show_bug.cgi?id=371207
[09:14] <yossarianuk> this doesn;t occur with neon/plasma 5.8 (which I use at home) - I;'m running kubuntu @ work due to it not being rolling...
[09:14] <yossarianuk> any ideas how to prevent the issue happening every reboot/login
[09:19] <barq> OK, maybe updating is not the best idea then.
[09:20] <yossarianuk> I just hopoe I don't have to bugger about with the display options every reboot until Plasma 5.8 PPA is online (assuming it is going to be)
[09:36] <hateball> hmmm, interesting. I have yet to update my workmachine (which has dual monitors) from 16.04
[09:36] <hateball> perhaps I shall not do that this week then
[09:40] <yossarianuk> I was on 16.04/plasma 5.6.5 and that was ok
[09:40] <yossarianuk> I did a fresh install
[09:41] <yossarianuk> (maybe 5.6.4)
[09:41] <hateball> yossarianuk: did you try wiping the kscreen configs also?
[09:41] <yossarianuk> hateball: i.e delete a config file ?
[09:41] <hateball> yossarianuk: yes
[09:42] <yossarianuk> rm -rfv ./.local/share/kscreen
[09:42] <yossarianuk> ?
[09:42] <hateball> that'll be it, assuming you are in your $HOME
[09:42] <yossarianuk> ok - will do
[09:43] <yossarianuk> I wonder if its due to my primary screen being on the right (rather than left)..
[09:43] <hateball> then a reboot to regenerate configs
[09:43] <hateball> yossarianuk: I have seen that mentioned in #plasma iirc
[09:43] <yossarianuk> is it best to exit kde first before wiping the files?
[09:43] <hateball> I have the same setup
[09:43] <hateball> yossarianuk: doesnt matter, but you'll want to reboot/relog after
[09:43] <yossarianuk> ok
[09:44] <yossarianuk> thanks
[09:44] <hateball> yossarianuk: and then you'll have to set primary etc anew
[09:44] <yossarianuk> sure
[09:44] <yossarianuk> just on this subject.. Is 5.8 ppa planned ?
[09:45] <hateball> I think it is underway, might wanna ping acheronuk about that tho
[09:48] <lordievader> hateball: Loggin out and in is enough to regenerate that config.
[09:49] <yossarianuk> cheers - I won't bother him, just nice to know its on the horizon.
[09:52] <hateball> lordievader: yea I suppose it would be
[09:52] <hateball> I just reboot anyway, adds... 5 seconds :p
[10:35] <eagles0513875|2> hey guys I have a memory card which i kinda didnt let complete formatting :(
[10:35] <eagles0513875|2> and basically i want to know how can i mount it in linux and use gparted to format it
[10:36] <hateball> eagles0513875|2: why wouldnt you? just nuke the entire FAT create new partition etc
[10:36] <yossarianuk> eagles0513875|2: insert card, check dmesg to see what device is it - then gparted
[10:36] <eagles0513875|2> ok will try that out
[10:36] <eagles0513875|2> brb
[10:49] <eagles0513875_> hey again . So I removed and reinserted the memory card and in dmesg im seeing   253.111078] mmc0: card never left busy state [  253.111085] mmc0: error -110 whilst initialising SD card [  254.763035] mmc0: card never left busy state [  254.763043] mmc0: error -110 whilst initialising SD card
[10:50] <eagles0513875_> plus if i do an fdisk -l im not even seeing the card listed
[10:51] <hateball> busted SD card is not unlikely
[10:51] <hateball> if another card works in the same reader
[10:52] <eagles0513875_> hateball: it was working before i kinda borked it up and it didnt finish formatting
[10:52] <eagles0513875_> also not visible on my macbook air where it was previously working
[10:53] <hateball> Working before being broken is not an uncommon scenario
[10:53] <eagles0513875_> ok i am seeing Partition 1 does not start on physical sector boundary. in dmesg
[10:53] <eagles0513875_> in fdisk dmesg is saying something else
[10:54] <eagles0513875_>  226.274407] Buffer I/O error on dev sr1, logical block 32765, async page read
[10:55] <hateball> eagles0513875_: when you insert the card, can you see what device it gets assigned? with dmesg
[10:55] <hateball> you could try nuking the device using dd
[10:55] <eagles0513875_> hateball: negative should i have it out and then insert after logging in
[10:55] <eagles0513875_> and nuking it with dd is what i want to do o
[10:57] <hateball> eagles0513875_: do you have any /dev/mm* ?
[10:57] <hateball> eagles0513875_: anyhow, removing and re-inserting it should show a new entry in dmesg
[11:01] <eagles0513875_> i dont have /dev/mm*
[11:02] <eagles0513875_> and dmesg doesnt show anythign except what i pasted above
[11:03] <eagles0513875_> hateball: im also noticing http://pastebin.ubuntu.com/23347990/
[11:04] <acheronuk> hateball: it is the intention to backport 5.8 once we have it in 17.04. can't give a precise ETA, but everpne here wants it to be as soon as is practical
[11:04] <acheronuk> yossarianuk: ^^^
[11:05] <eagles0513875_> any other ideas hateball
[11:08] <hateball> eagles0513875_: is /dev/sr1 your sd-reader?
[11:08] <hateball> usually sr* is some optical media iirc
[11:09] <eagles0513875_> not sure what my card reader is set to on this laptop
[11:09] <eagles0513875_> first time really dicking around with a card reader, its my fault cuz i didnt let the format of the memory card complete on my other laptop before pulling it out
[11:12] <hateball> eagles0513875_: well. we can find out with some trickery. first, is it connected using usb? "lsusb"
[11:13] <eagles0513875_> im going to try another idea that just came to me im goign to see if I can refiormat using my tablet
[11:14] <eagles0513875_> hateball: the issue is with the memory card itself
[11:15] <eagles0513875_> i put the 32gb one i had in the adapter and put it in memory card reader and it came up as /dev/mmcblk0
[11:16] <eagles0513875_> even better i did a number on the memory card
[11:16] <eagles0513875_> even my tablet cant find it
[11:16] <hateball> eagles0513875_: well, you can try putting in the nonfunctional card now that you know the device enumeration
[11:17] <hateball> and then "sudo dd if=/dev/urandom of=/dev/mmcblk0"
[11:17] <eagles0513875_> mc0: card never left busy state [ 1981.601764] mmc0: error -110 whilst initialising SD card
[11:17] <eagles0513875_> same errors
[11:17] <hateball> ye
[11:17] <hateball> as I said, it happens...
[11:18] <eagles0513875_> with the working card [ 1824.670485] mmc0: new high speed SDHC card at address 0001 [ 1824.683321] mmcblk0: mmc0:0001 00000 29.8 GiB  [ 1824.685062]  mmcblk0: p1 [ 1949.125999] mmc0: card 0001 removed
[11:18] <hateball> SD cards arent very awesome, certainly not if you do stuff like pull them out mid-write
[11:18] <eagles0513875_> I know so its a lost cause
[11:18] <hateball> I dont know of any more low-level way to bring them alive
[11:19] <eagles0513875_> anyone else have any ideas
[11:20] <eagles0513875_> hateball: seems like dd is working
[11:23] <eagles0513875_> hateball: is there a way i can see progress with dd how much has been done as the memory card is 128GB
[11:24] <hateball> eagles0513875_: should be able to cancel the dd (ctrl+c), issue "sync" and then remove and insert the card and see if you get errors
[11:24] <hateball> there is a way to attach to dd to show progrees but I forget it
[11:24] <hateball> to show when you run, use "dd status=progress if=etc etc"
[11:25] <yossarianuk> acheronuk: hateball: cheers
[11:26] <lordievader> Does it work in another pc?
[11:27] <eagles0513875_> lordievader: negative
[11:27] <eagles0513875_> it was before i pulled it out midformat as i thought it was ready
[11:27] <eagles0513875_> dd is working but i think i need to let it complete dding all 128gb
[11:28] <eagles0513875_> once dd is done i think ill go through https://ubuntuforums.org/showthread.php?t=2198218 and follow the steps there
[11:29] <eagles0513875_> lordievader: how are you
[11:30] <lordievader> eagles0513875_: Busy but good. How are you?
[11:30] <eagles0513875_> same here
[11:31] <eagles0513875_> then again when am i not things are finally winding down from the summer madness here
[11:31] <eagles0513875_> lordievader: also engaged and getting married in 2018 too
[11:31] <lordievader> eagles0513875_: Congrats ;)
[11:32] <eagles0513875_> thanks
[11:32] <eagles0513875_> excited and looking forward to it
[11:40] <eagles0513875_> lordievader: im realizing how much i hate being on windows but kinda stuck with it for one thing and one thing only sadly
[11:40] <eagles0513875_> most of our systems are tied into windows and IE
[11:41] <eagles0513875_> im going ot speak to my manager and see if I can get my laptop onto linux
[11:46] <lordievader> eagles0513875_: This is more a topic for #kubuntu-offtopic ;)
[11:47] <Not_a_Robot> guys, how can I make
[11:47] <Not_a_Robot> cd mtp:/Phone/
[11:47] <Not_a_Robot> ?
[11:47] <Not_a_Robot> I want to copy the content there
[11:47] <Not_a_Robot> but the only way I know is using Dolphin
[11:48] <hateball> Not_a_Robot: do you have the computer and phone on the same wifi network?
[11:48] <Not_a_Robot> yes hateball, but KDE connect is not an option
[11:48] <hateball> Alright :p
[11:49] <Not_a_Robot> xDD
[11:49] <Not_a_Robot> The thing is I would like to discover
[11:49] <eagles0513875_> ahh yes lordievader  sorry thought i was in there
[11:49] <Not_a_Robot> how Dolphin gets inside "mtp:/"
[11:49] <Not_a_Robot> I would like to get there via command line
[11:50] <hateball> it's fusemounted somewhere
[11:50] <hateball> Not_a_Robot: run "mount" in a terminal and it should show up
[11:53] <Not_a_Robot> by fuse I just finde this
[11:53] <Not_a_Robot> hateball: fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
[11:54] <hateball> Not_a_Robot: have you browsed the device in dolphin ?
[11:54] <Not_a_Robot> yes hateball
[11:54] <hateball> hmmm
[11:54] <hateball> well, I dont really know then.
[11:54] <hateball> I havent really battled MTP for a few years since kde connect :p
[11:55] <Not_a_Robot> I have a lot of content and KDE Connect crashes
[11:55] <Not_a_Robot> :P
[12:00] <eagles0513875_> hateball: i some how have an 8gb partition i believe to be on the memory card what do i need to do to format it properly
[12:00] <eagles0513875_> as gparted isnt picking it up still
[12:01] <eagles0513875_> lordievader: ^
[12:01] <eagles0513875_> thing is fdisk -l still isnt listing it
[12:03] <hateball> eagles0513875_: what do you mean believe to be on the memory card? either it is on the card, or it is on some other device
[12:03] <hateball> where are you seeing this?
[12:04] <eagles0513875_> its only 8gb out of 128 i dont have anythign 8gb in the system
[12:04] <eagles0513875_> only 2gb usb pen drive
[12:04] <eagles0513875_> which im on kubutnu with and the memory card
[12:06] <hateball> eagles0513875_: and you know for sure this is a 128GB device and not some trickery bought from ali express?
[12:07] <hateball> also if you ran dd against the raw device it shouldnt have any partitions at all, as that should have nuked MBR/FAT
[12:08] <eagles0513875_> hateball: it has
[12:09] <eagles0513875_> it seems like there are 4 mmcblk0  to 4 partitions
[12:39] <eagles0513875_> hateball: i have zeroed out /dev/mmcblk to blk4 and still nothing
[12:45] <BluesKaj> Hiyas all
[13:38] <paranoidabhi> hi
[13:40] <paranoidabhi> How can I fix this mess https://paste.ubuntu.com/23339263/?
[13:40] <paranoidabhi> Stuck at it for 2 days :(
[13:40] <paranoidabhi> any guesses?
[13:41] <paranoidabhi> I can boot into recovery somehow after a dpkg configuration fix every time.
[13:41] <paranoidabhi> No fstab problems, something related to swap has gone to wrong.
[13:41] <ben-no> hi
[13:42] <ben-no> do you also experience lots of problems with 16.10?
[13:43] <paranoidabhi> ben-no, yeah!!!
[13:43] <paranoidabhi> can't change brightness..multi-monitor no detection...etc
[13:45] <ben-no> the monitor problem seems to be related to: https://bugs.kde.org/show_bug.cgi?id=370411
[13:45] <ben-no> yep
[13:46] <paranoidabhi> ben-no, what problems are you saying? Something related to swap not being mounted? (https://paste.ubuntu.com/23339263/?)
[13:47] <ben-no> I have also problems with using multiple monitors and some problems with kontact
[13:47] <ben-no> https://bugs.kde.org/show_bug.cgi?id=362958#c24
[13:47] <paranoidabhi> hmm... any ideas guys? https://paste.ubuntu.com/23339263/?Let me know what else debugging info I can provide.
[13:52] <momoe> Does anyone know if Kubuntu 16.10 supports KDEConnect 1.0 yet?
[13:53] <paranoidabhi> momoe, 16.10 doesn't even support booting. :p
[13:53] <momoe> ???
[13:54] <Smurphy> momoe: I am using it in 16.04.
[13:55] <momoe> With the use of the backports ppa?
[13:56] <momoe> I did that and now there's a few things broken
[13:56] <paranoidabhi> momoe, it worked with 16.04
[13:57] <Meodudlye> momoe: I use it, and it works very well
[13:58] <user|10784> Hello ! My problem is that steam wont start! I would appretiate help
[13:58] <momoe> Okay, from my understanding 16.04 was only supporting the 0.9
[13:58] <paranoidabhi> sry I not sure how to debug this issue https://paste.ubuntu.com/23339263/. If anybody can help finding the issue it would be great/
[14:02] <paranoidabhi> :/
[14:02] <user|10784> https://thepb.in/p/n5fl4WMgOo8CY
[14:02] <Meodudlye> paranoidabhi: you have some strange characters in the uuid of your disks : \x2duuid-CA5D\x2dF91D.device
[14:02] <Meodudlye> can than be the problem?
[14:03] <paranoidabhi> Meodudlye, hi thanks for the suggestion. Which line are you referring to?
[14:04] <Meodudlye> paranoidabhi: Oct 17 19:19:00 hp systemd[1]: dev-disk-by\x2duuid-CA5D\x2dF91D.device: Job dev-disk-by\x2duuid-CA5D\x2dF91D.device/start timed out.
[14:07] <paranoidabhi> Meodudlye, nice find :). But I am unsure why the happens the fstab seems okay. Where is it getting this uuid from? Any guesses?
[14:07] <Meodudlye> paranoidabhi: and the settings in your fstab may cause that: you have UUID=CA5D-F91D  /boot/efi       vfat    umask=0077      0       1 maybe that should be default instead of vfat ?
[14:08] <Meodudlye> paranoidabhi: hmm, no, sorry, the default is for something else
[14:09] <Meodudlye> I have that in my fstab: UID=1C09-76EB  /boot/efi       vfat    defaults        0       1
[14:09] <Meodudlye> (with two U :UUID)
[14:10] <paranoidabhi> Meodudlye, it should defaults instead of umask=0077?
[14:11] <Meodudlye> paranoidabhi: that is what I have in my own fstab
[14:15] <paranoidabhi> Meodudlye, ok. I will check that and get back
[14:20] <CQ> hello, I have a problem with videos playing (youtube video, firefox, on YY). The video loads, buffers a bit, but never plays
[14:20] <hateball> CQ: are these html5 or flash videos?
[14:20] <CQ> hitting pause and play goes one frame forward / backwards
[14:21] <CQ> hateball: html5
[14:21] <CQ> I'm trysing to get rid of flash
[14:23] <hateball> CQ: weird. do you get the same behavior in say chromium?
[14:25] <hateball> I don't recall if you need any additional codecs for h264 or so in Firefox, if that could be the case with the video
[14:25] <CQ> hateball: installing, let me check.
[14:25] <CQ> Also, this is in a virtualbox VM (windows 7 host). The video plays in FF on the host
[14:26] <BluesKaj> CQ, chrome-browser uses it's own version of flash, unfortunately flash is a fact of life on a lot of websites ..HTML6 is slowly being adopted , but it's gonna take a while
[14:26] <BluesKaj> HTML5 even
[14:26] <CQ> hateball: same issue on chromium
[14:27] <hateball> BluesKaj: html5 has been default on youtube since 2015 or so tho
[14:27] <hateball> CQ: do you have working audio in other applications?
[14:27] <CQ> vbox has no acceleration set.
[14:28] <hateball> I *think* video playback may stall if it tries to connect to an audio device but cannot find one
[14:28] <CQ> hateball: I was going to say, i had pulseaudio problems in the past... how can I test the audio?
[14:28] <BluesKaj> hateball, but not all video on YT plays on HTML5
[14:30] <hateball> BluesKaj: Yep, not old ones (that havent been re-encoded yet)
[14:30] <hateball> CQ: can try playing this file /usr/share/sounds/alsa/Front_Center.wav
[14:30] <hateball> in any given player
[14:31] <CQ> hateball: audio seems to be the problem... the default amarok tune freezes the same way
[14:32] <BluesKaj> CQ, aplay -l  to see what we're dealing with
[14:33] <hateball> CQ: right, hopefully BluesKaj and others can help you sort that, I have to split
[14:33] <CQ> card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
[14:34] <CQ> hateball: ok, thanks!
[14:35] <CQ> BluesKaj: I have Intel HD, ICH AC97, and Soundblaster16 ... trying intelHD now as a controller
[14:36] <BluesKaj> CQ, sudo modprobe snd-hda-intel
[14:37] <CQ> BluesKaj: amarok seems to work now with the IntelHD controller
[14:37] <CQ> card 0: Intel [HDA Intel], device 0: STAC9221 A1 Analog [STAC9221 A1 Analog]
[14:37] <BluesKaj> F6 in alsamixer to choose the card0
[14:37] <CQ> card 0: Intel [HDA Intel], device 1: STAC9221 A1 Digital [STAC9221 A1 Digital]
[14:38] <BluesKaj> yup
[14:39] <CQ> alsamixer says its just set to default, but I can choose the card explicitly
[14:40] <CQ> anything else to check / do or just sit back and enjoy the video?
[14:42] <BluesKaj> CQ, yes and save the setting in /etc/modprobe.d/alsa-base.conf as : options snd-hda-intel index=0
[14:43] <BluesKaj> that should solidify your driver setting
[14:44] <CQ> ok, thanks!
[14:45] <BluesKaj> ok gotta rebbot ..bbiab
[14:52] <shaybox> Would anyone know why sometimes rebooting my computer will swap around KDE Panels and change my wallpaper, but only sometimes and only one of the monitor's wallpapers
[14:54] <ben-no> I think that is related to https://bugs.kde.org/show_bug.cgi?id=370711
[15:05] <shaybox> what do i open to see my plasma version? i forgot
[15:10] <shaybox> got it, Kinfocenter
[15:44] <danimal2> hi, rebooted pc this morning, kubuntu 14.04 lts after signing in does not load desktop..not sure if it was uninstalled by accident...how do i get it back, cant get to terminal...thanks
[15:45] <shaybox> what do you see? any hints, is grub showing or is it completely gone
[15:47] <yossarianuk> the issue i'm having with dual monitors and the primary screen being black and unusable (i.e not being able see a  right click menu, etc) on every boot -  looks like these bugs
[15:48] <yossarianuk> https://bugs.kde.org/show_bug.cgi?id=371207
[15:48] <yossarianuk> which is a dupe of -> https://bugs.kde.org/show_bug.cgi?id=369665
[15:49] <danimal2> shaybox i have the pretty wallpaper and a mouse working but nothing else
[15:49] <danimal2> no icons or menus
[15:50] <yossarianuk> its fixed in Plasma 5.8 - the comment from  Sebastian Kügler is 'This bug has been fixed in Plasma 5.8, please upgrade. :)'
[15:51] <yossarianuk> so is that fix ever going to make it back to plasma 5.7.5 in kubuntu 16.10 ?
[15:51] <yossarianuk> or is that it until plasma 5.8 is released /
[15:51] <danimal2> yossarianuk, is that reply for me or ?
[15:51] <yossarianuk> nope
[15:52] <yossarianuk> its relating to a major bug in kubuntu 16.10 - which is fixed in later Plasma
[15:53] <danimal2> i see thanks yossarianuk
[15:53] <yossarianuk> so will a bug that is affecting kubuntu 16.10, but fixed in plasma 5.8 going to be backported ever to kubuntu 16.10?
[15:57] <yossarianuk> ok  its bad Sebastian Kügler just responded  to my question, will it be fixed in Kubuntu 16.10 'It won't unless that kubuntu upgrades to Plasma 5.8.'
[15:58] <yossarianuk> so I can only assume that means if I stick with Kubuntu 16.10 I will be running a broken system until April next year...................
[15:58] <yossarianuk> which is terrible
[16:00] <ben-no> sounds like that there will be backports soon: https://www.kubuntuforums.net/showthread.php?70942-Plasma-5-8-in-16-10-backports&p=394086&viewfull=1#post394086
[16:01] <yossarianuk> ben-no: sure, but they should make the backports the normal upgrade so people are not running known broken software...
[16:01] <yossarianuk> seems silly to keep broken software in the name of 'stability'
[16:10] <danimal2> so i booted network cd to live shell...busybox..how do i get to su and reinstall desktop?
[16:11] <danimal2> not done this before and every command says not found..sorry not a linux expert.
[16:13] <ekto> I cant Boot kubuntu a blackscreen will Boot and nothing else happens
[16:13] <danimal2> ekto maybe try a live cd, thats what im doing..lol
[16:13] <ekto> I die that ... 20 times exactly
[16:14] <ekto> Did*
[16:14] <danimal2> ekto, not sure..backup your data first. so if you have HD failure or something else going on.
[16:15] <ekto> Well i guess thats too Late cuz i already installed kubuntu New by a desktop CD
[16:16] <ekto> Also my graphic card always worked fine
[16:16] <danimal2> ekto, yikes..u never want to lose data -- unless not important.
[16:17] <ekto> Only computer games Form steam, i can redownload Thema
[16:17] <ekto> From * stupid auti correction
[16:18] <danimal2> ekto, ok no worries then lol...id check your hardware then try a reinstall i guess.
[16:18] <ekto> How do i do that ?
[16:19] <danimal2> ekto, there's many ways. i personally network boot with some utilities that do all that for me. i use something called erpxe. but you can try other boot disks etc.
[16:20] <danimal2> it may be you have a driver issue with your graphic card, not sure.
[16:20] <ekto> I am right now in the recovery console AS root
[16:22] <ekto> My graphic card is nvidia-304
[16:22] <danimal2> ekto, not sure..maybe someone else can help.
[16:22] <danimal2> or google :)
[16:23] <ekto> I deleted the additional driver
[16:24] <ekto> And nvidia-304-dev
[16:25] <ekto> Its rebooting and...
[16:25] <ekto> Blackscreen
[16:26] <ekto> Ill reinstall the system again and restart it without installing the nvidia things
[16:28] <danimal2> ekto, gl!
[16:30] <ekto> THX
[16:31] <sponge> Hello
[16:32] <danimal2> solved my issue, doh! got to grub, recovery, enable network, then root ...:)
[16:33] <ekto> And what do i type in the root ? I did everything possible after these steps
[16:33] <sponge> I'm having trouble trying to d/l wallpapers from the "get new wallpapers" button. Is it broken for you too?
[16:33] <ekto> I feel dunked in
[16:33] <ekto> On !
[16:34] <ekto> Not even the DVD boots now
[16:34] <sponge> I get this error message: Some categories are missing.
[16:35] <ekto> Retry ...
[16:35] <sponge> ekto, the "Retry" is for me?
[16:36] <ekto> sponge oh no i cant Boot my laptop thats my Problem
[16:36] <danimal2> ekto, either make a new DVD or learn how to network boot with an image.
[16:36] <sponge> oh, ok
[16:36] <ekto> danimal2 OK , by the way are you german ?
[16:37] <danimal2> ekto, no
[16:38] <ekto> danimal2 OK oh it Bootes again
[16:40] <danimal2> ekto,this may help.  http://askubuntu.com/questions/620838/hardware-rendering-issues-with-nvidia-304-in-kubuntu-15-04#624659
[17:06] <OnkelTem> Hi all
[17:07] <OnkelTem> I've installed Kubuntu 16.04 and Super key doesn't work. Also when I've added 4 workspaces they are bound to Ctrl+F1...F4 for some reason.
[17:08] <OnkelTem> That it doesn't work I only judge by now switching desktops using Super+123
[17:08] <OnkelTem> it does something
[17:09] <OnkelTem> for example if I press Super+Q it shows some... rooms? Idk what is that
[17:10] <OnkelTem> Ah, forgot to mention. I call "Super" a Left Win key :)
[17:10] <OnkelTem> the*
[17:10] <OnkelTem> So probably I have to configure it somehow for KDE to use it as Super
[17:10] <OnkelTem> but I didn't find where it's configured
[17:14] <paranoidabhi> hi guys
[17:15] <mparillo> For Kubuntu 16.04 you would need to install ksuperkey, and incur upstream disapproval. When Plasma 5.8.1 drops, then the super key will bring up the application launcher.
[17:16] <paranoidabhi> I still couldn't fix that issue https://paste.ubuntu.com/23339263/?
[17:16] <paranoidabhi> please suggest.
[17:25] <sponge> mparillo, Can you get wallpapers from the "gen new wallpapers.." button?
[18:03] <haakonn> is there any ppa or anything for newer kde/plasma releases for 16.10? or will i be on plasma 5.6 forever?
[18:04] <acheronuk> 16.10 has plasma 5.7.5.
[18:06] <haakonn> what? where?
[18:07] <haakonn> ah, i meant 16.04, sorry :)
[18:08] <acheronuk> http://packages.ubuntu.com/yakkety/plasma-desktop
[18:08] <haakonn> is 16.10 out? holy moly i'm out of the loop
[18:09] <acheronuk> haakonn: plasma 5.7.5 is nearly done for 16.04. but as it got delayed I'm not sure if it may not be worth skipping and just doing 5.8
[18:10] <haakonn> that's cool. 5.8 is an lts too
[18:10] <acheronuk> precisely.
[18:12] <dbrom> hello all... I am trying to get a script to run from my ubuntu system that will move all data from a freenas share to a local folder.. using rsync -avz "ssh   " ssuser@<IP_ADDRESS>:/mnt/V1/Share/ /home/vuser/Documents/Bacup/ using default port because its inside a network
[18:12] <acheronuk> longer term to 16.04 5.8 will be the best fit. going to want that backported if achievable, anyway
[20:57] <honeybadger13> Is there a way to make plasma use the default pidgin systray icons? I'm not sure if it's just me but those new ones (green silouette for online, purple for new message etc...) don't really work for me as I'm used to something _very_ orange in systray when new message comes ...
[22:31] <sponge> What is the "price" one pays when he's using apps such as vlc/pidgin/firefox/thunderbird/hexchat instead of the native kde apps?
[22:42] <mparillo> sponge: You may being in more dependencies. Your theming / dialog boxes might seem generic.
[23:18] <sponge> mparillo, More dependencies = more mb from HD. That I don't care. But does this also affect the performance of these apps? or the burden on the system?
[23:56] <sponge> bbl. thanks mparillo


[00:48] -lugito:#lubuntu-devel- [rMANUALc57fdc1ac261: Start Chapter 2 of lubuntu manual] Diffusion committed: https://phab.lubuntu.me/rMANUALc57fdc1ac261
[00:50] <lyn||orian> ty for the lugito work tsimonq2
[00:51] <teward> can you who're subscribed to various phabricator notices confirm you're still getting notifications?
[00:51] <teward> (sorry I was poking the server on behalf of wxl and tsimonq2 - want to make sure I didn't break outgoing notices)
[00:52] <wxl> um
[00:52] <wxl> i don't think there
[00:52] <wxl> 's been a new task update
[00:53] <teward> just thought I'd check :)
[00:53] -lugito:#lubuntu-devel- [T34: Configure email commands] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T34#850
[00:54] <wxl> no email yet
[00:54] <wxl> nope
[00:54] <wxl> think you killed it
[00:55] -lugito:#lubuntu-devel- [lubuntu-manual] lubuntu-lugito pushed 1 new commit to master: https://git.io/vhvqb
[00:55] -lugito:#lubuntu-devel- lubuntu-manual/master c57fdc1 Lyn: Start Chapter 2 of lubuntu manual
[00:55] -lugito:#lubuntu-devel- [T34: Configure email commands] teward (Thomas Ward) commented on the task: https://phab.lubuntu.me/T34#851
[00:55] <teward> wxl: hrm
[00:56] <wxl> just got it
[00:56] <wxl> it was pretty snappy before
[00:56] <teward> indeed?
[00:57] <teward> you also didn't have an outward-facing mail system previously
[00:57] <wxl> at least with yours i got it within the same minute
[00:58] <wxl> actually same with mine
[00:58] <teward> wxl: indeed.  consider that since this is reachable in general from the Internet, so inbound mail works, right now there's more 'scanner' traffic - but this is the headache of mail servers.
[00:58]  * wxl is done whining now
[00:58] <teward> wxl: you mean sendmail on this box?
[00:58] <teward> because that was listening on localhost only.
[00:58] <teward> but it could be due to anything.
[00:58] <wxl> it's all good, we're good
[00:58] <wxl> thank you
[00:58] <wxl> i'm gong home
[01:00] <teward> see ya
[01:16] <tsimonq2> Thanks teward
[01:25] -lugito:#lubuntu-devel- [lubuntu-manual] lubuntu-lugito merged master into HEAD: https://git.io/vhvYu
 Sigh, I need to turn that off.
[01:44]  * tsimonq2 stretches
[01:44] <tsimonq2> Evening y'all
[01:45] <tsimonq2> lyn||orian: No problem; I'm going to migrate things off of GitHub and Launchpad now for the manual. I'll make sure you have commit access, and I'll let you know when it's done.
[01:47] <tsimonq2> lyn||orian: You should now have access to clone/push to ssh://git@phab.lubuntu.me:2222/source/lubuntu-manual.git
[01:48] <tsimonq2> m4sk1n: Same with you. ^^^^
[01:49] <tsimonq2> In fact...
[01:49] <tsimonq2> Creating an organization for the Manual now.
[01:54] -lugito:#lubuntu-devel- [T45: Audacious not in spec.pdf] tsimonq2 (Simon Quigley) just created this task: https://phab.lubuntu.me/T45
[01:54] -lugito:#lubuntu-devel- [T46: The footer of each page should show a Last Updated date] tsimonq2 (Simon Quigley) just created this task: https://phab.lubuntu.me/T46
[01:55] -lugito:#lubuntu-devel- [T47: We should programatically get version numbers] tsimonq2 (Simon Quigley) just created this task: https://phab.lubuntu.me/T47
[01:55] <tsimonq2> There, imported the open issues from GitHub: https://phab.lubuntu.me/project/board/5/
[01:57] <tsimonq2> There, go nuts. :)
[02:02] -lugito:#lubuntu-devel- [T38: Package LXQt 0.13.0] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T38#879
[02:22] -lugito:#lubuntu-devel- [rLIBQTXDGPACKAGING4e6fd2d34280: New upstream release.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING4e6fd2d34280
[02:22] -lugito:#lubuntu-devel- [rLIBQTXDGPACKAGING6edaa856ac33: Remove "~" from debhelper depends.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING6edaa856ac33
[02:22] -lugito1:#lubuntu-devel- [rLIBQTXDGPACKAGING6c48aa5d7640: Update Vcs-* and Maintainer to Lubuntu values.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING6c48aa5d7640
[02:23] -lugito1:#lubuntu-devel- [rLIBQTXDGPACKAGING4f2ab68ebc7b: Release to Cosmic.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING4f2ab68ebc7b
[02:23] -lugito:#lubuntu-devel- [rLIBQTXDGPACKAGINGb23f76a310b8: Update copyright file.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGINGb23f76a310b8
[02:23] -lugito:#lubuntu-devel- [rLIBQTXDGPACKAGING02b99e230182: Remove pristine-tar junk.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING02b99e230182
[02:23] -lugito:#lubuntu-devel- [rLIBQTXDGPACKAGING9bf136022e29: Update the watch file to point to the new upstream location.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING9bf136022e29
[02:24] -lugito:#lubuntu-devel- [rLIBQTXDGPACKAGING14613b54ac1d: Remove trailing whitespace from rules.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLIBQTXDGPACKAGING14613b54ac1d
[02:46] <tsimonq2> I'm going to turn off the webhook for now so I don't spam the channel with 100s of commit messages.
[03:49] <tsimonq2> Turning the webhook back on; I'm done for the night.
[03:51] -lugito:#lubuntu-devel- [T38: Package LXQt 0.13.0] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T38#881
[03:51] <tsimonq2> Night!
 Check out @PacktPub’s Tweet: https://twitter.com/PacktPub/status/998574382862581760?s=09
 That's a bit offtopic for here. :)
[17:00] <wxl> m4sk1n: ping me when you get a chance?
[17:18] <teward> wxl: tsimonq2: Phab emails should work now?
[17:18] <teward> (when sent to phab @ lubuntu.me)
[17:18] <wxl> test sent
[17:19] <teward> so your message was delivered to Phab's mail handler
[17:19] <wxl> that's good
[17:19] <teward> whether Phab did anything with it I can't tell.
[17:19] <wxl> unlikely
[17:20] <wxl> i don't think we set up the email handler, did we?
[17:20] <teward> not sure if you did in the Phab settings but I did set up the step where it's handed off to Phab's mail handler
[17:21] <teward> ah there's the mail messages
[17:21] <wxl> ?
[17:21] <teward> so
[17:21] <teward> Phab shows the test messages so far
[17:22] <teward> via its list-inbound test function
[17:22] <wxl> ok
[17:22] <wxl> one sec
[17:22] <teward> whether you've configured Phab specifically for mail is a different issue
[17:23] <wxl> oh
[17:23] <wxl> did we already install mailparse
[17:23] <wxl> ?
[17:23] <teward> yes
[17:23] <teward> otherwise the script segfaults
[17:24] <teward> `apt install php-mailparse` :P
[17:24] <teward> so
[17:24] <teward> your message shows up here:
[17:24] <wxl> oh oh ok
[17:24] <wxl> hold on
[17:24] <teward> 4  -      -            Re: [Maniphest] [Commented On] T34: Configure email commands
[17:24] <teward> but not sure if Phabricator is actually set to care about inbound mail yet, that's a step not documented
[17:24] <wxl> uh
[17:25] <wxl> https://secure.phabricator.com/book/phabricator/article/configuring_inbound_email/
[17:25] <wxl> see configuring fabricator
[17:25] <wxl> it will need to be able to handle +bits
[17:25] <wxl> so let me test something
[17:26] <teward> wxl
[17:26] <teward> so
[17:27] <teward> that's... not really as useful an explanation
[17:27] <teward> the fact is, Phab is already receiving mail
[17:27] <teward> and it sounds like this is a Phabricator side conig issue
[17:27] <wxl> did the one i sent to<EMAIL_ADDRESS>come through?
[17:28] <teward> Phab sees it as received yes
[17:28] <wxl> good
[17:28] <teward> wxl: the core problem is, *all* mail going to this box is received by phab
[17:29] <teward> with no additional configuration options needed
[17:29] <wxl> yep hold on
[17:29] <teward> so this sounds a lot more like a specific Phabricator side thing
[17:30] <wxl> yep hold on
[17:32] <wxl> hm
[17:32] <wxl> i wonder if this will work
[17:32] <wxl> it seems he has the mta domain set up as phab.lubuntu.me not lubuntu.me
[17:32] <wxl> but let's try
[17:33] <teward> wxl: hmm, well, I can't really change the domain, and you don't want all @lubuntu.me mail to route to this box
[17:33] -lugito:#lubuntu-devel- [T34: Configure email commands] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T34#882
[17:33] <teward> so you might have to set Phab's MTA domain to be phab.lubuntu.me
[17:34] <teward> wxl: was the 'testing' comment an email?
[17:34] <wxl> no
[17:35] -lugito:#lubuntu-devel- [T34: Configure email commands] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T34#883
[17:36] -lugito1:#lubuntu-devel- [T34: Configure email commands] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T34#885
[17:36] <wxl> YAY!
[17:37] <wxl> thank you teward :)
[17:37] <teward> wxl: did it work?
[17:37] <wxl> yep
[17:37] <teward> what did you have to change?
[17:37] <wxl> metamta.single-reply-handler-prefix = phab
[17:37] <teward> ah, well, there you go.
[17:37] <wxl> metamta.reply-handler-domain = phab.lubuntu.me
[17:38] <wxl> so what it does is use a reply to of<EMAIL_ADDRESS>as a reply to
[17:38] <teward> ah, I see.
[17:38] <teward> makes sense.
[17:38] -lugito:#lubuntu-devel- [T34: Configure email commands] teward (Thomas Ward) commented on the task: https://phab.lubuntu.me/T34#886
[17:38] <teward> wxl: well, at least it's working :)
[17:39] <wxl> yeah i guess in retrospect maybe the<EMAIL_ADDRESS>wasn't really necessary
[17:39] <teward> wxl: let me know if there's anything else I can assist with.  Note I did some pretty tight lockdown on the email side of things, to make it use strong TLS connections, etc.
[17:39] <teward> wxl: never hurts to still have it
[17:39] <wxl> absolutely
[17:39] <teward> i can redirect it to /dev/null if you want
[17:39] <teward> or we can keep it.
[17:40] <wxl> ask tsimonq2 but i'm inclinded to /dev/null it
[17:40] <wxl> it SHOULDN'T be valid
[17:41] <teward> *grabs the flamethrower*
[17:41] <teward> wxl: you can have Canonical SA remove it
[17:41] <teward> if you want.
[17:41] <wxl> naw it'll give us control
[17:41] <teward> now that Phab's reply-to works proper
[17:41] <teward> ack
[17:43] <teward> wxl: mail redir'd to /dev/null currently
[17:43] <teward> but we can tweak that later
[17:44] <teward> i'm going to go find coffee, let me know if there's anything else I can do to assist :)
[17:51] -lugito:#lubuntu-devel- [T34: Configure email commands] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T34#887
[18:00] -lugito:#lubuntu-devel- [T48: Make tweets automatically go to Mastodon] tsimonq2 (Simon Quigley) just created this task: https://phab.lubuntu.me/T48
 cat /dev/urandom | /dev/teward
[18:12] <teward> ERROR: UNSTABLE RESPONSE DETECTED, AUTOMATED SELFDESTRUCT ARMED, ANTIMATTER EXPLOSION IN 30 SECONDS.
[18:12] <teward> :P
[18:12] <teward> tsimonq2: oh your domain's SSL died, I'm redoing it
[18:12] <teward> also 'yay phab emails!'
 @teward, Thanks
[18:13] <teward> yep
[18:17] -lugito:#lubuntu-devel- [T48: Make tweets automatically go to Mastodon] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T48#897
[18:19] -lugito:#lubuntu-devel- [T34: Configure email commands] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T34#898
[18:22] -lugito:#lubuntu-devel- [T48: Make tweets automatically go to Mastodon] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T48#899
[18:29] -lugito:#lubuntu-devel- [T48: Make tweets automatically go to Mastodon] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T48#900
[18:32] -lugito:#lubuntu-devel- [T48: Make tweets automatically go to Mastodon] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T48#901
[18:38] -lugito1:#lubuntu-devel- [T48: Make tweets automatically go to Mastodon] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T48#902
[18:55] <wxl> jeez simon you and your unnecessary acks
[18:55] <teward> hah.
 @wxl, ur an unnecessary ack
 :P
[19:11] <wxl> well played
 omg ikr


[20:51] <smoser> harlowja, for the tox changes...
[20:51] <smoser> i want / need to be able to run 'make test' in package build
[20:51] <smoser> which doesn't have general access to inter-tubes
[21:04] <harlowja> smoser hmmm
[21:04] <harlowja> durn intertupes
[21:05] <harlowja> *tubes
[21:14] <astol> hi all, how do I tell cloud-init to run first boot commands again on next reboot? (ie reset first boot attribute)
[21:23] <smoser> astol, you can configure that in /etc/cloud/cloud.cfg
[21:24] <smoser> if you're just wanting '#!' things to run again, then you can change 'scripts_user' to be 'always'
[21:24] <smoser>  - [scripts_user, always]
[21:44] <astol> smoser: I am building an ami base image and since I have already booted once, I need to somehow reset that flag
[21:44] <astol> so when I create instances again from that ami first boot sequence will be executed
[21:45] <astol> I don't need to run them always, just one more time
[21:45] <natorious> wouldn't deleting the /var/lib/cloud dir be what you want then?
[21:46] <astol> natorious: well that's kind of what I did, but this felt so crude I decided to ask
[21:47] <astol> natorious: I honestly scanned cloud-init sources for 15 minutes, but saw nothing (being a non-pythonista)
[21:48] <astol> so I just delete /var/lib/cloud and that's all?
[21:48] <smoser> astol, thats fine. you dont need to change anything.
[21:48] <smoser> it will do that by design.
[21:48] <smoser> the user-scripts run "per-instance"
[21:48] <smoser> and "per-instance" is "whenever an instance-id changes".
[21:49] <smoser> 'rm -Rf /var/lib/cloud' would suffice, but it is not necessary.
[21:50] <astol> smoser: wow! that's actually even more nice, thanks :) I wonder if I'm the only guy asking about that
[21:52] <smoser> pretty much its all supposed to "just work" :)
[22:05] <smoser> this is pretty cool, we moight have 2 more datasources sometime ssoon
[22:06] <smoser> GCE and cloud-sigma.
[22:18] <harlowja> smoser u forogot mine! :-P
[22:18] <harlowja> thats 3
[22:18] <harlowja> ll
[22:18] <harlowja> *lol


[14:22] <usr2033> hi, im trying to install openstack-base bundle. i got "'certificates' missing, 'ovsdb' missing" error. How can i solve this?
[14:38] <parlos> usr2033 wrt. certificates, look up Vault.
[14:39] <parlos> https://discourse.charmhub.io/t/vault-and-ingress-how-does-it-work/1906/2 if for kubernetes, but its a start.
[14:39] <parlos> https://discourse.charmhub.io/t/vault-and-ingress-how-does-it-work/1906/2 is for kubernetes, but its a start.


[12:35] <oznt> hi guys, just a quick question: how does cloud init translate "set-passwords" in cloud_config_module to "cc_set_passwords" ? Can't figure this one out
[12:47] <oznt> Well, I found out myself : https://github.com/canonical/cloud-init/blob/7c88f96245535aacfac9b0b04d9c0d82ac2067f4/cloudinit/config/__init__.py
[13:12] <lucasmoura> blackboxsw, thansk for the review :) I will start working on the proposed changes today
[13:36] <Odd_Bloke> oznt: Was that your entire question, or is there anything else we can help you out with?
[13:38] <oznt> Odd_Bloke, that was the question
[14:18] <Odd_Bloke> OK, great. :)
[17:06] <Odd_Bloke> falcojr: I've pushed the requested changes to both https://github.com/canonical/cloud-init/pull/354 and https://github.com/canonical/cloud-init/pull/349 :)
[17:31] <falcojr> cool, I'll re-review now
[17:32] <falcojr> I've technically already approved on the second one, you just need another approval from a committer
[17:33] <usrdev> hello all - hope you are safe and well! just a quick question. when utilizing cloud-init to create templates, i have noticed that the startup script for network configuration is severely delayed. i have cloud-init to pull a DHCP lease, and this works without issue for directly standing up VM from an ISO. i am utilizing proxmox as the HV.
[17:33] <usrdev> is there something i am missing to make this DHCP lease request, quicker...
[17:42] <Odd_Bloke> blackboxsw: Can you add https://github.com/canonical/cloud-init/pull/349 to your list of PRs to double-check as core committer, please?
[17:44] <Odd_Bloke> We also didn't assign reviews today, and I'm first so I've taken #358.
[17:59] <blackboxsw> Odd_Bloke: yes I can/will
[18:40] <AnhVoMSFT> @Odd_Bloke, did you have a chance to take a look into the issue with the test_conftest having pylint error https://pastebin.ubuntu.com/p/QMkhNtShjW/
[19:30] <Odd_Bloke> AnhVoMSFT: I didn't, apologies!
[19:30] <Odd_Bloke> Let me take a quick look now.
[19:36] <Odd_Bloke> AnhVoMSFT: Hmm, could you give me a more recent log?  I'm seeing differences in package versions, and it's hard to tell if that's just because there have been releases in the past ~week.
[19:51] <Odd_Bloke> AnhVoMSFT: Hmm, actually, this is stranger than that.  I can reproduce the error if I give the exact path (i.e. `.tox/pylint/bin/python -m pylint cloudinit/tests/test_conftest.py`), but not if I only specify the directory (i.e. `.tox/pylint/bin/python -m pylint cloudinit/tests/`).  I'm also running Python 3.8 (instead of, I think, 3.5 in these logs).
[19:59] <Odd_Bloke> AnhVoMSFT: And I also can't reproduce on 3.5, using tox. :/
[20:08] <AnhVoMSFT> @Odd_Bloke yeah, I am having a hard time reproducing on my local machine - let me try with the .tox/pylint/bin/python. That should be the same version though
[20:10] <AnhVoMSFT> yes I can repro using that particular command
[20:10] <AnhVoMSFT> and I am on 3.5.2 on my xenial box (python3 --version)
[20:10] <AnhVoMSFT> the build server gets a new container every time it runs the test, so whatever is in .tox isn't cached between runs
[20:46] <Odd_Bloke> AnhVoMSFT: OK, I think we're dealing with some sort of pylint bug here: I see different output for `.tox/pylint/bin/python -m pylint -j1 cloudinit.tests.test_conftest cloudinit.tests.test_util` and `.tox/pylint/bin/python -m pylint -j1 cloudinit.tests.test_util cloudinit.tests.test_conftest`.  Can you confirm you see different behaviour also?
[20:56] <Odd_Bloke> AnhVoMSFT: I'm filing a pylint issue now, will drop the link here once I have done so.
[21:11] <Odd_Bloke> AnhVoMSFT: https://github.com/PyCQA/pylint/issues/3611
[21:20] <AnhVoMSFT> yes @Odd_Bloke I can confirm I am seeing different behaviors between those two commands
[21:21] <AnhVoMSFT> how did the different ordering could come up in one build environment vs the others though?
[21:21] <AnhVoMSFT> Oh, is this because the container we were running the test had only one core ?
[21:24] <AnhVoMSFT> @Odd_Bloke: I guess the question now is: which one of them was the right one? (I know we want a consistent behavior, but which one is the "right" consistent behavior?)
[21:39] <Odd_Bloke> AnhVoMSFT: So I think it's actually more likely that the container had many cores: I think the error is only reported if test_conftest is the _first_ module that a worker process tests (as I've just posted to the issue).
[21:40] <Odd_Bloke> (The number of CPUs in the host is almost certainly what pylint will discover.)
[21:41] <Odd_Bloke> AnhVoMSFT: So in this case, that test is specifically testing for behaviour when the wrong arguments are called (i.e. exactly what this pylint check is warning us about :p).  So it's a valid pylint error, which we should be ignoring in this specific case.
[21:41] <Odd_Bloke> However, I bet we also have a whole load of other instances of this error (or others which are similarly buggy).
[21:52] <blackboxsw> lucasmoura: thanks one minor nit on https://github.com/canonical/cloud-init/pull/359
[21:52] <blackboxsw> then we can land that