| Wizzup | freemangordon: hm, well, the tracker indexed my stuf and then removed itall again | 03:12 |
|---|---|---|
| freemangordon | Wizzup: no idea | 06:47 |
| freemangordon | maybe check the status | 06:47 |
| freemangordon | or runt tracker-extract from the shell | 06:47 |
| Wizzup | freemangordon: now it's ok again | 08:46 |
| Wizzup | oh, no, empty again :D | 08:46 |
| Wizzup | I will tell it not to recurse home | 08:47 |
| Wizzup | maybe this makes it unhappy | 08:47 |
| freemangordon | Wizzup: better try to find what happens | 08:52 |
| freemangordon | like, maybe attach gdb or run it manually with -v3 | 08:52 |
| freemangordon | and G_MESSAGES_DEBUG-all | 08:52 |
| freemangordon | *=all | 08:52 |
| Wizzup | I don't even know if it crashes though | 09:01 |
| Wizzup | I guess I need to stop it all first, and then what? | 09:01 |
| Wizzup | df -h | 09:02 |
| Wizzup | oops | 09:02 |
| Wizzup | yeah, same thing, it seems | 09:08 |
| Wizzup | maybe somehow starting omp / mafw-tracker-source made it drop all its entries | 09:08 |
| freemangordon | ok, stop mafw-tracker-source and then reset | 09:09 |
| freemangordon | /usr/bin/mafw.sh stop mafw-tracker-source | 09:09 |
| Wizzup | so stop with dsmetool, then tracker reset --hard, then G_MESSAGES_DEBUG=all /usr/libexec/tracker-miner-fs -n -v 3 | 09:09 |
| Wizzup | and then /usr/bin/mafw.sh start mafw-tracker-source | 09:10 |
| Wizzup | (after a bit) | 09:10 |
| freemangordon | no | 09:10 |
| freemangordon | stop mafw, reset db, start mafw | 09:10 |
| freemangordon | lets see if it will recover | 09:11 |
| freemangordon | if not, then we'll see what to do | 09:11 |
| Wizzup | so it will start the tracker? | 09:11 |
| freemangordon | yes | 09:11 |
| Wizzup | I doubt it will since I've done this many times throug reboot, but will try | 09:11 |
| Wizzup | how tracker actually mines is a mystery to me too | 09:12 |
| freemangordon | maybe I'll have to change tracker source to not keep permanent connection to the tracker | 09:12 |
| freemangordon | as this seems to keep sqlite db opened | 09:12 |
| freemangordon | and tracker reset *deletes* the db | 09:12 |
| freemangordon | and it becomes a mess | 09:12 |
| Wizzup | ok | 09:13 |
| Wizzup | it's running again | 09:13 |
| freemangordon | wild guess, but that's what I suppose happens | 09:13 |
| Wizzup | what's kind of weird is that tracker finds some files immediately, but the rest it will index much later or something | 09:13 |
| freemangordon | we have miners and then extract | 09:14 |
| freemangordon | those run in separate "passes" | 09:14 |
| Wizzup | ok | 09:14 |
| Wizzup | well it's doing something now, so I'll wait | 09:14 |
| Wizzup | whatever it did, it's back to very few files again | 09:18 |
| Wizzup | tracker search -m | wc -l | 09:18 |
| Wizzup | this was 500+ just minutes ago | 09:18 |
| Wizzup | (2 means 0) | 09:18 |
| Wizzup | now stopping mafw and trying to see if it doesn't go down | 09:19 |
| freemangordon | something is crashing it | 09:20 |
| Wizzup | but the tracker processes themselves don't seem to crash | 09:20 |
| Wizzup | like, it's not like their start time changes | 09:20 |
| freemangordon | hmm | 09:20 |
| Wizzup | afaict | 09:20 |
| freemangordon | no idea then | 09:20 |
| freemangordon | actually | 09:20 |
| freemangordon | try one more h | 09:21 |
| freemangordon | thing: | 09:21 |
| freemangordon | stop mafw, reset the tracker and delete /home/user/.cache/tracker/ | 09:21 |
| Wizzup | ok, even with mafw-tracker-source not running it does the same thing | 09:22 |
| Wizzup | (tracker-miner-fs:11224): Tracker-DEBUG: 16:21:40.959: tracker-extract vanished, maybe restarting. | 09:22 |
| Wizzup | hm | 09:22 |
| freemangordon | riht | 09:22 |
| freemangordon | *right | 09:22 |
| freemangordon | do tracker daemon -t | 09:23 |
| Wizzup | ok, they are terminated | 09:23 |
| freemangordon | and then G_MESSAGES_DEBUG=all /usr/libexec/tracker-extract -v3 | 09:23 |
| Wizzup | -v 3 | 09:23 |
| Wizzup | but yes | 09:23 |
| freemangordon | yeah | 09:23 |
| freemangordon | my kbd misbehaves somethimes | 09:23 |
| Wizzup | it just stops after inactivity | 09:23 |
| freemangordon | ok, delete the databes folder | 09:24 |
| Wizzup | should it run while miner is running? | 09:24 |
| Wizzup | seems like it | 09:24 |
| freemangordon | *database | 09:24 |
| freemangordon | rm -fr /home/user/.cache/tracker/ | 09:24 |
| Wizzup | it's running atm, should I stop it? | 09:25 |
| Wizzup | if it's going to crash this might trigger it too | 09:25 |
| freemangordon | stop it then | 09:25 |
| freemangordon | and the delete the db | 09:25 |
| Wizzup | ok | 09:27 |
| Wizzup | and then only start extract | 09:27 |
| Wizzup | ? | 09:27 |
| freemangordon | and then tracker daemon -s | 09:28 |
| freemangordon | if that does not wok, later on I will request remote shell :) | 09:28 |
| Wizzup | ok | 09:30 |
| Wizzup | it's running atm | 09:30 |
| Wizzup | it just stops by itself after there is no more to do, no crash | 09:34 |
| freemangordon | is it ok now? | 09:35 |
| Wizzup | currently, yes, but it's been like this before | 09:35 |
| Wizzup | I will leave it like this fo a bit before I start mafw | 09:36 |
| freemangordon | ok, start mafw | 09:36 |
| freemangordon | have to run, bbl | 09:40 |
| Wizzup | currently it looks ok | 09:42 |
| Wizzup | let's see if it continues | 09:42 |
| Wizzup | still fine currently | 10:11 |
| Wizzup | still stable, will reboot and see what happens | 11:43 |
| Wizzup | uvos: tmlind: so the trick is to just install kexecboot and then one can boot to stock android and/or the sdcard, right? | 14:02 |
| Wizzup | do we need a certain android version? | 14:03 |
| * Wizzup should re-read the logs from like last year | 14:03 | |
| sicelo | anyone on N900, i'm curious to see what you get from `busctl call org.ofono /n900_0 org.ofono.NetworkRegistration GetProperties` | 15:29 |
| sicelo | you could mask off the lac and cid if necessary | 15:29 |
| sicelo | seems to me N900 does not report operator name, at least not in a 'normal | 15:32 |
| sicelo | way | 15:32 |
| sicelo | it's not critical, of course, since, after doing a scan, you can get operator name from the /n900_0/operator/xxxxx path, but i'm still curious nonetheless | 15:48 |
| sicelo | and would like to fix it at some point, since actually the operator name is constantly being sent to ofono by the modem | 15:48 |
| sicelo | ah, this happens only on some operators ... on a different sim, operator name is filled in perfectly ootb | 19:07 |
| uvos | Wizzup: you install kexecboot on androids cache partition | 20:21 |
| uvos | android still sortof works after that, but its wonky | 20:21 |
| uvos | mostly you can still use it for charging, wich is important because the mianline kernel and bearly charge the device | 20:22 |
| uvos | as it has a extra charging chip for that that is currently not supported | 20:22 |
| uvos | and cpcap cant really keep up with the tablets bigger power draw, nor can it really put a dent into the huge battery in resonable timespans | 20:22 |
| uvos | mz617 has no sdcard reader | 20:23 |
| uvos | you can install an extreamly limited rootfs without breaking android further | 20:23 |
| uvos | realistcly you need to overwrite at least the exdata partiton, causeing even more issues for android | 20:24 |
| uvos | unfortinatly because of the power and storage issues, its quite easy to end up in at least a soft brick | 20:24 |
| uvos | i frankly dont see a resonable user frendly way to install leste on mz617 for now | 20:26 |
| uvos | mz609 is more frendly to our purposes | 20:26 |
| uvos | some of the european versions also have a sdcard reader, im not quite sure which however | 20:27 |
| uvos | but they have no modem so, you lose that then | 20:27 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!