Chromium error: Error in execution of ...

Bug #1546716 reported by ineuw on 2016-02-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BleachBit
High
Unassigned

Bug Description

Received this error message in BleachBit 1.10 Windows 7 Pro SP1 32bit. It is a persistent error because it's reoccurs after reboot.

Error in execution of <bleachbit.Command.Function instance at 0x02E32DA0>

This happened after after updating a some software:
.
LibreOffice to V5.0.1
Ghostscript for Cute PDF
Logitech mouse and keyboard software

ineuw (ineuw) wrote :
Andrew Ziem (ahziem1) wrote :

If you uncheck everything except Google Chrome, does this happen?

This may be the same as bug #1545567

Changed in bleachbit:
milestone: none → 1.12
ineuw (ineuw) wrote :

Unchecked everything except Chromium (not Chrome) and the error persisted.

Unchecked Chromium and checked everything else as I always do and the error disappeared.

The only other error is about the Avast lock file which I reported previously.

Error in execution of Command to delete C:\Windows\temp\_avast_\AvastLock.txt

I know what lock files are, and I am not concerned about it.

Andrew Ziem (ahziem1) on 2016-02-18
summary: - Execution error after installing software update
+ Chromium error: Error in execution of ...
Changed in bleachbit:
importance: Undecided → High
Andrew Ziem (ahziem1) on 2016-02-20
Changed in bleachbit:
importance: High → Critical
ineuw (ineuw) wrote :

I found the source of the Chromium problem. It happens only when "vacuum" is selected. It is a reproducible error.

Andrew Ziem (ahziem1) wrote :

Would you mind trying a kind of hot-fix?

Here is the newest version of SQLite DLL, which BleachBit uses to vacuum Chromium. If you would please

1. Download https://www.sqlite.org/2016/sqlite-dll-win32-x86-3110000.zip
2. Unzip it
3. Copy the DLL
4. Replace the DLL that comes with BleachBit. Off the top of my head, I think it is in c:\program files (x86\BleachBit\ . Make sure there is an sqlite.dll in the directory to verify it is the right location.
5. Try vacuuming again
6. Let me know how it goes

ineuw (ineuw) wrote :

Unfortunately it didn't solve the error. Without vacuum it still works fine. With vacuum tried it twice and got this identical 0x02BE82D8 error.

Error in execution of <bleachbit.Command.Function instance at 0x02BE82D8>

Just to be clear, FYI the old and new files are both named sqlite3.dll, but the old was about ~300kb, the new one is 805kb.

Andrew Ziem (ahziem1) wrote :

Reproducible on this system

Chromium 50.0.2660.0 (Developer Build) (32-bit)
Windows 8.1
BleachBit 1.10

The error is that Thumbnails is a folder instead of an SQLite file, so a recent update to Chromium changed the Thumbnails from a file to a folder.

The error is reproducible also on Linux (Ubuntu) with Chromium 48. It did not have a Thumbnails file or folder, so I made one and got this error:

Error in execution of <bleachbit.Command.Function instance at 0x7fba8affcab8>
Traceback (most recent call last):
  File "bleachbit/bleachbit/Worker.py", line 84, in execute
    for ret in cmd.execute(self.really_delete):
  File "/bleachbit/bleachbit/Command.py", line 146, in execute
    self.func(self.path)
  File "/bleachbit/bleachbit/FileUtilities.py", line 739, in vacuum_sqlite3
    execute_sqlite3(path, 'vacuum')
  File "/bleachbit/bleachbit/FileUtilities.py", line 300, in execute_sqlite3
    conn = sqlite3.connect(path)
OperationalError: unable to open database file

Andrew Ziem (ahziem1) on 2016-02-26
Changed in bleachbit:
importance: Critical → High
assignee: nobody → Andrew Ziem (ahziem1)
status: New → In Progress
Andrew Ziem (ahziem1) wrote :

Fixed in git commit 967e824

Thank you for reporting the bug

Changed in bleachbit:
assignee: Andrew Ziem (ahziem1) → nobody
status: In Progress → Fix Committed
Andrew Ziem (ahziem1) wrote :

To confirm the fix, please test the fix in BleachBit 1.11 beta
https://www.bleachbit.org/news/bleachbit-1110-beta

Changed in bleachbit:
status: Fix Committed → Fix Released
ineuw (ineuw) wrote :

This error is no longer reported in 1.11

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers