THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Konstantin Stepanov (kstep)
Attached to Project - awesome
Summary - C API selection() doesn't work consistently
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - According to http://awesome.naquadah.org/doc/api/modules/selection.html there's
"selection" function one can use to get current selection, but it hangs
sometimes.
In my case it works only once after first awesome start, but once I select
other text and run it again it hangs waiting for answer and times out.
Steps to reproduce:
1) Select some text
2) Run commands:
$ killall -HUP awesome
$ awesome-client
awesome#return selection()
string "awesome"
awesome#return selection()
string "awesome"
3) Select something else
4) Run command
awesome#return selection()
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.
On step 4 there's a long waiting period before error message pops up.
Also once I restart awesome (via sending HUP signal or with Ctrl-Shift-R
binding) it works again, but only until I select something else.
The bug is perfectly reproducable for me.
My environment:
ArchLinux
Xorg -version:
X.Org X Server 1.11.2
Release Date: 2011-11-04
X Protocol Version 11, Revision 0
awesome -v
awesome v3.4-598-g8c62698 (Closing In)
• Build: Dec 14 2011 15:17:44 for x86_64 by gcc version 4.6.2 (kstep@blackbook)
• D-Bus support: ✔
uname -a
Linux blackbook 3.1.5-1-ARCH #1 SMP PREEMPT Sat Dec 10 14:43:09 CET 2011 x86_64
Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GenuineIntel GNU/Linux
Also reproducable on my other Debian Wheezy system (not available at hand just
right now, so I can't provide configuration details).
For now I'm using awful.util.pread('xsel') as a workaround, but I'd rather
prefer native awesome functions.
I looked up "selection()", "selection" and "xsel" in Flyspray, but I couldn't
find similar bug, so I add it now.
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=950
You are receiving this message because you have requested it from the Flyspray
bugtracking system. If you did not expect this message or don't want to
receive mails in future, you can change your notification settings at the URL
shown above.
--
To unsubscribe, send mail to [email protected].
