September 2020 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Unable to delete LVM partition
by Aaron Digulla 20 Sep '20

20 Sep '20

Hi, I've created a Dropbox partition some time ago to when Dropbox stopped supporting BTRFS. I'm now trying to delete the partition using YAST but I get an error: ----- command '/sbin/wipefs --all '/dev/system/dropbox'' failed: stderr: wipefs: error: /dev/system/dropbox: probing initialization failed: Device or resource busy exit code: 1 ----- lsof -n | grep dropbox as root returns nothing. Google found some sources saying that udev locks the device node. Shouldn't lsof report that? How do I unlock the device? I tried "udevadm settle" but that didn't help. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] aspell - myspell - hunspell
by Stakanov 20 Sep '20

20 Sep '20

So, for what I found out: aspell is the historical program. On which built myspell and finally on which bases hunspell. Hunspell should be compatible with libreoffice. Myspell strangely is required for kmail orthografic korrektor (why did they not use hunspell?). Why are there the three, another reason? And then: what is the secret reason (which an irritated German user did raise argument with me, and another one did in the German list in 2018 apparently) that aspell is available in all languages but since 42.3 is missing German. But only in Leap while it is there in TW. Which is curious for a distribution done in Nurimberg. Isn't it? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Incompatibility between Rufus and our Live ISOs
by Dario Faggioli 20 Sep '20

20 Sep '20

Hello, So, here it is what happened to me earlier today. Someone from the local LUG sent a message about him wanting to try Tumbleweed. He downloaded the live ISO, but it was not booting. Errors were some "dracut timeouts" and then the usual "problems-problems- problems, give CTRL-D for maintenance etc". He took the ISO from here: https://software.opensuse.org/distributions/tumbleweed I did some checks and tests, but could not help him much. Later, he came back announcing success in booting into the Live OS. Turns out, he used some Windows tool called "Rufus" for putting the ISO on an USB key. And, apparently, this tool has an history of being potentially (I think it depends on the options) doing stuff that makes our ISOs non-bootable. My friend claims to have just used the said tool, with the default set of options. This how he found out about the incompatibility: https://forums.opensuse.org/showthread.php/529966-Usb-tumbleweed-does-not-g… Now, I had no idea such tool even existed, and I am not at all suggesting that we change anything in our ISOs because of it. It apparently is a quite famous image writing tool for Windows, and live ISOs of other distros apparently work well with it, but let's live this aside for now. In that forum thread, at some point there is this: "I think the openSUSE Live deserve a better explanation page, check for example the similar page for CentOS which warns users about this problem: https://wiki.centos.org/HowTos/InstallFromUSBkey " That page has a list of tools that can be used for "burning" images that work. The Fedora equivalent page is also pretty nice, and has the same information, right upfront: https://getfedora.org/en/workstation/download/ I think we should have something similar in our one. Regards -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)

6 28

[opensuse] Heat
by Carlos E. R. 20 Sep '20

20 Sep '20

(comment, not a question) Hi, A friend's new laptop, a Lenovo E15. With an 8 cores CPU. processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 142 model name : Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz When I load it a bit (about half) with this: mkfifo mdpipe dd if=/dev/nvme0n1p3 status=progress bs=16M | tee mdpipe | pigz > nvme0n1p3.gz & md5sum -b mdpipe | tee -a md5checksum_expanded (source is nvme M2 media, reading at more than 200 Mbyt/s, perhaps 400 (I don't remember for sure), destination is rotating rust, external on usb3, writing at about 60Mb/s, and all the cpu cores working at about 60%, for half an hour, *the machine overheats*. I see it in the log: 2020-09-13T00:23:45.965798+02:00 Rescate kernel: [ 3874.567857] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 27199) 2020-09-13T00:23:45.965816+02:00 Rescate kernel: [ 3874.567857] mce: CPU4: Core temperature above threshold, cpu clock throttled (total events = 27198) 2020-09-13T00:23:45.965817+02:00 Rescate kernel: [ 3874.567859] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 32537) 2020-09-13T00:23:45.965818+02:00 Rescate kernel: [ 3874.567860] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 32537) 2020-09-13T00:23:45.965819+02:00 Rescate kernel: [ 3874.567861] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 32537) 2020-09-13T00:23:45.965820+02:00 Rescate kernel: [ 3874.567862] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 32537) 2020-09-13T00:23:45.965822+02:00 Rescate kernel: [ 3874.567863] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 32537) 2020-09-13T00:23:45.965823+02:00 Rescate kernel: [ 3874.567864] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 32537) 2020-09-13T00:23:45.965824+02:00 Rescate kernel: [ 3874.567865] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 32537) 2020-09-13T00:23:45.965824+02:00 Rescate kernel: [ 3874.567866] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 32537) 2020-09-13T00:23:45.969800+02:00 Rescate kernel: [ 3874.571856] mce: CPU4: Core temperature/speed normal 2020-09-13T00:23:45.969808+02:00 Rescate kernel: [ 3874.571856] mce: CPU0: Core temperature/speed normal 2020-09-13T00:23:45.969809+02:00 Rescate kernel: [ 3874.571857] mce: CPU3: Package temperature/speed normal 2020-09-13T00:23:45.969810+02:00 Rescate kernel: [ 3874.571858] mce: CPU2: Package temperature/speed normal 2020-09-13T00:23:45.969811+02:00 Rescate kernel: [ 3874.571859] mce: CPU7: Package temperature/speed normal 2020-09-13T00:23:45.969812+02:00 Rescate kernel: [ 3874.571860] mce: CPU1: Package temperature/speed normal 2020-09-13T00:23:45.969813+02:00 Rescate kernel: [ 3874.571860] mce: CPU6: Package temperature/speed normal 2020-09-13T00:23:45.969814+02:00 Rescate kernel: [ 3874.571861] mce: CPU5: Package temperature/speed normal 2020-09-13T00:23:45.969815+02:00 Rescate kernel: [ 3874.571861] mce: CPU0: Package temperature/speed normal 2020-09-13T00:23:45.969816+02:00 Rescate kernel: [ 3874.571862] mce: CPU4: Package temperature/speed normal (gkrellm said CPU temp was about 70ºC; when idle, it is 40) I take it that this is designed for. It simply can not take a full load for half an hour, overheats, and reduces the CPU clock to cope. I did put it over a fan platform, no much difference. Maybe more expensive machines cope better. I could feel the case was hot, near the display hinge. No, I'm not asking for help, the machine is as it is. :-) Just remembering Jdd and his hot laptop :-) Luckily the owner will just be doing email and office things. -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar)

4 4

[opensuse] No borders on windows - KDE on 15.2
by James Knott 19 Sep '20

19 Sep '20

One thing I've noticed since updating to 15.2 is there doesn't seem to be anything to mark the edge of a window, so that if the background of one is the same colour as another, to can't see where one ends and the other starts. Is this some sort of new "feature"? If so, it's extremely annoying. For example, I currently have a Seamonkey email window open over a Chromium web page, both with a white background. The only way I can tell where one or the other is, is to see where the Chromium text ends, covered up by the Seamonkey window. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 18

Re: [opensuse] Unable to delete LVM partition
by Andrei Borzenkov 19 Sep '20

19 Sep '20

19.09.2020 17:32, Aaron Digulla пишет: > Am 18.09.20 um 21:07 schrieb Andrei Borzenkov: >> 18.09.2020 21:35, Aaron Digulla пишет: >>>>> lsof -n | grep dropbox >>>>> >>>>> as root returns nothing. >>>>> >>>>> Google found some sources saying that udev locks the device node. >>>>> >>>>> Shouldn't lsof report that? >>>>> >> It depends on how it is used. >> ... >>> I tried to remove it: >>> >>> $ lvremove /dev/system/dropbox --autobackup y --verbose --test >>> TEST MODE: Metadata will NOT be updated and volumes will not be >>> (de)activated. >>> Logical volume system/dropbox contains a filesystem in use. >>> $ mount|grep dropbox >>> $ >>> >>> Who is using the file system? >>> >> What >> >> fuser -c /dev/system/dropbox >> >> says? > > Thanks for the suggestion. That lists all kinds of processes including > PID 1 (systemd): > > /dev/dm-5: 1rce 2rc 3rc 4rc 6rc 9rc > ... plus a ton more > This means that either device /dev/system/dropbox is root filesystem or that /dev/system/dropbox is a file on root filesystem. >> In the worst case it could be lazy unmounted or it could be mounted in >> another namespace. I am not sure if it is possible to list all mounts in >> all namespaces. >> actually "lsns -t mnt" does it. From there it may be possible to see what is mounted in each namespace. But it is probably premature. >> Did you try to reboot? > > Not yet. I was wondering why Linux thinks that the drive is used when > the command line tools can't tell me the process. I'm trying to learn > something right now, not just quickly fix it. > > Regards, > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] [SOLVED] Strongswan fails to configure / stopped working / how to configure on OpenSuse 15.1/15.2
by Glen 19 Sep '20

19 Sep '20

All - On Thu, Sep 17, 2020 at 2:34 AM Carlos E. R. <robin.listas(a)telefonica.net> wrote: > On 17/09/2020 03.16, Glen wrote: > > worked, I wanted to log this in here for our community. > Thankyou :-) Thank you! > > Does anyone here have guidance or an opinion on whether this > > information should be sent to a different list (e.g. opensuse-support) > IMO, here is fine. Good to know, thank you. > > Does anyone here have guidance or an opinion on whether this should be > > bug reported? > Yes, certainly, you should report in Bugzilla. And On Wed, Sep 16, 2020 at 9:10 PM Andrei Borzenkov <arvidjaar(a)gmail.com> wrote: > You should open bug report. Such changes are not acceptable in stable > releases. I just wanted to thank you both for your guidance here. As suggested, I have filed a detailed bug report on this issue here: https://bugzilla.opensuse.org/show_bug.cgi?id=1176735 We shall hope for the best. Thank you! Glen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] e-books
by Dave Howorth 18 Sep '20

18 Sep '20

I'm discussing with a publisher and author of a book how to get an electronic copy of the book. It's published for Kindle, as an ePub (with Adobe DRM) and as a PDF. So I asked how to download the PDF but haven't got a straight answer yet (grr! :) In the meantime, is it easy/possible to read an e-book intended for a Kindle or a DRM-protected ePub? (And I'd rather not start with trying to install Adobe software inside wine unless there's some absolute guarantee of support, and even then I'd prefer not to). -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

13 76

[opensuse] Re: [opensuse-factory] Thunderbird 78 and encryption status
by Wolfgang Rosenauer 17 Sep '20

17 Sep '20

Hi, Am 14.09.20 um 20:53 schrieb Martin Wilck: > Q: "I need to use both GnuPG and Thunderbird in parallel, can I > synchronize my keys?" > A: "No." > > Q: "How is my personal key protected?" > A: "At the time you import your personal key into Thunderbird, we > unlock it, and protect it with a different password, that is > automatically (randomly) created. [..] You should use the Thunderbird > feature to set a Master Password. Without a master password, your > OpenPGP keys in your profile directory are unprotected." > > These two answers prove to me that this feature isn't production-ready. > Protecting one of the most important items for personal privacy (the > GPG secret key) with just the thunderbird master password sounds like a > joke. In general, not relying on gpg strikes me as a bad idea, as > that's what allows sharing the same set of keys between different > applications. And being unable to share or even synchronize keys with > the de-facto-standard PGP encryption software seems - dumb, sorry. > > It's not your fault. But perhaps let it sit in the mozilla repo for > some more time. what I understood it was not a light decision to implement it like this. There was basically not much choice from what I know. The Mozilla platform does not allow that deep integration with the system anymore (with the removal of legacy extensions to webextensions only). Integrating or linking to GPG components then again would have been a platform specific one and also apparently license wise not really an option. Just waiting most likely won't change the situation because of that. For certain usecases a bit of GPG support is still available: https://wiki.mozilla.org/Thunderbird:OpenPGP:Smartcards Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] Filing bugs at https://bugzilla.opensuse.org/index.cgi
by Moby 17 Sep '20

17 Sep '20

I recently posted to the list about a problem with the latest update to icinga2 package on openSuSE Leap 15.2. With no luck so far, I decided to open a bug. I installed the source RPM to find the location to post bugs. in the SPEC file, it mentions "Please submit bugfixes or comments via https://bugs.opensuse.org/". I assume this means I can also go to this site to file bug reports. There is no clear indication of where to go to file bugs. Once I go to https://bugzilla.opensuse.org/index.cgi, I can find no hints as how to file a new bug. There are multiple "new" options on the site (new test case, new bug etc.) but no matter which "new" I go to, I can only get as far as choosing the product, after which I have no idea what to do. The system seems stuck on trying to search for "Test plans" etc. Am I at the wrong place to report a bug? Thank you in advance for your help, --Moby -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 10