Bug 84143 - kandy can not lock device, needs to use lockdev
Summary: kandy can not lock device, needs to use lockdev
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: rawhide
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Petr Rockai
QA Contact: Ben Levenson
URL: http://bugs.kde.org/show_bug.cgi?id=8...
Whiteboard: Upstream maintainer want a patch
Depends On:
Blocks: 79579 CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2003-02-12 19:36 UTC by Eugene Kanter
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-17 14:24:14 UTC


Attachments (Terms of Use)

Description Eugene Kanter 2003-02-12 19:36:55 UTC
Description of problem:

minicom uses /usr/sbin/lockdev, but kandy tries to create lock file direclty and
fails.

Version-Release number of selected component (if applicable):

kdepim-3.1-2

Steps to Reproduce:
1. configure minicom to access any serial port as user (no need to have anything
connected) and verify that there is not "permission denied" errors.
2. start kandy and point it to the same serial port

    
Actual results:

kandy pops up an error dialog.

Expected results:

successful connection.

Comment 1 Aleksey Nogin 2004-04-23 19:19:00 UTC
This is still there in Fedora Core devel

Comment 2 Aleksey Nogin 2004-04-23 19:35:44 UTC
I also reported this upstream - see
http://bugs.kde.org/show_bug.cgi?id=80228

Comment 3 Aleksey Nogin 2004-04-28 07:22:33 UTC
Upstream maintainer wrote (in
http://bugs.kde.org/show_bug.cgi?id=80228) that he does not have acces
to a lockdev-based distro and he would like to get a patch.

Comment 4 Petr Rockai 2005-03-17 14:24:14 UTC
I fixed the bug in upstream CVS. Expect the fix to appear in next KDE and a 
following Fedora release. I will consider backporting this to 3.4 though. 


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