Bug 265358 – Stabilise x11-terms/yeahconsole-0.3.4-r1

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Jeroen Roovers (RETIRED) 2009-04-07 16:48:19 UTC]

Please stabilise x11-terms/yeahconsole-0.3.4-r1.

[Comment 1 Jeroen Roovers (RETIRED) 2009-04-07 16:49:29 UTC]

Stable for HPPA.

[Comment 2 Raúl Porcel (RETIRED) 2009-04-14 09:54:36 UTC]

x86 stable

[Comment 3 Jeremy Olexa (darkside) (RETIRED) 2009-04-24 00:50:58 UTC]

When ran on amd64 it just says:
"10  XError caught" and doesn't do anything.

[Comment 4 Jeroen Roovers (RETIRED) 2009-04-24 00:58:20 UTC]

(In reply to comment #3)
> When ran on amd64 it just says:
> "10  XError caught" and doesn't do anything.
> 

Did you read the README? And the einfo messages? Is xterm installed?

[Comment 5 Jeremy Olexa (darkside) (RETIRED) 2009-04-24 01:03:19 UTC]

Of course I read that. xterm is all that I use.

Calculating dependencies... done!
[ebuild   R   ] x11-terms/yeahconsole-0.3.4-r1  0 kB
[ebuild   R   ] x11-terms/xterm-242  USE="unicode -Xaw3d -toolbar -truetype" 0 kB

[Comment 6 Jeroen Roovers (RETIRED) 2009-04-24 06:29:48 UTC]

Which window manager?

[Comment 7 Jeroen Roovers (RETIRED) 2009-04-24 06:33:02 UTC]

Reading from /usr/include/X11/X.h:

#define BadAccess     10    /* depending on context:
                 - key/button already grabbed
                 - attempt to free an illegal
                   cmap entry
                - attempt to store into a read-only
                   color map entry.
                - attempt to modify the access control
                   list from other than the local host.
                */

I would guess it's most likely that the default key combination is already taken (the first on the list of causes).

[Comment 8 Jeremy Olexa (darkside) (RETIRED) 2009-07-22 04:36:02 UTC]

I guess I really don't know how to use this thing. *shrug* marking stable.