December 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] bluetooth keyboard
by jdd＠dodin.org 19 Dec '19

19 Dec '19

Hello, I wonder if it's possible on Leap 15.1 to use a BlueTooth keyboard? (like this http://www.dodin.org/wiki/pmwiki.php?n=Bavardages.ClavierPhysiquePourTablet…) the device is seen, the numeric code accepted, but the keyboard do not works any clue? thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 6

[opensuse] Experience with openslp?
by Daniel Spannbauer 19 Dec '19

19 Dec '19

Hello, are here people with openslp experience? If have som troubles with it and the mailing list of openslp is dead. Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] desktop backgrounds plasma5
by Patrick Shanahan 18 Dec '19

18 Dec '19

where are the desktop backgrounds for kde5/plasma5 stored? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] sudo related question
by Carlos E. R. 18 Dec '19

18 Dec '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I wrote a little script to change group owner and permissions of my photo tree: #!/bin/bash find /data/storage_b/cer/Pictures /data/storage_b/cer/Pictures.tmp /data/storage_b/cer/Pictures.astro -type f \ -exec sudo chgrp cer '{}' \; \ -exec sudo chmod u+r+w,g+r+w,o+r-w-x,-t '{}' \; \ -exec sudo setfacl -m g:users:r '{}' \; With corresponding sudoers file entries: cer Telcontar = (root) /usr/bin/setfacl -m g\:users\:rx * cer Telcontar = (root) /usr/bin/setfacl -m g\:users\:r * cer Telcontar = (root) /usr/bin/chgrp cer * cer Telcontar = (root) /usr/bin/chmod u+r+w+x\,g+w+x\,o-r-w-x\,+t * cer Telcontar = (root) /usr/bin/chmod u+r+w\,g+r+w\,o+r-w-x\,-t * The script works, but there is a nuisance side effect on syslog: thousands of photos, so several times as many long entries: <10.6> 2019-12-04 22:53:10 Telcontar sudo - - - pam_unix(sudo:session): session opened for user root by (uid=0) <10.6> 2019-12-04 22:53:10 Telcontar sudo - - - pam_unix(sudo:session): session closed for user root <4.5> 2019-12-04 22:53:10 Telcontar sudo - - - cer : TTY=pts/83 ; PWD=/data/storage_b/cer ; USER=root ; COMMAND=/usr/bin/chgrp cer /data/storage_b/cer/Pictures/2016/08/DSC_1403.JPG <10.6> 2019-12-04 22:53:10 Telcontar sudo - - - pam_unix(sudo:session): session opened for user root by (uid=0) <10.6> 2019-12-04 22:53:10 Telcontar sudo - - - pam_unix(sudo:session): session closed for user root <4.5> 2019-12-04 22:53:10 Telcontar sudo - - - cer : TTY=pts/83 ; PWD=/data/storage_b/cer ; USER=root ; COMMAND=/usr/bin/chmod u+r+w,g+r+w,o+r-w-x,-t /data/storage_b/cer/Pictures/2016/08/DSC_1403.JPG <10.6> 2019-12-04 22:53:10 Telcontar sudo - - - pam_unix(sudo:session): session opened for user root by (uid=0) <10.6> 2019-12-04 22:53:10 Telcontar sudo - - - pam_unix(sudo:session): session closed for user root <4.5> 2019-12-04 22:53:10 Telcontar sudo - - - cer : TTY=pts/83 ; PWD=/data/storage_b/cer ; USER=root ; COMMAND=/usr/bin/setfacl -m g:users:r /data/storage_b/cer/Pictures/2016/08/DSC_1403.JPG <10.6> 2019-12-04 22:53:10 Telcontar sudo - - - pam_unix(sudo:session): session opened for user root by (uid=0) <10.6> 2019-12-04 22:53:10 Telcontar sudo - - - pam_unix(sudo:session): session closed for user root This spams my log file and makes the script much slower. Ideas? I can of course run the script directly as root. sudo find? With a loooong sudoers line, more "dangerous" when I put the '*' somewhere - I can't put the entire script. sudo script? I thought that was forbidden. I can not try anything now, the script has not finished... - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXegr/xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVls8Anjp0Nq2+1ZUGf/zDkOtb zpeycaldAKCDajGo5hQkExItb39y5y2IeoT/oA== =SnEm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 31

[opensuse] System failing to suspend on inactivity
by Richmond 18 Dec '19

18 Dec '19

My system has started failing to suspend quite regularly. Here is an example: PM: Suspending system (mem) Suspending console(s) (use no_console_suspend to debug) wlan1: deauthenticating from 28:28:5d:bd:0a:80 by local choice (Reason: 3=DEAUTH_LEAVING) sd 0:0:0:0: [sda] Synchronizing SCSI cache sd 0:0:0:0: [sda] Stopping disk xhci_hcd 0000:06:00.0: WARN: xHC CMD_RUN timeout suspend_common(): xhci_pci_suspend+0x0/0xc0 [xhci_pci] returns -110 pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -110 dpm_run_callback(): pci_pm_suspend+0x0/0x130 returns -110 PM: Device 0000:06:00.0 failed to suspend async: error -110 PM: Some devices failed to suspend, or early wake event detected sd 0:0:0:0: [sda] Starting disk 4.12.14-lp150.12.82-default #1 SMP Tue Nov 12 16:32:38 UTC 2019 (c939e24) x86_64 x86_64 x86_64 GNU/Linux I am using kde: /bin/sh /usr/bin/startkde /usr/lib64/libexec/kf5/start_kdeinit --kded +kcminit_startup kdeinit5: Running... kded5 [kdeinit5] /usr/lib64/libexec/polkit-kde-authentication-agent-1 /usr/lib64/libexec/kdeconnectd /usr/lib64/libexec/org_kde_powerdevil kwin_x11 It is when suspending with the power saver inactivity. If I manually suspend from the menu it works, although I have not tried it over and over. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] The fetchmail trap
by Wolfgang Mueller 18 Dec '19

18 Dec '19

Not receiving mail any more since Thursday, 12 December, I found out that the mail is still fetched from the provider's server and destroyed there, but no more put on /var/spool/mail/<user>. No idea where it finally arrives, probably on /dev/null. I do not know which patch I have installed on last Thursday, but I'm convinces it is a patch, because I observe the error on all three of my computers, which I updated all at the same time, unfortunately. For getting mail again, I do no rely on the fetchmail daemon any more, which has become a trap, but I use the direct POP3 mail server access of Firefox. It's a pity. Sad greetings, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 13

[opensuse] Is there a GEBC build for opensuse with patch 3? (GNU External Ballistics Computer)
by David C. Rankin 18 Dec '19

18 Dec '19

All, Does anyone know if GEBC is being built for openSUSE. I don't find it searching (but I can't search all buildservice either). There is a patch 3 that extends what was patch 2 for years, but there are problems loading earlier saved .gbc files. (I've reported on SourceForge) I'm curious if anyone is building and has fixed the open issue with the latest patch. If not, I'll probably just manually add the difference between patch 2 and patch 3 and find the issue that way. (here is to hoping I don't have to :) I haven't updated the .spec since 11.4... -- 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

1 0

[opensuse] An early Xmas present
by Per Jessen 17 Dec '19

17 Dec '19

I know disks keep getting bigger every time you don't look, but this is ridiculous: # smartctl -T permissive -a /dev/sdd smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.7.10-1.32-default] (SUSE RPM) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org Vendor: /1:0:1:0 Product: User Capacity: 600,332,565,813,390,450 bytes [600 PB] Logical block size: 774843950 bytes In fact, this is a Seagate 8TB drive, but it's obviously not doing too well. :-) -- Per Jessen, Zürich (11.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 12

Re: [opensuse] Software Defined Radio
by James Knott 17 Dec '19

17 Dec '19

On 2019-12-17 01:39 PM, Lew Wolfgang wrote: > BTW, last night I found my old AM/FM radio that I haven't used for more > than ten-years, at least. I set it to the AM band and walked around a > bit > listening to both the upper and lower bands between stations. It > actually > works as a very crude interference collector! I was able to hear > interference > from the powerline adapter itself at about 15-cm. Farther away than that > it was undetectable. I followed the in-wall power wires and didn't pick > up anything. The Visio flat-screen television was much noisier than the > powerline adapter, as was the microwave oven, even with it not cooking > anything. I should make a more detailed survey sometime. Granted, > using an AM radio like this isn't a true field strength meter, but > it's still > a data point. The neighbor's SSB interference would have boomed in, > swamping even 50-Kw clear-channel AM stations. An AM radio wouldn't have a hope of detecting interference at the VHF and higher frequencies. AM runs roughly 500 KHz to 1.5 MHz. As for your neighbour, unless they're operating on the 160 M band, their transmissions will be at a higher frequency than AM. This means the problem is either the AM radio is unable to tolerate the strong signal, which indicates a flaw in the radio, or there is external mixing going on. If there was a fault with the transmitter, it would generate harmonics, which are even further from the AM band. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Software Defined Radio
by James Knott 17 Dec '19

17 Dec '19

On 2019-12-17 01:39 PM, Lew Wolfgang wrote: > Moving this interesting thread to off-topic. > > On 12/16/19 2:20 PM, James Knott wrote: >> On 2019-12-16 05:17 PM, Patrick Shanahan wrote: >>> if a tree falls in the forest and no one hears it, did it make a sound? >> >> The problem with that is interference with modern communications is >> not noticed until it causes a complete failure. The signal is either >> receivable or or it's not, with little in between. On FM radio, the >> signal to noise ratio would gradually decrease, but it took a fair >> bit to be noticeable. It's not like AM radio where the interference >> was obvious. > > So what are we to do? Microwave ovens make interference, should we > dump them? Automobiles emit RFI from their ignition systems, and > motors in household devices may generate voltage spikes due to inductive > kick. Ditch them all? > Microwave ovens, baby monitors, WiFi and other devices use the ISM bands, where there is no protection from interference. Auto engines produce nowhere near the interference they used to. One of the first steps to reduce it was the resistor spark plugs, which have an internal resistor. Also, the frequencies generated by cars, motors, etc. are fairly low, so by the time you reach the VHF spectrum, they're gone. This is not the case with data over power lines. As I mentioned, they symbol rate for 100 Mb & Gb is 125 M symbols (baud) per second. This means a much greater potential for interference with modern communications. > IEEE and others have standards for powerline systems that are approved by > the FCC. I don't hear any trees falling in my forest, should I ask my > neighbors > if they hear falling trees? Presumably I'd be the first to be > affected by EMI/RFI > from my own devices, true? > > BTW, last night I found my old AM/FM radio that I haven't used for more > than ten-years, at least. I set it to the AM band and walked around a > bit > listening to both the upper and lower bands between stations. It > actually > works as a very crude interference collector! I was able to hear > interference > from the powerline adapter itself at about 15-cm. Farther away than that > it was undetectable. I followed the in-wall power wires and didn't pick > up anything. The Visio flat-screen television was much noisier than the > powerline adapter, as was the microwave oven, even with it not cooking > anything. I should make a more detailed survey sometime. Granted, > using an AM radio like this isn't a true field strength meter, but > it's still > a data point. The neighbor's SSB interference would have boomed in, > swamping even 50-Kw clear-channel AM stations. > > Regards, > Lew > > > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0