<Wizzup> freemangordon: so I get the exact problem after I killed the processes, did a hard reset, removed any extra files
<Wizzup> same problems: tracker-extract starting constantly
<Wizzup> with was with mafw not even running
<Wizzup> this was*
akossh has quit [Quit: Leaving.]
slep has left #maemo-leste [#maemo-leste]
parazyd has quit [Ping timeout: 268 seconds]
parazyd has joined #maemo-leste
slep has joined #maemo-leste
rafael2k has joined #maemo-leste
sunshavi has quit [Ping timeout: 264 seconds]
rafael2k has quit [Ping timeout: 268 seconds]
joerg has quit [Ping timeout: 264 seconds]
joerg has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
<freemangordon> Wizzup: maybe try to do hard reset, remove both directories (.cache/tracker and .local/share/tracker/) and then start trackers
<freemangordon> if it still does not work, I am out of ideas
<freemangordon> and yes, mafw has nothing to do
xmn has joined #maemo-leste
arno11 has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
arno11 has joined #maemo-leste
<arno11> is it normal that my device (up-to-date) is not affected by trackers issue ?
<arno11> just to be sure
<freemangordon> seems the issue appears when there is a huge amount of music
<arno11> ok
<freemangordon> also, after the last experiments, my device does not suffer as well
<arno11> ah cool
<freemangordon> not really, as now i can't repro :)
Daanct12 has joined #maemo-leste
<arno11> ok :)
arno11 has left #maemo-leste [#maemo-leste]
pere has quit [Ping timeout: 245 seconds]
pere has joined #maemo-leste
xmn has quit [Ping timeout: 252 seconds]
dos has quit [Ping timeout: 256 seconds]
dos has joined #maemo-leste
<Wizzup> freemangordon: I did that
sch has quit [Ping timeout: 264 seconds]
sch has joined #maemo-leste
rafael2k has joined #maemo-leste
Daanct12 has quit [Quit: WeeChat 4.1.2]
<freemangordon> :(
rafael2k has quit [Ping timeout: 256 seconds]
<freemangordon> Wizzup: how many GB of music do you have?
<Wizzup> let me check
<Wizzup> # du -sh /mnt/sd/music/
<Wizzup> 17G/mnt/sd/music/
<freemangordon> ok
<freemangordon> I'll copy some more to the VM
<Wizzup> I wonder if we need to take a step back to try to figure out what's going on here
<Wizzup> this seems like such a grave tracker bug maybe something else is going on
<freemangordon> mhm
<freemangordon> for sure thre is a nasty memleak in mafw-tracker-source
<freemangordon> I already fixed, have to issue a build
<Wizzup> it looks like the tracker irc channel is mostly empty, probably the irc bridge is gone, so we'll have to install a matrix client to talk to gnome
<Wizzup> well, unless valgrind finds serious problems (not just with memleaks), I doubt they can cause the issues we are seeing
<Wizzup> so you are sure that the behaviour we are seeing is because one db is deleted, and the other doesn't realise, and the db gets deleted, why? do we know?
<freemangordon> yes, db gets deleted because tracker receives "CORRUPTED" result from some sqlite query
<freemangordon> but I can;t repro anyhmre
<Wizzup> and then they just decide to the delete the db? interesting
<freemangordon> on both my d4 and my VM after I deletet *all* tracker related files, I see no issue anymore
<Wizzup> I mean I'm happy to do it again, I just don't think it'll make a diff, sec
<freemangordon> so:
<freemangordon> stop ,mafw
<freemangordon> tracker reset -r
<Wizzup> mafw-source-tracker is stopped
<freemangordon> start mafw
<freemangordon> oh,sorry
<freemangordon> tracker reset -r
<Wizzup> I am confused now
<freemangordon> rm -rf ~/.cache/tracker
<freemangordon> rm -rf ~/.local/share/tracker/
<freemangordon> start mafw
<freemangordon> why?
<Wizzup> and then tracker daemon -s
<Wizzup> ?
<freemangordon> no need
<freemangordon> starting mafw will start the tracker
<freemangordon> why are you confused?
<Wizzup> I was confused when you wrote 'oh,sorry'
<Wizzup> in any case I did what you wrote above
<Wizzup> the only difference is that I didn't even run mafw, I just ran tracker daemon -s
<freemangordon> because I missed the 'rm -rf' steps :)
<Wizzup> to rule out mafw messing anything up
<freemangordon> I see
<freemangordon> anyway, I have 11GB on my VM
<freemangordon> the diff is that it is in MyDocs
<freemangordon> maybe that's the reason
<Wizzup> does mafw-dbus-wrapper honour /etc/profile.d btw?
Juest has quit [Ping timeout: 268 seconds]
<freemangordon> no idea
<freemangordon> what is in there?
<Wizzup> looks like it
<Wizzup> $ cat /etc/profile.d/tracker-maemo.sh
<Wizzup> export TRACKER_USE_LOG_FILES=1
<Wizzup> freemangordon: ^
<freemangordon> ah
<Wizzup> well so far only tracker-store is running, but maybe others will start eventually
<freemangordon> I am not sure what happens if started it from xsession file
<freemangordon> yes, they will
<freemangordon> I'll do the same here
<freemangordon> to see if it will fail this time
<freemangordon> (in the VM)
<Wizzup> right
<freemangordon> btw, how do you stop mafw?
<Wizzup> /usr/bin/mafw.sh stop mafw-tracker-source
<freemangordon> ok
<Wizzup> still only tracker-store
<Wizzup> 6 mins later
<freemangordon> yeah
<Wizzup> shall I run tracker daemon -s ?
<freemangordon> no
<Wizzup> when/how do these get started then?
<freemangordon> I guess tracker-store uses lots of cpu
<Wizzup> it's doing something still
<freemangordon> tracker daemon -f
<Wizzup> it just finished
<freemangordon> and?
<freemangordon> what does tracker daemon -f say?
pere has quit [Ping timeout: 255 seconds]
<Wizzup> freemangordon: following
<Wizzup> it's crawling various dirs
<Wizzup> and now is processing
<Wizzup> extractor not running yet
<freemangordon> ok
<freemangordon> hmm, why extractor is not running?
<freemangordon> it should
<freemangordon> ah, wait
<freemangordon> miner shall finish with crawling first
<Wizzup> yes
<Wizzup> now it is running on my d4
<Wizzup> brb
Juest has joined #maemo-leste
<freemangordon> ok, after copying some more music in the VM, it happened again
inky_ has joined #maemo-leste
inky_ has quit [Ping timeout: 268 seconds]
pere has joined #maemo-leste
<freemangordon> Wizzup: "(tracker-store:7084): Tracker-CRITICAL **: 16:49:35.135: SQLite error: database disk image is malformed (errno: Success)"
<Wizzup> do we have a line number for this somewhere?
<freemangordon> rebuilding tracker with debug symbols, will have it in few minutes
_inky has joined #maemo-leste
<freemangordon> Wizzup: ../src/libtracker-data/tracker-db-interface-sqlite.c:2346
<freemangordon> this is where g_unlink is called from
_inky has quit [Client Quit]
<freemangordon> so it comes from link 2341
inky1 has joined #maemo-leste
inky1 has quit [Client Quit]
<Wizzup> ok, I need to get vm started and apt-get source
<freemangordon> lemme run that under valgrind
<Wizzup> ah, you got it to the point where it doesn't actually remove the db? that's good
<Wizzup> (for testing)
<freemangordon> no
<freemangordon> I put a BP in g_unlink :)
<freemangordon> and it got hit right after that error
<freemangordon> so it does remove the db
<freemangordon> so, somehow, someone is corrupting the database
<freemangordon> and that seems to be for real
<Wizzup> SQLITE_CORRUPT isn't as bad as it sounds from my reading
<Wizzup> but yes, something is weird there
<freemangordon> it should not happen without a crash, no?
<freemangordon> btw, there are 3453 frames in the backtrace
<freemangordon> it seems to be executing huge query
<freemangordon> hundreds if not thousands of DELETE statements
xmn has joined #maemo-leste
<Wizzup> not sure why there should be so many frames if it's a big delete
<freemangordon> I suspect this is the final cleanup
<freemangordon> maybe they do a recursion
<Wizzup> *facedesk* :)
<freemangordon> yes, I see 2 functions again and again
<Wizzup> Maybe it runs out of stack depth then or something?
<Wizzup> it might also be that it runs out of the size limits they themselves set
<Wizzup> but still, this should happen to many people, no?
<freemangordon> ok, under valgrind there is no issue :(
<freemangordon> no idea
<freemangordon> lemme try again
inky1 has joined #maemo-leste
<Wizzup> I don't know if the page_size or cache_size have any effect here
<Wizzup> it looks like I've gotten into the same situation again btw
inky1 has quit [Client Quit]
<Wizzup> last update was 08 Dec 2023, 16:05:19: 69% Extractor - Extracting metadata 05m 55s remaining
<Wizzup> and now the extractor is always idle
<Wizzup> and the db 'seems' empty
inky has joined #maemo-leste
<Wizzup> interesting, my tracker-miner-fs has two db handles open it looks like
<Wizzup> at least judging from it's fds
<Wizzup> 0 lr-x------ 1 user user 64 Dec 8 16:12 10 -> '/home/user/.cache/tracker/meta.db (deleted)'
<Wizzup> 0 lrwx------ 1 user user 64 Dec 8 16:12 11 -> '/home/user/.cache/tracker/meta.db-wal (deleted)'
<Wizzup> 0 lrwx------ 1 user user 64 Dec 8 16:12 12 -> '/home/user/.cache/tracker/meta.db-shm (deleted)'
<Wizzup> 0 l-wx------ 1 user user 64 Dec 8 16:12 13 -> /home/user/.local/share/tracker/data/tracker-store.journal
<Wizzup> 0 lr-x------ 1 user user 64 Dec 8 16:12 14 -> anon_inode:inotify
<Wizzup> 0 lr-x------ 1 user user 64 Dec 8 16:12 15 -> '/home/user/.cache/tracker/meta.db (deleted)'
<Wizzup> 0 lrwx------ 1 user user 64 Dec 8 16:12 16 -> '/home/user/.cache/tracker/meta.db-wal (deleted)'
<Wizzup> looks like the same is true for tracker-extract, so maybe that means nothing
<Wizzup> (but the ones it looks at aren't deleted of course)
<freemangordon> it means that it was tracker-extract to delete the db
<Wizzup> it gets started every 15 seconds
<Wizzup> so I am not sure if that is true
<Wizzup> but your logs should tell you
<Wizzup> btw, I asked in the #gnome-tracker channel here just in case there would be a response
inky has quit [Quit: Leaving.]
<Wizzup> not sure if this is relevant, googling atm for 'SQLITE_CORRUPT gnome tracker'
<Wizzup> we do have this specific version
<Wizzup> (of sqlite3)
<Wizzup> do we have this?
<Wizzup> freemangordon: ^^
<freemangordon> I doubt
<Wizzup> well, we have 3.34.1-3
<Wizzup> and I have text files in my music
<freemangordon> mhm
<freemangordon> lemme pull that and retest
<Wizzup> he's also on irc but didn't respond yet
<Wizzup> he just did
<Wizzup> said 2.x is stagnant and not maintained, so that the problem is probably with updated deps (sqlite3), and that it would be best to switch to 3.x if we can
<Wizzup> 3.6.x specifically
<Wizzup> freemangordon: I'm getting a bit more confident this really is our problem
<freemangordon> mhm
<freemangordon> testing atm
<freemangordon> with the fix that is
<freemangordon> seems like
<freemangordon> lemme clone tracker
<Wizzup> freemangordon: btw, want to join #gnome-tracker even just to idle? the dev is somewhat chatty and then I won't have to relay the info
<Wizzup> he's linking me a list of changes from tracker 2-3, which you're probably aware of already (https://gnome.pages.gitlab.gnome.org/tracker/migrating-2to3.html)
<freemangordon> Wizzup: in the meanwhile, could you add tracker to jenkins?
<Wizzup> sure, I thought we already had it
<Wizzup> I guess we had miners?
<Wizzup> freemangordon: what repo name?
<freemangordon> tracker
<freemangordon> miners are separate repo
<Wizzup> added
<freemangordon> ok, thanks
elastic_dog has quit [Ping timeout: 260 seconds]
<freemangordon> fatal: Authentication failed for 'https://github.com/maemo-leste-upstream-forks/tracker/'
<Wizzup> freemangordon: hangon
<freemangordon> oh, wait
<freemangordon> my bad
<Wizzup> freemangordon: the repo is private
<Wizzup> want me to fix?
<freemangordon> fixed
<freemangordon> why private is the default?
<Wizzup> github :)
<Wizzup> idk
<Wizzup> they hate sharing I guess
<freemangordon> M$ you mean :)
<Wizzup> yes
elastic_dog has joined #maemo-leste
<freemangordon> Wizzup: please upgrade tracker to see if the issue is fixed for you
<freemangordon> hmm with the new tracker 11GB were indexed in less than a minute
<freemangordon> on d4 that is
<Wizzup> let me try
<freemangordon> i just reset the db
<freemangordon> and restarted mafw
<freemangordon> no manual deletion etc
<Wizzup> did you restart mafw?
<freemangordon> (18,36,09) freemangordon: and restarted mafw
<Wizzup> ah
<Wizzup> ha
<Wizzup> ok
<freemangordon> actually after db reset, I just killed mafw-tracker-source
<freemangordon> that's enough to trigger a new index
<Wizzup> doesn't look like mine will finish in a minute
<freemangordon> well...
<Wizzup> but hey, as long as it works :D
<freemangordon> you'd better pray for it to finish at all :p
<Wizzup> I'm not a religious man, but I'll sacrifice some plant
<freemangordon> me neither, but that does not mean we shall lose opportunities... what is... :)
<freemangordon> *what if
<Wizzup> actually it is going much faster now it seems
<freemangordon> mhm
<Wizzup> 08 Dec 2023, 17:43:41: 35% File System - Processing… 02m 55s remaining
<Wizzup> maybe some optimisations from our CI?
<freemangordon> I doubt
<freemangordon> but... who knows
<Wizzup> hah, now omp shows the right time indication as well
<Wizzup> it follows tracker daemon -f
<freemangordon> yes
<freemangordon> ok, if that's fixed, during the weekend I'll put xv support back in mafw-gst-renderer
<freemangordon> after that we can push all the recent work on multimedia to -stable
<Wizzup> cool
<Wizzup> agreed
<Wizzup> let's monitor pm meanwhile
<freemangordon> yeah
<Wizzup> I could probably use some help with telepathy on the sip/xmpp front, in debugging some issues
<freemangordon> sure
<freemangordon> did it finish?
<freemangordon> (tracker)
<Wizzup> still extracting
<Wizzup> probably 5 more mins
akossh has joined #maemo-leste
<freemangordon> 5 minutes passed :)
<Wizzup> 13:21 eta
<freemangordon> omg
<Wizzup> my files are complicated :)
<Wizzup> btw, there is telepathy-tank
<Wizzup> we have it packaged I think (I packaged it)
<Wizzup> but I didn't get it to work yet with conversations
<freemangordon> we will need accounts plugin I guess
<Wizzup> well there was more to it
xmn has quit [Ping timeout: 255 seconds]
<Wizzup> as in, I got the account set up
<Wizzup> but I only got it to connect once iirc
<Wizzup> 4 mins left
<Wizzup> eta is a bit off:p
<freemangordon> I wonder why it is so slow on your device
<freemangordon> how complicated could a music be?
<Wizzup> I don't know where you get it from, but I ripped a lot of it from CDs using custom sw that adds all kinds of metadata and embeds images in the files
<Wizzup> some of it is flac too
<Wizzup> 08 Dec 2023, 18:20:39: ✓ Extractor - Idle
<Wizzup> let's see
<Wizzup> brb, have to make some dinner
<Wizzup> looks like tracker is pacified for now
rafael2k has joined #maemo-leste
<freemangordon> yeah
rafael2k has quit [Ping timeout: 264 seconds]
parazyd has quit [Ping timeout: 252 seconds]
parazyd has joined #maemo-leste
<Wizzup> btw, I took a quick look earlier today what would 'break' without python2 and pygtk2 and hildon pkgs in python
<Wizzup> these packages will not work anymore: binaryclock-plugin, quicknote, sojourner, syncevolution-frontend, modrana
<Wizzup> from extras
<Wizzup> which depend on one or more of these:
<Wizzup> python2-gconf python-conic python-hildon python-hildondesktop python-location python-mafw python-osso
rafael2k has joined #maemo-leste
<freemangordon> Wizzup: did you unpack your PPP?
<Wizzup> freemangordon: no, but I can tomorrow, or in ~2 hours or so
<freemangordon> ok, lets try to find some time tomorrow to look at h-d issue
<freemangordon> that's pointed to me as well
<Wizzup> ok
rafael2k has quit [Ping timeout: 255 seconds]
DPA2 is now known as DPA
LjL has quit [Read error: Connection reset by peer]
LjL has joined #maemo-leste
uvos has joined #maemo-leste
k1r1t0 has joined #maemo-leste
k1r1t0 has quit [Quit: leaving]
k1r1t0 has joined #maemo-leste
<uvos> tmlind: so even with mainline 6.6.4 - no cpufreq for me
<uvos> cpufreq_dt isent loaded by default loading it by hand dosent help
<uvos> nothing usefull in dmesg, of_node/operating-points is present
<uvos> i dont get it
<uvos> thats the dts i booted with
<uvos> cpu nodes looks fine to me
<uvos> diffing it compeared to the leste stock dts dosent reveal anything suspiciously missing or anything
xmn has joined #maemo-leste
<Wizzup> uvos: btw if you upgrade tracker the problem should disappear