Chromium cleaning generates an error

Forums: 
Forum tags: 

When cleaning Chromium with History included, it generates an error. It's neither serious, nor do I think that it's a BB error. Without History it's error free. I checked ownership and permissions and everything in the home folder is user owned with full permissions.

Error in execution of
Traceback (most recent call last):
File "/usr/share/bleachbit/Worker.py", line 84, in execute
for ret in cmd.execute(self.really_delete):
File "/usr/share/bleachbit/Command.py", line 149, in execute
self.func(self.path)
File "/usr/share/bleachbit/Special.py", line 162, in delete_chrome_favicons
raise RuntimeError('%s is version %d' % (path, ver))
RuntimeError: /home/ineuw/.config/chromium/Default/Favicons is version 33

Bleachbit 1.12 for Linux
Linux Mint 18.1 Cinnamon,
Chromium Version 58.0.3029.110 Built on Ubuntu , running on LinuxMint 18.1

ineuw's picture

I still have this issue. Is there a solution for this?

Windows 10 Pro 64bit, and Linux Mint 19.1 64bit

ineuw's picture

Please mark this as solved. Remembered that I installed Chromium after Bleachbit 1.12. So, I uninstalled and reinstalled BB and now everything seems fine.

Windows 10 Pro 64bit, and Linux Mint 19.1 64bit

HubertCumberdale's picture

I receive a very similar error message (see below), however (unlike you) after uninstalling and then reinstalling BB the issue persists.

Error in execution of
Traceback (most recent call last):
File "/usr/share/bleachbit/bleachbit/Worker.py", line 84, in execute
for ret in cmd.execute(self.really_delete):
File "/usr/share/bleachbit/bleachbit/Command.py", line 146, in execute
self.func(self.path)
File "/usr/share/bleachbit/bleachbit/Special.py", line 161, in delete_chrome_favicons
raise RuntimeError('%s is version %d' % (path, ver))
RuntimeError: /home/user/.config/chromium/Default/Favicons is version 36

Chromium 60.0.3112.78 (Developer Build) Built on Ubuntu, running on LinuxMint 18.2 (32-bit)
BleachBit 1.10

-------------------------------------------------------------------------------
"I’m good at exploring roofs. You never know when that kind of thing comes in useful.”
The Rubadub Mystery, Enid Blyton

ineuw's picture

This may be another solution which I tried earlier and also worked for me. The problem may be an ownership and user rights issue. Some software installations may assign ownership of a folder or a file to 'root' in the /home/user folder. Change the owner of /home/user/.config/chromium/ sub folders and files to the user, or to be 100% sure, change ownership to the user, to all sub folders and files in /home/user/.

Windows 10 Pro 64bit, and Linux Mint 19.1 64bit

HubertCumberdale's picture

Thanks for your reply. Can you explain to me how to do what you explained?

I tried the following, but it didn't work:
- I opened Nemo the file browser
- I navigated to /home/user/.config and right-clicked on the chromium folder and selected Properties
- I clicked on the Permissions tab

This tab shows the following:
- Owner: user***
- Folder access: Create and delete files
- File access: --- (I changed this Read and Write and then clickedon "Apply Permissions to Enclosed Files")
These settings don't stick though, because if I close the Properties dialog and then reopen it, I can see that file access has changed back to "---"

Could you explain what I'm doing wrong?
Thanks.

*** I'm confused about this, because when I go into System Settings > Users and Groups (I get prompted for my root password at this point), and then get to the Users and Groups window, user has Account Type: Administrator. If the user is the Administraor, why am I being prompted for my root password to get to this screen?

-------------------------------------------------------------------------------
"I’m good at exploring roofs. You never know when that kind of thing comes in useful.”
The Rubadub Mystery, Enid Blyton

This is a known bug that I will fix soon: Favicons is version 36 (LP#1710542)

---
Andrew, lead developer

ineuw's picture

Hi,

I just saw Andrew's comment above, and he is the boss.

Though, this is no longer an issue with the current version of Chromium. [Version 60.0.3112.78 (Developer Build) Built on Ubuntu , running on LinuxMint 18.2 (32-bit)]

FYI, Even if one is an Admin, the password is always required for any system related operation.

For ownership and user rights operations I always rely on the terminal.

Being careful as to what I change, even when it's in the user's home folder, I first save the current files' and folders' ownership settings in a text file with the following command in the terminal.

ls -la -R > Documents/before.txt

. . . . This records the current folder and the subfolders' file settings in a text file before the changes. This text file is created in the Documents folder.

The uppercase "-R" switch indicates "Recursive" (current and subfolders and files).

Then, issue the following command in the terminal.

sudo chown -R user:user /home/user

. . . . user:user indicates username : groupname. The groupname is usually the same as the username on a single user system.

. . . . One needs "sudo" because folders that are owned by the root can only be changed as a superuser.

If you wish to compare the changes, save a new file list another text file:

ls -la -R > Documents/after.txt

I hope that this helps.
ineuw

Windows 10 Pro 64bit, and Linux Mint 19.1 64bit

I fixed the "Favicons is version 36" bug today for the next release.

If your files are not owned by the same user account as with you run BleachBit, then you may get a "permission denied" error. This situation is rare, but if you do, ineuw's instructions may help.

---
Andrew, lead developer

HubertCumberdale's picture

Thanks to both of you for your replies.
I'll wait to see if this is resolved on my machine in the new version of BB whenever it's released through the Linux Mint Update Manager.
ineuw: thanks for your instructions, I'll refer to them if the update doesn't fix the problem
Andrew: I'm experiencing serious problems logging in. I had to request a one-time log-in to change my password. I tried 5 times to log in and each time my password wasn't recognized. I was definitely entering it correctly. Are you aware of any issues with login recognition/acceptance? My old password contained an underscore, was that causing the problem?

-------------------------------------------------------------------------------
"I’m good at exploring roofs. You never know when that kind of thing comes in useful.”
The Rubadub Mystery, Enid Blyton