Bug 502592 - Review Request: btnx-config - GUI configuration tool for btnx
Summary: Review Request: btnx-config - GUI configuration tool for btnx
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 502591
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-26 11:25 UTC by Zarko (grof)
Modified: 2009-06-04 06:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-04 06:19:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Zarko (grof) 2009-05-26 11:25:51 UTC
Spec URL: http://wiki.open.hr/~zpintar/fedora-11/SPECS/btnx-config.spec
SRPM URL: http://wiki.open.hr/~zpintar/fedora-11/SRPMS/btnx-config-0.4.9-2.fc11.src.rpm

Description: 
btnx-config is a graphical user interface for btnx

So, rpmlint is clean, and Koji scratch builds are here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1376808
http://koji.fedoraproject.org/koji/taskinfo?taskID=1376796

Comment 1 Zarko (grof) 2009-06-04 06:19:33 UTC
I contacted upstream about evdev incompatibility and maintaining. 
Here is the answer:
----------------------------------------------------------------------
btnx is unofficially dead and I have moved onto other things. It's
been a while since I looked at what caused the problems so my memory
is a little rusty. But at least one problem was that evdev locked the
input device preventing btnx from reading it. I remember doing some
stuff with HAL (I don't remember the module name anymore) and I got
around the problem, but it ended up being too complicated to make
casual users go through the process and mistakes could lead to an
unstartable X session.
----------------------------------------------------------------------

According to this, I'm closing this thread.


Note You need to log in before you can comment on or make changes to this bug.