Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29119 - [xfe] unable to edit text fields

Attached to Project: Community Packages
Opened by steve (culyun) - Monday, 26 March 2012, 10:18 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 28 February 2013, 14:57 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

xfe

Unable to edit any text fields (eg. rename file).
Mouse could position cursor, but keys unresponsive.

Tried gogglesmm to see whether this was a fox issue.
gogglesmm didn't experience the same problem.

Running LXDE with Openbox, IBus
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 28 February 2013, 14:57 GMT
Reason for closing:  Fixed
Comment by steve (culyun) - Tuesday, 27 March 2012, 07:59 GMT
My LOCALE="en_NZ.UTF-8" in rc.conf
Comment by steve (culyun) - Tuesday, 27 March 2012, 08:28 GMT
Found problem.

There's an upstream bug in fox.
Apparently the '--with-xim' configure option is buggy.
See http://sourceforge.net/tracker/index.php?func=detail&aid=1683915&group_id=64835&atid=508822

I rebuilt fox without the '--with-xim' option.
xfe is now working fine.

Would you consider updating the fox package to remove this option?
Comment by Sergej Pupykin (sergej) - Tuesday, 10 April 2012, 03:39 GMT
did you try fox-devel from aur? https://aur.archlinux.org/packages.php?ID=29046
Comment by steve (culyun) - Tuesday, 10 April 2012, 10:41 GMT
No, I didn't try fox-devel.
However, the dependency notes on the xfe site say that "Xfe do not compile with the development version 1.7.x of FOX! "
Comment by steve (culyun) - Saturday, 12 May 2012, 11:09 GMT
Any movement on this one?
I just rebuilt fox-1.6.45-1 without the '--with-xim' option so that I could get xfe working again.
Comment by Sergej Pupykin (sergej) - Saturday, 12 May 2012, 11:44 GMT
It breaks  FS#16506 . Probably we need to fix xfe or it may be fox upstream bug.
Comment by steve (culyun) - Monday, 14 May 2012, 11:06 GMT
Fair enough, I was hoping for a quick fix, but it looks like some work will be required.
I just discovered that text entry in fox calculator does not work without --with-xim, ie. you need xim for the calculator (I think).

Thanks for the hard work btw.
Comment by Sergej Pupykin (sergej) - Thursday, 09 August 2012, 07:48 GMT
Can it be reproduced with xfe-1.33?
Comment by steve (culyun) - Wednesday, 14 November 2012, 23:54 GMT
  • Field changed: Percent Complete (100% → 0%)
Can reproduce with xfe 1.33 and fox 1.6.46.

I upgraded both xfe and fox to the latest versions using pacman. Bug was present.

I then manually rebuilt fox without the '--with-xim' option and reinstalled. I was able to edit filenames etc. with xfe afterwards.

NB. I am running IBus (Korean + English)
Comment by steve (culyun) - Thursday, 15 November 2012, 07:18 GMT
I see this issue has been reopened. I did some digging around in the xfe source following my last post.
I found and *fixed* what was causing the behaviour I was seeing.
I flicked a patch through to the xfe author but haven't heard back.

In short this needs to be fixed in the upstream xfe + fox source.
It's not something which can be addressed through packaging.
Comment by Greg (dolby) - Thursday, 15 November 2012, 07:25 GMT
Have you reported this on sourceforge, in which case a link would be nice,
or by direct email to the author?
Comment by steve (culyun) - Thursday, 15 November 2012, 12:10 GMT
I see this issue has been reopened. I did some digging around in the xfe source following my last post.
I found and *fixed* what was causing the behaviour I was seeing.
I flicked a patch through to the xfe author but haven't heard back.

In short this needs to be fixed in the upstream xfe + fox source.
It's not something which can be addressed through packaging.
Comment by Sergej Pupykin (sergej) - Friday, 16 November 2012, 09:30 GMT
btw fox-1.6.47 is in community
Comment by Sergej Pupykin (sergej) - Monday, 11 February 2013, 15:03 GMT
can it be reproduced with xfe-1.34?

Loading...