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#24252 - [wvdial] reports all serial ports as busy unless /var/lock is manually created

Attached to Project: Community Packages
Opened by Jakub Schmidtke (sjakub) - Friday, 13 May 2011, 04:53 GMT
Last edited by Florian Pritz (bluewind) - Saturday, 26 November 2011, 13:35 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

wvdial simply doesn't work with the default settings.
It reports all serial ports as busy, with no additional
messages which makes it tricky to solve.
The solution is to create a /var/lock directory.
If it is critical for wvdial, it should be created by the package...
Closed by  Florian Pritz (bluewind)
Saturday, 26 November 2011, 13:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in pacman 4
Comment by Andrea Scarpino (BaSh) - Friday, 13 May 2011, 06:54 GMT
Hi, could you test wvdial 1.61-3 before I push it?
http://dev.archlinux.org/~andrea/pkgs/wvdial-1.61-3-i686.pkg.tar.xz
http://dev.archlinux.org/~andrea/pkgs/wvdial-1.61-3-x86_64.pkg.tar.xz
Thanks
Comment by Ray Rashif (schivmeister) - Friday, 13 May 2011, 20:41 GMT
I no longer keep up with this so disowning. Reassigned to last packager (Andrea; he already has something to push for this as well).
Comment by Jakub Schmidtke (sjakub) - Friday, 13 May 2011, 23:38 GMT
1.61-3 still experiences the same problem. I removed /var/lock directory, installed that package and it still wasn't working properly.

But in the meantime I noticed that when pppd is used directly it experiences exactly the same problem.
When there is no /var/lock/ directory it simply exists. With no error messages.
Since wvdial depends on ppp package, maybe ppp package should make sure that this directory exists - it could
be created by the installation script if it doesn't exist? Or maybe it should be a part
of some generic "core directories" package?
Comment by Jakub Schmidtke (sjakub) - Saturday, 14 May 2011, 00:08 GMT
I don't see anything in ppp's rc.d script, but I was not using the script anyway, just running pppd from the command line.
In either case, I think it should work also without being called from the rc.d script.
Comment by Andrea Scarpino (BaSh) - Sunday, 15 May 2011, 21:57 GMT
wait. I just read that you removed the /var/lock/ dir, you cannot do this. Why you don't have that dir?
That dir is installed by the filesystem package, you can set /var/lock as tmpfs in the fstab to create the dir at the boot.
Comment by Jakub Schmidtke (sjakub) - Sunday, 15 May 2011, 22:15 GMT
I removed it now, to restore the environment from before doing anything.
I didn't have that directory at all before I found out that I need it.
I didn't remove it in the past, I simply didn't have it.
Apparently something did not create it, so it's still a bug.
And it's not only my machine, I found a solution to my problem (the solution being creating the /var/lock directory that did not exist)
in a forum post. Quick search shows that some other people had the same problem too:
https://bbs.archlinux.org/viewtopic.php?id=74163
https://bbs.archlinux.org/viewtopic.php?id=118886
https://bbs.archlinux.org/viewtopic.php?id=118724
Comment by Andrea Scarpino (BaSh) - Monday, 16 May 2011, 14:59 GMT
Seems that an update removed /var/lock on some system. Anyway this isn't a bug in the wvdial package neither in the ppp package. /var/lock is a standard part of a Linux system and should exists.
Comment by Amitav (amitavmohanty01) - Wednesday, 13 July 2011, 19:41 GMT
Yes, it should exist. It is not a bug in the package but it sure is an issue with our release.

Loading...