BleachBit crashes in Xubuntu 14.04 checking for updates

Bug #1463652 reported by ineuw
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
BleachBit
Invalid
Medium
Andrew Ziem

Bug Description

This a duplicate of my post on the Bleachbit Forum.

I am sorry but it was about time that I let you know that bleachbit 1.60 has been crashing on a fairly regular basis. Finally found the crash reports and there are 7 crashes, with the content of the .gz files:
"Thu Dec 18 11:14:26 EST 2014 crash report /var/crash/_usr_share_bleachbit_bleachbit.py.0.crash detected" and ended on December 28, 2014.

Then 7 crash reports beginning May 28.2015 and ending today with the following message.
"Mon Jun 8 19:13:51 EDT 2015 crash report /var/crash/_usr_bin_bleachbit.0.crash detected
bleachbit
Mon Jun 8 23:19:04 EDT 2015 crash report /var/crash/_usr_bin_bleachbit.0.crash detected"

This entry must have been doubled because I was running both user and admin mode. usually I run it as user.

I apologize for not reporting it earlier, but didn't know where the linux logs were, and forgot about it because the OS always recovered, except today

System information

BleachBit version 1.6
GTK version 2.24.23
local_cleaners_dir = /usr/share/cleaners
locale_dir = /usr/share/locale/
options_dir = /home/ineuw/.config/bleachbit
personal_cleaners_dir = /home/ineuw/.config/bleachbit/cleaners
system_cleaners_dir = /usr/share/bleachbit/cleaners
locale.getdefaultlocale = ('en_CA', 'UTF-8')
os.getenv('DESKTOP_SESSION') = xubuntu
os.getenv('LOGNAME') = ineuw
os.getenv('USER') = ineuw
os.getenv('SUDO_UID') = None
os.path.expanduser('~') = /home/ineuw
platform.linux_distribution() = ('Ubuntu', '14.04', 'trusty')
platform.platform = Linux-3.13.0-53-generic-i686-with-Ubuntu-14.04-trusty
sys.argv = ['/usr/bin/bleachbit']
sys.executable = /usr/bin/python
sys.version = 2.7.6 (default, Mar 22 2014, 22:59:38)
[GCC 4.8.2]
__file__ = /usr/share/bleachbit/Diagnostic.py

A suggestion: perhaps on the help section a buttong to the logs could be added?

I opened this post for additional info:
Installed v1.7.7 beta and it also crashed, but I made two screen images of the details shown by Xubuntu. Where can I sent/upload this info?

Revision history for this message
ineuw (ineuw) wrote :
Revision history for this message
Andrew Ziem (ahziem1) wrote :

In the BleachBit preferences do you have enabled "Check periodically for software updates via the Internet"?

Revision history for this message
Andrew Ziem (ahziem1) wrote :

Note to self, the screenshot shows the error "xcb_xlib_threads_sequence_lost"

Revision history for this message
ineuw (ineuw) wrote :

Yes, both the user and the admin versions the option to check was selected. I deselected them and tested the user's once, and the admin version twice. Once before Ubuntu update and once after. The error has not returned and will keep you posted.

Changed in bleachbit:
importance: Undecided → Medium
milestone: none → 1.14
Revision history for this message
Andrew Ziem (ahziem1) wrote :

I am going to try another way to reproduce.

Meanwhile, do you still use Xubuntu 14.04? If you have updated to a new Linux and you enable "Check periodically for software updates via the Internet", do you still have this error? Let me know whether it happens, which version of Linux, and which version of BleachBit.

summary: - Bleachbit crashes in Xubuntu 14.04
+ BleachBit crashes in Xubuntu 14.04 checking for updates
Changed in bleachbit:
status: New → Triaged
assignee: nobody → Andrew Ziem (ahziem1)
Revision history for this message
ineuw (ineuw) wrote :

I changed awhile ago to Linux Mint 18.0 (Sara) which I believe is the equivalent of Ubuntu 16.04. I am using both 32bit and 64bit versions with BleachBit v1.12 without any problems whatsoever. I believe you can close this ticket. Thank you.

Revision history for this message
Andrew Ziem (ahziem1) wrote :

ineuw: Thank you for the updated report!

On Google I found other bug reports related to this, including reports about BleachBit, but all of them were from 2012-2013. I assume this was caused in an older version of PyGTK

Changed in bleachbit:
milestone: 2.0 → none
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.