[Bug 1222949] New: bijiben fail to start for the first time
https://bugzilla.suse.com/show_bug.cgi?id=1222949 Bug ID: 1222949 Summary: bijiben fail to start for the first time Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs@suse.de Reporter: grace.wang@suse.com QA Contact: qa-bugs@suse.de CC: heiko.rommel@suse.com, yfjiang@suse.com, zcjia@suse.com Target Milestone: --- Found By: --- Blocker: --- 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) ================================================================================ -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c1 Alynx Zhou <alynx.zhou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou@suse.com --- Comment #1 from Alynx Zhou <alynx.zhou@suse.com> --- Looks like a tracker and SQLite version problem: https://gitlab.archlinux.org/archlinux/packaging/packages/tracker3/-/issues/... https://gitlab.gnome.org/GNOME/tracker/-/issues/418 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c2 Alynx Zhou <alynx.zhou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gnome-bugs@suse.de |alynx.zhou@suse.com Status|NEW |IN_PROGRESS --- Comment #2 from Alynx Zhou <alynx.zhou@suse.com> --- I'll backport the fix. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c3 --- Comment #3 from Alynx Zhou <alynx.zhou@suse.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 Yifan Jiang <yfjiang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(grace.wang@suse.c | |om) CC| |grace.wang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c4 Grace Wang <grace.wang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(grace.wang@suse.c | |om) | --- Comment #4 from Grace Wang <grace.wang@suse.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c5 Alynx Zhou <alynx.zhou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?, | |needinfo?(grace.wang@suse.c | |om) --- Comment #5 from Alynx Zhou <alynx.zhou@suse.com> --- Could you try `tracker3 reset -rs` first to remove the current on disk database and see whether the error disappears? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c6 Grace Wang <grace.wang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(grace.wang@suse.c | |om) | --- Comment #6 from Grace Wang <grace.wang@suse.com> --- (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" -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c7 Alynx Zhou <alynx.zhou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |SHIP_STOPPER? --- Comment #7 from Alynx Zhou <alynx.zhou@suse.com> --- Is this happen without the patch? What if you remove `~/.local/share/tracker/data/` ? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c8 --- Comment #8 from Grace Wang <grace.wang@suse.com> --- (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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c9 Alynx Zhou <alynx.zhou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #9 from Alynx Zhou <alynx.zhou@suse.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c10 --- Comment #10 from Grace Wang <grace.wang@suse.com> --- (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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c13 Alynx Zhou <alynx.zhou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #13 from Alynx Zhou <alynx.zhou@suse.com> --- Patch merged and let's close this. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1222949 https://bugzilla.suse.com/show_bug.cgi?id=1222949#c14 --- Comment #14 from Maintenance Automation <maint-coord+maintenance-robot@suse.de> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com