Bug 1222949

Summary: bijiben fail to start for the first time
Product: [openSUSE] openSUSE Distribution Reporter: Grace Wang <grace.wang>
Component: GNOMEAssignee: Alynx Zhou <alynx.zhou>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: alynx.zhou, grace.wang, heiko.rommel, yfjiang, zcjia
Version: Leap 15.5Flags: alynx.zhou: SHIP_STOPPER?
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Grace Wang 2024-04-17 08:18:58 UTC
Env:
openSUSE Leap 15.5
GNOME version 41.8
Windowing System Wayland

Steps:
1. Install all the available updates and reboot
2. Launch gnome-terminal -> type bijiben and press Enter

Actual Result:
bijiben fail to start for the first time due to the below errors:

================================================================================
gracew@gracewang:~> bijiben
Tracker-Message: 16:11:11.784: Corrupt database: failed to create integrity_check statement: no such tokenizer: TrackerTokenizer

** (bijiben:28900): WARNING **: 16:11:11.795: Unable to connect to Tracker: Corrupt db file

** (bijiben:28900): WARNING **: 16:11:11.795: Cannot initialize BijiManager: Corrupt db file

================================================================================

Additional Info:
If we try to launch bijiben one more time, then it can be started but lots of below errors shown:
================================================================================
(bijiben:28684): Tracker-CRITICAL **: 16:08:32.602: SQLite error: database disk image is malformed (errno: No such file or directory)
================================================================================
Comment 2 Alynx Zhou 2024-04-18 07:40:44 UTC
I'll backport the fix.
Comment 3 Alynx Zhou 2024-04-18 08:47:59 UTC
I manually re-write the patch because tracker changed it's code structure between 3.2 and 3.6, please try package from <https://download.opensuse.org/repositories/home:/AZhou:/branches:/GNOME:/STABLE:/41/openSUSE_Leap_15.4/> to see whether it fixes this.
Comment 4 Grace Wang 2024-04-19 03:15:51 UTC
Thanks Alynx help fixing this issue.

I tried the packages from the repo you provided. (tracker, libtracker-sparql-3_0-0, tracker-data-files, tracker-data-files and typelib-1_0-Tracker-3_0 were updated)

The bijiben can be started for the first time now.

But if we start the bijiben from terminal, we still can see lots of errors 
"(bijiben:973): Tracker-CRITICAL **: 10:59:47.084: SQLite error: database disk image is malformed (errno: No such file or directory)"

One more thing I observed is that: if I use the gnome-terminal to start the application bijiben, the bijiben window will be shown behind the gnome-terminal window. That's to say, if my gnome-terminal is in full screen mode, then I am not able to see the bijiben window directly unless I switch to it specifically.

I don't think this is right.
Comment 5 Alynx Zhou 2024-04-19 05:15:37 UTC
Could you try `tracker3 reset -rs` first to remove the current on disk database and see whether the error disappears?
Comment 6 Grace Wang 2024-04-19 06:44:40 UTC
(In reply to Alynx Zhou from comment #5)
> Could you try `tracker3 reset -rs` first to remove the current on disk
> database and see whether the error disappears?

The error "(bijiben:17287): Tracker-CRITICAL **: 14:43:02.910: SQLite error: database disk image is malformed (errno: No such file or directory)" still appears after doing "tracker3 reset -rs"
Comment 7 Alynx Zhou 2024-04-19 08:02:15 UTC
Is this happen without the patch? What if you remove `~/.local/share/tracker/data/` ?
Comment 8 Grace Wang 2024-04-19 08:07:37 UTC
(In reply to Alynx Zhou from comment #7)
> Is this happen without the patch? What if you remove
> `~/.local/share/tracker/data/` ?

No, as I wrote in the #c0, the errors are there without your patch.

Remove `~/.local/share/tracker/data/` and the errors still appear.
Comment 9 Alynx Zhou 2024-04-19 08:25:08 UTC
OK, I think it is another problem, it should be fixed if we can find the corrupted database and clear it. But I don't know where the database is.

Let's submit the fix first.
Comment 10 Grace Wang 2024-04-19 08:52:12 UTC
(In reply to Alynx Zhou from comment #9)
> OK, I think it is another problem, it should be fixed if we can find the
> corrupted database and clear it. But I don't know where the database is.
> 
> Let's submit the fix first.

Thanks. 
bsc#1223121 was filed to track the SQLite error issue.
Comment 13 Alynx Zhou 2024-04-25 05:03:35 UTC
Patch merged and let's close this.
Comment 14 Maintenance Automation 2024-04-29 16:30:37 UTC
SUSE-RU-2024:1467-1: An update that has one fix can now be installed.

Category: recommended (moderate)
Bug References: 1222949
Maintenance Incident: [SUSE:Maintenance:33568](https://smelt.suse.de/incident/33568/)
Sources used:
SUSE Manager Server 4.3 (src):
 tracker-3.2.1-150400.3.6.2
SUSE Linux Enterprise Workstation Extension 15 SP5 (src):
 tracker-3.2.1-150400.3.6.2
openSUSE Leap 15.4 (src):
 tracker-3.2.1-150400.3.6.2
openSUSE Leap 15.5 (src):
 tracker-3.2.1-150400.3.6.2
Basesystem Module 15-SP5 (src):
 tracker-3.2.1-150400.3.6.2
Desktop Applications Module 15-SP5 (src):
 tracker-3.2.1-150400.3.6.2
SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src):
 tracker-3.2.1-150400.3.6.2
SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src):
 tracker-3.2.1-150400.3.6.2
SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src):
 tracker-3.2.1-150400.3.6.2
SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src):
 tracker-3.2.1-150400.3.6.2
SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src):
 tracker-3.2.1-150400.3.6.2
SUSE Manager Proxy 4.3 (src):
 tracker-3.2.1-150400.3.6.2
SUSE Manager Retail Branch Server 4.3 (src):
 tracker-3.2.1-150400.3.6.2

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.