sch has quit [Quit: Gateway shutdown]
akossh has quit [Quit: Leaving.]
neimsaci has quit [Quit: WeeChat 4.0.5]
DFP has quit [Quit: Leaving]
<Wizzup> freemangordon: will do!
* Wizzup excited
<Wizzup> uvos: nov 4-5 I am at openfest again with a maemo leste stand, do you know what needs to be done to get our -devel kernel mz617 ready?
xmn has joined #maemo-leste
xmn has quit [Remote host closed the connection]
ahmed_sam has joined #maemo-leste
nyov has quit [Ping timeout: 255 seconds]
nyov has joined #maemo-leste
norly has quit [Quit: Leaving.]
norly has joined #maemo-leste
joerg has quit [Ping timeout: 255 seconds]
joerg has joined #maemo-leste
Juest has quit [Ping timeout: 255 seconds]
ahmed_sam has quit [Ping timeout: 245 seconds]
ceene has joined #maemo-leste
Juest has joined #maemo-leste
<freemangordon> Wizzup: hmm, so the issue with stacked windows appears after pressing the 'back' arrow, it somehow destroys the stack
<freemangordon> hmm, no, scratch that
<freemangordon> I suspect you want to continue the while() loop, but it will continue the for() one :)
<Wizzup> will check soon, sry
Daanct12 has joined #maemo-leste
uvos has joined #maemo-leste
<freemangordon> Wizzup: also, please elaborate - is this code supposed to implement support for multiple window stacks?
<freemangordon> stacks of stacked windows that is
Daanct12 has quit [Quit: WeeChat 4.0.5]
Daanct12 has joined #maemo-leste
ahmed_sam has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos__> freemangordon: certenly the gtk code dosent
<uvos__> it can only have a single stack per process, (a problem for sphone), so the qt code would have parity here
<freemangordon> uvos__: right, but currently it seems to me that qt code tries to do that, and fails :)
<freemangordon> I just want to understand what we want to do - do we want to support multiple chains?
<freemangordon> 'that' == multiple stacked windows stacks
ahmed_sam has quit [Read error: Connection reset by peer]
<Wizzup> freemangordon: back now
<freemangordon> Wizzup: hi!
<freemangordon> please see backscroll
<Wizzup> installing mafw-tracker-source atm, should I reboot to try it?
<Wizzup> (maybe easier)
<freemangordon> no reboot needed
<freemangordon> just install the new OMP
<Wizzup> I'm looking at xcb-maemo code now, and I'm not sure if the continue is wrong, but there I guess is some proble mwith the code
<freemangordon> the continue is wrong to me
<Wizzup> It sees three songs now :)
<freemangordon> the outer loop will be executed only once, no matter what
<freemangordon> good :)
<freemangordon> it takes time to index
<freemangordon> also, it does not index the whole fs, only some stuff in MyDocs, afaik
<Wizzup> oh
<freemangordon> like XDG_WHATEVER_DIR
<Wizzup> it doesn't use whatever the gnome tracker finds?
<Wizzup> or is that what the gnome tracker does
<freemangordon> this is gnome tracker :)
<freemangordon> so yes, it finds whatver gnome tracker finds
<Wizzup> it indexes home for me
<Wizzup> so on the code, I must admit I don't know whta it does right now
<Wizzup> given a window, it should set the stackable property
<freemangordon> ok, at could you remember what it is supposed to do
<freemangordon> ok, but what position
<Wizzup> and I think it needs to figure out what number to set that property to
<freemangordon> also, why it depends on the parent?
<Wizzup> because the parent contains the previous position
<freemangordon> but not on the last depth/position?
<freemangordon> why don't we just store in a static var?
akossh has joined #maemo-leste
<Wizzup> would make sense to me, I guess
<freemangordon> ok, I'll implement that
<freemangordon> we need to hook in show() / hide() as well I guess
pere has quit [Ping timeout: 255 seconds]
<Wizzup> freemangordon: ok, yes, I think I agree that the continue is wron
<Wizzup> g
<Wizzup> static var sounds good
<freemangordon> ok
neimsaci has joined #maemo-leste
<Wizzup> freemangordon: does omp itself show everything from the tracker?
<freemangordon> yes
<freemangordon> move your music to .sounds directory
<freemangordon> as a workaround
<Wizzup> ok
<Wizzup> and for videos, to .videos or so?
<freemangordon> or see how to tell tracker where to index
<freemangordon> yes
<Wizzup> well so the tracker already knows of my /var/lib/mpd/music/
<freemangordon> no idea how
<Wizzup> I told it about it months ago
<Wizzup> but yeah
<Wizzup> I will just try the way of least resistance first
<freemangordon> mhm
<freemangordon> it is some configuration we have to understand
<freemangordon> "See /etc/xdg/user-dirs.defaults and $HOME/.config/user-dirs.default"
<Wizzup> yeah I edited that juts now
<Wizzup> in gsettings
<freemangordon> yes, but we should already have those, no?
<freemangordon> also ,how do you edit gsettings?
<freemangordon> dconf?
<Wizzup> dconf-editor or gsettings
<Wizzup> well yeah but I added some dirs
<freemangordon> ok, but we should have user-dirs.conf
<freemangordon> why don't we have one?
<freemangordon> check fremantle
<freemangordon> oh, we have :)
<freemangordon> check ~/.config/user-dirs.dirs.leste
<freemangordon> so, everything is ok :)
<Wizzup> we should also have the non- .leste one
<Wizzup> but yeah
<Wizzup> I think we added it
<Wizzup> bbiab
pere has joined #maemo-leste
<freemangordon> yes, we have, as a link
pere has quit [Ping timeout: 258 seconds]
<Wizzup> freemangordon: that's normal btw, the symlink stuff
Daanct12 has quit [Quit: WeeChat 4.1.0]
ceene has quit [Ping timeout: 240 seconds]
xmn has joined #maemo-leste
<freemangordon> uvos: actually hildon supports multiple stacks, see http://maemo.org/api_refs/5.0/5.0-final/hildon/HildonWindowStack.html
<freemangordon> so yeah, then it makes sense qt to support that implicitly
<freemangordon> by using the parents
neimsaci has quit [Quit: WeeChat 4.0.5]
pere has joined #maemo-leste
gnarface has quit [Quit: Leaving]
gnarface has joined #maemo-leste
uvos__ has quit [Ping timeout: 255 seconds]
<freemangordon> dsc_: OMP is ready for UI fixes, if you are still interested in
uvos__ has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
<dsc_> freemangordon: sure thing
<uvos> freemangordon: yeah i know the per process thing is only in gtk
<uvos> in x11 the wm ofc dosent even know what process the window comes from
<uvos> (well besides the optional pid hint)
<freemangordon> hmm, I see tracker in top every now and then
<freemangordon> ugh, it coredumps :(
<freemangordon> what the?!? Thread 17 "single" received signal SIGSYS, Bad system call
<freemangordon> uvos: does this https://pastebin.com/2uq5EWyg make any sense to you?
<freemangordon> it seems our kernel lacks seccomp support
pere has joined #maemo-leste
<freemangordon> ok, tracker seccomp does not allow clock_gettime64()
<freemangordon> Wizzup: ok, we have to patch the tracker
<freemangordon> done, no more crashes
_whitelogger has joined #maemo-leste
ahmed_sam has joined #maemo-leste
uvos has quit [Read error: Connection reset by peer]
uvos__ has quit [Read error: Connection reset by peer]
uvos has joined #maemo-leste
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 272 seconds]
[TheBug] has quit [Ping timeout: 248 seconds]
uvos has quit [Ping timeout: 272 seconds]
Danct12 has left #maemo-leste [A-lined: This user has been AViVA-lined!]
Danct12 has joined #maemo-leste