January 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] SuSEfirewall2-fail2ban
by Marc Chamberlin 18 Jan '19

18 Jan '19

I thought I would throw this out for discussion based on my recent experience with this particular package. I installed this in my new installation of OpenSuSE15.0. I thought initially this package SuSEfirewall2-fail2ban was a good idea for integration between these two applications. But based on my recent experience with trying to install it I got to say either this package needs to be tossed or fixed, as it stands it seriously breaks SuSEfirewall2 and it is not an easy thing to debug. Some of the problems I had, once it was installed were - 1. It forces the startup of the fail2ban service each time SuSEfirewall service is started, not something you might want sometimes, and not easy to figure out how to discover and stop this relationship. 2. It has/causes dependency errors in the systemd launcher that breaks the ability of the SuSEfirewall service from starting properly. (this problem is widely talked about in other distros as well with their versions of firewalls, bug reports have been submitted, and no fix is yet available) 3. It caused/forced my networks internal NIC card to be relabeled as an external facing NIC, which then caused me to have 2 external facing NIC's and that broke all sorts of other services I had running on my server. (which led me on many wild goose chases trying to track down errors that other services such as Apache2, Tomcat, Apache James and even Named were reporting.) Given all the headaches this package caused me, my recommendation is to get rid of it, it is not really necessary AFAIK and my system seems to be running fine without it. Want to have some fun? Try it yourself, install the fail2ban service and this package also. Then restart the SuSEfirewall2 service and watch it belly ache. If you have two NICs like I do, one ext and one int then you will also see what happens with the int NIC. Yarrg! Marc... -- Linux Counter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 45

[opensuse] MD RAID output
by stakanov 16 Jan '19

16 Jan '19

cat /proc/mdstat Personalities : [raid1] md127 : active raid1 sdc1[2] sdb1[0] 976760640 blocks super 1.0 [2/2] [UU] bitmap: 2/8 pages [8KB], 65536KB chunk unused devices: <none> Is this a correctly working raid? I would say yes. UU should show it is working as expecte. But I do not understand sdc1(2) and sdb1(0). Could somebody shed some light on how to read this output correctly? What does (2) and the (0) stand for? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postf�cher sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 20

[opensuse] VirtualBox 6.0.0 Win7 guest (dir in cmd.exe takes 50% CPU)
by David C. Rankin 15 Jan '19

15 Jan '19

All, If any of you are running Win7 guest in virtualbox, I'm trying to nail down an issue and need some help. I basically keep a win7 guest on the server to access over the LAN with the --headless option to use to answer coding questions involving MinGW or VS. I have used this setup since Virtualbox 4. With the update to Virtualbox 6.0.0, the Command Prompt in the Win7 guest is rendered all but unusable. Something has changed that effects the ability to 'redraw' the terminal as lines are output (slowing output to that of a Dot-Matrix printer) Attempting to move the command prompt window (or PowerShell window) similarly results in artifacts left of the desktop which are slowly repainted to complete the move. I'm working the issue on the vbox-users-community list and I could use some additional input. With my setup I launch the Win7 guest while ssh'ed into the host server with: VBoxManage startvm Win7Pro_32bit --type headless (if needed I set the resolution for the guest with) VBoxManage controlvm "Win7Pro_32bit" setvideomodehint 1440 864 32 (I have done it this same way for years) With the install I have with vbox 5.2.22, there is no problem with the Command Prompt 'dir' listing in the Win7 guest. With 6.0.0 it takes 20.5 seconds to list 176 files (do you know how long 20.5 seconds is just waiting for a short directory list to complete is? -- it's really long) So does anyone else use Virtualbox to access headless windows 7 guest via their LAN? If so, open a Command Prompt and change to a directory with a 100 files or so and type 'dir' and let me know if it takes a painfully long time to complete while spiking the CPU usage by 40-50%. -- 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 5

[opensuse] Firefox javascript debugger
by Dave Howorth 15 Jan '19

15 Jan '19

I'm obviously missing something pretty basic, but can anybody tell me what? I want to debug a javascript program on a web page. So I fire up FF, go to the Tools menu and select Web Developer and then Debugger. The developer area opens at the bottom of the window but it is blank. Then I repeat the process and the developer area contains some ASCII art style buttons and two areas titled 'Breakpoints' and 'Watch Expressions' both containing text that says they are empty. It's all black text on a white background. Oh and there's just the top of some box showing above. I pasted an image at https://paste.opensuse.org/49017814 When I look at the mozilla MDN pages, they show the debugger as multi-coloured text on a black background and say there should be three areas at the bottom, with the right-hand one divided into four parts. So completely different. What am I missing? TIA, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] install Oracle Virtualbox in tumbleweed
by George from the tribe 15 Jan '19

15 Jan '19

6 10

[opensuse] Ready! Set! GO!!!
by Fraser_Bell 15 Jan '19

15 Jan '19

IMPORTANT: DO NOT REPLY ON THIS LIST!!! IMPORTANT: DO NOT REPLY ON THIS LIST!!! Replies or comments should be made on the openSUSE Project Mailing List. ================ *... and they're off!* <url>https://news.opensuse.org/2019/01/15/and-the-race-is-on-2018-2019-opensuse-…</url> <url>https://en.opensuse.org/openSUSE:Board_election#2018-2019_openSUSE_Board_Ca…</url> -- -Gerry Makaro openSUSE Board Elections Committee (election-officials **at** openSUSE.org) openSUSE Member openSUSE Global Moderator openSUSE Contributor YaST Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] TW: xfce4-notes
by ellanios82 14 Jan '19

14 Jan '19

- since recent TW zypper dup , cannot coax 'notes' to get started : trying to start from konsole , this is error message : " ~> /usr/bin/xfce4-notes /usr/share/themes/Breeze/gtk-2.0/widgets/styles:13: error: invalid string constant "toolbuttons", expected valid string constant /usr/share/themes/Breeze/gtk-2.0/widgets/styles:11: error: invalid string constant "scrolled_window", expected valid string constant" - any suggestions what i might try ? thanks ..... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 6

[opensuse] leap 15, Nouveau and kernel 4.12
by Frans de Boer 14 Jan '19

14 Jan '19

Finally changed the default kernel for leap 15. First 4.9.x and now 4.19.15. As expected, I got rid of tearing - mostly the bottom half of the screen - while using KDE zoom functionality. I guessed before that 4.12 had a problem with the Nouveau drivers so I changed to another kernel. Now finally I can use Leap 15 as my production environment. Strange, however, that nobody reported similar behavior before, at least not to my knowledge. Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Anybody find a clean UserChrome.css addition for Rounded Tabs in FF60esr?
by David C. Rankin 14 Jan '19

14 Jan '19

All, Web sites are slowly intentionally breaking compatibility with FF 52.9esr, so I bit the bullet and went to 60.4esr (from the update repo), and I'm trying (valiantly) to make this GTK3 monstrosity look palatable. One of the awkward looking features is the tabs at the top are now just square boxes (that frankly just look ugly, not to mention 40% taller) I have found some rather extensive UserChrome modes on github, e.g. https://github.com/wilfredwee/photon-australis which look pretty good, but seem heavy just to try and make Firefox look somewhat like it did in 52esr (from July) Does anyone have a tweak (or shorter version of the UserChrome additions) that will restore some of the rounded tab features to FF 60esr? Example Comparison of 52 -> 60 (screenshot) http://paste.opensuse.org/view//46109343 -- 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

[opensuse] Upgrading to OpenSuSE15.0 problems
by Marc Chamberlin 14 Jan '19

14 Jan '19

I am in the process of trying to upgrade one of my computers to OpenSuSE 15.0 and running into a number of problems. I first started with OpenSuSE42.3 x64 with the KDE/Plasma desktop, and I tried to do an in place straight upgrade. I will also mention that my OpenSuSE42.3 system had something broken with the network drivers so I did not have access to the internet directly from it. So I used my laptop to download the OpenSuSE 15.0 iso file and burned it to a DVD. I mention this because I am suspicious that this may be what is causing me some of the problems I am experiencing, though I do not understand why that should be the case. After my first attempt to upgrade my computer to 15.0 it failed to boot. My research lead me to discover that the installer had changed the grub configuration so that it was trying to make calls to linuxefi and initrdefi. I don't use the efi filesystem on this computer and have no desire to do so. (don't get me started on how much troubles I have had with efi. I use it on my laptop only because I am using solid state drives and it seems that I must use efi on it.) My BIOS in the computer I am trying to upgrade has EFI turned off and only uses legacy file management. So I manually edited the grub configuration file and removed the efi suffix of these calls, i.e. made calls to linux and initrd instead, and the boot up succeeded. However, that lead me to another mess, after logging in to my account, I discovered the KDE/Plasma desktop was not working properly. I had a few konsole windows that opened up (ones I had left open when I brought the system down) but the plasma part of the desktop was not there. No background, no kicker bar, no mouse activity or the ability to right click and bring up the pop up menu dialog etc. In other words almost useless, although all the services and background tasks I have configured to run started up fine. (things like Apache, Tomcat, Bind, DHCPD etc.) I don't know how to recover from this mess, I tried reinstalling all the KDE and Plasma packages but no joy, so I decided to try a different approach - My next attempt was to install OpenSuSE 15.0 into a new/separate partition but I cannot get past the partitioner. It appears it is trying to force me into using the EFI boot system. I don't allow the OpenSuSE installer's partitioner to decide for me (it's defaults) how to configure my system as it makes choices that I don't want. Instead I have it import all my mount points that I have defined in what was my OpenSuSE42.3 (now upgraded to a broken 15.0) system. That much works fine and I just move the mount point for / to a new partition so that the new OpenSuSE15.0 system will be mostly installed in a different partition and I can keep my old system for the time being. However when I tell the partitioner to accept all the new changes I get a complaint - "Missing device for /boot/efi with size equal or bigger than 256MiB and filesystem vfat." Why am I being forced into using EFI? My system/BIOS is configured to use the legacy boot loaders and explicitly turns off EFI! I cannot find any means of telling the OpenSuSE installer/partitioner to use the legacy method of boot loading either, so I am stuck. I have one other complaint about the OpenSuSE 15.0 installer/partitioner that I want to pass along as it almost destroyed my entire system, had I not caught it. After I told the partitioner to import all my mount points from my previous system, I fortunately observed that it had marked ALL of my mount point partitions to be formatted!!! That is just plain wrong, the user should NEVER have to opt out of having data destroyed, but have to opt in to having anything formatted. That modus operandi really needs to be reversed, formatting of any partition should never be done by default. I will listen to any arguments to the contrary but I feel pretty strongly that this should be reported as a bug and fixed. (I am willing to do so.) Appreciate any thoughts on how to install OpenSuSE 15.0 using the legacy boot loaders and not use EFI booting? Sorry for the long writeup and please forgive me if I didn't communicate this technically correctly, this is definitely not my area of expertise! ... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 12