ccsm crashed with AttributeError in CheckActionConflicts()

Bug #124704 reported by KIAaze
8
Affects Status Importance Assigned to Milestone
compizconfig-settings-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: compizconfig-settings-manager

Crash while I was trying to set the shortcut for "Initiate" to shift+super+F for the paint fire plugin.
The desktop effects still work as before and the ccsm window is still open.

ProblemType: Crash
Architecture: i386
Date: Sun Jul 8 09:26:08 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/ccsm
InterpreterPath: /usr/bin/python2.5
Package: compizconfig-settings-manager 0.0+git20070703-0ubuntu2
PackageArchitecture: all
ProcCmdline: python /usr/bin/ccsm
ProcCwd: /home/mike
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/ccsm']
SourcePackage: compizconfig-settings-manager
Title: ccsm crashed with AttributeError in CheckActionConflicts()
Uname: Linux mike-laptop 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

Tags: apport-crash
Revision history for this message
KIAaze (zohn-joidberg) wrote :
Revision history for this message
Sebastian Rode (sebastian-ro-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in compizconfig-settings-manager:
status: New → Incomplete
Revision history for this message
KIAaze (zohn-joidberg) wrote : Re: [Bug 124704] Re: ccsm crashed with AttributeError in CheckActionConflicts()
  • unnamed Edit (2.7 KiB, text/html; charset=ISO-8859-1)

I completely forgot about this bug.
But I just tried again and now it's more interesting:

After setting shift+super+F to initiate fire painting, the key combination
works to activate fire painting (it draws a single dot since it's not
dependent on mouse movement).
However, after using it all open windows became partially responsive (except
ccsm).
For example, in this case, kate and firefox were open. I couldn't select any
text in them or move up and down.
I could use the menu in Kate to create a new document, but the new document
didn't show up.
I could click on other tabs or create a new tab in firefox, but it still
displayed the same page, while the text in the title bar changed.
Switching between windows worked.
The applications/places/system menu worked too.

I made another test using the default binding for initiate
(shift+super+mouse1) and obtained the same results: painting fire partially
disables other windows.

Both were with and without clearing the fire paint.

After deactivating desktop effects, the windows were usable again.

However, I would like to note that I currently have a not so clean system.
I allready upgraded to Intrepid and the latests upgrades I made through
synaptic forced me to remove a lot of packages and sound is not working
anymore for example:
https://bugs.launchpad.net/ubuntu/+bug/229266

On Sun, May 11, 2008 at 4:52 PM, Sebastian Rode <email address hidden> wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in advance.
>
> ** Visibility changed to: Public
>
> ** Changed in: compizconfig-settings-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> ccsm crashed with AttributeError in CheckActionConflicts()
> https://bugs.launchpad.net/bugs/124704
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Unlock your computing: http://www.getgnulinux.org/

Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

Revision history for this message
KIAaze (zohn-joidberg) wrote :

I managed to reproduce the problem again, but only once.
Firefox still worked, but Kate was unusable again.
After minimizing+maximizing the Kate window, it worked again.

After that, I wasn't able to reproduce the issue again, despite having
logged out and in again, disabling/reenabling desktop effects.

I'll post again if I find a way to reliably reproduce the bug (maybe I
can reproduce it after rebooting... :/ ).

On Sat, Nov 29, 2008 at 5:55 PM, JaysonRowe <email address hidden> wrote:
> Since it's been a very long time since any additional info was added to
> this bug, I'm just checking to see if this is still an issue, and find
> out what additional work should be done on this bug.
>
> --
> ccsm crashed with AttributeError in CheckActionConflicts()
> https://bugs.launchpad.net/bugs/124704
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Unlock your computing: http://www.getgnulinux.org/

Revision history for this message
Hew (hew) wrote :

Does the crash that was originally reported still occur with Intrepid release?

Revision history for this message
KIAaze (zohn-joidberg) wrote :

No, no more crash.

As for the "Kate not reponding after activating fire painting", I can only reproduce it once after every reboot (logging in/out or deactivating/reactivating compiz doesn't work).
Minimizing and maximizing the Kate window makes it work again, so it's not such a big problem.

Revision history for this message
Hew (hew) wrote :

This bug report is being closed as the crash originally reported no longer occurs with the latest Ubuntu release. If you are having a separate issue with kate, you should file a new bug report for it. Thanks for your report.

Changed in compizconfig-settings-manager:
status: Incomplete → 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.