https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #80 from commit-h...@freebsd.org ---
A commit references this bug:
Author: madpilot
Date: Thu Mar 11 09:06:00 UTC 2021
New revision: 568071
URL: https://svnweb.freebsd.org/changeset/ports/568071
Log:
MFH: r566943
Import
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #79 from commit-h...@freebsd.org ---
A commit references this bug:
Author: madpilot
Date: Tue Mar 2 11:01:41 UTC 2021
New revision: 566943
URL: https://svnweb.freebsd.org/changeset/ports/566943
Log:
Import patch from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #78 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #77 from Jethro Nederhof ---
Thanks Guido, I can confirm the patched port from your tarball fixes the issue
and the up arrow continues to work as expected with these changes.
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Attachment #222475|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #75 from Guido Falsi ---
Upstream informed me a few minutes ago that a revised and improved version of
this patch is going to be published in a few days, so any testing should be
performed on that.
So no hurry right now.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #74 from Guido Falsi ---
Not sure how to deal with this now.
I have seen no negative effect from running with this patch.
Only report I have is in comment #72 and indicates this patch is not fixing the
actual issue.
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #73 from Dmitry Postolov ---
In my case in FreeBSD 13.0-BETA1 and 13.0-BETA2, Xfce 4.16 the problem with the
"arrow up" does not appear by default settings with US and RUS keyboard layout.
Xfce 4.16 is installed from the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #72 from Jethro Nederhof ---
Doesn't fix the issue for me. Same behavior as before the ugrab patch; up arrow
doesn't work, resetting keyboard shortcuts to default makes it work again until
you start a new X session.
I might
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Attachment #221942|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #70 from Guido Falsi ---
Looks like I actually lost a message from upstream.
Upstream developer states the patch at
https://gitlab.xfce.org/xfce/libxfce4ui/-/merge_requests/27 could fix this.
I'm going to create a patch to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Status|In Progress |Open
URL|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #67 from commit-h...@freebsd.org ---
A commit references this bug:
Author: madpilot
Date: Fri Jan 29 08:03:41 UTC 2021
New revision: 563178
URL: https://svnweb.freebsd.org/changeset/ports/563178
Log:
Add patch to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #66 from Conrad Meyer ---
(In reply to Guido Falsi from comment #65)
Awesome!
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xfce@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #65 from Guido Falsi ---
(In reply to Guido Falsi from comment #64)
I'm using the proposed patch on my machines, and I see no regressions.
Switching to and from vtys works as usual, My key combinations work as
expected.
Plan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Attachment #215420|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #63 from Victor Sudakov ---
(In reply to Guido Falsi from comment #62)
I actually run two Xorg Xservers on the same PC, one for myself and another for
the wife (both start from their respective startx), so that each of us could
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #62 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #61 from Conrad Meyer ---
(In reply to Guido Falsi from comment #59)
+1, let's add it back. I'm not experiencing the issue yet because I'm still on
4.14.
(In reply to Guido Falsi from comment #60)
Even if it caused a 30
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #60 from Guido Falsi ---
(In reply to Guido Falsi from comment #59)
Conversation with upstream [1] indicates that the ungrab line was removed
mainly because in linux it caused a 30-40 seconds delay and high CPU usage when
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #59 from Guido Falsi ---
(In reply to Jethro Nederhof from comment #54)
In relation to this commit:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Dmitry Postolov changed:
What|Removed |Added
CC||dposto...@yandex.ru
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Victor Sudakov changed:
What|Removed |Added
CC||v...@sibptus.ru
--- Comment #57
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #56 from Conrad Meyer ---
(In reply to Alexey Dokuchaev from comment #55)
This seems like a new, related regression introduced in the 4.16 timeline.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Alexey Dokuchaev changed:
What|Removed |Added
Resolution|FIXED |---
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #54 from Jethro Nederhof ---
Yeah, can confirm this was reintroduced to 4.16 upstream in
https://gitlab.xfce.org/xfce/libxfce4ui/-/commit/85d8d390f9f2265613da4291992523937a7a2519
If you don't mind building the port instead,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Gordon Hartley changed:
What|Removed |Added
CC||gro.dsbeerf.sgub@gordonhart
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Piotr Sawicki changed:
What|Removed |Added
CC||psawick...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #50 from commit-h...@freebsd.org ---
A commit references this bug:
Author: madpilot
Date: Thu Jul 16 08:48:39 UTC 2020
New revision: 542340
URL: https://svnweb.freebsd.org/changeset/ports/542340
Log:
MFH: r542258
Update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Conrad Meyer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #48 from Guido Falsi ---
I think the issue reported here has been fixed, and the change is now included
in upstream repository, so it will be included in the next official release.
Can this issue be closed and marked as fixed?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #47 from commit-h...@freebsd.org ---
A commit references this bug:
Author: madpilot
Date: Wed Jul 15 13:26:46 UTC 2020
New revision: 542258
URL: https://svnweb.freebsd.org/changeset/ports/542258
Log:
Update patch to Fix
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #46 from Samy Mahmoudi ---
(In reply to Samy Mahmoudi from comment #45)
Correction (inversion):
> So I think there's a different issue with xorg initially detecting the wrong
> keymap until first keypress.
With all the mess
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #45 from Samy Mahmoudi ---
(In reply to Jethro Nederhof from comment #44)
> Yes, thanks for clarifying it's just the first keypress, you had me worried
> there!
You're welcome.
> I suspect the issue not appearing with display
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #44 from Jethro Nederhof ---
(In reply to Samy Mahmoudi from comment #43)
Hey Samy,
Yes, thanks for clarifying it's just the first keypress, you had me worried
there! I can replicate this, and as far as I understand the bug,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #43 from Samy Mahmoudi ---
I just found out something interesting that may help to isolate my problems and
separate them from this PR. Context: patch from comment 39 applied.
If I refrain from starting xbindkeys, or if I start
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #42 from Samy Mahmoudi ---
(In reply to Guido Falsi from comment #38)
Neither does the absence of LANG in my environment (I created a new user
account to also exclude potential problems coming from a previous
configuration).
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #41 from Samy Mahmoudi ---
(In reply to Guido Falsi from comment #39)
Tested! Unfortunately, the patch in its current form does not resolve the
problem (at least in my case).
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #40 from Samy Mahmoudi ---
(In reply to Guido Falsi from comment #38)
> I don't have a full grasp of all the freedesktop.org standards and tools,
> like consolekit and the like.
I was struggling with ConsoleKit before landing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #39 from Guido Falsi ---
Created attachment 215420
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215420=edit
Newer patch
Attaching patch to the ports tree applying code proposed upstream to the port.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Resolution|FIXED |---
Status|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #37 from Samy Mahmoudi ---
(In reply to Samy Mahmoudi from comment #36)
blinks ---> blink
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #36 from Samy Mahmoudi ---
By trial and error I have noticed some things that might be interesting.
Context:
libxfce4menu-4.14.1_1
12.1-RELEASE-p5 amd64
FACT 1: Starting xfce4 from vt, the up arrow key is not correctly mapped
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
See Also|https://bugzilla.xfce.org/s |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Samy Mahmoudi changed:
What|Removed |Added
CC||samy.mahmo...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #33 from Melroy van den Berg ---
Created attachment 214538
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214538=edit
Key pressed observed by xev
Same kind of findings I saw before,. It looks like the 'up' arrow key
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #32 from Jethro Nederhof ---
Fantastic, thanks a lot Conrad & Guido for your work on this issue! Looking
forward to seeing the fix in an upstream release soon.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
See Also||https://bugzilla.xfce.org/s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #31 from Conrad Meyer ---
No worries, just checking up. :)
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xfce@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #30 from Guido Falsi ---
(In reply to Conrad Meyer from comment #29)
Actaully no, I wanted to clean up the patch before, but did not have time to.
I"m going to have a better look in the next few days.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #29 from Conrad Meyer ---
Guido, did you get a chance to report or submit this upstream yet?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #28 from Conrad Meyer ---
Excellent!
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xfce@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #27 from commit-h...@freebsd.org ---
A commit references this bug:
Author: madpilot
Date: Sun Apr 12 20:47:19 UTC 2020
New revision: 531556
URL: https://svnweb.freebsd.org/changeset/ports/531556
Log:
MFH: r531554
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Conrad Meyer changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #25 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #24 from commit-h...@freebsd.org ---
A commit references this bug:
Author: cem
Date: Sun Apr 12 20:23:56 UTC 2020
New revision: 531554
URL: https://svnweb.freebsd.org/changeset/ports/531554
Log:
x11/libxfce4menu: Fix leaked
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
Flags||merge-quarterly?
--- Comment #23
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Conrad Meyer changed:
What|Removed |Added
Keywords||patch
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #22 from Conrad Meyer ---
Please try this patch. It seems to fix the issue, at least for me:
https://reviews.freebsd.org/D24338
My test may be confounded by having deleted the Printscreen shortcut entirely,
so additional
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #21 from Conrad Meyer ---
Probably related: PR 244339
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xfce@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #20
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #19 from aryeh.fried...@gmail.com ---
(In reply to Jethro Nederhof from comment #18)
What appears to have happened is the bug was found and patched and then somehow
the patch got lost in an update (see email thread for details)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #18 from Jethro Nederhof ---
OK so I've dug into this a bit further and I think there is a relevant bug in
XFCE.
For port x11/libxfce4menu, in libxfce4kbd-private/xfce-shortcuts-grabber.c and
the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #17 from Guido Falsi ---
(In reply to Jethro Nederhof from comment #15)
No offense taken!
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #16 from Guido Falsi ---
After a quick look I'd say xfce is doing some default binding with the arrow
keys. up and down ones at least.
I have no idea which xfce component and which library function they may be
calling to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #15 from Jethro Nederhof ---
(In reply to Guido Falsi from comment #12)
Sorry all, I think I've come across more rudely than intended!
I didn't mean to claim disabling the shortcut was the best solution or a fix
for everyone,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #14 from aryeh.fried...@gmail.com ---
(In reply to Guido Falsi from comment #12)
>From my testing other WM's for the most part see xev correctly
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #13 from Guido Falsi ---
(In reply to Guido Falsi from comment #12)
This was meant as a reply to comment #10
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #12 from Guido Falsi ---
(In reply to aryeh.friedman from comment #11)
As I have already stated, I have no clue, so I'm not proposing solutions.
What I was asking if you "tested" some changes whch had an effect for other
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #11 from aryeh.fried...@gmail.com ---
(In reply to Jethro Nederhof from comment #10)
Out of all the suggested solutions both here and in the mailing list thread the
setxkbmap is the one that is:
1. The most universal (there
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #10 from Jethro Nederhof ---
(In reply to Guido Falsi from comment #9)
I don't think Virtualbox/Windows are the problem because outside of XFCE in the
VM it works 100% as expected so the kernel sees it fine. It is only an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #9 from Guido Falsi ---
(In reply to Jethro Nederhof from comment #8)
The fact that it is running in virtualbox on windows add a whole layer of
things that could be interfering even before the FreeBSD kernel sees the input.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #8 from Jethro Nederhof ---
xev output, down arrow which works fine and is what you'd expect, followed by
up arrow which fails:
==
# Down arrow, works OK
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #7 from aryeh.fried...@gmail.com ---
For those who want to see the -x11@ thread where this was discussed/solved at
great length see
https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/024971.html
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #6 from aryeh.fried...@gmail.com ---
(In reply to aryeh.friedman from comment #5)
Forgot it is a standard old cheap 105 key wired keyboard on a generic desktop
(Logitech K120 which I have used for years and cost less then $15
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #5 from aryeh.fried...@gmail.com ---
(In reply to Guido Falsi from comment #4)
xev is what gave us the clue to try the solution I mentioned in comment 3.
Short answer is then events are not passed through to where xev can see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Guido Falsi changed:
What|Removed |Added
CC||madpi...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #3 from aryeh.fried...@gmail.com ---
I should of updated the PR to show the temp solution that me and someone
working together in -x11@ devised.. add the following line to your .xinitrc (or
.xsession as the case may be):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Jethro Nederhof changed:
What|Removed |Added
CC||jet...@jethron.id.au
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
--- Comment #1 from M. Voorhis ---
(In reply to aryeh.friedman from comment #0)
I have the same issue as in comment zero -- I rebuilt everything, had no
up-arrow (but others DID work).
Up-arrow works from a FreeBSD text console, and it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244290
Mark Linimon changed:
What|Removed |Added
Summary|xfce4 does not see up arrow |x11-wm/xfce4 does not see
82 matches
Mail list logo
