[08:35] <pavlushka> I am facing a bug,  in thunar, file indexing service is malfunctioning.
[08:38] <pavlushka> when I open file a, it opens some file b in the same directory and then if I open file b, it opens file a, obviously of same type.
[08:39] <pavlushka> it happened in multiple occasions and for other directories.
[08:44] <pavlushka> will fsck fix this issue?
[08:51] <pavlushka> though the problem occurred in multiple partitions including root.
[10:11] <pavlushka> hi krytarik !
[10:12] <krytarik> Morning, pavlushka.
[10:13] <pavlushka> Morning, krytarik !
[10:15] <pavlushka> I am facing a bug,  in thunar, file indexing service is malfunctioning.
[10:16] <pavlushka> when I open file a, it opens some file b in the same directory and then if I open file b, it opens file a, obviously of same type.
[10:16] <pavlushka> it happened in multiple occasions and for other directories.
[10:16] <pavlushka> will fsck fix this issue?
[10:16] <pavlushka> though the problem occurred in multiple partitions including root.
[10:17] <flocculant> pavlushka: why do you find it necessary to repeat things 
[10:38] <pavlushka> flocculant, I repeated the thing after 1 hour 30 mins and after kryterik joined as he will not see that post, So I thought he might help, that's why.
[10:39] <flocculant> very odd issue though - not something I've come across
[10:43] <pavlushka> ok, I am filing a bug, but under which tag, thunar?
[10:43] <flocculant> not sure
[10:48] <dkessel> pavlushka: you could try something to see if thunar is the problem or the filesystem, which you are suggesting
[10:49] <pavlushka> but multiple file system at a time?
[10:49] <dkessel> you could open a terminal in the directory and try opening the file using xdg-open FILENAME
[10:50] <dkessel> if that opens another file, something is seriously wrong ;)
[10:53] <pavlushka> on it
[10:55] <flocculant> if it works properly - I'd install something like pcmanfm and try there as well
[10:56] <flocculant> you can also - add a user and try from there
[10:56] <flocculant> eliminate as much as possible before deciding it is a bug and not just local 
[11:16] <pavlushka> like to add, I faced the issue for newly copied or downloaded files, I've checked though not all possible, now I am not facing the issue in those particular cases , syncing delay I guess.
[12:38] <bluesabre> flocculant: apparently user name and details can be updated with AccountsService... which might be a bigger patch for mugshot, but should solve many more issues :)
[12:40] <flocculant> :)
[12:40] <bluesabre> basically found reports where KDE was having the same issue, and they just moved to that
[12:40] <flocculant> aah right
[12:40] <bluesabre> so, thats neat
[12:44] <flocculant> knome: not sure this is what you were expecting http://tracker.xubuntu.org/
[12:45] <bluesabre> flocculant: I imagine you're probably right
[12:45] <bluesabre> :D
[12:45] <flocculant> :)
[12:46] <flocculant> also - topic :)
[12:57] <bluesabre> Unit193: ^
[13:39] <bluesabre> oh wow
[13:39] <bluesabre> AccountsService is painless
[13:39] <bluesabre> after hiding the dbus stuff behind some methods, changing real name is as easy as
[13:40] <bluesabre> import AccountsServiceAdapter
[13:40] <bluesabre> adapter = AccountsServiceAdapter.MugshotAccountsServiceAdapter("bluesabre")
[13:40] <bluesabre> adapter.set_real_name("New Name")
[13:42] <bluesabre> no passwords necessary :D
[13:42] <flocculant> \o/
[13:43] <dkessel> yay
[13:48] <flocculant> as I thought - gnome software is designed to only show gui apps 
[13:48] <flocculant> I guess we'll need to note that somewhere when we release
[13:51] <bluesabre> seems like an interesting decision
[13:52] <bluesabre> apparently, for whatever reason, you can change all user details with AS except phone numbers
[13:52] <bluesabre> :\
[14:10] <flocculant> ha
[14:15] <flocculant> well gnome software thinks it's ok to leave dependencies behind as well - so hardly surprising - perhaps it can't see them once the gui app is removed :p
[14:51] <bluesabre> flocculant: getting ready to head out, should have a new mugshot somewhere later (probably after you're asleep)
[14:51] <bluesabre> some combo of pkexec and accounts service to cover all the bases
[14:51] <bluesabre> bbl
[15:04] <flocculant> bluesabre: ok - have a good day - speak tomorrow then perhaps :)
[16:30] <Unit193> bluesabre: Alright, congrats? :P  Keep in mind not everything exposed in Ubuntu is upstream though.
[18:31] <pleia2> social mediaed the wallpaper thing again
[20:02] <flocculant> knome: ty :)
[20:23] <knome> flocculant, np
[20:23] <knome> flocculant, and actually yeah, i could see that coming
[20:23] <knome> pleia2, should i ask canonical to discommission the subdomain?
[20:24] <pleia2> knome: yeah
[20:24] <knome> ok, doing that now
[20:26] <pleia2> will likely take a couple days, I think they're having all the holidays at the moment
[20:26] <knome> yeah, but at least it's then filed...
[20:27] <pleia2> :)
[20:29] <flocculant> thought it might be something like that :)
[20:30] <flocculant> I filed it under websitey things 
[20:30] <knome> and done
[20:30] <knome> oh, well
[20:31] <knome> flocculant, bug?
[20:31] <flocculant> not on launchpad - in my head :)
[20:32] <knome> hahah
[20:32]  * knome pokes flocculant's brain and adds an "inprogress" tag to the issue
[20:32] <flocculant> ha ha 
[20:32] <knome> oops, i touched the appetite nerve
[20:32] <knome> sorry! you'll always be hungry now
[20:32] <knome> wait... no change in that
[20:33] <flocculant> LOL
[20:42] <flocculant> mmm
[20:42] <flocculant> anyone got a xenial install handy
[20:43] <flocculant> nvm
[20:43] <flocculant> I must have turned it off :D
[20:46] <knome> hahah
[20:46] <knome> the brain?
[20:47] <flocculant> just checking bugs in the tracker :)
[20:47] <flocculant> bug 1543786 - looks fixed to me http://www.ubuntu.com/download/ubuntu-flavours
[20:48] <flocculant> knome: can the tracker look at all the 'affects' of a bug - and not leave it wip ? 
[20:48] <flocculant> for example - bug 1548647
[20:48] <flocculant> fix released for LO - and is
[20:49] <flocculant> but that bug has x-art as confirmed - and of course hundredpapercuts pointlessly added to it too
[20:49] <flocculant> no idea why he does that and NEVER actually fixes them
[20:49] <flocculant> cynicism would look at some sort of 'hey 100papercuts and it's fixed' thing 
[20:58] <knome> flocculant, that's hard because there is no "default" or "priority" target for bugs
[20:58] <knome> what if fixing the bug indeed required fixing 3 packages?
[20:59] <knome> i've been playing with the idea of moving the work item tracking to the code internally, eg. no loading from launchpad
[21:00] <knome> if i do that, then it's relatively easy to mark which packages we're interested to track per bug
[21:00] <knome> i mean at that point it's a relatively simple thing
[21:00] <knome> not automatical, but yeah
[21:01] <flocculant> ok - that makes sense as to why 
[21:01] <knome> so when all targets are "fix released", then the bug is "done"
[21:01] <knome> (just to confirm)
[21:01] <flocculant> yea
[21:02] <flocculant> except the 100 cuts - never get marked fixed - because it seems to be drive by adding of it anyway
[21:02] <knome> yes
[21:02] <knome> while think the situation is silly, i don't think i care enough to actually want to ignore any target specifically
[21:03] <flocculant> yep
[21:04] <flocculant> just a pita - go looking at the tracker - scratch your head - mmm I'm sure that's fixed 
[21:04] <flocculant> :)
[21:04] <knome> yes
[21:04] <knome> another option is to create an item for all targets for the bug individually
[21:05] <knome> eg. in this case three different items
[21:05] <bluesabre> Unit193: yup, got the code from upstream KDE and spec from Fedora
[21:05] <knome> apparently i can change statuses for papercuts
[21:06] <pleia2> \o/
[21:06] <knome> bluesabre, tell me again, was the openid auth a pain and were you able to get the team data from LP?
[21:07] <flocculant> knome: aah cool
[21:07] <flocculant> mmm
[21:07] <knome> but is the bug really fixed?
[21:07] <flocculant> actually so can I :p
[21:07] <knome> i mean, the status is not closed for x-a
[21:07] <knome> does that package still need something else?
[21:07] <knome> (unfortunately i haven't been following close enough to know)
[21:08] <flocculant> no idea - not the only one with 100 on it 
[21:08] <flocculant> knome: icons in LO is elementary 
[21:08] <knome> ok
[21:08] <bluesabre> knome: not generally a pain, but lp teams are addons to the spec
[21:09] <knome> bluesabre, can you confirm this is good and that we don't need changes to x-a?
[21:09] <knome> right
[21:09] <bluesabre> knome, the LO theme?
[21:09] <knome> yes
[21:10] <bluesabre> It's fixed, the theme is now upstream libreoffice, so x-a is not applicable anymore
[21:10] <knome> ok
[21:12] <knome> ok, bug dealt with, now booting desktop up
[21:13] <bluesabre> Thanks!
[21:15] <flocculant> bluesabre: did we decide in the end that bug 1513590 isn't actually a bug - but expected behaviour with it? 
[21:23] <flocculant> bluesabre: also "bluesabre to set up the next meeting"
[21:23] <knome> :)
[21:23] <knome> pleia2, would you be very angry at me if i just ported the tracker into a wordpress site? :P
[21:30] <tracker7> Desperately needs help over here
[21:30] <knome> who?
[21:30] <tracker7> me
[21:30] <knome> on what?
[21:30] <tracker7> on kernel(?) freezes
[21:31] <knome> when testing 16.04?
[21:31] <tracker7> tried 14.04 15.10 16.04
[21:31] <tracker7> 4.2 4.4 4.5 kernels
[21:32] <knome> then you are likely looking for the user support channel at #xubuntu
[21:33] <tracker7> ok, sry
[21:48] <pleia2> knome: another wordpress site /o\
[21:48] <knome> pleia2, that's why i asked first :P
[21:48] <pleia2> is it getting that complicated? 
[21:49] <knome> if possible, i would want to avoid the openid/LP auth hassle
[21:49] <knome> that would be one of the easy choices since canonical people have figured it out perfectly
[21:49] <pleia2> I mean, it's probably ok if we keep it updated and watch useage, but I've had to add caching to my wordpress instances of late because they're getting heafty
[21:49] <knome> but of course there are options
[21:49] <knome> and i'm not doing that *now*
[21:49] <knome> just thinking about the future
[21:50] <knome> that is, if we want to (mostly) move away from hammering the LP API every 30 mins
[21:50] <knome> for a completely different option, what do you think about basic auth?
[21:50] <pleia2> well, I wouldn't be very angry, but I'd want to make sure we'd evaluated our options sanely ;)
[21:51] <pleia2> basic auth?
[21:51] <knome> http basic auth
[21:51] <knome> :Ð
[21:52] <pleia2> oh, heh
[21:52] <pleia2> meh
[21:52] <knome> i know
[21:52] <knome> but hey, that's easy...
[21:52] <pleia2> I need to go eat food now
[21:52] <knome> lol
[21:52] <knome> does mentioning http basic auth make you hungry?
[21:52] <knome> anyway, bon appetit
[21:53] <knome> let's talk about this some other time/later
[21:57] <flocculant> night all
[21:57] <knome> nighty flocculant