[wmii] Crash and a Reccuring Issue

From: Thomas Gallen <kaori.hinata_AT_gmail.com>
Date: Sat, 19 Jul 2008 11:09:59 -0400

Hmm, wmii has been running really well for me lately so while this is a
crash, I probably wouldn't have found this had I not been in the process
of finding a solution to problem #2. This problem regards the usage of
the title bar movement sqare and using the right click to bring a window
to the float layer, and returning it to a column.

Steps to Reproduce:
1. Spawn a window (number doesn't seem to have any effect, neither does
   what application it is).
2. Left click and hold on the movement square in the upper left hand
   corner.
3. While holding the left mouse button, right click to bring the window
   to the float layer.
4. Release left mouse button and it should be in the float layer.
5. Now repeat the above to return it to the column layer.
6. Once you select the column and placement and release the left mouse
   button it crashes out.

Wmii version is: wmii-hg2338
Backtrace at: http://merumeru.mobi/files/pub/wmii/wmii_backtrace-2008_07_19.log

Now on to issue two, this is a duplicate (mostly) of this one here:
http://lists.suckless.org/wmii/0805/4380.html
...however there are some differences.

This issue effects all Bash shells spawned from wmii (I.E. all
terminal emulators. :( ) in which I'm having the following issues
with gentoo portage:

*SNIP*
        /var/tmp/portage/games-arcade/ascii-invaders-0.1b/temp/environment: line 1: *=/usr/users/kyon/.wmii-3.5/urxvt: No such file or directory
        /var/tmp/portage/games-arcade/ascii-invaders-0.1b/temp/environment: line 2806: declare: `*=/usr/users/kyon/.wmii-3.5/urxvt': not a valid identifier
*SNIP*

This first chunk I believe Kris had already said was a non-Wmii issue,
and although it's displayed during an emerge and unemerge (-C), it seems
to have no effect and I believe it can be taken just as a warning
(unmerges finish regardless of this issue being displayed, it's emerges
that suffer the issue below).

*SNIP*
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/tr: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/sort: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/tr: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/tr: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/tr: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/sort: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/tr: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/tr: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/sort: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/tr: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/sort: Argument list too long
        /usr/lib/portage/bin/ebuild.sh: line 1658: /bin/tr: Argument list too long
        /var/tmp/portage/games-arcade/ascii-invaders-0.1b/temp/environment: line 1363: /bin/cat: Argument list too long
*SNIP*

This on the other hand I believe Kris has already added a line to fix
(line 124 of wmii.rc I think it was based on the previous report).
However, the issue seems to be occuring again.

If you need any further information just ask!

Thanks greatly in advance,
Thomas
Received on Sat Jul 19 2008 - 15:09:59 UTC

This archive was generated by hypermail 2.2.0 : Mon Jul 21 2008 - 17:24:04 UTC