Bug 991517 - gtkterm cannot create lockfile
Summary: gtkterm cannot create lockfile
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gtkterm
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-02 15:53 UTC by Maxwell Bottiger
Modified: 2016-03-31 09:16 UTC (History)
5 users (show)

Fixed In Version: gtkterm-0.99.7-0.4.rc1.git26021e33.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-08 02:31:47 UTC
Type: Bug


Attachments (Terms of Use)

Description Maxwell Bottiger 2013-08-02 15:53:29 UTC
Description of problem:
GTKTerm complains that it connot create a lock file on start up.  This prevents it from opening serial ports, or doing most useful tasks

Version-Release number of selected component (if applicable):
gtkterm-0.99.7-0.1.rc1.git26021e33.fc19.x86_64

How reproducible:
Every time

Steps to Reproduce:
1.Run gtkterm from the gui or command line
2.
3.

Actual results:
Cannot create lockfile: Permission denied

Expected results:
A lock file

Additional info:

Comment 1 Hans de Goede 2013-08-03 13:24:47 UTC
Hi,

It can not only not create the lockfile, it will also be unable to open the serial-port if it where to get passed the lockfile issue. Serial ports are not open to all users, you need to add your user to the dialout and lock groups, we unfortunately don't have a nice userfriendly solution for this.

IE you need to do as root:
usermod -a -G dialout,lock <username>
 
Regards,

Hans

Comment 2 Paulius Zaleckas 2013-09-03 10:12:49 UTC
Adding user to lock and dialout groups does not help.
Problem is that gtkterm tries to create lockfile in /var/lock
when it should be in /var/lock/lockdev

Please reopen this bug.

Comment 3 Hans de Goede 2013-09-03 10:16:31 UTC
You're right, re-opening. I'll try to fix this one of the coming days.

Comment 4 Fedora Update System 2013-09-04 12:10:30 UTC
gtkterm-0.99.7-0.4.rc1.git26021e33.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/gtkterm-0.99.7-0.4.rc1.git26021e33.fc20

Comment 5 Fedora Update System 2013-09-04 12:11:27 UTC
gtkterm-0.99.7-0.4.rc1.git26021e33.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/gtkterm-0.99.7-0.4.rc1.git26021e33.fc19

Comment 6 Fedora Update System 2013-09-04 16:06:35 UTC
Package gtkterm-0.99.7-0.4.rc1.git26021e33.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gtkterm-0.99.7-0.4.rc1.git26021e33.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15753/gtkterm-0.99.7-0.4.rc1.git26021e33.fc20
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-09-13 00:59:34 UTC
gtkterm-0.99.7-0.4.rc1.git26021e33.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-09-23 00:22:23 UTC
gtkterm-0.99.7-0.4.rc1.git26021e33.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Maxwell Bottiger 2014-07-17 19:21:14 UTC
I have a Fedora 20 installation with gtkterm gtkterm-0.99.7-0.4.rc1.git26021e33.fc20.x86_64 which is displaying this same problem.  Could this bug please be reopened?

Comment 10 Hans de Goede 2014-07-18 09:51:39 UTC
(In reply to Maxwell Bottiger from comment #9)
> I have a Fedora 20 installation with gtkterm
> gtkterm-0.99.7-0.4.rc1.git26021e33.fc20.x86_64 which is displaying this same
> problem.  Could this bug please be reopened?

In order to be able to use gtkterm as a normal user you need to do:

usermod -a -G dialout,lock <username>

As root, replacing <username> with your username, so that your user gets access to serial ports.

Please let us know if that solves your issue.

Comment 11 Maxwell Bottiger 2014-10-08 02:31:47 UTC
I forgot to add myself to the lock group.  I'd read about the need to add users to the dialout group before.


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