0.7.2dev does not have click-mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AllTray |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Just tried 0.72dev. when i try to run it in console with just "alltray", i'm getting this error:
The program 'alltray' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 120324 error_code 3 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
When trying to run it with a program as "ALLTRAY_DEBUG=ALL alltray -D firefox":
[2009-04-06 22:01:48 EEST] INFO/MISC: Debugging subsystem setup complete.
[2009-04-06 22:01:48 EEST] INFO/CL: Command line options parsed.
[2009-04-06 22:01:48 EEST] INFO/MISC: Set WNCK Client Type to PAGER
[2009-04-06 22:01:48 EEST] INFO/PROCESS: Child process 21274 (firefox) now running.
The program 'alltray' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 5700 error_code 3 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Using KDE4.2.1
Related branches
Changed in alltray: | |
status: | Fix Committed → Fix Released |
Yes, AllTray does not currently have an implementation of Click-Mode in the development trunk. This will be addressed in a future test released; tentatively marking it for the 0.7.3dev release; will re-target it if necessary at some point down the road.
Thank you for your bug report, I forgot to mention this in the release notes for 0.7.2dev.