ALHP/ALHP.GO
6
42
Fork 9
Code Issues 25 Pull Requests Projects Releases Wiki Activity

tracker3 still in database after build failed #46

New Issue
Closed
opened 2021-10-04 15:15:19 +02:00 by Timo · 20 comments
Timo commented 2021-10-04 15:15:19 +02:00
Copy Link

Pre system upgrade works fine, post tracker3 stops working. Verified with removing the repo and running a full downgrade, check functionality, and then upgrading again.

❯ G_MESSAGE_DEBUG=all nautilus
** Message: 15:12:30.002: Connecting to org.freedesktop.Tracker3.Miner.Files

** (org.gnome.Nautilus:2402): WARNING **: 15:13:00.032: Unable to create connection for session-wide Tracker indexer: Timeout was reached

** (org.gnome.Nautilus:2402): WARNING **: 15:13:00.032: Could not establish a connection to Tracker: Timeout was reached

Checking logs:

Oct 04 15:12:31 mauve tracker-miner-fs-3[2420]: /usr/lib/tracker-miner-fs-3: symbol lookup error: /usr/lib/tracker-miner-fs-3: undefined symbol: tracker_resource_set_datetime

Oct 04 15:12:31 mauve systemd[651]: tracker-miner-fs-3.service: Main process exited, code=exited, status=127/n/a
Pre system upgrade works fine, post tracker3 stops working. Verified with removing the repo and running a full downgrade, check functionality, and then upgrading again. ``` ❯ G_MESSAGE_DEBUG=all nautilus ** Message: 15:12:30.002: Connecting to org.freedesktop.Tracker3.Miner.Files ** (org.gnome.Nautilus:2402): WARNING **: 15:13:00.032: Unable to create connection for session-wide Tracker indexer: Timeout was reached ** (org.gnome.Nautilus:2402): WARNING **: 15:13:00.032: Could not establish a connection to Tracker: Timeout was reached ``` Checking logs: ``` Oct 04 15:12:31 mauve tracker-miner-fs-3[2420]: /usr/lib/tracker-miner-fs-3: symbol lookup error: /usr/lib/tracker-miner-fs-3: undefined symbol: tracker_resource_set_datetime Oct 04 15:12:31 mauve systemd[651]: tracker-miner-fs-3.service: Main process exited, code=exited, status=127/n/a ```
anonfunc commented 2021-10-04 15:20:14 +02:00
Owner
Copy Link

Hello @Timo,

I'm going to requeue tracker3-miners to see if that fixes it.

Hello @Timo, I'm going to requeue `tracker3-miners` to see if that fixes it.
anonfunc commented 2021-10-04 15:28:58 +02:00
Owner
Copy Link

Rebuild of tracker3-miners just finished. Can you redownload (you should get a signature error on first try) und retest if the issue still exists?

Rebuild of `tracker3-miners` just finished. Can you redownload (you should get a signature error on first try) und retest if the issue still exists?
anonfunc added the
bug
 label 2021-10-04 15:29:13 +02:00
Timo commented 2021-10-04 15:41:27 +02:00
Author
Copy Link

Still exists unfortunately. I'll see what happens if I manually recompile it locally on my system (albeit a bit differently). :)

Still exists unfortunately. I'll see what happens if I manually recompile it locally on my system (albeit a bit differently). :)
anonfunc commented 2021-10-04 15:44:32 +02:00
Owner
Copy Link

Did you try downgrading to the official package version via pacman -S extra/tracker3-miners and checking if the issue still occurs? If so maybe we rebuild the wrong package.

Did you try downgrading to the official package version via `pacman -S extra/tracker3-miners` and checking if the issue still occurs? If so maybe we rebuild the wrong package.
Timo commented 2021-10-04 15:46:42 +02:00
Author
Copy Link

Nope also breaks with Clang 14 with -Ofast

Did you try downgrading to the official package version via pacman -S extra/tracker3-miners

Yes. Works.

Oct 04 15:48:34 mauve systemd[658]: Starting Tracker file system data miner...
Oct 04 15:48:34 mauve dbus-daemon[683]: [session uid=1000 pid=683] Successfully activated service 'org.freedesktop.Tracker3.Miner.Files'

Oct 04 15:48:34 mauve systemd[658]: Started Tracker file system data miner.
Oct 04 15:48:34 mauve dbus-daemon[683]: [session uid=1000 pid=683] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.65' (uid=1000 pid=2003 comm="/usr/lib/tracker-miner-fs-3 ")

Oct 04 15:48:34 mauve systemd[658]: Starting Tracker metadata extractor...
Oct 04 15:48:34 mauve dbus-daemon[683]: [session uid=1000 pid=683] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'

Oct 04 15:48:34 mauve systemd[658]: Started Tracker metadata extractor.
Nope also breaks with Clang 14 with -Ofast > Did you try downgrading to the official package version via pacman -S extra/tracker3-miners Yes. Works. ``` Oct 04 15:48:34 mauve systemd[658]: Starting Tracker file system data miner... Oct 04 15:48:34 mauve dbus-daemon[683]: [session uid=1000 pid=683] Successfully activated service 'org.freedesktop.Tracker3.Miner.Files' Oct 04 15:48:34 mauve systemd[658]: Started Tracker file system data miner. Oct 04 15:48:34 mauve dbus-daemon[683]: [session uid=1000 pid=683] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.65' (uid=1000 pid=2003 comm="/usr/lib/tracker-miner-fs-3 ") Oct 04 15:48:34 mauve systemd[658]: Starting Tracker metadata extractor... Oct 04 15:48:34 mauve dbus-daemon[683]: [session uid=1000 pid=683] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' Oct 04 15:48:34 mauve systemd[658]: Started Tracker metadata extractor. ```
👍 1
anonfunc commented 2021-10-04 15:50:12 +02:00
Owner
Copy Link

Did you try downgrading to the official package version via pacman -S extra/tracker3-miners

Yes. Works.

Okay that's definitively one for the blacklist then. Just added it. Thanks for your time figuring this out :)

> > Did you try downgrading to the official package version via pacman -S extra/tracker3-miners > > Yes. Works. Okay that's definitively one for the blacklist then. Just added it. Thanks for your time figuring this out :)
Timo commented 2021-10-04 16:00:19 +02:00
Author
Copy Link

No problem. Been wondering for a while why my nautilus was doing this but finally checked logs lol. Have a nice day :)

No problem. Been wondering for a while why my nautilus was doing this but finally checked logs lol. Have a nice day :)
🎉 1
Timo closed this issue 2021-10-04 16:00:19 +02:00
Timo commented 2021-10-04 16:37:15 +02:00
Author
Copy Link

Update: A whoopsie happened.

The mirror i used stopped updating their packages. My stock Arch package of tracker3-miners was version 3.1.2. After I upgraded from new mirrors made via reflector, tracker3-miners was upgraded to 3.2.0, and subsequentially failed again. Is the 3.2.0 package just broken?

I'm currently extremely confused about why my pacman mirrorlist isn't working properly.

Update: A whoopsie happened. The mirror i used stopped updating their packages. My stock Arch package of tracker3-miners was version 3.1.2. After I upgraded from new mirrors made via reflector, `tracker3-miners` was upgraded to 3.2.0, and subsequentially failed again. Is the 3.2.0 package just broken? I'm currently extremely confused about why my pacman mirrorlist isn't working properly.
Timo reopened this issue 2021-10-04 16:37:15 +02:00
anonfunc commented 2021-10-04 16:44:48 +02:00
Owner
Copy Link

That is certainly one possibility. I already checked the Arch bugtracker to no avail.

There is a staging version of tracker3-miners, but the commit mentions a rebuild of some dep. which was not pushed out of staging yet AFAIK.

That is certainly one possibility. I already checked the Arch bugtracker to no avail. There is a staging version of `tracker3-miners`, but the commit mentions a rebuild of some dep. which was not pushed out of staging yet AFAIK.
Timo commented 2021-10-04 16:47:40 +02:00
Author
Copy Link

After some more looking, to me it seems the reason it broke wasn't quite a bad package, but not all packages have been upgraded properly.

tracker3 on Arch is on 3.2.0, while on here it seems to be 3.1.2, while tracker3-miners has been upgrade to 3.2.0? Or is my pacman acting up?

E: Nope, your tracker3 package is on 3.1.2, just checked. Presumably that's why it broke.

After some more looking, to me it seems the reason it broke wasn't quite a bad package, but not all packages have been upgraded properly. `tracker3` on Arch is on 3.2.0, while on here it seems to be 3.1.2, while `tracker3-miners` has been upgrade to 3.2.0? Or is my pacman acting up? E: Nope, your `tracker3` package is on 3.1.2, just checked. Presumably that's why it broke.
anonfunc commented 2021-10-04 16:51:19 +02:00
Owner
Copy Link

Only one bug is open on tracker3-miner. I thought that its not relevant, since you see no SEGV, but maybe it is relevant. Some of the commenters observe the same behavior as you observe.

https://bugs.archlinux.org/task/69167

tracker3 on Arch is on 3.2.0, while on here it seems to be 3.1.2, while tracker3-miners has been upgrade to 3.2.0? Or is my pacman acting up?

If it would be build it would be 3.2.0+6+gfffef2772-1.1. So you should see no tracker3-miner in [extra-x86-64-v3] currently.

https://alhp.harting.dev/packages.html#extra-x86-64-v3-tracker3-miners

Only one bug is open on `tracker3-miner`. I thought that its not relevant, since you see no SEGV, but maybe it is relevant. Some of the commenters observe the same behavior as you observe. https://bugs.archlinux.org/task/69167 > tracker3 on Arch is on 3.2.0, while on here it seems to be 3.1.2, while tracker3-miners has been upgrade to 3.2.0? Or is my pacman acting up? If it would be build it would be `3.2.0+6+gfffef2772-1.1`. So you should see no `tracker3-miner` in **[extra-x86-64-v3]** currently. https://alhp.harting.dev/packages.html#extra-x86-64-v3-tracker3-miners
Timo commented 2021-10-04 16:54:13 +02:00
Author
Copy Link

Updated both packages from Arch (which means versions match 3.2.0 now) and it works. This most definitely seems like you or your script missed an update to it 🤔

E: Ah so the reason it's not there is a failed build.

So the tracker3-miners on 3.2.0 caused issues due to a failed build of tracker3 3.2.0, therefore had a missing symbol. Makes sense

Updated both packages from Arch (which means versions match 3.2.0 now) and it works. This most definitely seems like you or your script missed an update to it 🤔 E: Ah so the reason it's not there is a failed build. So the tracker3-miners on 3.2.0 caused issues due to a failed build of tracker3 3.2.0, therefore had a missing symbol. Makes sense
anonfunc commented 2021-10-04 16:57:52 +02:00
Owner
Copy Link

E: Ah so the reason it's not there is a failed build.

No, it was build successful previously. Now its blacklisted, so no build is happening. I rebuild it just a hour ago, so it definitely build, and as far as I remember the version matched as well.

So the tracker3-miners on 3.2.0 caused issues due to a failed build of tracker3 3.2.0, therefore had a missing symbol. Makes sense

Dependencies are not sourced from the ALHP repos, but from the official repos. So there can be no correlation between a failed ALHP build and a failed dependency of that package in ALHP.

> E: Ah so the reason it's not there is a failed build. No, it was build successful previously. Now its blacklisted, so no build is happening. I rebuild it just a hour ago, so it definitely build, and as far as I remember the version matched as well. > So the tracker3-miners on 3.2.0 caused issues due to a failed build of tracker3 3.2.0, therefore had a missing symbol. Makes sense Dependencies are not sourced from the ALHP repos, but from the official repos. So there can be no correlation between a failed ALHP build and a failed dependency of that package in ALHP.
Timo commented 2021-10-04 16:59:08 +02:00
Author
Copy Link

No, it was build successful previously. Now its blacklisted

Should've clarified I was referring to tracker3, not tracker3-miners

image

tracker3 failed due to this: tracker/meson.build:83:0: ERROR: python3 is missing modules: tap

> No, it was build successful previously. Now its blacklisted Should've clarified I was referring to tracker3, not tracker3-miners ![image](/attachments/b8cf1352-f9ab-49e7-aed4-ab38bf8069f4) tracker3 failed due to this: `tracker/meson.build:83:0: ERROR: python3 is missing modules: tap`
image.png
4.0 KiB
anonfunc commented 2021-10-04 17:02:00 +02:00
Owner
Copy Link

Yeah I noticed just now you were talking about tracker3. That most likely happened because of a bug few weeks back when failed packages were not removed.

I'll remove tracker3, maybe we can build tracker3-miner again after that?

Yeah I noticed just now you were talking about `tracker3`. That most likely happened because of a bug few weeks back when failed packages were not removed. I'll remove `tracker3`, maybe we can build `tracker3-miner` again after that?
Timo commented 2021-10-04 17:04:28 +02:00
Author
Copy Link

maybe we can build tracker3-miner again after that

Once both packages succeed to build I'm sure it'll be fine. Currently running builds on both to verify :)

> maybe we can build tracker3-miner again after that Once both packages succeed to build I'm sure it'll be fine. Currently running builds on both to verify :)
anonfunc commented 2021-10-04 17:10:03 +02:00
Owner
Copy Link

I removed tracker3 so you should get its latest version now. I removed tracker3-miner from the blacklist to see if it works with the now up-to-date tracker3.

image

Can you retest if all works now?

I removed `tracker3` so you should get its latest version now. I removed `tracker3-miner` from the blacklist to see if it works with the now up-to-date `tracker3`. ![image](/attachments/8b2aa7b0-184a-49dd-a1c1-21ac4aa07a89) Can you retest if all works now?
tracker3.png
22 KiB
Timo commented 2021-10-04 17:24:06 +02:00
Author
Copy Link

tracker3-miner from you, tracker3 from Arch, works, all 3.2.0.

So the issue was mismatching versions. Pulling from official Arch repos worked because my mirrors haven't updated their packages, annoyingly.

`tracker3-miner` from you, `tracker3` from Arch, works, all 3.2.0. So the issue was mismatching versions. Pulling from official Arch repos worked because my mirrors haven't updated their packages, annoyingly.
anonfunc commented 2021-10-04 17:30:49 +02:00
Owner
Copy Link

So the issue was mismatching versions. Pulling from official Arch repos worked because my mirrors haven't updated their packages, annoyingly.

Well, it happens. Good that we figured it out in the end 👍 .

I have gone through all packages after that bug happened and I figured I caught all. Must have missed some.

> So the issue was mismatching versions. Pulling from official Arch repos worked because my mirrors haven't updated their packages, annoyingly. Well, it happens. Good that we figured it out in the end 👍 . I have gone through all packages after that bug happened and I figured I caught all. Must have missed some.
anonfunc changed title from Tracker3 breaks after a system upgrade causing nautilus to stall on search (wait for timeout) to tracker3 still in database after build failed 2021-10-04 17:33:16 +02:00
anonfunc commented 2021-10-07 16:54:35 +02:00
Owner
Copy Link

Closing this now, please reopen if you encounter any more issues.

Closing this now, please reopen if you encounter any more issues.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked upstream
bug
Something is not working
build-failure
package build fails
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
informational
Provides information about something
invalid
Something is wrong
invalid/corrupt package
Package needs to be rebuild
packaging issue
priority: high
High priority
question
More information is needed
support
wontfix
This won't be fixed
No Label
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
anonfunc
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ALHP/ALHP.GO#46
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?