search

smashgen / superswitcher

Automatically exported from code.google.com/p/superswitcher
GNU General Public License v2.0
0 stars 0 forks source link

segfault randomly #20

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Start superswitcher
2. Use my computer
3. superswitcher missing

What is the expected output? What do you see instead?
I expect it to WORK more than a halb of a hour.
I see this when I start superswitcher from a terminal:
u-foka@u-foka-laptop:~$ superswitcher 

(superswitcher:8305): Wnck-CRITICAL **: wnck_workspace_get_number:
assertion `WNCK_IS_WORKSPACE (space)' failed
Segmentation fault (core dumped)

What version of the product are you using? On what operating system?
0.6, installed from deb package on ubuntu gutsy.

Please provide any additional information below.
I used the previous version of superswitcher before on feisty with no
problems, but the older version can't install on gutsy :S

Original issue reported on code.google.com by ufo...@gmail.com on 17 Jan 2008 at 5:30

GoogleCodeExporter commented 8 years ago 
superswitcher 0.6 segfaulted on me fairly quickly as well.  I open up about 
three
windows for each of four workspaces and it segfaulted shortly after closing one 
of
them.  I clicked on the window in the superswitcher menu before closing it (by
clicking the close button on the window's frame).

Original comment by phillip....@gmail.com on 22 Mar 2008 at 6:43

GoogleCodeExporter commented 8 years ago 
Which window manager are you guys using?  Metacity, compiz, or something else?

Original comment by nigel.ta...@gmail.com on 23 Mar 2008 at 12:20

GoogleCodeExporter commented 8 years ago 
fluxbox 1.0.0
Slackware 12.0
libwnck-2.18.0

The segfault only happened to me once so far, but I only tried out the program 
for
about 30 minutes.

Original comment by phillip....@gmail.com on 23 Mar 2008 at 2:25

GoogleCodeExporter commented 8 years ago 
I've just committed revision 33, which should be more robust to things like 
window
managers that aren't Metacity.  If you can check out and build from the latest
source, let me know if this latest version helps fix the crashes you've been 
seeing.

Original comment by nigel.ta...@gmail.com on 16 Apr 2008 at 2:36

GoogleCodeExporter commented 8 years ago 
Hey I think the randomness is caused by windows that have "Always on visible
workspace" option set - as commented here
http://code.google.com/p/superswitcher/issues/detail?id=10

Original comment by robert.s...@gmail.com on 19 Feb 2009 at 8:47

GoogleCodeExporter commented 8 years ago 
Hi, I was using superswitcher 0.6 in Puppy Linux 214X (Release Candidate) and I 
had
the same segfault right after I killed any other running application.

Anyway after I installed the latest SVN version (Revision 37) I didn´t get any
segmentation fault in Puppy Linux, I can kill any app and superswitcher still 
works
fine without errors.  Puppy Linux uses JWM Windows Manager and Rox-Filer.

It seems that you get few feedback about the latest Revisions and this segafault
issue, In my opinion this is a mayor bug fixed in latest SVN. I suggest you to
Release in your HomePage a new version (could be 0.65 or something between) 
with the
latest SVN version, because few people try the latest SVN versions or search 
inside
the google.code pages and as I said before this is a mayor bug that prevents
Superswicther to be used in a wider range of Windos Managers.

Than your for the attention pleased.  

I also want to wish you a very happy holiday and a great new year.  Please keep 
this
great project alive.

clarf.

Original comment by clarf.pu...@gmail.com on 23 Dec 2009 at 2:23