August 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Wireless networking fail > KDW wallet interference precedes segmentation fault
by Mark Ballard 24 Aug '14

24 Aug '14

KDE Wallet stopped me connecting my wireless network. And now the network config has crashed. I can't connect. Not only that, KDE Wallet doesn't know when it's not wanted. I keep telling it to go away. It keeps coming back. KDE Wallet --------------- If I must use KDE wallet for this opensuse system to work, then it should say: "you *must* do this or your system won't work". If KDE Wallet is optional, then it should learn to know when it's not wanted. If I tell it to go away, I do not want it to keep coming back. If there is a compelling reason to use KDE wallet, it is not apparent from the description it gives when it comes up in the way it does. If there is a good reason for using wallet, it has not conveyed this information. I suspect there is not. This did no become more than an irritation until it came to networking. Prior to attempting to establish a connection KDE Wallet came up every time I wanted to put in a password. I pressed <ESC> and it went away. KDE Wallet and Wireless Networking ---------------------------------------------- But KDE Wallet prevented me from establishing a connection to my wireless network. I configured the network. But when I tried to connect, it would say, "waiting for authorization", and it would soon become apparent that the KDE Wallet config window had popped up in the background. If I told KDE Wallet to go away, the network app would stop trying to establish a connection. The wallet was forcing itself upon me. So I figured I would have to use it against my wishes. When I addressed the KDE Wallet dialogue, however, it provided a tick box on the first page that I would have to click to indicate that I wanted to use it. So it seemed I did have an option after all. What a relief! Maybe now I could connect my network and KDE Wallet would go away for good! So having not ticked the box I clicked <Next>. I kept having to click <Next> to skip through the setup process, studiously not entering any information. Then I clicked okay and the wallet went away. Hooray! But then when I tried to connect the network, it said "waiting for authorization" again (though you have to squint really hard to see it). And nothing more happened. The KDE Wallet didn't come back. There was nothing I could do. I had searched out the KDE Wallet config again. It had a useful looking interface with a tickbox prominently offering to <Enable kDE Wallet>. So this did imply again that I did not have to enable it. I have to trust this, don't I? Despite appearances, I have to trust that I don't need to enable the wallet to use the networking, don't I? I tried looking at <Manage Connections>. It showed the connection I had set up. But I had trouble getting the details up. When I selected the connection and pressed <Edit>, nothing happened. Nothing happened either when I double clicked on the connnection. After an inordinate amount of time - and quite by chance, really, that I was still in the room - an error came up. It said: "Error: KDE Control Module - Did not receive a reply. Possible causes include: the remote application did not send a reply; the message bus security policy blocked the reply; the reply time out expired; or the network connection was broken". So it looked like KDE Wallet was still in the way. I went to check the wireless password dialogue and the password was no longer there. It was when I entered this last time that the KDE Wallet first came up, if I remember correctly. I entered the password again. It failed to establish a conenction. It is not very good at reporting what's going on. It also doesn't know when it already has a config window open for a particular network. In clicking to open the network config I somehow managed to open more than one. I sent one off with a password and it came back with nothing. I sent another one off. And it crashed. It reported a segmentation fault: ---------------------------------------- Executable: kcmshell4 PID: 20187 Signal: Segmentation fault (11) I'm afraid I was not able to report this in the usual way because I don't have a connection. I was unable to report it to your forum because - surprise! - it has proved probitively difficult getting a login and actually using it. (I've got logins to bugzilla, launchpad, stackexchange etc, easily enough, why does your's have to be so difficult - and why can't I just use one of those other logins?). Perhaps someone would be kind enough to file this somewhere where it might get dealt with? It reported the following bug details: -------------------------------------------- Application: KDE Control Module (kcmshell4), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb5446740 (LWP 20187))] Thread 2 (Thread 0xae262b40 (LWP 20198)): #0 0xb773f430 in __kernel_vsyscall () #1 0xb5f92372 in clock_gettime () from /lib/libc.so.6 #2 0xb6ce007c in ?? () from /usr/lib/libQtCore.so.4 #3 0xb6dc5e82 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb6dc443b in ?? () from /usr/lib/libQtCore.so.4 #5 0xb6dc44ca in ?? () from /usr/lib/libQtCore.so.4 #6 0xb59330d3 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #7 0xb59339ef in ?? () from /usr/lib/libglib-2.0.so.0 #8 0xb5933c38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #9 0xb6dc460f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #10 0xb6d93a03 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #11 0xb6d93d29 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0xb6c8230d in QThread::exec() () from /usr/lib/libQtCore.so.4 #13 0xb6d73e14 in ?? () from /usr/lib/libQtCore.so.4 #14 0xb6c84c5f in ?? () from /usr/lib/libQtCore.so.4 #15 0xb6c0107a in start_thread () from /lib/libpthread.so.0 #16 0xb5f8480e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb5446740 (LWP 20187)): [KCrash Handler] #6 0xb6cd37f3 in QString::operator=(QString const&) () from /usr/lib/libQtCore.so.4 #7 0xae636846 in Knm::Connection::setName(QString const&) () from /usr/lib/libknminternals.so.4 #8 0xae68b776 in ConnectionWidget::writeConfig() () from /usr/lib/libknmui.so.4 #9 0xae6c893f in ConnectionPreferences::save() () from /usr/lib/libknmui.so.4 #10 0xae6d1e2b in ConnectionEditor::editConnection(Knm::Connection*) () from /usr/lib/libknmui.so.4 #11 0xae780621 in ?? () from /usr/lib/kde4/kcm_networkmanagement.so #12 0xae77db74 in ?? () from /usr/lib/kde4/kcm_networkmanagement.so #13 0xb6da9c55 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #14 0xae6ffadd in NMDBusSettingsConnectionProvider::getConnectionSecretsCompleted(bool, QString const&, QString const&) () from /usr/lib/libknm_nm.so #15 0xae73ef18 in NMDBusSettingsConnectionProvider::onConnectionSecretsArrived(QDBusPendingCallWatcher*) () from /usr/lib/libknm_nm.so #16 0xae6ffc71 in ?? () from /usr/lib/libknm_nm.so #17 0xb6da9c55 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #18 0xb5b364c5 in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib/libQtDBus.so.4 #19 0xb5b3650c in ?? () from /usr/lib/libQtDBus.so.4 #20 0xb6da63da in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4 #21 0xb6dae2bb in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #22 0xb62804b4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #23 0xb6286ee3 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #24 0xb74e5cb4 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #25 0xb6d94fba in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #26 0xb6d982e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4 #27 0xb6d9880c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4 #28 0xb6dc4e0e in ?? () from /usr/lib/libQtCore.so.4 #29 0xb59337ce in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #30 0xb5933b78 in ?? () from /usr/lib/libglib-2.0.so.0 #31 0xb5933c38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #32 0xb6dc45ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #33 0xb633051e in ?? () from /usr/lib/libQtGui.so.4 #34 0xb6d93a03 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #35 0xb6d93d29 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #36 0xb67b15d1 in QDialog::exec() () from /usr/lib/libQtGui.so.4 #37 0xb52d0ff9 in kdemain () from /usr/lib/libkdeinit4_kcmshell4.so #38 0x0804fba3 in _start () --------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] problem with numlock
by jdd 24 Aug '14

24 Aug '14

Hello, since some days (may be a week), my laptop under 13.1 boots with numlock on. As it don't have numeric pad, this makes typing passwd difficult (I have to deactivate numlock first). I never had this before, neither with this computer. Yast is on no numlock as is kde4. The problem is on kdm. what may I look for? thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

Re: [opensuse] Wireless networking fail > KDW wallet interference precedes segmentation fault
by Dylan 24 Aug '14

24 Aug '14

Replies to the list, please... On 23/08/14 15:06, Mark Ballard wrote: > Thanks, Dylan. But the point was that I don't want to enable the wallet. Hence I said UNCHECK the box - if it's still activated and the box is clear then you have other problems > > > On 23 August 2014 14:25, Dylan <dylan(a)dylan.me.uk> wrote: >> On 23/08/14 13:57, Mark Ballard wrote: >>> >>> KDE Wallet stopped me connecting my wireless network. And now the >>> network config has crashed. I can't connect. >>> >>> Not only that, KDE Wallet doesn't know when it's not wanted. I keep >>> telling it to go away. It keeps coming back. >>> >>> KDE Wallet >>> --------------- >>> >>> If I must use KDE wallet for this opensuse system to work, then it >>> should say: "you *must* do this or your system won't work". >>> >>> If KDE Wallet is optional, then it should learn to know when it's not >>> wanted. If I tell it to go away, I do not want it to keep coming back. >>> >> >> Go into System Settings, open the Account Details, go to KDE Wallet and >> uncheck "Enable the KDE wallet subsystem" >> >> If, for some reason, you don't find it there, just type "wallet" into the >> search box on the System Settings first page and it will highlight the >> relevant module. >> >> -- >> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse+owner(a)opensuse.org >> > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Why using postfix at all? [Was: Why is dovecot using user home directory?]
by Carlos E. R. 23 Aug '14

23 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2014-08-19 at 09:51 -0400, Patrick Shanahan wrote: > * Anton Aylward <> [08-19-14 09:22]: >> 2. The spam/av processing can be done within procmail so why not >> eliminate the sendmail/postfix step and have fetchmail hand off >> to local procmail directly? >> >> >> What this boils down to is this: >> >> Do you have a good reason to apply the processing that can >> *only* be carried out by sendmail/procmail in this path? >> >> >> I poured over this and could not find any. >> >> >> Please note: I'm not saying "Postfix is not needed" in any universal >> sense. I said "in this path". > > I have postfix and by fetchmail handing to postfix I get *all* mail logged > in /var/log/mail, ie: not just fetchmail's and procmail's logs. > > It was a *conscious* decision :^). We forgot another important reason(s): parallelization, speed, and safety. spamd/spamc called from procmail takes 1..3 seconds per email in my machine, but often it goes up to 5 seconds per email (I see this in the log), and even more. This is due not to lack of cpu power, but for waiting for online tests to respond or timeout. See (all are entries trimmed from the 2014-08-15 log): _00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD scantime=1.1,size=5696,user=cer,uid=1000,required_score=5.0, _00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD scantime=1.2,size=6345,user=cer,uid=1000,required_score=5.0, _00,DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_DKIM_INVALID,URIBL_BLOCKED scantime=1.7,size=7578, _00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,URIBL_BLOCKED scantime=1.9,size=5677,user=cer,uid=1000,re _00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_TVD_MIME_EPI,URIBL_BLOCKED scantime=1.6,size=6297,user=cer _00,DKIM_SIGNED,RCVD_IN_DNSWL_HI,T_DKIM_INVALID,URIBL_BLOCKED scantime=2.7,size=7320,user=cer,uid _00,DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_DKIM_INVALI _00,DKIM_SIGNED,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,T_DKIM_INVALID,URIBL_BLOCKED scantime=1.6,size=7151 _00,RCVD_IN_DNSWL_HI,URIBL_BLOCKED scantime=13.3,size=6114,user=cer,uid=1000,required_score=5.0 _00,RCVD_IN_DNSWL_HI scantime=13.3,size=5946,user=cer,uid=1000,required_score=5.0,rhost=localhost 00,RCVD_IN_DNSWL_HI scantime=4.0,size=7131,user=cer,uid=1000,required_score=5.0,rhost=localhost 00,DKIM_SIGNED,RCVD_IN_DNSWL_HI,T_DKIM_INVALID,URIBL_BLOCKED scantime=4.1,size=8650,user=cer 0,RCVD_IN_DNSWL_HI,URIBL_BLOCKED scantime=5.3,size=6182,user=cer,uid=1000,required_score=5.0 00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,SPF_SOFTFAIL,URIBL_BLOCKED scantime=6.6,size=45027, You can see one scantime=13.3 8seconds) in there (with size=6114). Two, actually. On occasion, 12 seconds per email becomes typical, till I find out that a particular online spamassassin test has to be disabled because the internet server it queries no longer responds. Well, if you use fetchmail calling procmail directly, only one email at a time can be processed, but if you put postfix in the toolchain, it queues email internally, and does so safely, because fetchmail can not tell the imap/pop server to delete that email till postfix has saved it to a file in the queue, and tells fetchmail "Ok, I got it". This is so in the entire chain of servers and daemons, local and remote (should be). Old Unix hands would tell you to mount the partition used for mail processing with the option "sync", for this safety reason. This way fetchmail can run at top speed, without waiting for spam/av processing, because postfix is safely storing email in queues on disk, prior to processing it. And postfix can feed typically 2 procmail processes per user, but if you have the power, you can let it call dozens simultaneously, and that means several spamc/spamd processes running simultaneously. When each email takes a few seconds to be processed, most of that time waiting idle (no cpu used), well, feeding say, 5 emails simultaneously does speed things up a bit. This is a big issue when you get a queue of a thousand emails. It can takes hours if you do one at a time. Ah, and procmail can handle several simultaneous processes, even when using mbox files, because it by default uses a different lock file per destination folder. Of course, if all email goes to the same folder, it has to wait. And typically, the spamc call is in another rule. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlP0fMgACgkQtTMYHG2NR9XyyACZAUfz1CJnLJALhrajtbcEkI1O 9kMAn0z1fYqL1JJNMPXn1kHX62gJRC3c =UAnX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 36

[opensuse] How would you do this?
by Lew Wolfgang 23 Aug '14

23 Aug '14

Hi Folks, I've got a web site that's being "retired", so to speak, and will be replaced with a shiny new presentation. But I want to keep the old one on-line for historical reference at a different domainname. For example, the domain hosting the new content would be foobar.org, the one I want to keep for history would be foobar.info. So I need to go through the old html and substitute any references of foobar.org to foobar.info. There are 3705 separate lines in probably 1000 files in a large filesystem hierarchy containing the string that needs swapping. I'd rather not do it by hand! What would you use? awk? A shell script? Something using grep and sed? Thanks in advance for any advice, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 11

[opensuse] most frequently used applications in top part of KDE4 application launcher
by Istvan Gabor 22 Aug '14

22 Aug '14

Hello: I would like to have the list of the most frequently used applications instead of recently used applications in KDE4 application launcher (start menu, set to classic style). I see there is a favorites menu but launching application from there requires a more complex, two-way mouse navigation, easy to lose focus. Starting applications from the top part of the launcher easier and requires only one way mouse movement. Shortly, I want favorites to be placed where recently used applications are now. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] MSI touch screen all-in-one screen brightness
by Istvan Gabor 22 Aug '14

22 Aug '14

Hello: I have a new MSI AIO (all in one) AE200 touch screen computer. I installed openSUSE 13.1 with its default KDE4 on it. The installation was very smooth, and - as a very pleasant surprise - the touch screen has been working "out of the box". I have configured KDE more or less to my liking, it's OK. But there is one thing I don't know is normal or not: The device has buttons to increase/decrease screen brightness but they don't have any effect. Is it possible that they don't adjust the brightness directly but require the OS for an effect? I have worked only with regular monitors so far where I can change monitor settings directly using the buttons/monitor's menu. How can I change the screen brightness in this device? I googled but could not find anything. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 5

[opensuse] procmail, dovecot-lda, and lockfiles: problems.
by Carlos E. R. 22 Aug '14

22 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I had this type of rule in .procmailrc: :0f * ^X-Mailinglist: opensuse | /usr/bin/formail -bfi 'Reply-To: "OS-en" <opensuse(a)opensuse.org>' :0 a: $HOME/Mail/_Lists/os-en which, following talks here, I change to this type of rule: DELIVER="/usr/lib/dovecot/dovecot-lda" ... :0f * ^X-Mailinglist: opensuse | /usr/bin/formail -bfi 'Reply-To: "OS-en" <opensuse(a)opensuse.org>' :0 aw: | $DELIVER -m _Lists/D-os-en which produces these entries in the procmail log: procmail: Couldn't determine implicit lockfile from "/usr/lib/dovecot/dovecot-lda" procmail: Locking ".lock" procmail: Executing "/usr/lib/dovecot/dovecot-lda,-m,lists/D-os-en" procmail: Assigning "LASTFOLDER=/usr/lib/dovecot/dovecot-lda -m lists/D-os-en" procmail: Unlocking ".lock" procmail: Notified comsat: "cer@:/usr/lib/dovecot/dovecot-lda -m lists/D-os-en" The reason is explained in this section of the manual: Local lockfile If you put a second (trailing) ':' on the first recipe line, then procmail will use a locallockfile (for this recipe only). You can optionally specify the locallockfile to use; if you don't however, procmail will use the destination filename (or the filename following the first '>>') and will append $LOCKEXT to it. It also says this about that error message: Couldn't determine implicit lockfile from "x" There were no `>>' redirectors to be found, using simply `$LOCKEXT' as locallockfile. The manual also discourages against using a global lock: LOCKFILE Global semaphore file. If this file already exists, procmail will wait until it has gone before proceeding, and will create it itself (cleaning it up when ready, of course). If more than one lockfile are specified, then the previous one will be removed before trying to create the new one. The use of a global lockfile is discouraged, whenever possible use locallock- files (on a per recipe basis) instead. The working is thus. In the first type of recipe: :0 a: $HOME/Mail/_Lists/os-en procmail easily determines that it has to use "$HOME/Mail/_Lists/os-en.lock" as local lock file. On the second type, however: :0 aw: | $DELIVER -m _Lists/D-os-en It knows that there is a pipe, so it looks for the redirect to file at the end of the line to find out what is the destination "folder" of the recipe to create a lock with that name, and not finding one, it simply creates one with the default name of ".lock", which ends being a global lock and breaks parallelization of procmail. The solution, it would seem, is for me to specify a lock file myself: :0f * ^X-Mailinglist: opensuse | /usr/bin/formail -bfi 'Reply-To: "OS-en" <opensuse(a)opensuse.org>' :0 aw: HOME/Mail/_Lists/os-en.lock | $DELIVER -m _Lists/os-en But this creates a new problem: procmail: [20651] Thu Aug 21 12:02:34 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: Unlocking "/home/cer/Mail/_Lists/yp-os-en.lock" procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20702] Thu Aug 21 12:02:34 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20815] Thu Aug 21 12:02:35 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20773] Thu Aug 21 12:02:35 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20652] Thu Aug 21 12:02:42 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" ... procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20652] Thu Aug 21 12:04:27 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: Executing "/usr/lib/dovecot/dovecot-lda,-m,_Lists/os-en" 2 minutes timeout. procmail: [20702] Thu Aug 21 12:05:31 2014 procmail: [20794] Thu Aug 21 12:05:31 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" ... procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20773] Thu Aug 21 12:06:03 2014 procmail: Locking "/home/cer/Mail/_Lists/os-en.lock" procmail: [20651] Thu Aug 21 12:06:08 2014 procmail: Assigning "LASTFOLDER=/usr/lib/dovecot/dovecot-lda -m _Lists/os-en" procmail: Unlocking "/home/cer/Mail/_Lists/os-en.lock" procmail: Couldn't unlock "/home/cer/Mail/_Lists/os-en.lock" procmail: Notified comsat: "cer@:/usr/lib/dovecot/dovecot-lda -m _Lists/os-en" From opensuse+bounces-162890-......... Thu Aug 21 12:02:10 2014 Subject: [opensuse] Re: on why maildir isn't standard... Folder: /usr/lib/dovecot/dovecot-lda -m _Lists/os-en 9722 The problem is that dovecot-lda also checks and creates a lock file, using that same lock file, of course (/home/cer/Mail/_Lists/os-en.lock). As the lock already exists, it waits... for ever, or till I manually delete the lock file. What should I do? I think that I should tell procmail to abstain from creating a lock file at that point, and let "dovecot-lda" handle it itself. But I have not found a setting for that in procmail. Perhaps removing the last ":" from the recipe :-? But that would instead create a global lock file instead, which breaks parallellization. The manual says: Recipes A line starting with ':' marks the beginning of a recipe. It has the following format: :0 [flags] [ : [locallockfile] ] <zero or more conditions (one per line)> <exactly one action line> ... Local lockfile If you put a second (trailing) ':' on the first recipe line, then procmail will use a locallockfile (for this recipe only). You can optionally specify the locallockfile to use; if you don't however, procmail will use the destination filename (or the filename following the first '>>') and will append $LOCKEXT to it. So I think I should specify a dummy lock file somewhere, perhaps under "/run/user/[UID]/" for speed. But I don't know how to automatically create a folder hierarchy there for my use, on every boot. And link to it by name, not UID. I may concoct something. I will try that. Reading material: The documentation on the dovecot site doesn't mention the issue at all: <http://wiki2.dovecot.org/procmail> And on the procmail site: <http://www.procmail.org/>, many of the links are dead. * a searchable archive of the procmail mailing list <http://www.rosat.mpe-garching.mpg.de/mailing-lists/procmail/> --> Error 404 * Era Eriksson's Procmail Mini-FAQ <http://www.iki.fi/era/procmail/mini-faq.html> redirects to <http://partmaps.org/>, which is in German, I think. Google translate translates: +++······························· Simple shower enclosure or shower cubicle luxury Posted by Maxi on August 14, 2014 . No comments . Besides shower enclosures, which are available in different shapes, you can buy individual shower elements, such as a shower door or a shower wall or a shower enclosure for the tub. Especially handy are the foldable shower enclosures, which are simply placed on the bathtubs and there it ·······························++- I guess that does not help me. :-} * Peter Hartzler's SmartList FAQ <http://www.hartzler.net/smartlist/SmartList-FAQ.html> - --> The requested URL /smartlist/SmartList-FAQ.html was not found on this server. * Jari Aalto's Procmail resources <http://pm-doc.sourceforge.net/> There is nothing here, just a stub from sourceforge. But it links to "Procmail Documentation main page" at <http://pm-doc.sourceforge.net/doc/>, which finally contains real text. I'll read that. There is an interesting section: «4.11 Local lockfile usage» [...] Nope, no way to disable the lock. «5.4 Flag w, lock file and recipe with pipe(|) » It says that if you do not use 'w', the lock file is inmediately removed after handling over to the pipe. BUT, if the pipe fails, procmail would not learn about it, and the email would be lost (if it fails and knows about it, the email is sent instead to the default folder). * Nancy McGough's Procmail Quick Start page at it's primary server or from a mirror. - --> <http://www.ii.com/internet/robots/procmail/qs/>, and the site is up (PROCMAIL QUICK START - An introduction to email filtering with a focus on procmail). Last modified: 2007-11-27T14:37:28 CET There is an interesting info here: it says to run "procmail -v" to find out the lock strategy used by procmail (<http://www.ii.com/internet/robots/procmail/qs/#lock>). It turns out to be: Locking strategies: dotlocking, fcntl() The procmail people aparently decided, long ago, not to use kernel locks - see <http://pm-doc.sourceforge.net/doc/#compiling_procmail_and_choosing_locking_…> +++······························· General advice: Everything except dot locking is usually broken. [stephen, <199607292139.XAA12433(a)hera.cuci.nl>]. Remove fcntl() and lockf(), only allow flock() (or omit it completely) Kernel locks don't work. But that's all some programs use. Across a networked filesystem, lockf() doesn't work, fcntl() and flock() should, but they don't either because the lockd is buggy. Mailtool uses fcntl() but does it wrong, so that's another problem. The only thing that works on all platforms, all networks, all the time are .lock files. ·······························++- The above mentioned link on <http://www.ii.com/internet/robots/procmail/qs/#lock> has very interesting info on locking, but some of the links are dead. +++······························· Mailbox Locking If you use a mail or news client to change a mailbox that is receiving messages — for example, to delete a message — make sure that both procmail and your client use the same locking scheme. To determine what locking strategies are used by your installation of procmail, and the order in which these locking strategies are used, run: procmail -v and look at the value of “Locking strategies.” To learn about file locking, see: 11.4 How does folder locking work? and questions 11.5, 11.6, & 11.16 in the UW Pine Information Center's Info for systems administrators, developers, etc. This is useful to read even if you do not use Pine. (working link). File locking in the Era's Procmail FAQ (redirects to page about showers) 4.11 Local lockfile usage and 4.12 Global lockfile in Jari's Procmail Tips (broken link: 404) The thread "Lock files - confused" in the Procmail mailing list archives (working link) Configuring Netscape Mail on Unix by Jamie Zawinski — this is useful to read even if Netscape is not your mail client. (redirects to silly netscape.aol.com page) [!] Make sure that you are not delivering to mailboxes in Unix spool (mbox) format on an NFS or any other network file system since locking does not help on those systems. For a possible workaround to this, see the comp.mail.imap message Re: UoW IMAP, lock files and multiple servers by Mark Crispin. The Netscape mail client does no locking of its local mailboxes, meaning that there is no safe way to deliver directly to them. Kmail seems to be flaky about locking local mailboxes. For details, search the KDE Documentation for procmail. ·······························++- * Timo Salmi's procmail tips and recipes <http://www.uwasa.fi/~ts/info/proctips.html> redirects to <http://www.netikka.net/tsneti/info/proctips.php>, with the correct info. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlP2VLgACgkQtTMYHG2NR9XWwgCfagPCZRpg31oX5LcNzlXz1Kvz i8wAn3D59PZBDvqsas8QEvNc9uUycGfb =A9yO -----END PGP SIGNATURE-----

3 2

[opensuse] Connecting to MS communicator
by Klaus Vink Slott 22 Aug '14

22 Aug '14

On my work they are replacing our telephone system with a Microsoft lync 2010 solution (sigh). One colleague using Pidgin on Ubuntu have had success in using Pidgin with pidgin-sipe on top. He claims he is able to make and receive voice calls using this combo. I have found the same packet for OpensSUSE and my pidgin now registers with the MS phone server. My colleagues can see my status. But I have no sign of a voice call possibility in any menu. Does anybody have a guess on what I am missing to get voice support in pidgin/sipe? Any other suggestions on a framework for connecting to MS-com are also welcome (other than running windows in a VM). I have tried Telepathy for IM in the past but back then it was a pain to keep connected and often broke after a update. -- Regards Klaus -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] hylafax/avantfax with php 5.4+ (any fixes or interest in helping fix it?)
by David C. Rankin 21 Aug '14

21 Aug '14

All, The elegant fax handling solution of hylafax/avantfax will not work with php >= 5.4. I have discussed the issue with the developer on the hylafax list and understand that avantfax is basically broken until it can be rewritten but the developer hasn't, and probably won't, have time to fix/rewrite avantfax over the next few months. The purpose of the post here is to ask: (1) are there any users of avantfax that have patched avantfax to work with php 5.4+; (2) any interest in doing so? If there is anyone fluent in php that is interested, I'm interested in helping and have a couple of installs to test with. However, I don't have the time or php fluency required to shoulder the rewrite. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4