Closed GoogleCodeExporter closed 8 years ago
Bah, mispasted the title, and I now can't change it. Useless :(. Proper title is
something about WNCK_IS_WORKSPACE assertion failing.
Original comment by vitamin...@gmail.com
on 24 Oct 2007 at 2:51
I've changed the title of this issue.
I don't run AMD64 myself, so it's going to be very hard for me to debug this.
:(
Can you tell me things like how many workspaces you have, how many windows were
open,
does it crash always or only sometimes, is your system pretty much a fresh Gutsy
install or was it an upgrade from Feisty?
Original comment by nigel.ta...@gmail.com
on 24 Oct 2007 at 4:55
Window count doesn't seem to matter (I'm usually somewhere around 10), it's
crashed
100% of the times that I've tried it. I've got four workspaces, arranged in a
2x2
grid. My monitors are both 20" widescreens, so my resolution is the somewhat odd
3360x1050. This is an upgrade to gutsy, and has been running out of the gutsy
tree
for some time.
I'm attaching a gdb backtrace of the self-compiled package, not sure if it'll
help.
Let me know if there's anything you can think of that would help.
Original comment by vitamin...@gmail.com
on 24 Oct 2007 at 5:28
Attachments:
It doesn't seem to work when I disable my second monitor, so I don't think it's
related to that.
Original comment by vitamin...@gmail.com
on 24 Oct 2007 at 5:30
Thanks for the backtrace. The NULL workspace at
ss_window_new (workspace=0x0, wnck_window=0x6535c0) at window.c:345
is certainly unusual. I'll try to look at it soon.
If you're running GNOME (as a default Ubuntu install will do), can you tell me
if the
Workspace Switcher applet works fine for you? It's in the default panel
config, so
I'm presuming that it does.
Original comment by nigel.ta...@gmail.com
on 25 Oct 2007 at 12:30
It seems to work 100%.
Original comment by vitamin...@gmail.com
on 25 Oct 2007 at 6:16
I'm able to reproduce a similar-looking crasher on x86 just by opening a Tilda
window. Should be fixed in revision 31. Please re-open this issue if
superswitcher
still segfaults.
Original comment by nigel.ta...@gmail.com
on 4 Nov 2007 at 7:16
Updated to the latest svn, compiled again, and it runs fine now. I'm not sure
if it
was a system update, or the svn update that fixed it.
Original comment by vitamin...@gmail.com
on 4 Nov 2007 at 7:19
Wow, so that was pretty incredible timing on my part (updating and testing three
minutes before you closed the bug). It's definitely working now, so thank you
very much.
Original comment by vitamin...@gmail.com
on 4 Nov 2007 at 7:33
Original issue reported on code.google.com by
vitamin...@gmail.com
on 24 Oct 2007 at 2:50