Updated quite a few packages this morning, including tdm. I could hardly believe my ears, but a tdm restart played the kde sign-on music, so I got a terminal on tty1 and ran speaker-test -c2, worked a treat.
Rebooted just to make sure I wasn't hallucinating, worked again.
So you found whatever was killing my audio as soon as x started.
Thank you, thank you, thank you, thank you!
Did I say it yet? A tip of my Woolrich hat, and a hearty Thank you.
Do I dare ask what it was?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2018/07/07 07:39 PM, Gene Heskett wrote:
Updated quite a few packages this morning, including tdm. I could hardly believe my ears, but a tdm restart played the kde sign-on music, so I got a terminal on tty1 and ran speaker-test -c2, worked a treat.
Rebooted just to make sure I wasn't hallucinating, worked again.
So you found whatever was killing my audio as soon as x started.
Thank you, thank you, thank you, thank you!
Did I say it yet? A tip of my Woolrich hat, and a hearty Thank you.
Do I dare ask what it was?
Either bug 2844 or 2845, most likely the second one. http://bugs.pearsoncomputing.net/show_bug.cgi?id=2844 http://bugs.pearsoncomputing.net/show_bug.cgi?id=2845
If you didn't have all arts/tdemultimedia packages installed (perhaps because of a selective installation), playing OGG files was crashing the sound server.
Glad you are enjoying the fix :-)
Cheers Michele
On Saturday 07 July 2018 09:09:47 Michele Calgaro wrote:
On 2018/07/07 07:39 PM, Gene Heskett wrote:
Updated quite a few packages this morning, including tdm. I could hardly believe my ears, but a tdm restart played the kde sign-on music, so I got a terminal on tty1 and ran speaker-test -c2, worked a treat.
Rebooted just to make sure I wasn't hallucinating, worked again.
So you found whatever was killing my audio as soon as x started.
Thank you, thank you, thank you, thank you!
Did I say it yet? A tip of my Woolrich hat, and a hearty Thank you.
Do I dare ask what it was?
Either bug 2844 or 2845, most likely the second one. http://bugs.pearsoncomputing.net/show_bug.cgi?id=2844 http://bugs.pearsoncomputing.net/show_bug.cgi?id=2845
If you didn't have all arts/tdemultimedia packages installed (perhaps because of a selective installation), playing OGG files was crashing the sound server.
I think I had it all, and haven't added anything tde related recently.
Glad you are enjoying the fix :-)
Yes, and because in my excitement over its working, I neglected to start ~/bin/mailwatcher after the reboot, which starts fetchmail for me, and links the incoming email directly into kmail, I did not get the first thank you message back, and just now sent another when I saw there had been no incoming while I was taking a morning nap. Fixed, 31 fetched when fetchmail was launched.
Can I blame it on oldtimers? :) If you're ever in north central WV USA, I've got an imitation (I'm a DM-II so its near beer) hand cooler for all.
Cheers Michele
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Either bug 2844 or 2845, most likely the second one. http://bugs.pearsoncomputing.net/show_bug.cgi?id=2844 http://bugs.pearsoncomputing.net/show_bug.cgi?id=2845
If you didn't have all arts/tdemultimedia packages installed (perhaps because of a selective installation), playing OGG files was crashing the sound server.
I think I had it all, and haven't added anything tde related recently.
Actually it was probably bug 2844. The vorbis OGG plugin was simply "nuking" your input, i.e. reading the file without playing any sound. Depending on which package was installed or not, that plugin would have been used to play the login sound.
Glad you are enjoying the fix :-)
Yes, and because in my excitement over its working, I neglected to start ~/bin/mailwatcher after the reboot, which starts fetchmail for me, and links the incoming email directly into kmail, I did not get the first thank you message back, and just now sent another when I saw there had been no incoming while I was taking a morning nap. Fixed, 31 fetched when fetchmail was launched.
Why don't you set it to start automatically when you log into TDE? So you won't forget again.
Cheers Michele
On 2018-07-08 01:39:53 Michele Calgaro wrote:
Yes, and because in my excitement over its working, I neglected to start ~/bin/mailwatcher after the reboot, which starts fetchmail for me, and links the incoming email directly into kmail, I did not get the first thank you message back, and just now sent another when I saw there had been no incoming while I was taking a morning nap. Fixed, 31 fetched when fetchmail was launched.
Why don't you set it to start automatically when you log into TDE? So you won't forget again.
I believe the idea is to have mailwatcher running whether or not one is logged in, so that the mail is delivered as e.g. USPS requires.*
Leslie
*"Neither snow nor rain nor heat nor gloom of night stays these couriers from the swift completion of their appointed rounds."
On Sunday 08 July 2018 02:55:33 J Leslie Turriff wrote:
On 2018-07-08 01:39:53 Michele Calgaro wrote:
Yes, and because in my excitement over its working, I neglected to start ~/bin/mailwatcher after the reboot, which starts fetchmail for me, and links the incoming email directly into kmail, I did not get the first thank you message back, and just now sent another when I saw there had been no incoming while I was taking a morning nap. Fixed, 31 fetched when fetchmail was launched.
Why don't you set it to start automatically when you log into TDE? So you won't forget again.
I believe the idea is to have mailwatcher running whether or not one is logged in, so that the mail is delivered as e.g. USPS requires.*
Leslie
Not really. It has to run as me, the only carbon-based lifeform that accesses this computer, and once booted, I rarely log out for weeks at a time.
Running as me, also leads to all sorts of logging permission problems in /var/log, so I finally gave up and moved all those log files into ~/log, redirecting logrotate to do its thing there. I did that about 4 years ago and haven't had to putz with it since.
fetchmail feeds procmail, who proceeds to check incoming for viri and spam, and sends several phony illegits to /dev/null, the spam gets graded by spamassassin but still comes into kmail by being placed in /var/mail/me. procmail can also generate other names depending on who its from. Where mailwatcher comes into play is it launches an instance of inotifywait to watch /var/mail, returning the name of the file that the mail was written to when its closed. That triggers a dbus msg to kmail to go get the mail, and it relaunches another instance of inotifywait to replace the one that died returning the filename.
All this, when working, reduces my work to handle incoming mail to hitting the + key to goto the next unread msg, if I can reply, I select the reply style, type my answer as I'm doing now, and a ctrl+return sends it. Everything else is done by the computer and these scripts with zero intervention by me. I mean, computers are supposed to do as we wish, right? Makes perfect sense to me. :)
Now, if I just had a good idea where to put the launching command so it was started by my logging in, the only other thing would be to assure that kmail is running on workspace 10. Sometimes it autostarts, but only sometimes.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2018/07/08 04:56 PM, Gene Heskett wrote:
Now, if I just had a good idea where to put the launching command so it was started by my logging in, the only other thing would be to assure that kmail is running on workspace 10. Sometimes it autostarts, but only sometimes.
You can start for example from TDE control center -> autostart manager Cheers Michele
On Sunday 08 July 2018 05:42:12 Michele Calgaro wrote:
On 2018/07/08 04:56 PM, Gene Heskett wrote:
Now, if I just had a good idea where to put the launching command so it was started by my logging in, the only other thing would be to assure that kmail is running on workspace 10. Sometimes it autostarts, but only sometimes.
You can start for example from TDE control center -> autostart manager Cheers Michele
I do not have such a critter in my tde control center menus.
But synaptic might have found it, installing now.
Yup now have that in the menu's. Added ~/bin/mailwatcher & So we'll see on the next reboot.
Thank you Michele.
On Sunday 08 July 2018 09.56:07 Gene Heskett wrote:
fetchmail feeds procmail, who proceeds to check incoming for viri and spam, and sends several phony illegits to /dev/null, the spam gets graded by spamassassin but still comes into kmail by being placed in /var/mail/me. procmail can also generate other names depending on who its from. Where mailwatcher comes into play is it launches an instance of inotifywait to watch /var/mail, returning the name of the file that the mail was written to when its closed. That triggers a dbus msg to kmail to go get the mail, and it relaunches another instance of inotifywait to replace the one that died returning the filename.
Well, I'll sound as a noob, but what exactly does this (to me) very complicated way of doing bring?
I mean, for 20 years almost I've been "simply" downloading my mail with kmail, using a few filters to post the messages to directories for clarity.
I used to run spam filters, but since i got modern and also read my mail on a smartphone I had to hire an external service for that.
Thierry
On Sunday 08 July 2018 06:00:25 Thierry de Coulon wrote:
On Sunday 08 July 2018 09.56:07 Gene Heskett wrote:
fetchmail feeds procmail, who proceeds to check incoming for viri and spam, and sends several phony illegits to /dev/null, the spam gets graded by spamassassin but still comes into kmail by being placed in /var/mail/me. procmail can also generate other names depending on who its from. Where mailwatcher comes into play is it launches an instance of inotifywait to watch /var/mail, returning the name of the file that the mail was written to when its closed. That triggers a dbus msg to kmail to go get the mail, and it relaunches another instance of inotifywait to replace the one that died returning the filename.
Well, I'll sound as a noob, but what exactly does this (to me) very complicated way of doing bring?
I mean, for 20 years almost I've been "simply" downloading my mail with kmail, using a few filters to post the messages to directories for clarity.
kmail is single-threaded, and cannot do anything else while its downloading that email. For a member of multiple lists like me, 45 or so, if I had kmail do all that, I'd be waiting 30 minutes a day. So I offloaded that job away from kmail by haveing a background daemon named fetchmail do that, scanning my ISP's mailserver every 2 minutes. So fetchmail and all the stuff procmail can do are now background processes with no effect on kmail. It still goes away when it has been commanded to go get the mail, freezing but not forgetting whats been typed and might appear to freeze while my slow typing might pile up 3 or 4 characters in the buffer, which it will process as soon as it runs out of mail to fetch and sort, which is right there in /var/mail. So thats just a copy operation, takeing perhaps 300 milliseconds as opposed to several minutes if you are on dial up.
I used to run spam filters, but since i got modern and also read my mail on a smartphone I had to hire an external service for that.
Thierry
I might do that, but my $99/year tracphone isn't smart, in fact I need to go get the sim card renewed for another year, its been dead since the 26th of last month. I'd toss it, but if I need to go somewhere a long ways out, I need it to check on the missus as she's an invalid these days or if I should have a breakdown. She's 78, nearly finished by COPD, and breaks bones as if they were soda straws. I'm going on 84, a retired tv station Chief Engineer. A DM-II, my legs are slowly going away so walking to the mailbox is a long trip for them, taking 2 grams of metformin a day and blood pressure stuff and a little rat poison for blood thinner plus a handfull of OTC stuff to keep up bone strength. I'm old enough to recommend you don't get old, its not fun. Avoid it if you can.
But I have "hobbies" that keep me out of the bars. With two cnc'd milling machines and 2 cnc'd lathes, (I did the conversions,) and a garage full of woodworking power tools, I just last fall put a new barrel in old meat in the pot, and am still playing with handloads for what is now a SS (stainless steel) 30" barrel in 6.5 Creedmoor. I've bought 3 boxes of factory rifle shells, and have worn out 4 rifle barrels since about 1961 when I started loading my own. The Creedmoor did a 1.25" 10 shot group at 100 yds on its last trip to the range, but I'm looking for a load that will put 10 in one ragged hole. Thats as good as I can see these days.
And I've already had my 10 minute warning buzzer, a pulmonary embolism, usually fatal, about 3 years back. I don't recommend it as a way to die as its scary as hell. Thats the reason for the rat poison in the pill-tainer.
More than you wanted to know. Lots more. And I'd better go see what the missus wants for breakfast, I play short order cook too.
-
Gene Heskett -
J Leslie Turriff -
Michele Calgaro -
Thierry de Coulon